Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: [email protected]
π‘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: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
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.
-
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.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
Now, if only Google wasn't a cunt about allowing other apps for rcs, that would be great
Imagine cross-platform RCS support built into Signal. π₯Ήπ
Man that would be nice. Could finally have it be all in one again like Google Hangouts before it was killed.
I still miss Hangouts + Voice
Same I legit think it could've been Google's actual competition to iMessage but they fumbled the bag so badly it's crazy.
Oh that'd be nice but since no more SMS in Signal I can't see it going back in (unless they reversed course?)
IIRC their point was that SMS is insecure, so they don't want people using SMS in Signal to think that this is Signal. With RCS, they could do what Apple will - be interoperable while providing extras with own platform (iMessage).
Admittedly, that doesn't sound like enough reason to reimplement SMS and RCS alone would still be kind of inconvenient.
they could go the apple route and just make sms messages an ugly color
Why not have separate apps so users can opt to install one or the other?
Why do you use two apps for SMS or iMessage now.
I don't understand. I don't do that. But I have Whatsapp, telegram, signal and discord installed, and those are all quite separate apps.
The point being, why would I want my Whatsapp install to come integrated with a whole discord client? I can already just install both, which is much easier and keeps things separate.
The point is getting adoption. Especially in the US, where people actually use iPhone, no one wants to download a second app because iMessage is 'good enough' 99% of the time.
Samsung Messages is the only other, right?
Technically anyone who makes an android device could have their own. The API is a system-level API, so any app signed with system certificates (aka, any app packaged with your phone) can use it. Any app you download from the play store can't.
Afaik, yeah
What do you think Apple will do? π
Cue several years of Google and Apple pointing at each other and shouting "see, they don't want to be compatible with us!"
RCS was an idiotic take from the start. It should've been a layer of encryption over SMS and remain otherwise stateless and platform agnostic.
But of course companies and governments don't really want encryption. So it became something that's trivially easy to subvert by each company that implements it, because it needs to pass through servers, and who controls the servers gets to be an ass about it.
It's origin came from a good place. The wireless industry, not Google, started driving the standard to retire/replace SMS/MMS. However, then the wireless industry was reduced to a duo-culture and Google decided to drive RCS after many years of carriers/manufacturers trying to do their own thing to little success.
Another route: MMS could be enhanced to have some modern features while still being backwards-compatible. The datagrams are just XML and the syntax is akin to E-Mail. Larger message sizes could be supported, while the gateways still handle resize/reformat for older device backwards compatibility. There was even a format for a few minutes in the early aughts called EMS that had some promise but it died from disuse. Message delivery confirmation has existed since GSM and CDMA.
There's even a standard for IMS video calls that has been in the 3GPP stack since the 1999 release that would've allowed universal standard video calls. Since carriers hated building data networks and consumers weren't ready for video calls, it just sat stagnant until iChat AV/FaceTime came along and popularized video calls. It's still there, it could still be used.
Somewhere along the way, standards-based universal calls, video, and messaging took a back seat to tech bros and their proprietary stacks, and governments (at least the US) were too stupid and incompetent to understand what regulation was necessary to correct this path we are now on. Hopefully the EU can continue to help fix this.
Umm what?
SMS has a very short size limit. Implementing RCS as an encryption layer on top of it would require devices to send several messages just to cover a short one-word reply. They also often come out of order so they would need to include a numbering system so the client could piece them back together.
Granted that is already how SMS works on modern devices, but the underlying protocol is woefully inept at modern messaging and completely unviable for what you're proposing.
How should media attachments work? I assume you expect that to just use encryption built on MMS? So media can come through even more compressed than basic MMS? None of the actual benefits of RCS would be possible if it was built on top of the existing ancient standards.
Encrypting doesn't necessarily boost the size of the message. You can also use compression very effectively since it's mostly text.
You don't need to also solve media hosting, you can just leave it be links like it is now. Just adding encryption would be an amazing improvement.
There are no additional changes needed to the transport layer, it would be transparent for telcos. It can be an OTG encryption layer.
Initial key exchange would be the only part that would require a couple of additional one-time messages but it would be automated. And not all messages need to be encrypted, nobody cares that my package has been shipped. And it would be an improvement anyway from having zero encryption to being able to have encryption
The whole thing is so simple that it could be implemented today by all the SMS apps without missing a beat. The only thing missing is the willingness to do so.
In fact it could be added as an option in any SMS app very easily β only for people who are both on the same app of course.