“immovable” object (a smart power socket designed to be unopenable) vs. unstoppable force (I want to see what’s inside and access the mcu that controls it).
“call everyone sir/madam, it’s a sign of respect.”
“write names with an uppercase letter, it’s a sign of respect.”
^ things said by people able to despise, ridicule, hate, marginalize and threaten others - and feel good about it as long as they smile and wear a suit doing that.
@tokyo_0@rysiek oh, that is a good point I haven’t considered.
both approaches are valid use cases. I definitely follow some people whose content I like to read, but I don’t want them to see my personal posts. still, I get what you mean and see how it would be the preferred logic for some users or some situations.
all of that would be solved by acl-like features. some of that would still be solved by “public-only follow”.
I’m starting to think fedi needs a two-tier follow system.
“follow” as in “I want to see all public posts from that account on my timeline”.
“folllow” as in “I want to actually be a follower and see followers-only posts”.
now we only have 2. but there are valid use cases for 1. that I am encountering both as a follower and as someone others want to follow.
as far as I can tell, there is no reason for 1. to not exist: those posts are public anyway. is it possible and practical at protocol level? is there a way to get the source instance to federate all such posts to the “follower’s” instance despite no “real” follow? no clue. someone who knows activitypub would have to chime in.
as for my use cases: I am posting almost everything public, but sometimes do a more personal post (usually related to mental health) that’s followers-only. I restrict my followers to queer neurodivergent beings that pass my vibe check because that’s the audience I’m comfortable sharing this with.
but there are others interested in less personal things I post and right now they have no way to get those things on their timeline. this is annoying.
sure, I can do multiple accounts. but that feels like a kludge that got carried over as a “solution” from tw*tter instead of doing it right in the first place. also, using multiple accounts is a pain in existing frontends. they implement an impractical paradigm of switching the context of the entire application, instead of presenting a combined timeline. then there’s the entire bullshit with having to boost things from the other account so they reach the rest of the relevant audience and so on. kludge.
@drewdevault@ironiridis framing a disabled person's need and request for accomodatimg features as "entitlement" is a category error.
for every case of one of them expressing those in a less-than-excellent manner, there's a crowd of others who were excellent about it and got ignored because importance of the request was judged on purely technical grounds by able-bodied developers. some of the less-than-excellent cases may have been born out of frustration and exhaustion from trying to get that across.
please do not apply collective responsibility like this.
usually, your takes on social issues in technology are among the very best and most considerate. let's try to figure out how to turn this into one of those, for the benefit of everyone involved.
looking forward to the release of c23 language standard?
remember, if you hear someone say “I know everything about c”: you either misheard them and they’re actually a marine biologist - or they’re just full of shit.
Transfem enby weirdo, neurodivergent, plural system, 34.Co-founder of Warsaw Hackerspace. Hardware/software hacker. Heavy industrial machinery enthusiast.Some posts might be by @erin because "why bother switching accounts when we share the memory stream" or something.:verifiedpansexual: :verifiedenby: :verifiedtrans: :verifiedpolyam_pi: