founders inc is unreal. went to their demo day in sf today. @fdotinc@super8n
a few that stuck:
- copilot for public market investors @DeepInsightLabs
- earbuds with a camera + ai built in @heyordo
- retail robots for restocking + online order picking @LucenRobotics
anyone else?
$12,368 in 1 Week spamming tiktok slideshows
- How to target USA
- How to bypass tiktok's duplicate detection
- How to PRINT with slideshows..
Retweet & Comment "Slideshow" (must be following) and I'll send you the link to the full guide.
If you have a lot of meetings,
use this free app.
There’s no time limit,
and since it runs on local AI,
your data never leaves your device.
This app is https://t.co/d8LHTikhXd - free, unlimited, offline AI voice notes.
LLM Knowledge Bases
Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So:
Data ingest:
I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them.
IDE:
I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides).
Q&A:
Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale.
Output:
Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base.
Linting:
I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into.
Extra tools:
I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries.
Further explorations:
As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows.
TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
오픈소스 무료 AI, 로컬 실행, 요약 및 번역 작업으로 사용하기에 괜찮아 보여요! 일단 설치해보고 써봐야겠습니다. 카이스트 학생이 직접 사용하려고 만들었다고 하네요. 지금은 macOS 앱만 제공중입니다. https://t.co/HqGvxKwnpY github Star 벌써 400개 넘음
“KAIST 학생이 직접 쓰려고 만든 AI 강의 필기앱
# 10,000시간을 써도 무료⏤ 서버, API 비용이 안들기 때문에 가능합니다. 결제도 안 붙였어요.
# 로컬 AI⏤ 서버가 없기 때문에 인터넷이 필요없어요.
# 철저한 보안⏤모든 내용은 사용자 PC에만 저장됩니다.
# 실시간 번역“
https://t.co/daGkEgkqVJ