by vpontis on 4/3/20, 9:20 PM with 49 comments
by bretpiatt on 4/4/20, 1:25 AM
by bartread on 4/4/20, 9:15 AM
On the face of it this sounds fair, but the problem is that being "sceptical" and "realistic" is far easier and requires much less effort than being "visionary"[1]. Too much of the former early on can really suck the life out of a team, increasing the risk that the product fails, or is simply never built.
Safeguarding from abuse is much better achieved by systematic thinking and discipline (which are learned skills) rather than hiring "realists" who might simply turn out to be whiners and energy vampires.
As much as Zoom is currently in the spotlight, and I can't say I'm overjoyed by a number of the issues I've read about (e.g., encryption keys being passed through Chinese servers?!??), many of them are the problems of success, and every successful company has or will experience their fair share of those.
[1] I might also add that it's far easier to commentate and to critique than to do, eh, TechCrunch?
by TACIXAT on 4/4/20, 4:55 AM
by arkadiyt on 4/4/20, 1:08 AM
A meeting id with a password is semantically the same as a longer meeting id (or a meeting id with a character space larger than just digits). I wish they'd do that instead (make meeting ids longer) so I could continue to enter my company meetings with only a link but not have to worry about getting wardialed.
by jdlyga on 4/4/20, 1:16 AM
by wcoenen on 4/4/20, 11:33 AM
by blackrock on 4/4/20, 9:40 AM
As for the Zoombombing, I can’t say that I am surprised. All you really need is the URL.
And all the other tools are like that too. Sure, you can require a separate passcode, but damn it, it’s like trying to figure out rocket science to enter the passcode.
1) you have to dial the number
2) you have to punch in the meeting ID
3) you have to punch in the passcode.
4) ERROR. You flipped it, and used the passcode for the meeting ID instead. Aargh.. frustration.
5) Forget about the passcode. Just let everyone in that has the meeting ID. And monitor if there’s someone unknown on the line.
by faitswulff on 4/4/20, 2:55 AM
by mavsman on 4/4/20, 1:36 AM
She didn't follow the recommendation because she "didn't think someone would join" because she hadn't posted the meeting link on social media. You have you protect your users that won't protect themselves.
by rdlecler1 on 4/4/20, 3:11 AM
by wodenokoto on 4/4/20, 10:01 AM
Would this be solved by generating chat names through a cryptographic hash algorithm?
I have google docs that are edible by anyone with the link and I’m kinda assuming that the link is as hard to guess as logging in with a password.
Am I completely off and in dire need of reevaluating my personal web security?