Very few cases can't be covered by either WSL or a VM, and having dual-booted for years I can tell you that after a few days you get into the habit of only booting the more convenient OS most of the time. It's twice the maintenance and 5-15 minutes of context switching every time you need to do something else.
Ah, WSL... which gives you the best of both worlds: unpredictable and unreliable Windows updates combined with whatever grievances you have about Linux applications.
If by 'booting to the most convenient OS' you mean 'booting to the OS which does not usurp your machine for internal housekeeping purposes (plus a little side of snooping here and there 'to enhance your experience') the moment you switch it on that would surely mean booting to some variant of Linux? Windows seems to think it is more important to try to install the 1709 or 1803 update pack for the umpteenth time, try to stuff the 'Windows 10 update assistant' down unwilling users' throats, ignoring all those 'do not update' flags and settings they were told to hack into the registry. Where the OS can suddenly decide that you obviously are not using that FileHistory backup so let's remove it altogether. In other words, the OS which isn't at the whim of a supplier with an agenda different from yours.
I didn't specify which operating systems, which makes it ironic that Windows was not involved at all in that process. I've used WSL, but on my Windows-only desktop that mostly runs games. See, my work machine never ran Windows. Good job going on a rant about it though.
If Google really wanted to help here, why don't they just, you know, make every part of YouTube less optimised for maximum view time. Remove autoplay, turn down the recommendations. Nah, we're gonna throw some optional, possibly ineffective shit into our mobile OS instead so we can say we did something.
Those features you listed seem like quite useful ones for day to day usage. Many things won’t have a bright line “this makes the product useful” vs. “this makes the product addictive” feature classification.
Because for certain things, it's better to split the content on multiple parts. For example, I was watching a series of videos on Windows Server administration and the content was split into multiple parts and it made sense.
Just because Denic doesn't allow private domain registrations doesn't mean you're supposed to go after people and dump their personal info into your popular blog. Large parts of the information was historical data persisted by third parties that'd be hard to expunge. There's a good reason for pr0gramm admins to want to remain anonymous - cha0s initially quit the site because he received an 80kg steel oven as sort of a threat. The post includes names and contact information of volunteer moderators that weren't even part of their company.
But Brian Krebs' private information - which is definitely out there - is to be kept out of public view? I'm sure he'd pursue legal action if I put that on my blog with some half-baked accusations
It's wrong, plain and simple, which is why pr0gramm moderators have been removing posts with both their own private information and krebs'.
Telegram's security is a joke. They show the first and last letter of your password and the length (the number of asterisks they put in the middle changes) when you sign in. Next to some pretty bad implications (do they store the password in cleatext or just the length and two letters?) , that password is down to about 1/5 of its original entropy. Told them a year ago, they don't seem to care.
EDIT: Yes, Telegram uses passwords if you enable them. This is what the questionable query looks like: https://i.imgur.com/BAnddlg.png
They do? On which login do they show that information? I've only seen the kind-of two-factor one where you have to enter a code sent in a text message or with a telegram message to a different device.
Hint is a text field that you fill in when creating a new cloud password. The hint text is generated based on password if you did not fill it yourself.
A lot of banking apps store cached transaction data and authentication tokens on the "protected" (not accessable to non-root from other apps) part of the data partition. If you run without encryption or with either unlocked bootloader or TWRP installed, someone could just pull that from a device in recovery mode. That's also why unlocking the bootloader wipes your data partition usually.
This should be OR. If you have FDE enabled, then the data is encrypted and it doesn't matter if your bootloader is unlocked or you have a custom recovery installed -- all caveats about the trustworthiness of the crypto and strength of your key still apply.
