Harmony: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
Development ceased around the 11th of February 2022<ref>https://github.com/harmony-development/scherzo/commit/b9f0ac21f7a79c464a7c84bc4d535be91e71cfc6</ref>. | Development ceased around the 11th of February 2022<ref>https://github.com/harmony-development/scherzo/commit/b9f0ac21f7a79c464a7c84bc4d535be91e71cfc6</ref>. | ||
The harmonyapp.io domain expired on the 18th of December 2022. | |||
{| class="wikitable" | {| class="wikitable" | ||
|+Notable Sub-projects | |+Notable Sub-projects | ||
Latest revision as of 12:16, 3 January 2023
Harmony was an open source federated chat protocol, the developers do not intend to pursue it anymore[1].
Development ceased around the 11th of February 2022[2].
The harmonyapp.io domain expired on the 18th of December 2022.
| Project | Description |
|---|---|
| Challah | A Qt/KF5 client for Harmony |
| ilo toki | A terminal client for Harmony |
| Loqui | Harmony client made with Rust using the egui GUI library |
| Tempest | A web client for Harmony written in Vue |
| Marcato | A Swift-based server for Harmony |
| schzero | A Rust server for Harmony, built using hyper |
| legato | Scalable server implementation for the Harmony protocol (written in Go) |
-
Loqui Client -
Tempest Client -
Harmony's Website -
Harmony's FAQ
hRPC
hRPC is an RPC system using protocol buffers over HTTP and WebSockets[3].
An article was posted in November 2021 explaining the goals and idea behind hRPC[4].
- ↑ https://wiki.rvlt.gg/index.php/File:Harmony_developers%27_stance_on_project.png
- ↑ https://github.com/harmony-development/scherzo/commit/b9f0ac21f7a79c464a7c84bc4d535be91e71cfc6
- ↑ https://github.com/harmony-development/hrpc
- ↑ https://dev.to/harmonydevelopment/introducing-hrpc-a-simple-rpc-system-for-user-facing-apis-16ge
