You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should probably be tested if it's supported by an implementation. The primary use case is for aggregating instance statistics and high-level metadata (for fediverse crawlers). It's not required for federation per se and a nontrivial number of instances do not support it.
Possible tests:
Correct content-type for the JRD and the version-specific nodeinfo data.
Validate nodeinfo response per the version-specific nodeinfo JSON Schema
Check that a server can handle non-nodeinfo links in the nodeinfo JRD (e.g., "application actor" links).
My guess is that a majority of instances will fail one or more of these tests. Possible failure cases:
Uses application/json for JRD
Adds values for properties like protocol that are not valid per the schemas
Assumes nodeinfo JRD only contains nodeinfo links.
Should we test that as well? If so, what needs testing?
The text was updated successfully, but these errors were encountered: