re: meta, fediblock
@Kye@tech.lgbt To be clear, in this case I wasn't referring to this block in particular, but more to the general discourse around "fediblock is out of hand" that seems to be going around again. Though at least this time, some of the discourse is more nuanced than that, which is good to see.
But yeah, in that specific case, a lot of people seem to just be *assuming* that there must not be much to it, just because they haven't seen 'printed receipts' of the exact details, if that makes sense. That's something I've seen happen a few times before as well.
meta, fediblock
Since there's apparently fediblock discourse again: "instance blocking is a last resort" and "instance blocking is a frequent occurrence" can both be true simultaneously.
There's an awful lot of people (including instance admins!) who still need to learn how to deal with community safety effectively and what the impact of their choices is on other communities.
If you want to see the amount of instance blocking reduced, then your focus should probably be on "eliminating the reason for it" rather than "telling people not to do it" or invoking cancel culture rhetoric.
This includes things like "understanding how one admin's failure to moderate leads to everybody else's workload increasing", and "when someone is behaving abusively, the primary focus should be on the safety of the victim(s) and not on the abuser, even when the abuser has trauma/etc. themselves".
@tobi Oh is *that* why people instance-block m.s
@scanlime I haven't tried exactly that, but I *do* regularly keep an eye on where things are served from, and unfortunately Cloudflare controls a double-digit percentage of web traffic and that's not *just* big sites, quite the opposite :(
meta, blocklists
@asb This is something I've been conflicted on, personally.
There's clearly value in off-the-shelf blocklists for at least some baseline set of malicious instances, which people now have to gradually rediscover themselves after getting a lot of abuse.
On the other hand, there's a very real risk with "review-less" blocklists in particular, of instances ending up on blocklists and getting widely *wrongly* blocked (for reasons ranging from "this is a more subjective block reason" to "someone was added to the list maliciously"). There's a history of this sort of thing being weaponized towards marginalized folks in particular.
I'd really like to see some implementation of blocklists that accounts for this, and that involves a review step but without making it a lot of work. The Fediblock hashtag gets pretty close, but is difficult to explore retroactively for new admins.
TL;DR: Yes, I think it's needed, but it's also something that's very easy to get dangerously wrong.
@whreq Wow.
@ethorsoe Yeah, and how inextricably it conflates that with the technical properties of what *should* be called eg. a library or module (depending on perspective).
"Motonormativity":
gets my vote for Urbanist Word of 2023 (aka "Car Brain").
The idea that people think it's normal for cities, and the world, to be designed around automobiles, a transport method that excludes almost one-third of people in most societies.
Based on philosopher David Hume's hoary is/ought fallacy (Just because something "is" like that, people think it "ought" to be like that.)
Thanks to Ian Walker for coming up with a very useful term!
Study here:
@jfhbrook Hmm. Don't think that's possible? IIRC qmk expects you to specify options at compile time?
@jfhbrook This is pretty much how I at one point implemented Nix (lexical) scope inheritance in my Nix-to-JS compiler, but iirc there was some cursed Nix-specific nonsense that made it not work in 100% of cases
"ai"
Earlier today, I saw something from ChatGPT go mildly viral, only to notice it had plagiarized some of my papers. It hurt like hell to see all the technical meaning that I had worked so hard to convey with my words reduced to textured English product and regurgitated.
The last thing in the world I want is for that to be integrated with my literal browser.
re: meta, infosec.exchange
@rosnovsky@lounge.town See https://pleroma.envs.net/objects/c1cd6fa1-147d-4cbf-8b87-bec64b9a4293
In the process of moving to @joepie91. This account will stay active for the foreseeable future! But please also follow the other one.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.