Then you are just another centralized app. What's the point of nostr if we don't teach people ways to control their data?
Login to reply
Replies (3)
Yes, but not only that. It's actually about supporting the Outbox model, so that when I set my relay list on client A, they’re automatically used on apps B, C, and D. And having the peace of mind of knowing that if my connections do the same, clients will actually fetch from their relays; no more, no less.
Lots of apps let users edit Kind 10002 (and other list events) but still hardcode a bunch of default relays and media servers, meaning users don’t really have control over where their content is fetched from or sent to. Ultimately, this is about giving the user choice; and once those choices exist, actually respecting them.
This is the way for Stela to post her personal content to friends on a small selection of relays, and for Anthony to blast his Haven release notes to as many relays as he wants, without either side feeling cheated or locked into a model that doesn’t work for their needs.
Of course, this creates technical challenges and inconveniences, and requires users to have at least a surface-level understanding of relays. But in my mind, freedom trumps convenience. And I'm sure thay with time we can have both.
Yes. All nostr apps are centralized.
We can teach users how to create and use accounts and events across apps. But controlling data is a different matter. Censorship resistance, yes. Access management, no.
> All Nostr apps are centralized
lol. There are many apps that don't have main relays and just use what the user chooses. Just because you don't know or don't want to decentralize, it doesn't mean that all apps are centralized.