{"type":"rich","version":"1.0","title":"codonaft wrote","author_name":"codonaft (npub1al…7rg94)","author_url":"https://nostr.now/npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94","provider_name":"njump","provider_url":"https://nostr.now","html":"Thanks for your efforts. I took a brief look; the UI idea is cute.\n\nI hope to not be overwhelming with the inquiries; let me know if I am.\n\nDoes it appear to be privacy-respecting and with no lock-in? Is it possibly FOSS in the future?\n\nIs it designed to store things only in browser, and as the tuno files on disk, and never to sync over network?\n\nAn obvious question arises: what about storing nostr events in it? Or any standardized things (which I'm not aware of any better). Not asking as some nostr cult leader, there are a few fundamental things I'm not happy about with the protocol, but I think a lot of stuff is useful for your problem, already solved in an adequate way. Even for offline-only software, if you're targeting it.\n\nI think storing things in the standardized events will make your software more competitive in multiple ways: users will be more confident to use it because there would no be a soft lock-in (besides the usual hard lock-in people experience in projects with no takeout/export button, there's also always a possibility of the \"it's a goodbye letter, we're out of business, here's how you can export your jsons\" thing, which leaves users with incompatible, non-standard, hardly useful stuff out of the blue; it's problematic even for FOSS projects), and there are lots of things would be possible (almost) out of the box (like private sync over network or share/collaboration even)."}