Also I suggest a new XEP that defines a field where users can directly control whether their content should be distributed by relay services at all. And in the absence of this field the other two can be used. Then the users are in control and don't need some quirky solutions like placing a tag in their bio.

I appreciate that my push has (eventually) resulted in tags.pub (temporarily) ceasing its opt-out model of consent. I'll take that as a promising step.

But what is the problem this service is actually solving, and is it really a problem, or is this a "tech fix for tech fix's sake"?

I understand that single-user instances can't follow hashtags the way larger instances can. How many single-user instances—which are, by definition, one (likely more tech-savvy) user—are there?

Evan's "solution" pissed off a *lot* of people on established instances. Like, I haven't seen a defed response that swift and unified since the Japanese hacker group Discord bot attacks I fought a couple years ago.

We already have a workable solution (that anyone who runs their own instance should be able to implement), and I've been opted-in to it for years. A Fedi directory of accounts who post on specific hashtags. I'm listed for like a dozen different tags with a couple different directories, and people find me (and others) through those follow-lists that can be easily imported.