ABH3PO's avatar
ABH3PO abhay@formstr.app 4 months ago
Ahh this is the problem and the paradigm shift with nostr. There is no authoritative record. The GitHub repository is treated as such but im arguing that it shouldn't be. Even NIP-01 isnt necessary in its entirety to be interoperable the only thing necessary is following libsecp56k1 for key derivations and signatures. The fact that the GitHub repository is exist and as dogmatic as it is, is intact a problem.
↑ Parent

Replies (3)

ABH3PO's avatar
ABH3PO abhay@formstr.app 4 months ago
The sync issue sbouldnt have happened at all, because there should have been no reason to sync at all.
ABH3PO's avatar
ABH3PO abhay@formstr.app 4 months ago
Not being strawmanned at all. I really do mean it, all of the rest really is just strung together ideas of what can work to achieve your goals. Goals that can be different for different people, need to true censorship resistance? Use gossip. Need media servers with nostr identities? Use blossom. Need http auth? Use nip-98 or whatever it is. This is what makes nostr special, the fact that it can be stripped to its bare necessities. Also you've established that its not your circus, I dont mean to pull you in, just stating the facts as they appear. Libsecp256k1k is at the heart. Use it and you get the reusable ideaBritt. Event structure is the next most basic part, use this and you get 80% of the interoperability, add websockets and it is the protocol as we see it today.
1 replies ↓
↑