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

Nodeinfo tests? #53

Open
jernst opened this issue May 2, 2024 · 1 comment
Open

Nodeinfo tests? #53

jernst opened this issue May 2, 2024 · 1 comment
Labels
nice to have An issue that is not terribly important and can be deferred

Comments

@jernst
Copy link
Member

jernst commented May 2, 2024

Should we test that as well? If so, what needs testing?

@steve-bate
Copy link
Member

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.

@jernst jernst added the nice to have An issue that is not terribly important and can be deferred label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nice to have An issue that is not terribly important and can be deferred
Projects
None yet
Development

No branches or pull requests

2 participants