First let's break it down what it means to be federated,
pluggable and a message-exchange protocol. By federated
we
mean that Bester operates in a similar network topology to that
of e-mail or XMPP whereby users registered on one
server can interact with those registered on another. By pluggable
we are implying that Bester is a generalized protocol
that supports sub-protocols that can run on top of it to handle
different message types and that these "handlers" are
separate processes communicated with via IPC. And last but not
least, message-exchange, this is pretty obvious, it's
a network for exchanging messages, what these messages are is up
to the developer writing a sub-protocol to run
on top of a Bester-based network.
Downloads available below (for the daemon).
Architecture |
Version |
Download link |
x86_64 |
v0.0.11 |
https://github.com/besterprotocol/besterd/releases/tag/v.0.0.11 |
Architecture | Name |
Description |
Repository |
x86_64 |
besterd |
bester daemon, serves the protocol |
https://github.com/besterprotocol/besterd |
x86_64 | libester |
D library for interacting with bester
servers, sending and receiving of messages |
https://github.com/besterprotocol/libester |