WEBVTT

00:00:00.000 --> 00:00:07.000
It's time for tech news, and you know what that means.

00:00:04.840 --> 00:00:11.240
I know what it means, but I Why don't you say it so I know you know? So,

00:00:09.040 --> 00:00:15.760
OpenAI just had a weekend that puts the one at Bernie's to shame. The twists and

00:00:13.640 --> 00:00:20.800
turns have honestly made my head hurt, but here's our summary. Late Friday

00:00:17.800 --> 00:00:23.240
evening, CEO Sam Altman was fired by the

00:00:20.800 --> 00:00:26.480
four other members of the OpenAI board, while president Greg Brockman was

00:00:25.080 --> 00:00:31.200
removed as chairman. They wanted an old man. You're too much of a normal man.

00:00:28.800 --> 00:00:35.800
Upon hearing the news, Greg quit and tweeted his account of recent events,

00:00:32.880 --> 00:00:42.120
implying, possibly unintentionally, that OpenAI chief scientist and board member

00:00:38.280 --> 00:00:43.960
Ilya Sutskever was the Brute in this

00:00:42.120 --> 00:00:47.720
Shakespearean drama. Most of you will get that. What's that knife for, bro?

00:00:45.480 --> 00:00:51.720
You too, Brutus? It's still not clear what the board's exact reasons for

00:00:49.920 --> 00:00:56.560
the shakeup were, and the story is complicated by OpenAI's truly weird

00:00:54.440 --> 00:01:00.840
corporate structure, where the nonprofit board controls the capped profit

00:00:58.600 --> 00:01:05.760
company. But, some speculate that Sam seeking investment for a new AI chip

00:01:02.960 --> 00:01:10.760
company played a role, as OpenAI's board accused him of being not consistently

00:01:08.320 --> 00:01:16.880
candid in his communications with them, despite a later memo from OpenAI COO

00:01:13.600 --> 00:01:19.800
Brad Lightcap, cool name, definitively

00:01:16.880 --> 00:01:23.560
claiming that Sam was not fired for malfeasance, a French word meaning

00:01:22.120 --> 00:01:28.160
weasel. If that confused you, then you know how

00:01:25.840 --> 00:01:33.320
everyone, including the OpenAI board, felt this weekend. They apparently

00:01:30.120 --> 00:01:36.160
agreed to step down and bring back Sam

00:01:33.320 --> 00:01:41.480
and Greg, right before Microsoft swooped in and announced they'd hired Sam, Greg,

00:01:39.320 --> 00:01:48.160
and a bunch of other OpenAI employees. Right after that, OpenAI hired Twitch

00:01:44.640 --> 00:01:51.240
co-founder Emmett Shear as interim CEO,

00:01:48.160 --> 00:01:54.120
replacing day-and-a-half-old interim CEO

00:01:51.240 --> 00:01:57.320
Mira Murati, presumably because she just needed more experience. And her name

00:01:55.640 --> 00:02:01.480
sounds like a car. We can't have that. But really, Emmett may have been chosen

00:01:59.160 --> 00:02:08.240
because, like the safety-minded board members, he said he wants AI development

00:02:04.680 --> 00:02:10.679
to slow down. He also said that CEO jobs

00:02:08.240 --> 00:02:13.800
could be replaced by AI. So, slowing down means he could enjoy his new

00:02:12.040 --> 00:02:17.800
position for longer than 5 minutes. So, that's probably Emmett may soon be

00:02:15.840 --> 00:02:22.680
captain of a ghost ship, though. A letter from OpenAI employees threatening

00:02:19.959 --> 00:02:27.720
to resign unless the board steps down and brings back Sam. And conduct ours to

00:02:25.400 --> 00:02:34.200
the break room. And what? Was signed by 650 of the company's 770 employees on

00:02:31.600 --> 00:02:39.920
Monday morning. Including Ilya Sutskever. Et tu, Brute? What? Brutus?

00:02:37.840 --> 00:02:45.720
You're back. What are you doing here? Confusingly, Ilya tweeted that he deeply

00:02:42.800 --> 00:02:51.800
regrets his participation in the board's actions, a tweet Greg reposted with a

00:02:49.000 --> 00:02:56.200
heart emoji. Mira Murati also replied with a heart to Sam's tweet saying, "I

00:02:54.440 --> 00:03:00.519
love OpenAI." So, I don't know whether these people are actually still trying to be friends despite all the drama or

00:02:59.080 --> 00:03:05.360
whether they just don't know what emojis mean. Now, here's the real kicker. The

00:03:02.920 --> 00:03:09.920
Verge claims multiple sources are saying that Sam and Greg's Microsoft situation

00:03:07.880 --> 00:03:15.120
isn't a done deal and that they are still willing to return to OpenAI if the

