"Invalid credentials" when posting a status to a Pleroma instance #1423
Unanswered
jncosideout
asked this question in
Q&A
Replies: 1 comment
-
|
OK I think I found that "create" actions are always POSTed https://github.com/neet/masto.js/blob/main/src/adapters/action/dispatcher-http.ts So if POST is the required method for Pleroma to create a status, then that must not be the problem. I'll see if I can apply a custom header to set "Content-type" = "multipart/form-data" in my request, and see if that fixes it like it did with the Tusk lib. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am switching from another JS library for the mastodon api called Tusk.
I am using the same access token I was granted for my pleroma instance and it is still valid, yet I am getting "Invalid credentials" when I use the Masto library and try to post a status or call verify_credentials.
Is Masto,js incompatible with Pleroma completely?
For what it's worth, I found this documentation explaining some differences between the mastodon and pleroma apis
It looks like pleroma uses the POST method. Could that make a difference?
And this is anecdotal, but to get the Tusk library to work for me on a pleroma instance, I had to set a parameter to force tusk to send a multipart form request instead of a url query, in order to post a status. That leads me to believe the http method may be different for pleroma vs mastodon.
Thanks for any help or guidance.
Beta Was this translation helpful? Give feedback.
All reactions