Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 0
Generated: 17:15:00
One of the potential issues that can happen on #nostr is replacing an editable event before it has been loaded yet. So if a client is slow at loading and the user starts a new (blank) copy of that event, it will potentially wipe the previous content. One example of this is Memos on nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qg6waehxw309aexjcn09ejh2tnwdaehgunfvyhxzurs9uqzp5daxvenwv7ucsglpm5f8vuts530cr0zylllgkwejpzvak0x2kqmehusjv The "New Memo" button was enabled while loading, so if you clicked it, it would create a new list of memos and the old memos would be wiped. It could also happen if you use the same account across multiple devices and you happen to be offline while doing some work, and when you come online, it can potentially result in data loss. Solved it by keeping a local backup of the last 10 edits, and allows you to perform merges if such an incident happens. You can already download a backup, but keeping an automatic history helps user even more. There is already a backup feature in Nostria to keep your following list and other events, yet I might implement a similar backup feature for your following lists that is automatic. image
2025-11-21 21:35:19 from 1 relay(s)
Login to reply