PABLOF7z @PABLOF7z - 1y
the sad state of nostr we must do better than this or we're fucked
B.O.P @B.O.P - 1y
I don’t understand what about this is sad, genuinely wondering
Derek Ross @Derek Ross - 1y
Yes.
Gossip. All clients need to implement Gossip in a similar fashion to Snort or something similar.
it's incredibly centralizing. Continuing that status quo would mean a guaranteed failure for nostr
Exactly.
Vitor Pamplona @Vitor Pamplona - 1y
We will or I will die trying.
🤝 same
mattybs @mattybs - 1y
It's centralized
7cc32 - 1y
97c70 - 1y
Just remember that our current "big" relays are incredibly small if nostr succeeds. Relay hints being signed also help heal the network. Even if everyone uses the hubs, outliers can still force hubs to route to them, if hubs want any content with inbox-model-generated hints.
do any gossip implementations post replies to the relay hint from the note it's replying to?
SamSamskies @SamSamskies - 1y
It’s easy to change your relays, so why does it matter? If they go down or start doing something you don’t like, you can switch relays in a second.
I don’t necessarily think it’s a “guaranteed failure”, it’s a free market, if relays perform a service well then more users will add them. If they start to do things like censoring users, etc, people will drop them and search for alternatives quickly.
Coracle doesn't, but I do publish replies to the user's NIP 65 inbox relays. The reason being there's not really a mechanism to self-hint that I'm aware of. I suppose `r` tags could be used, but those are frequently used for other things.
it's grossly not enough to be able to change your relays using hubs relays masquerades the fact that clients are wildly still not good enough to find events where they should and that if you are not publishing in a centralized relay you are a second-class citizen it doesn't even require malice from the relay operators, sheer scale would crash nostr if "just add X and Y relay and use blastr just to be sure" is how we scale
complacency, hell of a drug
Greg @gregwhite - 1y
Yeah I wanted to help make it easy to publish updated sets of relays using https://relay.guide but not every client uses the same system for respecting a user’s preferred relays. If we could agree a bit more on that then a combo of Relay Guide and a backup tool could make it really easy
signal_and_rage ☕️ @signal_and_rage ☕️ - 1y
Please ELI5
No. That’s how you end up with a single huge relay called relay.x.com. This is the equivalent of bcash. Bitcoin nodes must jeep state in sync and the limited blocksize is the compromise we make to make that possible. Nostr can’t limit the amount of data it produces.
DHTs do not scale well with small pieces of content. The hash map ends up occupying almost as much space as the content itself.
