deleted by creator
deleted by creator
Thanks! I got it now. I’ll look into it this week.
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)
What issue did you have with the jitsi integration on rocket.chat?
On PCs (specially steam):
On Consoles (specially nintendo):
So in short: There’s hardly any reason to pirate something on PC other than to avoid paying for it. There’s several benefits to getting the game legitimately. On consoles, getting games from the high seas is actually more convenient. Sometimes people will even buy the game but still play a pirate copy instead.
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.si
domain 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).