You don't, there's privacy respecting ways of delivering notifications in android.
Also, a 24/7 connection to a server isn't nearly as bad as you might think.
The connection isn't active the whole time, it only uses any significant amount of battery if there's actually data being sent or received. You likely already have quite a few of them anyway, how do you think systems normally listen for push notifications?
Besides all that, I read in other comments that the privacy issue was the device id firebase needs. Obviously apple also needs some kind of device id, otherwise how do they know where the notifications are going?
Did some searching, yup apple also needs a unique identifier:
When it’s time to send a notification, you generate a request that contains the notification data and a unique identifier for the user’s device.
Pretty sure both windows and macos allow programs to interrupt shutdown, usually if there's any unsaved documents open. I quite like that feature actually, if it's used correctly anyway.
uh, no? on smartphones, yes, but not on computers.
That's not true. Most operating systems at least have filesystem permissions, and on a lot of Linux distros you additionally get AppArmor or PolKit to further restrict what files a program can read/write.
While very useful, it's not exactly the same as connecting straight to your WiFi. Iirc your android device will act as an additional nat and firewall, which can make it more difficult connecting to the device behind it from devices connected to the regular network, and vice versa.
I have never had a suspicious transaction, because the way payments work here (NL) they always need to be authorised, and recurring payments require a different authorisation that you can of course always cancel. You can't just take money by knowing the card number and cvv (which we also don't have (yet)).
Well to be fair, on my pixel at least, those are literally the same setting. Which it actually is just depends on if you're currently on WiFi or not. Kinda Google's fault for labelling it like that.
It's right there under the header