this will affect 300 people heavily, and the other 99 % will just create an account then lol
this will affect 300 people heavily, and the other 99 % will just create an account then lol
idk tbh, SafetyNet / Play Integrity have existed for a while
Kinda makes sense. A paid app on Google Play is a license to download the .apk file(s). Then a user could make copies, and without DRM, it’d be the same situation as with copyrighted movies and whatnot.
I’m not saying I support them, it’s just that they are like this for a reason
Maybe everyone was just OK with mobile devices being locked down heavily from the start, and now it’s more or less the same level for most
Is the bootloader unlocking requirement that FRP is not triggered a hard one or just because the settings screen isn’t (or shouldn’t) be reachable? Now that OEM unlocking and FRP aren’t tied together anymore, it doesn’t seem like a hard one
This could still be bypassed by flashing a new OS that deliberately messes up the userdata wipe-persisting secrets. Well idk if there’s a way to prevent that, but I guess really needy and tech-savvy people could recover lost devices that way
Looks like they “just” have to stop signing in with a Google account, and may have to enable adb and install apps using it / e.g. Shizuku
cunny has been a disaster for mankind
jokes on you one of my not so much into linux friends had it and his setup kept breaking, now he’s about to install fedora
i like disabling apps I rarely use but still need from time to time, like Spotify
boobs
Windows is king at being inconsistent 🔥
If only they had trained advanced users to use the CLI that would never change unlike the GUI
I bet they at most remove control.exe or make it open the Settings app, but still allow launching old vendor .cpl items just like they already can be opened in Control Panel.
sometime ago I had my home directory managed by systemd-homed
on Fedora (before 38 even afaik). the SELinux policy wasn’t configured properly for it though, so I had to keep setting it to permissive mode. for some stupid reason I remember running the command to do that on every. single. boot. lol
yet another reason to use sd-boot?
Holy hell, does every Windows 11 device require touch-based input soon or what?
Why not fork the latest CE?
anyone know how intel’s microcode update policy is in comparison to AMD’s?
there’s AVIF and AV1 extensions by Microsoft itself on their store afaik…
early boot stages?