kb-fediverse-hashtags

Explain Fediverse hashtag implementation across ActivityPub wire format and federation mechanics.

9|Updated Mar 12, 2026

Search Tags:#protocol #federation #fediverse #activitypub #hashtags #mastodon

Ready to run

npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-hashtags

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kb-fediverse-hashtags
Source: https://github.com/reiver/vibefed/tree/main/skills/kb-fediverse-hashtags
Command: npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-hashtags

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill demystifies the complex and often inconsistent world of Fediverse hashtags, enabling developers to correctly implement, detect, and understand hashtag functionality across different platforms.

Core Features & Use Cases

ActivityPub Wire Format: Understand the Hashtag type, its declaration in @context, and its placement within the tag array and content field.
Case Sensitivity & Normalization: Learn how to handle inconsistent capitalization for reliable interoperability.
Federation Mechanics: Grasp why hashtag feeds are server-specific and how relays can expand reach.
Use Case: Debugging why a hashtag search on your Fediverse platform returns incomplete results, or ensuring your platform correctly indexes posts by their tags.

Quick Start

Explain how the tag array and content field must both be populated for correct hashtag federation.

Frequently Asked Questions about kb-fediverse-hashtags

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

FAQPage Schema

How do ActivityPub hashtags work in the Fediverse wire format?▼

ActivityPub hashtags require the `Hashtag` type declared in `@context`, populated in the `tag` array, and integrated into the `content` field to ensure proper federation across Fediverse platforms.

Why are my Fediverse hashtag searches returning incomplete results?▼

Fediverse hashtag feeds are server-specific, meaning your platform only indexes posts it has already received. Federation mechanics limit reach unless activity relays are configured to expand incoming post visibility.

How do I handle case sensitivity when normalizing Fediverse hashtags?▼

Hashtag case sensitivity requires normalization during implementation to handle inconsistent capitalization across different platforms, ensuring reliable interoperability and accurate tag indexing for searches.

Can I follow hashtags directly in ActivityPub like on Mastodon?▼

ActivityPub has hashtag following limitations, meaning you cannot directly subscribe to a tag's feed across the broader Fediverse. Implementing this requires understanding server-specific relay mechanics to aggregate tagged posts.

What are common implementation mistakes when building ActivityPub hashtag federation?▼

Common mistakes include failing to populate both the `tag` array and `content` field simultaneously, mishandling case normalization, and misunderstanding that hashtag feeds are server-specific rather than globally federated.