-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Incompability with Misskey v13.5.6+ #125
Comments
Hi! Weird. pleroma-bot --version I've been running the bot against the instance misskey.io, which is running Misskey v13.9.1 and it's able to create notes as far as I can tell. The latest release candidate as of now for the bot is
That's the version of the bot that I'm running, give it a try and see if it makes any difference in your case. I'm curious, did you run into this issue when upgrading your Misskey instance? Oh, and did you generate new tokens on the new Misskey version and they also didn't work? Next thing we could try is to make a call directly to the Misskey API of your target instance using your token (with cURL, for example) to see whether the API is working fine and the issue is with the bot or not. |
Hi! Thank you for your prompt reply :) I installed using pip so the version was
Not really. I tried to install the bot today without doing any upgrades. After I found out the bot didn't work with my instance ( You could try testing if using Thank you so much for your help! |
Oh and may i ask if it's normal that Almost every time I run the bot I get something like the codes below
|
Possibly due to recent changes in Misskey's API, it appears that the bot does not work with Misskey v13.5.6 to v13.9.2 (the latest version). While the same bot configuration is compatible with Misskey v12.118.1, it does not seem to work with version 13.5.6+. Despite granting the API token full access by selecting the "enable all" option, I still received an error message stating that I am not authorized to post using that API when attempting to run the bot.
The text was updated successfully, but these errors were encountered: