499
Kamala Harris’s campaign mocks how much Donald Trump and Elon Musk suck at the Internet
(www.vanityfair.com)
this post was submitted on 14 Aug 2024
499 points (99.0% liked)
politics
19104 readers
2709 users here now
Welcome to the discussion of US Politics!
Rules:
- Post only links to articles, Title must fairly describe link contents. If your title differs from the site’s, it should only be to add context or be more descriptive. Do not post entire articles in the body or in the comments.
Links must be to the original source, not an aggregator like Google Amp, MSN, or Yahoo.
Example:
- Articles must be relevant to politics. Links must be to quality and original content. Articles should be worth reading. Clickbait, stub articles, and rehosted or stolen content are not allowed. Check your source for Reliability and Bias here.
- Be civil, No violations of TOS. It’s OK to say the subject of an article is behaving like a (pejorative, pejorative). It’s NOT OK to say another USER is (pejorative). Strong language is fine, just not directed at other members. Engage in good-faith and with respect! This includes accusing another user of being a bot or paid actor. Trolling is uncivil and is grounds for removal and/or a community ban.
- No memes, trolling, or low-effort comments. Reposts, misinformation, off-topic, trolling, or offensive. Similarly, if you see posts along these lines, do not engage. Report them, block them, and live a happier life than they do. We see too many slapfights that boil down to "Mom! He's bugging me!" and "I'm not touching you!" Going forward, slapfights will result in removed comments and temp bans to cool off.
- Vote based on comment quality, not agreement. This community aims to foster discussion; please reward people for putting effort into articulating their viewpoint, even if you disagree with it.
- No hate speech, slurs, celebrating death, advocating violence, or abusive language. This will result in a ban. Usernames containing racist, or inappropriate slurs will be banned without warning
We ask that the users report any comment or post that violate the rules, to use critical thinking when reading, posting or commenting. Users that post off-topic spam, advocate violence, have multiple comments or posts removed, weaponize reports or violate the code of conduct will be banned.
All posts and comments will be reviewed on a case-by-case basis. This means that some content that violates the rules may be allowed, while other content that does not violate the rules may be removed. The moderators retain the right to remove any content and ban users.
That's all the rules!
Civic Links
• Congressional Awards Program
• Library of Congress Legislative Resources
• U.S. House of Representatives
Partnered Communities:
• News
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Are they really? The tools are there, Zoom (like she already used), Discord, or whatever.
Have you seen popular games on launch day falling down on auth flows? That's largely just HTTPS text connections via REST. Now add in a binary data stream on top of that (likely RPC, but I'm not sure of Twitter's implementation).
All that said, Twitter dropped the ball due to Musk's arrogance. Instead of having limited issues, it was riddled with issues as a result of him firing all the people that could have reduced the issues. As was foretold by our ancestors.
Yeah no. It works just fine.
Harris used Zoom to speak to hundreds of thousands. I've used it for work for years. It's absolutely fine.
The scope here is a live stream to hundreds of thousands of people with modest quality.
So yes, it's not just fine, it's good.
The goal was a livestream, not a fancy video or anything.
~200,000 simultaneous connections vs ~2,000,000 simultaneous connections is a world of difference.
Additionally, while a successful Zoom call, it still had issues, with a dedicated Zoom support team.
Nothing about either of these events were "easy" or "fine".
The big difference is that Musk is an arrogant idiot and decided to roll-his-own streaming service with a reduced headcount and a product that that is lacking proper load balancing, reservations, & scaling through load testing & real world tests scenarios that ramp up scale over time.
What's sad is that at least partially because of this asshat, a lot of other companies got the idea that they can just fire lots of their staff and let the remaining people pick up the slack (because they should be thankful they even have a job)...I cannot wait for the chickens to come home to roost not only at Xitter, but other companies doing this because he did.
Zoom is the lowest bitrate of any platform. It's not a firehouse like traffic out of teams. It's literally the easiest solution to do this with.
To not, I've designed and overseen the implementation of deployments for zoom, teams, pexip, etc, etc, for companies that employ a small country worth of people globally.
"High production" is never easy. But at a certain level, there are additional tools from Zoom (as well as others) that can be used, which even have hooks into production consoles. Mostly cheap ones, but still.
Sure
The biggest thing to me is don't share the Internet connection. Get a separate line turned up to handle the session, with a dedicated firewall (commercial grade, doesn't need to be a palo alto or anything, but a mikrotik, Cisco fp, etc is fine), connected to a switch for just the zoom machines. No meeting connector or any of those shenanigans - the throughput is dedicated to the session. If it's the kind of place that can't do that, get share the pathway as little as possible, and provide that client endpoint with the highest priority. This is, to me, the most important part.
Production Studio will get used, but it's not really doing any of the lift - it's a full production studio before it hits that machine (which has a matching spec machine right next to it in case of failure, turned on and ready to go as a co-host machine). All it's doing is allowing for some border content, some backgrounds for content, session wallpaper, etc. Glorified OBS at that point.
Feeding it is usually a Ross Carbonite or a Grass Valley, but I've also done it with a black magic atem, Roland, etc. At this point, all the production is outside of Zoom, so any lower thirds, virtual studio backgrounds, etc. are all handled there. This way, if there is any issue with the main Zoom Prod Studio machine, there's a second video feed to the backup (co-host) PC. That's the only advantage/reason why I even bother with Prod Studio over just tossing a zoom room on a PC and walking away.
All production hardware is on a segregated network, no outbound internet or routes, especially if using Dante/aes67, NDI, qlan, whatever. Stacked switches if more than one is needed, no simple uplinks (ie: bottlenecks).
At that point not much else matters, grab your shure lavs (if there is density, axient) and a few wires mic backups, cameras at your preference (honestly a lot of BM Ursa/Studio with good cine lenses, mostly primes), and good to go.
Couldn't tell you about Discord, sorry, don't really use it.
Just to mention, smaller scale production takes the same tactics, just without a GV/Ross/etc, more likely a BM ATEM or something. But I don't deal with that too much these days.
More often than not, I'm designing a studio which can also run webinars. For a presidential candidate, they probably did something similar, maybe making use of a few tools not public yet (though I wouldn't have risked it with an event like this).
Teams can be much more problematic, it's like a firehose of traffic, using whatever you give it. Looks good when you have the bandwidth, making the first statement - not sharing the connection - even more important. Zoom is heavy on the compression, but quite stable as a result.
Recordings should be local, with the session also recorded, so the session can be distributed with the local recording edited in for a better quality result. Remote participants, when I have to deal with that, get a full kit including a local recording system (aja mostly), so the drive can be shipped back with the kit for the finals edits.
No problem!
Ideally, on-site local crew and a portable kit, preferably two sets in case of issues. Usually a small prod switcher, lenovo tiny (or hp/dell, we just use Lenovo mostly), and a small audio mixer, with wired mics rather than wireless, like an SM7B or an ev re-20. It's basically a mini version of the same kit used for the main session. Backup machine though is a laptop rather than another PC if it's only one kit.
If there is no one going on site to the remote participant, there's a session before hand to set it up (a week if possible), a session to test with them and get them comfortable (a few days before), and a session a few hours before the main event start to make sure they are all set.
Edit: Stupid autocorrect
Btw, the short answer on this is don't expect zoom to be more than it is - conferencing/webinar software. For production quality, do it outside zoom so you're feeding it what you want, and not relying on their interpretation of what good video production looks like.
Because let's be honest here, they suck at that. As does Microsoft. None of them understand the needs, so it's best to assume they never will.