The issue is about getting locked out of your own data, which can easily happen in a number of cases.
And you don't necessarily need to actually have your account banned.
Let's just say you signed up for a Microsoft account when setting up for a new PC (well, because you have to). You don't use that account anywhere else, and you forgot the password, even though you can log in via PIN or something else. Now you install Linux or just boot to a different system once. When you need to boot to Windows again, good luck.
And that's just one of the cases.
A real disaster happened to someone, although on a different platform, and the context is a bit different: https://hey.paris/posts/appleid/
> I wonder if the largest software company on the planet (with an operating system in practically every home) can help with making that better. Seems like Apple can, weird.
If you're talking about time machine, windows has had options built in since NT.
Let's be serious for a second and consider what's more useful based on the likelihood of these things actually happening.
You're saying it's likely to happen that a laptop thief also is capable to stealing the recovery key from Microsoft'servers?
So therefore it would be better that users lost all their data if
- an update bungles the tpm trust
- their laptop dies and they extract the hard drive
- they try to install another OS alongside but fuck up the tpm trust along the way
- they have to replace a Mainboard
- they want to upgrade their pc
?
I know for a fact which has happened to me more often.
You've listed five scenarios where local recovery would help and concluded that cloud escrow is therefore necessary. The thing is every single one of those scenarios is solved by a local backup of your recovery key, not by uploading it to Microsoft's servers.
The question isn't "cloud escrow vs nothing". It's "cloud escrow vs local backup". One protects you from hardware failure. The other protects you from hardware failure whilst also making you vulnerable to data breaches, government requests, and corporate policy changes you have zero control over.
You've solved a technical problem by creating a political one. Great.
The newer amd and Intel systems are also copilot certified. After getting a new laptop last month I can say that it doesn't hurt and has some nice advantages. If you just ignore the stupid names. The NPU means your images can now get indexed by content without ruining your battery life for example, same thing with recall. Without certain hardware requirements there's no way these things could run on device.
Now MS just needs to keep working and refining these features that don't sell copilot subscriptions...
You don't get ads on YouTube with a premium sub, your activity data (views, for how long, what topics, what times of the year, of the day, so on and so forth) is still collected, and appended to your profile, the same profile that is used by AdSense to show you ads around the rest of the web.
With that website open, runs at 2850 MHz to be specific, it normally idles at 400-500 MHz with ~20 processes (firefox, gnome-shell, alacritty, etc, etc) using the GPU
There's eu(maybe even EEA?) wide free roaming legally mandated since I think 2017 or so? But it's not a permanent solution, your second paragraph still holds true.
As far as I know it is only EU. Both UK and Switzerland have some operators that roam and some that do not. fwiw, fastweb in Italy provides roaming in both and has a very generous fair usage policy.
That's because we are no longer in the EU. Before Brexit they were legally mandated to allow free roaming in the EU. Now they are back to charging whatever outrageous prices they wish.
Except ASS streams really aren't that big and don't have to be stored with each encode. They can just be in a separate file. And this is how cr used to serve them. Before they used hardware drm you could just download all of the separate sub tracks.
You don't need to multiply anything here, except the number of sub streams. One is ass, the other the primitive standards Netflix and other surges use.
Someone else was saying they maintained burn-in subs for devices that didn't handle ASS renderers. Even without accounting for the burn-in versions, using non-standard subs still bumps them off of commodity subtitling services and limits distribution/syndication.
Edit: and to the peer comment regarding S3 vs self host: regardless of 10x cloud cost, it's still 10x volume. Where 1TB local would do, now you need 10TB (10x the cost).
The labor of ass to ttml is there yeah. But the the factors are n_videos * languages * 2 Formats. And considering these are pretty compressible text(34MB->4MB for a completely bonkers sub track that includes animations, animated fonts and otherwise transformed text). I can't imagine that hosting costs cost more than their analysis.
done here meaning you've lost your data which uhhh, is currently on a drive in the hands of thieves, so what did you lose again?
reply