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.

A trigger warning on this post for Android devs would’ve been nice.

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.

“Deep Rock Galactic: Survivor” has been a blast so far. I’m about 12 hours in.

I’m running DualSense on Arch without issues. It even uses the touch pad for mouse movements when not in-game (Steam).

Make sure to check the docs if you aren’t using Gnome: https://wiki.archlinux.org/title/Gamepad.

My only complaint is the atrocious battery life, but that’s not a Linux issue.

The existence of ArchWiki and the Arch User Respository (AUR). And rolling releases, if that’s your thing.

In the early days they would quietly take all your contact info on your phone and send emails in your name that made it seem like you were reaching out to those contacts. Something like “(your name) is trying to reach you on LinkedIn”.

Back then, Android didn’t have app permissions like it does now where you have to ask the user explicit permission for access to certain data. It would only show up on the very first app install and only if you’d be looking for that.

I cancelled my account back then and never looked back.

No issues here with Gnome via Arch on a Framework 13. At 150% scaled if recall correctly.

My only regret for picking team red is that DaVinci Resolve doesn’t support hardware encoding.

why doesnt GNOME have a maximize button

Probably because you can double-click the window ‘bar’ to achieve the same.

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).

Great job! Is there a way to donate to the project?

Internal dash cam video and/or audio.

It’s probably an SSD for a Fusion Drive setup: https://en.m.wikipedia.org/wiki/Fusion_Drive

It seems to check out for iMac in 2019.

From StackOverflow:

Switches will send packets to all interfaces when using broadcasts or under extreme conditions (full MAC Address Table). This can lead to duplication if there is a loop between two or more switches and if the Spanning Tree Protocol is not used. So the answer is rarely.

https://stackoverflow.com/questions/9196791/duplicate-udp-packets-how-often-it-happens#9220574