Depends on the part of the problem you want to tackle. With an E2E-encrypted feed, identifying CSAM is non-trivial even if law enforcement offers to put a box somewhere to scan all the things and do the classification.

What this seems to be aiming at is having somebody who's responsible in case any given meeting ends up being investigated.

"No login" doesn't offer any clue (besides an IP address, perhaps). "Enter your name" will see tons of Donald Ducks doing video conferences. "Enter any valid email address" (+ confirmation) will see tons of throw-away domains not paid for by stolen credit card data. Same for OpenID etc.

OAuth from Meta, Alphabet or Microsoft offloads that problem to megacorps with the resources to handle that question, and they do for their own anti-spam purposes: For example with that phone number verification step when creating a new account.

So that's the benchmark that any alternatives compete with.

Jitsi could start its own user database and do an SMS handshake for room-creation permissions - which means they'll have to deal with global SMS, associating a phone number with each meeting while protecting that data (the OAuth identifiers are relatively harmless since they're unique for each OAuth consumer).

That's a steep increase in costs and responsibilities for a service they provide for free...