Displaying 1 to 4 from 4 results

braid - Braid is a team-chat app with a novel UI that leads to better conversations.

  •    Clojure

Braid is an experimental team chat application with a novel UI: instead of chatrooms, it's based on many short conversations. You can think of Braid as an email/mailing-list/web-forum/chatroom hybrid, but without the constant interruptions and FOMO of Slack. It's particularly good for remote-first companies, developer teams and online communities. Braid is also open-source, so you can hack on it and host your own version. You can read more about Braid and then give Braid a try.

Friends - P2P chat powered by the web

  •    Javascript

Friends is like Slack except P2P, offline friendly and open source. Data is transmitted over secure channels and messages are authenticated. It is made by a group of open source developers who are motivated to make a public chat platform that is easy to use but isn't centrally controlled, and where data is owned by its users.

Rocket.Chat.Apps-ts-definition - The Rocket.Chat Apps TypeScript definition.

  •    TypeScript

Handlers are essentially "listeners" for different events, except there are various ways to handle an event. When something happens there is pre and post handlers. The set of pre handlers happens before the event is finalized. The set of post handlers happens after the event is finalized. With that said, the rule of thumb is that if you are going to modify, extend, or change the data backing the event then that should be done in the pre handlers. If you are simply wanting to listen for when something happens and not modify anything, then the post is the way to go. To update or generate the documentation, please commit your changes first and then in a second commit provide the updated documentation.

Rocket.Chat.Apps-engine - The Rocket.Chat Apps engine and definitions.

  •    TypeScript

The engine which manages and controls everything....more details coming soon. Handlers are essentially "listeners" for different events, except there are various ways to handle an event. When something happens there is pre and post handlers. The set of pre handlers happens before the event is finalized. The set of post handlers happens after the event is finalized. With that said, the rule of thumb is that if you are going to modify, extend, or change the data backing the event then that should be done in the pre handlers. If you are simply wanting to listen for when something happens and not modify anything, then the post is the way to go.