TLDR in text please. Not going to spend 16 minutes watching that.

Dr. Disrespect: I’ll fucking own this problem!
Also Dr. Disrespect: Owns up to inappropriate message exchange with a minor.

awkward_side_eye.jpg

“the job market is so fucked up so but I’ve done a lot of open source work, here’s my Github”

Economy 2.0 is next week I think (hope!) - so this is just vanilla breakage.

The obvious recommendation is Gentoo stage1 tarball running in Windows Linux Subsystem.

(on a serious note: whatever you’re running on your daily driver)

Been using Nebula for a while now. Going to miss some YouTube creators, but I’ll expect to get over it.

The rubber keyboard was pretty weird first, felt a lot like cheap pocket calculator, but once you got used to the BASIC shortcuts, you could program like a champ on it.

The Swedish Social Democratic party (supposedly staunchly left wing) are the ones behind Chat Control 2.0. So just voting for left is not a guarantee we actually get sane MPs in the parliament.

Baseball

So, is this the type of SLAM you’d typically see in a moshpit? Or are we talking about wrestling slams?

Well, that was extremely long winded way to say “depends on your threat model”. Which it does.

So nothing new under the sun.

deleted by creator

I think what we mainly lack is people asking questions, not a particular set up of tech.

Why?

So your requirement with cellular calling (eSIM) is already fairly restrictive and depends on which market we’re talking about. Where I live (.se) you get to choose between Apple and Samsung and since Apple was out of the question, you’re stuck with Samsung.

Not entirely sure if your second requirement with long battery life can be fulfilled. You’ll be charging the watch every day, probably more often if you take calls on it.

There’s some rumors that Garmin Forerunner/epix will get eSIM support, but that will be also carrier dependent.

These wearables are pretty complicated high end devices, I wouldn’t really give them to elderly parents who stuggle using a normal mobile.

I think it might be better to look into other tyoe of devices like pager systems from caregivers, if you’re worried about health issues.

I thought it was funny as well. Sometimes FOSS communities are so very uptight, we should relax a bit.

Yeah, well just go ahead and see if it works for you now. I doubt much has changed, but some bits are probably more polished these days.
Most distros support some kind of LiveCD, so you can try it out without having to reinstall your machine, it’s painless and quick to evaluate before you take the plunge.

zenbook duo pro

A quick search reveals this. Might be helpful. https://davejansen.com/asus-zenbook-duo-and-fedora-linux/

Looks like AI wrote the article

I also don’t get much value out of the statement that “every” OS except Android is vulnerable. Do they really mean all other OSes, or just what would come to mind for most people, i.e. Windows, macOS, Linux, iOS? What about the various BSDs for example?

It’s a DHCP manipulation attack, so every RFC 3442 compliant DHCP implementation implementing option 121 would be “vulnerable” (it’s not vulnerability though). Android apparently doesn’t implement it, so it’s technically impossible to pull off against Android device. There might be others, but I’d guess most serious server/desktop OS’es implement it.

The title isn’t misleading at all, even though the “neutering their entire purpose” is a bit of a click-bait. This doesn’t affect ingress VPN at all.

It’s an attack that uses DHCP features (according to RFC).

It’s a clever way to uncloak egress VPN users, therefore it does have privacy impact since most of us use VPN for purposes of hiding out traffic from the local network and provider and there’s no “easy” fix since it’s just a clever use of existing RFC.

Knowing history, that’s a one tape I have no intention of listening. RIP the crew and all other early space flight pioneers who perished pushing the boundaries of our planet.