I am OVER THE MOON excited to see that #Mastodon now has a filtering option for notifications from bots. It's working spotlessly from a build of Mastodon 4.6 from today. This means that people using servers with #tagspub as a relay can opt out of getting boost notifications from tagbots but still keep sharing their content and still keep getting boost notifications from people. Thanks šŸ™šŸ¼ to the @Mastodon team for including this feature; it goes a long way to making tags.pub work for everyone.
One thing that's worth noting is that boost notifications aren't put into filtered notifications by Mastodon -- only replies and quotes. So, setting the Bots notifications option to Filter is equivalent to Ignore for boosts -- they just disappear. Bot replies will be filtered, though.
This option landed in main sometime today, so it's not in the`edge` Docker container or in the 4.6 beta release yet.
@evan
I’ve seen it come up here and there: what is tagspub?
@fname it's a global hashtag server. If someone posts with a tag like #kamloops the account @kamloops will boost that post. So following that account will give you more tagged content from across the network. See https://tags.pub/ for more info about how and why it works.
tags.pub

@evan
Hmm. Interesting…

@evan
I’ve added the relay and followed the @kamloops account.

Let’s see what happens…

@evan
Now that I’m using it, I can definitely see the issue with notifications. Did you say that that notifications from bots will be suppressed/disableable in 4.6?
@fname yes. A quick workaround is to disable notifications from people who don't follow you.
@evan
To clarify: what is the advantage to using #TagsPub beyond just regular hashtags? Does it overcome a limitation with the standard federation model?

@fname https://tags.pub/#why tells you the why.

First, not every platform lets you follow a hashtag.

Second, following a hashtag in Mastodon doesn't get you all content with that hashtag across the Fediverse. It just filters content that is arriving at your server for other reasons: someone on your server follows the author, or you have a relay, or boosts or replies.

Different servers see very different hashtag feeds. Very small servers <1000 people see very sparse feeds.

tags.pub

@fname tags.pub is there to make it easy to follow tags. We've got about 5600 servers connected. Some of the top 20 sites, which have 66% of accounts. After 4.6 is released, I will start asking more of those top 20 sites to connect.
@evan
Cool. So far on my 2-person instance I haven’t noticed a big difference in hashtagged content volume since connecting the relay. Where would the content appear? In the ā€˜federated’ timeline?
@fname did you follow hashtags you're interested in?
@evan
I do yes. However you just reminded me that I have to re-setup a bunch of my hasthtags since moving instances. Apparently 4.6 also solves this problem! šŸ˜€