@@ 1,14 1,16 @@
# What is Arbor?
## What is Arbor?
Arbor is an open-source chat collaboration system that thinks a little differently about conversations. Arbor captures more of the context of messages than traditional chat, allowing you and your peers to communicate more clearly with less effort.
# Why is it called Arbor?
## Why is it called Arbor?
An arbor is an artificial structure that supports the growth of climbing vines in a garden. Arbor is an artificial structure for chat that helps conversation flourish.
# How is it different?
## How is it different?
Arbor messages track what you were responding to when you wrote them. Every message explicitly has a "parent" message that it is a response to. This allows Arbor to visualize the relationships between messages for its users in a way that other chat systems cannot. This makes your conversation history into a [tree](https://en.wikipedia.org/wiki/Tree_(data_structure)) instead of a list.
@@ 18,6 20,8 @@ If you think about it, most things you say in a conversation are a response to w
Arbor started in February 2018 as a wacky idea. We implemented a proof-of-concept system that embodies chat as a tree over the course of the next ten months, and we were really pleased by the results. However, this system had some serious flaws due to its proof-of-concept nature. It had no security, and no good way to build security. We've started over, but this time we're building something serious. It takes a lot of work to build a secure communication platform from the ground up, so it's slow going.
For the new implementation, we have these components built:
- [forest-go](https://git.sr.ht/~whereswaldon/forest-go): a library for creating and manipulating messages (nodes) in the Arbor system
@@ 33,3 37,32 @@ For our proof-of-concept implementation, there is:
- [ivy](https://github.com/arborchat/ivy): an old test client
- [pergola](https://github.com/arborchat/pergola): the first arbor chat client; has a terrible UX
- [yggdrasil](https://github.com/arborchat/yggdrasil): an arbor chat client in C
## Get Involved
If you'd like to keep up with what's going on in Arbor or to help us build it, you can:
- Join our [mailing list](https://lists.sr.ht/~whereswaldon/arbor-dev)
Who do we need?
- Developers: right now, there's a mountain of code that we need to right before the new implementation can go live. If you want to get involved, we're happy to have you. Many design decisions have not yet been made, and there's a lot of opportunity to shape the direction of the project.
Who will we need?
- Users: just using Arbor and telling us what you think about it is immeasurably valuable
- Designers: it's easy to build a capable tool that is crippled by a terrible user experience. We could really use people who can help us avoid that pitfall. Additionally, there's a lot of space for innovation in tree-based chat. There aren't many user interfaces like this, and we think some really cool things are possible.
## Where did the logo come from?
The inspiration for the logo was a sketch by Katerina Waldon. Chris Waldon hacked together the current one in Inkscape.
## Why is some stuff on GitHub and some stuff on SourceHut?
When the project started, we didn't know sourcehut existed. We really like some of the ideas behind sourcehut, and we're trying it out for the time being as a possible permanent home for the project. We will try to mirror all of our code back to GitHub to make it all easy to find though.
## Why make a new chat application? Isn't the market saturated enough?
Sure; there are hundreds of other applications that do chat, and many of them are very good tools. Arbor's goal is to address some shortcomings that we see in existing chat platforms.