• 0 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle

  • I believed they maybe weren’t listening because those cases that people claim as “proof” of listening can usually be explained in other ways as well. People tend to assume they were listening because its the easier explanation but with the amount of data that Meta has, they can easily lead people into thinking about things by showing specific posts on the Facebook timeline and also predict to some extent what people may end up talking about based on things like how many times you replay a certain video and how long did you keep certain posts in focus on the screen and that sort of stuff that people often don’t realize is also data for them.

    Still, I would never put my hand on fire for them and never completely discarded the possibility of them listening.














  • 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).