How do you solve problems arising from bad actors without an object representing the user?
Sure, but then the student who shares their interactive class URL (w/ or w/o password) on 4chan still isn't accounted for.
>How do you solve problems arising from bad actors without an object representing the user?
In response to the argument that user objects are no longer needed, even for something like virtual meetings. The scenario of zoombombing isn't something "I came up with", it's a real life scenario that having a user object helps prevent bad actors with.
In the event of a user sharing their account, you would know who it was and be able to hold the bad actor accountable, as opposed to a meeting URL being shared. I think the better question is why you are so hostile to the idea of user accounts having utility.
Emphasis added. You could create user-specific passwords, but that would require... users.
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.
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.
The vast bulk of sites want to make signup easy, meaning user objects are cheap. Cheap user ids are easily disposed of and replaced. So if you need to keep bad actors out, user accounts may not help a ton.