#tagspub

Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸 @evan@cosocial.ca · Jun 30, 2026

I made some changes to #tagspub over the last couple of days. It's now using the #IFTAS DNI and AUD domain blocking lists, both for sending and receiving data. It will not let actors on those domains subscribe to tags, send activities, or read any data from the site. I've tried to harden the service to blocked domains as best as I could, which might have been too tight -- let me know if you have problems receiving data from the service.

0

1

2

0

Mina @mina@berlin.social · Jun 28, 2026

I wonder why everyone seems to hate the tags.pub bot so much. I mean: Until now, there was no way no get a notification if somebody posts something with a hashtag you're subscribed to. This is a great feature, especially for hashtags with a low number of occurrences, greatly enhancing the value of the Fediverse for information purposes. Just asking. #TagsPub

3

1

3

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Replying to @OliviaVespera@spacey.space

I think one way it could work is through opt-in chains. Secondary relay(SR) identifies as relay and makes request to primary relay(PR) to relay PR's content. PR asks source instance (SI) for permission. SI either grants permission or not. If granted, PR grants permission to SR. SR relays SI content via PR. #Tagspub #relays #R2R #Fediverse #OptIn

1

0

1

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Replying to @OliviaVespera@spacey.space

This can also be placed inside a closed registration-esque structure where only secondary relays which the primary relay has registered with can make the request to relay PR's content. thereby reducing the number of requests to an SI to only SRs that are trusted by the PR. But perhaps opt-in needs to be propagated further to individual user accounts. #Tagspub #relays #R2R #Fediverse #OptIn

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Boosted by

Furbland's Very Value = 71 Account™ @GroupNebula563@mastodon.social

Replying to @OliviaVespera@spacey.space

The other alternative is to delegate opt-in responsibilities to the primary relay. Source Instances could set an option that says, you don't have to ask me for permission, I will leave it to you to decide whom to share my content with. Reducing the number of requests to users. Or Source Instances could set a flag in the primary relay that says do not relay to secondary relays. (and don't ask me for permission because I won't ever grant it) #Tagspub #relays #R2R #Fediverse #OptIn

0

1

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

tags.pub has unsubscribed from all open relays. Evan recognises there's a mismatch of expectations on what Relay 2 relay, R2R connections should be like. It should not have taken as long as it did but it's done. However this is ultimately a stop gap and not a full solution. What was asked for was an opt-in solution because there is value in having relays of relays. So on the tags.pub issue, how should R2R relays gain consent?🧵 #TagsPub #Relays #Fediverse #OptIn

1

0

3

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Boosted by

Furbland's Very Value = 71 Account™ @GroupNebula563@mastodon.social

Replying to @OliviaVespera@spacey.space

So how should Opt-in work with R2R? Should it be that the source instance must explicitly register or give permission to the secondary relay? Should it be the job of the primary relay to explicitly register with the secondary relay? Should it be the job of the secondary relay to explicitly flag itself as a relay to the primary relay and send a relay request message to the primary relay? How should the primary relay handle that permission? #Tagspub #relays #R2R #Fediverse #OptIn

0

1

0

🌈 Barbapulpe 😇 ᴹᵃˢᵗᵒᵈᵒⁿ @barbapulpe@gayfr.social · Jun 28, 2026

Replying to @evanprodromou@socialwebfoundation.org

@evanprodromou I have been one of the "victims" of the spammy, non-consented boosts from the tags.pub server. It has invaded my server with boosts impacting all my users, with no consent from anyone and no prior information. I am doubtful about the nature of the scraping, reputedly based on open-registration relays. Because I am not subscribed to any open-registration relay, only two relays which are not open, and to which tags.pub is not listed as participating. So, how this software is scraping my servers is probably done in another way. Due to unconsented and uninformed apparent mass-scraping by bots, I have defederated all my Fediverse servers from tags.pub #tagspub

0

ana «model a7m2»

🎶 @ana@starlite.rodeo · Jun 28, 2026

Replying to @ana@starlite.rodeo

i block the "trending" bots on sight, and if there's a whole server full of bots boosting posts i'll defederate from it. they have no right to insert themselves into my social fabric #tagsPub

134

2

21

0

Chłop Marcin

@chlopmarcin@101010.pl · Jun 28, 2026

Replying to @chlopmarcin@101010.pl

O, chyba właśnie zmienili sposób łaczenia się z serwerami relay: https://socialwebfoundation.org/2026/06/28/unsubscribing-tags-pub-from-open-registration-relays/ #TagsPub

Quoting

Evan Prodromou @evanprodromou@socialwebfoundation.org

Today the W3C standards organization announced a new working group to advance the ActivityPub and Activity Streams standards. The Social Web Foundation, as a W3C member organization, will be participating in the group. The working group’s goal is to release a backwards-compatible iteration of each specification in Q3 of 2026.

