[JonathanBeuys]

You cannot self-host identity. You cannot self-host a social graph.

If people would host "abc liked my tweet" and "xyz follows me" on their own server, then everybody would claim that Billie Eilish liked all their tweets and Joe Biden is their best friend.

People go on social media for the social graph.

You can do that via a central authority (and live in fear that everything is taken from you) or you can do it via cryptographic proof. Self hosting is not a solution.

You also cannot host identity.

If your domain gets stolen from you (search for the horror stories on Google or HN search), your identity is gone. Nothing you can do against it, since you are at the mercy of authorities again: The registrars.

[devmor]

>If people would host "xyz liked my tweet" on their own server, then everybody would claim that Billie Eilish liked all their tweets.

This problem is what public key verification is literally made to solve.

If Billie Eilish likes your tweet, her client signs the like with her private key and sends the result to your server. Other clients can verify the like is real by looking at the result you send back with the "like" and verifying it against her public key.

Edit: The person I'm replying to has edited their post at least 3 separate times in the past couple minutes, adding multiple new lines to say different things, so if this disagreement to it ends up making no sense, you know why.

[rhn_mk1]

Sure you can self-host identity. Why would it be tied to a domain name? It is tied to a public key already, in e-ID systems, S/MIME, or GPG, Tor, blockchain, etc.

[ranger_danger]

have you not heard of the fediverse?

[mavhc]

only if you rely on a domain name for identity, instead of private/public keypairs

[GoblinSlayer]

>then everybody would claim that Billie Eilish liked all their tweets and Joe Biden is their best friend

Twitter bots already do that.