WEBVTT

00:00:00.080 --> 00:00:07.520
It's tech news time right now, but after we film this, I'm gonna go listen to SCA

00:00:04.799 --> 00:00:13.040
on my Zoom and plan the release of my NFT collection. It calms me. Google has

00:00:10.719 --> 00:00:18.560
found a way to force Apple's AirDrop feature to work with Android's similar

00:00:15.599 --> 00:00:22.640
quick share feature. It only works on the Pixel 10 lineup for now, but

00:00:20.640 --> 00:00:27.680
complaining about that would be a bit like complaining about the distance a

00:00:24.720 --> 00:00:33.280
pig flew. To trigger this dark magic, iPhone users can set AirDrop to allow

00:00:30.240 --> 00:00:35.200
files from everyone for 10 minutes and

00:00:33.280 --> 00:00:40.239
boom, they'll be able to receive files from the enemy. Even better, this ritual

00:00:38.000 --> 00:00:45.200
goes both ways. So, you can drop stuff from iOS onto your Android, too. What's

00:00:43.200 --> 00:00:50.320
even crazier, though, is that Google went rogue and did this on its own.

00:00:47.760 --> 00:00:54.160
essentially forcing Apple to communicate like an introvert being pulled out of

00:00:52.480 --> 00:00:57.840
the laundry room at a party by their friend who's annoyingly social, but also

00:00:56.160 --> 00:01:01.120
maybe they have a crush on, so they go with them. >> I've seen that movie.

00:00:59.600 --> 00:01:05.920
>> And don't worry, Google wants you to know this new feature is secure, too.

00:01:03.840 --> 00:01:10.000
Releasing a security blog post all about it, stating that they built the feature

00:01:07.920 --> 00:01:15.920
in the Rust programming language to avoid common security bugs and promising

00:01:12.320 --> 00:01:17.840
they'll support contacts mode on iOS at

00:01:15.920 --> 00:01:21.280
some future point. For now though, if iPhone users want to get a drop from

00:01:19.600 --> 00:01:25.119
their Android buddy, they're going to have to risk also getting the local

00:01:23.119 --> 00:01:29.920
aspiring rappers mixtape. >> Riley, I'm I'm like a young Eminem.

00:01:27.600 --> 00:01:34.640
>> It's like following you around. They're going to open up airrop any any time

00:01:31.600 --> 00:01:37.439
now. Qualcomm's acquisition of Arduino

00:01:34.640 --> 00:01:41.280
has the entire maker community on alert after updates to their terms,

00:01:39.119 --> 00:01:46.240
conditions, and privacy policy signaled a potential shift away from the

00:01:43.680 --> 00:01:51.920
company's open-source roots. These new changes include restricting the reverse

00:01:48.799 --> 00:01:53.920
engineering of their platform, expanding

00:01:51.920 --> 00:01:58.560
data collection rights under Qualcomm ownership, and introducing vague

00:01:55.920 --> 00:02:03.520
language about the ownership of user generated content. Now, many fear this

00:02:00.960 --> 00:02:07.600
could let Qualcomm claim broader control on existing or future projects, with

00:02:05.840 --> 00:02:12.640
sections of the agreement potentially giving Qualcomm blanket authority over

00:02:10.160 --> 00:02:18.959
the patentability of anything built using Arduino tools. Even if the AGPL

00:02:16.959 --> 00:02:22.959
licensed dev environment and firmware technically remain open source, the

00:02:21.120 --> 00:02:27.120
wording is open-ended enough that people worry Qualcomm is laying the groundwork

00:02:24.800 --> 00:02:30.800
for future lockdowns. Open source hardware company Adafruit publicly

00:02:29.120 --> 00:02:35.519
criticized the move, pointing out that imposing enterprise style software as a

00:02:33.440 --> 00:02:40.080
service rules on a community-run platform is a surefire way to destroy

00:02:37.920 --> 00:02:44.560
trust. Before buying Arduino, did Qualcomm actually know what open-source

00:02:42.480 --> 00:02:51.840
means? Tell you what, I'll open source my feelings right now. Boo.

00:02:49.040 --> 00:02:55.360
Bad. Dell and HP have discovered a new way to make some of their business

00:02:53.200 --> 00:02:59.280
laptops worse. And no, it's not another round of questionable product names.

00:02:57.519 --> 00:03:03.840
Small victories. Apparently, these companies decided to start disabling

00:03:01.200 --> 00:03:08.080
HEVC hardware decoding on several laptops, even though the feature is

00:03:06.080 --> 00:03:11.760
supported by their CPUs at a hardware level. These cuts are leaving affected