Activity Streams was released in 2017, and ActivityPub was released in early 2018. Since that time, the experience of hundreds of implementers and millions of users has shown places that the specifications are confusing or unclear, or missing features. Some problems have been documented with errata, but others require more work. The Next Version tag in the ActivityPub GitHub issue repository gives some good examples of topics to be considered. The new Social Web Working Group will provide revisions of these documents to make them easier to use for implementers.

ActivityPub is an actively used protocol with millions of users and billions of notes, images, video and audio files published. Standards work on ActivityPub will necessarily be evolutionary, not revolutionary, and will incorporate backwards compatibility. Developers can confidently keep working on ActivityPub today without worrying about breaking changes in the future.

The Social Web Working Group will work closely with the Social Web Community Group, the organization that has been stewarding ActivityPub and its extensions since 2018. The Community Group will remain the focal point for innovative developments extending ActivityPub into different areas like geosocial applications or threaded forums, while the Working Group will concentrate on the core documents.

One Community Group document that will be moving into the Working Group is LOLA, the live data portability spec that originated in the CG’s Data Portability Task Force. LOLA lets users move from one ActivityPub server to another while retaining all their social connections, their content, and their reactions. It’s a great improvement for data portability on the social web.

The Social Web Working Group will consist of representatives of W3C member organizations and invited experts from the standards and development community. The group will be chaired by Darius Kazemi, longtime contributor to the ActivityPub developer community. Meetings and proceedings will be public, and developers can review the work happening in the ActivityPub GitHub repository.

Thanks to everyone who’s done the work getting this charter to completion; especially @dmitri@social.coop, the SocialCG chair who drove the charter editing and review process. Now, the work begins!

Open quoted post

0

1

0

Chłop Marcin

@chlopmarcin@101010.pl · Jun 28, 2026

Ciekawa rozmowa rozwinęła się wokół tags.pub w wątku pod adresem: https://lgbtqia.space/@alice/116824281370893420

Niektórzy ludzie są bardzo zdenerwowani, że serwis tags.pub opiera się na domyślanej zgodzie, czyli trzeba się wypisać (opt-out), żeby nie wchodzić w interakcje z tym botem.

