There has been a lot of froth about tags.pub the last few days. I feel like I've already said what I'm going to on that subject. Although I rose to it's defense, it did motivate me to fix one thing that had been bugging me.

I went to extra effort to get my blog/podcast site feeding **in** to tags.pub. That required figuring out Bridgy Fedi login stuff and getting the bridged account to follow @_followback which was a bit of a pain in the ass. Eventually it worked.

However, then the problem was that when #11ty assembled the webmentions for each post which it has been doing dutifully for the last year and a half, those would be swamped with the tags.pub bots. Particularly on my podcast episodes where I have a lot of topics and a lot of tags, the first 15 interactions could be the bots.

So, I sat down and wrote a filter to strip out the webmentions before I render them on the page.

<code>

eleventyConfig.addFilter('removeTagsPub', (webmentions) => {
return webmentions.filter((webmention) => {
return webmention['author']['url'].startsWith('https://tags.pub') == false;
});
});
</code>

It does work a treat. Now I get the advantage of pushing to tags.pub and hopefully increasing the discoverability of my fairly niche indie project while not having to look at lots of "#thistag boosted your post" webmentions on every blog post. Win-win.

#tagspub #eleventy

tags.pub

@mina
I suddenly got spammy boosts from bot accounts.
I had to find out what this is, why it happens (still dont know. Opted-in somehow by my instance) and how I can stop it.
Older posts with #tagspub said it wasnt possible to opt-out because tagspup even worked around a server block.
Bad communication of Evan ignoring the problems of many people and only stepping back after huge pressure.

I want a big fedi and see social media as essentially about the public conversation and getting attention. I want hashtags to work well here without bots but otherwise can't understand the concern.

#TagsPub

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.

Edit: There's some good discussion below, worth reading. Also including some arguments for being sceptical about this thing.

#TagsPub

"You pointed out how I was violating consent and opting others into my bot-farm against their will and now I'm receiving abuse so f*ck you" is perhaps not the flex the author intended it to be.

#consent #TagsPub #hashtag #ReplyGuy

@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

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

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

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