I’ve been using federated social media for a while now and I recently considered setting up an instance for my local community as a sort of Facebook alternative. However, as I thought about it, I wondered if ActivityPub’s deletion problem (i.e. if a user deletes their content on their server it doesn’t guarantee the content being deleted on other servers) is a fatal flaw. I worry that it would be difficult to secure buy-in from people if they were made aware of this issue, which they have the right to. It does make me wonder if the ATProtocol will be the better protocol if and when it becomes open source.
I’m curious as to other drivers users’ thoughts. While it is an issue that we may be happy to live with given the numerous other benefits ActivityPub provides, is it a flaw that will ultimately prevent wide scale adoption?
I don’t actually think it’s safe to say that. I suspect that most people wouldn’t be very concerned about ActivityPub’s “best effort” federated deletion. But without actually polling people, I don’t think that either of these theories holds enough water to call “safe to say.”
Sorry I forgot to address your point - migrating people to a more technical setup would be a challenge in itself, but then informing them that deletion across servers isn’t guaranteed would likely give them cold feet.
FWIW, it’s fairly rare for a deletion to not propagate. And I’ve yet to come across a rogue instance intentionally refusing to honor deletions. If we did, our instance would defederate from it.
Good point :)
I’d hazard a guess that ActivityPub users are a small portion of the population, especially considering the people I’m thinking of setting a server up for are Facebook users in a medium sized town - mostly people over the age of 40 who only started using social media in the past ten years.
It’s no secret that onboarding is a barrier to entry for Mastodon for example, and even then most people likely haven’t even heard of it. I am the only person on any of my social circles who is aware of it.