Subnostr

Replying to

PABLOF7z

It’s not about trying to control really; we just need better usage patterns on clients

It’s absurd trying to have all/most content in all relays: leads to centralization.

The gossip-style relay usage (I’m implementing it in NDK) and better relay groups selection in clients will fix this

yunginter.net 2y ago

Shouldn’t a relay just be able to say “no rebroadcast” and the white list clients that respect this?

Whitelist because you can’t force clients to respect it.

I’d love to build locals/discord/Patreon like functionality, but it just doesn’t work if you interact with it and your client rebroadcast it WillyNilly.

Reply to this note

Please Login to reply.

Discussion

PABLOF7z 2y ago

I don't think you can prevent an event from being published to it, other than enforcing some kind of whitelist, whether it's pubkey, tag, whatever based.

that's what I mean by clients needing to interact with relays better and de-commoditize them.

We'll get there

yunginter.net 2y ago

when you say “publish to it” what is the it?

yunginter.net 2y ago

I’m suggesting a client respect a relay running a no rebroadcast nip, so if it pulls from that relay, and then I interact with it, it won’t rebroadcast the note I’m replying too if it came from the topic specific relay. I’m not suggesting relays stop it from being published too.