awesome!
not if you dont rly care ab your older notes one day dissappearing
eventually relay operators can clear up there storage if they dont have the means to upgrade data storage
also sometimes things happen as described above where switching clients can wipe the list of npubs you follow (have had that happen once, never again after), but this probably will be fixed in the future
also the media you upload through media hosting services, you need to backup your media yourself on hardware but i think only important if you are a content creator
luckily, you can spin up an own relay and store your notes to prevent all this OR use backup services like relayable.org and the one nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 is running (cant recall the name)
I don't care. If I did I would run my own relay. I consider this to be a feature of the protocol, not a bug.
I am pretty sure that is going to be the normal architecture in the future. It would be very easy to add fiatjaf's relay to any mobile app back end.
Tools to manage that backup wouldn't be hard to work out either, and you could have all kinds of parameters to pick out items that will persist in the cache longer than others, and have the cache back up these to an archive. Could be automated also, with a backup client on your PC. You could even have a flag you set that rebroadcasts old notes to keep them live on the network.
Thread collapsed