Open mikedilger opened 3 months ago
Thank you for sharing your thoughts! I agree with what you propose; the only issue with re-doing nostr is like nearly zero interest I have witnessed since my original proposal here. So I am glad that the interest appears, let's try to build a community around that and work on the task!
Someone pointed me to your thoughts on nostr post here: https://dr.orlovsky.ch/blog/thoughts-on-nostr
I think you have identified a number of real problems with nostr that would require a do-over to get right. But there are more. I would hate to see a redo of nostr that only fixed some of the problems. For this reason I hope to persuade you to work with other/existing nostr developers if and when we start over so that we can fix all of it once and for all, and not create a bunch of non-interoperable competing forks. That being said, I don't think anyone is working on a nostr2 right now, we just think about it from time to time and toss the idea around.
I've been involved in a nostr client (gossip) and NIP development of nostr for a few years now and I've been collecting notes on all the things we ought to change if we started over (or at least what we should discuss before settling on a new standard) here: https://github.com/mikedilger/nostr-next
NOTE: I'm adding this issue here instead of nrps because nrps doesn't have issues.