WEBVTT 00:00:00.000 --> 00:00:05.560 Some hack for good, some hack for evil, 00:00:03.360 --> 00:00:09.320 and some hack because Taylor Swift's Eras Tour sold out too quickly. Or at 00:00:07.480 --> 00:00:13.600 least that's how it seems now that Ticketmaster hackers have leaked what 00:00:11.440 --> 00:00:17.600 they claim are valid Taylor Swift tickets. Now that might sound cool and 00:00:15.520 --> 00:00:22.240 Robin Hood-like, but unfortunately, it is not. This goes back to May when 00:00:20.240 --> 00:00:27.080 hacker group and sparkly twilight vampires Shiny Hunters allegedly stole 00:00:24.800 --> 00:00:32.279 the data of 500 million Ticketmaster customers, including 193 million ticket 00:00:30.160 --> 00:00:36.160 barcodes. To try and put the pressure on Ticketmaster to pay a ransom, Shiny 00:00:34.280 --> 00:00:41.280 Hunters seems to have released the ticket data for 166,000 00:00:38.800 --> 00:00:45.440 Taylor Swift tickets with instructions on how to turn this data into scannable 00:00:43.560 --> 00:00:49.400 barcodes. Ticketmaster has released a statement saying no customers are at 00:00:47.280 --> 00:00:53.600 risk of losing their tickets because their SafeTix technology refreshes 00:00:51.720 --> 00:00:57.120 ticket barcodes every few seconds, preventing them from being stolen or 00:00:55.080 --> 00:01:01.800 copied. Having said that, they also advertise that their barcodes are saved 00:00:59.040 --> 00:01:06.160 offline to the Ticketmaster app once viewed, which could imply the tickets 00:01:04.199 --> 00:01:10.000 could be transferred. One software engineer already found a way around 00:01:08.000 --> 00:01:13.520 SafeTix just to avoid using Ticketmaster's god-awful app. Oh, and 00:01:12.080 --> 00:01:17.160 also scalpers have been bypassing Ticketmaster's rotating barcodes for at 00:01:15.160 --> 00:01:20.960 least a year now. So, yeah, they're they're just straight-up lying. Boeing 00:01:18.720 --> 00:01:25.920 has agreed to plead guilty to conspiracy to defraud the US government in relation 00:01:23.400 --> 00:01:31.320 to the two fatal crashes that occurred in 2018 and 2019. Those crashes killed a 00:01:28.640 --> 00:01:35.560 total of 346 people, but Boeing gave the Department of Justice a strong defense 00:01:32.960 --> 00:01:40.880 against going to trial. Money. In 2021, Boeing made a $2.5 00:01:38.480 --> 00:01:45.000 billion deal with the DOJ that required the aeronautics firm to implement major 00:01:42.640 --> 00:01:49.760 safety changes and engage in no wrongdoing for 3 years. But after the 00:01:47.760 --> 00:01:53.560 door blew out on that Alaska Airlines flight earlier this year, the DOJ 00:01:51.880 --> 00:01:57.920 smartly determined that Boeing had broken the terms of the deal. Now, 00:01:55.480 --> 00:02:02.920 Boeing has accepted a new deal to avoid a trial that will require them to spend 00:02:00.160 --> 00:02:06.680 at least $455 million on improving compliance and safety programs. And 00:02:05.320 --> 00:02:09.759 they're definitely not going to break another promise to the US government. 00:02:08.520 --> 00:02:13.560 That'd be crazy. They pinky swore. 00:02:11.560 --> 00:02:17.040 Not everyone is super happy with this deal. For example, the families of the 00:02:15.560 --> 00:02:20.560 crash victims. They've made it known that they will be asking the court to 00:02:18.560 --> 00:02:24.800 reject the deal, believing it fails to hold Boeing accountable. And yeah, when 00:02:23.040 --> 00:02:28.960 you think about how Boeing's deception of federal regulators led to hundreds of 00:02:26.640 --> 00:02:34.040 deaths, a promise to do better next time does sound a bit inadequate. PC hardware 00:02:31.080 --> 00:02:38.240 manufacturer ZOTAC has come under fire for allowing anyone to access private 00:02:36.320 --> 00:02:41.960 customer data with a simple Google search. According to an investigation by 00:02:40.240 --> 00:02:46.360 Gamers Nexus, the company seemed to have been storing RMA files containing full 00:02:44.840 --> 00:02:49.960 names, mailing addresses, and other sensitive customer information in a 00:02:47.880 --> 00:02:53.760 publicly accessible server, making them accessible in Google search. Not only 00:02:52.280 --> 00:02:58.280 was customer data exposed, but business-to-business invoices were also 00:02:56.320 --> 00:03:02.080 equally Googleable. Fortunately, it seems ZOTAC is now trying to fix the 00:03:00.120 --> 00:03:05.840 issue. While links will still show up in web searches, they appear to be dead 00:03:04.160 --> 00:03:09.560 when you actually click on them. But before we give ZOTAC too much credit for 00:03:07.720 --> 00:03:13.480 doing the bare minimum after a maximum screw-up, some information is still 00:03:11.600 --> 00:03:17.440 stored in Google's cache. So, if you happen to have bought and then returned 00:03:15.560 --> 00:03:21.640 any ZOTAC merchandise, you may want to search your name and ZOTAC to see if any 00:03:19.440 --> 00:03:25.080 results pop up. You can request that Google remove the result from search by 00:03:23.720 --> 00:03:28.760 clicking the three dots in the top right of the result, or you can leave it up 00:03:27.080 --> 00:03:31.760 and just pretend you're famous. I'm basically Taylor Swift. 00:03:30.120 --> 00:03:35.800 being internet famous isn't really your thing, check out our sponsor DeleteMe, 00:03:33.840 --> 00:03:40.400 the pros at making sure your personal information is personal. Keeping your 00:03:38.120 --> 00:03:44.040 family's online life private isn't just about you. It's a team effort. That's 00:03:42.280 --> 00:03:47.880 why DeleteMe now has family plans to cover everyone. Each family member gets 00:03:46.320 --> 00:03:51.680 their own personalized data cleanup to remove their information from the web. 00:03:50.000 --> 00:03:55.880 From the kids to the grown-ups, they've got everyone protected from online 00:03:53.320 --> 00:03:59.040 snoops and scams. And managing it all is easy peasy, so you don't even have to 00:03:57.560 --> 00:04:02.680 think about it. Head on over to the link in the video description out DeleteMe 00:04:01.000 --> 00:04:07.080 today. Make sure to get a parent's permission before handling quick bits. 00:04:04.800 --> 00:04:12.160 They're very sharp. Contrary to previous rumors, AM5 will not be getting a boost 00:04:10.160 --> 00:04:17.040 in the 3D V-Cache department over the previous 7000 X3D series chips. 00:04:14.880 --> 00:04:24.040 According to WCCFTech, the new 9000 X3D processors will feature 00:04:19.400 --> 00:04:26.360 up to 128 or 96 MB of L3 cache on dual 00:04:24.040 --> 00:04:31.040 and single CCDs, respectively. If there's one thing we love in technology, 00:04:28.080 --> 00:04:35.040 it's when things stay the same. Like core counts and clock speeds, the latter 00:04:32.960 --> 00:04:39.000 of which haven't been confirmed yet for the X3D variants. Unless you're into 00:04:36.720 --> 00:04:44.080 overclocking, you might want to wait to upgrade. Qualcomm seems to be leaving 00:04:41.200 --> 00:04:48.040 users of ARM-based Copilot Plus laptops to fend for themselves when it comes to 00:04:45.760 --> 00:04:52.760 compatibility issues. After Microsoft espoused its Prism x86 emulator for 00:04:50.480 --> 00:04:58.360 Snapdragon X notebooks, Samsung warned customers that its Galaxy Book Edge 4 00:04:54.680 --> 00:05:00.520 Copilot Plus PC cannot run some common 00:04:58.360 --> 00:05:04.560 software. According to The Register, Qualcomm is simply directing concerned 00:05:02.600 --> 00:05:08.640 users to community-made crowdsourced websites that list compatible apps 00:05:06.760 --> 00:05:12.840 without explaining why some apps can't be emulated. Meanwhile, Microsoft is 00:05:10.520 --> 00:05:16.360 apparently continuing to parrot that x86 emulation works great. But hey, I guess 00:05:14.840 --> 00:05:20.280 the Windows on ARM revolution couldn't be a real revolution if the new regime 00:05:18.520 --> 00:05:24.280 wasn't pumping up propaganda. It's a real M1 moment. It takes a while. 2 00:05:22.720 --> 00:05:27.960 years for Apple. We just learned that last month, police in Phoenix, Arizona 00:05:26.240 --> 00:05:32.040 pulled over an autonomous Waymo vehicle that was driving in the wrong lane 00:05:29.800 --> 00:05:35.840 towards oncoming traffic. The car's onboard system had apparently gotten a 00:05:34.000 --> 00:05:39.960 bit scrambled by inconsistent construction signs and wound up running 00:05:38.080 --> 00:05:44.320 a red light like a confused senior trying their best. The car had neither a 00:05:42.200 --> 00:05:48.240 driver nor a passenger, and the police dispatch records note that the 00:05:45.680 --> 00:05:52.440 responding officer was unable to issue citation to computer. According to 00:05:50.520 --> 00:05:54.880 Waymo, its cars are three times better at avoiding collisions than human 00:05:53.600 --> 00:05:58.720 drivers. Because human drivers also suck. It's 00:05:56.720 --> 00:06:02.520 like multiplying by zero. Microsoft's Notepad is finally getting an upgrade 00:06:00.280 --> 00:06:06.440 though. Spell check and auto-correct 41 years into development. What's next? 00:06:04.200 --> 00:06:09.800 Predictive text in 2034? The new features came out to select users 00:06:08.080 --> 00:06:13.200 earlier this year, but now that the massively complicated beta test is 00:06:11.320 --> 00:06:17.640 complete, the team has deemed it ready and safe for everyone on Windows 11. 00:06:15.880 --> 00:06:21.080 There's dozens of us. Along with all of the other developments over the past few 00:06:19.120 --> 00:06:26.440 years like find and replace and text zooming, the debate over Notepad versus 00:06:23.240 --> 00:06:28.760 Notepad++ is over. Plus plus wins. Just 00:06:26.440 --> 00:06:33.680 use that one. Please. And Australian telecom companies that are now sending 00:06:30.440 --> 00:06:35.440 suspected spam callers to Apate, an 00:06:33.680 --> 00:06:39.520 AI-powered system designed to learn more about scammers while wasting their time 00:06:37.600 --> 00:06:44.560 and frustrating their efforts. Apate is modeled off past scam baiting systems 00:06:41.440 --> 00:06:46.600 like Lenny, a 2011 chatbot meant to 00:06:44.560 --> 00:06:51.440 imitate a telephone scammer's perfect victim, a lonely old man desperate to 00:06:48.840 --> 00:06:56.240 talk and annoy the out of them. Unlike Lenny, however, Apate can imitate 00:06:53.720 --> 00:07:00.440 victims of any age and background, making it like a shape-shifting 00:06:57.960 --> 00:07:05.200 time-wasting hydra of an old man who just wants to talk. My grandkids never 00:07:03.040 --> 00:07:09.440 call. Where am I? Who are you? I DON'T HAVE any grandkids, but it won't 00:07:07.880 --> 00:07:12.840 be a waste of your time to come back on Wednesday for more tech news, unless you 00:07:11.160 --> 00:07:16.800 consider hearing tech news a waste of time. But in that case, why are you here 00:07:14.760 --> 00:07:19.360 now? Still, come back though.