WEBVTT

00:00:00.000 --> 00:00:04.160
The infamous 12-volt high-power connector is no more, and it's being replaced with something

00:00:04.160 --> 00:00:10.560
hopefully less flammable. I'm Jacob, this is TechLinked, and this is justice. As the 16-pin

00:00:10.560 --> 00:00:14.560
connector has been responsible for so many melts, it should be working at a sandwich shop.

00:00:14.560 --> 00:00:19.680
But according to Igor's lab, future GPU owners will not need to fear it. As PCI SAG,

00:00:19.680 --> 00:00:24.880
the organization responsible for specifying the PCIe standard, gave Igor an excerpt of a new

00:00:24.960 --> 00:00:30.240
specification that will replace the 12-volt high-power with a new connector. Called 12-volt

00:00:30.240 --> 00:00:36.000
2x6, the new connector should be compatible with 12-volt high-power headers since the specifications

00:00:36.000 --> 00:00:42.640
don't list any new header changes, and the 12-volt 2x6 connectors will use the same 12-power rails

00:00:42.640 --> 00:00:48.560
and 4-sense pins. One of the major changes is that the 12-volt 2x6 pins are set further back in

00:00:48.560 --> 00:00:53.680
the plug based on the radical idea that electricity should only flow from the cable if it is fully

00:00:53.680 --> 00:00:58.800
inserted into your GPU. Another interesting change is this connector will support cards up to

00:00:58.800 --> 00:01:04.560
675 watts, which is 75 watts higher than the original 16-pin connector, and you know NVIDIA

00:01:04.560 --> 00:01:08.800
is frothing at the bit to make an even larger graphics card to suck up even more power. Brace

00:01:08.800 --> 00:01:14.320
yourselves, the achonkalypse is nigh. Google has been accused of misleading advertisers about

00:01:14.320 --> 00:01:19.280
their TrueView in-stream ads, according to advertising research firm Adalytics. You've

00:01:19.280 --> 00:01:23.280
probably seen TrueView ads at some point, they're the ones you can skip after five seconds,

00:01:23.280 --> 00:01:27.840
and that's important because advertisers are only supposed to be charged for TrueView ads if a

00:01:27.840 --> 00:01:32.640
customer watches 30 seconds of the ad, or the whole ad if it's shorter than that, and the video must

00:01:32.640 --> 00:01:37.760
be playing audio. The ads must also be in-stream, which means that they played before, during,

00:01:37.760 --> 00:01:42.720
or after video content, or whenever your mom needs a life in Candy Crush. I assume that's

00:01:42.720 --> 00:01:48.320
how it works, I haven't played Candy Crush in years. However, Adalytics found that 42-75% of

00:01:48.400 --> 00:01:53.600
TrueView ad spend was allocated to ads that did not meet Google's claims standards.

00:01:53.600 --> 00:01:58.080
Many advertisers Adalytics reached out to were surprised to learn their ads were allegedly

00:01:58.080 --> 00:02:03.280
muted and auto-playing on niche third-party websites or, and I quote, foreign-developed

00:02:03.280 --> 00:02:08.400
Android mobile gaming apps for toddlers. You know, toddlers, famous for their vast

00:02:08.400 --> 00:02:14.160
expendable income and ability to speak good. In a blog post, Google's director of global video

00:02:14.160 --> 00:02:19.920
solutions said the report made extreme and inaccurate claims and that over 90% of ads on

00:02:19.920 --> 00:02:25.280
Google Video Partners are visible to people across the web, which notably doesn't mean anyone saw

00:02:25.280 --> 00:02:30.160
them. And Adalytics actually points out that not once in the blog post was sound mentioned,

00:02:30.160 --> 00:02:36.400
which is a big part of how many people experience ads and also the world. And speaking of Google,

00:02:36.400 --> 00:02:41.040
there's been a strange succession of pixel leaks over the last week and some of them make sense,

00:02:41.040 --> 00:02:47.520
but others just today, pictures of the Pixel 8 Pro were posted to Reddit and like a pair of tight

00:02:47.520 --> 00:02:52.320
jeans, they leave little to the imagination. The photos match older leaked renders showing a flat

00:02:52.320 --> 00:02:58.720
screen, which is nice for people like me who use screen protectors. Why do you make curved screens?

00:02:59.360 --> 00:03:03.760
I hate it. Do you ever, Mark, have you ever used the screen protectors on a curved screen?

00:03:04.400 --> 00:03:09.600
They're terrible. They're awful. They're just these these thin like plastic polymers that like

00:03:09.840 --> 00:03:16.720
they tear and rip. They do nothing. Spray them. That's even worse. Oh, and according to a leaker

