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]
📰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
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.
Is the Google version of RCS not compatible with someone else's RCS, then?
As in, I take it nobody else wants to run a server because it costs money, right? But suppose I did, and I had an RCS app to run with it. Would someone using my app be able to send a message to an Android user using Google Messages?
No. Google Messages only talks to Google's servers.
The way it's supposed to work is Google has some servers and an app, and you have your own servers and own app, and when someone sends a message from your app it goes your app > your server > Google server > Google app. And the same in reverse.
But in reality Google doesn't let anybody's servers talk to theirs and tries to make everybody use their app and their servers. Which they can afford to do because they own Android and can shove their app down anybody's throat.
[This comment has been deleted by an automated system]
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.