Technology

37800 readers

139 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

464

Jitsi, the open-source video conferencing platform, now requires a Google, Microsoft, or Facebook account for their online service (jitsi.org)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

104 comments fedilink hide all child comments

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

[–] [email protected] 4 points 1 year ago

How disappointing.

It was great for sharing private contact info with Google/Facebook/etc friends without revealing it to those invasive services. Instead of sharing your private address where it would be harvested, you could meet in an anonymous Jitsi room, exchange addresses there, and contact each other directly from then on.

Self-hosting doesn't solve that use case, unless perhaps you're willing to buy throw-away domains and IP addresses every time you do it.