Our great sponsors
-
Mattermost
Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Gotify
A simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui) (by gotify)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
By the way, looking at what others have posted on matrix, i would recommend you look at the following project...which is conceptually similar to what we built...but there's is vastly more sophisticated (ours is soooo muich simpler, since we didn't need all that)...but this person's code is great! https://github.com/nim65s/matrix-webhook
Check Mattermost (https://mattermost.com/). I use it for chat, and a channel for notifications.
Does Gotify fit your needs?
There are also webhook to xmpp projects such as https://gitlab.com/navlost.eu/xmpp/components/webhooks and https://github.com/tmsmr/xmpp-webhook
There are also webhook to xmpp projects such as https://gitlab.com/navlost.eu/xmpp/components/webhooks and https://github.com/tmsmr/xmpp-webhook
e-mail to xmpp project (https://github.com/Puppet-Finland/milter-xmpp/)
What we've been doing is to use a python CLI app that we built to post simple messages to a private matrix room. Everyone who needs to see the messages posted there, simply has a mobile matrix client (in our case we use Element, but can be any other matrix client too) and receives the messages. Its just a chat room, so it lacks the sophistication of a threaded ticket management system or anything like that. So, again, any matrix client will more than suffice. We just need the room to capture messages, and in a place that anyone on our team can easily see things (without polluting their email inbox, etc.). But, it fulfills the need quite nicely. Also, since its "just a chat room", you can imagine that we can chat about any particular direction for dealing with an issue that makes its way into the room. But, we keep those types of interactions to a minimum. Though, again, chatting on a topic in the same context - the chat room - is easily done. Now, in the future, i'm very sure that instead of a conventional room, the matrix protocol does support more than simple "chat" messages...so i firmly believe that a solid, comprehensive issue management system can be easily built on top of matrix...but for us, our simple system works fine. Oh, and by the way, we're still technically in beta (long beta period)...so we're just leveraging a private room on the free matrix.org homeserver. Obviously, that is not the correct approach long-term, though we have had no performance issues to date. To be fair, we don't have an avalanche of messages either.
Related posts
- Have any of you used a decentralized messenger before?
- freenode now belongs to Andrew Lee, and I'm leaving for a new network.
- Element: A sovereign and secure communications platform
- Discord is nuking Nintendo Switch emulator devs and their entire servers
- Gotify: A simple server for sending and receiving messages