If you’re down for a desktop webapp, let’s collab. We’re about to build the first nostr client to support cryptographically signed files on relays, thanks to the new Scionic Merkle Trees.
Discussion
nostr:note10t59fzta0ckyqw0tfdl70ef5ptzwfhp5cezpafa2m8d8svgnnkaqdppnn4
would love to chat more
We’d love if someone kept carrying the torch after we implement the file storage abilities into the webapp.🗽
This way the webapp client can be improved by its primary maintainer, and we can continue to optimize our #nostr relay’s syncing system.
The Strfry relay uses Merkle Tree syncing called Negentropy. Our syncing will require fewer rounds of communication between relays exchanging missing data, and will support file storage due to our new Scionic Merkle DAGs/Trees.
Negentropy requires relays to request one missing note at a time… this inherently slows it down. IPFS has a syncing protocol that works just like it called BitSwap, but they evolved it into GraphSync so that nodes can ask for a large range of missing notes/data in a single request.
Our syncing protocol will mimic what GraphSync did with ranged/batched requests, but for #nostr — we achieve the ranged requests in a simpler way too, without needing the complicated graphing system.
This is why we don’t want to lead the webapp development. We have a lot of work to do implementing our syncing system. So, if anyone is interested in teaming up I’m all for it.