ByteWelder

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.

Speaking of which: I’m cooking up an app platform for this purpose on ESP32: https://github.com/ByteWelder/Tactility

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.

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.

Besides the other mentioned reasons: exposure through the app store can be a motivator too.

It’s likely mostly Google and a bit of Amazon: Casting support requires Google Play Services installed on the device. Google Play Services is only allowed to be used (as in: allowed by Google) if the Android device also comes with many other Google apps. Amazon probably doesn’t want their device to become a Google-centric device. That’s likely the reason.