Skip to content
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

Closed
evanp opened this issue Feb 29, 2024 · 3 comments
Closed

Best terms for Webfinger -> Actor ID and Actor ID -> Webfinger #12

evanp opened this issue Feb 29, 2024 · 3 comments

Comments

@evanp
Copy link
Collaborator

evanp commented Feb 29, 2024

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.

@trwnh
Copy link
Collaborator

trwnh commented Mar 1, 2024

Oh, I was using Encoding to talk about allowed characters, MIME types, links formatting, and stuff like that

@trwnh
Copy link
Collaborator

trwnh commented Mar 3, 2024

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.

@trwnh
Copy link
Collaborator

trwnh commented Mar 3, 2024

Especially noteworthy is that issue #4 was filed as "reverse discovery", so I'm just taking that terminology :)

trwnh added a commit that referenced this issue Mar 3, 2024
Force-pushing until #12 is addressed, plus initial work on #9
@trwnh trwnh closed this as completed Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants