A double coincidence of wants? I want to type. You want to read. I send to our relays. Relays' delete-timers start. Your client needs to pull from our relay(s) before deleted. The shorter the relay delete-timer, the lower the relay costs, and the more constant your client needs to be online and pulling. You wake up in the morning and read my notes, long after they've been deleted from our relays. So we'll either have to pay the relays, or have an always-on client? Something like that?
Discussion
The sender and/or the reader will need to pay for longevity, somehow, somewhere.
There is a heck of a lot of empty storage on remote servers, personal devices and USB sticks.
Idk, I only have about 1TB free to share ATM, which according to nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w is practically useless
It wouldn't need to be that short. Storage is cheap and json is tiny. I was thinking more like weeks on the very biggest, months on the mid-sized, years on the smaller, indefinitely on personal devices.
Datacenters currently store documents I wrote literally decades ago and I don't even know what all is in those folders and I don't care. 🤷♀️
Just deleting older versions of notes or notes that had been marked "delete" would help. Relays currently store EVERYTHING, even if the user specifically asked them to delete it.