Oddbean

▲ ▼

 So we can’t try stuff out is what your are saying?

▲ ▼

 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.

▲ ▼

 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 @thenostrworld 

After @HORNETS 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 @HORNETS 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.

▲ ▼

 Mate, that’s not it at all… if you can’t take criticism, pack-up shop now.

I’m just pointing out why NNS doesn’t scale. It’s nothing personal.

▲ ▼

 I agree — let the best ideas win.

I’ll see you guys on the other side, where there are no URLs or missing notes. 🚀