this post was submitted on 18 May 2025
463 points (99.2% liked)
Microblog Memes
10837 readers
513 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
- Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
- Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
- You are encouraged to provide a link back to the source of your screen capture in the body of your post.
- Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
- Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If an image is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
- Absolutely no NSFL content.
- Be nice. Don't take anything personally. Take political debates to the appropriate communities. Take personal disagreements & arguments to private messages.
- No advertising, brand promotion, or guerrilla marketing.
RELATED COMMUNITIES:
founded 2 years ago
MODERATORS
Google is trying to kill SMS. My new android by default has sms disabled, defaulting to RCS with "try sending sms instead if rcs fails to send" option being off by default, which makes no sense from user perspective
RCS is actually a huge improvement over SMS, as it is fully encrypted. One of the few times I've ever approved of something Google did...
If only it was an open standard...
It... is? It's an open standard that anyone can use and implement. The main provider is Google and there has been a huge push from them to get Apple to adopt, which they mostly have. It's not 'owned' by any company. It's predominantly serviced by Google, but is in fact an open standard. Google and others have their own format which is how they and their apps interpret and interact with each other, but it is an open standard. There are some backend and requirements for it which stops most from setting it up and implementing off the shelf and just going with Google, but you absolutely could use and make your own format with the standard.
Yep, main reason it's associated with Google because they bought a company (Jibe Mobile) making one of the main backend service offerings and offered cloud hosting of it, so providers just went with that rather than rolling out their own software.
Also with Apple ignoring it in favour of iMessage, Google was the only one supporting it on handsets. Google client + Google backend = people think it's Google's iMessage competitor.
I'd say it does have some merit from a security perspective though.
I agree it should be something that's at least more clear for users to enable/disable on setup, but I personally don't think having it enabled by default is ideal, considering how insecure SMS is.
...but I can literally send infected files thru RCS to my grandma.
True, as is the case with almost any messaging service. But the benefits of RCS do include:
It's purely an improvement over SMS in terms of security and privacy, and personally, I don't think users should be defaulted into having their phone downgrade to insecure protocols. It should always be an opt-in decision they have to make. (although they could definitely make it clearer that someone could enable it if their messages are failing to send with RCS)