tags.pub is a new service under development by the Social Web Foundation. It is a global hashtag server — it lets you follow a hashtag across the Fediverse. There’s lots of information on the tags.pub home page, and I (Evan) did a talk about tags.pub at FOSDEM 2026. This blog post answers some basics about tags.pub.
- To follow a hashtag globally, search for a user with that name at tags.pub, like @example for the #example hashtag. Follow that account, and it will share all the content it sees with that hashtag to you. If you unfollow the account, it should stop sharing to you. The usernames only have letters and numbers in them, and they only go up to 64 characters.
- To share your content with tags.pub, search for and follow the @_followback account. It will follow you back (thus the name) and your public posts will be shared by the hashtag accounts on tags.pub. If you unfollow the follow back account, it will unfollow you back, and your content will no longer be shared.
- You can connect a whole server to tags.pub by using the relay interface. Add
https://tags.pub/user/_____relay_____/inbox(Mastodon) orhttps://tags.pub/user/_____relay_____(Pleroma) to your server relays. This is a one-way pipe — your server will send public posts to tags.pub, but tags.pub won’t send all its public data back to you. Instead, your users should follow hashtag accounts to get specific feeds. - We respect your agency. If your server is connected to tags.pub and you don’t want it to boost your content, add #NoTagsPub to your bio. If you already have #NoBots, that should be plenty. You’ll still be able to follow tags.pub hashtag accounts. If you don’t want to see or be seen by tags.pub at all, you can block the domain ‘tags.pub’ entirely.
- Becoming the ‘global’ hashtag server is a goal. We are still ramping up, and there are a lot of people and servers that are not yet connected.
- tags.pub will not share your content with accounts or servers that you have blocked. It only shares the link to your content, so your block will be respected.
- tags.pub is developed and operated by Social Web Foundation. We are a US non-profit. The servers are located in Beauharnois, Quebec, Canada in a data centre run by OVHCloud, a French corporation. We try to keep the data storage to the absolute minimum necessary to provide the hashtag sharing service. There is no search index, and we don’t archive your content. The code is Free and Open Source software under the AGPL-v3.
- If you have a feature request, or a bug report, please add a GitHub issue. If you have a private comment or question, please use our contact form.
25 responses to “Introducing tags.pub”
@evanprodromou Very cool, thanks. Giving it a tryβ¦
@evanprodromou @example ooooh. I like the sound of this.
@evanprodromou Looks like I'm the first to follow @signpainting and @signwriting, among a few others to get the ball rolling.
I'm intrigued to see how this works and what lands in my feed as a result…
@blag Great!
@evanprodromou
@evan Quick follow-up: is there any way to *not* have the boosts by these bots appear in notifications? I don't get a lot of boosts, so now they're getting in the way of 'genuine' human boosters…
@blag sure; put hashtag NoTagsPub in your bio. Or, block tags.pub domain.
@evan@cosocial.ca I’m assuming @blag@typo.social still wants the boost but not to be notified about it?
It can be done if the
recipientboostee isn’t explicitly addressed, I think.@julian it might be possible but it prevents the server from tracking shares. I'm not going to implement that.
@julian "I don't want notifications from particular users/domains/whatever" is a client issue.
@julian @blag another option is muting the hashtag users. That should prevent notifications by those users. Unfortunately, you have to do it for each user, but if you use the same hashtag a lot, it should help.
@evan @julian Yes, none are ideal solutions as I want to actively follow the hashtags, especially the ones I regularly use.
A possibly unintended consequence of this is that posts that use hashtags are now going to appear more popular due to this automated boosting. (At least for people like me that usually have single-figure numbers of boosts on their posts.)
No sweat, I'll accept my new-found popularity with the robots and continue to follow the tags accounts that relate to my interests.
@blag @julian ππΌ
@evanprodromou How is this different from https://relay.fedi.buzz ?
Fedibuzz is great! It normally works as a relay, though. So, you have to be an admin to set it up. But I’ve recently found out you can also follow the accounts, like with tags.pub. So it’s similar in that way. I think it’s a big Fediverse and it’s good to have different services.
@evanprodromou
So this isn’t global tracking, but rather opt-in for a couple of servers and a dozen individual users?
@johan @evanprodromou
Re: https://mastodon.social/@rusty__shackleford/116188992459133547
When you are on the fedi, your messages are broadcast. ***Anyone*** can see them. That's why I can see your posts, mastodon.social saved your post, and served it to me, and vice versa, that's why you see this text.
If you don't want the possibility of 'tracking', we may not have been able to have this conversation but you could join a private server, or be more safe about your personal identity, or get offline.
@rusty__shackleford @evanprodromou
Exactly. For example, in the Cyrillic segment thereβs a bot that reposts every message in Russian it can get access to. And it operates on an opt-out basis.
Here, however, as I understand it from the description, either you yourself (for your own account) or the server admin (for the whole server) has to connect the bot manually. And posts from those who donβt do that simply wonβt be seen by the bot.
We’d like to get it to global, but we’re doing it a step at a time.
@evanprodromou @example @_followback hi! we are very interested in talking to you about this
Great!
@evanprodromou @example Itβs probably worth adding an explanation why tags.pub is necessary; aka: why Mastodonβs existing βfollow hashtagβ feature is inadequate.
There’s a whole section on it in the video!
I think there’s an issue with the follows, at least with NodeBB. Followback didn’t follow me back, and the relay won’t establish π
It’s probably just NodeBB being overly strict.
@julian @swf I had a follow bug; try unfollowing and refollowing and see if that fixes it.
@evanprodromou@socialwebfoundation.org looks like i can’t follow from Sharkey. There seems to be a open issue about it https://github.com/social-web-foundation/tags.pub/issues/9