#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?
Some experimentation seems to indicate that the problem is on my side since I can use Mastodon Archive if I generate the access token manually: https://alexschroeder.ch/wiki/2018-05-12_Mastodon_OAuth2_Issues
So now I need to look at what I'm doing wrong in my use of Mastodon.py (and then fix it in the C code of bitlbee-mastodon, too).
#bitlbee #mastodon #archive #oauth
@enkiv2 If you follow the link you'll see that I was able to get all the necessary info using curl. I think this proves that there is no config option blocking me, at least in this case. I also asked the admin of tabletop.social whether there was a whitelist of apps or something like that (same idea, basically) and they said no. That's why I started experimenting.
@kensanata
Ah, nice.
I wonder what my issue was, then.
@kensanata
Some instances don't like to give out auth tokens when scripts request them (and just tell the scripts "forbidden").
Mastodon.social is like this in my experience.
I assumed it was a config option available to admins.