As a fellow Beehaw local, ditto. Would definitely be a shame, even if I can appreciate why it’s being considered.

I do think the potential federation to build a unified alternative to centralised megacorps with freedom of movement for users is well worth the cost, and Beehaw leaving the party erodes that, but ultimately what will hit me on a day to day will be the loss of the usage pattern described above.

Where do we stand on hoarding code to protect against outsourcing? I have a friend who is encouraging his team to do everything he can to hoard and make it impossible for recently onboarded individuals in a "cheaper cost center" to mess with it.

I think it's the right call, for both the team and the company. The team wants to keep their job, and to keep building the thing they worked so hard on. But I think it's also best for the company. Management can't control themselves when they see that they can get literally 10 engineers for the price of 1 local engineer. They know that each of the 10 is going to be less good than than a local engineer, but they always fall for "but still, they're not that much worse and for that price how can I lose!". Of course, the damage of 10s of mediocre-bad engineers is far more costly, especially when outsourcing an existing project. So I'd say it's the right thing for everyone for the team to protect their code ownership anyway they can.

This comes to mind https://youtu.be/KrcY6PXkGuE?si=ShC5paBmaDBcR66C

I’m going out my damn mind trying to work out what I should set it at. I’ve been obsessively adding more and more temperature and humidity sensors around my living space to work out exactly what my idiot brain thinks is comfortable.

I don’t understand why 23C/50% makes me feel like I’m in the fucking Amazon rainforest one day, but on another I feel like I’ve got ice forming on my damn face like Jack Nicholson at the end of The Shining.

I’m this close to buying a ZigBee rectal thermometer. Core body temperature has to be the missing piece. (I suppose any ZigBee environment sensor can be a rectal one if I bite down on something first).

(Oh and lux, I wonder if lux levels tricked my brain but that doesn’t seem to correlate either!)

While I appreciate the difference between mirroring and emulation, @lemmyvore@feddit.nl might have a point in so far as scrcpy and other options that aren’t emulation, may still be part of the reason why no one is making polished emulation options. If a dev can get by with a bunch of physical devices connected and controllev via adb, scrcpy and the like, or a passable emulator in Android Studio, then there’s less reason for them to build or contribute to an emulator for their needs, and consequently op (and the rest of us) don’t get a shiny open-source emulator.

Man! I was super excited about this, being a big NixOS fan, but then I realised that the “Way” bit is going to kick me in the nuts. I haven’t made the switch to wayland yet; I keep thinking about switching, but last time I checked being tied to i3 and nvidia hardware scared me off (although I’m aware sway is a drop-in alternative to i3, but it’s an extra complication). Another reason to make the switch when I can though!

Out of curiosity, how do big media apps treat something like Waydroid? Like, I imagine Netflix and co being awkward with anything like this in a misplaced attempted to prevent “piracy”. Do you find apps treating you like a second class citizen?