nostr:npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9 I can completely understand why you are frustrated. I believe in the model of releasing early and iterating through feedback.
I intended to have released something bare bones much earlier but for (1) shifting ideas about the protocol and mistakes such as (2) premature optimisations and (3) writing code with very good test coverage that likely to completely change.
When nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 posted the nip proposal, it was a trigger for me to push how what I had, pretty much in the state it was in.
Yes it is a bit embarrassing that it is full of bugs and the half-baked 'optimisation' are causing many issues but it was definitely a good thing. It means I can discuss the approach with the community and get feedback. I can shape their ideas and the community can shape mine. Together we will work towards a better solution faster.
I encourage you to get involved in the conversation, explore the different approaches and see what you can incorporate or ideas you can share. https://github.com/nostr-protocol/nips/pull/997 is a good place to start.
I wish you all the best.
Once we release, I encourage you to check out our specification. We solved a lot of problems you asked us about in Japan, including permissions. Repository state and distribution is fully thought-out too, with signed Merkle DAGs.
Everyone is free to act how they see fit. We shouldn’t be too much longer now. Maybe we will all converge on a standard. 🐣
I'm hoping that there will be lots of innovation with different clients and experiences that cater for different needs but it in an interoperable way. I encourage you to write up your spec and share it because the conversations are happening now about the standards. We will all be more open to different ideas now than when a standard is agreed.
