Damus
Alex Gleason profile picture
Alex Gleason
@Alex Gleason
I've gone back and forth on whether relays should be infrastructure or communities, and by now I'm firmly in the "infrastructure" camp. They should be a boring implementation detail that users should never have to think about unless something is wrong - like DNS.
121❤️5💯1🤙1
utxo the webmaster 🧑‍💻 · 6d
you don't think there are good private applications for relays? that would require auth / not leaking that you're tagged in a note
mar · 6d
Relays shouldn’t become communities. If they do, we just recreate centralized hubs all over again. Relays in Nostr are infrastructure. They store and forward events. That’s their job. They should get a little smarter, better syncing between relays, small optimizations, basic spam control. But ...
feld · 6d
How are relays effecting dealing with spam these days? Looking for insights from someone who probably knows so I don't have to weed through stupid posts from a search engine
Sebastix · 5d
Agree, relays are infrastructure. The network facilitating the broadcasting. Upon that, communities can be build. They need to have a common ground where people can interact. With that said, a community can be a (smart) relay. But a relay is not a community.
Niel Liesmons · 5d
Yup :110percent: . End users should by default only be concerned with what communities they engage with. Those communities just happen to use whatever combo of relays, blossoms, moqs, mints, content types, white-lists.... they need. Specified in one community definition event. Signed by the comm...
Constant · 5d
well, time to go either back or forth again, because you are wrong. But the response needs an article i notice. TLDR for article not yet written: >You have: Things(events), People(Npubs), Places(relays). >''To Nostr'', on the read side, is to query, and you can play around with the specification s...