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.

What they didn’t mention is that hat guy is an Alpine user.

It seems like this might break the GDPR rules for consent:

Any element of inappropriate pressure or influence which could affect the outcome of that choice renders the consent invalid.

https://gdpr-info.eu/issues/consent/

or if the performance of a contract, including the provision of a service, is dependent on the consent despite such consent not being necessary for such performance.

https://gdpr-info.eu/recitals/no-43/

I’m not a lawyer though, so maybe a legal expert can chime in.

edit: the jury is still out it seems:

https://techcrunch.com/2023/10/03/meta-subscription-vs-consent/

My theory is that it covers dash cam recordings (video and/or audio). Some dash cameras point backwards from the back mirror, so they get a partial view from inside the car. Everyone’s assuming that Nissan is intending to collect this info, but their EULA might merely be a side-effect of dash cam data being available to technicians when they work on the car (e.g. fixing the dash cam).

Like someone else mentioned: you should be able to join meetings without an account.

That said, making an account with a custom email address will not create a microsoft mail inbox for you. Microsoft, however, will use your email address to send service-related messages. If I recall correctly, you can manage what kind of messages you want to receive, in your account settings.

The main difference is that you’d just be making a regular(free) microsoft account bound to an existing email address of your choice, as opposed to binding your domain name to a microsoft account to host your email there - which is mostly something companies do and is a paid service last time I checked.

This is partially true: Android does sandboxing, but it only gives you partial control over your apps. Firstly, certain permissions give a wider access than initially seems (e.g. media access). Secondly, not all permissions are user-manageable. For example: you cannot stop certain apps (like banking apps) to query the system for other apps you have installed.

As an experienced Android dev and former iOS dev: pushing someone to Google products is not going to improve someone’s privacy. Apple is not “good” in terms of privacy, but Google is much worse. The only real options in that area are MicroG-based Android OS-es, or fully de-googled ones. However, custom ROMs are often not problem-free though. In that case, a Pixel phone is probably still the best option.