This repository has been archived on 2023-12-04. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Find a file
2019-12-29 22:24:43 +00:00
schemas/1.0 Add new keys to 1.0 schema 2018-04-08 15:31:23 +03:00
.gitignore Add .gitignore 2016-05-14 14:11:47 +03:00
LICENSE Add LICENSE 2018-11-07 17:59:38 +00:00
PROTOCOL.md added wordpress server and webmention protocol 2018-11-30 23:20:54 +02:00
README.md Update README.md 2019-12-29 22:24:43 +00:00

NodeInfo2

NodeInfo2 is an effort to create a standardized way of exposing metadata about a server. This might be necessary to expose ownership and organization details, usage statistics and protocol capabilities.

Protocol

Please see the protocol definition.

Versioning

Current version is 1.0. Version upgrade shall happen only in backwards incompatible major changes. Forward changes, ie adding keys will not cause a version upgrading. This means implementors can be guaranteed a stable basic implementation that will not have to be changed all the time.

Support

Implemented in the following platforms:

Library support is available for the following:

Have a server or library you have added support to? Send a PR!

License

All content in this repository is under CC0 unless otherwise noted.

Contributing

Please open issues and pull requests if you want to suggest a change. If you open a pull request you agree for your work to be released under CC0.

History

NodeInfo2 is a fork of NodeInfo which was seen as too complex for the problem it is solving. NodeInfo2 is interested in controlling structure of the document, not content. Additionally, discovery and strict versioning has been dropped for simpler implementation.

NodeInfo emerged from it's predecessor /statistics.json that was added to the diaspora* software to be able to built a statistics collection and aggregation service, it was quickly supported by Friendica and RedMatrix. As more and more metadata was added and modifications occurred that would break backward compatibility, we felt the need to make this a more coordinated effort.