NodeInfo

This API is available since Fedify 0.2.0.

According to the official NodeInfo website:

NodeInfo is an effort to create a standardized way of exposing metadata about a server running one of the distributed social networks. The two key goals are being able to get better insights into the user base of distributed social networking and the ability to build tools that allow users to choose the best-fitting software and server for their needs.

In fact, many ActivityPub servers, including Mastodon and Misskey, provide NodeInfo endpoints. Fedify provides a way to expose NodeInfo endpoints for your server.

NOTE

The version of NodeInfo that Fedify supports is 2.1.

Exposing NodeInfo endpoint

To expose a NodeInfo endpoint, you need to register a NodeInfo dispatcher with Federation.setNodeInfoDispatcher() method. The following shows how to expose a NodeInfo endpoint:

typescript

import { createFederation
 } from "@fedify/fedify";

const federation
 = createFederation
({
  // Omitted for brevity; see the related section for details.
});

federation
.setNodeInfoDispatcher
("/nodeinfo/2.1", async (ctx
) => {
  return {
    software
: {
      name
: "your-software-name",  // Lowercase, digits, and hyphens only.
      version
: { major
: 1, minor
: 0, patch
: 0 },
      homepage
: new URL
("https://your-software.com/"),
    },
    protocols
: ["activitypub"],
    usage
: {
      // Usage statistics is hard-coded here for demonstration purposes.
      // You should replace these with real statistics:
      users
: { total
: 100, activeHalfyear
: 50, activeMonth
: 20 },
      localPosts
: 1000,
      localComments
: 2000,
    }
  }
});

For details about the NodeInfo interface, see the next section.

TIP

You don't have to use /nodeinfo/2.1 as the path, but it is quite common among ActivityPub servers.

NOTE

Whether or not you expose a NodeInfo endpoint, /.well-known/nodeinfo is automatically handled by Federation.fetch() method. In case you don't register a NodeInfo dispatcher, Fedify will respond with an empty links array, e.g.:

json

{
  "links": []
}

NodeInfo schema

The NodeInfo interface is defined as follows:

software.name: Required. The canonical name of the server software. This must comply with pattern /^[a-z0-9-]+$/.
software.version: Required. The version of the server software. This must be a valid SemVer object. For your information, a Semantic Versioning string can be parsed into a SemVer object using parse() function.
software.repository: The URL of the source code repository of the server software.
software.homepage: The URL of the homepage of the server software.
protocols: Required and non-empty. The protocols supported on the server. At least one protocol must be supported. You usually put ["activitypub"] here.
services.inbound: The third party sites the server can retrieve messages from for combined display with regular traffic.
services.outbound: The third party sites the server can publish messages to on the behalf of a user.
openRegistrations: Whether the server allows open self-registration. Defaults to false.
usage.users.total: The total amount of on the server registered users. This number has to be an integer greater than or equal to zero.
usage.users.activeHalfyear: The amount of users that signed in at least once in the last 180 days. This number has to be an integer greater than or equal to zero.
usage.users.activeMonth: The amount of users that signed in at least once in the last 30 days. This number has to be an integer greater than or equal to zero.
usage.localPosts: The amount of posts that were made by users that are registered on the server. This number has to be an integer greater than or equal to zero.
usage.localComments: The amount of comments that were made by users that are registered on the server. This number has to be an integer greater than or equal to zero.

NodeInfo ​

Exposing NodeInfo endpoint ​

NodeInfo schema ​

NodeInfo

Exposing NodeInfo endpoint

NodeInfo schema