kb-fediverse-webfinger-discovery

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

9|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-webfinger-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-fediverse-webfinger-discovery
Source: https://github.com/reiver/vibefed/tree/main/skills/kb-fediverse-webfinger-discovery
Command: npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-webfinger-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of reliably determining a user's human-readable WebFinger address (like [email protected]) when only their ActivityPub actor URL is known, a process that is currently inconsistent across the Fediverse.

Core Features & Use Cases

  • Reverse Discovery: Implements FEP-2c59 to find a WebFinger address from an actor URL.
  • Handles Domain Mismatch: Correctly identifies WebFinger addresses when they are on a different domain than the ActivityPub server.
  • Validation: Ensures the discovered WebFinger address correctly resolves back to the original actor URL without redirects.
  • Use Case: When you have a link to a user's profile on a social platform and need to find their [email protected] handle for cross-platform interactions or identity verification.

Quick Start

Explain how to use the kb-fediverse-webfinger-discovery skill to find the WebFinger address for an actor URL.

Frequently Asked Questions about kb-fediverse-webfinger-discovery

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

FAQPage Schema
How do I find a WebFinger handle from an ActivityPub actor URL?

To find a WebFinger handle from an ActivityPub actor URL, you use reverse WebFinger discovery defined in FEP-2c59. This resolves the actor URL to its corresponding human-readable WebFinger address, ensuring reliable cross-platform identity verification.

What is FEP-2c59 and how does it relate to WebFinger discovery?

FEP-2c59 is a Fediverse Enhancement Proposal that standardizes reverse WebFinger discovery. It defines the `webfinger` property used to resolve ActivityPub actor URLs back to their corresponding WebFinger addresses, addressing inconsistencies across different platforms.

How do I handle domain mismatches between ActivityPub servers and WebFinger addresses?

Handling domain mismatches requires checking the `webfinger` property on the actor URL to correctly identify WebFinger addresses hosted on a different domain than the ActivityPub server. FEP-2c59 provides the mechanism to bridge these cross-domain identity scenarios.

How do I validate a discovered WebFinger address?

Validating a discovered WebFinger address involves resolving it back to the original ActivityPub actor URL. The validation ensures the discovered address correctly resolves without redirects, confirming the identity link is legitimate and unbroken.

Does Mastodon support FEP-2c59 for reverse WebFinger discovery?

Mastodon currently uses its own approach to WebFinger discovery rather than strictly implementing FEP-2c59. This Skill analyzes Mastodon's current method and highlights ongoing community debates regarding alternative solutions for resolving actor URLs.