Nostr Web Client

also, yeah, main thing it's useful for now is you can back up your events (though that may also be buggy, but worth trying) and you can search and delete your events (if clients support it, some do, jumble at least, and forks, you can also do it there)

the relay honors the request, stores the delete event and deletes the referenced events from the delete. the clients might be better to use for general deleting, but likely not all of your relays actually do it. but at least, on the relays that do, they will never let anyone upload the deleted event again

Comte de Sats Germain 1mo ago 💬 1

Backing up events is super needed. Could also be cool to turn backed up events into a website like a blog, for highlighting certain things or integrating nostr npubs with a business webpage

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1mo ago

yeah, currently i have not enabled you to upload a backup of events as a regular (write) user, but probably i should, just make a size limit and time-based allowance so users of the relay can migrate old stuff to a new relay they are using.

i figured for now, a user could message the relay operator to ask to upload a provided event jsonl file but that also isn't implemented fully yet, the pubkey in the nip-11 info does not forward messages to actual admins, that is also a part of the DM interface feature, so that you basically can just copy that npub from the relay information and follow it and message to it and then it forwards to the admins who can then reply back to you, maybe with some mechanism to send the user a note from the added relay npub that you have a message from an admin npub.

lots to think about.

but yeah, step by step, orly is going to be the go-to relay for nostr deployments. because it will do everything everyone needs, with full control and no stupid opinions like too many relay devs have.