←back to thread

Slack has raised our charges by $195k per year

(skyfall.dev)
1502 points JustSkyfall | 2 comments | 18 Sep 25 01:37 UTC | HN request time: 0.464s | source
Show context
matthewaveryusa ◴[18 Sep 25 05:30 UTC] No.45285801[source]▶
For those of you recommending matrix, have you tried in earnest to use it? I couldn't get reliable video and call to work, even with stun/turn servers properly configured (chrome doesn't trust let's encrypt for ICE certs, that was a fun one to debug, had to go with zerossl).

Sometimes the phone wouldn't ring, rarely did video work.

The element app for android doesn't notify correctly unless the app is open.

For day to day desktop chat it's great, but it falls apart on videoconferencing and mobile

replies(6): >>45285852 #>>45285857 #>>45285942 #>>45286000 #>>45286241 #>>45286546 #
Arathorn ◴[18 Sep 25 05:51 UTC] No.45285942[source]▶
Are you having these problems on Element X or Element Classic (the old mobile app, which is in maintenance mode?)

(Element Classic used a mix of legacy Matrix voip calling for 1:1 and Jitsi for group calling; Element X has switched to native MatrixRTC (Element Call) for E2EE for both 1:1 and group, but is technically still beta as we’re still finishing the 1:1 UX. On Android, notifications are a known problem on Element X Android but if you give the app total permission to run in the background they should work.)

replies(1): >>45286061 #
1. sneak ◴[18 Sep 25 06:10 UTC] No.45286061[source]▶
I grow tired of your chronic replies to everyone critical of Matrix implying that they’re holding it wrong.

If everyone using your software has trouble using your software (or tracking the bugfixes supposedly resolved in the never ending rewrites, rebrands, etc), maybe you should stop pushing it until it’s ready.

Every experience I have had with using Matrix has been a bad one: with the old client app, with the new client app, with the web app, trying to run the server, etc. It’s clunky and slow when it does work. It phones home to the Vector servers by default, despite being selfhosted. It’s a pain in the ass for end users to point it at a different hosted instance.

Maybe the answer is just “the whole thing, client, server, protocol - it’s all still in beta and you shouldn’t expect it to work well”. If that’s the answer, I wish people would stop recommending it until such time it works well.

replies(1): >>45286405 #
2. Arathorn ◴[18 Sep 25 06:56 UTC] No.45286405[source]▶
I'm not implying they're holding it wrong - i'm explaining that we're finishing a migration from one VoIP stack to another, and the new tech is still beta, hence asking which one they're using. If you're going to try to flame my replies, please at least read them.