Oddbean new post about login | logout #testing. I thought if i post here, it doesn't go to all my relays but only to this one relay.
@cloud fodder that was me posting on tig's relay and it showed up everywhere. Weird..
Depending on your client you use and depending on relay settings for mirroring other relays you can post on one single but still show at some others. This is amethyst for choosing where to post. https://image.nostr.build/737a1240cbbdbdfd293503e2882723f5d06f16daef2defa42c77bcf929e7d3f6.jpg https://image.nostr.build/af5ad9bb13a8a8a13f7b02d3666bf86009bff56c8db68e539bc6eadbb75370d0.jpg
I posted directly to the relay itself didn’t use a gui client
when you send to one relay, the note will usually leak out to the wider network. that can happen if someone replies, or reacts or boosts. and also if search engines scrape the relay and it shows on nostr.band etc. thats why i have been thinking a lot lately about multipubs
right i recall you saying this. but didn't realize how much leakage. i have been spamming everyone inadvertently. however with the LNBits relays they can be used quietly for testing and i can spin up an infinite number over there. Been doing instead recently as I noticed the nostr1.com relays propagate super fast.
lemme guess this actually might have something to do with strfry's " negentropy syncing protocol." its super smart and efficient the way its done, but production not staging :P
that is a small part of it, though I'm unsure how many use negentropy and how many are simply doing basic scrapers.. a lot of this is actually clients, when two or more people add a relay, and they see a message they like, they comment or etc, and it blasts out to all their relays. this is all client side optimization for "event not found" stuff.. eventually it will be nice if they didn't have to do this and could simply use relay hints, outbox etc. but for now, it does make nostr 'work better' for the twitter model. then on top of that, the scrapers are looking at nostr.watch and if the relay is there, you can pretty much know it's part of a huge shadowy supercoder network shuttling messages around. nostr1 does not do any of this pro-actively, it just happens once nostr.watch sees the relay via the relay lists. ```curl https://api.nostr.watch/v1/online |jq``` we all like seeing notes so much and growing nostr, test messages tend get a lot of engagement lol..
