| >If it's an instance level ban, then you can vote with your feet by migrating to a new instance. That's the part that interests me the most. Which is why I (when I get around to it) will self-host my own ActivityPub instance (Mastodon? Pleroma? WriteFreely?). That way, I decide what gets blocked and what doesn't. And since it's federated (assuming other sites will federate with me), I can still access the benefits of using fediverse resources, without being beholden to someone else to make such decisions for me. From a longer-term perspective, ISTM that an ActiviyPub (AP) "user agent server" (UAS) which allowed individual users to federate with the resources of their choosing without having to "join" an extant instance, makes a lot of sense. Rather the UAS would utilize your local (i.e., generated and managed/federated from your AP UAS instance) fediverse credentials and act as a proxy for you, communicating with the instances containing the resources you're interacting with and acting as storage/cache/server for the user's client apps. This would make the fediverse even more decentralized and under user control. However, it would also make discoverability even harder. Perhaps that's ActivityPub's killer app? A discovery app. Perhaps a protocol change to require a cryptographically signed summary/intro for each instance, along with with a searchable index? |