[f1refly]

You can easily generate individual share links for every pupil and sanction the one whose link was used by a hundred random people from all over the world to join the conference. Jitsi and Big Blue Button are both able to handle this special use case where users aren't trusted to act in good faith I believe.

[bduerst]

The individual share links would be linked to what exactly? A non-user object with the student's name and email address?

[f1refly]

You can just make your own list. Generate 20 links, paste them somewhere, have your list of students next to it. Delete the list if nothing happened, check which number offended if it went wrong.

If you can trust the platform, in cases where the school hosts the program itself, the names can be added to the links directly. You don't need a big db of students for this, just an ephemeral list of strings.

[bduerst]

So you're creating user records every meeting in a spreadsheet to get around having user records?

[hedora]

If you use email or a chat platform that has some sort of history, this rapidly reduces to sending a separate link to each person. No spreadsheet needed.

Yes, it is a pain. No, it's not more of a pain than managing user accounts for the video conference thingy. Also, the video conference thing could automate emailing/texting each participant a unique link. It could manage the invites and address books locally (e.g., via the phone's existing contact list).

If something like the windows phone social hub still existed, it could even send the links via gateways to any social network the phone was logged into. I miss that phone. So much wasted potential.