Sirius's avatar
Sirius 3 months ago
Iris has had double ratchet messaging for a long time, but trying to support multi-device made it flaky. Now I made
iris chat
 which is single device and works pretty reliably. Using it to control my clawdbots. Had to set it up because whatsapp / signal setups were such a pain. Also I didn't want to use nip04 which would reveal all our chat history if the private key was ever leaked. On command line the clawdbot uses nostr double ratchet tool ndr in rust:
iris files
 And of course my clawdbots use git-remote-htree for decentralized code sharing on nost + blossom — not annoying github tokens. image

Replies (7)

Sirius's avatar
Sirius 3 months ago
At this point it's nice hacking, but not very productive yet. It needs to become more proactive and autonomous, while being conscious of token limits, or hopefully running on decent local models soon. But I think we'll have actually useful and easy to set up agents later this year.
1 replies ↓
Sirius's avatar
Sirius 2 months ago
512gb unified memory Mac ultras are interesting, but might wait for M5. Local LLM would be definitely good, there's so many parts in the remote LLM supply chain that can break.
Yegor Lapshov's avatar
Yegor Lapshov 1 month ago
Should we promote share as the primary way to onboard users from the web? It seems like the most effective tool to replace manual copy-pasting, making the transition from a browser to a Nostr client seamless for new users. I’m building a project right now and hit this exact wall. It’s easy to fix. I’ve just drafted a solution and shared it as NIP-222 on GitHub:
GitHub
Draft: NIP-222 - URI Scheme for Share Intents by Ty13rS2 · Pull Request #2266 · nostr-protocol/nips
Mobile UX for sharing into Nostr is broken. This draft proposes a standardized intent URI (nostr:share?text=...) to allow external web apps and gam...
 This would be a massive win for your client and the ecosystem as a whole. Take a look, would love to hear your thoughts on pushing this forward.
↑