WEBVTT 00:00:00.000 --> 00:00:05.840 Intel just unveiled Puma, a photonic chip that sounds less like a real thing and more like an 00:00:05.840 --> 00:00:10.560 April Fools joke from the time before most tech companies decided that was cringe. Razer didn't 00:00:10.560 --> 00:00:16.480 get the memo. I'm Riley Murdoch, this is TechLinked and you might want to sit down as I tell you that 00:00:16.480 --> 00:00:23.600 the prototype CPU Intel showed off at Hot Chips 2023 is based on a custom risk architecture 00:00:23.680 --> 00:00:32.800 with eight cores and 66 threads per core for a frankly offensive 528 total threads. 00:00:34.880 --> 00:00:41.200 Wow! Modern x86 CPUs usually only have two threads per core, but that hasn't always been the case. 00:00:41.200 --> 00:00:46.160 Intel's old Xeon 5 could do four threads per core, IBM's Power 8 could do 00:00:46.800 --> 00:00:51.440 eight, and Sun's Spark chips thought they were fancy going up to 16. 00:00:51.920 --> 00:00:57.200 But adding threads makes each thread weaker, and a ton of weak threads wouldn't benefit most 00:00:57.200 --> 00:01:03.280 workloads today. Except for the pay to buy scale workloads Intel has designed this CPU to tackle 00:01:03.280 --> 00:01:08.640 with its one terabyte per second of data throughput and optical interconnects between 00:01:08.640 --> 00:01:14.640 chips so they can be connected together in eight socket server sleds that in turn connect to each 00:01:14.640 --> 00:01:19.440 other to create Sam Altman's wet dream. Pam Anderson, what are you doing here? 00:01:20.400 --> 00:01:22.720 She's like made of silicon. 00:01:23.920 --> 00:01:30.160 iFixit is taking the right to repair fight to McDonald's because everyone deserves a burger 00:01:30.160 --> 00:01:38.400 with all the fixins. No, the target here is McDonald's notoriously unreliable ice cream 00:01:38.400 --> 00:01:44.320 machines. iFixit bought and tore down one of the machines, which aren't terribly complex. 00:01:44.320 --> 00:01:50.080 The problem is that they're prone to overheating, not ideal in an ice cream machine, 00:01:50.080 --> 00:01:56.560 and their error codes are just simply baffling. Employees have tried to read the effing manual, 00:01:56.560 --> 00:02:01.600 but the manual appears to have been written by an infinite number of chimpanzees with a grudge 00:02:01.600 --> 00:02:08.080 against the working class. The machines are built and must be repaired by Taylor, which is either 00:02:08.080 --> 00:02:15.040 an ice cream machine company or a 19 year old sorority sister. Taylor is infamously slow to 00:02:15.040 --> 00:02:20.000 respond to repair requests, probably because she's so busy with cheer practice. Is this based on a 00:02:20.000 --> 00:02:25.600 personal experience of yours just now? No. Okay. Despite that, 25% of Taylor's profits come from 00:02:25.600 --> 00:02:35.360 service technician callouts, which cost $315 per 15 minutes of work. That's like $1,200 an hour. 00:02:35.360 --> 00:02:40.320 Franchisees would obviously prefer to work with a cheaper, more responsive repair service, 00:02:40.320 --> 00:02:45.600 but the DMCA is what allowed Taylor to put in a digital lock that prevents anyone else from 00:02:45.600 --> 00:02:50.560 getting in there. So now iFixit is petitioning the copyright office for an exemption that allows 00:02:50.560 --> 00:02:56.320 third-party repair workers to fix these machines and for Congress to fix the DMCA in general, 00:02:56.320 --> 00:03:00.560 because working at McDonald's is already punishment enough. YouTube will be changing 00:03:00.560 --> 00:03:05.440 its community guidelines policy so that creators can get violation warnings removed from their 00:03:05.440 --> 00:03:12.080 channel if they complete an educational training course. The course is intended to explain YouTube's 00:03:12.080 --> 00:03:17.520 content policies and help creators avoid future infractions, kind of like sensitivity training 00:03:17.520 --> 00:03:23.120 for live streamers, which many of them desperately need. If creators complete the course and go 90 00:03:23.120 --> 00:03:28.480 days without violating the same policy again, then the warning will be lifted. Prior to this change, 00:03:28.480 --> 00:03:33.280 that one-time warning would simply stick around forever, increasing the risk that if a creator 00:03:33.280 --> 00:03:37.760 accidentally fell afoul of the rules again years in the future, it might lead to a formal strike 00:03:37.760 --> 00:03:43.440 against the channel. According to YouTube, more than 80% of creators who receive a warning 00:03:43.440 --> 00:03:48.720 never violate their policies again. And I guess they think that last 20% are repeat offenders 00:03:48.720 --> 00:03:56.000 because they simply didn't know being racist is bad. No one told me. But not every flagged video 00:03:56.000 --> 00:04:02.000 deserves it. Due to the sheer scope of YouTube, its sometimes nebulous guidelines, and its limited 00:04:02.000 --> 00:04:07.600 number of human content moderators, it's unfortunately easy for videos to get inappropriately flagged 00:04:07.600 --> 00:04:13.360 as inappropriate. If that happens, at least the falsely accused will have the opportunity to think 00:04:13.360 --> 00:04:17.920 about what they haven't done. You know, just when I thought the bits couldn't get any quicker, 00:04:18.880 --> 00:04:25.200 there they go. Wow. Get out of the way. They don't stop for people. In a spot of good news for 00:04:25.200 --> 00:04:30.800 people who like smartphones that fit in normal sized hands, ASUS has declared that the rumors of 00:04:30.800 --> 00:04:36.400 the Zenfones demise have been greatly exaggerated. The company says they have a strong commitment 00:04:36.400 --> 00:04:42.880 to their smartphone business and even potentially teased a Zenfone 11 release in 2024. So maybe we 00:04:42.880 --> 00:04:49.520 can finally get Riley to stop crying. I did just in time to film this. Thank God. Elon Musk live 00:04:49.520 --> 00:04:55.440 streamed a demonstration of Tesla's updated full self-driving beta, which impressively uses only 00:04:55.440 --> 00:05:01.280 cameras and algorithmic intelligence, rather than also relying on other sensors like LiDAR and radar, 00:05:01.280 --> 00:05:05.600 which they removed from the cars. During the demo, Musk sat in the driver's seat, 00:05:05.600 --> 00:05:11.040 filming on his cell phone and interacting with commenters in violation of automated driving 00:05:11.040 --> 00:05:16.640 policies put in place by none other than Tesla. At one point, the car attempted to accelerate 00:05:16.640 --> 00:05:22.400 through a red light requiring Musk to look up from his phone and intervene. So inconvenient. 00:05:22.400 --> 00:05:26.560 Police will not be issuing a ticket for a distracted driving because despite the thousands and 00:05:26.560 --> 00:05:31.360 thousands of witnesses, if it doesn't happen in front of the police, it doesn't count. 00:05:31.360 --> 00:05:38.560 Google is launching Duet AI for Workspace, which is basically Microsoft's co-pilot AI for Microsoft 00:05:38.560 --> 00:05:45.920 365 in both function and price. But you get to choose which multi-billion company gets your money. 00:05:45.920 --> 00:05:51.120 After the free trial, Duet will cost $30 per month per user for large organizations, 00:05:51.120 --> 00:05:56.160 which is exactly how much Microsoft charges. However, there's no word yet if Duet will be 00:05:56.160 --> 00:06:01.760 able to sing the share part of I Got You Babe at your company's annual karaoke night. The only 00:06:01.760 --> 00:06:05.120 thing I would really use it for, so I don't see the point right now. The FBI announced they were 00:06:05.120 --> 00:06:11.360 able to dismantle and destroy the Quackbot Botnet, a network of infected computers responsible for 00:06:11.360 --> 00:06:18.160 worldwide ransomware attacks and other cybercrimes. The FBI led Operation Duck Hunt, that's real, 00:06:18.160 --> 00:06:24.160 identified 700,000 infected computers worldwide and disrupted it by tricking those computers into 00:06:24.160 --> 00:06:30.720 downloading an uninstaller from FBI servers, which must have come packaged with a gif of the 00:06:30.720 --> 00:06:34.960 Super Nintendo dog laughing in your face. But actually, I think that would require the FBI 00:06:34.960 --> 00:06:39.600 to have the sense of humor that they inevitably lost by seeing what you all do in front of your 00:06:39.600 --> 00:06:44.240 webcams. I used to love spying on the populace, and now, I don't even know that you can do that 00:06:44.240 --> 00:06:50.160 with a camp alone. And after nearly a year of waiting, Meta's virtual avatars finally have 00:06:50.160 --> 00:06:55.200 legs. The beta for the new limbs will roll out and quest home over the next few weeks, 00:06:55.200 --> 00:07:00.560 but not in Horizon Worlds, where players will continue to resemble a levitating Lieutenant 00:07:00.560 --> 00:07:05.920 Dan, but with significantly less existential angst. There are still a few issues to buff out. For 00:07:05.920 --> 00:07:11.120 example, you can see your avatar's legs if you look into a virtual mirror, but not if you look 00:07:11.120 --> 00:07:17.280 down at your own hovering virtual torso. It's all in your head, man. Your reflected avatar also 00:07:17.280 --> 00:07:22.400 doesn't track when you crouch. Instead, the camera just sinks about a foot and leaves you 00:07:22.400 --> 00:07:28.160 staring at your own digital belly button. Which, honestly, I've wanted to do my whole life. It's 00:07:28.160 --> 00:07:36.800 so hard. That sounds weird. And all this after only 11 months of development. Truly, we live in 00:07:36.800 --> 00:07:41.440 an age of wonders. The developers wanted to work on the feature, but Mark Zuckerberg just keeps 00:07:41.440 --> 00:07:49.040 challenging everyone to bouts of jiu-jitsu. You can work on that later. Come here. I want to show 00:07:49.040 --> 00:07:54.720 you something. And it would be truly wonderful if you came back on Friday for another episode of 00:07:54.720 --> 00:08:00.800 Tackling. If you don't show up, we don't really have anything to do, so please clear your schedule 00:08:00.800 --> 00:08:02.320 because it's lonely in here.