search

octoshrimpy / quik

The most beautiful SMS messenger for Android - Revived
GNU General Public License v3.0
473 stars 23 forks source link

✏️ [ FEAT REQ ] RCS support #124

Open YannBirba opened 3 weeks ago

YannBirba commented 3 weeks ago

Describe the feature you'd like

Is it plan to support rcs ? Is it possible ?

spart0n654 commented 2 weeks ago

This is not possible for any 3rd party text app until google makes that api available for public use.

ilmaisin commented 2 weeks ago

https://github.com/Hirohumi/RustyRcs

It is possible by implementing RCS in the app. However, if one's carrier requires USIM authentication, it will require the system privilege.

If your carrier offers no RCS service, then you need to depend on Google. There has been a proof-of-concept 3d party client for Google's carrier-independent RCS service, though.

YannBirba commented 2 weeks ago

https://github.com/Hirohumi/RustyRcs

It is possible by implementing RCS in the app. However, if one's carrier requires USIM authentication, it will require the system privilege.

If your carrier offers no RCS service, then you need to depend on Google. There has been a proof-of-concept 3d party client for Google's carrier-independent RCS service, though.

Ooooh nice, I wish I cloud implement it myself but I don't think I can honestly ... But thank you, I reopened the issue so

theotheroracle commented 1 week ago

https://github.com/vidit135g/Replify-Messenger/issues

this qksms fork claims to support RCS, might be easy enough to draw some code from !

theotheroracle commented 1 week ago

I wasn't able to get the app running on my phone, so I can't say for sure, but its promising at least

here's some other libraries that might be helpful: https://github.com/android-rcs/rcsjta

theotheroracle commented 1 week ago

there's a lot of confusing information about RCS, but I keep reading that carrier rcs is going away and everything is relying on Google messages anyways, so rooted / ROMs android may never get rcs unless we reverse engineer Google messages app, which may be impossible to do anyways, and bypassing play integrity seems like a pipe dream, so this effort may be a pointless endeavor

theotheroracle commented 1 week ago

might need to get the EU to step in tbh

YannBirba commented 1 week ago

It's so sad ... Thank you for investigating

theotheroracle commented 1 week ago

one possible way this could work, is if you were to register with https://jibe.google.com/ and not publish the keys i guess ? which means the f-droid release wouldn't have rcs support, but that wouldn't be a deal breaker for most people who wanted RCS i think . it could still be updated through izzydroid, so it wouldn't be too much of an issue . i tried registering for a jibe account, but i kept getting some vague error about how my request couldn't be completed, likely meaning they disqualified my application for some reason, and are being vague about it so as to prevent me from fixing the issue, which is pretty terrible, but i'll try emailing them tomorrow and see if i can get an account .

theotheroracle commented 1 week ago

i did manage to install and run the rcs-fi-client locally, but without an account with jibe or some other RCS SIP provider, i can't do much with the software besides the --sim test messages it runs . i do have another sip account, so i'll have to check if that supports RCS and i'll try with that .

jume2003 commented 4 days ago

i did manage to install and run the rcs-fi-client locally, but without an account with jibe or some other RCS SIP provider, i can't do much with the software besides the --sim test messages it runs . i do have another sip account, so i'll have to check if that supports RCS and i'll try with that .

is that working ?