00:03:12.160 --> 00:03:20.160
board resigns. And Sam did recently imply that the OpenAI team are all going

00:03:18.000 --> 00:03:24.440
to work together some way or the other. As for Microsoft, well, they've invested

00:03:22.200 --> 00:03:28.720
billions in OpenAI. So, whether they get Sam or Sam returns to OpenAI with a new

00:03:27.280 --> 00:03:35.000
board, this is really a win-win for them. And hey, how about a seat for old Satya while

00:03:31.959 --> 00:03:37.560
we're playing musical chairs, eh?

00:03:35.000 --> 00:03:41.480
Okay, back to work making a digital god. This whole thing sounds like the most

00:03:39.040 --> 00:03:43.959
hard to follow polycule I've ever heard in my life. Honestly, I'm just proud of

00:03:42.680 --> 00:03:48.120
myself for following it all the way through. Sunbird, the company Nothing

00:03:45.959 --> 00:03:53.560
partnered with on their Nothing Chats iMessage compatible app for Android, has

00:03:50.760 --> 00:03:57.600
apparently comically misrepresented the security of their services. Multiple

00:03:55.880 --> 00:04:01.480
professional and amateur investigators have claimed that the full contents of

00:03:59.280 --> 00:04:06.720
messages sent through Sunbird's service are accessible in plain text by not only

00:04:04.400 --> 00:04:11.200
Sunbird, but by anyone with a smattering of hacker know-how, despite Sunbird

00:04:09.000 --> 00:04:15.160
claiming not to collect any data because they use end-to-end encryption. On

00:04:13.080 --> 00:04:19.359
Twitter, Sunbird tried to dismiss security researchers' concerns, but all

00:04:17.600 --> 00:04:24.880
of their points seem to have been systematically refuted by a team from

00:04:21.799 --> 00:04:27.160
texts.com. When enough had been enough,

00:04:24.880 --> 00:04:32.280
nothing removed the chats beta from the Play Store on Saturday, saying they were

00:04:29.320 --> 00:04:36.080
delaying the launch to fix several bugs in what the Sunbird team's brains?

00:04:35.040 --> 00:04:42.880
These are probably like southern hemisphere bugs. Like rhino beetles. Yeah. And Sunbird themselves put their

00:04:39.919 --> 00:04:47.880
services on hold. Now, this is another story where it's very unclear what's

00:04:45.400 --> 00:04:52.240
actually going on. A texts.com engineer was banned from Sunbird's Discord after

00:04:49.919 --> 00:04:58.120
making a tool that lets users delete Sunbird's copies of their stored data,

00:04:54.840 --> 00:04:59.320
which Sunbird is apparently storing. You

00:04:58.120 --> 00:05:05.000
know what? I think we better delay the launch though. Yeah, just let Just let it all blow over. Now, it's time for

00:05:02.800 --> 00:05:09.280
quick quick shopping time. No, Dennis, not again. Is your budget

00:05:07.440 --> 00:05:13.160
small like Gladys' hand? Please, don't hang your laugh on a crappy gift this

00:05:11.240 --> 00:05:17.480
holiday. Newegg is here to bring joy to your bag. With their Black Friday sales,

00:05:15.120 --> 00:05:22.000
you get up to 84% off. From gaming laptops, monitors, and CPUs to printers.

00:05:20.000 --> 00:05:26.560
You get a GPU. You get a GPU. You get a GPU. Oh, you get You get this back.

00:05:24.680 --> 00:05:30.440
Plus, you can save even more on a GPU by using Newegg's GPU trading program.

00:05:28.680 --> 00:05:34.120
Their Black Friday's price protection ensures you have the lowest price on

00:05:32.120 --> 00:05:37.160
Newegg. Be a Santa everyone laughs and check out Newegg at the link below.

00:05:36.040 --> 00:05:41.200
Yeah! Nice bits you got there.

00:05:39.440 --> 00:05:46.680
Be a shame if someone quickened them. Reviews are out for

00:05:43.640 --> 00:05:50.600
AMD's Ryzen Threadripper 7970X and

00:05:46.680 --> 00:05:52.720
7980X, and the general consensus is

00:05:50.600 --> 00:05:55.120
that these chips are sick AF. If your name isn't Brutus, that means they're

00:05:53.960 --> 00:06:01.320
good. Not only that, but they stand as a formidable and currently uncontested

00:05:58.880 --> 00:06:06.160
entry into the niche of prosumer processors for high-end desktops.

00:06:03.680 --> 00:06:11.560
Ironically, a term coined by Intel. Doesn't feel good. The top SKU, the

00:06:07.960 --> 00:06:13.920
7980X model, has 64 cores, 128 threads,

