Matt Jankowski

Noticed same thing for an api/streaming example - added on to here instead of new PR.

Rebased this after https://github.com/mastodon/mastodon/pull/32285 Will rebase again after https://github.com/mastodon/mastodon/pull/32307 and see what's left.

Rebased again after openssl added in another PR, this is now sufficient for "wrap the `HTTP` lib errors up" purposes. The additional classes being added here after the 2 other...

Sounds good - there are a few spots in the spotlight wrappers which I think can use the added array but I wanted to consider more before updating; will do...

Did you ever work this out? If not, can you provide more info about what exact endpoint and how to replicate? My guess would be some sort of permissions/params type...

Thanks for additional info ... I was able to replicate (not your exact response, but similar) locally. Opened a docs PR to just capture, at bare minimum, that these sorts...

Can you add a before/after image here?

Closing on assumption this is abandoned, and b/c of [general policy of not accepting unsolicited external UX changes](https://github.com/mastodon/.github/blob/main/CONTRIBUTING.md#project-specific-considerations) If you want to push forward, can you reopen and add some...

In this section of the methods/oauth page - https://github.com/mastodon/documentation/blob/main/content/en/methods/oauth.md?plain=1#L115-L119 - there is language in the grant type section about using `authorization_code` only when `code` is provided. Is the issue/request here...

Looks like this needs rebase, and also CI approval. Separately - might help to add at least some before/after screenshots here...?