Skip to main content

Business Bonus: Netflix Livestream Turns Into A Learning Opportunity

 Good on Netflix for being more like cable television, from adding ads, to attempting to livestream in 2023. 

I am not familiar with Netflix's "Love Is Blind" show, but on 4/16, Netflix had intended to livestream a reunion at 8/7c, and it was hotly anticipated.

To their credit, they did it successfully earlier this year, after a comedian's stint at the Hippodrome Theater in March, where there was apparently a waiting room for viewers while technical checks were run.

When it did not start on time, tweets began to flow in confusion -- and jokes. Netflix tried to play along and soothe impatient fans:


Even (the last existing) Blockbuster took to the stage to fire shots:

Apparently, the internet at the venue had issues:

 

That's Vanessa Lachey.

The production ended up being aired an hour late, to the point where they just scrapped the 'live' aspect all together and will put it on the site soon.

 That's thinking on your feet and being flexible! I mean, who asked it to be live?

I'm sure internet connectivity was tested and retested at the venue, and it was something extremely disruptive to delay a company valued at almost 150$ Billion dollars (When it isn't taking massive losses on entertainment it refuses to promote). I am more curious about the source of the technicians onsite. Are they from a staffing agency, or is Netflix building out a field team for livestreams?

Anyone waiting probably moved on to watch Succession instead. People are angry, demanding refunds, but it's not as if the entire site was down, just one (albeit highly advertised) aspect that people were looking forward to.

You don't need a refund and Netflix as a whole doesn't need our pity.

Postmortem -- Reed Hastings basically boiled it down to "Several systems did not play nicely together that were not tested initially." A handful of last minute changes on the livestream site caused the issue.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory