this post was submitted on 06 Jan 2024
667 points (97.3% liked)
Lemmy Shitpost
26837 readers
3173 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I mean it's just a gsm standard with some extra features. Realistically you could probably (relatively) easily figure it out and code it yourself like beeper mini did with iMessage but I don't think gsm or Google is going to change the standard to stop you.
...no, you can't. I've seen people try. Google says they will open the RCS protocol to 3rd parties... soon?
Google doesn't own the RCS protocol. This is like saying they own the SMTP protocol because they provide Gmail. They are just one company that has implemented the protocol in their default text message app. They built end-to-end encryption into their implementation, which is currently closed source. I'm guessing this is what you're referring to.
Anyone can implement RCS. It may cost you some money and some time, but it is possible. That's the difference I was originally trying to highlight.
No, anyone cannot. That's why I said it wasn't really open. 3rd party android apps can't use RCS. I would need to use Google's Messages app.
No. I'm sorry. You can't just say it and make it true. Please show me how Google owns RCS or prevents other developers from implementing it within their own apps.
I'm convinced you're incorrect. SMTP is an open transport protocol defined in RFC 2821 by the IETF. Anything that is an IP "open protocol" would be defined by IETF as an RFC. No one owns it. No license is required to operate an SMTP server. Same with other common protocols like SIP. It sets qualifications/requirements for what it is so anyone can use it.
RCS is a proprietary standard owned by the GSMA. It seems there is some support for developers that want to use RCS but it's through an API. Meaning your use is licensed and at a cost. Also, you can't really see what it's doing. You're just using an API. Your access can be revoked. So is it an open standard? No.
I did my own research and I plan to try these APIs because I have used other messaging services like twilio for paging applications. But here are some other geeks arguing about it:
https://www.reddit.com/r/Android/comments/wm18td/stop_telling_people_that_rcs_is_an_open_standard/
https://www.gsma.com/futurenetworks/wp-content/uploads/2019/10/RCC.07-v11.0.pdf
The specification exists. It's not free as in beer. This is really beside the point. Google implemented an RCS messaging client. Your cellular carriers implement the RCS endpoints the clients use.
Well others including I have explained it to you. It's not open. And your comparison (SMTP) shows your lack of knowledge on the subject.
What have you explained? That RCS is not stewarded by the IETF? That's not the crux of the issue. My original claim was that RCS was more open than iMessage and that RCS is not owned or controlled by Google. Tell me where I'm wrong, and back it up with good sources. Or not. Whatever you're feeling like.
I don't have the technical knowledge to explain how what works, but there are no FOSS or 3rd party RCS apps for a reason and you can find various posts on social media from devs trying to implement or even reverse engineer RCS and failing
That's their rcs protocol. It's the one with the features. Without the features is easy, the features are what make it difficult.