Friends, if you haven't already, it would be a big favour to me if you could enable tags.pub to boost your public tagged posts.

Just search for @_followback in your Mastodon UI. Click the follow button there. (Don't try to follow from the profile page; it doesn't work yet.)

It will follow you back, and when you make a post with a hashtag in it, the server will boost your post from the appropriate hashtag.

#tagspub #hashtags #activitypub

@evan Is there a reason to do this when we can already follow hashtags?

@mayintoronto one reason is because your friend Evan asked you to do it as a favour.

Another reason is that when you "follow" a hashtag in Mastodon, it only filters the content that got to your server for other reasons.

There are three ways that content arrived: either you follow the author, someone else on your server follows the author, or your server is subscribed to a relay.

tags.pub lets you follow a hashtag globally, not just filter what got to your server.

@evan ah, so this would help a lot with say, @introduction for unfederated single user servers.

@evan @mayintoronto

This gives me the heebie-jeebies. "Global" makes me uncomfortable. Automatic boosting makes me uncomfortable. Both are not particularly Fediverse-type concepts.

Here's the intro page on this (note that Social Web Foundation lists Meta and Auttomatic as partners):

https://socialwebfoundation.org/2026/03/17/introducing-tags-pub/

Sorry, Evan, but no thank you.

@jakebrake I was a tad worried about that, but I'm on a server that has threads blocked. If it's just a boost, I'm willing to try it out.

Mostly want to see if I find an uptick in harassment.

@evan

@jakebrake @evan The thing I like about this specifically is that it's an opt-in global booster. So many bots currently boost without our consent.

@mayintoronto @evan

I'm wondering about down the line.

To really work, this system needs to connect to basically every Fedi server, or at least all the big ones, right? Which sounds very centralized to me. And, if it does become a popular thing, gives SWF leverage over the Fediverse: Want your posts "fully" boosted, you need to talk to SWF.

Maybe I'm missing something?

@jakebrake @mayintoronto I totally get the concern about centralisation. I think there are two mitigations for that issue.

The first is that there are two other services that do something similar already: https://relay.fedi.buzz/ and tagpush.

The other is that the tags.pub software is Free and Open Source software; anyone can set up their own server using the software. If you decide to do that (I hope you do!), please let me know, and we can figure out how to share public data.

#FediBuzz Relay

The buzzing ActivityPub relay service

@evan @mayintoronto

Thanks Evan for listening to my concerns and for your thoughtful replies!

One of the really neat things about the Fediverse is that us in the peanut gallery can reach out to folks like you who are building and improving the "plumbing" of the place, and vote with our posts. It is a special thing, and I try not to squander it by overuse or by being snarky or rude, mostly.

TBH, I do like Fedi how it is, semi-useful search and not-quite-boosts and all. So, yeah. 🤷

@mayintoronto The way tags.pub does boosts, we don't share any of your content with servers that you have blocked. So, hopefully, you shouldn't see an uptick in harassment.
@evan @mayintoronto how do you know which servers I've blocked personally? You cannot.

@AzureKingfisher @mayintoronto we can't and we don't want to.

tags.pub does not share the full content of your post; just a link. When a subscriber to a tags.pub account receives the boost, it has to go fetch the content from your server.

When it asks for the content from your server, your server checks against your blocklist. If the subscriber is blocked, your server won't return the post.

I hope that explains it!

@evan @mayintoronto I didn't mean server side blocks but user side blocks. I have blocked domains that mastodon.art has not. The boost cannot be checked against that.

@AzureKingfisher @mayintoronto When you block a domain, that information is stored in your server. Your server prevents requests by that domain for your content.

tags.pub doesn't check your blocks information; it just shares very minimal info to subscribers, and they can't get the full information if they are blocked.

If you'd like a demo, I can record a screencast for you, or you can test it yourself.

@jakebrake @mayintoronto No problem! Nobody is obligated to use it. It's there to serve a purpose for people who want that feature.

@evan
But Evan, don't you see? If *someone* on the Fediverse doesn't like it, it shouldn't exist!

That's why Mastodon was wiped out years ago by Diaspora users.
@jakebrake @mayintoronto

@jakebrake @mayintoronto Hey, Jake. Your concerns are justified! It's never a bad idea to look at projects carefully.

tags.pub is one of the oldest projects on the ActivityPub network. It was one of the test implementations of ActivityPub. It's been dormant for years; we've been lucky enough to get to implement this with funding from the Sovereign Tech Agency.

The service is opt-in, either by user or by server (and users can opt out if their server opted in). Nobody has to use it.

@jakebrake @evan @mayintoronto I'm with you. No thank you. People can follow hashtags. Nobody is following the accounts that are set up to echo hashtags. It's a waste of bandwidth.

@mlanger @jakebrake @mayintoronto

You can definitely opt out of tags.pub! Nobody has to use it if they don't want to.

You can follow hashtags in Mastodon; many other servers on the Fediverse don't have that feature.

When you follow a hashtag in Mastodon, it only shows you content from people you follow, or from people who others on your instance follow. If someone posts on the Fediverse using a hashtag and nobody on your instance follows them, you won't see it.

@mlanger @jakebrake @mayintoronto you're right that there are very few followers for the hashtag accounts on tags.pub. We are just getting this service started.

We're actually pretty careful with bandwidth.
I am one of the authors of ActivityPub, and I wrote a programmer's guide for O'Reilly Media about the protocol. I try to use it as carefully as I can.

If nobody's following a hashtag account, no data gets delivered.

@evan @jakebrake @mayintoronto Yet every single time I use a hashtag I get a notification for each hashtag. Your system is obviously creating accounts for each hashtag.

I honestly don't understand why you think this is necessary when one of the benefits of mastodon over other systems is that you can easily follow hashtags. You are attempting to solve a problem that does not exist. (1/2)

Personally, I'd like to see you folks deal with hashtag abuse, when people use 10 or more hashtags in a post to spam as many people as possible. I cannot count the number of times I've seen posts totally unrelated to one of the hashtags I follow. That's a problem. How about solving that? (2/2)
@evan @jakebrake @mayintoronto
@mlanger @jakebrake @mayintoronto thanks, I'll add that to our list of things to work on!

@mlanger @jakebrake @mayintoronto

> You can follow hashtags in Mastodon; many other servers on the Fediverse don't have that feature.

> When you follow a hashtag in Mastodon, it only shows you content from people you follow, or from people who others on your instance follow. If someone posts on the Fediverse using a hashtag and nobody on your instance follows them, you won't see it.

@evan @jakebrake @mayintoronto Maybe this needs to be fixed? Find some sort of way to "call" hashtags without actually boosting them? Creating accounts. Because #NotEveryoneUsesHashtagsTheSameWay
@evan @jakebrake @mayintoronto Also, what you say is true, following hashtags does not do what everyone says it does. I was led to believe that following a hashtag would show all of the posts containing that hashtag, regardless of whether other people on my instance followed the account posting it. It seems to me that the current set up puts small instances at a disadvantage.
@evan @jakebrake @mayintoronto Perhaps the real solution to the hashtag problem — because yes, now I can see an actual problem that needs to be solved — is to automatically put all tagged posts on a central server for a day or two and then have all mastodon instances call that server once a day or more for hashtags that its users are following.

@mlanger @jakebrake @mayintoronto I agree about the notifications. Right now, you either have to block the tags.pub server or turn off all boost notifications. I think we'll need to get a change made to Mastodon to let you hide boost notifications from a single server.

We do have one hashtag actor per hashtag, which lets people follow a specific hashtag. It's very lightweight, though.

@mayintoronto @evan @introduction and this could give me access to more people in my profession (I find few, right now, using the hashtag #lifecoach)