I think that while #ActivityPub provides possibilities, it also has problems if you plan to roll your own implementation like for your blog.
Then you have to fight against follow bots, spam, etc. by yourself. Very much like it was fought when blogs had open comments, but I don't know how bad it is.
Even if #Mastodon doesn't become super de-centralized it's still an improvement, as it allows bigger players to fight out each other. Lot like with E-mail servers.
But how would you design such a protocol to address those problems?
@volkris I don't think they are solvable without human labor. Even in fully decentralized social networks like Nostr and ScuttleButt they need to be addressed somehow.
Usually, people form groups and pay somehow for someone to deal with bots, spam, block other people, etc...
Here the single group is a single server where the admins get paid, but in fully decentralized networks people must form groups, and set someone to oversee and moderate.
I don't see an answer to "how" in that :)
I'm kidding, well half kidding.
From my perspective, it's not a problem that can or should be solved at the protocol level. Yeah, I agree that it requires human labor, and I'd put it as a social problem that requires a social, not technical, solution.
Me, I'm often drawn toward solutions that are fully decentralized, empowering end users to shape their experiences, especially by using web of trust type techniques to avoid interactions that they'd rather not get into.
And that probably wouldn't integrate down into the protocol
