admin
admin copied to clipboard
nodejs
Zoom meetings
Hi, over the break it appears that Zoom has added some new security features, including verification by email when someone logs in from a new location.
I looked into it and here's the fix. Instead of having the meeting host log directly into the [email protected] zoom account, you should instead log in with your own Zoom account. When you're in the meeting, open the participants panel and click "Claim host". It will ask you for the host key, which is a six digit number specific to each zoom account. This should be done by the person who will run the livestream, as only the host can initiate a stream. (As before, you'll still need access to the YouTube account in order to stream, that part is unchanged.)
There are a few advantages to this, one being that we no longer have to use LastPass to share out the credentials. I'll provide the host key to a few community members, or you can email [email protected] to request it.
It think we discovered this only works for meetings versus webinars that we have been using. We should experiment if meetings will be a good replacement now (do they have the raise hand etc.)
@brianwarner I also assume that even though the host ends up being a regular user the 40 minute limit will not apply since the meeting was set up in a paid account?
Good question. That should be the case, yes, since the meeting is being hosted on the pro account.
Also, I can confirm meetings have the raise hand as well as non-verbal feedback. Also breakout rooms, mute-all, etc.
On Fri, Jan 14, 2022 at 5:29 PM Michael Dawson @.***> wrote:
It think we discovered this only works for meetings versus webinars that we have been using. We should experiment if meetings will be a good replacement now (do they have the raise hand etc.)
@brianwarner https://github.com/brianwarner I also assume that even though the host ends up being a regular user the 40 minute limit will not apply since the meeting was set up in a paid account?
— Reply to this email directly, view it on GitHub https://github.com/nodejs/admin/issues/654#issuecomment-1013516578, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOVQJV6YWBGWVGXHHQNNW3UWCPUVANCNFSM5LW2LDLQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
--
Brian Warner The Linux Foundation @.*** +1 724 301-6171
👋 I'm having trouble starting the Tooling Group meeting, due to this issue, I get what looks like an OTP entry, but I'm not seeing how I would take over the meeting (since it doesn't start automatically).
Any suggestions on a workaround?
@bcoe can you PR yourself into https://github.com/nodejs/email/blob/main/iojs.org/aliases.json in the zoom-nodejs section. That is the email to which the OTP codes are sent to.
We ended up with that approach and it shoud be what you need to log in when challenged.
Am I right in understanding I will need to do that too for running the diagnostics working group meetings?
@Qard yes, sorry I forgot to do that when we onboarded you. If you can PR yourself in that would be great.