Skip to main content

Matrix Channel

·306 words·2 mins

The last months I played around with Matrix, a secure and open collaboration system. The protocol looks very promising, it allows hosting your own server and federate it to other systems. So like SMTP, all these matrix users can communicate to each other.

This is Matrix.
#

Matrix is an open source project that publishes the Matrix open standard for secure, decentralised, real-time communication, and its Apache licensed reference implementations.

Maintained by the non-profit Matrix.org Foundation, we aim to create an open platform which is as independent, vibrant and evolving as the Web itself… but for communication.

As of June 2019, Matrix is out of beta, and the protocol is fully suitable for production usage. https://matrix.org/

Matrix Homepage

I registered a user at nope.chat, and you can reach me at @stoeps:nope.chat.

Why did I start using Matrix?

  • My first group which I joined and reason for registering a Matrix account was the Tilpod matrix chat
  • Fosdem 2022 hosted the online conference with Matrix and Jitsi and handled up to 23000 users
  • All messages are encrypted, the clients and protocol is Open Source
  • Bridges are available to integrate other collaboration protocols like Discord, Whatsapp, Skype and Slack (any many more)
  • Clients for most OS are available to use Matrix for Android, iOS, Web browser, Desktop and so on.

So I hope that whenever I want to change to another collaboration system, I don’t loose messages again.

Like the Tilpod group, I created a new group to discuss things around HCL Connections, the group is public, and you’re open to join at any time.

When you follow the link, it provides you with all steps to join with your own Matrix instance, or with the web client.

If anybody wants to test the bridge to Discord, I’m happy to help set up something like https://t2bot.io/discord/.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

Install All Packages After Restore on RPM-based Linux

·301 words·2 mins
In the last days I had a problem with a crashed virtual disk on a WebSphere Application Server. The backup team was able to recover all the data, but the operating system needs to be reinstalled. The operating system was Red Hat Linux, so rpm-based. One of the first tasks after recovery was to identify and reinstall missing packages.

Asciidoctor Windows

During my talk at FrOSCon I wasn’t sure how to install Asciidoctor on Windows. So I tried on a Windows 10 VM. When you want to use Asciidoctor on a Windows desktop, you need to download the Rubyinstaller and install it. Now you can open a administrative command window and install with gem install asciidoctor.

Update Elasticsearch certificates in Componentpack

Elasticsearch in HCL Connections Componentpack is secured with Searchguard and needs certificates to work properly. These certificates are generated by bootstrap during the initial container deployment with helm. These certificates are valid for 10 years (chain_ca.pem) or 2 years (elasticsearch*.pem) and stored in the Kubernetes secrets elasticsearch-secret, elasticsearch-7-secret. So when your HCL Connections deployment is running for 2 years, the certficates stop working.