Elon Musk buys Twitter

[Browser Brody]

Ouch…..

https://twitter.com/x/status/1968473003592990847

 

[How bad boy]

Ouch…..

https://twitter.com/x/status/1968473003592990847

Never do live demos, especially for anything that needs a wifi connection at a conference.

Making physical stuff is hard to get right.

 

[nelly sham]

Never do live demos, especially for anything that needs a wifi connection at a conference.

Making physical stuff is hard to get right.

Exactly this.
They must have been convinced they knew better

 

[Browser Brody]

Never do live demos, especially for anything that needs a wifi connection at a conference.

Making physical stuff is hard to get right.

Hmmm i would be surprised if they were connected to the same SSID as the attendees.

This didnt look like a connectivity problem to me.

 

[How bad boy]

Hmmm i would be surprised if they were connected to the same SSID as the attendees.

This didnt look like a connectivity problem to me.

The SSID isn't the problem, it's the overall congestion on the bandwidth.

If you've got 5,000 devices all trying to find, and transmitting in your frequency band, then it'll screw the connection regardless of how it's separated, your signal to noise goes to shit because your noise floor is so elevated.

Of course, they're not idiots, they know that and probably were hoping that a very directional wifi beam would raise the signal to noise high enough to make it work. It's hard to maintain a connection in those settings with as limited a protocol as wifi, especially on the uplink as you can't simply raise the power amplifier power on the device easily.

Might not have been connectivity, but that would be my guess, that the responses to queries weren't being received.

 

[sigourney's knickers]

Could be all that but.... what if it's just shit.

 

[Browser Brody]

The SSID isn't the problem, it's the overall congestion on the bandwidth.

If you've got 5,000 devices all trying to find, and transmitting in your frequency band, then it'll screw the connection regardless of how it's separated, your signal to noise goes to shit because your noise floor is so elevated.

Of course, they're not idiots, they know that and probably were hoping that a very directional wifi beam would raise the signal to noise high enough to make it work. It's hard to maintain a connection in those settings with as limited a protocol as wifi, especially on the uplink as you can't simply raise the power amplifier power on the device easily.

Might not have been connectivity, but that would be my guess, that the responses to queries weren't being received.

“
When the chef said ‘hey Meta, start Live AI,’ it started every single Meta Ray-Ban’s Live AI in the building,” said Bosworth. “We had routed Live AI traffic to our dev server, in theory, to isolate it, but we had done it for everyone in that building on those access points. We DDoS’d ourselves, basically.” So yeah, it wasn’t the Wi-Fi, as Zuck claimed on stage.“

Meta’s failed smart glasses demos had nothing to do with the Wi-Fi

‘We DDoS’d ourselves, basically.‘

www.theverge.com

 

[How bad boy]

“
When the chef said ‘hey Meta, start Live AI,’ it started every single Meta Ray-Ban’s Live AI in the building,” said Bosworth. “We had routed Live AI traffic to our dev server, in theory, to isolate it, but we had done it for everyone in that building on those access points. We DDoS’d ourselves, basically.” So yeah, it wasn’t the Wi-Fi, as Zuck claimed on stage.“

Meta’s failed smart glasses demos had nothing to do with the Wi-Fi

‘We DDoS’d ourselves, basically.‘

www.theverge.com

The simultaneous activation of course isn't a new thing:

Amazon Echos activated by TV comment

A comment on a US TV news show activates Amazon Echo gadgets in viewers' homes.

www.bbc.co.uk

But the dev server, presumably it was the network that tipped over, rather than the server, assuming Zuck's were connected to prod, not the dev server.

 

[sigourney's knickers]

Development server for a demo.

Were they off their heads.

 

[How bad boy]

Development server for a demo.

Were they off their heads.

I think what he means is they booted everyone off to the dev server, but Zuck was on prod.
I suspect there's a load balancer or router in the comms chain that crapped out.