The "war dialing" issue is a great example. Webex has had the exact same "flaw" for a decade, with the exact same solution - set a meeting password. Other solutions like Google Meet or Skype have the "lobby" approach.
Zoom was founded in 2011 by Eric Yuan, a lead engineer from Cisco Systems and its collaboration business unit WebEx.[1] [1] https://en.wikipedia.org/wiki/Zoom_Video_Communications#Hist...
https://casetext.com/statute/california-codes/california-bus...
You should also always have some reasonable rate limit of any sort of API query, if someone is querying rooms at 10qps or more, there's clearly something wrong.
I will add: security and convenience are always polar opposites.
The most successful companies are typically the ones that can get away with being as convenient as possible for the longest.
I’m open to being proven wrong, and as eythian implied, I may in fact be subconsciously cherry-picking times where security and convenience were opposites and missing times where they were not, but even with that awareness no counter examples are coming to mind.
[1] Probably available on a Linux system at /usr/share/dict/american-english
[2] '^[a-z]+$'
[3] log_2(77649^4)
Your memorable phrase is 'correct horse battery staple'.
<copy> <generate new phrase in $LANG>
Its not often that people without a common language have zoom meetings anywayUsability is the zoom priority, and the reason why people who already own more secure, no cost, solutions like Teams, Skype or Google Meet buy Zoom.
As with most things, its a trade off.
It's not always ideal though. I've organized meetings with 10+ people, want able to attend the meeting and now nobody can join the session.
One kind is missing something or unintended consequences. Making all URLs clickable opens a UNC attack due to some obscure Windows "feature", for example. Or having N digit numbers means they're technically iterable, but this is the same for cellphones, and there are workarounds.
The other kind is security holes caused by explicitly working to bypass security restrictions yourself. Installing a server with webcam permissions that you don't cleanup so reinstallation is easier for you (don't be surprised when other apps start telling it to switch on the webcam), impersonating the system root password dialog (don't act surprised when other apps steal the password from you), claiming end to end encryption without being clear about where and when it's on, and others.
The first is normal security work, the second is sleazy. We all forgive the first, but we shouldn't let sleaziness slide.
I've never used the web version, but it wouldn't surprise me if it's not the same experience. The video and audio encoding and decoding stuff seems like it just makes more sense as a native app. Given the number of variables that browsers, versions, sandboxing, etc. bring to the equation, I can tell you where I'd spend the majority of my efforts if I were doing video chat: on a great native app. You have a lot more control over that experience, IMHO.
Anyway, your comment reads to me like someone who will never install it, but I would encourage you to at least test out the difference to see why it's become so popular.
So people keep saying "it just works" because Zoom has a noticeably high ratio of works compared to almost any other video conferencing software. It does not mean it works 100% of the time flawlessly for every single user ever always and forever.
FWIW, of the hundreds of Zoom calls I've had, many with non-technical people, I have yet to encounter any issues. I cannot say the same for most other video conferencing products I have used. YMMV, take with grain of salt, caveat emptor, etc.
"it just works" doesn't mean "its a superior product". I use Zoom over hangouts whenever I'm on a call with more than ~3 people, but automatic gcal integration + being fully functional from a browser means that hangouts makes more sense sometimes.
(I also don't have nearly the amount of issues you do with hangouts. The biggest problem for me is how much worse they handle crosstalk, which isn't an issue when there are only a couple of people on a call.
Google Delays Hangouts Shutdown Until June 2020
https://www.extremetech.com/internet/297037-google-delays-ha...
WebRTC Internals in Chrome with frame rate capped at 5 FPS while screen sharing:
https://www.reddit.com/r/chromeos/comments/absxt2/chromebox_...
Screen Share through Hangouts/Meet with high FPS? R: Nope
https://www.reddit.com/r/chromeos/comments/fo60me/screen_sha...
Anyway, my biggest concert is with lack of fluidity of slide/screen sharing.
It is not viable for presentations with animations or where the presenter needs to point with mouse/cursor to a specific point or area of the slide (for example, a point in a curve in a graph).
I work with this.
I'm struggling with this tools first hand. My impression is there a lot of opinions here from people which is not using these tools.
It sounds like your case is less common but the idea is that a video or camera feed can handle more compression (and subsequent drop in quality) as long as it isn't choppy or dropping out. Alternately, a slide or document may have small text which would quickly become unreadable if the compression is too high. To prevent that, you get high quality but only 5FPS or whatever so people can read your document or slide.
Slides and docs don't usually need high framerates so it would just be wasteful to try delivering a mostly static, high resolution, low compression 1920x1080 feed of a PowerPoint at 15 or 30 FPS.
There are ways around this (even on a consumer PC) such as using something like OBS to switch between sources like a webcam, a video clip, or a screen cap and feed them to a virtual webcam (which can be selected in your VTC software as the webcam input). Alternately, there are dedicated switchers and mixers but they're usually reserved for studios or in-facility installations.
But again...you may not like the results even so. The webcam feed often trades higher FPS for higher compression.
They have a lot more ability to ensure it works when it's their own binary. When you're relying on a bunch of browser functions, it's way harder.
The browser version is a last resort.
Latest Safari/macOS.
It is even harder when you try and graft the security on after the fact. Security needs to be a consideration from day 1, not once youve your minimal product. Proper security may steer architecture decisions that may be difficult or impossible which to adapt. This is especially true for internet facing services.
I had a hell of a time bolting on authentication/permission to an internal API (not web based) at a previous employer. By the time I left, we had all users authenticating, but only maybe 20% of the API surface had permissions beyond being authenticated. It was a CRUD API over +300 objects. Yeah, everything was audited, so we couls recover from a malicious or bumbling idiot authenticated user, but the exposure was way to high with people having far more access than their roles needed. It was a mess.
You are saying because they had lax security, now they will have good security.
Con: After the product was released :)
Another post about Zoom, another comment how it's the only video conferencing platform in the planet that "just works". You know I find that really hard to believe... not least of all because I personally use other solutions without never having major hiccups at all.
You’re kidding... right?
Or they're having productivity problems like every other company right now and are spinning it to seem like they are on top of things. These security issues have been around for years.
As a consequence, I suspect Zoom's security is more likely than not to improve going forward... although it will surely take a long while. Security is Capital-H Hard.
Also, I cannot think of any other multi-video-conferencing solution that "just works" and has been as thoroughly stress-tested and attacked by bad actors in the wild at such a large scale. If Zoom does a decent-to-good job fixing all the security issues, it looks likely to continue to dominate its market.