WEBVTT

00:00:00.000 --> 00:00:05.520
Some hack for good, some hack for evil, and some hack because Taylor Swift's

00:00:05.520 --> 00:00:09.280
Errors Tour sold out too quickly, or at least that's how it seems now that

00:00:09.280 --> 00:00:14.080
Ticketmaster hackers have leaked what they claim are valid Taylor Swift tickets.

00:00:14.080 --> 00:00:18.320
Now that might sound cool and Robin Hood-like, but unfortunately it is not.

00:00:18.320 --> 00:00:23.840
This goes back to May when hacker group and sparkly Twilight Vampires, Shiny Hunters,

00:00:23.840 --> 00:00:27.840
allegedly stole the data of 500 million Ticketmaster customers,

00:00:27.840 --> 00:00:33.920
including 193 million ticket barcodes. To try and put the pressure on Ticketmaster to pay a ransom,

00:00:33.920 --> 00:00:40.160
Shiny Hunters seems to have released the ticket data for 166,000 Taylor Swift tickets,

00:00:40.160 --> 00:00:44.320
with instructions on how to turn this data into scannable barcodes.

00:00:44.320 --> 00:00:48.720
Ticketmaster has released a statement saying no customers are at risk of losing their tickets,

00:00:48.720 --> 00:00:53.600
because their safe ticks technology refreshes ticket barcodes every few seconds,

00:00:53.600 --> 00:00:57.760
preventing them from being stolen or copied. Having said that, they also advertise that

00:00:57.760 --> 00:01:02.640
their barcodes are saved offline to the Ticketmaster app once viewed,

00:01:02.640 --> 00:01:08.960
which could imply the tickets could be transferred. One software engineer already found a way around safe ticks,

00:01:08.960 --> 00:01:13.520
just to avoid using Ticketmaster's god-awful app. Oh, and also scalpers have been bypassing

00:01:13.520 --> 00:01:18.320
Ticketmaster's rotating barcodes for at least a year now, so yeah, they're just straight up lying.

00:01:18.320 --> 00:01:24.160
Boeing has agreed to plead guilty to conspiracy to defraud the US government in relation to the two

00:01:24.160 --> 00:01:30.400
fatal crashes that occurred in 2018 and 2019. Those crashes killed a total of 346 people,

00:01:30.400 --> 00:01:34.160
but Boeing gave the Department of Justice a strong defense against going to trial.

00:01:35.600 --> 00:01:41.600
Money. In 2021, Boeing made a $2.5 billion deal with the DOJ that required the aeronautics firm

00:01:41.600 --> 00:01:46.960
to implement major safety changes and engage in no wrongdoing for three years.

00:01:46.960 --> 00:01:51.840
But after the door blew out on that Alaska Airlines flight earlier this year, the DOJs

00:01:51.920 --> 00:01:55.200
smartly determined that Boeing had broken the terms of the deal.

00:01:55.200 --> 00:02:00.560
Now, Boeing has accepted a new deal to avoid a trial that will require them to spend at least

00:02:00.560 --> 00:02:06.480
$455 million on improving compliance and safety programs. And they're definitely not going to

00:02:06.480 --> 00:02:13.600
break another promise to the US government. That'd be crazy! Not everyone is super happy with this

00:02:13.600 --> 00:02:17.440
deal. For example, the families of the crash victims. They've made it known that they will

00:02:17.440 --> 00:02:21.920
be asking the court to reject the deal, believing it fails to hold Boeing accountable.

00:02:21.920 --> 00:02:26.560
And yeah, when you think about how Boeing's deception of federal regulators led to hundreds

00:02:26.560 --> 00:02:30.400
of deaths, a promise to do better next time does sound a bit inadequate.

00:02:30.400 --> 00:02:36.320
PC hardware manufacturer Zotac has come under fire for allowing anyone to access private

00:02:36.320 --> 00:02:41.040
customer data with a simple Google search. According to an investigation by Gamers Nexus,

00:02:41.040 --> 00:02:46.080
the company seemed to have been storing RMA files containing full names, mailing addresses,

00:02:46.080 --> 00:02:49.600
and other sensitive customer information in a publicly accessible server,

00:02:49.600 --> 00:02:54.320
making them accessible in Google search. Not only was customer data exposed, but business to

00:02:54.320 --> 00:02:59.760
business invoices were also equally Google-able. Fortunately, it seems Zotac is now trying to

00:02:59.760 --> 00:03:04.320
fix the issue. While links will still show up in web searches, they appear to be dead when

00:03:04.320 --> 00:03:08.640
you actually click on them. But before we give Zotac too much credit for doing the bare minimum

00:03:08.640 --> 00:03:13.680
after a maximum screw up, some information is still stored in Google's cache. So if you happen

00:03:13.680 --> 00:03:18.240
to have bought and then returned any Zotac merchandise, you may want to search your name

