Happy to have inspired π Having a real DB that juggles between memory and disk and saves the indexes sure makes sense. I could try and see if nostr-social-graph could use indexeddb and not have to load everything into memory on app start. For native, I've made a social graph pull request to nostrdb: https://github.com/mmalmi/nostrdb
https://x21.social/ doesn't load for me, blank page π¬
or at least web clients should be loaded content-addressed, over nostr
Online beefs should be settled on Airchat. No keyboard warriors there.
When servers are needed, instead of DNS bound APIs we'll be able to use double ratchet or MLS channels soonβ’.
Nostr apps should be served over Nostr, independently of DNS, CAs and host servers. Nostr app env can provide key management, relay connections and event storage without every app having to duplicate. Ideally, this would happen on the browser or even OS level.
What's trusted / untrusted?
Tauri version of this would be interesting. Independent of DNS + CA + host server, doesn't update without the user knowing. Could use native keystore outside the browser renderer.
What would it take to make Brave browser add Nostr sign in, event storage and relay connections?
Parent web app could run relay conns & event storage and child apps could communicate with it over postMessage
I did not find source code for 44billion.net. Is there a spec for this "napp" packaging?
If Github is to be used as a trusted source, it's best to host the whole UI from there. The other domains could always make it not use Github and re-prompt your nsec, or use it in a manner you did not authorize etc. That said, it's a cool project β nostr apps would benefit from OS / browser level integration that takes care of key management, event storage and relay connections without every app having to do it.
Welcome to Martti Malmi spacestr profile!
About Me
developing iris.to
Interests
- No interests listed.