Introducing tags.pub
Social Web Foundation
5
Posts
4
Posters
0
Views
-
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.
-
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.
@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...
-
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.
@evanprodromou When I click on the @_followback link in your blog entry I get a bunch of code.
-
@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...
-
@evanprodromou When I click on the @_followback link in your blog entry I get a bunch of code.
@nantel @evanprodromou Don't click on it. I haven't built the pages yet. Search for it in Mastodon. I'll fix the link.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@nantel @evanprodromou Don't click on it. I haven't built the pages yet. Search for it in Mastodon. I'll fix the link.
-
@blag Great!
-
@evanprodromou When I click on the @_followback link in your blog entry I get a bunch of code.
-
@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...
-
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) or https://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.
-
As part of my book “ActivityPub: Programming for the Social Web“, I created a coding example to show how to program for the ActivityPub API. ap is a command-line client, written in Python, for doing basic tasks with ActivityPub.
ap login yourname@yourserver.example
For example, you can log into a server using this command:Once you’re logged in, you can follow someone:
ap follow other@different.exampleOr, you could post some content:
ap create note --public "Hello, World"This isn’t enough to have a real social networking experience, but I think it’s pretty useful for testing an ActivityPub API server, or automating some repetitive tasks.
I should note quickly here that not all ActivityPub servers support the ActivityPub API. It’s an under-utilized part of the ActivityPub standard. In particular, Mastodon, Threads, Flipboard, and other services don’t support the API. There’s a pretty good list of servers and clients that do support the API in this Codeberg issue.
Suffice it to say, unless you’re actively working with one of those platforms, or you are writing your own, you’re not going to get much use out of ap. It will probably give you an error message like “No OAuth endpoints found” if it can’t use the service.
Refreshing the projectI’ve never packaged ap for distribution; it was always supposed to be example code. But given the recent interest in the ActivityPub API, including the work going on in the ActivityPub API task force, I decided to get it into shape for installation by developers working on other apps. My friend Matthias Pfefferle of Automattic asked me about it when we were at FOSDEM this year, and I was embarrassed to see how difficult it was for him to use.
So, I’ve made two big upgrades to the package. The first was actually making it a package, and distributing it! I upgraded the package management framework to uv, which seems like a good bet for now, and pushing the application to PyPI, the Python Package Index. It’s visible at https://pypi.org/project/activitypub-cli/ now. (Note: different package name from the command name! The PyPI “ap” package name was taken a while ago.)
You can now install the application in one shot with this command on a computer that has Python on it:
pipx install activitypub-cliYou can test that the application installed correctly in your path by running the version command:
ap versionThat should show the same version as is currently on the pypi.org page for the project.
The second change was implementing the current OAuth 2.0 profile best practices. I’ve upgraded the login flow so it tries a lot of different options for identifying itself to the server: CIMD, FEP d8c2, and Dynamic Client Registration. It tries to do them in preferential order; it uses permanent, global client identifiers before dynamic ones.
Help me testI’m especially interested in testing this command-line client against other servers. If you’re developing an ActivityPub API server, please install the ap command and try it out against your (development!) server. Report a bug if it doesn’t work well, or send me a DM at @evanprodromou if it works OK. Given time, I think ap can be a useful first smoke test for ActivityPub API implementations.
-
I’m going to be participating in the Growing the Open Social Web workshop at Fediforum on March 3, 2026. I’m excited to talk to other people who care about the Fediverse about ways to connect more people through ActivityPub.
Fediforum invited attendees to publish position papers before the workshop. SWF has a number of hypotheses about growth of the social web; I’ll try to summarise some of them here.
Growth can’t come at the expense of privacy. People currently on the Fediverse must have the tools they need to preserve their privacy as the network grows. This means privacy from other users, as well as privacy from new platform operators. Expanding the options for private interactions on the Fediverse, like end-to-end encrypted messages and private groups, is necessary for preserving privacy as the user base and platform list expands.Connecting platforms to the Fediverse is our most efficient way to grow. There are already billions of people on social platforms across the Internet. Getting these platforms to let users publish to the Fediverse, as well as having two-way interactions with remote users, lets people share in the benefits of the Fediverse with a platform and interface that they’re already used to. Even when brand new social platforms adopt ActivityPub, they bring their new features and users.Connecting communities helps us grow fast and stay cohesive. Bringing formal and informal communities onto the Fediverse is a great way to enable a lot of new users quickly. By formal communities, we mean organized groups like clubs, universities and schools, professional societies, enterprises, or local and regional governments. These groups can set up their own places on the Fediverse, like Mastodon servers, and provide user accounts for all their members. (One great way to connect formal communities is to Fediverse-enable the community platforms they already use.) These new Fediverse users have the kind of connections in place that retain active users, as well as the support they need to use the Fediverse. More informal communities, like people sharing the same profession, fans of a particular hobby, or users of a language or technology, can be great additions to the Fediverse, but these groups are less cohesive and less likely to bring their own infrastructure.People come to social networks for existing social ties. Bringing on new users one-by-one is the most difficult way to grow this network. The best way to engage new users on the network, and to keep them active and interested, is to make sure they can connect to people they already know and care about. That may be friends, family, colleagues and neighbours, or brands, creators, and publications they recognise. Our onboarding processes for Fediverse users need to encourage the social contacts so that people feel a reason to stick around for day 2, 7, and 30.We’re looking forward to engaging with the Fediforum community on these and other topics. We’ll see you on March 3!
-
@renata @evanprodromou @fabio I hope it is important!
