Support https://gitlab.com/morph027/python-signal-cli-rest-api ...

[rotdrop]

... in addition to the deprectated https://gitlab.com/morph027/signal-cli-dbus-rest-api.

As of now that package has been deprecated:

https://gitlab.com/morph027/python-signal-cli-rest-api

But it still works in principle.

I will soon start to work on a version which supports signal-cli's native JSON RPC HTTP endpoint which has been introduced in

signal-cli 0.11.5+

[ostasevych]

Please, consider adding support for https://github.com/bbernhard/signal-cli-rest-api/
Here there are experiments with styled messages.

[rotdrop]

Please, consider adding support for https://github.com/bbernhard/signal-cli-rest-api/ Here there are experiments with styled messages.

Where is "here"?

IMHO, it should still work with https://gitlab.com/morph027/python-signal-cli-rest-api

Doesn't it then also cover this bbernhard things?

[ostasevych]

Please, consider adding support for https://github.com/bbernhard/signal-cli-rest-api/ Here there are experiments with styled messages.

Where is "here"?
Sorry, for the ambiguity. I mean, bernhard is working on bringing styles to the Signal CLI REST API (bold, italic, strikethrough, monospace are already working).

IMHO, it should still work with https://gitlab.com/morph027/python-signal-cli-rest-api

Doesn't it then also cover this bbernhard things?

That was my question, actually. I should test it.

By now, I have modified the Gateway.php by replacing v1/send with v2/send. Do you think it may be placed in upstream?