Background knowledge about Lemmy, the federated link aggregation and discussion platform (Reddit alternative). Covers Lemmy's fundamental architectural decision of Communities as Group actors that automatically Announce all content to followers, the ActivityPub object type mappings (Post as Page with mandatory title, Comment as Note with inReplyTo tree, Community as Group, User as Person, Instance as Application, Private Message as ChatMessage), voting via Like/Dislike activities (unique first-class downvotes unlike most Fediverse platforms), ranking algorithms (Active, Hot, Scaled, Top), the full activity reference (Create/Update/Delete for posts and comments, Follow/Accept for community subscription, Remove/Block/Lock for moderation, Flag for reporting, Announce for community relay), federation modes (allowlist, blocklist, open), custom namespace extensions (stickied, distinguished, commentsEnabled, postingRestrictedToMods), the Lemmy JSON-LD context (join-lemmy.org/context.json), the REST API v3 with JWT auth and pictrs image service, known interoperability issues (name vs preferredUsername reversal, JSON-LD context errors, Mastodon reply propagation failures, vote federation inconsistencies, strict parsing), the tech stack (Rust/Actix-web/Diesel/PostgreSQL backend, TypeScript/Inferno.js frontend, activitypub-federation-rust library), and the Threadiverse ecosystem (Kbin/Mbin, PieFed, Sublinks). Load when the user asks about Lemmy federation; implementing a Lemmy- compatible ActivityPub server; how Lemmy communities work as Group actors; how Lemmy voting federates; Lemmy's Page object type; how posts and comments federate in Lemmy; Lemmy's moderation activities; interoperating with Lemmy instances; the Lemmy API; or the Threadiverse.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Background knowledge about Lemmy, the federated link aggregation and discussion platform (Reddit alternative). Covers Lemmy's fundamental architectural decision of Communities as Group actors that automatically Announce all content to followers, the ActivityPub object type mappings (Post as Page with mandatory title, Comment as Note with inReplyTo tree, Community as Group, User as Person, Instance as Application, Private Message as ChatMessage), voting via Like/Dislike activities (unique first-class downvotes unlike most Fediverse platforms), ranking algorithms (Active, Hot, Scaled, Top), the full activity reference (Create/Update/Delete for posts and comments, Follow/Accept for community subscription, Remove/Block/Lock for moderation, Flag for reporting, Announce for community relay), federation modes (allowlist, blocklist, open), custom namespace extensions (stickied, distinguished, commentsEnabled, postingRestrictedToMods), the Lemmy JSON-LD context (join-lemmy.org/context.json), the REST API v3 with JWT auth and pictrs image service, known interoperability issues (name vs preferredUsername reversal, JSON-LD context errors, Mastodon reply propagation failures, vote federation inconsistencies, strict parsing), the tech stack (Rust/Actix-web/Diesel/PostgreSQL backend, TypeScript/Inferno.js frontend, activitypub-federation-rust library), and the Threadiverse ecosystem (Kbin/Mbin, PieFed, Sublinks). Load when the user asks about Lemmy federation; implementing a Lemmy- compatible ActivityPub server; how Lemmy communities work as Group actors; how Lemmy voting federates; Lemmy's Page object type; how posts and comments federate in Lemmy; Lemmy's moderation activities; interoperating with Lemmy instances; the Lemmy API; or the Threadiverse.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Background knowledge about Lemmy, the federated link aggregation and discussion platform (Reddit alternative). Covers Lemmy's fundamental architectural decision of Communities as Group actors that automatically Announce all content to followers, the ActivityPub object type mappings (Post as Page with mandatory title, Comment as Note with inReplyTo tree, Community as Group, User as Person, Instance as Application, Private Message as ChatMessage), voting via Like/Dislike activities (unique first-class downvotes unlike most Fediverse platforms), ranking algorithms (Active, Hot, Scaled, Top), the full activity reference (Create/Update/Delete for posts and comments, Follow/Accept for community subscription, Remove/Block/Lock for moderation, Flag for reporting, Announce for community relay), federation modes (allowlist, blocklist, open), custom namespace extensions (stickied, distinguished, commentsEnabled, postingRestrictedToMods), the Lemmy JSON-LD context (join-lemmy.org/context.json), the REST API v3 with JWT auth and pictrs image service, known interoperability issues (name vs preferredUsername reversal, JSON-LD context errors, Mastodon reply propagation failures, vote federation inconsistencies, strict parsing), the tech stack (Rust/Actix-web/Diesel/PostgreSQL backend, TypeScript/Inferno.js frontend, activitypub-federation-rust library), and the Threadiverse ecosystem (Kbin/Mbin, PieFed, Sublinks). Load when the user asks about Lemmy federation; implementing a Lemmy- compatible ActivityPub server; how Lemmy communities work as Group actors; how Lemmy voting federates; Lemmy's Page object type; how posts and comments federate in Lemmy; Lemmy's moderation activities; interoperating with Lemmy instances; the Lemmy API; or the Threadiverse.
About this listing
Category
Engineering
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI