On a normal unmodified phone you have to manually confirm each app you want to install. so no auto-updates in the background etc.

Background app updates are possible since Android 12, Fdroid just took two years to implement the new API (and you have to do a fresh install of the apps - apps already installed using the old API still require confirmation on each update). There is still friction on the initial install though.

This is the a model, it won't have optical zoom either way.

It's easy to dismiss as an ad. I did, too.

Well, Vivaldi's built-in in adblock apparently agrees with this categorization. The video shows up if I disable it. Lol

Where's the article?

But it's a design for designs - it tells you how to design your own UIs, it doesn't dictate what for example a calculator app should look like. You can follow Material Design and still end up with a terrible UI design.

Surely that's enough for some distinction, right?

The Quick Share option missing is weird - Nearby Share/Quick Share is supposed to be available on every Android 6 or newer device since roughly 2020. And it's supposed to be able to automatically figure out a reasonable way to connect the devices (LAN if they are in the same network, Bluetooth or WiFi Direct otherwise).

xrandr is Xorg only, it doesn't work with Wayland. You should be able to make SDDM use your Plasma display configuration - https://wiki.archlinux.org/title/SDDM#Match_Plasma_display_configuration

No clue if that's going to fix your issues, but at least it's supposed to work with Wayland.

But "open source" doesn't even mean that you can reproduce it or use it for free.

You're thinking of source-available licenses. Open source has a clear and widely accepted definition that requires a certain level of freedom. You're free to ignore this definition, but you can't expect the rest of the world to do the same.

To be clear, open source allows for only providing access to paying customers, but those paying customers are then free to use and distribute their copies without any further payment. Then it wouldn't be open source anymore.

Or is there any functional difference between the two methods?

Can't test right now, but I have a strong suspicion you will have trouble getting IP broadcast to work. Normally broadcast address is calculated by setting all bits after the network prefix to 1, but your computer believes to be in a /32 "network". It won't broadcast over routes that are not part of its network.

And even if you calculate the broadcast address successfully (maybe the software you use has /24 hardcoded for whatever reason), no computer configured with a /32 address will receive it - 192.168.0.255 is not within the 192.168.0.1/32 network, so it will probably get forwarded according to your routes if you have forwarding enabled (except it shouldn't in this case with one network interface, because you never send packets back the way they came from)

It is, and it's the reason Pixel 6 and 7 series had so many issues with poor battery life and weak modem. Although it appears that the third generation Tensor CPUs in Pixel 8 have major improvements on both of these pain points.

Still, that probably brings Pixel 8 only to the cheap-ish midrange standard when it comes to cell signal, as the Pixel 7 phones were atrocious and 6s were apparently even worse.

No, kernel immediately stops execution of all normal processes once it gets into a kernel panic, and there's no way for processes to hook into this functionality. It is intended to be the emergency stop state when the kernel realizes it doesn't know what's going on and it would be dangerous to continue executing. So it does the bare minimum to report the issue and then stops even its own execution.

There's also a softer variant of the kernel panic called kernel oops that should let the user choose to continue if they think the risk of data corruption doesn't outweigh losing all data currently in memory. But just like the kernel panic, it is handled completely inside the kernel and userspace is frozen until the user chooses to continue.

This is intended for situations where systemd runs into an unrecoverable issue while booting (for example you have misconfigured fstab and a required disk is missing). Without this, you just get thrown into the terminal with some error messages that might not make much sense to you if you don't have a decent understanding of Linux. Now, you get a more newbie friendly message and a QR code that should bring you somewhere you can learn more about possible causes and troubleshooting steps.

I'd love it too with my 7a, but there's no way Google does something nice just 'cause. They've already sold the phones with a shorter support window and they gain nothing by releasing more updates for those devices.