0xtero

joined 6 months ago
[–] [email protected] 3 points 1 month ago (2 children)

I notice you quoted the sentence from the description - did you watch the video itself?

No, I'm afraid I didn't.

[–] [email protected] 2 points 1 month ago* (last edited 1 month ago) (4 children)

Every time I talk about privacy online, the pessimists always come out. "It's impossible to have any online privacy.

My experience is actually completely opposite. While mainstream "normies" don't seem to care, most of them are using readily available privacy tools in their communication daily. Things like WhatsApp, Signal and iMessage. Most websites these days are HTTPS enabled. Governments are so concerned about this loss of monitoring capability, they're trying to craft laws which allow them to backdoor devices before encryption happens. And they're meeting resistance, despite all the lobbying (see Chat Control2.0). We've never had as widely adopted privacy tools as we have today.

Big tech and advertising are two problems that still create trouble. A lot of this stems from completely different, non-privacy related reasons (the lax US policies concerning anti-consumer and monopoly laws) but even here policies around the world are slowly catching up. GDPR gives Europeans quite a bit of control over our data and while this is still just one baby step - it's much better than it used to be. There's a lot of global inequality here though. Facebook/Meta is synonymous to Internet in the developing world, because they've used their monopoly money to exploit the situation. Digital imperialism is still strong.

I'm not going to harp too much on SMTP privacy, Proton has a bunch of nice services. If that's where your MX happens to point at is, then great, but we do also need to slowly move away from these old protocols that offer no privacy choice (yeah I know, SMTP is here to stay).

What I'd like to see more, is talk about threat modeling in this space. Because that's where it all starts and threat models are quite personal. There's no "one size fits all" privacy, because our needs vary. Political dissident living in exile from hostile government has completely different needs for privacy compared to a person who doesn't like YouTube ads. We should try to foster easily digestible discussion around personal threat modeling - right now we (the privacy crowd) come across as loonies since lot of the advice we give starts from the wrong end of the model.

I don't see digital privacy as a pessimistic space. But what do I know, I'm not a content creator.

[–] [email protected] 12 points 1 month ago* (last edited 1 month ago)

What else am I missing?

Large scale manufacturers pre-installing Linux? Readily available multi-language support for home users? Coherent UI regardless of computer and distro underneath. Billions on lobbying money spent on politicians for favorable policy crafting? Billions spent on marketing campaigns to actually sell the idea to the masses who simply don't care any of your points (or any technical reasons, privacy or anything else that might be top of mind of the current Linux userbase).

I'd say Linux has a good chance of capturing 5-6% of the market in the coming years if lucky (I believe we're somewhere around 4% at the moment), unless one of the big tech monopolies decides to start throwing money into it (Like Google did with Android)

[–] [email protected] 57 points 1 month ago

This is the moment in Scooby-Doo where the gang unmasks the person they've just caught and underneath is just the Microsoft Bing logo

[–] [email protected] 23 points 1 month ago (1 children)

[email protected] used to be cool, but it's heating up!

[–] [email protected] 61 points 1 month ago* (last edited 1 month ago) (7 children)

The only AI function I could see myself using is one that would summarize 15 minute youtube videos into coherent readable text in blog format. That would be nice. Especially when they're posted like this, just links without much context.

[–] [email protected] 11 points 1 month ago (6 children)

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

So nothing new under the sun.

[–] [email protected] 7 points 1 month ago* (last edited 1 month ago)

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.

[–] [email protected] 12 points 1 month ago (1 children)

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

[–] [email protected] 24 points 1 month ago* (last edited 1 month ago) (2 children)

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/

[–] [email protected] 14 points 1 month ago* (last edited 1 month ago)

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.

view more: ‹ prev next ›