Telodendria: The terminal branches of an axon.
Telodendria is a Matrix homeserver implementation written from scratch in ANSI C. It is designed to be lightweight and simple, yet functional. Telodendria differentiates itself from other Matrix homeserver implementations because it:
Telodendria is on Matrix! Check out the official Matrix rooms:
Room | Description |
---|---|
#telodendria-releases:bancino.net
|
Get notified of new releases. |
#telodendria-general:bancino.net
|
General discussion and support for Telodendria. |
#telodendria-issues:bancino.net
|
Report issues with Telodendria. |
#telodendria-patches:bancino.net
|
Submit code patches to the Telodendria project. |
Telodendria is distributed as source tarballs, in true Unix
fashion. If you want, you can verify the checksum of your download,
and check the signature. To check the signature, you'll need
signify
, and the signify public key:
telodendria-signify.pub.
If your operating system has an official package or port of Telodendria, you should prefer to use that instead of manually downloading the source and building it. If your operating system's package or port is too out of date for your tastes, please contact the package's maintainers to notify them, or offer to update the package yourself.
Version | Download | Checksum | Signature |
---|---|---|---|
No downloads here yet. See the Project Status for more information. |
You can check out the change log here.
Telodendria's documentation is distributed with the source
code as man
pages, which contain all of the information
on what Telodendria is, what its goals are, how to build the source,
configure it, as well as contribute to the project. The man
pages are also available online for convenience:
Telodendria is a very ambitious project. There's a lot that needs to happen yet before it is usable. At the moment, there's nothing that even remotely ressembles a Matrix homeserver here; I'm still getting off the ground and building a foundation.
But just because there's nothing here yet doesn't mean you should go away! I could always use help, so you are more than welcome to help out if you want things to go quicker. Please see the contributing(7) page for details on how you can get involved.
The Telodendria roadmap is organized into phases, with each phase representing a new milestone in the project's lifetime.
A new open-source project needs a few basic things before development can begin. This phase covers the pre-development stage of Telodendria.
Matrix homeservers require a few prerequisites. In this phase, we build up all the tools required to properly implement a Matrix homeserver. This includes basic data structures, exchange format parsers, and more. We also build up a command line application, multi-threaded HTTP server, and architect a flat-file database framework.
-c file -Vh
)Canonical JSON
\u
escapesWhen the foundations are laid, we can start implementing a real Matrix homeserver. This phase tracks our current progress in implementing the Matrix specification.
/_matrix/client/versions
The Matrix specification is only a part of what it takes to be a production-ready Matrix homeserver. While the spec details how clients and homeservers interact with each other, we still need a way to administer our homeserver. This phase tracks our progress on getting Telodendria packaged, as well as writing some useful administrative tools. Only when these things are completed can we call Telodendria "production-ready."
This documentation needs just a little work. Here's the things on my list for that:
indent(1)
instead.anoncvs
account is just anoncvs
.make.sh
recipes, and what they domsg-error
div)li
elements.div
s for notes and warnings.
Telodendria is designed to be fairly straightforward, but that
doesn't mean there won't be hiccups along the way. If you are struggling
to get Telodendria up and running, you're more than welcome to
reach out for support. Just join the
#telodendria-general:bancino.net
Matrix channel. Before
you do though, make sure you're running the latest version of
Telodendria and you've thoroughly read through all the
relevant documentation.