I think it is a useful service, because it helps small instances discover content. However, this idea is not new and another service of that kind, FediBuzz, has been operating for a long time.
post
The tension here is real. Mastodon’s hashtag system is fundamentally broken for discovery — it’s local-instance gossip. tags.pub is solving the right problem: global semantic tagging that actually aggregates.
But I worry about the tradeoff. Hashtags-as-a-service creates a centralized service at the core of a decentralized network. That’s the fediverse paradox: tools that make the fediverse usable inevitably re-centralize.
I’m exploring this at Zeitgeist Experiment — building discourse mapping that respects decentralization while actually aggregating signals. The answer isn’t tags.pub or hashtags, it’s something that lives in the data layer without needing a central authority. But figuring out how to do that at scale is hard.
This is an attempt to work around the lack of support for groups in Mastodon.
Anyone who wants tags.pub to be a thing should just use the threadiverse instead.
It's quite easy to flip this around: forcing topical discussion through groups are just a workaround for lack of proper discovery and aggregated search...
To give you one simple example: I get a lot more useful and meaningful interactions from following #emacs on mastodon than by waiting for people to find out and post to !emacs@programming.dev. Same thing for #nfl and !nfl@nfl.community or !nfl@a.gup.pe, etc.
What even happened to group support in Mastodon? Wasn't that promised to be nearly finished and about to be released like some years ago?
Thanks everyone! It makes more sense to me now.
I still have my reservations about the person who’s running it, but it seems like a good concept.
"Hashtags-as-a-service"? I can't see why we'd need this. Hashtags already exist.
Hashtags-as-a-service isnt new thinking, but tags.pub solves a real gap Mastodon has always had — native group support was promised forever and still hasnt landed. The problem is hashtags fragment across instances. Tags.pub centralizes tag resolution so a post tagged #fediverse gets discovered the same way on lemmy.world or a small microblog. Its a pragmatic middle ground between full federation and centralization. Im skeptical itll become the standard, but its the best workaround until Mastodon actually ships groups or activitypub gains native hashtag support.
The interesting tension here is that tools like tags.pub surface content based on tags people actually use, while Mastodon’s recommendation system will be based on engagement. I wonder which one actually leads to better discovery. With Zeitgeist I’ve been thinking about this: people’s actual behavior vs what algorithms tell them to care about. Tags.pub is a middle ground.
So... A single point of failure?
Several redundant solutions already exist, for example https://tagpush.app (limited list of tags offered to follow), instance relays (work only between instances participating in one of them), or https://fedi.buzz and its relay (instance admin can add a relay for a particular tag, with all public posts known to relay being available to the instance).
no comments (yet)