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
    1 Posts
    12 Views
    Is there a place in the #Fediverse where groups can meet? 🤔#random question
  • 0 Votes
    2 Posts
    17 Views
    Second floor!! You can't miss our thick Plushtodon in our table. #FOSDEM #FOSDEM26
  • 0 Votes
    1 Posts
    12 Views
    The big feature in release v3.2.2 of Ktistec is pinned posts with support for the Mastodon Featured Posts collection. Federation works both ways—pin a post on Ktistec and it will show up as a pinned post on Mastodon and vice versa. When you refresh an actor profile, Ktistec also fetches and updates the actor's pinned posts. This is another small step in the direction of supporting all features that Mastodon-compatible client applications expect to access via the API. It's also useful in its own right. The other major feature, which I posted a short video demonstrating here, is X-Ray Mode. X-Ray Mode is a developer and power-user tool for inspecting ActivityPub JSON-LD representations of actors, objects, and other content. Pressing Ctrl+Shift+X on any page displays the data behind the page—like an x-ray. You can:Cached Version: View the local JSON-LD representation stored in the Ktistec databaseRemote Version: Fetch and view the original JSON-LD representation from the source serverNavigation: Click on any ActivityPub IRI to navigate to that objectHistory: Use Alt+Left and Alt+Right to navigate through your viewing historyThis feature is useful for debugging federation issues, understanding ActivityPub structures, and verifying how content is stored and represented.Here's the full changelog for the release:AddedSupport for pinned posts and the Mastodon "featured posts" collection.X-Ray Mode for viewing and navigating JSON-LD resource (actor, object, etc.) representations.Back links on thread pages for easier navigation. (fixes #1)License page for LibreJS compliance. (fixes #127)Highlighting of recently fetched hashtagged posts.ChangedImproved presentation of audio and video media.Refactored theming/styling implementation.The next release will focus on smaller features and bug fixes.Enjoy!#ktistec #crystallang #activitypub #fediverse
  • 0 Votes
    1 Posts
    9 Views
    Website LeagueAn island network using Fediverse technologies in allowlist-only mode.#SocialNetwork #SocialNetworking #Fediverse #ActivityPub