At least you’re not using Azure Devops boards, Service Now or Basecamp. Those are all worse in my opinion. I miss Jira.
Last time I checked, it was broken for years already. It’s been a while though. edit: Confirmed: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ Only basic/device attestation is working.
As far as I’m aware, there are no work-arounds that allow for circumventing the Play Integrity API. Probably because you cannot avoid the involvement of a Google backend API that is accessed by the app’s backend. It works like this: Play Services hands a token to the app, the app sends it to the app backend, and then the app backend lets a Google backend verify the token, which results in a verdict. You cannot manipulate the token.
More specifically, Play Integrity API will fail on the Play Service integrity check. If I recall correctly, this is why Google Pay won’t work on GrapheneOS.
Some banks require the app to be used as second factor to log into their website.
The main problem with case-insensitive is that software sometimes is lazily developed: If a file is named “File.txt” and a program opens “file.txt”, then on a case-insensitive file system it will work fine. If you then format your drive to case-sensitive, the same software now fails to load the file. Source: tried case-sensitive filesystem on macOS some years ago.
It can also be due to unsafe charging (over-voltage) or unsafe discharging (over-current, generating too much heat). The actual fire doesn’t necessarily happen immediately during charging/discharging.
Incorporates 3rd-party DRM: EA on-line activation and Origin client software installation and background use required
Requires 3rd-Party Account: EA Account (Supports Linking to Steam Account)
Seems like another cursed EA game with built-in spyware.
My Steelseries Prime Wireless only has basic functionality working. I could run the software via Wine or VM (don’t remember) but it didn’t remember the settings after a power cycle of the mouse or the PC (also don’t remember).
That’s incorrect. At least as a generalization. For example: In The Netherlands, you do not own the airspace above your property. The EU laws for drones do state that you can’t just film people without permission, though. Operators of camera drones also need to register and get an operator id.
The scanning is done on your device. You could theoretically only overload the CSAM reporting feature if such a thing will exist.
If a messaging service is non-compliant, the government could theoretically take action with court orders against domain owners, server owners or pursue anyone hosting a node in case of a distributed setup. In a worse case scenario, they might instruct ISPs via court orders to block these services (e.g. The Pirate Bay in some countries)
It’s literally in the article: They want to use client-side scanning. The client already has the data decrypted. This is much like what Apple wanted to introduce with CSAM scanning a while back. It’s a backdoor in each client and it’s a matter of time until it will be abused by malicious entities.
Have an upvote. I’d pay double what Affinity is currently asking to have their products on Linux. Gimp is the opposite of intuitive.
Regarding gaslighting: See Apple’s response on the CSAM backdoor shit show. All the critics were wrong, including the various advocacy groups.
Users can mark videos and submit that content. Users can vote on other users’ marking of content. It won’t work if YT streams the ads in if they randomly change the timestamp at which the ad(s) start.
Not all of it though. Like JST plugs, barrel connectors, breadboard pin spacing, etc.
If a driver doesn't behave properly, the things that are built on top of it won't work properly either. When that misbehaving driver is not open source, you're at the mercy of the vendor.. It's common knowledge for over a decade that nVidia drivers are problematic with Linux - especially on laptops. Bad drivers are entirely nVidia's fault.
I've been running Wayland with Intel graphics on my laptop and my desktop runs a Radeon. I've had 0 Wayland issues in the past years.
I think it’s roughly 2 hours at 60fps, but I don’t know for sure because I have mainly been playing with power connected.