@centopus personally, I see @AsahiLinux as a "canary" project in that regard.

@linuxfoundation and @torvalds need to enshure that toxicity and neighsayers are toned down way harder, cuz bullying people like #marcan into quitting isn't gonna help anyone and will only damage #Linux by making it look like the "#Neckbeard" #TechBro shitshow that #Lunduke, RMS et. al. stan for...

• I literally know a shitload of trans, non-binary or just non-#WHCM [white hetero/cis (binary) male] persons who refuse to even consider upstreaming or contributing to #Linux, #GNU or any #FLOSS projects at all due to the sheer #toxicity observed externally.

And that is a problem even if we don't care about #diversity, #equity and #inclusiom but merely the #survival of said #OpenSource projects!

• Cuz why would I (or anyone else) want to work with/on/for a company/project that'll get me (deservedly [!!!]) side-eyed at best if not unfriended by the few people I care about personally?

@msdropbear42 TBH, I would've considered some but sadly I've yet to find any that does implement said blocklist feed feature...

Tho if anyone knows I'd give it a shot...

• Also the problem isn't whether or not @Gargron et. al. are able or rather willing to implement such a feature or actually give a shit about the issue ( Spoiler: I'm convinced that's not the case cuz #glitchsoc tends to implement things first and only once people spam an issue with a drop-in PR will they consider fixing it by merging the solution someone else already did.) but rather the nonchalant attitude of those classifying and sorting issues without reading and/or understanding the contents.

It's almost as off-putting as fighting MRAs and transmisogynists that backroll any edits on principle including deleting any discussion and appeals against their actions 'Cuz I sez so!'...

• And then people wounder why noone wants to do #FLOSS and why #tech is dominated by #WHCM #TechBros that seem to suffer if not from #EliteProjection but #PrivilegueProjection...

Sorry, but I'd rather vent than suffer...

Whilst #Mastodon has some basic features like AUTHORIZED_FETCH after people like Laurelai had to invest a shitton of emotional labour to make #WHCM & #TechBro @Gargron understand that this is like a very basic feature, I've seen that #development has turned worse.

• Instead of actually reading the issue explained in detail, including reasons why this is #notADuplicate, there seem to be maintainers that instead of looking up the issue just bury it by closing as duplicate - and do so systematically...

• So instead of having arrogant 'lol, make it yourself!' we get an arrogant 'it sez subscribeable blocklists, so it's a duplicate' as reply and get stonewalled into "#closed for #duplicate" - 'jail'...

I find this rather upsetting because it's neither fixing the original issue nor have the maintainers any intent to do anything about it but stonewall anyone to a zombie issue as a matter of principle...