Possible to use strfry as an archival relay (e.g. preventing deletes)?

[PaulCapestany]

I read through docs, searched through GitHub issues, and checked if any config options for setting a strfry instance up as an archival relay existed (e.g. preventing deleting of events), but didn't come across any obvious way to pull this off.

I could totally be missing something though, is there a straightforward way to achieve making a strfry instance "write-only"?

If not, might going the plugin route (preventing "delete" events from coming in) perhaps be the way to go I guess?

[hoytech]

Currently this is not possible. I will look into adding an "append-only" feature for archival relays.

Note that delete events aren't the only way events can be removed: There are replaceable/parameterised replaceable events, and events that can expire.

Also, would you want to archive ephemeral events too? These are supposed to be forwarded and then never stored.

[PaulCapestany]

I will look into adding an "append-only" feature for archival relays.

Thanks for your reply Doug—really appreciate you taking the idea into consideration!

Also, would you want to archive ephemeral events too? These are supposed to be forwarded and then never stored.

Some use cases for an append-only feature could be:

1. dev/testing purposes: being able to easily toggle whether to keep every event (including theoretically ephemeral events) could vastly improve troubleshooting/debugging Nostr interactions in certain scenarios
2. people who like to hoard all their data: it's very likely that various government agencies/mega-corps will be (if they aren't already) doing this, so, might as well give people the option to track their own digital footprint as well if they want to, right?