-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Support for Misskey/Calckey API #539
Comments
That would be a nice addition! A PR will be highly appreciated, feel free to ask if you need insights or help to get started. |
With the move to FireFish, most of the API should be Mastodon compatible and thus work out-of-the-box with Sengi, as far as I understand, except for FireFish-specific things like reactions, etc. However, there seem to be a few issues, so the compatibility is probably not 100%:
For the 1st error, the console shows a bunch of unrelated requests:
@NicolasConstant if you'd like to look into it, is there anything I can provide to help debug this? In a way it does not seem FF-specific but I don't see it on my Mastodon account... |
Yes I've run a Firefish account in Sengi to test it quickly, there is still some incompatibilities. That's something that must be solve on the Firefish side, when I was looking to support Pleroma properly, I opened issues on their repo to notify discrepancies with the original MastoAPI / official MastoAPI documentation. I think that's the best way since it will ensure the API implementation itself will behave exactly like any MastoAPI implementation, and therefore being 100% compatible with 3rd party clients. ps: if you detect issues on Sengi, you could check the mastodon documentation, and open issues on Firefish to show them what isn't compliant and why. |
Would be awesome to see this added to Sengi, since I have accounts on Misskey instances as well as Mastodon.
If this is something that is desirable for the app I might be tempted to try and do the work myself.
The text was updated successfully, but these errors were encountered: