If they put the ads in the stream, you can just fast-forward. I don’t think it’ll work out well for Google.

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.

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.

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.

Not all of it though. Like JST plugs, barrel connectors, breadboard pin spacing, etc.

I found kdenlive terrible. DaVinci Resolve is much better, but it’s closed source and has some limitations in terms of hardware encoding support (nvidia only).

I looked it up and it seems to be the 2020 version. I recently got it with a Steam Deck that I bought second hand.