this post was submitted on 16 Nov 2023
145 points (100.0% liked)

Android

407 readers
10 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
 

It's happening!!!

top 24 comments
sorted by: hot top controversial new old
[–] jcarax 20 points 11 months ago (2 children)

This would be great if I could actually use it in AOSP without Google's own app, and view/reply to RCS conversations on my laptop using a 3rd party application. Open the APIs, Google, or you're just blowing hot air.

[–] smileyhead@discuss.tchncs.de 5 points 11 months ago* (last edited 11 months ago) (1 children)

+1 And why XMPP was always a better answer.

[–] jcarax 2 points 11 months ago

Yeah, I have a lot of mixed feelings about it, but I'm tending towards some forced adherence to standards. Or at least interoperability through open federation.

[–] limerod@reddthat.com 2 points 11 months ago (1 children)

The standard RCS lacks e2e encryption. You wouldn't have been able to use other clients with the google messages app either way even if they were developed.

[–] jcarax 1 points 11 months ago

That's why we need them to open up the APIs in the short term, but the long term goal should be to get the Universal Profile advanced, and move away from a Google-centric implementation.

Which, to be fair, Google really did seem to want carriers implementing their own interoperable RCS solutions. But they needed shit to be done, so they ended up doing it themselves.

[–] lemmyvore@feddit.nl 20 points 11 months ago* (last edited 11 months ago) (3 children)

It's going to be irrelevant. It will still be separate from iMessage. Different bubbles will still exist. People who aren't using SMS now (Europe) will continue to not use RCS either. And Apple's implementation of RCS will be independent from Goggle's and not 100% compatible.

In fact I suspect the whole thing is an attempt to skirt the upcoming EU interconnection regulations. Apple thinks that if they say "look we've implemented RCS and it's technically interoperable with other RCS implementations" they'll get a pass β€” or be able to assign blame on other vendors for not interconnecting with them and drag the whole thing for a few more years.

[–] NoDoy@lemmy.ml 12 points 11 months ago* (last edited 11 months ago) (1 children)

Glad that you emphasized Europe. Here in the states where iMessage is dominant, it'll make a difference.

At the end of the day it's not a bad thing. I'm also waiting for details with compatibility to be ironed out, but it's a start.

Just surprised at the whole negative energy with this announcement considering this was a "when pigs fly" or "when hell freezes over" sorta thing. Again, it's a start and hopefully Google opens it up (even if forcibly by the EU) down the road.

[–] lemmyvore@feddit.nl 3 points 11 months ago

I'm just extremely skeptical of anything that looks too good to be true coming from any of the incumbent tech giants. Call me cynical.

[–] Auli@lemmy.ca 6 points 11 months ago (1 children)

I care. Switched to iPhone and RCS is the one thing I miss.

[–] NoDoy@lemmy.ml 2 points 11 months ago

Exactly. It's in no way a bad thing for anyone. We'll see the way that it's implemented. It's the first step. r/Android is rearing its head here. Let's enjoy this for the moment

load more comments (1 replies)
[–] aiman@lemdro.id 13 points 11 months ago (2 children)

I have faith in Apple, it'll be difficult but they'll find a way to do this that still maintains all the toxicity towards green bubbles that they've worked so hard to cultivate.

[–] Flax_vert@feddit.uk 2 points 11 months ago

They are literally keeping the green bubbles for RCS users lmao

load more comments (1 replies)
[–] JackGreenEarth@lemm.ee 8 points 11 months ago (3 children)

Are there any FOSS RCS apps? Should this be the 'open' standard the EU are enforcing?

[–] lemmyvore@feddit.nl 13 points 11 months ago* (last edited 11 months ago) (1 children)

There aren't any because there's no point. And no, I hope this won't be the standard.

There are two things called "RCS": there's a theoretical specification; and exactly one implementation that has managed to get any real traction, and that's purely because it's pushed by Google.

The RCS spec was attempted by various companies and all implementations died when they figured out they'd have to make them compatible and open their servers to each other. Even if they wanted to it would be a mess.

SMS succeeded because it doesn't need servers, it's just pieces of text being sent around.

Google is the only one still pushing their RCS because they figure if they tie their version of it into Android they will own the messaging on Android forever. They don't want interoperability either.

If Google gets their way and their RCS becomes the EU standard it will lock the EU into a proprietary platform from one of the most vile data predators in the world.

There's no point in making a FOSS implementation of RCS because the spec is highly dependent on who runs the servers. The only way it would make sense is if the EU would dictate a spec and force everybody to follow it and open their servers. In that take on things FOSS would be ideal.

[–] skullgiver@popplesburger.hilciferous.nl 1 points 11 months ago* (last edited 11 months ago) (1 children)

[This comment has been deleted by an automated system]

[–] lemmyvore@feddit.nl 1 points 11 months ago (1 children)

SMS only transits the telco infrastructure, it doesn't need servers in the client-servers sense, RCS does. Not only that but RCS needs them because it includes hosting for things like images and videos that are sent in messages.

I don't think Google will allow anybody to partake in "their" RCS, the least of all custom ROMS. They will make it another thing like SafetyNet, designed to maintain their own control.

load more comments (1 replies)
[–] kaidelorenzo@lemmy.today 6 points 11 months ago

would much prefer matrix as the standard

[–] dandroid@dandroid.app 2 points 11 months ago

If they did, it wouldn't work on Android. There's no user-level API. So only apps that come bundled with the phone can use the API.

[–] Swarfega@lemm.ee 8 points 11 months ago* (last edited 11 months ago) (1 children)

I have no doubts it will be implemented in a way that still benefits Apple and its ecosystem. Also to help their cause to keep iMessage locked into Apple devices with that EU ruling. Still, this is great news.

[–] rikonium@discuss.tchncs.de 4 points 11 months ago* (last edited 11 months ago)

I don't think Apple will need (or want) to do anything "malicious" since Apple is implementing RCS the standard which between the carriers and Google mismanaging and fragmenting messaging for years - see: X carrier phones can only send RCS messages to X carrier phones, Google's implementation is not the RCS standard and is partially proprietary - it'll take a while to get S.S. RCS, The Standard steered right.

I hope Apple's involvement is ironically a kick in the butt to get everyone on the same page and get a standard rather than the current "Google iMessage" solution.

Edit: Typo

[–] SuperSpaceFan@lemm.ee 3 points 11 months ago* (last edited 11 months ago) (1 children)

Long overdue, but this will be a benefit for all.

load more comments (1 replies)
[–] possiblylinux127@lemmy.zip 2 points 11 months ago

That sucks. I was hoping for a open standard that wasn't dependent on Google

[–] smileyhead@discuss.tchncs.de 2 points 11 months ago

Now we wait another 10 years for Apple to support third-party RCS apps I guess?

[–] vamp07@lemm.ee 1 points 11 months ago

I bet they do some thing like make it optional on the iPhone and the user needs to turn that setting on to get RCS. Obviously most users don’t care and will never look. οΏΌ