"Starting on August 24th, we will no longer support the anonymous creation of rooms on meet.jit.si, and will require the use of an account (we will be supporting #Google, #GitHub and #Facebook for starters but may modify the list later on)."
@astrojuanlu@smallcircles Requiring an account on one of those three sites in particular is not, to me, understandable, honestly. That's requiring people to tie their sessions to one of three enormous American corporations.
@astrojuanlu@smallcircles We're certainly not entitled to free stuff forever. Does that mean that those three companies in particular are paying Jisti for the privilege of getting the login data of who sets up the calls? What other data are they given?
@astrojuanlu@smallcircles Actually, never mind what I said, we absolutely are entitled to free stuff forever.
An easy alternative to requiring SSO from one of three enormous and data-hungry American corporations is to instead do what the standard approach is and do e-mail confirmation of local accounts, with or without some sort of accessible CAPTCHA.
@pettter@smallcircles 🤷 What other widely available, single-sign on providers come to mind?
Again, I'm especulating here but probably they're not even receiving money for this, they went for the easiest way of setting up SSO. But I don't want to spend more time here defending a corporation I'm not involved with.
I'm not a paying customer, they don't owe me anything. Time to support your local cooperative offering a self-hosted Jitsi or BigBlueButton service.
@astrojuanlu@smallcircles The goal with a CAPTCHA is not to stop _all machines_ but _low-effort spammers_, which is why having something like "what's two plus five?" is usually sufficient.