Most relays don't respect expiration tags, and hardly any clients add them. Many relays ignore deletes or are sloppy about them, and the public relays are usually completely obsessed with archiving every ๐Ÿ‘๐Ÿปโค๏ธ๐Ÿคชโšก anyone ever posted ever. Most normal users assume more "monumental" events like longform articles or publications/books will be maintained, at least in the medium-term, so they put The Important Stuff in them. They don't usually realize that ABSOLUTELY EVERYTHING is being logged, catalogued, and archived, so that it can get dug back up in 10 years, to get thrown in their face. As soon as they realize this, and notice that no client has a delete button, they head for the exit. Universal event persistence is a protocol bug, not a feature.

Replies (7)

Default avatar
Deleted Account 6 months ago
100% agree with you on this. There is stuff worth archiving and then there is the 'sandpit' of everyday life where we want to experiment with life without non contextual 'blowback' in a decades time. Is anyone working on this? It's a really distinction that you raise here.
The problem is that with the exception of cases where you only post your notes on private relays, where there isn't much reach by definition, there's no way to guarantee the note won't be broadcast somewhere else and stored till time immemorial
Do you agree? > Universal event persistence is a protocol bug, not a feature. Reference:
Silberengel's avatar Silberengel
Most relays don't respect expiration tags, and hardly any clients add them. Many relays ignore deletes or are sloppy about them, and the public relays are usually completely obsessed with archiving every ๐Ÿ‘๐Ÿปโค๏ธ๐Ÿคชโšก anyone ever posted ever. Most normal users assume more "monumental" events like longform articles or publications/books will be maintained, at least in the medium-term, so they put The Important Stuff in them. They don't usually realize that ABSOLUTELY EVERYTHING is being logged, catalogued, and archived, so that it can get dug back up in 10 years, to get thrown in their face. As soon as they realize this, and notice that no client has a delete button, they head for the exit. Universal event persistence is a protocol bug, not a feature.
View quoted note →
Anything that you write for public view is persistent. It doesn't matter what protocol or service you use, and it definitely doesn't matter how many times you press the delete key. Once it's out, it's out, so think twice about how you identify (dox) yourself in every situation.
โ†‘