@armedevi
iAccount based inIndia
About this account
- Account based in
- India
- Connected via
- India App Store
Account-level information from X, not a live location or the device used for a specific post.
Building @presenttenseio: live web pages sent between browsers, not video. Also Khayal, a local-first second brain. SE @electrolux.
127.0.0.1
Joined December 2019
- Tweets200
- Following218
- Followers22
- Likes4.6K
Years ago I built a toy that let one browser follow another. Cursor, clicks, scrolling, all synced through DOM selectors. It worked, and I shelved it anyway.
Two reasons. Selectors are meaningless outside the page they came from, so one different div and "click this" lands on the wrong thing. And replaying my input on your page means I'm driving your logged-in session, which isn't screen sharing, it's session hijacking with extra steps.
Both turned out to be the same bug. "This" and "here" only mean something where they're said.
I'm building the version that resolves what I meant on your side instead. Posting the decisions here as I go.
Pinch to zoom on a screen share and you get bigger blur. This is real text, so it just gets bigger.
nitter.cf/presenttenseio/status/…
Sending "highlight this element" from one browser to another sounds easy until the other browser's page isn't identical.
I nearly shipped a confidence score for matching elements. Sat there picking a default threshold and realised I had no principled way to choose one.
The id either resolves or it doesn't. Fuzzy matching layered on an explicit identifier is just a slower way to get it wrong.
Cant wait to create one for @presenttenseio the vibe of pages everywhere matches so much with our product
Shipped Khayal v1.1.2
- Better semantic search (chunk-level)
- Proactive connections after capture
- Entity extraction
- Optional AI answers over your vault
Still fully local + plain markdown.
khayal.rawnaqs.io
All that fancy compute, and still not unlocking the power of instant capture, feels like a waste.
We’re recreating the Second Brain productivity trap with AI memory.
Capture everything. Summarize everything. Put it in Obsidian. Add embeddings. Retrieve two relevant notes and declare that your AI now “knows you.”
We did this before.
We reorganized our notes, redesigned our PARA folders, added backlinks and spent Sunday afternoon watching videos about how to improve the system that was supposed to save us time.
The outline looked fantastic, so the experiment was a success.
Retrieval isn’t the interesting test of AI memory.
The interesting test is whether retained knowledge improves future work when you don’t already know what should be retrieved.
Did it preserve the right decision? Did it know what was superseded? Can it distinguish evidence from speculation? Did it surface the constraint you forgot existed? Did the next worker produce a better outcome because of it?
Otherwise we’ve taken the Second Brain, given it a vector database, and started calling it intelligence.
Armedev retweeted
First, they're building for enterprise.
Then, they're building for degens.
Now, they're building for clawdbot agents.
Wen they building working drivers for my printer?
My WezTerm has GPU acceleration but my code still runs like it's 1995 - skill issue??
#wezterm