Przeycztałem zasady tag.pub (https://tags.pub/) i widzę potrzebę zaistnienia takiego serwisu (bo jest to częściowe rozwiązywanie problemu rozczłonkowania Fediwersum - czyli w praktyce zwykłego użytkownika: mało widać, co się faktycznie dzieje na Fedi). Ale z drugiej strony jest to dość inwazyjny serwis. No i niektórzy chcą lub potrzebuję lub muszą być ukryci w swojej kryjówce i... mają do tego prawo (bez bycia zmuszanym do ręcznego wypisywania się z serwisu, do którego się przecież nie zapisywali).

Twórca kontrargumentuje tak:

if you are being boosted by tags.pub bots, there are one of three reasons:

you followed our follow-back bot. My guess is that you didn't do this.
your server operator added tags.pub as a relay.
your server operator added an open-registration relay.

Unlike other relay services, tags.pub notifies you that you are being boosted, and gives you the option to opt-out.

Czyli rozumiem, że np. moja instancja dlatego jest objęta działaniem tags.pub, bo nasz administrator (@xaphanpl@101010.pl) ustawił drugą lub trzecią opcję z powyższych trzech. Nie rozumiem do końca, jak to działa, ale wygląda na to, że trudno pogodzić masowe automatyczne boostowanie hasztagów i oczekiwanie użytkowników Fedi, że nie będą zalewani niechcianymi działaniami botów.

#Fediwersum #hasztag #hasztagi #TagsPub

0

1

0

C. @cazabon@mindly.social · Jun 28, 2026

Replying to @riggs7sct@mastodon.scot

@riggs7sct@mastodon.scot This instance/service is violation enough to the point that I think that "the instance" deserves wide defederation, not just me putting a personal block on it. And fedizens should not have to take personal blocking action because some arsehole thinks "I'll create a billion bots to boost tags and people have to opt out of it to avoid me doing so for their content" is somehow good fediverse behaviour. #defederate #defederation #TagsPub

3

0

2

0

Princess Nettles Succubish @tiefling@bardicperspiration.club · Jun 28, 2026

"If u don't like me kicking u in the D whenever I see u then you can wear a T-shirt that says "I opt out" everywhere u go and I'll try to remember to honor it. #tagspub

0

GachaNoUta @anti42@sueden.social · Jun 28, 2026

Laut https://fedidb.com/servers ist #tagspub bereits die viertgrößte Instanz im #fediverse. Wie lange bis es die zweitgrößte ist nach Mastodon.social oder sogar Platz Eins? Mal abgesehen davon dass das ein Haufen Leute erstmal mit Benachrichtigungen abfuckt, sie rausfinden müssen was da passiert und wie man das abstellt, was bedeutet es für des fediverse, wenn es als Netzwerk mit hunderttausenden Bots wahrgenommen wird? Als Außenstehender versteht man das ja erst Recht nicht.

0

Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸 @evan@cosocial.ca · Jun 27, 2026

Replying to @alice@lgbtqia.space

@alice@lgbtqia.space there are a few ways to opt out. https://tags.pub/#optout The easiest is blocking the domain, either as a user or as a server. We use the NoBots/NoBot tag because it's already widely used to signal that you don't want bots to process your account. We added NoTagsPub if people didn't want to block other bots, just tags.pub. If you just don't want the notifications, but you still want your posts to be shared, you can use the new filter for bot notifications in Mastodon 4.6. #tagspub

1

2

3

0

Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸 @evan@cosocial.ca · Jun 27, 2026

Replying to @dansup@mastodon.social

@dansup@mastodon.social that'd be awesome. I think we'd be happy to share pairs data (which tags appear together most often) from #tagspub .

3

1

0

🌈 Barbapulpe 😇 ᴹᵃˢᵗᵒᵈᵒⁿ @barbapulpe@gayfr.social · Jun 27, 2026

Replying to @barbapulpe@gayfr.social

🇬🇧 TAGS.PUB Some of you may have noticed that a bot is reposting all your public posts using the account (hashtag)@tags.pub For now, I’ve decided not to block this server. It doesn’t pose a risk to personal data, since only public posts are reposted, and it doesn’t store the content (in this regard, it acts as a relay). It is operated by a nonprofit foundation, the Social Web Foundation, with servers hosted in Canada by OVH. What’s the point? The goal is to allow servers with limited federation to still track hashtags by following any account (hashtag)@tags.pub, thereby also increasing the overall visibility of public posts across the Fediverse. If this bothers you, you can block this feature yourself: simply open a bot's profile (click on a "boost" notification), click the three dots below the profile, and then select "Block tags.pub" at the very bottom of the context menu. Thank you in advance for your feedback. I may reconsider this decision and block the tags.pub server in the future. https://tags.pub/ #tagspub

0

1

0

1

🌈 Barbapulpe 😇 ᴹᵃˢᵗᵒᵈᵒⁿ @barbapulpe@gayfr.social · Jun 27, 2026

🇫🇷 TAGS.PUB Certains d'entre vous ont peut-être remarqué qu'un robot republie tous vos posts publics, avec un compte (hashtag)@tags.pub Pour le moment, j'ai décidé de ne pas bloquer ce serveur. En effet, il ne pose pas de risque pour les données personnelles, puisque seules les posts publics sont republiés, et qu'il n'en stocke pas le contenu (à ce titre, il agit comme un relais). Il est opéré par une fondation à but non lucratif : Social Web Foundation, avec un serveur hébergé au Canada par OVH. Quel intérêt ? Ce qui est affiché, c'est de permettre aux serveurs peu fédérés de pouvoir malgré tout suivre des hashtags en suivant n'importe quel compte (hashtag)@tags.pub et ainsi également d'augmenter la visibilité générale des posts publics sur le fédiverse. Si cela vous dérange, vous pouvez bloquer vous-même cette fonctionnalité : il vous suffit d'ouvrir le profil d'un bot (prenez une notification de boost), de cliquer sur les trois points sous le profil, puis sélectionner "Bloquer tags.pub" tout en bas du menu contextuel. Merci par avance de votre retour. Je n'exclus pas de revenir sur cette décision et de bloquer à l'avenir le serveur tags.pub https://tags.pub/ #tagspub

0

3

0

bbₜᵤₓᵢ @tux@burningboard.net · Jun 06, 2026

RE: https://burningboard.net/@AlienJay/116682536698437762 Verrückt, ich habe noch nie eine so umfangreiche Diskussion im Fediverse gesehen 😯 Wenn ich es richtig verstanden habe, sind wir zu dem Schluss gekommen, tags.pub nicht zu sperren, und dass jeder Nutzer selbst entscheiden kann, ob er die Instanz blockieren möchte? #tagspub #mastoadmin

Quoting

Jörg 🇩🇪🇬🇧🇪🇺 @AlienJay@burningboard.net

Ihr kenn die Instanz „tags.pub“? Das ist diese Domain, die Hunderte von Bots betreibt, nur um bestimmte Hashtags zu boosten. DAS NERVT! Ich habe schon die ganze Domain tags.pub blockiert, um diese ganzen scheiß Boost Bots die dort alle laufen los zu werden. Die Boosten mich immer noch. Ich will das nicht. Warum wird die Blockade der ganzen Domain ignoriert? Muss ich diese Hunderte von Drecksbots wirklich alle einzeln blockieren? Oder können wir die Instanz einfach mal aus dem #Fediverse schmeißen? Kann man irgendwie einen generellen Complain gegen so eine Instanz machen? #followerpower #fedihelp #genervt

Open quoted post

9

2

6

0

bbₜᵤₓᵢ @tux@burningboard.net · Jun 04, 2026

#tagspub #mastoadmin War doch etwas nervig, und außerdem gibt's doch die Relays die eigentlich das selbe machen 🤷‍♂️

2

0

About This Hashtag

#tagspub

Related