this post was submitted on 26 Jan 2025
547 points (98.6% liked)
Fediverse
29401 readers
2027 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Their rationale was that SMS is not secure and having something not secure on their app was damaging.
In what way is it insecure? If the user was going to message someone off platform they'd still be sending them an unencrypted message anyways if they have to switch apps to SMS. If users didn't understand the distinction, that's a design failure on signal's part.
To a lot of us, SMS fallback was the killer feature signal provided.
At least with matrix, it's decentralised. If they ever try to rug pull like signal did, their users can at least choose to not update if they self-host their own instance. I'd imagine a lot of lemmings would appreciate that, considering.
It sounds like they don't want to take responsibility for that user choice or be connected to anything that happens because of that choice.
It would still be an insecure choice, even with obvious UX distinctions. It would only be a matter of time before headlines muddy the waters with "intercepted Signal messages reveal..." or "Judge rules in favor of subpeona for unencrypted Signal messages..."
That's such a poor excuse. If they really really thought it was a problem, they could obscure-gate the feature. Make it so you have to long press on the 3rd word of the ToS or something ridiculous, and share that info online.
This is a fairly common practice for potentially dangerous android features, for example. It keeps the less tech savvy audiences from accidentally impaling themselves in the foot.
Usually the vanguard of adoption for platforms like these are fairly technical users. When you start cutting the feature set that brought them to your platform, it starts the death knell for your platform. They'll go elsewhere to find a platform that respects them more, and they'll drag everyone else with them sooner or later.
When was the last time you saw android getting a severely bad rap for including ADB?