00:06:11.560 --> 00:06:18.800
a base clock of 2.5 GHz, and a turbo clock that can hit up to 5.1 GHz.

00:06:16.560 --> 00:06:23.520
Finally, a fitting heir to the Threadripper 3000 series. Here's hoping

00:06:21.360 --> 00:06:27.720
AMD won't get bored and completely skip a generation like they did with the

00:06:25.080 --> 00:06:31.760
purely hypothetical Threadripper non-pro 5000 series, just leaving the throne

00:06:30.280 --> 00:06:36.520
unfilled. It's not right. Drop the crown, king. YouTube seems to

00:06:33.919 --> 00:06:40.760
be intentionally slowing itself down on Firefox and Safari, at least for some

00:06:38.840 --> 00:06:44.960
users. It looks like a hard-coded 5-second delay that disappears when the

00:06:43.320 --> 00:06:48.880
site is fooled into thinking it's running on Chrome. Now, it's tempting to

00:06:46.600 --> 00:06:54.080
assume that Google is simply punishing users for using a competing browser, but

00:06:51.600 --> 00:06:57.840
it's also plausible that this is a bug introduced by Google's heavy-handed ad

00:06:56.040 --> 00:07:02.120
block filtering. Always remember Hanlon's razor, and never attribute to

00:06:59.800 --> 00:07:06.040
malice what can adequately be explained by neglect or incompetence.

00:07:04.120 --> 00:07:08.640
Except in this case, it's you know, it's Google.

00:07:07.320 --> 00:07:13.280
They've done this before, but we don't know. NVIDIA and SK Hynix are working

00:07:11.000 --> 00:07:18.400
together on a new GPU design, according to Korean news site Joong Ang. The

00:07:15.919 --> 00:07:22.960
design would have HBM4 memory chips stacked directly on top of the GPU, like

00:07:21.280 --> 00:07:25.880
a hat that makes you much better at remembering what you said to Amanda in

00:07:24.640 --> 00:07:31.480
fourth grade. Like, what were you thinking? Ah, get it off! This structure

00:07:28.480 --> 00:07:33.840
sounds similar to AMD's 3D V-Cache used

00:07:31.480 --> 00:07:37.360
in the company's X3D processors, which are really good at gaming because they

00:07:35.760 --> 00:07:41.120
help you remember where the bomb sites are in Counter-Strike 2. That's what I

00:07:39.360 --> 00:07:45.160
think they do. I I don't design processors. And, you know, Valorant for

00:07:43.560 --> 00:07:50.080
the win. I don't play that either. Details of Intel's upcoming Lunar Lake

00:07:47.760 --> 00:07:55.560
MX have leaked showing that the CPU, GPU, and memory will all be on the same

00:07:52.800 --> 00:08:00.480
SOC, like Apple's unified memory architecture. Ooh, whoa. No, my watch.

00:07:58.880 --> 00:08:03.840
Stop that. This will be the first commercial release of the technology

00:08:02.280 --> 00:08:08.800
that Intel showed off to the press earlier this year at their Arizona fab.

00:08:06.320 --> 00:08:13.919
This leak is so big, it almost makes you forget that Meteor Lake the architecture

00:08:11.480 --> 00:08:18.720
Lunar Lake MX is meant to replace, hasn't actually been officially released

00:08:16.320 --> 00:08:23.720
yet despite Intel's promise of a 2023 launch. But, I haven't forgotten, Pat.

00:08:21.280 --> 00:08:27.880
Your mind tricks don't work on me. And if you paper launch the Meteor Lake you,

00:08:26.040 --> 00:08:32.039
I'm not sending you a Christmas card this year. That came out of nowhere.

00:08:29.800 --> 00:08:38.120
You're getting coal. An auto tech company, Valeo, is suing NVIDIA after a

00:08:35.000 --> 00:08:40.440
video call gaffe exposed alleged trade

00:08:38.120 --> 00:08:46.240
secret theft. Basically, a Valeo employee left for a job at NVIDIA and

00:08:42.960 --> 00:08:48.400
took Valeo's work with him. This came to

00:08:46.240 --> 00:08:53.560
light months later when he accidentally screen shared stolen code during a video

00:08:51.000 --> 00:08:57.160
call with Valeo employees. All because one employee couldn't make a normal

00:08:55.440 --> 00:09:00.800
video call mistake, like forgetting to wear clothes.

00:08:59.120 --> 00:09:04.200
It wouldn't be nearly as embarrassing or criminal. And you shouldn't forget to

00:09:02.440 --> 00:09:08.680
come back on Wednesday for more tech news. Also, you know,

00:09:07.200 --> 00:09:12.720
got to put some pants on. Just basic basic respect for me.
