Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Introducing tags.pub

  • 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 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 to your bio. If you already have , 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 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 to your bio. If you already have , 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 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 to your bio. If you already have , 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

    So this isn't global tracking, but rather opt-in for a couple of servers and a dozen individual users?

  • @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.

  • 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 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 to your bio. If you already have , 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 @example It’s probably worth adding an explanation why tags.pub is necessary; aka: why Mastodon’s existing “follow hashtag” feature is inadequate.

  • 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 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 to your bio. If you already have , 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.

  • @the_moep 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.

  • @octothorpes 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.

    @com There’s a whole section on it in the video!

  • @evanprodromou

    So this isn't global tracking, but rather opt-in for a couple of servers and a dozen individual users?

    @johan We’d like to get it to global, but we’re doing it a step at a time.

  • @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.

  • 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 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 to your bio. If you already have , 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.

    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.


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    3 Posts
    22 Views
    @akareilly which makes me wonder: who didn't? Who was I too busy / distracted / unaware to not notice that the system was letting them down?
  • 0 Votes
    36 Posts
    79 Views
    Our initial clients will be built in JavaScript, so you’d need to enable JS on your browser to use it (for now)And, it will require special features on your server, so this won’t work on Mastodon (for now)Download the road, things will change. We’re defining a standard API that anyone can build in. So hopefully someone can built installable clients (iOS, Android, desktop) that work separate from your browser. @ddlyh @bonfire @swf @sovtechfund
  • 0 Votes
    1 Posts
    11 Views
    Does anyone else have this issue with their Ghost 6.9.0 blog? I can write posts, I can follow other people, but the explore tab is completely empty. No matter if I try to use "top" or any other topic. I always get a "404". ActivityPub initialization seems to be fine though.What am I missing? (yes, the domain name is redacted)#ghost #activitypub #blogging
  • 0 Votes
    1 Posts
    18 Views
    We were excited to see the recent release of Ghost 6 with ActivityPub features. The Ghost team have been an active participant in our Long-form Text project. John O’Nolan, founder and CEO of Ghost.org, was kind enough to answer our questions about the software and its community.SWF: For our readers who don’t know Ghost, how would you describe the platform?JO: Ghost is an independent publishing platform for people who take writing seriously. We’re open source, non-profit, and built to give creators complete ownership of their content and their audience. We’ve helped indie publishers generate over $100 million in revenue from sustainable modern media businesses like 404Media, Platformer and Tangle News.SWF: Tell us about your user community. Can you paint a picture of them with a broad brush? What kind of people choose Ghost?JO: Ghost attracts people who care about owning their home on the internet, rather than having another profile on a social media platform. Our publishers range from solo journalists and creators, to established news outlets and large businesses. They value independence, and they’re willing to do the work to maintain control of their brand, distribution, data, and relationship with readers.SWF: What is it like to be a Ghost user in 2025? What kind of problems are your users facing today?JO: The big challenge today is the same one that’s haunted independent publishers for two decades: discovery. You can own your platform and serve your audience beautifully, but if people can’t find you, none of it matters. Email newsletters have been a solid answer, but they’re still dependent on deliverability and inbox placement. Algorithms on social platforms actively suppress links now, so sharing your work there is like shouting into a hurricane.SWF: Tell us about your experience with ActivityPub. Why did you decide to add ActivityPub support to your software?JO: Ghost has had support for delivering content by email newsletters for a number of years, and email has remained an unassailable distribution platform for publishers because it’s an open protocol. No company controls your email list except you, so it’s one of the best investments you can make. ActivityPub is now doing the same thing for social technology. It allows publishers to own and control a distribution channel that allows their work to spread and be discovered by others. For the first time, you can publish independently and grow faster than ever before.SWF: What stack is Ghost built on? What development tools does your team use?JO: Ghost is all built in modern JavaScript; mainly Node and React. Our ActivityPub service is built on Fedify, and everything we build is released under an open source MIT license. Our development tools are constantly evolving, and now more quickly than ever before with the advent of AI tools, which seem to change on a near weekly basis.SWF: What was the development process like?JO: Challenging, honestly. ActivityPub is beautifully designed but the spec leaves room for interpretation, and when you’re building something new, there’s no roadmap. Building interoperability between other platforms, who’ve all interpreted the spec in their own unique ways, has been a real challenge. The approach we took was to ship early versions as quickly as possible to beta testers so we could learn as we go, using real-world data and issues to guide our process. We’re in a good spot, now, but there’s still a lot to do!SWF: Ghost produces long-form blog posts, articles and newsletters. How was the experience adapting Ghost articles to the microblogging interfaces of Mastodon and Threads?JO: In some ways really easy, and in other ways quite tricky. We’re at a pretty early stage for long-form content on ActivityPub, and the majority of other products out there don’t necessarily have interfaces for supporting it yet. The easy part is that we can provide fallbacks, so if you’re scrolling on Mastodon you might see an article title and excerpt, with a link to read the full post – and that works pretty well! The dream, though, is to make it so you can just consume the full article within whatever app you happen to be using, and doing that requires more collaboration between different platforms to agree on how to make that possible.SWF: You’ve been an active participant in the ActivityPub community since you decided to implement the standard. Why?JO: ActivityPub is a movement as much as a technology protocol, and behind it is a group of people who all believe in making the web a weird, wonderful open place for collaboration. Getting to know those humans and being a part of that movement has been every bit as important to the success of our work as writing the code that powers our software. We’ve received incredible support from the Mastodon team, AP spec authors, and other platforms who are building ActivityPub support. Without actively participating in the community, I don’t know if we would’ve gotten as far as we have already. SWF: Ghost has implemented not only a publishing interface, but also a reading experience. Why?JO: The big difference between ActivityPub and email is that it’s a 2-way protocol. When you send an email newsletter, that’s it. You’re done. But with ActivityPub, it’s possible to achieve what – in the olden days – we fondly referred to as ‘the blogosphere’. People all over the world writing and reading each other’s work. If an email newsletter is like standing on a stage giving a keynote to an audience, participating in a network is more like mingling at the afterparty. You can’t just talk the whole time, you have to listen, too. Being successful within the context of a network has always involved following and engaging with others, as peers, so it felt really important to make sure that we brought that aspect into the product.SWF: Your reader is, frankly, one of the most interesting UIs for ActivityPub we’ve seen. Tell us about why you put the time and effort into making a beautiful reading experience for Ghost.JO: We didn’t want to just tick the “ActivityPub support” checkbox – we wanted to create something that actually feels great to use every day. The idea was to bring some of the product ideas over from RSS readers and kindles, where people currently consume long-form content, and use them as the basis for an ActivityPub-native reading experience. We experimented with multiple different approaches to try and create an experience with a mix of familiarity and novelty. People intuitively understand a list of articles and a view for opening and reading them, but then when you start to see inline replies and live notifications happening around those stories – suddenly it feels like something new and different. SWF: If people want to get a taste of the kind of content Ghost publishers produce, what are some good examples to follow?JO: Tough question! There are so many out there, and it really depends on what you’re into. The best place to start would be on ghost.org/explore – when you can browse through all sorts of different categories of creators and content, and explore the things that interest you the most. SWF: If I’m a Fediverse enthusiast, what can I do to help make Ghost 6 a success?JO: Follow Ghost publishers and engage with their content – likes, replies, reposts all help! Most importantly, help us spread the word about what’s possible when platforms collaborate rather than compete. And if you’re technical, our ActivityPub implementation is entirely open source on GitHub – contributions, bug reports, and feedback make the whole ecosystem stronger.