00:03:18.240 --> 00:03:23.120
and Zotac to see if any results pop up. You can request that Google removes the result from

00:03:23.120 --> 00:03:27.200
search by clicking the three dots in the top right of the result, or you can leave it up and

00:03:27.200 --> 00:03:33.040
just pretend you're famous. Make sure to get a parent's permission before handling quick bits.

00:03:33.040 --> 00:03:39.600
They're very sharp. Contrary to previous rumors, AM5 will not be getting a boost in the 3D Vcache

00:03:39.600 --> 00:03:46.720
department over the previous 7000X3D series chips. According to WCCF Tech, the new 9000X3D

00:03:46.720 --> 00:03:54.480
processors will feature up to 128 or 96 megabytes of L3 cache on dual and single CCDs respectively.

00:03:54.480 --> 00:04:00.080
If there's one thing we love in technology, it's when things stay the same, like core counts and

00:04:00.080 --> 00:04:04.800
clock speeds, the latter of which haven't been confirmed yet for the X3D variants. Unless you're

00:04:04.800 --> 00:04:10.080
into overclocking, you might want to wait to upgrade. Qualcomm seems to be leaving users of

00:04:10.080 --> 00:04:15.520
ARM-based Co-Pilot Plus laptops to fend for themselves when it comes to compatibility issues.

00:04:15.520 --> 00:04:20.240
After Microsoft espoused its Prism x86 emulator for Snapdragon X notebooks,

00:04:20.240 --> 00:04:26.640
Samsung warned customers that its Galaxy Book Edge 4 Co-Pilot Plus PC cannot run some common

00:04:26.640 --> 00:04:32.240
software. According to the register, Qualcomm is simply directing concerned users to community-made

00:04:32.240 --> 00:04:37.840
crowdsourced websites that list compatible apps, without explaining why some apps can't be emulated.

00:04:37.840 --> 00:04:42.720
Meanwhile, Microsoft is apparently continuing to parrot that x86 emulation works great, but hey,

00:04:42.720 --> 00:04:47.360
I guess the Windows on ARM revolution couldn't be a real revolution if the new regime wasn't pumping

00:04:47.360 --> 00:04:53.520
up propaganda. It's a real M1 moment. It takes a while. We just learned that last month, police

00:04:53.520 --> 00:04:58.080
in Phoenix, Arizona pulled over an autonomous Waymo vehicle that was driving in the wrong lane

00:04:58.080 --> 00:05:03.280
towards oncoming traffic. The car's onboard system had apparently gotten a bit scrambled by

00:05:03.280 --> 00:05:08.720
inconsistent construction signs, and wound up running a red light like a confused senior try in

00:05:08.720 --> 00:05:13.680
their best. The car had neither a driver nor a passenger, and the police dispatch records note

00:05:13.680 --> 00:05:19.600
that the responding officer was unable to issue citation to computer. According to Waymo, its

00:05:19.600 --> 00:05:24.400
cars are three times better at avoiding collisions than human drivers. Because human drivers also

00:05:24.400 --> 00:05:30.240
suck. Microsoft's notepad surprisingly got an upgrade, though. Spellcheck and autocorrect,

00:05:30.240 --> 00:05:36.000
41 years into development. What's next? Predictive text in 2034? The new features came out to select

00:05:36.000 --> 00:05:40.080
users earlier this year, but now that the massively complicated beta test is complete,

00:05:40.080 --> 00:05:45.680
the team has deemed it ready and safe for everyone on Windows 11. There's dozens of us. Along with

00:05:45.680 --> 00:05:49.920
all of the other developments over the past few years, like find and replace and tech zooming,

00:05:49.920 --> 00:05:56.240
the debate over no pad versus no pad plus plus is over. Plus plus wins. Just use that one, please.

00:05:56.240 --> 00:06:01.760
And Australian telecom companies are now sending suspected spam callers to Apatay,

00:06:01.760 --> 00:06:05.840
an AI-powered system designed to learn more about scammers while wasting their time

00:06:05.840 --> 00:06:10.480
and frustrating their efforts. Apatay is model off past scambating systems like Lenny,

00:06:10.480 --> 00:06:16.640
a 2011 chatbot meant to imitate a telephone scammer's perfect victim. A lonely old man,

00:06:16.640 --> 00:06:22.560
desperate to talk and annoy this out of them. Unlike Lenny, however, Apatay can imitate victims

00:06:22.560 --> 00:06:28.560
of any age and background, making it like a shape-shifting, time-wasting, hydra of an old man

00:06:28.560 --> 00:06:35.760
who just wants to talk. My grandkids never call. Where am I? Who are you? I don't have any grandkids,

00:06:35.760 --> 00:06:39.440
but it won't be a waste of your time to come back on Wednesday for more tech news unless you

00:06:39.440 --> 00:06:45.680
consider hearing tech news a waste of time. But in that case, why are you here now? Still, come back though.
