they wouldn't even be given any choice at first, outbox should handle it all for them. the client would look for the relay list of the npub they're trying to follow, in a predefined set (including nip65 specialized relays), which should be as large as possible. once the relay list is retrieved, thats a bunch of relays to explore, and in those relays, they might find hundreds of relay hints in events. thats how the magic happens, unless they're exploring nip70 dedicated relays. now if their point of entry is a relay, it's either: - amazing, a regular relay that relays events as it should - terrible, that relay is nip70 only, all the events are exclusive to it, no other relay hint can be found

this is a completely different scenario than what has been talked about for these NIPs. here the data probably does not hold any value to the point where people would broadcast the events, and nip63 doesnt apply, only nip70. in that case it makes sense, but the user needs to know that they could be rug pulled anytime by that google drive and dropbox, if they were to not care about the tag anymore. it would only be perfect in a scenario where the user owns both relays. so if that user wants peace of mind, i wouldn't recommend going with nostr. it unfortunately isn't a solution in every scenario. you know better than i do how nostr is, among a few other things, a solution to censorship, definitely not a solution to everything.

non-centralizing defaults come with outbox to begin with. however the user discovered nostr already gives a point of entry into the ecosystem, that could be following someone or connecting to a relay. and for obvious reasons, your third option is objectively the best, users need to have a basic idea of what goes on behind the UI so that they can make conscious choices. i agree with you that it gets really confusing, and thus the reason why this space needs more UX designers which are good at dealing with decentralized tools.

theres a fine line between relays having a personality/filtering/curating content and poorly attempting to make events exclusive to them. the idea of restricted access to events on nostr is a joke, thats just not compatible with the protocol. those NIPs are useless. there are and there should be a variety of relays, because of the need for incentives but also because some stuff just cannot be done client-side. now something i wish people looked more into is user or local communities owned relays - which are closer to the user - that's an opportunity to get done whatever is too heavy to do on clients there, making sure users have full control over it. even the outbox model would scale better that way, having clients fetch events from a home relay.

something pretty interesting about radicle: they claim to adopt a peer to peer archiecture that's based on a mix of secure scuttlebutt (very similar to nostr) and bitcoin lightning network

NIP 70 and NIP 68 are pointless possibilities, or useless proposals, whatever you want to call it. for the reason that they don't make sense with the 'core' protocol. get it now?

he didnt mean that literally, nostr clients talk to relays and relays talk back to clients. interoperability is actually achieved when the data back and forth with relays can be created/interacted with from different types of clients, each specialized in different nips

exactly. and a paywall fundamentally changes 'who has access and why' from a censorship resistant protocol to a gatekept permissioned one, which simply goes against that principle

in real life a simple tag won't make any difference its like printing something on paper and believing that just because you stamped it, people won't photocopy that paper. that is absurd. if the content on that paper is valuable then it's safe to assume people WILL keep a copy of it. that's the reason why scanners don't let you scan money nostr makes the whole process infinitely easier, its a matter of unchecking a box on your relay settings, and broadcasting the event with a single click

comparing paper with nostr... i hope you're joking. look im not trying to get philosophical here. its very simple, nostr has data portability designed at its very core, copying events, sharing and broadcasting them is what happens all day long on all relays relays are meant to relay events, not poorly attempt to gatekeep them its all up to the user if they want to take the "-" tag into account or not. if piracy was that easy, it wouldnt even be called piracy at that point and if you really still think it could work, in a dystopia where everyone respects that tag, look, companies could start using it in a detrimental way for users. say google for nostr, requiring auth on every connection, then we're right back to centralized systems