![]() ![]() ![]() It needs to be immediately helpful, remain short, non-technical and provide a quick solution directly related to the issue. Please consider using another name or setting a password as soon as you start using it.". Perhaps use this or similar text : "This room name is too common.This is the resulting warning, at room creation : I' d like to submit a few suggestions to improve the implementation. I've had some feedback from users alreay. I really hope that some of this ideas can be implemented. So many possibilities! It would be amazing to have some of them □Ĭan't agree more. People that don't have this URL (maybe because the URL is too long to spell on the phone) can still join the room by its human-friendly name, but will then need to be granted access from someone inside. Every room gets a long, random URL that grants immediate access to the room. For example: Users would create the room in the same way, they do now. Implement a server-wide setting that forces someone inside the room to grant access to other people joining (as if they were knocking and you are watching them through the spyhole).Only the people with the right URL can even find the room. Implement a server-wide setting that generates long and random strings for every room.Implement a server-wide setting that forces users to set passwords for every room they create.There are many possibilites, how this could be improved. One more thought on this: security measures are only effective if everyone knows how to use them. see that they join, without protection.another, supposedly unrelated user uses the "Start a new meeting" using the same common phrase like "MyFamily" as the name.one user uses the "Start a new meeting" UI using a common phrase like "MyFamily" as the name.interpose a "new user is knocking on your door" step whereby existing participants have to explicitly accept the new user."this already exists try to join it or choose another name?" when "start a new meeting" UI leads to joining an existing meeting, that is a violation of expectation, so interpose a second step, e.g.if a user-specified meeting name is chosen for a new meeting, then very strongly encourage setting a password (unless explicitly chose to start a public meeting).have the "create meeting" UI user choose whether they want a public/open meeting or a private/closed meeting.explain about the random phrase and its security implications and make accepting the suggested phrase a more discoverable option.There are several possible solutions and measures, including. On entering a simple meeting name, there should be some protections in place to prevent walking in on someone else's meeting, uninvited. On entering a simple meeting name there is a real chance of walking in on someone else's meeting, uninvited. I assume what I encountered was an ad-hoc meeting set up by visitors without an account, using the "choose a meeting name, tell it to your friends" method. This is insecure by default, and inconsistent with claiming "security". Their privacy was violated to me, and mine to them. I saw and heard six elderly people whom I don’t know, talking to each other, looking surprised to see me and saying “Oh, who is that?!” In real life just now, I chose a simple meeting name, something like "MyFamily" (but not that) and hit "Go".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |