-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best terms for Webfinger -> Actor ID and Actor ID -> Webfinger #12
Comments
Oh, I was using Encoding to talk about allowed characters, MIME types, |
After thinking about this, I think it's actually better to have them under the "Discovery" header, since they both deal with discovering some identifier given another identifier. I also don't see a problem with "forward" or "reverse" as disambiguation. I have more of a problem with "Encoding" being used to describe "reverse discovery", because to me, "encoding" is the best way to describe the section that's actually about encoding the identifiers and the responses. |
Especially noteworthy is that issue #4 was filed as "reverse discovery", so I'm just taking that terminology :) |
Currently the doc uses "Discovery" for the process of getting an Actor ID from a Webfinger address.
It uses "Encoding" for the process of getting a Webfinger address given an Actor ID.
I changed this from "forward discovery" and "reverse discovery" since those were a little hard to parse.
Regardless of the terms, I think they should each be top-level headings.
The text was updated successfully, but these errors were encountered: