53
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Feb 2024
53 points (93.4% liked)
Privacy
32033 readers
724 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
But where did those `` jitsi-meet://` links come from?
The calls generated inside rocket.chat are supposed to be handled by the rocket.chat app, everything else it doesn't get involved with.
(I wrote this integration so I'm legitimately interested in how it could be better)
Oh, nice! I can make a video later on how it looks on my machine. I even tried fiddling with the registry to force them to be opened with RocketChat, but that didn't work either.
I've made some screenshots instead of a video. I hope you still get what the issue is.
At the end there is no usuable call from the RocketChat client. But I can copy the meet.jit.si URL and open it in a browser.
Originally I had an error message telling me that Windows doesn't know what to do with jitsi-meet:// links, but that doesn't show up anymore for some reason. Maybe because of me messing with the registry to solve the issue, but I've actually removed the registry key I had created before.
Ah I had that popup confused with one of our own; Now that I checked the text on google translate I figured out what's happening.
The
meet.jit.sidomain is a public jitsi instance that is kept by jitsi themselves. They recently implemented this login requirement on that domain (one user in every meeting must authenticate); They probably assumed that those meetings would always be in a browser and our desktop app is not handling that authentication flow properly. I'll register a task for someone from our app's team to take a look.If you host your own jitsi instance, this login requirement won't be there and you won't have this specific issue (though I assume you probably won't stay with Rocket.Chat anyway due to the E2EE requirement).
Thanks! I got it now. I'll look into it this week.