You should try stuff in your head and decide not to code it.
These problems are easy to sniff out beforehand.
But I guess thatās what these discussions are for too.
Discussion
Honestly, thereās no way nostr will expand without a few changesā¦ but this NIP creates more problems than it solves.
Propose a better solution, have some stake in the game at the very least so we can entertain it.
The spec of the better solution will be released before the next nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l
After nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g launches on the 4th of July š
Buckle-up. š¢
We arenāt coding anything, itās a proposed NIP and we are having a discussion about it? Calling it a pile of garbage because obviously you know better and saying you wonāt use it because apparently you think so highly of yourself isnāt helping this discussion.
But fine, itās a pile of garbage, whats your solution? I bet itās perfect.
We do have a solutionā¦ Development is already underway. Youāll see soon enough. It scales outbox.
I outlined exactly why NNS breaks ā but you only focused on the mean part of my comment. Focus on the meat of what I said before that.
When the spec is ready, Iāll make sure to share it here first. Iām drowning in work atm preparing for launching nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g on the 4th of July, but after that it and Nestr are my main focus.
Be patient and I promise not to disappoint. š Iāve been trying to scale the CAP Theorem parameters of Nostr for 2 years straight now, so I get disgruntled when I see half-baked solutions that make relay discovery even more difficult.
Great. Donāt get mad at other people trying out their ideas too just because you have yours.
Let the best idea win out in the game.