skills.rest
reiver
reiverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

kb-fediverse-nodeinfo-extensions

Explain Fediverse capability discovery via NodeInfo and FEPs.

9|Updated Mar 12, 2026
Search Tags:#interoperability#fediverse#activitypub#nodeinfo#capability discovery#fep
One-click install
npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-nodeinfo-extensions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kb-fediverse-nodeinfo-extensions
Source: https://github.com/reiver/vibefed/tree/main/skills/kb-fediverse-nodeinfo-extensions
Command: npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-nodeinfo-extensions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps understand how Fediverse servers advertise their supported features and extensions, addressing the challenge of interoperability and feature discovery in a decentralized network.

Core Features & Use Cases

  • Capability Discovery: Learn how servers declare support for ActivityPub extensions and custom types.
  • Protocol Analysis: Understand NodeInfo, FEP-6481, FEP-9fde, and related proposals for feature negotiation.
  • Use Case: When integrating a new Fediverse application, use this Skill to determine what specific ActivityPub extensions a target server supports, ensuring smooth communication and feature compatibility.

Quick Start

Explain how Fediverse servers advertise support for custom ActivityPub extensions.

Frequently Asked Questions about kb-fediverse-nodeinfo-extensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover Fediverse server capabilities and supported ActivityPub extensions?▼

NodeInfo and related FEPs like FEP-6481 provide the mechanism for Fediverse capability discovery. Servers use these protocols to declare supported ActivityPub extensions and custom types, enabling clients to verify feature compatibility before interaction.

What is the difference between using custom types and extending standard ActivityStreams vocabulary in the Fediverse?▼

The debate centers on whether to use custom types or extend the standard ActivityStreams vocabulary. This Skill covers FEP-67ff and other proposals, detailing how NodeInfo metadata advertises these choices to ensure correct feature negotiation and capability discovery across servers.

How do Fediverse servers advertise support for custom ActivityPub extensions via NodeInfo?▼

Servers advertise custom ActivityPub extension support by exposing NodeInfo protocol versions and metadata. This Skill outlines implementation guidance for advertising server capabilities, referencing FEP-844e and FEP-eb22 to ensure proper feature discovery and decentralized network interoperability.

Which FEPs should I implement for NodeInfo capability discovery?▼

You should implement FEP-6481, FEP-9fde, FEP-eb22, FEP-844e, and FEP-67ff for NodeInfo capability discovery. This Skill provides background on these proposals, explaining how they handle metadata, protocol versions, and feature negotiation in the Fediverse.

Are there precedents for NodeInfo capability discovery outside of ActivityPub?▼

Yes, XMPP precedents exist for capability discovery. This Skill addresses these precedents to provide context for how Fediverse servers negotiate features, offering implementation guidance for advertising and checking server capabilities via NodeInfo and related FEPs.

Related Skills

Explore More Software Engineering Skills→
fedify-devfedify-dev
1.0k

add-vocab

Add ActivityPub/JSON-LD vocabulary types via YAML definitions and codegen.

Official
Intermediate
reiverreiver
9

kb-fediverse-portable-objects

Explain FEP-ef61 for server-independent ActivityPub object identities using ap:// URIs and DIDs.

Community
Advanced
rnavarychrnavarych
14

domain-iot:iot-security

Secure IoT devices with X.509 certificates, TLS/DTLS, and secure boot.

Community
Advanced
reiverreiver
9

kb-fediverse-webfinger-discovery

Resolve ActivityPub actor URLs to WebFinger addresses via FEP-2c59.

Community
Intermediate