In GS there is an extra "api". Don't know if this is needed by design... Maybe implementing it in the same way as Mastodon and Pleroma would help to establish a standard way?
Comparing nodeinfo in GS, Mastodon and Pleroma gives this:
https://gnusocial.net/api/nodeinfo/2.0.json
https://mastodon.social/nodeinfo/2.0.json
https://pleroma.libretux.com/nodeinfo/2.0.json
In GS there is an extra "api". Don't know if this is needed by design... Maybe implementing it in the same way as Mastodon and Pleroma would help to establish a standard way?
It isn't needed by design, but it was in fact a design choice :)
The standard way is to check `/.well-known/nodeinfo` as in [https://gnusocial.net/.well-known/nodeinfo](https://gnusocial.net/.well-known/nodeinfo).
Also, we aren't the only deciding to put nodeinfo under `/api/`, Pixelfed did the same, as seen in:
[https://pixelfed.social/api/nodeinfo/2.0.json](https://pixelfed.social/api/nodeinfo/2.0.json).
Comparing nodeinfo in GS, Mastodon and Pleroma gives this:
https://gnusocial.net/api/nodeinfo/2.0.json
https://mastodon.social/nodeinfo/2.0.json
https://pleroma.libretux.com/nodeinfo/2.0.json
In GS there is an extra "api". Don't know if this is needed by design... Maybe implementing it in the same way as Mastodon and Pleroma would help to establish a standard way?
It isn't needed by design, but it was in fact a design choice :) The standard way is to check
/.well-known/nodeinfoas in https://gnusocial.net/.well-known/nodeinfo.Also, we aren't the only deciding to put nodeinfo under
/api/, Pixelfed did the same, as seen in: https://pixelfed.social/api/nodeinfo/2.0.json.