- cross-posted to:
- googlepixel@lemdro.id
- cross-posted to:
- googlepixel@lemdro.id
cross-posted from !googlepixel@lemdro.id
You must log in or # to comment.
Gross :(
Allowing people to more easily sign in?
Half the people here are trying to de-google
Then this is irrelevant for them because they wouldn’t be using Google’s Messages application. They’d be using another one.
Unrelated, this is for accessing via messages.google.com if you want to dwgoogle don’t use GOOGLE messages.
Google Messages replaced the AOSP SMS app, and is the only app that provides support for E2EE RCS and standard RCS if your carrier has not provided their own.
It’s also one of the few mainstream mesaaging apps that won’t have a hissy fit about being installed on a rooted device
Edit: Ah, my point got lost. There is no other app on Android that will let you do RCS mesaaging from a desktop.
Yes but it’s a proprietary Google app. Degoogling is to rid yourself of this app.
It’s the only app that has RCS. I don’t use it, but I think it’s kind of terrible that Google has a monopoly on the format.
It’s terrible that no one else has decided to make an rcs app? That’s not really under googles control
Google has blocked anyone’s ability to make an RCS app by making the API a system-level API. In order to make an RCS app, you must make an Android device. So Samsung could make one and bundle it with their phones, but Textra can’t make one and make it available on the Play Store.
Ah ok, other replies mentioned API access in relation to servers so I misunderstood the issue. It looks like that API is hardlocked to Google (and Samsung?) devices. Thanks for the info
They won’t open the api. Anyone else who tries to make one would be starting from scratch. Including with a server
Sure, but isn’t that just complaining that Google runs the largest implementation of RCS? It would’ve been great if this was handled by carriers, but they never would pick up the task so Google just did it inhouse. I think if they hadn’t rcs would just be dead by now (for better or worse)
It’s because Google hasn’t allowed anyone else access to the RCS API, actually.
Google doesn’t open their own RCS API to the public. Nobody is stopping you from running your own server and service so far as I can tell
They don’t, RCS is open.
If the qr code options stays then its absolutely a positive, but RCS is already a (very frustratingly) closed ecosystem: locking certain features behind an account would just kinda suck, since google messages (or I think maybe Samsung messages also) is the only way to use RCS presently
That’s literally not this. This is for accessing on tablets and computers via the web app.
Yes, I know. I’d like to have access to that feature without having to use my google account
Use another messaging services. It’s google messages.
RCS is the only way to get read receipts with most folks I know, and google messages is the only way to use RCS presently
If you have a problem with using a Google account on a Google product, don’t use that Google product. Use signal, WhatsApp or any other messaging service.
Scanning a QR is a lot quicker than signing into an account though.
Not when you’re already signed in on different devices
That would be nice
deleted by creator
