188
submitted 1 year ago by carnha@lemm.ee to c/privacyguides@lemmy.one

cross-posted from: https://beehaw.org/post/7363991

While Jitsi is open-source, most people use the platform they provide, meet.jit.si, for immediate conference calls. They have now introduced a "Know Your Customer" policy and require at least one of the attendees to log in with a Facebook, Github (Microsoft), or Google account.

One option to avoid this is to self-host, but then you'll be identifiable via your domain and have to maintain a server.

As a true alternative to Jitsi, there's jami.net. It is a decentralized conference app, free open-source, and account creation is optional. It's available for all major platforms (Mac, Windows, Linux, iOS, Android), including on F-Droid.

you are viewing a single comment's thread
view the rest of the comments
[-] CrypticCoffee@lemm.ee 32 points 1 year ago

That is a massive disappointment. Hopefully Element gets their video calls sorted. Why can I not just have privacy tools that I can use? Why are the good ones taken away?

[-] garrett@infosec.pub 23 points 1 year ago

Short answer is that a lot of privacy-focused tools get abused like hell and put these companies in an untenable position. It sounds like Jitsi had something fairly bad happening that would’ve put them in a regulatory pinch.

[-] CrypticCoffee@lemm.ee 2 points 1 year ago* (last edited 1 year ago)

But the companies chosen for login is a slap in the face of anyone who cares about privacy.

If it is e2e encrypted, why would this change mitigate what they are concerned about?

[-] garrett@infosec.pub 1 points 1 year ago

“Slap in the face” is a bit dramatic when this doesn’t impact the truly private version of this software, the version you host on a system you control.

I’m also not sure what end-to-end encryption has to do with this since preventing the sign up of an abusive user essentially addresses the issue. It’s probably not something they’d wanna do but I’d wager they were getting some subpoenas and/or warrants that they couldn’t provide much information for and LEOs were ratcheting up pressure. Unfortunately, the legal side of tech is more than “ha ha can’t do that, officer”.

[-] HughJanus@lemmy.ml 15 points 1 year ago

Because privacy is not a lucrative business. And the opposite is incredibly lucrative.

[-] CrypticCoffee@lemmy.ml 2 points 1 year ago

So they abandoned what built them up. They sold out?

[-] HughJanus@lemmy.ml 10 points 1 year ago

Kinda? It sounds like their platform was being used for unethical activity. But it's like, you had to have seen that coming from the beginning, right?

[-] detun3d@lemm.ee 3 points 1 year ago

I don't remember Element using the Jitsi Team's instance. Element.io had their own so this shouldn't affect it's Matrix users at all.

[-] CrypticCoffee@lemmy.ml 4 points 1 year ago

Yes. Jitsi was one of the best for a while. Secure and just works. I think Element wasn't e2e encrypted while debugging but I'm guessing is close to usable. I mentioned it more as a FOSS alternative.

this post was submitted on 26 Aug 2023
188 points (100.0% liked)

Privacy Guides

16263 readers
40 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 2 years ago
MODERATORS