82
submitted 1 week ago by neme@lemm.ee to c/android@lemdro.id
top 18 comments
sorted by: hot top controversial new old
[-] unknowing8343@discuss.tchncs.de 22 points 1 week ago

Google’s work could encourage the adoption of MLS, much as it did with RCS.

How can you say what Google has done is "encouraging RCS"? They literally monopolised it.

[-] skullgiver@popplesburger.hilciferous.nl 9 points 1 week ago* (last edited 1 week ago)

RCS has been around since the early 2010s and absolutely nobody used it until Google did. You had to download carrier specific apps, which then only worked with other people who downloaded their carrier specific apps, because nobody bothered to write unofficial ones. Carriers have been shutting down their RCS servers for years because their customers didn't care. Google is the only reason anyone uses RCS, if it weren't for them we'd still be on SMS/MMS.

[-] BearOfaTime@lemm.ee 4 points 1 week ago

RCS has been around since 2010

15 years and it's still problematic? Sounds like something that just needs to be let go.

Stop pushing this garbage that's tied to hardware/sim/phone number on us. What value is that for the end user, seriously? Why would an end user today want a messenger that's tied to a phone number?

Fully-functional, cross-platform, network-based, open-source instant messaging has been available (even on mobile) since 2009, maybe earlier.

What I always ask about RCS: who benefits today from a messaging system that's hard-bound to a phone number?

The value for the end user, the way Apple and Google do it, is that it works on every phone. It was always intended to be the next generation of MMS messaging. RCS, as designed, never had companies like Google run their own servers, but Google had to because many carriers never bothered to set up RCS in the first place.

Who benefits today? Everyone sharing chat groups with iMessage people. I avoid iMessage but millions of people are stuck with text messaging or ostracised for breaking group messaging (because SMS and MMS are terrible).

Furthermore, RCS isn't just text messaging. The standard also contains digital payments and video calls. It's an open (to carriers) alternative to iMessage that has features ready to go that Signal doesn't even implement yet.

Communication is literally what phone numbers are for.

[-] unknowing8343@discuss.tchncs.de 4 points 1 week ago

What??

The RCS API on Android is only available to Google Messages and whomever Google allows (like Samsung Messages when they existed). This is the reality.

If the RCS API was truly open there would be an explosion of FOSS alternatives to Google's spyware.

[-] Illuminostro@lemmy.world -1 points 6 days ago

You don't know what you're talking about. Samsung, Verizon, ATT, and who knows who else all had their own proprietary RCS apps that were not compatible to any others.

[-] iiGxC@slrpnk.net 14 points 1 week ago

Except it's not all messaging apps cause google messages is the only android messaging app with rcs support

[-] Blisterexe@lemmy.zip 10 points 1 week ago

Except it is because the article is about mls and not rcs

[-] possiblylinux127@lemmy.zip 3 points 1 week ago

Do we have any reason to think that Google would want to not collect data?

[-] Blisterexe@lemmy.zip 3 points 1 week ago* (last edited 1 week ago)

The idea of standards like that is that the company cant collect data, obviously that wont stop google.

But the nice thing is that it means you can talk to people who refuse to install signal or matrix from those apps, once the protocol is established

For those who thought this was a serious question:

No

[-] christophski@feddit.uk 13 points 1 week ago

Does this protocol actually mean arbitrary cross-app messaging or would that require the app developers to coordinate in some way?

MLS is just the message encryption part, the MIMI working group is working on a standard that would also open up cross app messaging, using MLS for security. Of course, app developers would need to implement that first. Given the EU is forcing some of these companies to open up their services, it's possible app developers will choose MLS to do this (for EU citizens). Meta itself has several people in the MIMI working group, for instance.

[-] BearOfaTime@lemm.ee 3 points 1 week ago

They're working on something other protocols have had for years. 🤦🏼‍♂️

Yes, because other federated protocols (email, XMPP, Matrix) don't have the same features modern messengers have and don't interoperate with other protocols well. I don't think XMPP OTR or OMEMO are RFC standards either, they're just extensions on top of XMPP.

Some XMPP people are part of the conversation and Matrix is already moving to adopting MLS, so clearly "just use x" wasn't an option, even for them.

[-] christophski@feddit.uk 1 points 1 week ago

I doubt it will ever happen but it would be amazing if I could just have one messaging app and message whomever I want on whatever platform I wanted, without having to using some crazy bridges.

[-] possiblylinux127@lemmy.zip -3 points 1 week ago

How about we just get people to switch apps

[-] BearOfaTime@lemm.ee -2 points 1 week ago

With you.

Fuck RCS. It's trash. Who benefits from a messenger, in the 21st century, that's tied to a phone number?

this post was submitted on 05 Jul 2024
82 points (97.7% liked)

Android

16946 readers
230 users here now

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


founded 1 year ago
MODERATORS