But what this means is that when we create tools to facilitate "better blocklist sharing" we need to acknowledge how that effort takes away from other potential solutions in this space.

Like as it is currently written, I'm pretty sure that the #FSEP proposal will not be mergeable into the #mastodon code base—they will balk at the increased centralization.

But there are a thousand small features could help, or could provide more value from the blocklists themselves, or lowering the costs.

5/

Basically: the more effort we put into tooling that _solves the wrong problem_ it takes away from our ability to contribute to tooling that is as likely (or more so) to move the needle, or that will make it more worthwhile to solve that original problem.

I'm just not convinced that adding additional features on top of instance-instance blocks helps here unless there is a dedicated focus on later steps and more robust tooling, which we seem to get distracted from while arguing blocklists.

6/

n.b. that when I say it's "solving the wrong problem" this isn't a dis on the people working in this space because I _do_ think there are interesting problems there that will eventually help…

It's just that, at least _in my view_, they aren't the problems that will make the fediverse as a whole safer. They may disagree and that's also fine, and I could very well be wrong, it just influences what we both choose to work on in this space, and who and how we recruit to various efforts.

7/7

@hrefna
I think tools that boost what we WANT in our feed are going to be more powerful than tools that remove what we DON'T want. So being able to easily share and import hashtag lists and follow lists would be very useful and have longer term value.