I think the digest part is a bit misleading because the examples are about GET requests, which would typically not involve a Digest header.

Fair point. Separated the explanations for digest into a separate section.

Before investing more time, just to clarify: are you generally interested in a contribution? Based on first hands experience I believe the documentation should be fixed (given the growing interest in Mastodon and probably also in the tooling ecosystem) and I am happy to iterate over this PR. But I should have asked earlier.

@sventiffe I just added 57d1d76 to #1060 -- does this commit address your concerns, or are there improvements that could be made in your opinion? To summarize, the examples now include both GET and POST, with the POST example calling out the need for digest.

EDIT: Added a few more commits to clarify use of RSA with SHA256 and fix the public key vs private key mixup.

@trwnh it largely addresses my concerns (your changes/PR are a little bit challenging to navigate as it is really a lot of pending changes bundled into one PR). I left one comment about the error in the doc of signing the string with the public key (it needs to be the private one).

On a meta level: I am not familiar with the governance structure of this project, the reviewers/approvers and regular contributors. I would however strongly suggest to get documentation improvements out in smaller chunks if that allows faster updates. Given that there are probably a lot of people joining the ecosystem now. 🏒 😄 cc @Gargron

Thank you folks for the hard work! I have no particular feelings about my PR, please close if not needed.

Well, they are small chunks, but they keep building up on account of there being no one to merge them quickly...