All nostr.build serves is media not text, so if it goes down, we just have broken media(kind 0, 1 pictures, audio, & videos) not the core text and all notes still work.

You'd have to solve global CDNs, and getting a different media handler wouldn't be no lesser evil because it's all just as centralized if Mystery-Owner-1 transfers it to Mystery-Owner-2. Maybe we offload all our images onto the relays but nostr won't scale any bigger if all new users have to pay upfront to post before they even learn conviction for the protocol.

I'm not trying to tell you you're completely wrong, it's just a really complex problem and hinting at things should change without proposing a solution/NIP doesn't move the wheel forward.

Keep thinking/learning about it all and maybe you'll end up contributing an important stepping stone later on.

Reply to this note

Please Login to reply.

Discussion

The solution at some point will need to be what IPFS promised but never realistically delivered.

Files become special notes with a specific hash that are replicated across relays.

The second part is making all phone users becoming relays themselves, in essence making hard to go after tens of thousand relays hosting content.

Third step is encrypting that content on the devices, make sure node operators are not held responsible for the content hosted on their device.

phone users won't become relays. that will just kill the battery. phone users running their own relays at home in some way would work though, the same way we run lightning nodes on the pc, not at the phone. if not i2p, maybe, we could use torrents&magnet in some form? free message sizes could be limited to encourage this

You'd be surprised with the efficiency of push notifications.

I've got a personal nostr relay running on my phone, uses like 3% of the battery across the day.

This happens because there is no display involved, which tends to eat the most energy.