If it is, we'll be happy to investigate.Ĭould you please make sure you are on the latest version of Slack (4.21.1) and restart Slack for me? This will send me a fresh set of logs I can use to what might be going on here. We do have an issue with our Snap package not handling links for Firefox well, however this should not be present in the regular direct download. Could you please confirm this is on Ubuntu, and let me know if you have the Snap store version installed? Thanks for getting in touch and I am sorry for the issues here. I sent the above report to slack support and they replied:

Since firefox only allows one instance running at a time, it fails. Since the upgrade to 4.19.2 links now try to launch a new instance of firefox.

Before the latest upgrade links would open in a running firefox in a new tab.

This is how Matrix democratises control over communication.īy default, Matrix uses simple HTTPS+JSON APIs as its baseline transport, but also embraces more sophisticated transports such as WebSockets or ultra-low-bandwidth Matrix via CoAP+Noise.Using slack version 4.19.2. This means that every server has total self-sovereignty over its users data - and anyone can choose or run their own server and participate in the wider Matrix network.

Even if your server goes offline, the conversation can continue uninterrupted elsewhere until it returns. There is no single point of control or failure in a Matrix conversation which spans multiple servers: the act of communication with someone elsewhere in Matrix shares ownership of the conversation equally with them. When you send a message in Matrix, it is replicated over all the servers whose users are participating in a given conversation - similarly to how commits are replicated between Git repositories. Matrix is really a decentralised conversation store rather than a messaging protocol.

Slack firefox