Documenting federation behavior in a semi-standard way?

[silverpill]

The proposal has been submitted to the FEP repository. Discussion: FEP-67ff: FEDERATION.md

[indieterminacy]

Fwiw, I updated the Lemmy link.

Also, I flagged up that the link for Zot requires updating:

Guide for new ActivityPub implementers

I notice Zap has been moved to a different location in the same forge, Codeberg: This would affect the url pointer in the section on fediverse.md Does anybody know the correct update to provide?

[indieterminacy]

I didnt get anything for this site:
https://fedidocs.org/

Did you mean this instead?:

About Fedi Devs | Fedi Devs

[aschrijver]

Yes, the domain name has changed.

[WisTex]

Is there a standard way of indicating that protocols may be turned on and off on a user by user basis?

For example, on Hubzilla, the default protocol is Zot, but individual users can activate ActivityPub if they want (if installed by the administrator).

So it would be inaccurate to imply that all accounts (channels) on the server support ActivityPub.

[silverpill]

If account is identified by an HTTPS URL, clients can use content negotiation to test protocol support.

For example ActivityPub servers should return ActivityPub representation if Accept header is set to application/ld+json; profile="https://www.w3.org/ns/activitystreams".