Notices by Elia :verifiedtrans: (elia@fedi.quiescent.nexus), page 3

it’s time for the “fun” part: swapping out the pm6-600 monolithic power supply/servo drive monstrosity.

this one is fucked, the seller included it because I might be able to fix it and sell if back to them.

the thing weighs 40kg or so, slides out on rails that let go of it at some point and the last time I actually handled one of those was well before hrt. this is going to go so very well.

ok, that went better than expected.

now I need to figure out which one of the two spares I have is the working unit, and which is the very non-working one.

the story: when I originally bought the robot, it came with one of the servo drive channels broken, reporting “torque limit exceeded” on its axis. it was, in fact, a faulty current transducer reporting exaggerated current readings. I bought two more of pm6-600, “condition unknown”, for cheap. then turned three broken units into two working and one very, very broken.

identified the spare that’s completely fucked - some of the fuse holders were broken off. this means the other one should be fine.

also left a little message.

fun little detail: the customized volkswagen enclosure is equipped with a service light.

but not just any random light.

it’s a car ceiling light made by volkswagen.

pm6-600 all wired in.

I think the only thing I’m missing to power it up is the power input cable. let’s find/make one.

found a plug, time to look for a cable.

almost ready to power it up.

last step before powerup: connecting the control pendant.

it’s alive.

it boots.

it boots windows 95.

*muffled “wait what” in the distance*

“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).

“being visibly trans” vs. “being hi-visibly trans”.

I prefer the latter.

“follow dress code, it’s a sign of respect.”

“use nice language, it’s a sign of respect.”

“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.

every time I see the “sonoff” iot devices brand name, I mentally complete it into “sonoffabitch”.

@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.

1. “follow” as in “I want to see all public posts from that account on my timeline”.
2. “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.

I’m back from a week-long tour of germany on regio trains and this is the only way I can summarize the deutsche bahn experience.

germany is not a real country, it is a conspiracy run by rats: there’s a rathaus in every city.