3 Boosts
0 Likes
@evan I'd love to see hashtags treated as sets and support for set operations. See here: https://github.com/thi-ng/blog/blob/main/2025/20251107-tags-are-sets.md
@toxi how interesting! We have a task force on aggregation and remixing that covers some of these topics. I think that work is a level up from tags.pub, though -- I think it might be another service that uses tags.pub as a source.
@evan recognition of the fact that even with the same name, tags are still differentiated by their host.
Encouraging the wider fediverse to treat them as such.
@mariusor that's an interesting idea that is not reflected in any other ActivityPub software. Maybe yours?
@toddsundsted initially it can only be through some color disambiguation. This version can be modified locally, this other one can't... or something like that.
The fact that a tag can be an object, also means it can have recipients, so when the users of your software add a tag to their communication, you can add said recipients to the outgoing list.
I don't know all the cool things that can be done with it, but I be there's a couple.
@evan no, not really.
I'm just annoyed that the fediverse is treating any object as belonging to a global namespace when that's simply not true.
What I do do is to give tags an actual HTML representation, where there's details and what not. (See something like https://releases.bruta.link/tags/New )
And I plan to use them this way in the different instances of the brutalinks link aggregator. On it local tags can be used to differentiate between actor roles on each instance: moderators as an example.
@mariusor it feels like a stretch to say that hashtag linux on social.tchncs.de is entirely different from hashtag linux on mstdn.ca. I think that different communities use the same hashtag differently, but I don't think those communities break down cleanly on server lines.
@evan related tag groups: aka #fediverse and #fediversum together as one concept.
@liaizon I think that's a really good feature, but it might be too high-level. I'd like to have a server that lets you aggregate search terms, individual accounts, and hashtags, but tags.pub might be one-feed-per-tag.
@evan Consent from users
@evan I’m not getting into discussion with on this since I’ve seen you prove multiple times that you don’t understand opt-in. It’s opt-out for tags.pub. That’s not the same.
@prutser I'll be clear on how data gets into tags.pub.
1. User opts in directly. The user follows @_followback , and their public tagged posts are boosted. If they unfollow or block, their posts are no longer shared.
Should it work with Pixelfed too?
It says "follow requested". My server is on 0.15.2, so the newest Pixelfed version.
At the moment there is no possibility to add a relay, https://github.com/pixelfed/pixelfed/issues/4472 was closed by @shlee - not sure if it's still planned or not. I'm also not sure, if I would add tag.push for all #PUNKdotPHOTOS users or not.
What I would love to see, @evan, that I can subscribe my posts just to specific tag.push bots.
E.g. I would love that only my posts with #foo are reposted by #foo@tag.push but not the #dontrepostthisone.
Can you point me to the github issues and I will add a feature request...
Thx
Some definitions:
- Trending tags: tags which have increased in frequency the most lately
- Co-occurring tags: tags that appear together in posts most often, like EvanPoll and poll
- Global stats: total subscribers, total publishers, total number of posts shared, total number of unique tags by day/week/month/year/whatever
- Tag of the day: an interesting curated tag, with a description
Thanks everyone for the responses and ideas! I'm going to put these into the issue tracker for #tagspub, and I'll work on bringing them out.