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

And if you're interested in a hashtag, search for thathashtag at-symbol tags.pub in your Mastodon search UI and follow it there. It will boost all the content it finds with that tag to you.
@evan Oh nice! @janboehm has a yearly live-streamed event with his podcast @festundflauschig . They once used the comments of one post as the feedback channel as hashtags didn't work. Using this technique, they could make it work.
@evan would that be #quilting@tags.pub or [email protected]?

@inarticulatequilter @evan It's the latter. If you search for it via mastodon.art, you should find this profile:

https://tags.pub/profile/quilting

activitypub.bot

@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)
@evan @mayintoronto This description sounds like following a tags.pub via hashtag is even more limited as it only gets tags from people who’ve opted into tags.pub.
@Chigaze @mayintoronto Yes, it's still in its early stages, but the architecture is made so it can handle more and more content over time. The system is opt-in for individuals, but servers and whole platforms can opt in, also.
@mayintoronto
People on sites running other systems generally can't.
@evan
@evan @_followback @nokings why would you not just follow the hashtag?

@bipolaron

When you follow a hashtag locally on your server, it only filters content that arrived at your server due to following.

So, if someone on the Fediverse posts with a hashtag, and nobody on your server follows them, you won't see the post.

tags.pub is trying to improve that, and bring you *all* the content posted with that tag.

@evan Done; I didn't know about this, so thanks for that.

Reading the replies, it's surprising to me that people don't really understand how tags work here. I think maybe my world view is different because I'm on a single-user instance, so it's much more obvious to me that tags don't always have a lot of reach.

@sean @evan /me goes to convert my hashtag follows to tags instead.

#tagspub

@sean Thanks so much! I appreciate it.
@evan I am so confused. I click on that account and am met with a wall of buttons(?) that say Add. There is one that reads "Accept" but I haven't knowingly clicked anything. I don't see how to simply follow. And when I click on the follow account in certain iOS apps I get nothing at all. *shrug*
@rickscully OK. I'll change the instructions. Search for @_followback in your Mastodon server, then click the follow button there.

@evan I had questions. What is tags.pub? Why would I want it to boost my posts?

https://tags.pub explains most of it. Presumably someone has to pay for this. Is it just altruism?

tags.pub

@edwiebe So, do you still have questions after reading the home page?

It's a project of the Social Web Foundation. We're a non-profit with the goal of making the Fediverse easier to use. We think that if tagged content connects more Fediverse servers, it makes our conversations better and people's experience here richer.

Development and maintenance of tags.pub is sponsored by a grant from the Sovereign Tech Agency.

@evan Honestly, the past decade of social media and, well, everything, has made me very suspicious. The home page explains a lot but the link to the Foundation is very far down at the bottom of the page and without actually clicking it tells me nothing.
@edwiebe So, what you're looking for is more information about SWF, earlier in the page? I can do that. I added an issue here: https://github.com/social-web-foundation/tags.pub/issues/15
More information about SWF earlier in the tags.pub home page · Issue #15 · social-web-foundation/tags.pub

Suspicious user asked to know who's providing this service and why. Found the SWF link in the privacy section, but expected more information sooner.

GitHub
@evan Yes, it’s difficult for a naive mastodon user to understand this. At first it looked like the kind of scam one seems in the spam folder, SEO, buy likes, kind of stuff. I immediately wondered. I did notice your instance name and recognized it as a very unlikely source of spam. Most of the info on the about page is helpful but still I think doesn’t provide what naive users need to understand what this is about. Obviously, I hope, these are my opinions.
@evan @edwiebe I think it needs to explain how hashtags work in Mastodon and what this adds, because I don't think most people know that
Explain why this is needed · Issue #16 · social-web-foundation/tags.pub

Explain why this is different than following a hashtag in Mastodon.

GitHub

@evan @_followback

Hey Evan.

Done! I posted a photo after following, and used two hashtags. Less than a minute later, I got notifications that it had been boosted, once per hashtag. Each boost was from an account corresponding to one hashtag I'd used.

That seems like the expected behaviour, but I figured I'd let you know what it did in case something seems amiss.

Cheers!

@ihember thank you so much! I'm glad it worked.
@evan is it normal than even from a mastodon account there is no followback ?
@rmdes no, it should follow you back. This account?
@[email protected] I followed but didn't get an accept or follow back, so I think there's something up on my end! The relay follow also didn't work so I'll need to take a closer look this week 🙂
@julian OK. I use a separate key ID and actor ID for HTTP Signature, so that can throw off some implementations.
@julian I commented on the ticket! Looks like we can both make some changes to make this more robust. I'm going to push and test today.