134 points

I don’t understand why the article writes that iMessage is the only way for encrypted messaging between Android and iOS. I can thing of several off the top of my head:

  • Matrix
  • Signal
  • WhatsApp
  • Facebook Messanger (very soon)
  • Threema
  • Telegram
  • Viber
  • Line
  • Skype

And there are surly more …

permalink
report
reply
57 points
*

cause of lazy iOS users that can’t be bothered to use anything else

permalink
report
parent
reply
-14 points

Then why are we shaming Apple and not the iOS users? I think Apple is totally reasonable here.

permalink
report
parent
reply
40 points

Apple’s biggest crimes here are creating a proprietary platform with an exclusive protocol and making it the default messaging protocol on their devices. None of this is really new, though. All that shit is common. We need Signal or Matrix to improve in user-friendliness and even do some marketing to the point where they become viable solutions.

permalink
report
parent
reply
7 points

Message works, it’s seamless and does a good job. Sure I’ll change to something else if I need to send images or group chat with Android uses, but in the UK that generally means WhatsApp, which I am definitely not keen on.

permalink
report
parent
reply
-3 points

There is absolutely nothing reasonable with using an inferior and outdated standard compared to what literally everybody else uses.

permalink
report
parent
reply
31 points
*

Most of those are proprietary. My list:

  • Matrix
  • Session
  • Signal and signal clients
  • Simplex Chat
  • Jami
  • Briar (android only)
  • Nextcloud talk (needs nextcloud)
  • probably a lot more
permalink
report
parent
reply
9 points

telegram is not encrypted by default, and does its best to make you forget to enable it for each individual contact. if you want to do a group chat, you’re out of luck.

Telegram is only (partially) secure for pedantic power users, which most people aren’t.

permalink
report
parent
reply
-2 points

telegram is encrypted, but not end to end encrypted by default

permalink
report
parent
reply
9 points
*

so, relative to pretty much all other messaging services, it might as well not be.

You’re saying “by default not everyone can read your messages, only you, the recipient, telegram themselves and anyone who they might decide to share them with, with neither your consent, nor knowledge”

When compared to “nobody except you and the recipient” that becomes effectively equivalent to “nothing”.

also, not end-to-end ever when it comes to group chats

permalink
report
parent
reply
5 points

Technically, yes, this is a solution.

Socially, no. This is not a solution. People are just too lazy.

permalink
report
parent
reply
4 points

I assume that if people are too lazy to switch to a solution which works for every one then they are not very interested in talking to you anyway.

permalink
report
parent
reply
3 points
*

Except it’s not a solution that works for everyone. It’s 9 solutions. If it were one it would be a lot easier.

7 once you take out the ones owned by Facebook.

permalink
report
parent
reply
2 points

XMPP

permalink
report
parent
reply
57 points

Apple protecting it’s precious garden.

permalink
report
reply
20 points

Oh look, a weed slipped through.

permalink
report
parent
reply
3 points

Must eradicate it.

For the safety and security of our users!

permalink
report
parent
reply
2 points
2 points

takes out flame thrower

permalink
report
parent
reply
53 points

If only there was a secure and open standard that would work on any platform, regardless of ecosystem…

Oh well!

permalink
report
reply
24 points

If you are talking about RCS - the encryption aspect is a google proprietary extension

permalink
report
parent
reply
15 points

Probably meant Matrix.

permalink
report
parent
reply
12 points

Or Signal.

permalink
report
parent
reply
5 points

True, but the Apple RCS announcement said that they were going to work with the GSM association and google to build it into the base spec

permalink
report
parent
reply
1 point
*

Thought RCS used the Signal Protocol?

Edit for source: Technical paper: Messages end-to-end encryption

permalink
report
parent
reply
1 point

It’s not natively supported by the base RCS standard, in the section at the end of the paper in the section titled “Third Party RCS Clients” Google explains that they’ve built the e2ee their Messages app themselves, (on top of standard RCS).

A developer has to use Google’s implementation specifically in order to send and recieve e2ee messages to Google’s Messages app (and Samsung Messages who also implemented this recently)

Although the e2ee implementation is using the Signal protocol under the hood, it’s for message content only - this is what is transmitted in cleartext (taken from the paper)

  • Phone numbers of senders and recipients
  • Timestamps of the messages
  • IP addresses or other connection information
  • Sender and recipient’s mobile carriers
  • SIP, MSRP, or CPIM headers, such as User-Agent strings which may contain device manufacturers and models
  • Whether the message has an attachment
  • The URL on content server where the attachment is stored
  • Approximated size of messages, or exact size of attachments

Without using this implementation of the Signal protocol on top of RCS, the message will deliver to the contact’s phone, but shows up as unencrypted garbled text

That is a very useful resource though, never knew there was a paper available on the implementation. Saving 😁

permalink
report
parent
reply
10 points

Signal

permalink
report
parent
reply
5 points

The problem is actually getting people to use it since they’re all too busy arguing over the color of a message

permalink
report
parent
reply
43 points

We took steps to protect or users by forcing them to communicate to Android phones using unencrypted channels. After all, those peasants are not iPhone users, they deserve to be spied.

permalink
report
reply
43 points

our walled garden*

permalink
report
reply
31 points

Aside from the obvious reasons of competition, Beeper also used Apples infrastructure, that Beeper was then going to monetize. Not too surprising they shut it down.

permalink
report
parent
reply
-1 points

No, they were charging money as they had their own APN to BPN bridge. Plus the usual cost of development and more.

permalink
report
parent
reply
4 points

To keep Beeper Mini running, Beeper uses a Beeper Push Notification (BPN) service to connect to Apple’s servers and notify you of new messages.

And it uses Apples gateway service for setup.

arstechnica.com/gadgets/2023/12/beeper-mini-on-android-claims-to-have-reverse-engineered-imessage-compatibility

permalink
report
parent
reply
-4 points
Deleted by creator
permalink
report
parent
reply
9 points

Apple already knows that iMessage, alone, is a huge selling point for their iPhones. They held out for a few years keeping iTunes away from the rest of us before finally giving in, but I very much doubt that they’re going to open up iMessage any time soon. It’s pretty much the only thing that keeps iPhone users in their ecosystem anymore.

permalink
report
parent
reply
3 points

That’s true, but it would be more Applelike to develop their own app. They obviously know how to do it, then they could have 100% of the profits and not have to deal with a partner. But Tim Cook said they re not interested in doing anything like that.

permalink
report
parent
reply
3 points

our shareholders*

permalink
report
parent
reply

Android

!android@lemdro.id

Create post

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it’s in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it’s not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website’s name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don’t post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities
Lemmy App List
Chat and More

Community stats

  • 2.5K

    Monthly active users

  • 2.7K

    Posts

  • 34K

    Comments