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

kb-fediverse-actor-statuses

Explain FEP-82f6 for ActivityPub actor statuses with ActorStatus object details.

9|Updated Mar 12, 2026
Search Tags:#fediverse#activitypub#json-ld#fep-82f6#actor status#profile text
One-click install
npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-actor-statuses
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kb-fediverse-actor-statuses
Source: https://github.com/reiver/vibefed/tree/main/skills/kb-fediverse-actor-statuses
Command: npx skills add https://github.com/reiver/vibefed --skill kb-fediverse-actor-statuses

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive knowledge on implementing and understanding a standardized way for ActivityPub actors to display short, non-interactable status messages on their profiles, complete with optional expiration and metadata.

Core Features & Use Cases

  • FEP-82f6 Understanding: Deep dive into the ActivityPub extension for actor statuses.
  • Implementation Details: Covers ActorStatus object structure, actor fields (status, statusHistory), and associated activities (Create, Remove, Delete).
  • Use Case: A developer building a federated social network needs to implement a "custom status" feature similar to Discord or GitHub profiles. This Skill provides all the necessary technical specifications and ActivityPub protocol details.

Quick Start

Explain the FEP-82f6 standard for ActivityPub actor statuses.

Frequently Asked Questions about kb-fediverse-actor-statuses

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

FAQPage Schema
How do I implement custom profile status text for ActivityPub actors in a federated social network?▼

The ActorStatus object in FEP-82f6 manages profile status text by defining actor fields like status and statusHistory. It handles state transitions using associated activities such as Create, Remove, and Delete to update or clear the profile status.

What is the FEP-82f6 standard for ActivityPub actor statuses?▼

FEP-82f6 distinguishes itself by defining a standardized, non-interactable ActorStatus object with optional expiration and metadata, explicitly comparing its design philosophy against centralized platform statuses and rejecting alternative implementations to ensure protocol consistency.

Does FEP-82f6 support status expiration and metadata for ActivityPub profiles?▼

You need to understand the JSON-LD context and character limits defined by FEP-82f6 to properly format ActorStatus objects. This ensures your ActivityPub profile status implementation correctly serializes data and respects the protocol's length constraints.

What are the limitations of using FEP-82f6 for ActivityPub actor statuses?▼

FEP-82f6 is limited to non-interactable status text, meaning it does not support direct replies or interactions like standard posts. It is specifically designed for short profile messages with optional metadata and expiration rather than full content federation.

Related Skills

Explore More Software Engineering Skills→
reiverreiver
9

kb-lemmy

Explain Lemmy's ActivityPub federation, including Group actors and voting mechanisms.

Community
Advanced
reiverreiver
9

kb-fediverse-json-ld

Explain JSON-LD processing and value variability in ActivityPub.

Community
Intermediate
reiverreiver
9

kb-mbin

Explain Mbin's ActivityPub implementation, actor types, and message processing architecture.

Community
Advanced
reiverreiver
9

kb-fediverse-portable-objects

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

Community
Advanced