PROVIDER - Federated discussion platform
Lemmy
Lemmy turns link aggregation and discussion into a federated platform on ActivityPub, where one instance hosts communities and voting while interoperating with Mastodon and the wider fediverse. It suits teams that want to own their community data outright.
3.7pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
Lemmy appeared around 2019, initiated by the LemmyNet community, with join-lemmy.org as its home, source hosted on GitHub under AGPL-3.0, and a Rust backend on PostgreSQL. Its shape is link aggregation plus discussion: people post links or text, others vote on a score and reply in threads. Structurally it resembles early Reddit, but underneath it runs the ActivityPub federation protocol.
Within the Community & Forum category it is one of the few products that treats federation as a core design rather than an optional add-on. Content is organised in three layers: the instance is the deployment unit, the community is the topic unit, and posts plus comments are the content unit. Communities can be subscribed across instances, and a single account sees continuous discussion across instances, which is why it belongs to the fediverse, where it can like, reply and boost alongside Mastodon and Misskey.
The payoff is data sovereignty and resistance to single points of failure: community data stays on servers you control and accounts do not belong to a commercial platform. The price is complexity pushed onto users and operators, because federation links take time to establish, instance blocklists differ, and a self-hosted instance needs public HTTPS, a working domain, SMTP and image storage before delivery and signup verification behave.
Key Strengths
- Federated by default: ActivityPub lets instances subscribe to and interact with Mastodon, Misskey and Pleroma communities, so 1 account spans multiple servers without duplicate registrations.
- Clean three-layer model: instances host communities, communities host posts and comments, and each community sets its own rules and moderators, with cross-instance subscriptions acting as follows and keeping migration costs low.
- Manageable footprint: a Rust backend on PostgreSQL avoids middleware sprawl, so 1 mid-sized server carries a community with tens of thousands of daily users.
- Complete API: JSON endpoints cover login, posting, commenting, voting and messaging, and both official and third-party mobile clients use them, so automation and analysis need no scraping.
- Data ownership: AGPL-3.0 licensing with no fees, a database you control, and exports and backups that no platform can block, which matters to technical communities sensitive about content ownership.
Product Ecosystem
Platform capabilities
Communities carry a name, description, icon, banner and rules, and admins decide whether posting is open or moderated. Posts support links, text and images, comments nest and take votes, and the score drives ordering. Moderation offers report queues, bans, instance-level blocklists and keyword filters, while the federation layer can block an entire instance. Direct messages and notifications run through the internal messaging system, with email requiring SMTP.
Integrations
Federation is the widest integration surface, since any ActivityPub-capable service can interoperate, and microblog boosts and forum subscriptions unify at the protocol level. Image handling usually delegates to pict-rs with object storage, authentication can ride on OAuth or third-party login, monitoring typically uses Prometheus with log shipping, and analytics read from the API or a read-only PostgreSQL replica.
Typical scenarios
Self-hosted discussion for technical communities, open source projects replacing a Reddit-style subreddit, independent discussion spaces for media or podcasts, internal knowledge communities, and brand communities that want fediverse reach.
Limitations
- Federation sync lags, edits and deletes do not reach every instance immediately, and consistency of older content needs manual judgement.
- Self-hosting overhead is real, since public HTTPS, a domain, SMTP, image storage and database migrations are all mandatory, and thin operations experience shows up as failed federation delivery.
- Cross-instance discovery is weak, remote communities only appear after a local search, and the missing global index leaves new instances looking empty.
- Interface and copy localisation for Chinese is still in progress, Chinese operational material is thinner than English, and federation incidents usually end up in upstream code discussions.
Use Cases
- Technical communities and open source projects (★★★★☆) - Communities plus voting sort technical topics well, and the federated model matches open source expectations about data.
- Brand or media communities that want ownership (★★★☆) - A self-hosted instance keeps every post and relationship, at the cost of operations and compliance work.
- Campaigns that need fediverse reach (★★★☆) - ActivityPub carries discussion into the Mastodon ecosystem and widens organic reach.
- Non-technical teams needing a fast launch (★★) - Deployment and federation debugging need operational skill, and a managed SaaS forum is less work.
- Strictly moderated compliance environments (★★☆) - Moderation tools are adequate, but inbound federated content cannot be fully controlled without extra policy.
Pricing
| Item | Price | Notes |
|---|---|---|
| Lemmy software | Free | AGPL-3.0, public source, no licence fee |
| Server and bandwidth | Provider rate | 2 vCPU and 4 GB is a sensible floor, images and federation traffic dominate the bill |
| Domain and TLS certificate | Annual fee | Federation requires a publicly reachable HTTPS domain, free certificates are accepted |
| Email and object storage | Usage based | SMTP handles verification and notifications, images can live in object storage |
The software itself is free, so total cost equals server plus domain plus email plus maintenance hours. Federation traffic is the hidden line item: the more remote communities an instance subscribes to, the more posts and images it pulls, and bandwidth plus storage scale with subscription count.
FAQ
How does Lemmy relate to Mastodon?
Both use ActivityPub and belong to the same fediverse, but Mastodon is microblogging while Lemmy is community-based discussion. They can follow and reply to each other even though content is organised differently.
What does a self-hosted instance require?
A publicly reachable domain with HTTPS, PostgreSQL, image storage and a working SMTP relay, plus the discipline to run database migrations. If the domain or certificate is unreachable, federation delivery essentially fails.
Can one account join many communities?
Yes. Register on any instance, then search for and subscribe to communities elsewhere. The local instance hosts the account and a cache while content originates on the source instance.
Do deleted posts disappear from other instances?
Not reliably. A delete is broadcast as a federated activity, but peer instances may ignore it because of version differences, policy or network issues, so some copies usually survive.
Code Examples
Log in through the API and publish a post
export LEMMY_URL="https://lemmy.example.com"
export LEMMY_USER="$LEMMY_USERNAME"
export LEMMY_PASS="$LEMMY_PASSWORD"
export COMMUNITY_ID="2" # community id, visible in the community URL or API
# Exchange credentials for a JWT, sent in the Authorization header afterwards
TOKEN=$(curl -s -X POST "$LEMMY_URL/api/v3/user/login" \
-H "Content-Type: application/json" \
-d "{\"username_or_email\":\"$LEMMY_USER\",\"password\":\"$LEMMY_PASS\"}" \
| jq -r '.jwt')
# Publish a text post; use the url field instead for link posts
curl -s -X POST "$LEMMY_URL/api/v3/post" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{\"name\":\"Weekly notes are updated\",\"body\":\"Progress is in the body.\",\"community_id\":$COMMUNITY_ID}" \
| jq '{post_view: .post_view.post.id}'
JWTs expire, so long-running scripts must log in again on 401 instead of reusing one token forever.
Start a minimal instance with Compose
# docker-compose.yml: inject variables from .env and never commit plaintext secrets
services:
lemmy:
image: dessalines/lemmy:latest
restart: always
environment:
LEMMY_CONFIG_LOCATION: /config/config.hjson
volumes:
- ./lemmy.hjson:/config/config.hjson:ro
depends_on:
- postgres
- pictrs
ports:
- "8536:8536"
postgres:
image: postgres:16-alpine
restart: always
environment:
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
volumes:
- ./volumes/postgres:/var/lib/postgresql/data
pictrs:
image: asonix/pictrs:latest
restart: always
environment:
PICTRS__SERVER__API_KEY: ${PICTRS_API_KEY}
volumes:
- ./volumes/pictrs:/mnt
The hostname in config.hjson must be the externally reachable domain, and leaving it as localhost breaks every federated delivery. Back up PostgreSQL before pulling a new image and run the documented migrations.
Community & Resources
Communities and official channels
- Lemmy — Instance directory, client recommendations and project overview
- Lemmy documentation — Self-hosting guides, configuration keys and federation notes
- Lemmy repository — Source code, issues and release changelogs
- ActivityPub specification — The W3C standard behind the federation protocol
Learning resources and tools
- Lemmy API reference — HTTP endpoint documentation organised by resource
- pict-rs project — Configuration reference for the image proxy and storage service