Earde
Explore EardeConnect a project
The community platform for open source

A shared home for open-source communities.

Live chat, searchable forums, and canonical discussions shared across related project communities.

Open web · no account required

Public discussions are indexed by search engines and readable without an account.

Connect a projectExplore Earde
A durable thread in the Northstar community, marked shared with Rivet.The live #general channel in the Northstar community.The Earde feed: live activity and durable knowledge across the communities you follow.

What Earde does today

01

Build a community around your GitHub repo.

Verify a repository you maintain through GitHub, choose how the project should belong on Earde, and publish a real community home around it.

The freshly created Mithril community home: one section, no threads yet, one live channel, and its network panel.tolwiz/Mithril verified through GitHub, with the project details that decide how it belongs on Earde.Choosing which public repositories verified through GitHub belong to the Earde project, including tolwiz/Mithril.
02

Share a discussion with a connected project community.

An existing discussion can be shared with a connected project community. Its moderators decide whether to accept it, and where it belongs.

Rivet's Shared threads settings, where its own moderators accept or reject the incoming request from Northstar and choose the destination section.The Share thread page in Northstar: pick Rivet as the connected community and add a private note for its moderators.
03

Create a shared discussion from the start.

Choose a connected project community while creating a thread. Once accepted there, both communities participate in the same canonical discussion and comment tree.

The same thread, Should resume tokens be single-use across transport handoffs?, open in Northstar and marked shared from Rivet.The New thread composer in Rivet, with the Share with a connected community field set to Northstar and a private request note.

How Earde compares

CapabilityDiscordDiscourseZulipEarde
Live chatYesYesYesYes
Searchable forumsNoYesPartialYes
GitHub-backedNoNoNoYes
Community connectionsNoNoNoYes
Shared threadsNoNoNoYes
Mobile appYesYesYesIncoming
Voice / videoYesNoNoIncoming
Connected communities

Codebases have relationships.Their communities should too.

Open-source projects depend on one another, but their communities still live as isolated spaces. Earde gives related project communities explicit relationships without merging their identity, moderation, or governance.

PLANNEDNot built yet.

Turn a settled discussion into a GitHub issue.

The maintainer decides every time, and the issue keeps a link back to the discussion it came from.

Also plannedBug reportFeature requestDocumentation draft
/c/dream / § questions / thread
Canonical · shared with /c/ocaml
How should cancellation be handled in Lwt applications?
14 comments · accepted answer from u/raphael-proust
Create GitHub issue
aantron/dream · Issues
OpenClarify cancellation semantics for Lwt handlers#412
Handlers that own a resource should wrap the body in Lwt.finalize and re-raise Lwt.Canceled after cleanup.
↩ earde.org/c/dream/questions/lwt-cancellation

Build a community around your GitHub repo.

Live chat, searchable forums, and canonical discussions shared across related project communities.

Connect a projectExplore Earde