- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
I’ve been working really hard to research and rank messaging apps by their privacy. The more green boxes the better.
I plan to turn PrivacySpreadsheet.com into a place for privacy data on everything from cars to video games. It’s all open source too on GitHub.
Not trying to advertise, I just put a lot of time into researching all this, and I want to share it since I think others could benefit.
The issue with me is ease of use to use with other people. I’ve tried Matrix and Session with other tech minded people and it’s not nearly as seemless as Signal. I’m just waiting for an app that ticks all my boxes, really looking forward to Signal usernames though.
Signal really is that better replacement for WhatsApp since the functionality is identical, others would have to force people to get used to the different ui and the options.
Except Signal UI is… Not good. It feels like using a texting app.
Between the UI and dropping SMS support, I can’t get anyone to use it anymore, and people I had using it have moved on.
Dropping SMS is really frustrating - it was the big selling point I had.
I’m one of those people who thinks SMS has no place in a private messaging app. Signal is the gold standard, and enabling sms merely legitimised this incredibly non private and antiquated messaging protocol.
And gave a constant reminder to people that something better was right there.
And put things in one place.
You’re letting perfect be the enemy of good. At least with SMS support I could get people to switch to “this new texting app”, and we’d then have a proper Signal encrypted chat. And when they texted someone else, Signal would append the “you could have encryption too” signature, generating a conversation about it.
The people who moved off of Signal went back to SMS entirely. How is that better?
Huge bummer. Kind of understood why they did it but they lost a lot of people because of this.
I made the mistake of getting my family to switch to Signal. It works great for messaging, but it has other issues—beyond the typical SIM-required complaint. I hate that you have to register with a ‘primary’ device on either iOS or Android fueling that duopoly (SoL if you are on a postmarketOS or KaiOS or Capyloon phone… or just don’t want a internet-capable phone). Notifications are sent thru Google’s FSM (news 1–2 months ago that of course Apple & Google send all the metadata to the feds) & refuse to support UnifiedPush (thank goodness the Molly fork does). They’re also not too happy to support alternative clients meaning you are stuck with the shitty, resource-sucking Electron client while not having a web client or native or TUI client. And the worst cherry on top is shipping those iOS emoji to Android & Linux …eww.
Yeah not having it as a default SMS app sucks. Can’t really argue with you there. Perhaps, one could make a fork with it?? Just thought of that now.
I seriously doubt any encrypted messenger is going to support OS like KaiOS or non internet capable devices.
For unified push, just use molly.
iOS emojis…I really don’t care, Signal devs have other things to worry about.
With an FPGA or special CPU instruction set, the encryption algorithms could run on a toaster—which would give access to whatever low-spec handheld you wanted without making it chug to have strong encryption. That also still isn’t covering the future hope of a Linux phone, or someone that just wants to register an account on their laptop.
Using forks puts stress on other teams to keep up with breaking changes, & 90%+ of folks won’t be looking for forks or be willing to trust their unofficial status. I saw the code for UnifiedPush as a Mattermost plugin & it was like 50 lines or something small which is much less than the rest while allowing users to keep control of their metadata which is a big deal if you care about privacy. A fork for SMS support would encounter similar issues, & now you either need to compete with Molly or copy its featureset otherwise users have to choose, SMS or UnifiedPush. That said, I agree with the SMS situation since it was easy to convince relatives to use this new “text app” where encryption magically came to a chunk of their contact list.
Saying emoji was the most important was tongue-in-cheek, but it makes the application feel non-native (& I think Apple’s emoji are particularly ugly). You would think at least the Google set was shipped to Android, or—now hear me out—not ship emoji, don’t override the user experience, let the user’s fontconfig display the one they set. Shipping a whole font (or images) for emoji is why the application size is so bloated for a chat app.
The first two arguments I get. But the emoji argument about not shipping them at all? Yeah if this is going to be a mainstream and easy to use app then that won’t fly. My friends, family, and I all use emojis, gifs, and stickers. I’m sure many people enjoy these things as well. All that bloat.
Are you using a device without an emoji font installed on the system at all? The web works just fine without browsers shipping an emoji font.