I'm almost certain that earlier versions of iOS exposed the comma on the main keyboard and hid the period under the symbols button, because double-tapping space added it.
Which meant that, depending on version, you'd sometimes need to tap 6 times to write "..." (to enter the symbols keyboard mode after every period, since it would go back to the primary set every time), and only 3 to write ",,,".
But I might be wrong.
I never understood the scale of this bullshit until I had a user request his script packaged. Now, Intune doesn't like executing random python scripts, so I gave him several options for 8 KB, 50-lines-of-code script.
He disregarded them and wrapped it all in Electron.
I received a 380 MB zip file.
But, well, it had an .exe inside so I could work with that. ¯\_(ツ)_/¯
I know it’d be expensive, but I wonder if it’d be worth it to valve to start producing ram.
There's a reason why there's only, like, three RAM manufacturers. It's horrifically expensive to start production.
but it won’t make the money people happy
"The money people" is Google which is bankrolling Firefox so that it won't have to divest Chrome under monopoly laws.
opt-out
Not two months ago I was downvoted to oblivion on this community when arguing with someone who claimed that any feature being opt-out is bloat and dark patterns.
Heh, good one. Just think about it for a second - what would then Nintendo do with their whole office building full of lawyers?
If you actually read his github you would know that there is a different version of the responsible component between the recovery environment and an installation. Only the RE has the issue.
I know. It was mentioned in the article. It's precisely why I said:
Another possibility is that they have two separate builds fro BitLocker, and the one used in WinRE is vulnerable which they missed.
Microsoft is the developer of the vulnerable bitlocker package and the ones who chose to ship it.
... one guy claims.
Another possibility is that they have two separate builds fro BitLocker, and the one used in WinRE is vulnerable which they missed.
We don't have enough information to clearly state that they did this on purpose.
We can know for FOSS software. You are treating uknownable as being less than the known bugs in Foss software. That’s dishonest, lad.
Again, read up about the XZ Utils vulnerability. We technically can know, but we don't know, which was a statement by the guy responsible for package. It's not dishonest, it's a statement of fact.
I wish you all the luck in regaining a bit of happiness in life, so that you can stop with this insane "us vs them" bullshit. It's unhealthy, mate.
Microsoft shipping a vulnerable version of the recovery environment. It is the ‘exploit’.
Red Hat and Canonical shipped a vulnerable version of SSH, the thing was caught basically hours before hitting all devices around the world.
Should Red Hat and Canonical be now considered hostile as much as MS is?
You select people who will remain complicit till they have a grievance against you. Even if they don’t and talked for moral reasons do you think they would not been fired for it?
I can only answer by saying this: I wish you luck in the job market and hope you'll eventually find an employer you don't assume to be a hostile entity towards you.
Who knows. How many more went through at closed source software a limited amount of people can test in the same way?
This is the equivalent of "prove that God doesn't exist". We can't know because they haven't been found, mate.
Yeah, that's kind of the exact opposite of the point I was making, but you do you.
Guys, just FYI - other adblocks still work. I'm using Ghostery on Vivaldi (Chromium-based) and it works perfectly fine, including blocking ads during YouTube videos.
No idea why uBlock specifically is being blocked, but it's not like you can't have an ad-blocker anymore.