It’s because doi g things on site requires CapEx, which then increases your tax liability.
By going SaaS, you offload the entirety of risk.
The problem is the morons who sign these contracts are fucking clueless about ensuring the liability is strong.
This isn’t about restrictiveness - it’s a problem of RCS being ass-backwards garbage.
This isn’t a an Android issue, it’s a Google and cell provider issue. And that RCS (like SMS), are based on ancient technology/concepts, and both need to just die.
SMS is based on the physical architecture of cellular networks, and has no error handling whatsoever - it’s a Best Effort transmission.
RCS uses a hardware-bound ID, something we decided was a Bad Idea 40 years ago, and is wholly dependent on cell provider support.
We have a protocol, TCP-IP, that eliminates all these issues. It’s been the networking standard since the mid-90’s when even Netware decided it was a superior solution to IPX/SPX. It’s wholly hardware independent (it’s not tied to a physical device’s ID), so you can transmit/receive from any device without having to update everyone else that this is your new device.
We have numerous IP-based instant messaging systems today, with one in particular (XMPP) being open, flexible, extensible.
There’s no use for an archaic solution like RCS, except keeping your messaging in a system controlled by Google and carriers.
No, it isn’t massive for privacy.
It’s hardware-bound, meaning at a minimum who you’re communicating with and when will always be known, today and in the future.
And I haven’t seen anything showing that it has Perfect Forward Secrecy, so all someone has to do is save the messages and if it’s ever cracked, they’ll know exactly what you said, when, and which device.
It’s a feel good to make people think something is being done, when it’s far from “good”.
BTW, hardware-bound ID was determined to be a bad idea 40 years ago. Even SPX moved away from it in the 90’s.
Now that’s just mean!
(Enjoy my upvote, haha)
There’s essentially Lineage (formerly Cyanogen, or a fork of it) and Graphene.
Ignore /e/ OS - it’s Lineage with their crap on it.
Go read about those two.
RCS is so backwards it’s not a step in the right direction.
It’s hardware bound - which tells me they want definite tracking capability.
Wow, that page has so much crap on it that it crashes because I block the crap.
Stopped using reddit years ago.
Never once used WhatsApp, and refuse to.
Same with a bunch of other social media sites.
YouTube - only use it to download high quality Vida using other tools, like Grayjay, Newpipe, and YT-DL.
Hahahaha, thanks for that.
A brilliant joke that will last forever!
My pronouns are fuck you AI
Worth quoting
I’m amazed that helicopter had the lift capability for something like this.
That thing is pretty big, so would still have some weight regardless of the material.
You’re overlooking 500 people in congress, their hangers-on, governors, their hangers-on, etc.
Politics is the nature of groups of people.
Al you always completely honest with everyone you talk to?
Read Machiavelli. This is all just human nature at scale.
Are you me? Lol
Even driving cross-country when I can get to cruise it’s hard to make a difference.
I can make a significant dent in time, but it’s over an 8 hour drive with no traffic. Then I can cut perhaps an hour if I’m doing 10 mph over consistently.
But this only works if you’re on a quiet road, say a “blue highway” in the midwest/western US, not an interstate.
I forget the rule or why, but if memory serves Beemer is car, Bimmer is bike.
Or the reverse. I don’t know why.
BMW - well there’s your problem!
I’ve driven like an old person since forever.
Done the math too many times - you can’t out-maneuver traffic or time.
Seems like this would be a sign to get off such a system
The problem is CapEx vs OpEx.