#mastodon developers: have you noticed any #OAuth errors with your apps? Today I discovered that my apps (bitlbee-mastodon and mastodon-archive) and others (I tried #tootstream) cannot get authorized on dice.camp, tabletop.social and social.nasqueron.org but it works for octodon.social. My existing dice.camp credentials keep working, though. I just can't get new ones. Both dice.camp and octodon.social seem to use Mastodon 2.3.3 so that does not seem to be the problem. Ideas?
@kensanata I tried this with #tootstream and managed to replicate the error. Wondering if the common thread is Mastodon.py and if something changed. I got a 401 error when I tried it on tabletop.social, and was directed by a user that they were having the same issue.
@craigmaloney Did you make any progress in this respect? I tried some stuff and password credentials still work; it's just client credentials which don't. My notes in the comments to my own blog post: https://alexschroeder.ch/wiki/2018-05-12_Mastodon_OAuth2_Issues
#mastodev #oauth #doorkeeper
@kensanata No, but I will take a look at your notes to see if anything jumps out.
@craigmaloney Maybe. The OAuth implementation in Bitlbee Mastodon is written in C and has the same problem, though. 😭