00:03:16.720 --> 00:03:25.040
with an aggressively polished name, Kamila Wojcikowska, the, I hope that's right, the 8 and 8 Pro will

00:03:25.040 --> 00:03:30.320
have larger batteries and support charging speeds that are four watts faster than last gen and

00:03:30.320 --> 00:03:35.600
the phones will also support the newer Wi-Fi 7 standard. That's all great, but what I don't

00:03:35.680 --> 00:03:40.320
fully understand is why the Pixel 8 series will support USB DisplayPort alternate mode,

00:03:40.320 --> 00:03:45.280
according to a source inside Google. Google could be taking pointers from the convergence

00:03:45.280 --> 00:03:51.360
idea from a decade ago where phone manufacturers wanted them to become desktop computers. Now,

00:03:51.360 --> 00:03:56.400
it'll be fantastic that they can make this work, but based on my experience with my Pixel this summer,

00:03:56.400 --> 00:04:01.360
I'm expecting a Chromebook that will shut itself off after being in direct sunlight for 10 minutes.

00:04:01.360 --> 00:04:07.920
What are quick bits? They're an icon. They're a moment. There are five shorter stories that follow

00:04:07.920 --> 00:04:13.120
the three main stories of every episode. There you go. That's for you. Now you know. Google,

00:04:13.120 --> 00:04:18.000
the company I was just talking about earlier, has decided they want to use everyone's data to train

00:04:18.000 --> 00:04:23.840
their AIs and not just on their platforms, any publicly accessible sources to help train Google's

00:04:23.840 --> 00:04:28.400
AI models. I mean, it makes sense. I'm honestly just surprised they put it in writing in their

00:04:28.400 --> 00:04:33.360
privacy policy. Maybe they wanted to finally do something that OpenAI didn't do first.

00:04:33.360 --> 00:04:37.680
Multiple third-party Reddit apps shut down over the weekend due to the API changes taking effect,

00:04:37.680 --> 00:04:42.400
while Relay and Now for Reddit have decided to switch to a subscription model. You have the drama

00:04:42.400 --> 00:04:47.760
still isn't over as the moderators for r slash blind, who are, fun fact, visually impaired,

00:04:47.760 --> 00:04:52.800
alleged that Reddit has made it impossible for them to actually moderate. The more accessible

00:04:52.800 --> 00:04:57.600
red reader app is apparently impossible to log into for them, but admin seems to be ignoring them

00:04:57.600 --> 00:05:01.600
when they ask questions. Hey Reddit, maybe you should observe how much you're blowing it?

00:05:02.400 --> 00:05:06.560
Mark Gurman teased several new Apple monitors in his subscribers only newsletter,

00:05:06.560 --> 00:05:11.680
including one with an onboard iOS chip that can be used as a smart home display when your Mac is

00:05:11.680 --> 00:05:17.600
idle. To give you an idea of what that might look like, picture a computer monitor, now picture a

00:05:17.600 --> 00:05:25.600
smart home display, and now picture a gaping hole in your savings account. There it is. Valve has

00:05:25.600 --> 00:05:30.240
issued a rare statement after they were accused by a developer named Simon Carlis of rejecting

00:05:30.240 --> 00:05:35.360
games with AI-generated assets from Steam. Basically, they said their review process is a

00:05:35.360 --> 00:05:40.080
reflection of current copyright law and policies, which shocked me because I was certain knowing

00:05:40.080 --> 00:05:44.720
the law would require you to be able to count past two. It's a Valve can't count past two joke.

00:05:45.760 --> 00:05:51.040
And Twitter decided to institute limits on how many tweets users can read. After the change,

00:05:51.040 --> 00:05:55.360
journalists were upset to find out that emergency service accounts were not exempt from the

00:05:55.360 --> 00:06:00.640
rate limit restrictions. And Twitter was probably upset to find out they might have been de-dossing

00:06:00.640 --> 00:06:05.360
themselves, at least according to one developer. Shortly after they instituted the rate limits,

00:06:05.360 --> 00:06:11.280
tweet decks stopped working altogether. I mean, man, why can't Elon have like one niceâ¦ wait,

00:06:11.280 --> 00:06:16.960
how many companies does he own? Why can't he have five nice things? And we hope you'll enjoy

00:06:16.960 --> 00:06:22.240
a nice thing of tech news this Wednesday when we drop another episode. It won't be a holiday,

00:06:22.240 --> 00:06:26.640
so we'll have a sidekick, and I won't feel so alone. I mean, Mark's here,

00:06:26.640 --> 00:06:30.880
but he's behind a camera. I'm all alone.
