ITT I give a brief introduction to Matrix on eom.dev and provide basic instructions to get started using the protocol. Reply to this thread with general thoughts, feedback, and questions about Matrix on eom.dev.
Matrix is an open protocol for decentralised, secure communications.
We believe:
People should have full control over their own communication.
People should not be locked into centralised communication silos, but instead be free to pick who they choose to host their communication without limiting who they can reach.
The ability to converse securely and privately is a basic human right.
Communication should be available to everyone as a free and open, unencumbered, standard and global network.
TLDR: Matrix is open-source instant messaging with encryption and account federation.
Clients provide the best interface for accessing Matrix. Element on eom.dev is available for convenience.
Accounts
Matrix accounts are similar to email addresses in that a user on one domain may send messages to users on any other domain. On the Matrix protocol, this is referred to as federation.
Users may create an eom.dev Matrix account using single-sign on with Google on Element, or by setting their homeserver address to eom.dev in the client of their choosing.
Users may also consider creating a Matrix account with one of many other providers.
Rooms
An account with any Matrix provider will allow you to access public rooms on eom.dev:
Main space for Matrix rooms. General discussions and community introductions. Help with eom.dev services.
I have been asking people to use the reply in thread feature on the Matrix server, so I wanted to clarify how I am intending to organize these chats. First of all, these are not rules, it is OK to not do this “correctly”, though I may point people back to this post so we are all on the same page about how we want to use the platform. I may also remove messages for this reason, but only for organizational purposes. Additionally, this is open for discussion, so if you have suggestions on how we can improve our use of the service, please offer your perspective in the thread.
Generally speaking, we should use threads to discuss a single topic and we should create new threads if/when the topic changes. Within a thread, the reply feature can be used to reference a specific message in the same thread. I have noticed users often go to reply before reply in thread, but doing so does not allow for this second layer of organization.
TL;DR:
Default to using reply in thread.
If in a thread, use reply to reference specific messages in the same thread.
Do not change the subject of a thread. Create a new threads for new topics.
Kindly link newcomers to this post when necessary.
Please leave a reply with any questions, comments, or suggestions!
A couple of weeks ago, a hardware failure caused a major outage on the main Matrix homeserver. My deployment was unaffected (save for matrix.org users being unavailable for a period of time), but I thought I would make note of it here. Between this and continued difficulty creating bots for the platform, I am considering supplementing the network with another protocol.
Voice and video calls have been functional on the Matrix server for a couple of weeks now; however, I have not done an announcement about it on Discourse until now as it was still being tested. It was deployed using a task file in the ansible-role-eom repository, and should be moved to its own Ansible role in the future. MatrixRTC is still not fully functional, so only the legacy call features are supported on eom.dev at this time. I may seek to implement the newer Element Call feature; however, the desired functionality is available through Coturn, so this will not be a high priority.
I imagine this will primarily be used to supply voice chat for Gaming events (at least initially); however, the long-term vision for this feature is to host meetings for Projects.
ITT I give a brief introduction to Matrix on eom.dev and provide basic instructions to get started using the protocol. Reply to this thread with general thoughts, feedback, and questions about Matrix on eom.dev.
Clients provide the best interface for accessing Matrix.
Element on eom.dev is available for convenience.
Main space for Matrix rooms.
General discussions and community introductions.
Help with eom.dev services.