Care to explain what’s anti-trans about this? Genuine question, I’m obviously out of the loop, and don’t want to inadvertently cross a line.

Triangle Shirtwaist Factory Fire
Maquiladora
NAFTA
No great single resources for Nike / Child Slavery but… just search for it there are too many to link
I really shouldn’t have to link to the environment, right?

Even the history of this is fascinating. This is the “Moses Bridge”, and it’s a renovated part of the old dyke system that was used to prevent attacking armies from getting in - because the dykes and levee’s had blocked the sea so effectively, they realised they could stop attackers by… flooding them out. Literally.

When it came to renovate this area, they wanted to provide access without denigrating the fact it was an old defensive structure, hence this unique sea-level bridge.

That’s fair enough. I didn’t read it as “initiating a discussion”, more “get off my lawn”. That may, however, be me - I’m coming off my meds and it’s making me grumpy.

I appreciate your point, however - if you wish for this series of communities to succeed, it needs to be welcoming to newcomers. And one of the ways of doing that is allowing for a continuation of conversations that were on the source communities - including, “Oh, we’re getting out”, “Why it’s so bad”, “Where do we go to”, “How do we make the new community look/feel like I’m used to”, etc. etc.

I’m happy to see this because it means that a corrupt and non-people-focussed environment is losing members. Like anything, it will pass, but please don’t push people away by making them feel unwelcome.

60% tinkle…

And the kbin.social formatting:

Accessing through kbin.social and the table format is not formatted correctly. Assume this is a kbin-problem, not a bot-problem, as looking at it through sh.itjust.works formats correctly…

I wanna see it, so here’s another comment to boost - let’s get to 5 and test this bot :P

Thanks for the tip. I really loathe having to do tihs as it doesn’t help mobile, but at least I can auto-sync across desktop browsers :/

That’s exactly the problem. Parts of the cookie banner are from the same domain, but then other parts are from the advertisers domain. So blocking the advertiser blocks bits of the banner, meaning you cannot click on the banner, because it’s just not letting you do so.