Skip to content

← Writing

engineering

Zoom, Meet, and the Sudden Weight of Video Calls

· Jerwin Arnado

Archive note: this is a backdated post, written years later while rebuilding this site. It’s dated to the moment it covers, but the hindsight is real.

Four months ago, “Zoom” was a verb for camera lenses. Now it’s how classes happen, how standups happen, how birthdays happen. Zoom went from around 10 million daily meeting participants in December to a reported 300 million by April. No company plans for 30x in four months. And it showed.

The cracks

The scrutiny that landed on Zoom this month is the kind that finds every shortcut you ever took:

  • Zoombombing. Meeting IDs were short, guessable numbers with no password by default. People wrote scripts to enumerate them and dropped into classrooms and company all-hands. The fix — default passwords, waiting rooms — was trivial. The lesson isn’t: defaults are security decisions. Most users never change a default, so whatever you ship is what the world runs.
  • “End-to-end encrypted” — except not. Zoom’s marketing said E2E; the implementation was transport encryption with Zoom holding keys. They had to publicly walk it back. For developers, this one stings because it’s so familiar: the gap between what marketing claims and what the architecture does. Words like “encrypted” have specific meanings, and someone will check.
  • Routing surprises. Researchers found some calls routed through servers in regions users didn’t expect. Where your traffic physically goes is an architecture decision with trust consequences.

To their credit, Zoom responded with a 90-day feature freeze to focus entirely on security. Freezing features to pay down trust debt — publicly — is a move worth remembering.

Meanwhile, on PH internet

There’s a layer to the video call boom that the international coverage misses: video calls assume bandwidth that much of the Philippines doesn’t reliably have. The unofficial local etiquette emerged fast:

  • Cameras off by default — it’s not rudeness, it’s packet loss.
  • Audio-only as the norm, video as the exception.
  • The chat box as a parallel channel for when someone freezes mid-sentence.
  • “Can you hear me?” as the new national greeting.

This shaped my opinion on meetings more than any productivity blog: if a meeting works with cameras off and half the audio dropping, it could have been a thread. The constraint is clarifying.

The takeaway for builders

Watching Zoom’s month from a developer’s chair, the notes I’m keeping:

  1. Scale doesn’t just stress servers; it stresses every assumption — defaults, docs, marketing copy.
  2. Security debt is invisible until you’re popular, then it’s the headline.
  3. Infrastructure strain is regional. Building for users on fiber in San Francisco and users on prepaid data in the provinces are different problems, and the second one is mine.

Every team in the world is now load-testing the video call industry in production. It’s a rough way to learn, but nobody’s going to forget the lessons.