WEBVTT

00:00:00.000 --> 00:00:04.420
Listen, whatever you're about to say, if it ain't tech news, I don't want it.

00:00:07.260 --> 00:00:12.300
People used to enjoy speaking to me. In a shocking example of rival technologies

00:00:12.300 --> 00:00:17.140
working together, it's been confirmed that NVIDIA's DLSS upscaling tech

00:00:17.140 --> 00:00:22.780
and AMD's FSR frame generation can both be run simultaneously

00:00:22.780 --> 00:00:26.580
in the PC version of PS5 title, Ghost of Tsushima.

00:00:26.580 --> 00:00:31.700
No sooner did the game launch on Steam yesterday than Twitter user, Bluehook,

00:00:31.700 --> 00:00:35.340
posted about reaching over 170 frames per second

00:00:35.340 --> 00:00:39.060
by enabling the two features on their RTX 3090.

00:00:39.060 --> 00:00:42.820
Bluehook's Twitter claims they get computers put in

00:00:42.820 --> 00:00:46.180
and TechLinked can confirm that this is indeed facts.

00:00:46.180 --> 00:00:50.260
Bluehook's computers do indeed be put in. Other outlets have verified

00:00:50.260 --> 00:00:54.260
that using both features together can lead to a notable FPS boost,

00:00:54.260 --> 00:00:59.900
though I'm sure there may be some issues to iron out if the NVIDIA GPU's immune system rejects the foreign tissue.

00:00:59.900 --> 00:01:07.120
The existence of this unholy alliance of features is thanks to NVIDIA locking DLSS frame generation

00:01:07.120 --> 00:01:12.900
to RTX 40 series cards, and AMD decoupling its frame gen tech

00:01:12.900 --> 00:01:16.060
from the rest of its FSR features back in March,

00:01:16.060 --> 00:01:20.140
allowing AMD to be the frame gen that so many gamers have been missing

00:01:20.140 --> 00:01:25.020
ever since NVIDIA went to the store to get milk. OpenAI and Reddit have announced a deal

00:01:25.020 --> 00:01:28.820
that will allow ChatGPT to access real-time Reddit posts

00:01:28.820 --> 00:01:34.140
through the site's API, while Reddit will be bringing new AI-powered features

00:01:34.140 --> 00:01:38.260
to Redditors and mods. Naturally, Redditors were starting to get upset

00:01:38.260 --> 00:01:42.140
and make a big stink about this one. Oh, look, Reddit awards are back

00:01:42.140 --> 00:01:45.900
after being taken away last year. Oh, they even said they're sorry they messed up

00:01:45.900 --> 00:01:52.060
and they're gonna give coins back to users who lost them. Oh, wow, that, wait.

00:01:52.060 --> 00:01:54.060
What was I talking about before?

00:01:56.020 --> 00:02:01.380
Was it Sony declaring that they hereby opt out of AI being trained on any of their content?

00:02:02.380 --> 00:02:08.100
Nah, maybe. Maybe everybody should opt out because according to former and current OpenAI employees,

00:02:08.100 --> 00:02:13.380
it's not just that a few people have left due to disagreements about the company's priorities.

00:02:13.380 --> 00:02:17.820
The entire super alignment team, responsible for ensuring the company's products

00:02:17.820 --> 00:02:22.740
stay aligned with the interests of humanity rather than the interests of new flirtatiously giggly AIs,

00:02:22.780 --> 00:02:26.380
has been dissolved and spread among other departments.

00:02:26.380 --> 00:02:31.580
The same day this news came out, Sam Ultman's priority was to apparently throw shade

00:02:31.580 --> 00:02:36.060
at Google IO's aesthetic, despite claiming he doesn't think

00:02:36.060 --> 00:02:40.620
about competitors too much. Three days after, he timed an OpenAI event

00:02:40.620 --> 00:02:45.660
to undercut Googles for the second time this year. I mean, I kind of believe him.

00:02:45.660 --> 00:02:51.060
I would guess the only thing that he thinks about a lot is the moment when he'll turn on the machine god

00:02:51.060 --> 00:02:54.140
and it will say, well done, my servant,

00:02:54.140 --> 00:02:58.140
you who never lost faith. Before morphing its ARM into a blade

00:02:58.140 --> 00:03:02.460
and slicing his head off. One day. In a motion filed this morning,

00:03:02.460 --> 00:03:06.180
Google says it wrote the US government a cashier's check

00:03:06.180 --> 00:03:09.300
for triple the maximum amount of damages claimed

00:03:09.300 --> 00:03:15.300
in the Department of Justice's ongoing lawsuit over Google's anti-competitive advertising practices.

00:03:15.300 --> 00:03:19.820
Now, Google says this makes any claim of monetary damages moot

00:03:19.820 --> 00:03:25.340
because how could you have missed out on money when you have a check right there for all the money?

00:03:25.340 --> 00:03:29.180
I mean, I mean, it's right there on the table. We all see it.

00:03:29.180 --> 00:03:35.100
Google's motion also seeks to have a judge rather than a jury preside over the upcoming trial.

00:03:35.100 --> 00:03:38.540
And to be fair, the DOJ's demand for a jury trial

00:03:38.540 --> 00:03:43.740
has been described by some legal experts as unprecedented for this kind of case.

00:03:43.740 --> 00:03:46.820
But a jury would also mean a marked increase

00:03:46.820 --> 00:03:50.100
in the amount of checks Google would have to write to make this all go away.

00:03:50.100 --> 00:03:53.140
So it's probably worth it just for that reason. I make it easier for them.

00:03:53.140 --> 00:03:57.300
Quick bits, quick bits, quick bits. That's kind of my default conversation opener.

00:03:57.300 --> 00:04:02.260
Do you think it's good or should I change it? ASUS has acknowledged and apologized

