|
Top-level
 @polotek The thing is, with Mastodon software, tools for controlling federation choices (both individually and at the instance level) are very limited in Mastodon. Allow-list federation at the instance level is strongly discouraged by Mastodon and cumbersome to manage; it doesn't exist at the individual level. Anything policy based, which is what you really need to make it scalable, isn't even a concept. Which is a problem! But it's hard to resolve at the individual level ... 4 comments
And there's historically a LOT of resistance in the fediverse to consent-based federation. @anildash talks about how consent's a key often-unstated value in the fediverse, and that's true, but in practice it's also very intermittent. And many (most?) high-profile fediverse "influencers" are in the camp that's actively hostile to consent. So incremental change is hard.  @jdp23 @anildash @polotek @tillshadeisgone I think (and we have already stated that in other conversations), that at least part of the resistance is the idea that small instance would suffer from consent-based federation. And I know that there are some ideas to overcome that, but it’s not an easy one to solve. |
Gregory's Server
Other fediverse microblogging platforms all have blockers to broader adoption -- functionality isn't fully there yet, horrible UI, not a lot of support from hosting companies, etc. And with most of them, support for controlling federation choices isn't much better. So things are trapped in this weird suboptimal state; and most microblogging resources go to Mastodon, so it's been hard to break out of the cycle.
@polotek @tillshadeisgone