Have they said that recently? The only definitive comment I remember from them was something along the lines “definitely not in the next 2-3 years” around launch, which was 3 years ago.

Not saying that means I “expect” it’s happening, just curious if you know of anything more recent that says its not happening.

I don’t think is is a backdoor. At the moment I wouldn’t consider this article any more than FUD.

It’s unclear to me if the security company has actually said what the vuln is or not, but if it’s what was presented in the slides linked in the article this is at worst something that can be “attacked” from a computer connected via USB (and I’m pretty sure it would require special software too), where the attack is sending out possibly invalid bluetooth messages to try to attack other devices or flashing new firmware to the ESP itself. It’s not a general “backdoor” in the ESP32 itself. At least that’s the best interpretation I’ve been able to make. Happy to be corrected if anyone finds more info.

Oh hey, actually reading the article for the win; it’s already possible to turn a limit on manually:

echo 80 | sudo tee /sys/class/hwmon/hwmon3/max_battery_charge_level

Agreed. I’m definitely capable of replacing my Decks’ batteries, but I’m excited about this feature because I’d still rather not have to. Plus my deck spends 99% of it’s life plugged in on it’s dock.

It doesn’t sync to homeassistant, but I use a Xiaomi scale with openScale off of F-Droid. There’s a few different scales supported: https://github.com/oliexdev/openScale/wiki/Supported-scales-in-openScale

I didn’t think any of those companies did any manufacturing.

They don’t. Well, TI does but not anywhere near the the node size of the three you mentioned: https://en.wikichip.org/wiki/technology_node

deleted by creator

The repo owner claims to have permission from contributors to relicense (and rewrote some other parts where they couldn’t get permission?): https://github.com/stenzek/duckstation/pull/3295#issuecomment-2348988362

I don’t really understand the rest of that comment though…

They may block IP addresses associated with consumer ISPs. Assuming that’s the case, I would guess you’re seeing that as an HSTS/TLS error because their network is trying to trick your browser into redirecting to/displaying an error page hosted by some part of their network.

Tell them if you have to go back to the office, you quit.

Nah, never say “or I’ll quit”, you just say you won’t go to an office. End of statement. You don’t make any sort of threat or give them an ultimatum, just set your boundaries. Make them fire you, if you’re valuable and/or well liked odd are they won’t and you just get to keep working remote.

deleted by creator

IMO, the best free option is https://freedns.afraid.org/. The biggest downside of that one is that you have to login a couple times a year (IIRC?) to keep it active. I actually still use this even though I have a paid domain, I just CNAME my real domains to the afraid dynamic name. That was easier than changing the config every time I become unhappy with my domain registrar and have to reconfigure everything after swapping.

That doesn’t mean the issue wasn’t/won’t be escalated. It might even mean it’s more likely since someone bothered to make a response macro for it, they presumably got more than one or two emails about it. So it’s probably more likely to make it on a “list of issues we saw this week/sprint/month/quarter”.

Apex Legends is verified: https://www.protondb.com/app/1172470

The finals doesn’t work because of anti-cheat: https://www.protondb.com/app/2073850

Edit: World of Warships is playable: https://www.protondb.com/app/552990

Less commercial interest means only hobby level development

Podman is developed by RedHat: https://github.com/containers/podman/graphs/contributors

The day Firefox shutters its doors is the day the internet truly dies.

*the web

The internet has so far been doing a much better job surviving as a proper decentralized system than the web.

Unfortunately, no. Samba needs a different label. Doing that relabels things so that only containers (and anything unrestriced) can access those files.

IMO, yes. Docker (or at least OCI containers) aren’t going anywhere. Though one big warning to start with, as a sysadmin, you’re going to be absolutely aghast at the security practices that most docker tutorials suggest. Just know that it’s really not that hard to do things right (for the most part^[1]).

I personally suggest using rootless podman with docker-compose via the podman-system-service.

Podman re-implements the docker cli using the system namespacing (etc.) features directly instead of through a daemon that runs as root. (You can run the docker daemon rootless, but it clearly wasn’t designed for it and it just creates way more headaches.) The Podman System Service re-implements the docker daemon’s UDS API which allows real Docker Compose to run without the docker-daemon.

The light is visible, the flashing isn’t.

The top white rectangle is a multi-color LED (presumably RGB). Can’t make out what’s in the bottom, but I wouldn’t be surprised if it was some form of light sensor for (literally) flashing new information onto the tag.