00:03:09.920 --> 00:03:16.560
users wondering why they were suddenly faced with web video showing continuous

00:03:13.840 --> 00:03:21.599
loading loops and random errors. Well, as indicated in spec documents for

00:03:18.319 --> 00:03:24.800
models like the HP ProBook 460G11,

00:03:21.599 --> 00:03:26.879
hardware HEVC support is turned off by

00:03:24.800 --> 00:03:32.080
design. And as for Dell, there's a clue buried on a support page that only shows

00:03:29.200 --> 00:03:36.640
devices with optional upgrades like a 4K screen or a discrete GPU having access

00:03:34.640 --> 00:03:40.879
to the decoder. Those ones are special. Neither company has offered up a real

00:03:38.480 --> 00:03:47.920
explanation, but what we do know is that HEVC license fees are going up from 20

00:03:43.760 --> 00:03:50.080
cents to 24 cents per laptop. So, to be

00:03:47.920 --> 00:03:54.480
fair, it probably ends up being a good chunk of change, but have a hard time

00:03:52.000 --> 00:03:57.920
believing it's making either HP or Dell gasp for air. Careful, there partner,

00:03:56.480 --> 00:04:02.319
don't want you having to pay a whole dollar to Microsoft to turn the feature

00:03:59.920 --> 00:04:06.159
back on. And that wasn't a joke. That's the official recommendation. How does

00:04:04.319 --> 00:04:10.480
Microsoft end up getting a free dollar out of this nonsense? We got to at least

00:04:08.159 --> 00:04:15.280
do a sponsor segue for our dollars. UPDF, your all-in-one PDF editor and AI

00:04:13.760 --> 00:04:18.959
assistant built to make reading, editing, and managing documents

00:04:16.880 --> 00:04:23.440
effortless. And you know that can be a pain in the butt. With UPDF, you can

00:04:20.959 --> 00:04:26.960
edit PDFs like a pro by highlighting, annotating, commenting, merging,

00:04:25.120 --> 00:04:31.520
splitting, and just generally organizing your files. Is that okay? On top of

00:04:29.360 --> 00:04:36.320
that, you can turn scanned PDFs into editable text. Convert PDFs to Word,

00:04:34.000 --> 00:04:40.960
PowerPoint, Excel or image files and compress large files to share and work

00:04:38.720 --> 00:04:46.560
seamlessly on Windows, Mac, iOS, Android or online. It's so easy to use. You PDF

00:04:44.479 --> 00:04:51.759
who PDF they anybody PDF and now it's even

00:04:49.680 --> 00:04:55.919
easier to use because with AI features, you can translate your PDFs, compare

00:04:53.680 --> 00:05:00.960
them side by side, summarize them, or find credible sources for your work.

00:04:58.320 --> 00:05:04.960
Damn, this thing does a lot. So my friend, it looks like you are about to

00:05:02.880 --> 00:05:10.080
be the you in UPDF. And this Black Friday, get every UPDF feature on every

00:05:07.680 --> 00:05:14.880
device for one sixth the cost of Adobe. Upgrade your workflow. Upgrade your

00:05:11.840 --> 00:05:17.039
life. Download UPDF now. Some people

00:05:14.880 --> 00:05:22.560
have called the Quickbits a flop and a fad. But they're still talking about the

00:05:18.880 --> 00:05:25.039
Quickbits, aren't they? So Microsoft is

00:05:22.560 --> 00:05:30.080
rolling out a preview of its Xbox full screen experience to any Windows 11 PC,

00:05:28.160 --> 00:05:34.240
not just handhelds. although you'll have to download the Windows Insider build to

00:05:32.000 --> 00:05:38.320
get it. Now, this gives desktop, laptop, and tablet users the ability to boot

00:05:36.400 --> 00:05:43.440
into the same controller friendly console-like interface as the ROG Xbox

00:05:40.880 --> 00:05:47.520
Ally and Ally X, skipping loading the desktop, potentially boosting

00:05:45.039 --> 00:05:53.199
performance, and totally redeeming the Xbox marketing team. I guess everything

00:05:50.720 --> 00:05:56.479
really is an Xbox except me. Unless my parents lied to me.

00:05:55.680 --> 00:06:01.360
>> Who told him? >> He can't discover he's an Xbox. We're a

00:05:59.039 --> 00:06:06.240
PlayStation family, damn it. A new Android Trojan called Sternis is

00:06:03.759 --> 00:06:11.199
reportedly stealing WhatsApp, Telegram, and Signal messages by abusing Android's

00:06:09.039 --> 00:06:16.479
accessibility service to read messages after they're decrypted on screen,

