I added a note that relay protocols are not standard AP protocols and are generally not fully conformant with AP.
Fixed, Thanks.
I added a note that there are other variants that may work. It’s interesting, AodeRelay uses /actor in the URI but “relay” as the preferred user name. It’s possible I misinterpreted the Pleroma source and they only require “relay” for the preferred user name and not the URI.
I’d like to transition “FEP-ae0c: Fediverse Relay Protocols: Mastodon and LitePub” to FINAL status (although I’m not exactly sure what that means for Informational FEPs).
/cc @silverpill @helge
Are you sure about the informational status? People are already implementing it: feat: add mastodon style relays by TheNoim · Pull Request #109 · fedify-dev/hollo · GitHub
Yes, I believe it’s informational. It’s documentation of a few existing implementations rather than prescribing future ones. However, given the “implementation” type is mentioned but not defined in the FEP process, I can’t be 100% sure.
It is left to the author’s discretion . We may make “Implementations” section required for proposals of this type, and then create some tooling that extracts information from this section, but there are no plans to add other requirements.
Some of my FEPs are similar to this one, they describe existing implementations, and I intend to assign “implementation” type to them.
What’s the process for moving FEP-ae0c to FINAL? Do I submit a PR with the changes or do the facilitators make those changes?
Could you submit a PR changing the status to FINAL and adding dateFinalized attribute?
Facilitators will merge it.