4 ms·

A fair point regarding exporting/importing, though again, self-hosting is the real answer if you're concerned about deplatforming in that context. > That is th

A fair point regarding exporting/importing, though again, self-hosting is the real answer if you're concerned about deplatforming in that context. > That is the benefit of decentralized solutions. Your identity and history can not be deleted or changed by a single actor. Yes, in consensus systems, but how much this is a benefit is an open question. Perhaps you find yourself in a situation where you actually do want to modify/delete your identity and/or history (cleaning up a drunk post, for instance?) and now it's technically impossible. In this case, having it stored somewhere mutable by a trusted host gives you the ability to make that change. On the other hand, maybe (the rhetorical) you are okay with these being immutable because it's more honest about what really happened and doesn't let people artificially clean up after themselves. I think an argument could be made for both approaches depending on what someone wants from their decentralized Twitter clone.

ArtTimeInvestor 5y ago
Is self-hosting really a solution? On a self-hosted instance, how do you prove to people that you are displaying the truth? That you really wrote that great prediction last year and not yesterday? That some popular person liked your post? That your post got 10000 likes and not just 3? That it really was Paul Graham who commented on it? And if you lose your domain, you lose your identity. There are horror stories out there, where businesses are destroyed because incompetent registrars gave the domain away. Again, you would need a decentralized solution like ENS to prevent that. There are decentralized solutions which allow the author of a piece of data to update or delete it. It is just a matter of incentives. When the protocol has a way for the author to update or delete content, that just means storing the old version of the content is not incentivised anymore.
- mariusor 5y ago
  > On a self-hosted instance, how do you prove to people [...] Generally the ActivityPub protocol disseminates a user's actions to a number of other users. On Mastodon specifically all users mentioned in a post will receive copies. Activities generated by users on other servers can be double checked against their own servers for validity, I think there's very few things that you can game when you're running your own instance without people being able to verify based on what these other instances have received.

ArtTimeInvestor 5y ago

Is self-hosting really a solution? On a self-hosted instance, how do you prove to people that you are displaying the truth? That you really wrote that great prediction last year and not yesterday? That some popular person liked your post? That your post got 10000 likes and not just 3? That it really was Paul Graham who commented on it? And if you lose your domain, you lose your identity. There are horror stories out there, where businesses are destroyed because incompetent registrars gave the domain away. Again, you would need a decentralized solution like ENS to prevent that. There are decentralized solutions which allow the author of a piece of data to update or delete it. It is just a matter of incentives. When the protocol has a way for the author to update or delete content, that just means storing the old version of the content is not incentivised anymore.

mariusor 5y ago
> On a self-hosted instance, how do you prove to people [...] Generally the ActivityPub protocol disseminates a user's actions to a number of other users. On Mastodon specifically all users mentioned in a post will receive copies. Activities generated by users on other servers can be double checked against their own servers for validity, I think there's very few things that you can game when you're running your own instance without people being able to verify based on what these other instances have received.