> Prudence is certainly a choice one can make, but in no way should it be recommended or required.
risk = probability X severity.
If something is a big deal to you, take precautions, even if it's unlikely, because the severity is high. This is why we take huge precaution with nuclear plants, because the likelyhood of an accident is low, but the severity is high.
If you have nude on your phone, severity is high. The probability that googles will mess with you is low, but it's good advice to tell you to protect yourself.
> If you have nude on your phone, severity is high.
Incorrect, for societal reasons.
For women, the severity of nudes being stolen is very high, regardless of social stature. The majority of nudes published without consent are of women, and the majority of 'revenge porn' nudes published explicitly to demean are of women, and the majority of societal outrage excluding public figures is directed at women. The long-term impacts of nudes being published without consent never fade, and is nearly as likely to result in loss of employment and social stature years later.
For men, the severity of nudes being stolen directly correlates with whether they perceive their career or social stature to be at risk if nudes are stolen are shared, as in the majority of cases men are blackmailed for payment before stolen nudes are published. The long-term impacts of nudes being published without consent fades rapidly for private individuals, hinges on their career and social profiles rather than being effectively universal across their gender, and is often disregarded altogether.
For public figures, the employment and societal circumstances vary wildly, and the overall risk of permanent harm to men increases considerably; however, the risk of permanent harm to women decreases only slightly, and typically only for women who already publish nudity of their own accord, and thus have already factored in the societal harm of doing so.
My time is limited, so here's one contributing citation only:
Modern Android actually does support disk encryption. And the Pixels even have TPMs that should (?) safeguard the key, preventing offline brute forcing the unlock pattern. I wonder what happened here that this did not work...
Someone else here mentioned that the the reddit comments (now deleted) said that the phone had no passcode on it, so anyone would be able to unlock it.
Ah, that's it then. I figured they would likely have a passcode, since the "someone steals my phone on public transport" threat vector is a pretty obvious one even for non-tech users. Unfortunately the thread got nuked before I got to read it more...
This week I was in a chat with the REAL support of a crypto currency.
Unable to help me with my problem at first (we eventually figured it out), they felt they hit a dead end and said: "ok, just send us your wallet.dat, we'll fix it".
I know those guy were the real deal. I knew they would not try to steal the money I had on this wallet, because it was so little it was not even worth the time.
Yet, the fact they asked that proves how much support can badly educate their users.
Of course, I didn't send my wallet, and found another solution since I'm tech saavy. But still...
I once got my screen replaced at one of the phone fix-it places. It's a decent sized chain, not just some rando. On the form you fill out during drop-off it asks you for your unlock code.
none since they can wipe the phone without a passcode. This is true for both iphone and android phones. I'm not familiar with off-brand OS phones though.
Would windows Bitlocker work too? My issue is that Veracrypt requires you to mount a drive, while Bitlocke provides protection over the whole drive (barring your adversaries being Microsoft and/or the NSA).
I just tried Bitlocker for the first time a few days ago. I enabled it, and next time I booted it up, it never asked for my password. It turns out it only protects the drive if it's removed from the computer.
You’re right, everyone has a need for privacy, and there is almost always private info on devices people use. So why is “advice” to avoid repair and eat the costs considered a tenable solution?
The “advice” would also apply if you ever logged into your bank or bought anything, if you ever read your email, if you have any secret keys or certificates for authentication of anything, if you ever visited a web site or searched for something you wouldn’t want someone else to see, if you have a list of contacts, if you have any personally identifiable information, if you ever worked on something considered confidential by your employer, etc., etc., etc.
I agree, but I’m confused; I didn’t make an or proposition, and you followed that statement with one. We can realistically deal with privacy problems using laws, and we cannot realistically ever expect people to never repair devices that have private information on them. Right?
There’s also an unfortunate environmental downside to suggesting that people avoid repair.
Sorry, I’m lost about what your point is. What “or” are you still referring to? You seem to be trying to correct something, and I have no idea what it is.
You defended the specific idea of avoiding repair. If we’re talking about other “precautions”, I’m not sure what you mean because you haven’t made it clear.
My point, I guess, is that “advice” about taking “precautions” really does boil down to victim blaming. There are no reasonable precautions that the general public can take when sending a device in for repair; private information will be available to the person with physical access to the device.
We already have some laws protecting against privacy violations, and the issue in this article is likely covered by some of them. The remaining solution is for Google or Google’s subcontractor to be held accountable and pay damages, which is exactly what is needed to address privacy problems at the social level: consequences for breach.
Otherwise, I don’t see how your suggestion to take “precautions” is helpful or realistic.
It's important to understand that for every person familiar with the name and the abbreviation there are roughly 22 people who have no idea who she is.
> A great comment to refer to the next time some young coder that never lived through IE6 says it's great to have one single engine everywhere.
OP is suggesting that Chrome should have spearheaded a spec that no one but Intel and Google ever showed any interest in. How would that not have been literally "they like a standard (or propose one), they implement it, use it on their projects like google doc, and let the competition deal with the mess"[1]?
Instead they're implementing a spec with broad involvement and support across browsers, it's just taking longer. Seems like exactly how we'd want things to go.
As someone who has lived through the browser wars, I have no idea what you’re trying to say? The situation today is vastly better than it was back then. It’s not hyperbole to say that porting JS from, say, IE to Mozilla took just as much time as it took to write it in the first place. Today, it’s expected (and often the truth) that something you developed in one browser works in the others.
Also, none of specific reasons people opposed Microsoft’s policies with IE, like it’s attempts to lock people into windows-only APIs (ActiveX etc) apply today.
In this case, google can pull off something like OP says because it's dominating the market.
> Also, none of specific reasons people opposed Microsoft’s policies with IE, like it’s attempts to lock people into windows-only APIs (ActiveX etc) apply today.
Chrome implements plenty of chrome only API. They like a standard (or propose one), they implement it, use it on their projects like google doc, and let the competition deal with the mess.
Sure, there is a long tail of web API's like this but they tend to be very specialized. They are easily avoided and ignored by most web developers, who likely have no need for them in the first place. (Both WebGL and WebGPU are arguably in this category - you are unlikely to need them for your website.)
This is nothing like the situation was with IE6. Back then basic functionality was half-broken and it was hard to get anything done without a pile of hacks.
> This is nothing like the situation was with IE6. Back then basic functionality was half-broken and it was hard to get anything done without a pile of hacks.
Causes are not 1 to 1, but consequences are the same: monopoly leads to abuse, abuse lead to some site not working with Firefox, consommers needs being ignored by google and them abusing their dominant position to pass what they want as standard, or just destroy API they don't like (see the latest adblock scandal).
- := makes for explicit assignation + comparison instead of a footgun
- None instead of null + undefined
- set literals
- matmul operator
- foo > bar > baz
- sorting callback semantics
- dunder methods for operator overriding
- list, dict and set comprehension
- generator expressions
- byte literals
- raise SystemExit() for clean script exit
- raw strings
- automatic string literal concatenation
- positional/keyword only parameters
- can use *args and **kwargs together, as opposed to spread
- docstrings
- typing is part of the language, no need for a transpiled dialect like typescript
- "async for" and "async with"
That's only what I come up on the fly, I'm pretty sure I can double the list. Then of course, do we consider builtin to be part of the stdlib, since it doesn't require any import? Because there is a load to say there.
JS does have some nice stuff too though:
- ? and ??
- futures are more ergonomic than coroutines and awaitable anyway
I wish there were more Firefox forks. I would love to have some of the features of Vivaldi, but running with Firefox's underlying engine. But that just isn't a thing, as far as I'm aware.
I'm meaning in terms of appearance, and especially customizing shortcuts. I already use Firefox customized mostly to my liking, but I don't like having the same generic (very tall) top bar that everyone gets. Tab management leaves some to be desired compared to Vivaldi. Yes, there are extensions for that, but they don't function as sleek.
risk = probability X severity.
If something is a big deal to you, take precautions, even if it's unlikely, because the severity is high. This is why we take huge precaution with nuclear plants, because the likelyhood of an accident is low, but the severity is high.
If you have nude on your phone, severity is high. The probability that googles will mess with you is low, but it's good advice to tell you to protect yourself.