Replying to Avatar fiatjaf

this is what happens in the future if the "outbox-is-broken-let's-use-smart-proxy-relays" people win:

- people start relying on "caching services" to fetch their notes. now every client must run their own caching service to remain competitive.

- as the network grows, syncing from all relays becomes more and more prohibitively and databases grow to the infinite.

- less and less caching services exist, but a "local best scenario" would be if we had like 4 different clients/caching-services to read from, but then if one of them banned alex jones that would mean 25% of users lose access to alex jones. there is nothing alex jones can do to change that.

- users could switch from app A to app B that hasn't banned alex jones, but app B had already banned donald trump, so that move is questionable and uncertain. anyway, it's too much friction for a user who doesn't know how to find this caching-service setting buried deep in their settings (because UX specialists said that's the best place to put it).

- eventually it makes no sense to switch anymore and as one of the caching services gains more market share they merge with the others, saving costs and regulatory burden (these caching servers are so big they need to do spam moderation, find and delete pornography and scam bots, comply with government takedowns, defend themselves against lawsuits, it's a huge cost), so it's much better to just have a single caching-service.

- everybody still publishes to their own relay, so nostr becomes exactly like bluesky and the central service can censor anyone. eventually people give up the stupidity of using intermediary relays and just publish directly to that central service.

- that central service now can serve you ads and blue checks, shadowban everybody who doesn't pay, modify your feed with amazing AI techniques to keep you engaged and prevent you from seeing anything they don't want you to see but keep you nourished with memes.

Aggregator/broadcaster relays can also implement the mailbox model, like wine just did.

Reply to this note

Please Login to reply.

Discussion

I don't know what a mailbox is, but if you mean the thing about accepting private events and only serving them to the rightful user after AUTH then yes, that's a good thing, but completely irrelevant to this discussion. inbox.nostr.wine is different than filter.nostr.wine. Completely different roles.

I meant that they have implemented NIP-65.

That is just a dumb list of relays.

It looks at their preferred relays and targets those, rather than just writing to a fixed list.

We use NIP-65 on the broadcast side now. More to come soon 😁

nostr:note18a4wfnk2e9rzuh8hj6szfr9rr6yhtt5ylx76cqeprpgzemrp5tysz7cl58

Can you exclude mutes? I'm going absolutely nuts switching clients, so often.

It could be done but it would be a bit wonky since we would need to filter out those mutes in real time (no negative nostr filters).

We are working on a more personalized solution too but still lots to do!

Okay, then I'll wait for you to wow me, instead. You're the data guy, so you're probably thinking of things I haven't thought of, yet.