

Some carriers do, some never did, and some did but gave up. In the end if they want wide deliverability they’ll have to connect to Google’s hubs (servers).
It is annoying that Google doesn’t provide an API for RCS as they do for SMS and MMS.


Some carriers do, some never did, and some did but gave up. In the end if they want wide deliverability they’ll have to connect to Google’s hubs (servers).
It is annoying that Google doesn’t provide an API for RCS as they do for SMS and MMS.


Be sure to use an online type that always powers the output via the batteries, rather than a backup type the switches to battery after the input looks bad.


Choice? I don’t use one but that’s due to never exposing ports that don’t need to be. Some that do that would still want one to provide “belt and suspenders”. Others want a specific one vs another primarily due to the software they use, that others do not. Given how trivial it is to install one does it really matter? I’m fine if they do as long as it is easy to remove, i.e., not a critical system/global dependency. I always install and remove some anyway, don’t you?
It’s wonderful but can be less complete or even missing typically due to settings (e.g., security), the environment (e.g., a container), or both.
Ditto VPN vulnerabilities. Belt and suspenders can help though if a remote is compromised likely all the things it uses will be, if not immediately then eventually.
And Samsung gave up.