pysogs zmq bot api#7
Conversation
d1ccb04 to
650ded2
Compare
85a40d6 to
cf7e5a6
Compare
6ae6d25 to
83464c5
Compare
e916894 to
d5a8aa8
Compare
d5a8aa8 to
5000f8f
Compare
37dadd1 to
97a093d
Compare
|
I will be able to send messages via curl with this right? |
no, you can do that already using the non legacy http endpoints. this PR is for using zmq. |
|
the current planned http endpoints are defined here: https://github.com/oxen-io/session-pysogs/blob/dev/api.yaml |
Actually almost all are implemented now with the recent PRs; I think the only one left is file downloading, which I'll be tackling tomorrow. |
|
Awesome! I'm really naive when it comes to api stuff but I find it very interesting. |
|
I just want to be able to send a message via curl lol |
|
Curl likely won't ever be possible (by itself) because you have to be able to compute blake2b hashes to sign your request header with your session ID. So a few lines of Python, sure, but it needs a bit more than a static HTTP request. |
|
Oh. Could you take a look at this service https://github.com/caronc/apprise/wiki#notification-services and let me know if it would be possible to use it to send a message to my open group? |
make an issue for this so it is tracked. thanks. |
* wire up event subscription via zmq to notify connections of new events * add zmq handler to inject http rpc calls via zmq authenticated by zmq curve pubkey
if data is a string or bytes dont try to bencode the repsonse
Co-authored-by: Jason Rhinelander <jason@imaginary.ca>
Co-authored-by: Jason Rhinelander <jason@imaginary.ca>
64ffc81 to
1dfdec1
Compare
it is an exceptional case and should not just be an assert so that i can happen on release mode too. |
bot api for sogs