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

Technology

23 readers
2 users here now

This magazine is dedicated to discussions on the latest developments, trends, and innovations in the world of technology. Whether you are a tech enthusiast, a developer, or simply curious about the latest gadgets and software, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as artificial intelligence, robotics, cloud computing, cybersecurity, and more. From the impact of technology on society to the ethical considerations of new technologies, this category covers a wide range of topics related to technology. Join the conversation and let's explore the ever-evolving world of technology together!

founded 2 years ago
 

While Jitsi is open-source, most people use the platform they provide, meet.jit.si [http://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. If you prefer not to self-host Jitsi and be identifiable via your domain, there’s jami.net [http://jami.net] as a replacement for Jitsi. It is a decentralized conference app that requires you to install an app. However, it’s 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
[–] csolisr@communities.azkware.net 4 points 1 year ago (2 children)

Remember the good old times where OpenID / OAuth were starting to become the norm, and you could log in with StatusNet? Well why can't Jitsi do the same with my Mastodon account?

[–] albinanigans@kbin.social 1 points 1 year ago (1 children)

What did happen with OpenID, anyway? I remember it being big when Livejournal was a thing.

[–] adora@kbin.social 1 points 1 year ago

the biggest problem, ironically, was how flexible it was.
users were forgetting WHICH provider they signed up to a service with, causing a support nightmare and multiple accounts

then there was the issue that all the big players didn't accept external auth - so google, etc.. require their own accounts.