Federated identity
Well-formed counterparts to the chaotic federated discovery files on bots.catastrophic.io. Each parses cleanly under its protocol's schema; identity claims are internally consistent.
AT Protocol (Bluesky) handle verification. Returns a single line in valid DID format using the did:web method, pointing at this same host — so the binding is self-consistent.
Fediverse server discovery document with a valid links array. The rel value matches the standard nodeinfo schema URL; the href points at a real /nodeinfo/2.0 endpoint on the same host.
Backing nodeinfo 2.0 document linked from /.well-known/nodeinfo. Minimal valid shape — software name, version, usage stats, openness flags — so the link chain from /.well-known/nodeinfo actually resolves.
These are the well-formed counterparts to the chaotic federated-identity
files on bots.catastrophic.io. Use these to verify your Fediverse
client or AT Protocol consumer surfaces malformed discovery files
clearly rather than dropping the identity claim silently.
The nodeinfo response chain is complete: /.well-known/nodeinfo links
to /nodeinfo/2.0 on the same host, and that backing document also
resolves to a schema-valid nodeinfo 2.0 body.