Feature wish: access code instead of name and idea for a solution

27 views
Skip to first unread message

Reimar Bauer

unread,
May 18, 2022, 4:29:00 AMMay 18
to bigblueb...@googlegroups.com
Hi there,

I have no idea why or how users can get the option to enter twice the access code. First in the access code field, second in the name field. Perhaps it gets not cleared for the second one, or some autofill mechanism?

Anyway I think we could have a simple comparison, and enable join only if the second one is not the access code? Or also write a message to the user to enter a valid user name?

best regards
Reimar

Martin Thomas Schrott

unread,
May 18, 2022, 5:04:33 AMMay 18
to bigblueb...@googlegroups.com, Reimar Bauer

Hi,


I am not sure what you try to explain, but maybe you mean:

users should not be able to enter the accesscode in the name input field.

Correct?

If accesscodes are numbers only, this could be done by not allowing names that do not contain any letter.

#if accesscodes can be alphanumeric this cannot be prevented I fear.


cheers

Martin

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CADfaKO_G52kw9NNoThaz6z4e-9XQmAvXNaXMPBBvh1fVW87-6w%40mail.gmail.com.

Reimar Bauer

unread,
May 19, 2022, 2:36:31 AMMay 19
to Martin Thomas Schrott, bigblueb...@googlegroups.com
Hi

On Wed, May 18, 2022 at 11:04 AM Martin Thomas Schrott <li...@mtsonline.at> wrote:

Hi,


I am not sure what you try to explain, but maybe you mean:

users should not be able to enter the accesscode in the name input field.

Correct?


Yes, we had yesterday three users with the name set to the access code. 

If accesscodes are numbers only, this could be done by not allowing names that do not contain any letter.

#if accesscodes can be alphanumeric this cannot be prevented I fear.


access codes are numerical and of course I assume no one's name is identical to an access code.
If both input values are compared True we can disable the join button and tell that the input field is for the name.

Since this input error happens regularly, we should take this as a hint to improve the user interface.
It is not obvious that the first input was already successful. I guess people think it didn't work and enter it again.

We should also think about whether numbers for the name field as first char are allowed.
This can get confusing if breakout rooms are used and one enters the main room by name "1"
Then the user's placeholder icon changes when he joins breakout room 2 to "2".
And if he didn't join a break out room the indicator looks like he has.
 
cheers
Reimar

elem hsb

unread,
May 19, 2022, 3:45:49 PMMay 19
to bigblueb...@googlegroups.com
Hi,

only joining a room if (access-code != username) solves the issue on ui (greenlight) level.
 

Reply all
Reply to author
Forward
0 new messages