Ryan Barrett

Hey fluffy, sorry for the trouble! I see your OAuth requests for both sites, and Bridgy redirected the same way to both of their OAuth endpoints (below), so I'm not...

I tried the app based OAuth flow with Bridgy's app for each site, and they both gave me an access token and responded fine to `/api/v1/apps/verify_credentials`. So, no clue what's...

I just realized this is probably https://github.com/mastodon/mastodon/issues/12915. Reproducible 502 in Mastodon's OAuth flow due to URL length, narrowed down pretty conclusively in that issue, but they haven't really shown any...

@syrabo ugh, sorry for the trouble! That's bad. Short term, I'm happy to disable your Bridgy account manually if you want, just post (or send me) your Bridgy user page...

Oh wow, interesting data point. I assumed it wasn't browser-specific since the Mastodon instance itself returns an HTTP 502, but something else may be going on. Thanks for the tip!

@metbril, got your email, and saw your https://github.com/mastodon/mastodon/issues/12915#issuecomment-1029936700. Sorry for the trouble! Here on GitHub issues is definitely right place to get Bridgy support. Just to confirm, when you click...

Yeah, it's unfortunate. The bug is only in Mastodon's user-facing OAuth flow. Bridgy holds long-lived access tokens for Mastodon users who have logged in successfully, so it can use those...

@metbril I did some surgery and managed to get your account working with the old Mastodon access token. The underlying Mastodon bug here is still a problem, but glad at...

Hi again @metbril! I've re-enabled backfeed for your account. Looks like your Bridgy Mastodon OAuth token doesn't include the publish scopes, though, which is why Bridgy was disabling the account....

Discussion is now in https://github.com/doorkeeper-gem/doorkeeper/issues/1554, tentative conclusion is that the issue is in doorkeeper. Still not much more movement though. 😐