@OvermindDL1 Yes!, Here are some additional details…
Architecture Notes
- Elixir & Phoenix Backend
- Light JS frontend
- After initial page load, channels are used for UI rendering. HTML is rendered on the server and pushed to the client over channel
- Originally build as a stand-a-lone single app.
- In the process of refactoring it to be extensible through plugins
- We will be using it for a client framework with initial support for the chat app and our commercial WebRTC soft phone (delivered as a plugin)
Current Features Implemented
- Multiple channel types (public, private, direct messages)
- Favourite channels
- @mentions with audible and badge notifications
- Presence with override
- Message editing, pinning, starring, deleting
- About 30 slash commands (create room, invite user, …)
- Autolink and preview urls
- Drag and drop file update with image and video preview
- Emoji support with picker
- Message reactions
- Unread message handling
- Customizable Role and Permission system
- Some basic Bot experimental support
- Code syntax highlighting
- Profile editing and admin pages
- Very configurable
- and more …
Feature Roadmap
- Peer to peer Video
- Peer to peer Audio
- Presence adapters for on-the-phone presence with Asterisk PBX
- Mobile clients and Push notifications
- Email and SMS notifications
- OTR Conversations
- Live chat feature
- 3rd party integration (web hooks, Rest API)
- BitBucket
- Github
- Jira
- …
- OAuth and LDAP
- XMPP Integration
- Internalization (Much of the UI uses gettext already)
- UI theming
- and more …
