Project · developer module
peer-status
- How you run it
- not recorded
- Holochain version
- 0.2.3
- Activity
- stalled
- Checked
- 27 October 2026
What is peer-status and what is it for?
peer-status is a small reusable module for Holochain apps that shows whether a participant is online, offline or busy. It exists so an app can display that presence without building the feature itself.
peer-status is a small reusable module that adds an online, offline or busy indicator for people in a Holochain app. A Holochain app is built from a shared backend — a DNA — plus an interface, and peer-status ships both halves: a zome that goes into an app's DNA, and a package of web components for the front end. Its README describes it as designed to be included in other apps while assuming as little as possible about them.
For a developer, the point is not to reinvent presence. Rather than each app working out its own way to show who is reachable, peer-status offers one module that keeps each participant's status in the shared state of the DNA it is added to, alongside interface pieces that can be dropped into a page. The README records one deliberate limit: the status lives in the app that includes the module, and linking it to separate profiles or persona data was left as future work.
A concrete case: an app that includes the module can show, beside a participant's name, whether they are currently online or busy, and a participant can set that state themselves. To learn more, the repository README links to installation instructions, module documentation and a developer setup guide. hAppRadar records the repository's activity as stalled, with its last push in May 2024 and no published releases, so this should be read as a historical module rather than software known to be maintained now.
How to get it
As a library
- peer-status is not a standalone app: it is a zome and a frontend module designed to be included in an existing Holochain app.
- The repository README points to the module's installation instructions, its documentation and a developer setup guide for adding the zome and the frontend module to an application.
Questions people ask
- Does peer-status run on its own?
- No. It is designed to be included inside another Holochain app's DNA, and the README says it assumes as little as possible from the app it is added to. source
- Where is a person's status kept?
- In the DNA of the app that includes the module; the README notes that bridging it with separate profiles and persona data was left as future work. source
- Is peer-status maintained today?
- hAppRadar records its activity as stalled, with no published releases and a last push in May 2024, so it should be treated as a historical module rather than software known to be maintained now. source
From 2 public sources, checked 23 September 2026.
Try peer-status
- Code on GitHubOpen on GitHub ↗Last change 8 May 2024.
- ReleaseNo GitHub release recorded.
- The project's own files do not say how it is run.
Details & sources
Evidence
- Last change
- api.github.com/repos/holochain-open-dev/peer-statuslisted by a third party · seen since 20 October 2026 · github.repository@1
- Activity
- api.github.com/repos/holochain-open-dev/peer-statuslisted by a third party · seen since 20 October 2026 · liveness@1
Compatibility
- hdk
- 0.2.3 · Cargo.toml @ 901af1d
- hdi
- 0.3.3 · Cargo.toml @ 901af1d
- holochain-client
- 0.16.0 · ui/package.json @ 901af1d
- happ.yaml
- absent
- web-happ.yaml
- absent