remove stale docs #1113
Open
remove stale docs #1113
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bnewbold
force-pushed
the
bnewbold/remove-stale-docs
branch
from
2868410 to
424d26d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are 2022-era docs written by @whyrusleeping
The feed notes stuff is out of date and uncontroversial to remove.
The JWT notes have info that is somewhat intentionally not documented elsewhere: PDS implementations can put whatever they want in there. I think self-hosted instances already maybe just use a UUID? But there might be some cases/hacks where this is helpful. We could copy to internal docs? I'd still push to remove, don't want lots of folks building on this and it results in breakage or interop problems down the line.