-
Notifications
You must be signed in to change notification settings - Fork 6
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
incorrect URL for streaming API #16
Comments
This updates the streaming url used to match that of the Misskey API docs at https://misskey-hub.net/docs/api/streaming/ Resolves yupix#16
Thanks for the report. I think this is probably a bug because the design was initially based on the assumption that URLs would be received in the wss//example.com/streaming format. |
I just remembered that in pull request #17, if you include streaming in the url, it may not work correctly as streamingstreaming. Please wait a while until this is resolved. |
In fixing this bug, we also fixed a bug that caused an error if there was a trailing |
The framework uses an incorrect URL for the streaming API. The streaming API documentation can be found at: https://misskey-hub.net/docs/api/streaming
wrong:
wss://misskey.example/?i={token}
correct:
wss://misskey.example/streaming?i={token}
I think this line needs to be changed:
MiPA/mipa/gateway.py
Line 66 in e53ee61
It only works because Misskey is currently permissive about which URL you use. Foundkey (a fork of Misskey) is more restrictive and only allows the path
/streaming
that is defined in the documentation.The text was updated successfully, but these errors were encountered: