I’ve started writing a new version of this FEP:
1 Like
Perhaps of interest, FediMod FIRES, my project for moderation data exchange, actually supports NodeInfo too (though using a non-standard protocols value, and not exposing usage or metadata), because I wanted a nice way to discover if a given server is a FIRES server: fires/components/fires-server/app/controllers/well-known/nodeinfo_controller.ts at b714be440326f7a95f3283076aeee3681b8d1c34 · fedimod/fires · GitHub
I’m not sure what metadata we’d eventually use, though probably none defined in FEP-0151 at this time, maybe nodeName, nodeDescription and staffAccounts since we do have those? That said though, staffAccounts would be IRIs to accounts right? Do they have to be same-origin as the NodeInfo document? Or could my staffAccounts point to actors on other servers (which is how this is intended in the FIRES setup)
1 Like
I think staffAccounts could point to other servers.
A more descriptive property was proposed for NodeInfo 2.2, which allows email addresses too: Add support by 6543 · Pull Request #84 · jhass/nodeinfo · GitHub.
Discussion thread for the new FEP: