nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau may I ask you "where" or more precisely on which relays our relay lists are published? I couldn't find this info in nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 's article about the outbox model.

It must be a handful of specific relays that all clients which use the outbox model have to agree upon, right? Or does it work differently?

If you don't want to explain in detail I'd be happy about a link, too 💜

Reply to this note

Please Login to reply.

Discussion

The relay lists should be published to as many relays as possible. That's why they need to be small. These records are the main points to get people to find you and your posts. So, they should be everywhere.

i've been calling for this for a while but it raises a spam problem

user metadata, relay lists, follows, mutes, all of these need to be everywhere

how do we go about making sure they end up on as many relays as possible without opening up a spam attack vector?

Only the outbox lists must be everywhere.

The outbox list is like a DNS, it points to where (which relays) your metadata, mutelists, follows ect are. So, you don't need these other events everywhere. They can all be hosted by the user's home relay.

well, that makes it simpler

relays could be broadcasting updates to them and fix that problem, still need some sort of rate limiter but this narrows down what you actually need to give auth-free access to

How do we achieve that goal in Amethyst for example?

Do we automatically publish our outbox and inbox relay lists to all relays under "general relays"?