#fediblock

  • IP Address: 142.132.225.129
  • User-Agent string: "fedi-block-api (https://gitlab.com/EnjuAihara/fedi-block-api)"
  • Why: actively compiling a database of who blocks who, expressly marketed to those who want that information for retaliatory harassment.

page snapshots for posterity: ① the website (note the “suggested” ban reason search string), ② the gitlab.com page (contains racial slur at the bottom)

It scrapes both pleroma and mastodon once a week, the next run will be on the 10th of August if any of you want to figure out fun ways to poison that data.

Follow

(thread missing CW) fediblock, harassment, actionable to instance admins 

(boost)

(thread missing CW) fediblock, harassment, actionable to instance admins 

@moonbolt Hm. So, I was thinking of making something that would let one figure out if a particular instance blocks their instance[*], because I end up responding into the void once in a while (someone boosts a post from an instance that blocks mine and I spend time writing a reply to it; even if I always checked /about/more of the appropriate instance they sometimes fail to mention suspensions/fail to mention all suspensions there). Would you personally consider such a thing abusive in any way?

[*] I was thinking of two ways:
a) making use of the way "suspending" works in Mastodon: the instance considers signatures from the blocked instance invalid -- so just send some random public post from my instance there and see what's the response,
b) try to find a post on the maybe-blocked instance that should have appeared in a thread on the maybe-blocking instance and see if it's actually visible via a web request there.

(thread missing CW) fediblock, harassment, actionable to instance admins 

@robryk .hg Based on the original post, yeah, don't do that?

It's not too much trouble to respond into the void occasionally, is it?

(thread missing CW) fediblock, harassment, actionable to instance admins 

@moonbolt

The original post was complaining[*] about basically a search engine that allows one to find every instance who blocks some particular instance. This is not what I would want to have: I would want to have something that answers the question of "does instance X block my instance". IIUC the undesired thing was aggregating that across all Xs and making that aggregation easy to access (i.e. easier than doing a web search for "inurl:about/more <instancename>" and manually grepping through results).

[*] for some value thereof, possibly weird word choice

> It's not too much trouble to respond into the void occasionally, is it?

I've just counted: happened to me 10 times last month, including 1.5 times when I spent nontrivial time and expected (and still expect) that the person would be interested in my response and would want to respond in a way I would find interesting. I'm not sure if that's occasional~

Sign in to participate in the conversation
Interlinked MST3K

this is mst3k