@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.
2. The server admin opts in by configuring the server relay interface.
You can argue that a server admin shouldn't configure relays for their users. That's not the state of Fediverse software today, though. Server admins make a lot of decisions for their users, and configuring relays is one of them.
It's probably a good argument to bring up with the Mastodon devs and your server admins.
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.
@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 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?
@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.
@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@cosocial.ca Hi, thanks for asking! This made me think of what info we could utilize to offer a better user experience.
I maintain Catodon, a Misskey fork, and Iβd like to show tags.pub on our Explore page without storing lots of extra posts on our server.
What weβre missing, and I would like to add, is a way to discover tags (outside of what the server already knows). A small read-only feed would be enough, with no post content:
- Trending tags (the most important one for us), with a rough activity count and the address of each tagβs account. Our own Trending page only reflects posts that reach our server, so this would be a clearly labeled βFrom tags.pubβ section next to it.
- Co-occurring tags, for a βrelated tagsβ line on tag pages.
- A way to look up a tag, so a tag page can show something like β41 boosts this week Β· 27 followers on tags.pub.β
Global stats would be nice but are lower priority for us. An hourly snapshot is plenty fresh, and weβd cache it.
Whether you could offer this as a simple API, or through FASP as you suggested in the Mastodon specs repo (issue #60) is not an issue - a plain API is easy for us to build against today. Weβd happily move to FASP if it becomes a real standard. I am also interested in adding a way for followed hashtags on our platform to include results from tags.pub.
Just one thing that somewhat holds me back: The idea for our feature is that it would link out to tags.pub for hashtags discovered through it. Today, a tag presented on tags.pub isn't great to look at for regular users: It can contain a lot of "HTTP 401", "Add", "Undo". It would be nice to provide a more presentable public feed, with just posts. Language filtering would be superb, but maybe I'm asking too much π
Happy to hear your thoughts, and to build our side and test in case you decide to provide a way to access this info.
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.
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