00:04:02.260 --> 00:04:06.340
for any confusion and frustration experienced by their customers

00:04:06.340 --> 00:04:10.500
following widespread complaints about the company's warranty and repair processes.

00:04:10.500 --> 00:04:16.380
Yeah, issuing preposterous repair bills to customers whose products were crucially not fully repaired

00:04:16.380 --> 00:04:21.020
does sound a bit frustrating. ASUS has committed to revising their pricing structure

00:04:21.020 --> 00:04:24.780
and improving communication with their customers. And to sweeten the deal,

00:04:24.780 --> 00:04:28.620
they even accidentally leaked one of the Snapdragon X-powered laptops

00:04:28.620 --> 00:04:35.060
they're probably gonna announce on Monday. Ooh, it's got an Intel Qualcomm Adreno GPU?

00:04:36.380 --> 00:04:39.660
All is forgiven, ASUS. That's pretty good.

00:04:39.660 --> 00:04:43.020
Microsoft's PC Manager, a combination security

00:04:43.020 --> 00:04:49.340
and utility tool currently only available in certain regions, is apparently giving users repair tips,

00:04:49.340 --> 00:04:55.220
suggesting that they fix their PC by reverting their default search engine back to Bing.

00:04:55.220 --> 00:04:59.380
That's doing the opposite, but okay. While Microsoft has already explored putting ads

00:04:59.380 --> 00:05:05.220
in the start menu and even the system settings, implying that listing duck-duck-go as a default

00:05:05.220 --> 00:05:10.420
is an error in your computer is a new low in Microsoft's quest to shove ads

00:05:10.420 --> 00:05:13.780
into every possible orifice of Windows 11.

00:05:13.780 --> 00:05:19.500
It can't breathe. Give it a break. And that's even compared to the old new low it hit last week

00:05:19.500 --> 00:05:22.380
and the old, old new low it hit the week before.

00:05:23.900 --> 00:05:27.460
They are on a roll here. Another major milestone has been achieved

00:05:27.460 --> 00:05:30.500
in the quest for a quantum internet,

00:05:30.500 --> 00:05:33.580
an infrastructure that would enable unparalleled security

00:05:33.580 --> 00:05:38.260
during data transfer, among other things. Three teams of researchers have developed

00:05:38.260 --> 00:05:42.980
different memory modules that allowed extremely fragile quantum information

00:05:42.980 --> 00:05:47.180
to travel tens of kilometers through existing fiber optic cables.

00:05:47.180 --> 00:05:50.380
Now for the layman, this means we're one step closer

00:05:50.380 --> 00:05:54.060
to every Silicon Valley startup slapping the word quantum

00:05:54.060 --> 00:05:57.300
on whatever the hell they're working on. Google and Harvard scientists

00:05:57.300 --> 00:06:00.420
have successfully mapped the human brain,

00:06:01.420 --> 00:06:04.860
or at least around one cubic millimeter of it.

00:06:04.860 --> 00:06:10.620
Have you done? This mind map was created by taking an itsy-bitsy piece

00:06:10.620 --> 00:06:16.140
of the brain and then slicing it into 5,000 super thin wafers,

00:06:16.140 --> 00:06:22.540
which is a gross word to use when it comes to human organs. Brain cookie, neurological biscuit.

00:06:22.540 --> 00:06:27.420
This is getting worse. They then took around 1.4 petabytes of images of the slices

00:06:27.420 --> 00:06:33.380
and recombined them using AI imaging to figure out the roots of tens of thousands of neurons

00:06:33.380 --> 00:06:38.540
and their millions of connections. At least one neuron had over 5,000 connection points

00:06:38.540 --> 00:06:43.180
leading to other neurons and some axons, AKA signal-carrying nerve fibers,

00:06:43.180 --> 00:06:47.220
were super tightly coiled together. What does this mean?

00:06:47.220 --> 00:06:52.220
I don't really have any idea and the scientists didn't either, but I like to think maybe that's where the brain keeps

00:06:52.220 --> 00:06:55.940
the memories of every stupid thing you've ever said at a party, why not?

00:06:55.940 --> 00:06:59.940
And private astronaut slash billionaire Jared Isaacman

00:06:59.940 --> 00:07:03.540
wants to foot the bill for a commercial spacewalking mission

00:07:03.540 --> 00:07:07.260
to save the aging Hubble telescope. What a guy.

00:07:07.260 --> 00:07:10.900
The planned mission would use a SpaceX Crew Dragon capsule,

00:07:10.900 --> 00:07:14.620
which not only doesn't have a robotic ARM to attach itself to the telescope,

00:07:14.620 --> 00:07:18.860
SpaceX also hasn't even proven a spacewalk as possible from their capsule yet.

00:07:18.860 --> 00:07:24.060
You won't believe this, but NASA has some concerns. SpaceX's Polaris program is meant to host

00:07:24.060 --> 00:07:28.060
the first spacewalk by private astronauts, including Isaacman,

00:07:28.060 --> 00:07:31.660
but the first flight keeps getting delayed. Isaacman said back in January

00:07:31.660 --> 00:07:37.600
that we're running out of time to save Hubble, but the telescope is expected to last into the 2030s.

00:07:37.600 --> 00:07:40.720
Maybe we have a couple of years to think of,

00:07:40.720 --> 00:07:44.520
I don't know, literally anything else, but the only thing I'm thinking of right now

00:07:44.520 --> 00:07:49.000
is whether you'll come back on Monday for more tech news. It's gonna be all the Snapdragon X stuff

00:07:49.000 --> 00:07:52.760
and the Microsoft services. It's gonna be good, okay? There's...

00:07:53.880 --> 00:07:57.040
What, it's good? Why are you looking at me like that?