00:06:13.840 --> 00:06:21.440
meaning it completely sidesteps the task of having to break encryption first. It

00:06:18.880 --> 00:06:26.000
can also generate fake banking loginins, enable full remote control of a device,

00:06:23.520 --> 00:06:31.280
and log every tap to harvest credentials. It can do it all. The worst

00:06:28.479 --> 00:06:35.759
part, Sternis is only in early testing among hackers. So once it fully rolls

00:06:33.520 --> 00:06:38.759
out, it's going to cause even more consternation.

00:06:39.280 --> 00:06:46.240
Meta is saying Dios Mio after a Spanish

00:06:42.880 --> 00:06:49.360
court said hola and ordered them to pay

00:06:46.240 --> 00:06:51.759
479 million euros to 87 Spanish news

00:06:49.360 --> 00:06:56.639
outlets. Boravore. The court ruled that Meta broke EU data protection and

00:06:54.000 --> 00:07:01.199
antitrust laws by unfairly using the personal data of its users to make

00:06:58.639 --> 00:07:05.440
targeted ads, giving it a serious edge over local media. Meta has slightly

00:07:03.840 --> 00:07:10.240
improved its rules around data collection consent, but the judge

00:07:07.120 --> 00:07:12.720
estimated Meta made over 5 billion euros

00:07:10.240 --> 00:07:18.080
from ads during the 5 years before the change. Of course, Meta is saying no

00:07:15.360 --> 00:07:22.080
manes and planning to appeal the ruling, but similar claims being investigated in

00:07:20.080 --> 00:07:27.680
France might soon have them shouting, "Sacray blue."

00:07:25.599 --> 00:07:33.520
Silicon Valley investors are reportedly funding a human embryo gene editing

00:07:30.479 --> 00:07:36.080
startup led by UC Berkeley biochemist

00:07:33.520 --> 00:07:40.960
Lucas Harrington raising about 30 million USD from backers including

00:07:38.479 --> 00:07:47.199
software engineer and husband of Sam Olman Oliver Molharin and Coinbase CEO

00:07:44.479 --> 00:07:52.000
Brian Armstrong. The company says it's focused strictly on lab research and

00:07:50.000 --> 00:07:57.360
definitely 100% will not test their findings if safety is found wanting

00:07:54.800 --> 00:08:01.360
because uh fun fact, geneediting human embryos is illegal in most countries.

00:07:59.759 --> 00:08:06.080
Don't they remember what happened to the guy in China who geneedited three

00:08:03.280 --> 00:08:09.919
embryos and then seemingly got edited out of existence himself? Those kids

00:08:08.319 --> 00:08:13.360
were actually born. >> They don't have a father anymore

00:08:11.759 --> 00:08:19.520
>> anymore. I don't think I don't think they were his kids. Never mind.

00:08:17.120 --> 00:08:24.879
>> And XAI's Grock chatbot has been sickantingly pumping his daddy Elon's

00:08:22.479 --> 00:08:30.080
tires in a bunch of now deleted interactions. The chatbot said Musk is

00:08:27.280 --> 00:08:34.560
more fit than LeBron James and disrupts comedy more than Jerry Seinfeld, but

00:08:32.479 --> 00:08:38.320
doesn't go quite as far as to say that Musk would rise from the grave faster

00:08:36.240 --> 00:08:43.120
than Jesus Christ. That would be a bridge too far. Grock appears to really

00:08:40.560 --> 00:08:47.120
respect baseball player Shohei Otani, though, who it admits Musk could not

00:08:45.519 --> 00:08:51.279
strike out. Now, if you thought all of this was just Musk ego tripping, the

00:08:49.279 --> 00:08:55.920
soon-to-be trillionaire tweeted that this latest Grock crash out was once

00:08:53.680 --> 00:09:00.320
again caused by someone else manipulating the chatbot, absolutely

00:08:58.240 --> 00:09:05.680
proving it wasn't him this time by disparaging himself with what Lionus

00:09:02.480 --> 00:09:07.360
would call the hard R word. I dropped my

00:09:05.680 --> 00:09:10.959
fair share of hard Rs back then because we didn't even the term hard and it'll

00:09:09.120 --> 00:09:15.040
be rude if you don't come back on Monday for more tech news. Hey, did you know

00:09:12.560 --> 00:09:20.200
that Microsoft's Zoom wireless sharing feature was widely known as squirting?

00:09:22.240 --> 00:09:27.920
>> Is that real though? >> Google it. Google it.

00:09:26.240 --> 00:09:31.680
>> Well, those NFTts aren't going to sell themselves. See you later.
