Point 2 is true but frankly I don’t see the issue, you’ll see that a person wrote a message they deleted, no exploitable information has been leaked, and if the account is ever deleted even that gets deleted too
Point 3 is outright false, the moment something is deleted, ActivityPub spreads a delete command to anything federating it
As an aside, the politics of the Lemmy creators are still mentioned a lot, but at this point the tankie population has been pretty much utterly outnumbered due to the Reddit migration, Lemmy has grown from a few hundred people to thousands and is STILL growing, hopefully it’s no longer an issue.
Hey, you wanna give more context to point 3? I only found comments regarding that delete will spread but the servers can (though should not I guess) just replace the deleted object with a “Tombstone” object and thus not really delete.
I’m busy right now, will look for the exact code snippets later, but in summary from what i read earlier when i first came across these claims last month or so, any activity that happens with a comment is also federated: Creation, editing and deletion, so barring any cache that will eventually expire, or an instance going down, the lifetime of a message will be replicated across anything that federates with it.
And yes, a patched instance could just ignore deletion and save everything, but at that point you’re fighting a rogue element and the rules change, we’re discussing the normal, designed behavior of the software.
OK, let’s check the status of that today:
As an aside, the politics of the Lemmy creators are still mentioned a lot, but at this point the tankie population has been pretty much utterly outnumbered due to the Reddit migration, Lemmy has grown from a few hundred people to thousands and is STILL growing, hopefully it’s no longer an issue.
Hey, you wanna give more context to point 3? I only found comments regarding that delete will spread but the servers can (though should not I guess) just replace the deleted object with a “Tombstone” object and thus not really delete.
I’m busy right now, will look for the exact code snippets later, but in summary from what i read earlier when i first came across these claims last month or so, any activity that happens with a comment is also federated: Creation, editing and deletion, so barring any cache that will eventually expire, or an instance going down, the lifetime of a message will be replicated across anything that federates with it.
And yes, a patched instance could just ignore deletion and save everything, but at that point you’re fighting a rogue element and the rules change, we’re discussing the normal, designed behavior of the software.