Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XMPP-Transport-Interface [feature-request] #42

Closed
hpmueller1971 opened this issue Jan 7, 2017 · 3 comments
Closed

XMPP-Transport-Interface [feature-request] #42

hpmueller1971 opened this issue Jan 7, 2017 · 3 comments

Comments

@hpmueller1971
Copy link

Hi everyone,

is there any chance that you could implement the spectrum2 transport gateway api, like transwhat does, or even the official XMPP Component Protocol API, so signal-cli could be user via Jabber...? transwhat is a whatsapp-transport for jabber, so it also uses an e164-number as the identifier and should be fairly similar to signal...

Or, is there any way to use the d-bus api from a jabber-transport?

@AsamK
Copy link
Owner

AsamK commented Jan 24, 2017

I don't have the time (nor the need ;) to implement this. If someone wants to do it, go ahead.
The dbus api is probably too limited currently.
I've also started on a json output, that might be useful for this.

@thundergreen
Copy link

Im also interested

@AsamK
Copy link
Owner

AsamK commented Aug 24, 2021

XMPP is out of scope for signal-cli.
However there's now a json rpc based api on master that could help with implementing this.

@AsamK AsamK closed this as completed Aug 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants