WEBVTT 00:00:00.000 --> 00:00:04.880 It's time for tech news, and you know what that means. 00:00:04.880 --> 00:00:09.080 I know what it means, but why don't you say it? So I know you know. 00:00:09.080 --> 00:00:12.120 OpenAI just had a weekend that puts the one at Bernie's 00:00:12.120 --> 00:00:15.840 to shame. The twists and turns have honestly made my head hurt, 00:00:15.840 --> 00:00:19.760 but here's our summary. Late Friday evening, CEO Sam Altman 00:00:19.760 --> 00:00:23.280 was fired by the four other members of the OpenAI board 00:00:23.280 --> 00:00:26.560 while President Greg Brockman was removed as chairman. 00:00:26.560 --> 00:00:31.000 They wanted an Altman. You're too much of a normal man. Upon hearing the news, Greg quit 00:00:31.000 --> 00:00:35.560 and tweeted his account of recent events, implying, possibly unintentionally, 00:00:35.560 --> 00:00:43.400 that OpenAI chief scientist and board member, Ilya Sutskiver, was the brutee in this Shakespearean drama. 00:00:43.400 --> 00:00:46.560 Most of you will get that. What's that knife for, bro? You two brutes? 00:00:46.560 --> 00:00:49.880 Shit. It's still not clear what the board's exact reasons 00:00:49.880 --> 00:00:55.480 for the shakeup were, and the story is complicated by OpenAI's truly weird corporate structure, 00:00:55.480 --> 00:00:59.360 where the non-profit board controls the capped profit company. 00:00:59.360 --> 00:01:04.720 But some speculate that Sam seeking investment for a new AI chip company played a role 00:01:04.720 --> 00:01:08.440 as OpenAI's board accused him of being not consistently 00:01:08.440 --> 00:01:13.800 candid in his communications with them. Despite a later memo from OpenAI's COO, 00:01:13.800 --> 00:01:17.580 Brad Lightcap, cool name, definitively claiming 00:01:17.580 --> 00:01:21.040 that Sam was not fired for malfeasance, 00:01:21.040 --> 00:01:26.580 a French word meaning weasel. If that confused you, then you know how everyone, 00:01:26.620 --> 00:01:31.940 including the OpenAI board, felt this weekend. They apparently agreed to step down 00:01:31.940 --> 00:01:36.740 and bring back Sam and Greg, right before Microsoft swooped in 00:01:36.740 --> 00:01:41.620 and announced they'd hired Sam, Greg, and a bunch of other OpenAI employees. 00:01:41.620 --> 00:01:45.580 Right after that, OpenAI hired Twitch co-founder, 00:01:45.580 --> 00:01:52.780 Emmet Scheer, as interim CEO, replacing day and a half old interim CEO, Mura Murati, 00:01:52.780 --> 00:01:56.660 presumably because she just needed more experience, and her name sounds like a car. 00:01:56.660 --> 00:02:02.100 We can't have that. But really, Emmet may have been chosen because, like the safety-minded board members, 00:02:02.100 --> 00:02:06.380 he said he wants AI development to slow down. 00:02:06.380 --> 00:02:09.900 He also said that CEO jobs could be replaced by AI, 00:02:09.900 --> 00:02:14.940 so slowing down means he could enjoy his new position for longer than five minutes, so that's probably. 00:02:14.940 --> 00:02:20.940 Emmet may soon be captain of a ghost ship, though, a letter from OpenAI employees threatening to resign 00:02:20.940 --> 00:02:24.420 unless the board steps down and brings back Sam. 00:02:24.420 --> 00:02:31.460 And calling back bars to the break room. And what? Was signed by 650 of the company's 770 employees 00:02:31.460 --> 00:02:35.300 on Monday morning, including Ilya Sutskiver. 00:02:35.300 --> 00:02:38.620 A2, Brute? What? Brute? 00:02:38.620 --> 00:02:43.660 You're back. What are you doing here? Confusingly, Ilya tweeted that he deeply regrets 00:02:43.660 --> 00:02:46.740 his participation in the board's actions. 00:02:46.740 --> 00:02:50.060 A tweet Greg reposted with a heart emoji. 00:02:50.060 --> 00:02:53.740 Mura Murati also replied with a heart to Sam's tweet 00:02:53.780 --> 00:02:57.540 saying, I love OpenAI, so I don't know whether these people are actually still trying 00:02:57.540 --> 00:03:01.060 to be friends despite all the drama, or whether they just don't know what emojis mean. 00:03:01.060 --> 00:03:05.500 Now, here's the real kicker. The Verge claims multiple sources are saying 00:03:05.500 --> 00:03:09.420 that Sam and Greg's Microsoft situation isn't a done deal 00:03:09.420 --> 00:03:13.340 and that they are still willing to return to OpenAI if the board resigns. 00:03:13.340 --> 00:03:16.980 And Sam did recently imply that the OpenAI team 00:03:16.980 --> 00:03:20.300 are all going to work together some way or the other. 00:03:20.300 --> 00:03:25.100 As for Microsoft, well, they've invested billions in OpenAI, so whether they get Sam 00:03:25.100 --> 00:03:29.300 or Sam returns to OpenAI with a new board, this is really a win-win for them. 00:03:29.300 --> 00:03:33.780 And hey, how about a seat for old Satya while we're playing musical chairs, eh? 00:03:33.780 --> 00:03:37.660 Ah, okay, back to work making a digital god. 00:03:37.660 --> 00:03:41.980 This whole thing sounds like the most hard to follow polycule I've ever heard of. 00:03:41.980 --> 00:03:46.860 Honestly, I'm just proud of myself for following it all the way through. Sunbird, the company nothing partnered with 00:03:46.860 --> 00:03:53.580 on their nothing chats iMessage compatible app for Android has apparently comically misrepresented 00:03:53.580 --> 00:03:57.700 the security of their services. Multiple professional and amateur investigators 00:03:57.700 --> 00:04:03.860 have claimed that the full contents of messages sent through Sunbird service are accessible in plain text 00:04:03.860 --> 00:04:09.540 by not only Sunbird, but by anyone with a smattering of hacker know-how, despite Sunbird claiming 00:04:09.540 --> 00:04:12.980 not to collect any data because they use end-to-end encryption. 00:04:12.980 --> 00:04:17.140 On Twitter, Sunbird tried to dismiss security researchers' concerns, 00:04:17.180 --> 00:04:23.220 but all of their points seem to have been systematically refuted by a team from texts.com. 00:04:23.220 --> 00:04:27.100 When enough had been enough, nothing removed the chance beta 00:04:27.100 --> 00:04:30.460 from the Play Store on Saturday, saying they were delaying the launch 00:04:30.460 --> 00:04:35.220 to fix several bugs. In what, the Sunbird team's brains? 00:04:35.220 --> 00:04:38.780 These are probably like Southern Hemisphere bugs. Like rhino beetles. Yeah. 00:04:38.780 --> 00:04:41.980 And Sunbird themselves put their services on hold. 00:04:41.980 --> 00:04:45.300 Now this is another story where it's very unclear 00:04:45.300 --> 00:04:49.820 what's actually going on. A text.com engineer was banned from Sunbird's Discord 00:04:49.820 --> 00:04:54.940 after making a tool that lets users delete Sunbird's copies of their stored data, 00:04:54.940 --> 00:04:58.180 which Sunbird is apparently storing. 00:04:58.180 --> 00:05:02.100 You know what, I think we better delay the launch though. Yeah, just let all blow over. 00:05:02.100 --> 00:05:04.260 Yeah! Nice bits you got there. 00:05:05.380 --> 00:05:08.420 Be a shame if someone quickened them. 00:05:08.420 --> 00:05:12.380 Reviews are out for AMD's Ryzen Threadripper 7970X 00:05:12.380 --> 00:05:16.540 and 7980X, and the general consensus is 00:05:16.540 --> 00:05:21.060 that these chips are sick AF. If your name isn't Brutus, that means they're good. 00:05:21.060 --> 00:05:26.300 Not only that, but they stand as a formidable and currently uncontested entry into the niche 00:05:26.300 --> 00:05:29.660 of prosumer processors for high-end desktops. 00:05:29.660 --> 00:05:32.900 Ironically, a term coined by Intel doesn't feel good. 00:05:32.900 --> 00:05:37.580 The top SKU, the 7980X model has 64 cores, 128 threads, 00:05:37.580 --> 00:05:42.500 a base block of 2.5 gigahertz and a turbo clock that can add up to 5.1 gigahertz. 00:05:42.500 --> 00:05:46.820 Finally, a fitting heir to the Threadripper 3000 series. 00:05:46.820 --> 00:05:50.720 Here's hoping AMD won't get bored and completely skip a generation like they did 00:05:50.720 --> 00:05:55.300 with the purely hypothetical Threadripper non-pro 5000 series. 00:05:55.300 --> 00:05:58.700 It's leaving the throne unfilled. It's not right. Drop your crown, King. 00:05:58.700 --> 00:06:02.220 Here. YouTube seems to be intentionally slowing itself down 00:06:02.220 --> 00:06:05.380 on Firefox and Safari, at least for some users. 00:06:05.380 --> 00:06:10.140 It looks like a hard-coded five-second delay that disappears when the site is fooled 00:06:10.140 --> 00:06:13.740 into thinking it's running on Chrome. Now, it's tempting to assume that Google 00:06:13.740 --> 00:06:17.500 is simply punishing users for using a competing browser, 00:06:17.500 --> 00:06:23.180 but it's also plausible that this is a bug introduced by Google's heavy-handed ad block filtering. 00:06:23.180 --> 00:06:26.240 Always remember, hand lawns razor and never attribute to malice 00:06:26.240 --> 00:06:30.060 what can adequately be explained by neglect or incompetence, 00:06:30.060 --> 00:06:33.300 except in this case, it's, you know, it's Google. 00:06:33.300 --> 00:06:37.500 I've done this before, but we don't know. NVIDIA and SK Hynex are working together 00:06:37.500 --> 00:06:41.820 on a new GPU design, according to Korean news site, Joong-ang. 00:06:41.820 --> 00:06:47.120 The design would have HBM-4 memory chips stacked directly on top of the GPU, 00:06:47.120 --> 00:06:51.180 like a hat that makes you much better at remembering what you said to Amanda in fourth grade. 00:06:51.180 --> 00:06:57.260 Like, what were you thinking? Get it off. This structure sounds similar to AMD's 3D Vcash 00:06:57.260 --> 00:07:01.380 used in the company's X3D processors, which are really good at gaming 00:07:01.380 --> 00:07:04.980 because they help you remember where the bomb sites are in Counter-Strike 2. 00:07:04.980 --> 00:07:08.020 That's what I think they do. I don't design processors. 00:07:08.020 --> 00:07:11.180 And, you know, Valorant for the win. I don't play that either. 00:07:11.180 --> 00:07:14.900 Details of Intel's upcoming Lunar Lake MX have leaked, 00:07:14.900 --> 00:07:19.660 showing that the CPU, GPU, and memory will all be on the same SOC, 00:07:19.660 --> 00:07:23.140 like Apple's unified memory architecture. Ooh. 00:07:23.140 --> 00:07:27.380 Whoa. No, my watch. Stop that. This will be the first commercial release 00:07:27.380 --> 00:07:32.340 of the technology that Intel showed off to the press earlier this year at their Arizona fab. 00:07:32.340 --> 00:07:36.700 This leak is so big, it almost makes you forget that Meteor Lake U, 00:07:36.700 --> 00:07:39.880 the architecture Lunar Lake MX is meant to replace, 00:07:39.880 --> 00:07:45.360 hasn't actually been officially released yet, despite Intel's promise of a 2023 launch. 00:07:45.360 --> 00:07:49.520 But I haven't forgotten, Pat. Your mind tricks don't work on me. 00:07:49.520 --> 00:07:54.520 And if you paper launch the Meteor Lake U, I'm not sending you a Christmas card this year. 00:07:54.520 --> 00:07:59.280 Oh my God, I came out of nowhere. You're getting cold. An auto tech company, Vallejo, 00:07:59.280 --> 00:08:02.480 is suing NVIDIA after a video call Gaff 00:08:02.480 --> 00:08:08.600 exposed a Ledge Trade secret theft. Basically, a Vallejo employee left for a job in NVIDIA 00:08:08.600 --> 00:08:11.680 and took Vallejo's work with him. 00:08:11.680 --> 00:08:16.320 This came to light months later when he accidentally screen-shared stolen code 00:08:16.320 --> 00:08:20.800 during a video call with Vallejo employees, all because one employee couldn't make 00:08:20.800 --> 00:08:25.060 a normal video call mistake, like forgetting to wear clothes. 00:08:25.060 --> 00:08:29.440 It wouldn't be nearly as embarrassing or criminal. And you shouldn't forget to come back on Wednesday 00:08:29.440 --> 00:08:31.720 for more tech news. Also, you know, 00:08:33.160 --> 00:08:36.760 gotta put some pants on. Just basic, basic respect for me.