WEBVTT 00:00:00.640 --> 00:00:07.560 I was a little worried, but on my drive into work, Harry Nilsson's 1971 hit 00:00:05.160 --> 00:00:12.720 Coconut came on and I knew that today was going to be okay. Put the tech in 00:00:09.840 --> 00:00:18.920 the news and drink them both together. Later, Sisqo's Thong Song came on. 00:00:16.360 --> 00:00:23.280 Sony PlayStation and AMD wanted to give a glimpse at the next-gen tech that will 00:00:21.200 --> 00:00:27.840 power the PlayStation 6. So, who better to awkwardly read a script about that 00:00:24.920 --> 00:00:34.000 off a teleprompter, hey, than AMD exec Jack Houen and Dana Carvey from SNL 00:00:31.080 --> 00:00:39.400 playing PS5 lead architect Mark Cerny. The update on the two companies' Project 00:00:36.560 --> 00:00:43.960 Amethyst collaboration detailed three apparently important technologies 00:00:41.000 --> 00:00:51.480 shaping its next-gen RDNA GPUs with top-tier techno babble names like neural 00:00:47.240 --> 00:00:53.680 arrays, radiance cores, and universal 00:00:51.480 --> 00:00:59.440 compression. These technologies will provide scalability as workloads grow 00:00:56.240 --> 00:01:02.120 and unified light transport, which are 00:00:59.440 --> 00:01:08.040 cool, but unfortunately, the extremely hyped symbiotic frame reintegration 00:01:05.880 --> 00:01:12.440 was not mentioned. Why did I even come to this TED Talk? And besides, when is 00:01:10.000 --> 00:01:17.000 the PS6 even coming out? Well, according to one of our favorite leakers, Kepler, 00:01:14.520 --> 00:01:21.480 Sony is planning to launch the PS6 in 2027. So, for now, you're going to have 00:01:19.600 --> 00:01:25.920 to just let all those cool buzzwords rattle around in your head until you can 00:01:23.120 --> 00:01:29.520 envision just how totally gnarly this beast is going to be. 00:01:27.840 --> 00:01:33.800 I think Intel has unveiled their next-gen Panther Lake processors. The 00:01:32.360 --> 00:01:39.280 company says Panther Lake is going to launch by the end of this year, on paper 00:01:36.320 --> 00:01:42.520 at least, and it's going to fix everything. 00:01:40.680 --> 00:01:47.000 After this, smooth sailing. While Intel's previous laptop chips were 00:01:44.480 --> 00:01:51.600 divided into Lunar Lake and Arrow Lake families, this laptop generation will be 00:01:49.280 --> 00:01:56.000 Panther Lake all the way down and will apparently leverage the best parts of 00:01:53.880 --> 00:02:01.520 its predecessors, Lunar Lake's power efficiency and Arrow Lake's 00:01:58.880 --> 00:02:05.360 compatibility with Skyrim memes. Think that was the best thing going for it. 00:02:03.200 --> 00:02:10.280 Intel didn't reveal model numbers, but did specify three distinct package 00:02:08.119 --> 00:02:16.480 configurations, an eight-core and a 16-core, each with four new XE3 GPU 00:02:13.400 --> 00:02:18.640 cores, and another 16-core with 12 GPU 00:02:16.480 --> 00:02:25.000 cores. Wait, wait, XE3? XE2 used Intel's Battlemage GPU 00:02:21.600 --> 00:02:27.960 architecture, so that means XE3 00:02:25.000 --> 00:02:32.560 is still Battlemage. Of course, of course it is. Intel's Tom 00:02:30.200 --> 00:02:39.160 Petersen confirmed to PCWorld that the Battlemage follow-up, Celestial, won't 00:02:34.920 --> 00:02:41.080 arrive until we get next next-gen XE3P 00:02:39.160 --> 00:02:46.120 cores, which Tom is already starting to hype up. >> XE3P coming up. Ooh, chills. That got me 00:02:45.080 --> 00:02:52.840 going. But to compensate for the disappointment, Intel also announced 00:02:49.320 --> 00:02:54.760 their new upscaling tech, XESS3, which 00:02:52.840 --> 00:03:00.440 will support multi-frame generation, beating AMD to the punch already thrown 00:02:57.560 --> 00:03:06.560 by NVIDIA. But unlike Team Green, Intel will let all Arc GPUs use their new fake 00:03:03.720 --> 00:03:10.520 frames tech, even older A-series gaming cards, like Intel's the cool older 00:03:08.800 --> 00:03:15.120 brother who will let his younger sibling play with his action figures. NVIDIA's 00:03:12.520 --> 00:03:19.880 like, "No, you'll break it. No, you'll decrease the resale value." Discord is 00:03:17.800 --> 00:03:23.760 calling out the hackers who breached the chat platform's third-party service 00:03:21.720 --> 00:03:28.800 provider, not for the actual hack, they already did that, but for lying to 00:03:27.080 --> 00:03:32.920 What's next? Parking in the handicap spot on the internet? 00:03:30.960 --> 00:03:38.160 The hackers claim they've swiped the data of five and a half million unique 00:03:35.640 --> 00:03:42.160 users, including nearly 2.2 million photos of government IDs. Well, in an 00:03:40.360 --> 00:03:47.520 updated press release, Discord says, "Actually, they've only identified 00:03:44.440 --> 00:03:50.400 70,000 users whose government ID photos 00:03:47.520 --> 00:03:54.360 have been swiped, which is barely any." And told The Verge that the hackers are 00:03:52.120 --> 00:03:58.640 circulating incorrect information as a way to extort payment from Discord. Now, 00:03:57.080 --> 00:04:01.560 we actually edited our story on this data breach in Monday's episode and 00:04:00.320 --> 00:04:06.400 pinned a comment with a correction because we initially implied the breach 00:04:03.800 --> 00:04:10.560 was connected to this year's wave of age verification rollouts across platforms. 00:04:08.360 --> 00:04:15.400 But it appears the IDs in question were collected before Discord's new age 00:04:13.520 --> 00:04:19.880 verification measures, which apparently don't store photos of IDs, were ever put 00:04:17.880 --> 00:04:24.200 in place. Now, Discord updated their press release again to underline this 00:04:22.200 --> 00:04:29.440 fact by naming the customer service provider that was breached. It's called 00:04:26.640 --> 00:04:33.880 5CA. Because people keep being weird and saying this is a Discord breach, except 00:04:31.680 --> 00:04:37.600 it literally has nothing to do with Discord other than all the Discord user 00:04:35.640 --> 00:04:42.560 data that was breached. Just drop it, okay? And then check out our sponsor, 00:04:40.160 --> 00:04:47.240 Thorum, and their handcrafted unique rings made of meteorite, whiskey barrel, 00:04:44.920 --> 00:04:50.760 World War II rifle stock, Damascus steel, dinosaur fossil, and other 00:04:49.440 --> 00:04:56.280 materials you hadn't thought of as something you could make a ring out. Well, get your brain out of that box 00:04:54.280 --> 00:05:00.320 like this guy did. Thorum's founder, Caleb Martin. Back in 2012, he couldn't 00:04:58.240 --> 00:05:05.800 afford an engagement ring, so he made one himself. And then, personally made 00:05:02.680 --> 00:05:08.000 10,000 more, so others like you can wear 00:05:05.800 --> 00:05:12.280 your story, too. And it's not just rings anymore. Thorum is now making beautiful 00:05:10.000 --> 00:05:16.480 minimalist watches with the same wacky and quirky materials. Thorum's rings 00:05:14.120 --> 00:05:21.480 have over 10,000 five-star reviews. They ship in an American walnut wood ring box 00:05:18.960 --> 00:05:24.640 worldwide for free within one business day, and they got a lifetime warranty. 00:05:23.400 --> 00:05:28.400 Whether you need a wedding band, a unique gift, or you just want an awesome 00:05:26.560 --> 00:05:33.600 ring or watch, you don't need a reason. Head over to thorum.com and use code 00:05:30.440 --> 00:05:35.960 TL20 to get 20% off. The link is in the 00:05:33.600 --> 00:05:39.760 description. The quick bits are actually ageless. They used to party with Harry 00:05:38.480 --> 00:05:43.680 Nilsson. The quick bits remember the lost weekend 00:05:41.800 --> 00:05:47.360 with Harry and John Lennon, but they don't talk about it. 00:05:45.280 --> 00:05:52.480 Apple is making some tweaks to how their accounts work in Texas. Starting in 00:05:49.800 --> 00:05:56.640 January, Texas's new age verification law will require app stores and 00:05:54.080 --> 00:06:00.360 developers to check users' ages before letting them download apps. Apple says 00:05:58.560 --> 00:06:04.560 that if you're in Texas and create an Apple account, you will have to verify 00:06:02.680 --> 00:06:08.720 you're over 18. Otherwise, you'll need to join a family sharing group and a 00:06:06.960 --> 00:06:12.680 guardian will have to approve all your downloads and purchases, so make good 00:06:10.760 --> 00:06:16.520 choices. Developers will also need to adjust their apps to follow the rules, 00:06:14.440 --> 00:06:20.400 but Apple's releasing tools to help them with age checks and getting parental 00:06:18.280 --> 00:06:24.720 consent. Google also announced they're doing something similar, letting apps 00:06:22.320 --> 00:06:28.560 access info like users' age range, verification status, and whether an 00:06:26.360 --> 00:06:32.960 account is supervised. Both companies are also laying out plans for what to do 00:06:30.800 --> 00:06:36.960 when the age verification government IDs inevitably get hacked. Step one, wasn't 00:06:35.400 --> 00:06:41.440 me. California's been on a consumer rights 00:06:39.240 --> 00:06:46.280 kick. Governor Gavin Newsom just signed a law that will force browsers to 00:06:43.480 --> 00:06:51.280 provide a simple portal that will allow users to opt out of third-party data 00:06:48.760 --> 00:06:55.600 collection across all websites. Whether the browser companies actually at it is 00:06:53.600 --> 00:07:01.000 remains to be seen, but California also tightened rules on streaming platforms 00:06:57.840 --> 00:07:03.160 by banning jarringly loud ad spots from 00:07:01.000 --> 00:07:06.200 playing during streaming. It's almost like the state that houses many of the 00:07:04.560 --> 00:07:10.040 world's biggest tech companies has a better understanding of how obnoxious 00:07:08.120 --> 00:07:13.840 online data collection and advertising efforts have become. 00:07:11.600 --> 00:07:17.760 Maybe that's their home advantage. California knows the call is coming from 00:07:15.840 --> 00:07:20.560 inside the house. And now we just need to follow their lead to get away from 00:07:19.320 --> 00:07:25.920 THESE MONSTERS. A LOUD AD. Battlefield 6 just launched, 00:07:23.720 --> 00:07:29.160 but not all its new players are actually getting to 00:07:27.440 --> 00:07:32.720 uh, you know, play the game. According to the Battlefield Comms Twitter 00:07:30.920 --> 00:07:36.520 account, some players are having issues with accessing the game at all, while 00:07:34.960 --> 00:07:40.040 others are just getting stuck in old-fashioned queues. I mean, it's kind 00:07:38.200 --> 00:07:44.560 of nostalgic. Based on what I've learned about war from TV, getting into the 00:07:42.440 --> 00:07:49.760 military isn't always that easy and soldiers do end up sitting around a lot 00:07:46.600 --> 00:07:51.800 between episodes of horrifying 00:07:49.760 --> 00:07:55.480 uh, conflict. So, maybe Battlefield 6 is just striving to be more realistic. 00:07:54.200 --> 00:08:00.520 Good job. South Korea's online government services 00:07:57.760 --> 00:08:05.480 are reeling after a giant fire at a state data center. The blaze caused the 00:08:02.920 --> 00:08:11.160 suspension of 70 online government services and destroyed 858 00:08:08.480 --> 00:08:16.800 terabytes of data, which was thoughtfully reported to be equivalent 00:08:13.440 --> 00:08:19.360 to 449 and a half billion sheets of 00:08:16.800 --> 00:08:24.640 A4-sized paper. Very helpful. Thank you so much. Worst of all, apparently, the G 00:08:22.120 --> 00:08:29.680 Drive system, no relation to Google, is government drive, uh, it was completely 00:08:26.880 --> 00:08:33.840 destroyed in the fire and they couldn't have backed it up, according to an 00:08:31.000 --> 00:08:37.640 unnamed official, because it was so big. Too big to back up. Sorry. While the 00:08:35.560 --> 00:08:42.840 incident is being reported as a battery fire, inspired by K-pop demon hunters, I 00:08:41.000 --> 00:08:48.000 did some quick research about Korean fire demons and I'm almost certain these 00:08:45.760 --> 00:08:51.520 fires were caused by the dastardly Dokkaebi 00:08:49.560 --> 00:08:55.080 and likely not the fire goddess Joangshin, 00:08:53.480 --> 00:09:00.200 unless a housewife did something bad to a fireplace's hearth. Wow. That's 00:08:57.840 --> 00:09:05.720 something to Google. And Figure claims that its new Figure 3 robot can wash 00:09:03.280 --> 00:09:08.560 dishes, clean floors, and handle other chores. 00:09:07.360 --> 00:09:15.520 Great. Good enough. I'm a tired dad. I've seen The Jetsons. Bring on the snarky robot 00:09:12.520 --> 00:09:17.600 maids. In a video released by Figure, we 00:09:15.520 --> 00:09:22.040 get to see the Figure 3 doing all sorts of jobs and it all looks pretty cool and 00:09:19.440 --> 00:09:26.600 and potentially even useful. However, at around the last minute of the video, the 00:09:23.760 --> 00:09:30.760 music takes on a more sinister tone and we see the robots doing 00:09:28.680 --> 00:09:36.760 uh, people's jobs. Hmm, probably nothing. Figure CEO Brett 00:09:34.120 --> 00:09:41.560 Adcock posted on LinkedIn that nothing in the film was teleoperated, which made 00:09:39.520 --> 00:09:45.360 me say, "Film? What are you from Europe?" But no, he's from Illinois. 00:09:43.840 --> 00:09:49.120 Anyway, if you thought I was being glib about these robots stealing your jobs, 00:09:47.160 --> 00:09:53.200 Figure has already had robots working on a BMW production line for five months. 00:09:51.720 --> 00:09:56.480 All right, all this automation better bring about that universal basic income 00:09:55.000 --> 00:10:01.560 everyone's been talking about, or otherwise, why did Bernie Sanders just 00:09:58.600 --> 00:10:05.120 posted 10-minute video talking about how dangerous the robots are? What are we 00:10:03.320 --> 00:10:09.000 going to do about these robots? Hey, you know what? Let's all just relax, okay? I 00:10:07.160 --> 00:10:13.880 hope you enjoyed today's show. We won't be back until next Wednesday. Monday is 00:10:11.480 --> 00:10:18.280 a holiday, but please do come back. I found a wiki page for something called a 00:10:15.800 --> 00:10:22.480 novelty song, which includes mentions of Weird Al, Randy Newman, and Frank Zappa. 00:10:20.640 --> 00:10:25.560 So, obviously, I have a long weekend of research ahead of me.