rainwall

Plus apparently her kids premiums are going to double, so she has a personal issue with it now.

For everyone but the trillion dollar companies that own the US government.

He points out very reasonably that the key to it is scrapping the American forced article 6 of the EU charter, which is basically their DMCA. That’s what would let Europeans legally reverse engineer these services to import data/process/apis/etc into the new EU stack. It would also instantly allow all “right to repair” efforts, as that law is what stops them.

Apparently it was supposed to be. They have the core functions in a “can’t OTA” container, with less important functions like AV/etc in a “can OTA” model.

This update was pushed to the “can update” side and fucked the “can’t update” side, which is its own can of worms. Another can? Jeep pushed a silent, emergency update “to all Jeeps even those who have automatic updates disabled.”

So the issue is not that they have no security model, it’s that it clearly doesn’t work and they can and will push secret updates even when you decline all updates.

Brain Krebs on Mastodon:

https://infosec.exchange/@briankrebs/115361904433612087

Some companies do “internet only” wifi where there is no routing to internal services for anyone, radius or not. A VPN is required, even when at work, to access anything internal wirelessly. Its a perfectly reasonable config that lowers the risk of breach of your internal network by exposing less of it over the air.

This is also the nominal config for most zero trust networks, but that’s more a consequence of the “always on” nature of those VPN connections since you never have unencryted traffic anywhere, regardless of origin point.

No one is taught to be irresponsible in traffic.

What is taught in normal, reasonable places, is that the person with a weapon is responsible for the damage it does. It’s a very straightforward rule.

Pedestrians always have right of way in my state, regardless of legality. They can indeed step out into a busy road and it is entirely the drivers responsibility to stop. Ensuring safety in a shared space is always heavily biased towards the person who is operating a deadly weapon, as it should be.

If you can’t be sure you wont kill a person walking, even one making irresponsible choices, you need to slow down, drive more defensively, or not drive at all.

Microsoft literally calls the feature “vibe working.” Youre not far off the actual name.

They aren’t even pretending to care anymore.

The vm/container side is less important than the “cant run a RAID parity check regularly because it makes the NAS useless” part. Thats my qnap experience. It might have gotten better, but it was shit heel for me, and the NAS was in the 1k range.

I’d argue that a NAS should be able to run containers at this point. NAS hardware does not need to be utterly gutless just because it can be. A versatile NAS is actually a great first choice for a homelab setup before you start to expand.

I’d recommend against it. It works “fine” but everything is in a thin, but walled, garden. Every app is some “Qsomebullshit.” They really, really want you in their ecosystem.

Id say the systems are underspec’ed as well. The model I bought years ago pitched itself as VM/container ready, but the chipset was so weak it couldn’t run anything worth a damn. It couldn’t even run a scrub on lowest priority without choking all other filesystem access. When a scrub takes 3 days or more, it wasn’t exactly a usable experience.

If you have the funds, i’d recommend 45drives. They make very good hardware and sell 4/8/15 disc form factors for homelabs.

That’s one the books I tried to get through. Maybe it was in a more raw state at the time, but it didn’t click for me.

Im honestly more interested in Nix, as even with all the chaos it feels like it has good technical momentum. I just wish there was something equivalent to Geerlings “Ansibles for devops” or Shotts “The linux command line” for it.

As someone who is curious about Nix but has given up after trying to wade through the myriad and conflicting “getting started” resources for it, I cant imagine how bad guix docs must be for a Nix enthusiast to adandon it.

It reads as an “honor” system rather than any objective exclusionary mechanism. Steering committee members are expected, and to their credit, were considered to have done so, but it all seems like judgement calls.

It is fully possible that grey areas or instances where other SC members didn’t personally care, were not met with recusal.

It would overall be better to not have those conflicts be likely or even possible.

Outside this community: someone who programs computers.

In this community: no one has any fucking idea how to answer that.

Note that this apparently does work with a 4 port local KVM as well. Technotim, a homelab youtuber, tested them working together smoothly.

So buddy up the above with a jetkvm and you can control 4 systems at once.

Tailscale has this same functionality, and is free for something like 100 hosts. Uses wireguard as the backend tech. It also has apple tv and android clients, so you can setup the Tailscale app on an end client for a user, then setup the jellyfin client and they should be good to go. That client device will just “see” your jellyfin server as a local client on the same network, albeit a tailscale wirrguard overlay network.

I haven’t actually deployed it as I don’t share my media server currently, but I was investigating it a bit ago.

Best case for their charity is likely to stay on Slack to get them as corporate sponsors, but add “data sovereignty” as a core part of their curriculum. That keeps the charity going, but instills the foss ethos in all their students.

Who knows though. They have 5 years of free slack either way because it would be incredibly bad PR to revoke it now. The runway is there to exit cleanly at least, which is a lot more than they had before.

The founders comments in the hacker new thread, plus some other errant ones from hack club users.

Here is there “we are staying on slack” comment:

Hi, update here (this is Christina, Hack Club cofounder): looks like Hack Club is staying on Slack.

Thanks to all of you for the appreciation and support for Hack Club, and for listening to what we were going through. The support has been amazing. Hack Club has so many cool teenagers coding awesome projects, making friends and solving problems together, and it’s great to see so many people championing them. We are glad to stay on Slack and want to do so much more with them together going forward.

Thanks to Denise and the Slack leadership team for reaching out here on hn, and in a call directly with me and Zach today. And thank you for restoring Hack Club’s terms with improvements. We really appreciate it, and we’re glad to be able to stay on Slack.

I just want to add that it was great to get to know Mattermost and the team- and the hack club engineers were actually pretty excited to move there. It’s an amazing product and for it to be open source is awesome.

She doesn’t mention the “new rate” but it was apparently confirmed internally, and there is a comment in that above thread that lists it.