WEBVTT - Tech News: Elections and Tech Clash

0:00:04.480 --> 0:00:12.319
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.320 --> 0:00:15.760
<v Speaker 1>and welcome to tech Stuff. I'm your host, John van Strickland.

0:00:15.760 --> 0:00:18.840
<v Speaker 1>I'm an executive producer with iHeartRadio. And how the tech

0:00:18.920 --> 0:00:21.159
<v Speaker 1>are you. It is time for the tech news for

0:00:21.200 --> 0:00:25.680
<v Speaker 1>the week ending on November one, twenty twenty four. And

0:00:26.079 --> 0:00:30.600
<v Speaker 1>here in the United States, we are rapidly approaching election day,

0:00:30.800 --> 0:00:33.640
<v Speaker 1>which is Tuesday, November fifth. Now, for those of y'all

0:00:33.800 --> 0:00:35.960
<v Speaker 1>eligible to vote in the United States but who have

0:00:36.040 --> 0:00:38.800
<v Speaker 1>not yet done so, I urge you to get out

0:00:38.840 --> 0:00:42.800
<v Speaker 1>there and vote. Do your research, look into candidates and

0:00:42.920 --> 0:00:45.159
<v Speaker 1>the issues in your area so that you can make

0:00:45.200 --> 0:00:48.720
<v Speaker 1>an informed decision, and go deeper than just sites that

0:00:48.760 --> 0:00:53.040
<v Speaker 1>are run by politically aligned outlets. Look for information that's

0:00:53.479 --> 0:00:56.400
<v Speaker 1>as objective as possible. It's very easy to fall into

0:00:56.480 --> 0:01:00.160
<v Speaker 1>a trap of misinformation or bias, and that goes for

0:01:00.240 --> 0:01:04.000
<v Speaker 1>any side. I'm not picking specific sides here, it's true

0:01:04.040 --> 0:01:07.360
<v Speaker 1>across the board, but for goodness sakes, get out and vote.

0:01:07.400 --> 0:01:11.320
<v Speaker 1>It's one of the most important components in maintaining a democracy,

0:01:11.680 --> 0:01:14.720
<v Speaker 1>and the very act of voting is under assault these days.

0:01:14.840 --> 0:01:16.920
<v Speaker 1>And I don't know about you, but I would rather

0:01:17.080 --> 0:01:19.640
<v Speaker 1>continue to have a say, even if it's just a

0:01:19.680 --> 0:01:22.959
<v Speaker 1>tiny say in how the country I live in operates.

0:01:23.319 --> 0:01:24.800
<v Speaker 1>Now that we have that out of the way, let's

0:01:24.800 --> 0:01:27.399
<v Speaker 1>get to a whole bunch of tech stories that relate

0:01:27.480 --> 0:01:30.560
<v Speaker 1>to the election, because there are tons of those this week,

0:01:30.760 --> 0:01:34.319
<v Speaker 1>which is no big surprise. First up, some voters in

0:01:34.360 --> 0:01:39.679
<v Speaker 1>Pennsylvania received a strange text message this past weekend stating

0:01:39.720 --> 0:01:43.160
<v Speaker 1>that they had voted in the November fifth election, even

0:01:43.200 --> 0:01:47.119
<v Speaker 1>though they hadn't done that yet. Now, obviously that could

0:01:47.120 --> 0:01:51.640
<v Speaker 1>stir up some pretty intense confusion and negative emotions. If

0:01:51.680 --> 0:01:54.760
<v Speaker 1>you received a message saying that you had already voted

0:01:55.120 --> 0:01:58.640
<v Speaker 1>and you had not already voted, clearly you would suspect

0:01:59.040 --> 0:02:02.960
<v Speaker 1>hanky and panky going on. Now, in this case, it

0:02:03.040 --> 0:02:06.840
<v Speaker 1>wasn't any sort of hanky panky at the actual polling locations.

0:02:07.000 --> 0:02:10.800
<v Speaker 1>It wasn't like the state department messed up. Instead, it

0:02:10.880 --> 0:02:14.480
<v Speaker 1>was with an organization called All Vote, and All Vote

0:02:14.480 --> 0:02:18.040
<v Speaker 1>had previously gotten into hot water for texting registered voters

0:02:18.040 --> 0:02:21.239
<v Speaker 1>to alert them that they were not actually registered to vote,

0:02:21.480 --> 0:02:25.360
<v Speaker 1>when in fact they were. County officials in different regions

0:02:25.400 --> 0:02:28.760
<v Speaker 1>of Pennsylvania have warned that that particular approach was a

0:02:28.840 --> 0:02:32.320
<v Speaker 1>hoax designed to gather personal information from people that would

0:02:32.360 --> 0:02:36.440
<v Speaker 1>later be exploited against those people. Max Marvin and Kate

0:02:36.520 --> 0:02:41.000
<v Speaker 1>Bernard reported on this issue in the Philadelphia Inquirer in

0:02:41.040 --> 0:02:45.040
<v Speaker 1>a piece titled Pennsylvania residents got phony texts claiming they

0:02:45.040 --> 0:02:49.600
<v Speaker 1>had voted already Ignore them, officials say so. They also

0:02:49.720 --> 0:02:54.800
<v Speaker 1>quoted a contracted spokesperson for All Vote named Charlotte Climber.

0:02:55.440 --> 0:02:58.400
<v Speaker 1>Climber has claimed that this is all just an innocent

0:02:58.720 --> 0:03:03.840
<v Speaker 1>but incredibly dumb and careless mistake made when All Vote

0:03:03.880 --> 0:03:07.280
<v Speaker 1>employees entered some sort of typo into their system. So

0:03:07.400 --> 0:03:12.480
<v Speaker 1>apparently the original idea was that the organization would text

0:03:12.560 --> 0:03:16.120
<v Speaker 1>folks who had voted in the twenty twenty two election

0:03:16.600 --> 0:03:20.240
<v Speaker 1>and direct them to voting resources for the twenty twenty

0:03:20.400 --> 0:03:23.760
<v Speaker 1>four election. Now, why All Vote felt the need to

0:03:23.840 --> 0:03:27.200
<v Speaker 1>inform people that the vote they had cast two years

0:03:27.200 --> 0:03:30.239
<v Speaker 1>ago had in fact been counted is a bit beyond me.

0:03:30.400 --> 0:03:33.480
<v Speaker 1>That ship has sailed Like I guess the message would be,

0:03:33.720 --> 0:03:36.920
<v Speaker 1>you voted in the election, meaning the twenty twenty two election.

0:03:37.240 --> 0:03:40.720
<v Speaker 1>Here are some resources for you. But because it left

0:03:40.800 --> 0:03:43.520
<v Speaker 1>off the twenty twenty two part, it seemed to indicate

0:03:43.560 --> 0:03:46.920
<v Speaker 1>that people had already voted in this election. Now, that

0:03:46.960 --> 0:03:50.040
<v Speaker 1>seems to me like that messaging was unnecessary in the

0:03:50.080 --> 0:03:52.640
<v Speaker 1>first place. And if that messaging had been left out,

0:03:52.680 --> 0:03:55.000
<v Speaker 1>you know, the whole you had voted in the election bit,

0:03:55.240 --> 0:03:57.080
<v Speaker 1>there'd be nothing to talk about with this story. It

0:03:57.080 --> 0:03:59.520
<v Speaker 1>would just be a text message saying, hey, here's some

0:03:59.600 --> 0:04:03.120
<v Speaker 1>resource for you for voting in this election, and then

0:04:03.280 --> 0:04:05.720
<v Speaker 1>there'd be nothing to talk about. Climber has said the

0:04:05.760 --> 0:04:08.960
<v Speaker 1>founders of All Vote are progressives, but declined to give

0:04:09.040 --> 0:04:12.880
<v Speaker 1>more information about them, saying that there's a concern for

0:04:12.960 --> 0:04:16.240
<v Speaker 1>their safety and that people who might be hard right

0:04:16.760 --> 0:04:21.320
<v Speaker 1>leaning voters might do them harm. This is where I

0:04:21.360 --> 0:04:24.479
<v Speaker 1>say that while I consider myself a progressive, so I

0:04:24.480 --> 0:04:28.520
<v Speaker 1>would consider myself aligned with the people who are at

0:04:28.640 --> 0:04:32.719
<v Speaker 1>least alleged to be behind All Vote. I also think

0:04:32.760 --> 0:04:38.240
<v Speaker 1>All Votes operations are not great like they're not done properly.

0:04:39.000 --> 0:04:43.120
<v Speaker 1>They were poorly thought out and executed, and if the

0:04:43.160 --> 0:04:46.120
<v Speaker 1>owners of all Vote are actually sincere, they're likely to

0:04:46.160 --> 0:04:48.839
<v Speaker 1>cause more harm to their cause than to help it

0:04:49.160 --> 0:04:53.240
<v Speaker 1>through these kinds of operations. Unless this was an actual

0:04:53.279 --> 0:04:58.560
<v Speaker 1>attempt to confuse and discourage people in say hard right counties,

0:04:58.600 --> 0:05:01.760
<v Speaker 1>from voting, in which case that's just despicable, Like, I

0:05:01.800 --> 0:05:04.919
<v Speaker 1>don't care what side you're for. At least according to

0:05:05.320 --> 0:05:08.560
<v Speaker 1>this spokesperson, the people who own all vote believe in

0:05:08.600 --> 0:05:11.679
<v Speaker 1>the same things I generally believe in politically, I don't

0:05:11.720 --> 0:05:16.240
<v Speaker 1>believe in discouraging people through deception so that they don't vote.

0:05:16.240 --> 0:05:20.359
<v Speaker 1>I think that's reprehensible. Whether or not that's what was

0:05:20.400 --> 0:05:22.039
<v Speaker 1>going on, I don't know. It could be that this

0:05:22.160 --> 0:05:25.239
<v Speaker 1>really was an innocent mistake and just a poorly thought

0:05:25.240 --> 0:05:28.520
<v Speaker 1>out campaign in the first place. Either way, a great

0:05:28.560 --> 0:05:32.200
<v Speaker 1>way to use technology to discourage the participation of the

0:05:32.240 --> 0:05:36.640
<v Speaker 1>democratic process. Speaking of unintentional tech issues affecting the election,

0:05:36.760 --> 0:05:40.200
<v Speaker 1>less talk about Colorado. So it seems that the Colorado

0:05:40.279 --> 0:05:44.560
<v Speaker 1>Department of State committed a major booboo, or, as Todd

0:05:44.600 --> 0:05:48.040
<v Speaker 1>Feathers of Gizmoto called it, a bit of an uh oh.

0:05:48.279 --> 0:05:51.280
<v Speaker 1>This comes from an article written by Todd Feathers. It's

0:05:51.320 --> 0:05:57.760
<v Speaker 1>titled Colorado agency improperly posted passwords for its election system online. Yeah,

0:05:57.800 --> 0:06:00.960
<v Speaker 1>that's not good. So what actually happened? Well, the Department

0:06:01.000 --> 0:06:05.560
<v Speaker 1>of State had a link to a spreadsheet on its website,

0:06:05.839 --> 0:06:10.440
<v Speaker 1>and the spreadsheet included some hidden tabs, so upon casual glance,

0:06:10.800 --> 0:06:14.839
<v Speaker 1>there's nothing hinky going on. However, you can just choose

0:06:14.839 --> 0:06:18.480
<v Speaker 1>an option to unhide tabs, in which case one of

0:06:18.520 --> 0:06:24.239
<v Speaker 1>those tabs contained passwords for the state's voting machines. Yikes,

0:06:24.360 --> 0:06:27.200
<v Speaker 1>I hear you say. Now, it's bad. There's no sugar

0:06:27.240 --> 0:06:32.680
<v Speaker 1>coating it. That's bad. That's a terrible breach of security etiquette.

0:06:32.720 --> 0:06:37.159
<v Speaker 1>It is, not, however, catastrophic. Why Well, for one thing,

0:06:37.600 --> 0:06:41.520
<v Speaker 1>these voting machines actually require two passwords. It's kind of

0:06:41.520 --> 0:06:43.520
<v Speaker 1>like one of those things you see in movies where

0:06:43.560 --> 0:06:46.400
<v Speaker 1>you have to have two keys to activate the nuclear

0:06:46.560 --> 0:06:48.599
<v Speaker 1>arsenal or whatever, and you have to have two people

0:06:48.640 --> 0:06:51.280
<v Speaker 1>across the room from each other insert and turned the

0:06:51.360 --> 0:06:54.279
<v Speaker 1>keys simultaneously to activate it. Well, in this case, the

0:06:54.440 --> 0:06:58.160
<v Speaker 1>voting machines require two separate passwords, and those passwords are

0:06:58.200 --> 0:07:02.760
<v Speaker 1>not collected together. So while a set of passwords were

0:07:02.760 --> 0:07:06.520
<v Speaker 1>available according to the spreadsheet, the other set was not available.

0:07:06.680 --> 0:07:09.920
<v Speaker 1>So even if you had access the spreadsheet and revealed

0:07:09.920 --> 0:07:12.600
<v Speaker 1>the tabs and you wrote down all the passwords, you

0:07:12.600 --> 0:07:15.560
<v Speaker 1>would still only have one half of the password component.

0:07:15.840 --> 0:07:18.480
<v Speaker 1>But that's not at all like in order to actually

0:07:18.600 --> 0:07:21.440
<v Speaker 1>use these passwords. You would need to have physical access

0:07:21.520 --> 0:07:24.960
<v Speaker 1>to the voting machines themselves. Now, in order to do that,

0:07:25.000 --> 0:07:27.680
<v Speaker 1>you would need credentials to be able to get access

0:07:27.760 --> 0:07:31.000
<v Speaker 1>to the areas where the voting machines are stored. They're

0:07:31.000 --> 0:07:34.800
<v Speaker 1>also under a constant video surveillance, so you'd have to

0:07:34.840 --> 0:07:38.760
<v Speaker 1>deal with that as well. Plus, Colorado uses paper ballots,

0:07:39.120 --> 0:07:43.080
<v Speaker 1>so there's a physical paper trail of every vote cast.

0:07:43.400 --> 0:07:46.760
<v Speaker 1>Voters verify that their ballots are correct before they cast

0:07:46.800 --> 0:07:50.160
<v Speaker 1>their vote, so even if someone did access the machine

0:07:50.160 --> 0:07:54.000
<v Speaker 1>somehow and messed with them, the paper trail would remain

0:07:54.160 --> 0:07:57.840
<v Speaker 1>a resource for verifying the votes that had been cast.

0:07:58.040 --> 0:08:02.040
<v Speaker 1>So while the mistake is a giant whoopsie and absolutely

0:08:02.120 --> 0:08:06.480
<v Speaker 1>should not have happened, the voting process itself is still reliable.

0:08:06.800 --> 0:08:09.520
<v Speaker 1>Of course, that's not stopping some people from using this

0:08:09.720 --> 0:08:13.480
<v Speaker 1>to bring into question the results of any votes that

0:08:13.520 --> 0:08:15.840
<v Speaker 1>are made in the state. In other words, this is

0:08:15.880 --> 0:08:20.360
<v Speaker 1>an opportunity to undermine confidence in the results of the

0:08:20.440 --> 0:08:23.520
<v Speaker 1>election ahead of time, so that no matter who wins,

0:08:23.800 --> 0:08:25.960
<v Speaker 1>you can have some wiggle room in case your side

0:08:26.000 --> 0:08:27.880
<v Speaker 1>didn't win. If your side did win, you say, hey,

0:08:27.880 --> 0:08:29.960
<v Speaker 1>look the system worked, and if your side didn't win.

0:08:30.000 --> 0:08:33.640
<v Speaker 1>You're like, this is because our system was compromised. Now,

0:08:33.679 --> 0:08:36.480
<v Speaker 1>I'm here to remind y'all that for democracy to fail,

0:08:36.679 --> 0:08:39.720
<v Speaker 1>you don't actually have to prove that the system is broken.

0:08:39.920 --> 0:08:42.760
<v Speaker 1>All you have to do is convince enough people that

0:08:42.800 --> 0:08:46.480
<v Speaker 1>the system is broken to reduce their confidence in the system,

0:08:46.679 --> 0:08:51.439
<v Speaker 1>and then democracy dies. That's how that works. Reporter Barbara

0:08:51.640 --> 0:08:55.880
<v Speaker 1>Ortute has a piece in AP News that's titled report

0:08:56.000 --> 0:09:00.319
<v Speaker 1>says crowdsourced fact checks on X failed to a dress

0:09:00.400 --> 0:09:04.760
<v Speaker 1>flood of US election misinformation. Now, I think that comes

0:09:04.800 --> 0:09:08.760
<v Speaker 1>as a surprise to absolutely no one. Before Elon Musk

0:09:08.920 --> 0:09:12.559
<v Speaker 1>carried us SYNC into the HQ of what was then Twitter,

0:09:13.120 --> 0:09:16.280
<v Speaker 1>I maintained that was foreshadowing that he would eventually sink

0:09:16.360 --> 0:09:19.480
<v Speaker 1>the company, which hasn't happened yet. But goodness gracious, I mean,

0:09:19.880 --> 0:09:23.240
<v Speaker 1>I think the band is playing while the Titanic is sinking. Anyway,

0:09:23.400 --> 0:09:27.280
<v Speaker 1>the site had content moderators, and they did stuff like

0:09:27.600 --> 0:09:30.640
<v Speaker 1>act on tweets that were spreading misinformation, like they could

0:09:30.760 --> 0:09:35.239
<v Speaker 1>label tweets as saying this is inaccurate or this is misinformation,

0:09:35.320 --> 0:09:38.280
<v Speaker 1>whatever it may be. Those days, however, are pretty much gone.

0:09:39.040 --> 0:09:42.200
<v Speaker 1>X relies very heavily on the user community to flag

0:09:42.240 --> 0:09:45.120
<v Speaker 1>posts that contain misinformation. You know, these are folks who

0:09:45.160 --> 0:09:47.839
<v Speaker 1>are not necessarily trained to do that, or it might

0:09:47.880 --> 0:09:51.400
<v Speaker 1>include people who are actually interested in spreading misinformation to

0:09:51.440 --> 0:09:54.400
<v Speaker 1>start with. Now, to be clear, this community based tool

0:09:54.559 --> 0:09:58.439
<v Speaker 1>existed before Elon Musk took over Twitter. This is not

0:09:58.520 --> 0:10:02.000
<v Speaker 1>like Twitter did this in instead of content moderation. Now,

0:10:02.040 --> 0:10:05.920
<v Speaker 1>originally this tool was called birdwatch. But while it used

0:10:05.960 --> 0:10:10.240
<v Speaker 1>to be a supplemental way for Twitter to monitor and

0:10:10.960 --> 0:10:16.000
<v Speaker 1>moderate content, it's now taking a more prominent role because

0:10:16.160 --> 0:10:19.680
<v Speaker 1>content moderation is not really a big thing over at

0:10:19.880 --> 0:10:22.240
<v Speaker 1>X these days, there aren't that many people left to

0:10:22.360 --> 0:10:26.240
<v Speaker 1>actually do it. The Center for Countering Digital Hate took

0:10:26.280 --> 0:10:29.199
<v Speaker 1>a look at the community notes tool on X and

0:10:29.320 --> 0:10:33.959
<v Speaker 1>found that seventy four percent of the tweets the posts

0:10:34.040 --> 0:10:40.319
<v Speaker 1>that they sampled had community notes that were inaccurate or inadequate.

0:10:40.679 --> 0:10:43.359
<v Speaker 1>The sample size was two hundred and eighty three posts

0:10:43.480 --> 0:10:46.560
<v Speaker 1>that had community notes attached to them. That means that

0:10:46.600 --> 0:10:49.360
<v Speaker 1>two hundred and nine of those posts were not accurate.

0:10:49.600 --> 0:10:52.559
<v Speaker 1>Now X maintains that the community notes feature is a

0:10:52.640 --> 0:10:55.720
<v Speaker 1>useful tool and has pointed to other academic research, saying

0:10:55.760 --> 0:10:59.400
<v Speaker 1>that it's a trustworthy source of information. So this is

0:10:59.440 --> 0:11:04.200
<v Speaker 1>not to say that definitively the tool is broken or

0:11:04.280 --> 0:11:08.720
<v Speaker 1>not performing as intended, but that this one nonprofit group

0:11:09.160 --> 0:11:12.960
<v Speaker 1>says that that's the case. For more information and a

0:11:13.000 --> 0:11:15.440
<v Speaker 1>more thorough look at all this, I recommend reading an

0:11:15.520 --> 0:11:19.760
<v Speaker 1>article by Ashley Bellinger on Ours Technica. It's titled Toxic

0:11:20.240 --> 0:11:26.840
<v Speaker 1>X users sabotage community notes that could derail disinfo report says. Okay,

0:11:27.160 --> 0:11:30.520
<v Speaker 1>while we're on the subject of Elon Musk, which is

0:11:30.920 --> 0:11:34.600
<v Speaker 1>tangential to X, I suppose in PRS Bobby Allen has

0:11:34.600 --> 0:11:38.160
<v Speaker 1>a piece titled and Elon Musk backed political group is

0:11:38.200 --> 0:11:42.720
<v Speaker 1>posting fake Kamala Harris ads on Facebook. So yeah, we've

0:11:42.760 --> 0:11:46.200
<v Speaker 1>got more misinformation and election news headed your way. My

0:11:46.320 --> 0:11:49.719
<v Speaker 1>apologies that we knew this was going to happen. I mean,

0:11:49.880 --> 0:11:52.199
<v Speaker 1>I've been talking about for months. But in this case,

0:11:52.240 --> 0:11:55.720
<v Speaker 1>Elon Musk has provided significant funds to a group called

0:11:55.920 --> 0:12:00.240
<v Speaker 1>Building America's Future. This group, in turn, has operated a

0:12:00.360 --> 0:12:04.719
<v Speaker 1>Facebook account that is called Progress twenty twenty eight, and

0:12:04.880 --> 0:12:08.880
<v Speaker 1>this account has published campaign ads that look like they're

0:12:08.920 --> 0:12:14.479
<v Speaker 1>from Kamala Harris's campaign, but in fact they are purposefully misleading,

0:12:14.880 --> 0:12:17.800
<v Speaker 1>both to trick the viewer into thinking that the ads

0:12:17.840 --> 0:12:22.560
<v Speaker 1>are actually from Kamala Harris's campaign, and also by misrepresenting

0:12:22.600 --> 0:12:26.760
<v Speaker 1>Harris's position on various topics. Now, according to the First Amendment,

0:12:27.200 --> 0:12:30.120
<v Speaker 1>there's nothing illegal going on here. There's nothing that says

0:12:30.320 --> 0:12:35.199
<v Speaker 1>you have to be truthful when you're advertising with political speech. Now, sure,

0:12:35.440 --> 0:12:37.880
<v Speaker 1>you got to be truthful when it comes to advertising

0:12:37.920 --> 0:12:41.280
<v Speaker 1>products and services. For example, if I were to endorse

0:12:41.360 --> 0:12:44.240
<v Speaker 1>something but it turned out I never actually used whatever

0:12:44.280 --> 0:12:47.120
<v Speaker 1>it was I was endorsing, I could potentially face a

0:12:47.320 --> 0:12:51.079
<v Speaker 1>pretty massive fine for that. Like I could get hit

0:12:51.240 --> 0:12:54.040
<v Speaker 1>hard for doing that, My company could get hit hard

0:12:54.080 --> 0:12:55.960
<v Speaker 1>for doing that. But you know, when it comes to

0:12:56.000 --> 0:13:00.520
<v Speaker 1>informing people about, you know, where politicians stand on specific topics,

0:13:00.679 --> 0:13:04.480
<v Speaker 1>truth just isn't a requirement here in the US. Further,

0:13:05.000 --> 0:13:07.680
<v Speaker 1>using the name Progress twenty twenty eight for the group

0:13:07.840 --> 0:13:11.480
<v Speaker 1>further obvious skates who's actually behind the campaign. So it

0:13:11.480 --> 0:13:14.000
<v Speaker 1>would be easy for someone to believe this is a

0:13:14.040 --> 0:13:17.240
<v Speaker 1>real ad from the Harris side. And it's interesting because

0:13:17.280 --> 0:13:19.559
<v Speaker 1>there are limitations for this kind of thing, I mean,

0:13:19.559 --> 0:13:21.959
<v Speaker 1>the use of deep fakes, you know, where you're making

0:13:22.000 --> 0:13:24.840
<v Speaker 1>it seem like someone is saying or doing something that

0:13:24.880 --> 0:13:27.840
<v Speaker 1>they actually did not do. That could be a violation

0:13:27.960 --> 0:13:31.600
<v Speaker 1>of policies. But an ad that ultimately does a similar

0:13:31.640 --> 0:13:34.440
<v Speaker 1>thing but without the use of deep fakes, that's fine,

0:13:34.720 --> 0:13:37.920
<v Speaker 1>which just makes me curious where the line is. Okay,

0:13:38.200 --> 0:13:43.960
<v Speaker 1>we've got tons more information about technology, including within the elections,

0:13:43.960 --> 0:13:56.280
<v Speaker 1>but also other stuff. But first, let's take a quick break. Okay,

0:13:56.320 --> 0:14:01.560
<v Speaker 1>we're back. Meta held its third quarter earnings call this week,

0:14:01.840 --> 0:14:06.640
<v Speaker 1>and CNBC's Jonathan Vanian has a piece all about the

0:14:06.679 --> 0:14:10.240
<v Speaker 1>Reality Labs part of that call, which was just one part.

0:14:10.480 --> 0:14:12.360
<v Speaker 1>There were there were more things to talk about than

0:14:12.440 --> 0:14:16.000
<v Speaker 1>just Reality Labs. But you might remember that Reality Labs

0:14:16.040 --> 0:14:19.680
<v Speaker 1>focuses on all things mixed reality, so that includes virtual

0:14:19.720 --> 0:14:23.680
<v Speaker 1>reality and augmented reality as well as the metaverse. You know,

0:14:23.920 --> 0:14:30.000
<v Speaker 1>this supposed future of our computational approach, and you know,

0:14:30.200 --> 0:14:32.240
<v Speaker 1>this has really served as a great way for Meta

0:14:32.240 --> 0:14:36.119
<v Speaker 1>to spend tons of money while having to assure investors

0:14:36.120 --> 0:14:38.680
<v Speaker 1>that the metaverse is very much going to happen and

0:14:38.720 --> 0:14:41.320
<v Speaker 1>it will be the future of computing, and that's something

0:14:41.320 --> 0:14:44.760
<v Speaker 1>that stakeholders remain skeptical about. I think for good reason.

0:14:45.040 --> 0:14:48.520
<v Speaker 1>That's my personal opinion. I remain unconvinced that the metaverse

0:14:48.880 --> 0:14:51.800
<v Speaker 1>is going to be a significant thing. I really doubt

0:14:51.840 --> 0:14:55.280
<v Speaker 1>it's going to be the new means of interacting with computing.

0:14:55.440 --> 0:14:57.880
<v Speaker 1>I just don't think that's true, but it could be wrong.

0:14:58.240 --> 0:15:01.400
<v Speaker 1>So anyway, the call revealed that Reality Labs had a

0:15:01.560 --> 0:15:05.440
<v Speaker 1>twenty nine percent increase in revenue, reaching two hundred and

0:15:05.440 --> 0:15:08.680
<v Speaker 1>seventy million dollars this past quarter. That's no small shakes.

0:15:08.680 --> 0:15:10.800
<v Speaker 1>Two hundred seventy million dollars is a lot of money.

0:15:10.880 --> 0:15:13.120
<v Speaker 1>Keep in mind, Reality Labs most of the money they

0:15:13.120 --> 0:15:18.440
<v Speaker 1>make is through product like the Meta VR headsets or

0:15:18.560 --> 0:15:23.320
<v Speaker 1>the augmented Reality ray bands that Meta has co branded

0:15:23.360 --> 0:15:28.240
<v Speaker 1>with ray Ban. Those are the source for revenue in

0:15:28.280 --> 0:15:31.480
<v Speaker 1>the most for the most part, for the Reality Labs division,

0:15:31.680 --> 0:15:33.600
<v Speaker 1>and two hundred and seventy million dollars that's a lot

0:15:33.600 --> 0:15:36.560
<v Speaker 1>of money, but it's not as much as analysts had

0:15:36.600 --> 0:15:39.520
<v Speaker 1>been hoping for. They had estimated that Meta would hit

0:15:39.800 --> 0:15:43.720
<v Speaker 1>around three hundred and ten million dollars in revenue from

0:15:43.720 --> 0:15:47.440
<v Speaker 1>the Reality Labs unit. Further, the division as a whole

0:15:47.720 --> 0:15:51.160
<v Speaker 1>chalked up an overall operating loss. So yeah, it made

0:15:51.160 --> 0:15:54.800
<v Speaker 1>two hundred and seventy million dollars, but it's spent way

0:15:55.880 --> 0:15:59.360
<v Speaker 1>way more than that. How much more? Well, the operating

0:15:59.440 --> 0:16:04.520
<v Speaker 1>loss is at four point four billion with a B dollars,

0:16:04.720 --> 0:16:06.880
<v Speaker 1>So yeah, you make two hundred and seventy million, but

0:16:06.960 --> 0:16:11.120
<v Speaker 1>you spent more than four point four billion. Yikes. Zuckerberg

0:16:11.160 --> 0:16:15.000
<v Speaker 1>continues to insist that vr AR and the metaverse are

0:16:15.080 --> 0:16:18.880
<v Speaker 1>the future, and he might be correct. Right, just because

0:16:18.920 --> 0:16:23.160
<v Speaker 1>it doesn't appeal to me and doesn't really seem to

0:16:23.840 --> 0:16:26.760
<v Speaker 1>fit with my concept of what computing really is all about,

0:16:26.920 --> 0:16:29.560
<v Speaker 1>that doesn't mean anything at all. I'm just one person,

0:16:30.040 --> 0:16:32.680
<v Speaker 1>but I've yet to see a demonstration of this technology

0:16:32.680 --> 0:16:36.480
<v Speaker 1>that convinces me that the pros actually outweigh the cons.

0:16:36.840 --> 0:16:39.680
<v Speaker 1>I mean, you know, feeling immersed is amazing, don't get

0:16:39.720 --> 0:16:43.040
<v Speaker 1>me wrong. Like, if you can experience a really immersive

0:16:43.360 --> 0:16:47.440
<v Speaker 1>presentation of some sort, that can be really fun and entertaining.

0:16:47.480 --> 0:16:50.040
<v Speaker 1>But wearing a headset for more than, you know, like

0:16:50.360 --> 0:16:53.000
<v Speaker 1>half an hour is a pretty hard sell for me,

0:16:53.240 --> 0:16:55.000
<v Speaker 1>as well as for a lot of other people. And

0:16:55.280 --> 0:16:59.240
<v Speaker 1>you know, people who like me are prone to motion sickness.

0:16:59.400 --> 0:17:02.480
<v Speaker 1>If the is not done really, really well, it's a

0:17:02.520 --> 0:17:05.800
<v Speaker 1>super hard sell. It doesn't matter how good the experience

0:17:05.920 --> 0:17:10.199
<v Speaker 1>is right, like, sometimes our tolerance is pretty low, and

0:17:10.280 --> 0:17:13.880
<v Speaker 1>I cannot imagine using this kind of technology to do

0:17:14.240 --> 0:17:20.040
<v Speaker 1>work right. Maybe leisure activities, but work is hard to

0:17:20.160 --> 0:17:23.800
<v Speaker 1>imagine in this particular context. Now, it could very well

0:17:23.840 --> 0:17:26.560
<v Speaker 1>be I'm just suffering under the problems of a very

0:17:26.600 --> 0:17:30.240
<v Speaker 1>limited imagination and that this really is the future. I

0:17:30.400 --> 0:17:34.560
<v Speaker 1>just remain very skeptical. Jason Kebler of four oh four

0:17:34.720 --> 0:17:37.919
<v Speaker 1>Media has a piece that's got a great headline. The

0:17:37.960 --> 0:17:44.440
<v Speaker 1>headline is Zuckerberg, the AI slop will continue until morale improves.

0:17:44.880 --> 0:17:47.440
<v Speaker 1>That's a great play on a popular joke that's typically

0:17:47.480 --> 0:17:52.120
<v Speaker 1>about flogging anyway. As you might suspect, Kebler is not

0:17:52.160 --> 0:17:57.480
<v Speaker 1>a huge fan of AI generated content flooding various social platforms,

0:17:57.680 --> 0:18:01.720
<v Speaker 1>but he quotes Zuckerberg who said during that earnings call quote,

0:18:01.920 --> 0:18:05.200
<v Speaker 1>I think we're going to add a whole new category

0:18:05.240 --> 0:18:09.800
<v Speaker 1>of content, which is AI generated or AI summarized content,

0:18:10.119 --> 0:18:13.680
<v Speaker 1>or kind of existing content pulled together by AI in

0:18:13.800 --> 0:18:17.119
<v Speaker 1>some way. And I think that's going to be just

0:18:17.400 --> 0:18:20.679
<v Speaker 1>very exciting for Facebook and Instagram and maybe threads or

0:18:20.880 --> 0:18:25.080
<v Speaker 1>other kind of feed experiences over time. End quote. So

0:18:25.119 --> 0:18:28.320
<v Speaker 1>that's all direct quote, including like the verbal stumbling now

0:18:28.320 --> 0:18:31.639
<v Speaker 1>in full disclosure, I actually don't mind using AI to

0:18:31.720 --> 0:18:35.119
<v Speaker 1>summarize something that I have already read in order to

0:18:35.160 --> 0:18:37.879
<v Speaker 1>like refresh my memory of the most important points, you know,

0:18:38.000 --> 0:18:40.240
<v Speaker 1>kind of like using it like a note taking app.

0:18:40.320 --> 0:18:42.760
<v Speaker 1>I don't mind doing that, but I do think it's

0:18:42.800 --> 0:18:46.239
<v Speaker 1>still vital to actually read the content first and not

0:18:46.400 --> 0:18:49.960
<v Speaker 1>just rely on an AI generated summary, because sometimes those

0:18:50.000 --> 0:18:53.960
<v Speaker 1>are not accurate or they misidentify what the most important

0:18:53.960 --> 0:18:57.520
<v Speaker 1>points are. I have less than zero interest in having

0:18:57.600 --> 0:19:02.880
<v Speaker 1>AI generated content populate my social media feeds as it stands.

0:19:03.000 --> 0:19:07.080
<v Speaker 1>I hate that a recommendation algorithm decides which posts I

0:19:07.200 --> 0:19:10.080
<v Speaker 1>see and when I see them, because I often miss

0:19:10.119 --> 0:19:13.600
<v Speaker 1>out on important, timely stuff because Meta thinks that I

0:19:13.600 --> 0:19:17.000
<v Speaker 1>should see that Facebook post later on, maybe sometimes weeks

0:19:17.119 --> 0:19:20.280
<v Speaker 1>later after it's been posted. Like I posted a picture

0:19:20.600 --> 0:19:24.680
<v Speaker 1>of me having voted. I believe that was on October

0:19:24.760 --> 0:19:28.320
<v Speaker 1>seventeenth or so. So anyway, it was not long after Georgia,

0:19:28.440 --> 0:19:31.040
<v Speaker 1>my area of Georgia had started doing early voting, and

0:19:31.320 --> 0:19:34.199
<v Speaker 1>I was still getting people just seeing that picture for

0:19:34.240 --> 0:19:38.520
<v Speaker 1>the first time and liking it this week, more than

0:19:38.560 --> 0:19:42.919
<v Speaker 1>a week after I had done it. So that tells

0:19:42.960 --> 0:19:46.200
<v Speaker 1>me that the recommendation algorithm is not serving this up

0:19:46.200 --> 0:19:49.240
<v Speaker 1>in a timely manner. So I don't want the stuff

0:19:49.240 --> 0:19:52.720
<v Speaker 1>that my friends post to be buried even further under

0:19:52.840 --> 0:19:57.280
<v Speaker 1>AI generated crap. You know, I'm tired of not being

0:19:57.320 --> 0:19:59.439
<v Speaker 1>able to see the things that my friends post. I mean,

0:19:59.440 --> 0:20:02.080
<v Speaker 1>there are times where someone appears to disappear from my

0:20:02.119 --> 0:20:05.160
<v Speaker 1>life entirely. But it's not that they're gone and they're

0:20:05.200 --> 0:20:08.280
<v Speaker 1>not posting or anything. It's that Meta has just decided

0:20:08.760 --> 0:20:11.560
<v Speaker 1>that I don't need to see their updates unless I

0:20:11.600 --> 0:20:13.600
<v Speaker 1>actually go to their page, and even then I'm not

0:20:13.640 --> 0:20:16.600
<v Speaker 1>necessarily going to see it in chronological order. And to

0:20:16.640 --> 0:20:20.880
<v Speaker 1>think that even this limited engagement could be limited even

0:20:21.000 --> 0:20:26.359
<v Speaker 1>more with AI generated junk is really upsetting. So is

0:20:26.400 --> 0:20:30.680
<v Speaker 1>Meta just trying to sever relationships between real life friends. No,

0:20:31.240 --> 0:20:33.159
<v Speaker 1>I don't think that's true. I don't think that's what

0:20:33.240 --> 0:20:36.040
<v Speaker 1>Meta's goal is. What the company is actually trying to do,

0:20:36.160 --> 0:20:38.960
<v Speaker 1>is what it's been doing for years, is trying to

0:20:39.040 --> 0:20:42.120
<v Speaker 1>keep you on its various platforms for as long as

0:20:42.119 --> 0:20:45.359
<v Speaker 1>possible in order to serve you more ads and to

0:20:45.440 --> 0:20:48.240
<v Speaker 1>make more money. And if your friends just aren't enough

0:20:48.480 --> 0:20:52.720
<v Speaker 1>to keep you glued to Facebook or you know whatever, Well,

0:20:52.880 --> 0:20:55.720
<v Speaker 1>by golly, we'll just have the bot's slave away and

0:20:55.760 --> 0:20:58.800
<v Speaker 1>the content minds to create stuff that does keep you there,

0:20:59.080 --> 0:21:02.680
<v Speaker 1>which is pretty gross. Oh and while Meta is looking

0:21:02.720 --> 0:21:06.240
<v Speaker 1>at a more than four billion dollar operating loss on

0:21:06.280 --> 0:21:09.320
<v Speaker 1>the reality Labs division, it's also looking to spend even

0:21:09.359 --> 0:21:13.159
<v Speaker 1>more money, largely on the AI side of things. So

0:21:13.440 --> 0:21:17.160
<v Speaker 1>according to CNBC, Meta plans to raise the low end

0:21:17.160 --> 0:21:21.520
<v Speaker 1>of its capital expenditures guidance for twenty twenty four up

0:21:21.600 --> 0:21:24.640
<v Speaker 1>to thirty eight billion dollars, So that's up a full

0:21:24.760 --> 0:21:27.720
<v Speaker 1>billion dollars from what it was before. Earlier, the low

0:21:27.840 --> 0:21:30.280
<v Speaker 1>end for expenditures for this year was going to be

0:21:30.320 --> 0:21:34.080
<v Speaker 1>thirty seven billion. Now the top end is forty billion,

0:21:34.119 --> 0:21:37.479
<v Speaker 1>which remains unchanged from earlier in the year. So really

0:21:37.640 --> 0:21:40.480
<v Speaker 1>the margin has just decreased, right, It's going to be

0:21:40.520 --> 0:21:43.120
<v Speaker 1>somewhere between thirty eight and forty billion dollars, but it's

0:21:43.119 --> 0:21:46.800
<v Speaker 1>definitely not thirty seven that's too little. Zuckerberg says next

0:21:46.880 --> 0:21:49.080
<v Speaker 1>year will be even more dramatic, which kind of is

0:21:49.119 --> 0:21:50.760
<v Speaker 1>in line with what he's been saying for the last

0:21:50.800 --> 0:21:54.000
<v Speaker 1>couple of years. And as I have said repeatedly on

0:21:54.160 --> 0:21:58.280
<v Speaker 1>tech stuff, AI is expensive and running AI operations in

0:21:58.320 --> 0:22:00.920
<v Speaker 1>the cloud costs a whole whole lot of money. You

0:22:01.320 --> 0:22:04.760
<v Speaker 1>need a lot of data centers, you need specialized processors.

0:22:05.240 --> 0:22:09.360
<v Speaker 1>This racks up the cost of operation very quickly. It's

0:22:09.359 --> 0:22:12.080
<v Speaker 1>one of the reasons that I actually favor having AI

0:22:12.240 --> 0:22:16.160
<v Speaker 1>processing capabilities built into chips that are in consumer devices

0:22:16.520 --> 0:22:19.919
<v Speaker 1>and moving at least some or hopefully all of that

0:22:20.240 --> 0:22:24.160
<v Speaker 1>AI processing to the end device, because one that speeds

0:22:24.200 --> 0:22:28.800
<v Speaker 1>things up considerably because it's just handling your calculations, not

0:22:28.960 --> 0:22:33.880
<v Speaker 1>everybody's two. It vastly improves security and privacy because you're

0:22:33.920 --> 0:22:38.760
<v Speaker 1>not constantly beaming your information to some server farms somewhere.

0:22:38.960 --> 0:22:42.080
<v Speaker 1>As you engage with an AI application, it's not being

0:22:42.200 --> 0:22:44.679
<v Speaker 1>held in some server farm. It's not being used to

0:22:44.960 --> 0:22:48.840
<v Speaker 1>train the next generation of large language models. It's just

0:22:48.960 --> 0:22:52.199
<v Speaker 1>you interacting with your device. So I much prefer that

0:22:52.359 --> 0:22:57.080
<v Speaker 1>approach to AI interactions than the cloud based ones. But

0:22:57.280 --> 0:23:00.600
<v Speaker 1>that's really a topic for another time now. Like reality labs,

0:23:00.640 --> 0:23:04.680
<v Speaker 1>the AI costs are something Zuckerberg doesn't really shy away from.

0:23:04.760 --> 0:23:07.960
<v Speaker 1>He just wades right into it. He says it's a

0:23:08.080 --> 0:23:12.560
<v Speaker 1>necessary cost in order to establish the infrastructure for future platforms,

0:23:12.840 --> 0:23:15.879
<v Speaker 1>and again he might be right, like, maybe this is

0:23:15.920 --> 0:23:19.000
<v Speaker 1>the future and he's just getting the work done early,

0:23:19.040 --> 0:23:21.760
<v Speaker 1>and it's very painful because it's very expensive and it's

0:23:21.760 --> 0:23:24.080
<v Speaker 1>not paying off right away, but that in the long

0:23:24.160 --> 0:23:28.320
<v Speaker 1>run it sets the groundwork that allows Meta to prosper.

0:23:28.640 --> 0:23:31.120
<v Speaker 1>But in the meantime, the market has been a little critical.

0:23:31.640 --> 0:23:35.760
<v Speaker 1>Shortly after the earnings call, in after market trading, the

0:23:35.880 --> 0:23:38.320
<v Speaker 1>stock price for Meta took a bit of a dip.

0:23:38.840 --> 0:23:42.280
<v Speaker 1>So it seems to me that investors are getting a

0:23:42.400 --> 0:23:46.960
<v Speaker 1>little anxious and tired of these reports about the company

0:23:47.040 --> 0:23:51.040
<v Speaker 1>spending so much money on reality labs and AI when

0:23:51.760 --> 0:23:57.080
<v Speaker 1>the payoff for those investments is pretty far down the road. Personally,

0:23:57.560 --> 0:24:01.600
<v Speaker 1>I think in general that preparing for the long term

0:24:01.760 --> 0:24:05.040
<v Speaker 1>is a better approach than just focusing on the short term. So,

0:24:05.680 --> 0:24:07.760
<v Speaker 1>you know, I feel conflicted about this because I do

0:24:07.800 --> 0:24:10.600
<v Speaker 1>think that if you're going to really invest in a

0:24:10.640 --> 0:24:14.480
<v Speaker 1>company's future, being willing to do that and know that

0:24:14.520 --> 0:24:17.720
<v Speaker 1>you're not going to see returns right away takes a

0:24:17.720 --> 0:24:21.000
<v Speaker 1>lot of bold decision making and ultimately can be the

0:24:21.040 --> 0:24:24.280
<v Speaker 1>best thing for the company. On the flip side, I

0:24:24.359 --> 0:24:27.880
<v Speaker 1>remain unconvinced that the metaverse and AI is really going

0:24:27.960 --> 0:24:31.520
<v Speaker 1>to give Meta the ability to stand apart from other

0:24:31.600 --> 0:24:34.879
<v Speaker 1>competitors in the space, or that the company has established

0:24:34.960 --> 0:24:37.560
<v Speaker 1>that there's a future in that particular type of computing

0:24:37.560 --> 0:24:40.560
<v Speaker 1>in the first place. So double edged sword kind of thing.

0:24:40.840 --> 0:24:43.520
<v Speaker 1>But I would actually like to see more companies take

0:24:43.640 --> 0:24:47.320
<v Speaker 1>a firm stance on yes, this is a painful decision

0:24:47.520 --> 0:24:49.919
<v Speaker 1>in the sense that you know, we're investing money in

0:24:49.960 --> 0:24:52.240
<v Speaker 1>something that's not going to be an immediate payoff, but

0:24:52.320 --> 0:24:55.000
<v Speaker 1>down the road it's going to be the best thing

0:24:55.040 --> 0:24:57.800
<v Speaker 1>for our company. I am really tired of seeing companies

0:24:57.800 --> 0:25:02.600
<v Speaker 1>that almost sacrifice everything for the purpose of getting short

0:25:02.680 --> 0:25:05.840
<v Speaker 1>term gains, because ultimately, I think that ends up corrupting

0:25:05.840 --> 0:25:09.159
<v Speaker 1>companies from the inside, and they ultimately crumble under their

0:25:09.200 --> 0:25:11.639
<v Speaker 1>own weight once they reach a point where you just

0:25:11.680 --> 0:25:15.000
<v Speaker 1>can't do that anymore. Okay, enough about that, But one

0:25:15.000 --> 0:25:18.680
<v Speaker 1>other thing that Zuckerbird brought up during that earnings call

0:25:19.080 --> 0:25:23.760
<v Speaker 1>was that Threads, the Meta operated alternative to Twitter, is

0:25:23.920 --> 0:25:27.720
<v Speaker 1>up to nearly two hundred and seventy five million monthly visitors.

0:25:28.080 --> 0:25:31.040
<v Speaker 1>That is a one hundred and seventy five percent increase

0:25:31.320 --> 0:25:34.240
<v Speaker 1>from last year, and he also said the app is

0:25:34.240 --> 0:25:38.080
<v Speaker 1>seeing more than one million new users sign up every

0:25:38.160 --> 0:25:42.439
<v Speaker 1>single day. Now, that, along with a general migration away

0:25:42.560 --> 0:25:46.280
<v Speaker 1>from X formerly known as Twitter, means the gap between

0:25:46.280 --> 0:25:50.240
<v Speaker 1>the two services is beginning to narrow. Analysts from Sensor

0:25:50.320 --> 0:25:53.119
<v Speaker 1>Tower estimate that X has somewhere in the neighborhood of

0:25:53.119 --> 0:25:56.400
<v Speaker 1>three hundred and eighteen million users. Now, I say estimate

0:25:56.480 --> 0:25:59.520
<v Speaker 1>because X is a private company, and as a private company,

0:25:59.600 --> 0:26:02.800
<v Speaker 1>they don't have to share that kind of information. Threads

0:26:03.240 --> 0:26:06.880
<v Speaker 1>is somewhere around two hundred and seventy five million monthly users.

0:26:07.119 --> 0:26:09.600
<v Speaker 1>So the growth of Threads, along with folks who are

0:26:09.680 --> 0:26:13.440
<v Speaker 1>ditching X, has changed the landscape quite a bit. Meta's

0:26:13.560 --> 0:26:17.560
<v Speaker 1>CFO Chief financial Officer Susan Lee has said that the

0:26:17.600 --> 0:26:20.680
<v Speaker 1>company doesn't expect Threads to be a significant revenue driver

0:26:20.760 --> 0:26:23.960
<v Speaker 1>in twenty twenty five. Rather, the focus will be on

0:26:24.520 --> 0:26:28.680
<v Speaker 1>growing the platform further before really exploiting the heck out

0:26:28.720 --> 0:26:31.000
<v Speaker 1>of it. Now, if I were a betting man, I

0:26:31.000 --> 0:26:33.800
<v Speaker 1>would say that Meta will eventually sprinkle some of its

0:26:33.840 --> 0:26:38.000
<v Speaker 1>targeted advertising ferry dust on Threads, and it will probably

0:26:38.000 --> 0:26:41.159
<v Speaker 1>happen in the not too distant future, and it will

0:26:41.200 --> 0:26:47.399
<v Speaker 1>increase Meta's already significant hold in the online advertising space. Meanwhile,

0:26:47.520 --> 0:26:51.440
<v Speaker 1>I expect X's decline to continue simply because Elon Musk

0:26:51.600 --> 0:26:56.000
<v Speaker 1>cannot help himself and consistently makes decisions that drive away

0:26:56.040 --> 0:27:00.959
<v Speaker 1>many users of X to other platforms include Threads and

0:27:01.000 --> 0:27:03.680
<v Speaker 1>blue Sky and mast it on. I think the one

0:27:03.720 --> 0:27:09.280
<v Speaker 1>advantage X has is that no other singular microblogging platform

0:27:09.720 --> 0:27:14.040
<v Speaker 1>has the dominance that Twitter once had, So either users

0:27:14.080 --> 0:27:17.359
<v Speaker 1>are adopting multiple platforms and kind of spreading their time

0:27:17.400 --> 0:27:20.719
<v Speaker 1>across them, or they're having to choose one of several

0:27:20.720 --> 0:27:23.879
<v Speaker 1>different offerings and just be satisfied with the fact that

0:27:23.920 --> 0:27:25.720
<v Speaker 1>they're not going to see everything they used to see

0:27:25.760 --> 0:27:29.760
<v Speaker 1>because other people have gone to competing services. So that's

0:27:29.840 --> 0:27:32.480
<v Speaker 1>kind of my view of where things are right now. Okay,

0:27:33.040 --> 0:27:34.960
<v Speaker 1>we're going to take another quick break, but I still

0:27:35.000 --> 0:27:38.800
<v Speaker 1>have plenty of tech news. This week was shock full, y'all,

0:27:39.040 --> 0:27:40.919
<v Speaker 1>so let's take a quick break. We'll be back with

0:27:40.960 --> 0:27:53.399
<v Speaker 1>some more headlines. Kylie Robson of The Verge has a

0:27:53.480 --> 0:27:57.639
<v Speaker 1>piece titled open AI's search engine is now live in

0:27:57.800 --> 0:28:01.159
<v Speaker 1>Chat GPT, which I'm sure is for concern for some

0:28:01.200 --> 0:28:04.800
<v Speaker 1>folks over at Google. Now. To be clear, this feature

0:28:04.920 --> 0:28:09.480
<v Speaker 1>is currently only available to paid subscribers of Chat GPT.

0:28:09.960 --> 0:28:13.199
<v Speaker 1>It will later roll out to other users, like, you know,

0:28:13.440 --> 0:28:17.560
<v Speaker 1>enterprise users or people who are working in educational institutions.

0:28:17.840 --> 0:28:21.919
<v Speaker 1>As Robison explains, the feature is integrated directly into the

0:28:22.000 --> 0:28:25.439
<v Speaker 1>chat gpt experience, so it's not like a separate tool

0:28:25.640 --> 0:28:29.800
<v Speaker 1>or tab or something. Users when they're putting in a

0:28:29.840 --> 0:28:35.639
<v Speaker 1>query and conversing with the chat gpt bot will sometimes

0:28:35.680 --> 0:28:41.160
<v Speaker 1>receive suggestions for various websites that relate to whatever the

0:28:41.320 --> 0:28:45.680
<v Speaker 1>topic of discussion is, so they'll get suggestions for resources

0:28:45.800 --> 0:28:49.880
<v Speaker 1>that they can use to further answer their questions. Robison

0:28:49.920 --> 0:28:53.400
<v Speaker 1>points out that chat GPT's search results do not contain

0:28:53.520 --> 0:28:57.200
<v Speaker 1>promoted results, so that might be a big advantage over

0:28:57.320 --> 0:29:00.360
<v Speaker 1>folks who previously had used Google. You can, and also,

0:29:00.440 --> 0:29:03.640
<v Speaker 1>by the way, directly ask chat gpt to give you

0:29:04.040 --> 0:29:07.520
<v Speaker 1>web results, so you can ask it to give you

0:29:07.560 --> 0:29:11.160
<v Speaker 1>those those websites from the beginning and just treat it

0:29:11.240 --> 0:29:16.440
<v Speaker 1>like it's a search engine. And by not including promoted results,

0:29:16.160 --> 0:29:19.840
<v Speaker 1>that's a shot across the bow at Google, because that's

0:29:19.880 --> 0:29:22.680
<v Speaker 1>Google's bread and butter. I'm guessing anyone who has used

0:29:22.720 --> 0:29:25.760
<v Speaker 1>Google for like the last decade has noticed that sponsored

0:29:25.800 --> 0:29:29.920
<v Speaker 1>results appear at the top of search results. Lists now.

0:29:29.960 --> 0:29:33.560
<v Speaker 1>In the very old days, the general expectation was that

0:29:33.640 --> 0:29:37.560
<v Speaker 1>the most relevant, highest quality search results would appear at

0:29:37.560 --> 0:29:41.200
<v Speaker 1>the very top of Google's results page. But for the

0:29:41.240 --> 0:29:44.160
<v Speaker 1>last several years, the very top of that list is

0:29:44.240 --> 0:29:48.440
<v Speaker 1>frequently dominated with paid ads that lock in those spots,

0:29:48.720 --> 0:29:51.760
<v Speaker 1>And even though Google does tag those search results as

0:29:51.800 --> 0:29:55.760
<v Speaker 1>being promoted search results, some folks still bristle at how

0:29:55.840 --> 0:29:58.680
<v Speaker 1>this feels like preferential treatment for what is often thought

0:29:58.680 --> 0:30:01.960
<v Speaker 1>of as a scholarly like ibbe. As if you went

0:30:02.040 --> 0:30:05.000
<v Speaker 1>to the library and you wanted to look up books

0:30:05.040 --> 0:30:07.600
<v Speaker 1>that were about a specific topic, and you found out

0:30:07.760 --> 0:30:10.600
<v Speaker 1>that the results of all the books in the library

0:30:10.600 --> 0:30:13.160
<v Speaker 1>that do relate to that topic have been ordered not

0:30:13.480 --> 0:30:18.640
<v Speaker 1>by author name or whatever, but by way of who

0:30:18.680 --> 0:30:22.040
<v Speaker 1>has paid the library to have their book promoted the most.

0:30:22.600 --> 0:30:26.400
<v Speaker 1>That's not cool. Open ai claims it does not intend

0:30:26.480 --> 0:30:29.560
<v Speaker 1>on selling advertising the way Google does, but that does

0:30:29.680 --> 0:30:33.520
<v Speaker 1>raise questions as to how AI will generate revenue from

0:30:33.600 --> 0:30:37.280
<v Speaker 1>free users who use this tool, because presumably free users

0:30:37.280 --> 0:30:39.680
<v Speaker 1>will be able to interact with this in the not

0:30:39.760 --> 0:30:43.040
<v Speaker 1>too distant future. Another question that remains is how open

0:30:43.080 --> 0:30:46.000
<v Speaker 1>ai will navigate the choppy waters when it comes to

0:30:46.120 --> 0:30:51.440
<v Speaker 1>referencing or pulling from various resources online. Most media companies

0:30:51.480 --> 0:30:53.600
<v Speaker 1>would very much prefer if you were to go to

0:30:53.720 --> 0:30:56.479
<v Speaker 1>their website and read stuff on their own web pages.

0:30:56.640 --> 0:30:59.200
<v Speaker 1>That's one of the many reasons I actually recommend folks

0:30:59.320 --> 0:31:03.240
<v Speaker 1>check out the articles that I reference in these episodes. BENJ.

0:31:03.520 --> 0:31:08.080
<v Speaker 1>Edwards of Ours Technica, as an article titled Google CEO says,

0:31:08.120 --> 0:31:11.720
<v Speaker 1>over twenty five percent of new Google code is generated

0:31:11.760 --> 0:31:15.600
<v Speaker 1>by AI. That's really incredible that more than one quarter

0:31:15.960 --> 0:31:19.880
<v Speaker 1>of the code generated within Google is coming from AI tools. Now,

0:31:19.880 --> 0:31:23.760
<v Speaker 1>according to Google executives, all these operations are still ultimately

0:31:23.800 --> 0:31:27.840
<v Speaker 1>overseen by actual human beings. AI might generate some of

0:31:27.880 --> 0:31:31.840
<v Speaker 1>that code, but humans review and then approve that code

0:31:31.920 --> 0:31:34.240
<v Speaker 1>before it can be deployed. Now, the purpose of this

0:31:34.320 --> 0:31:38.200
<v Speaker 1>structure is to streamline coding and speed things up, presumably

0:31:38.240 --> 0:31:40.240
<v Speaker 1>while also cutting down on the need for quite so

0:31:40.320 --> 0:31:43.280
<v Speaker 1>many people coding for Google in the first place. And

0:31:43.320 --> 0:31:46.720
<v Speaker 1>as Edwards explains, not everyone is super happy about how

0:31:46.800 --> 0:31:50.080
<v Speaker 1>AI is taking such a prominent role in coding. There

0:31:50.120 --> 0:31:53.240
<v Speaker 1>are critics who worry that relying so heavily on AI

0:31:53.440 --> 0:31:56.800
<v Speaker 1>means we could end up with apps and code that

0:31:56.880 --> 0:32:00.880
<v Speaker 1>has more errors in it more vulnerabilities interduced into the

0:32:00.920 --> 0:32:05.200
<v Speaker 1>code that are difficult to detect, meaning that anyone deploying

0:32:05.200 --> 0:32:08.600
<v Speaker 1>that code could be creating opportunities for hackers, and maybe

0:32:08.640 --> 0:32:11.880
<v Speaker 1>the hackers are using their own AI tools to identify

0:32:12.000 --> 0:32:15.120
<v Speaker 1>and then exploit those vulnerabilities. In fact, I think that's

0:32:15.160 --> 0:32:18.760
<v Speaker 1>just a guarantee. I think AI coding and AI hacking

0:32:19.000 --> 0:32:21.520
<v Speaker 1>that's the reality we face now. It's going to be

0:32:21.560 --> 0:32:26.240
<v Speaker 1>a seesaw like relationship moving forward. I recommend reading BENJ.

0:32:26.400 --> 0:32:29.280
<v Speaker 1>Edwards article in full for a deeper look into the story,

0:32:29.320 --> 0:32:32.000
<v Speaker 1>including how some studies have shown that folks who have

0:32:32.280 --> 0:32:36.400
<v Speaker 1>used AI to help code will simultaneously end up believing

0:32:36.440 --> 0:32:39.720
<v Speaker 1>that their code is superior to other people's code because

0:32:39.760 --> 0:32:43.080
<v Speaker 1>they used AI tools to make it, while also introducing

0:32:43.160 --> 0:32:46.480
<v Speaker 1>more bugs into their own work. So it's kind of

0:32:46.520 --> 0:32:51.960
<v Speaker 1>like creating this false sense of superiority or our expectation.

0:32:52.760 --> 0:32:57.240
<v Speaker 1>Jonathan M. Gitlin, also of ours Tetnica, has another Google piece.

0:32:57.320 --> 0:33:01.000
<v Speaker 1>This one is titled Generative AI is Coming to Google Maps,

0:33:01.200 --> 0:33:04.560
<v Speaker 1>Google Earth Ways and Yeah. It's all about how Google

0:33:04.640 --> 0:33:08.120
<v Speaker 1>is incorporating more AI tools into its various map apps

0:33:08.320 --> 0:33:11.440
<v Speaker 1>to give users more features. Some of this was news

0:33:11.440 --> 0:33:13.160
<v Speaker 1>to me, In fact, quite a bit of news to me,

0:33:13.240 --> 0:33:16.560
<v Speaker 1>even though apparently some of these features have been around

0:33:16.600 --> 0:33:20.400
<v Speaker 1>for a while. So for example, Getland quotes Google's VP

0:33:20.520 --> 0:33:25.959
<v Speaker 1>and general manager of GEO. That's Chris Phillips, who said, quote,

0:33:26.360 --> 0:33:30.080
<v Speaker 1>think of features like lens and maps. When you're on

0:33:30.120 --> 0:33:32.560
<v Speaker 1>a street corner, you can lift up your phone and look,

0:33:32.680 --> 0:33:35.760
<v Speaker 1>and through your camera view you can actually see. We

0:33:35.880 --> 0:33:38.400
<v Speaker 1>laid places on top of your view so you can

0:33:38.400 --> 0:33:41.640
<v Speaker 1>see a business, Is it open, what are the ratings

0:33:41.680 --> 0:33:44.400
<v Speaker 1>for it? Is it busy? You can even see businesses

0:33:44.440 --> 0:33:47.280
<v Speaker 1>that are out of your line of sight. End quote.

0:33:47.520 --> 0:33:49.560
<v Speaker 1>I didn't know about that, although I have talked about

0:33:49.640 --> 0:33:53.120
<v Speaker 1>that very use case and augmented reality in the past.

0:33:53.280 --> 0:33:55.440
<v Speaker 1>But I think it's pretty cool, particularly if you're out

0:33:55.440 --> 0:33:57.880
<v Speaker 1>and about somewhere that's new to you and you want

0:33:57.920 --> 0:34:00.840
<v Speaker 1>to find a place that's like open and nottally slammed.

0:34:01.160 --> 0:34:04.040
<v Speaker 1>I actually could have used that. Last weekend, me and

0:34:04.080 --> 0:34:07.880
<v Speaker 1>my party were in Pennsylvania for the Pennsylvania Renaissance Fair,

0:34:07.920 --> 0:34:10.480
<v Speaker 1>which now is over, but if you ever get a chance,

0:34:10.600 --> 0:34:13.160
<v Speaker 1>it's a phenomenal renaissance fair. I say that as someone

0:34:13.480 --> 0:34:16.560
<v Speaker 1>who used to work at a Renaissance Fair. It's amazing.

0:34:16.719 --> 0:34:19.560
<v Speaker 1>But after the fair was done on Sunday, we wanted

0:34:19.600 --> 0:34:21.680
<v Speaker 1>to go and eat at a restaurant, and we had

0:34:21.719 --> 0:34:23.839
<v Speaker 1>identified which one we wanted to go to, but by

0:34:23.880 --> 0:34:25.600
<v Speaker 1>the time we got there, we found out the kitchen

0:34:25.600 --> 0:34:28.880
<v Speaker 1>had already closed, and so we were forced to change

0:34:28.880 --> 0:34:31.560
<v Speaker 1>our plans and find somewhere else to grab dinner. Having

0:34:31.640 --> 0:34:34.440
<v Speaker 1>this tool would have told us like, oh, by the

0:34:34.440 --> 0:34:36.239
<v Speaker 1>time you get there, it's going to be too late,

0:34:36.320 --> 0:34:39.440
<v Speaker 1>so don't even bother, and that would have saved us

0:34:39.440 --> 0:34:42.960
<v Speaker 1>some trouble. Anyway, Google is bringing AI enabled search results

0:34:43.000 --> 0:34:45.480
<v Speaker 1>to Maps, so if you just have a general hanker

0:34:45.520 --> 0:34:47.680
<v Speaker 1>in for something but you don't know any more details,

0:34:47.920 --> 0:34:50.000
<v Speaker 1>you can ask Maps and have a little conversation with

0:34:50.040 --> 0:34:53.000
<v Speaker 1>an AI bought to whittle down your options. Check out

0:34:53.000 --> 0:34:56.320
<v Speaker 1>Getland's article to learn more about the upcoming features headed

0:34:56.400 --> 0:34:59.960
<v Speaker 1>to Google Maps and these other tools. Joshua Tyler of

0:35:00.080 --> 0:35:04.400
<v Speaker 1>Giant Freaking Robot has an article titled I attended Google's

0:35:04.440 --> 0:35:09.480
<v Speaker 1>Creator Conversation event and it turned into a funeral. Yikes.

0:35:09.600 --> 0:35:11.800
<v Speaker 1>All right, so this is about an event that Google

0:35:11.880 --> 0:35:14.960
<v Speaker 1>held this week, and Tyler's description of it is pretty

0:35:15.080 --> 0:35:18.400
<v Speaker 1>darn grim. He talks about receiving a tour of the

0:35:18.440 --> 0:35:21.240
<v Speaker 1>Google campus, and it was a tour of a campus

0:35:21.239 --> 0:35:24.760
<v Speaker 1>that was almost completely empty, although the event was happening

0:35:24.800 --> 0:35:27.480
<v Speaker 1>in the middle of a work day. He describes getting

0:35:27.520 --> 0:35:31.120
<v Speaker 1>not one but two security badges before being allowed into

0:35:31.160 --> 0:35:33.919
<v Speaker 1>a secure building, only to have no one actually look

0:35:33.960 --> 0:35:37.520
<v Speaker 1>at or check his credentials once that time came. According

0:35:37.520 --> 0:35:40.880
<v Speaker 1>to Tyler, the attendees of this event consisted of folks

0:35:40.920 --> 0:35:44.640
<v Speaker 1>who worked on independent websites that have been shadow band

0:35:45.280 --> 0:35:49.160
<v Speaker 1>due to Google's changes in its approach to generating search results. Now,

0:35:49.200 --> 0:35:51.800
<v Speaker 1>in case you're not familiar with the term shadow band,

0:35:52.080 --> 0:35:56.000
<v Speaker 1>it means that you're blocking someone or something from your

0:35:56.040 --> 0:35:59.920
<v Speaker 1>online service like a forum or in this case, Google

0:36:00.200 --> 0:36:02.919
<v Speaker 1>search results, and they don't have any knowledge that they've

0:36:02.960 --> 0:36:05.759
<v Speaker 1>been blocked. So the entity is still allowed to make

0:36:05.920 --> 0:36:09.040
<v Speaker 1>posts on the platform. Like let's say that it's a

0:36:09.080 --> 0:36:13.640
<v Speaker 1>social media platform, you could still post to it. The trick, though,

0:36:13.680 --> 0:36:16.160
<v Speaker 1>is that no one is seeing your posts. Yeah, your

0:36:16.160 --> 0:36:19.640
<v Speaker 1>posts are being published, but no one actually gets to

0:36:19.680 --> 0:36:23.200
<v Speaker 1>see them. That way, the entity that's making these posts

0:36:23.680 --> 0:36:27.120
<v Speaker 1>remains unaware that their work is purposefully being withheld from

0:36:27.160 --> 0:36:29.920
<v Speaker 1>the intended audience, and then they're just left to wonder

0:36:30.000 --> 0:36:33.759
<v Speaker 1>why the heck their traffic stats are in serious decline.

0:36:33.920 --> 0:36:38.000
<v Speaker 1>Tyler and other site owners and operators began to answer

0:36:38.160 --> 0:36:42.120
<v Speaker 1>questions from Googlers, So this conversation was really Googler's asking

0:36:42.760 --> 0:36:46.160
<v Speaker 1>the site owners questions, and the owners tried to bring

0:36:46.280 --> 0:36:49.600
<v Speaker 1>up their concerns about how changes to Google's approach had

0:36:49.600 --> 0:36:54.440
<v Speaker 1>disproportionately affected their traffic stats. I recommend reading Tyler's full article.

0:36:54.560 --> 0:36:57.719
<v Speaker 1>It is upsetting, it is sad, and as someone who

0:36:57.760 --> 0:37:00.400
<v Speaker 1>worked for a company that was really heavily depend on

0:37:00.880 --> 0:37:05.240
<v Speaker 1>ranking well and search results, I feel his frustration quite keenly.

0:37:05.800 --> 0:37:08.520
<v Speaker 1>Over in Russia, the government there is trying to force

0:37:08.600 --> 0:37:13.800
<v Speaker 1>Google to reinstate certain YouTube channels, particularly state backed channels

0:37:13.920 --> 0:37:18.239
<v Speaker 1>that are frequently associated with distributing misinformation, particularly about the

0:37:18.280 --> 0:37:22.440
<v Speaker 1>war in Ukraine. YouTube has banned those channels for violations

0:37:22.480 --> 0:37:25.520
<v Speaker 1>of the company's various policies, and Russia says that's just

0:37:25.600 --> 0:37:30.399
<v Speaker 1>not cool. So Russia levy to fine against Google, which

0:37:30.440 --> 0:37:36.000
<v Speaker 1>is currently standing at two undecillian rubles. Now I'm pulling

0:37:36.000 --> 0:37:39.600
<v Speaker 1>this from John Broadkin's article in Ours Technica. It's titled

0:37:39.800 --> 0:37:44.319
<v Speaker 1>Russia finds Google an impossible amount in attempt to end

0:37:44.480 --> 0:37:47.960
<v Speaker 1>YouTube bans. So if you're wondering how much is two

0:37:48.400 --> 0:37:52.400
<v Speaker 1>Undecillian rubles if you convert it to dollars, well, Broadkin

0:37:52.480 --> 0:37:56.160
<v Speaker 1>has kindly done that conversion for us, so it's roughly

0:37:56.480 --> 0:38:02.759
<v Speaker 1>the number twenty followed by thirty three zeros in dollars. Like,

0:38:02.800 --> 0:38:08.080
<v Speaker 1>it's more money than the world's gross domestic product. And

0:38:08.239 --> 0:38:10.319
<v Speaker 1>to say that Google will not pay this is of

0:38:10.320 --> 0:38:14.400
<v Speaker 1>course obvious because nobody could pay it. No one, not

0:38:14.520 --> 0:38:17.840
<v Speaker 1>the entire world, has that much money. So it's not

0:38:18.000 --> 0:38:21.239
<v Speaker 1>really a real fine. It's a message to Google saying, hey,

0:38:21.320 --> 0:38:24.120
<v Speaker 1>give us our YouTube channels back. We mean it. Or rather,

0:38:24.160 --> 0:38:26.920
<v Speaker 1>it's a fine that really had a stipulation attached to it.

0:38:27.000 --> 0:38:30.160
<v Speaker 1>So originally this fine was much less than that. But

0:38:30.239 --> 0:38:33.040
<v Speaker 1>if Google refused to reverse its decision to ban the

0:38:33.120 --> 0:38:36.080
<v Speaker 1>channels and to pay the fine, that fine would double

0:38:36.239 --> 0:38:38.440
<v Speaker 1>after a given amount of time. So have you ever

0:38:38.480 --> 0:38:41.160
<v Speaker 1>played the game where you take like two pennies and

0:38:41.200 --> 0:38:44.200
<v Speaker 1>then you double it to see how many times doubling

0:38:44.239 --> 0:38:47.319
<v Speaker 1>it would take before you're dealing with a good deal

0:38:47.320 --> 0:38:49.799
<v Speaker 1>of money. Like if you took two pennies and you

0:38:49.880 --> 0:38:52.400
<v Speaker 1>doubled it for eight rounds, you would end up with

0:38:52.440 --> 0:38:55.000
<v Speaker 1>two dollars fifty six cents in pennies. If you did

0:38:55.000 --> 0:38:57.760
<v Speaker 1>it for sixteen rounds, you've got six hundred and fifty

0:38:57.760 --> 0:39:00.799
<v Speaker 1>five dollars and thirty six cents also in pennies. If

0:39:00.800 --> 0:39:03.560
<v Speaker 1>you did it for thirty two rounds, you would have

0:39:03.760 --> 0:39:09.880
<v Speaker 1>nearly forty three million dollars in pennies. Doubling gets really big,

0:39:10.520 --> 0:39:15.560
<v Speaker 1>really fast, so no wonder that fine is now ginormously huge.

0:39:16.080 --> 0:39:18.600
<v Speaker 1>Google's response, in a large part over the course of

0:39:18.640 --> 0:39:21.640
<v Speaker 1>this dispute has essentially been to pull up Stakes out

0:39:21.640 --> 0:39:24.840
<v Speaker 1>of Russia and to shut down most operations there, including

0:39:24.920 --> 0:39:28.840
<v Speaker 1>like relocating people who work for Google to leave Russia

0:39:28.920 --> 0:39:32.120
<v Speaker 1>and work in other offices. So I suspect we're not

0:39:32.160 --> 0:39:35.720
<v Speaker 1>going to see much movement on Google's behalf here. Okay,

0:39:35.719 --> 0:39:38.720
<v Speaker 1>I've got a few recommendations for reading for all of y'all,

0:39:38.840 --> 0:39:40.960
<v Speaker 1>in addition to the articles that I've already mentioned in

0:39:41.000 --> 0:39:45.200
<v Speaker 1>this episode. First up is Eric Berger's piece in Ours Technica.

0:39:45.280 --> 0:39:49.399
<v Speaker 1>It is titled what is Happening with Boeing's Starliner Spacecraft?

0:39:49.680 --> 0:39:52.440
<v Speaker 1>As we have covered on tech Stuff, the star Liner

0:39:52.520 --> 0:39:55.320
<v Speaker 1>has had a really bumpy go of it. A Starliner

0:39:55.400 --> 0:39:59.759
<v Speaker 1>spacecraft successfully delivered two astronauts to the International Space Station,

0:40:00.200 --> 0:40:03.480
<v Speaker 1>but on the way there, the spacecraft experienced problems with

0:40:03.520 --> 0:40:07.360
<v Speaker 1>its thruster systems, and ultimately NASA decided to return the

0:40:07.400 --> 0:40:11.160
<v Speaker 1>star Liner to Earth without the astronauts aboard it. They

0:40:11.200 --> 0:40:14.799
<v Speaker 1>will have to come back home aboard a SpaceX spacecraft.

0:40:15.040 --> 0:40:18.840
<v Speaker 1>At a debriefing designed to address the star Liner as

0:40:19.360 --> 0:40:22.719
<v Speaker 1>it had returned to Earth, the two reps expected from

0:40:22.800 --> 0:40:27.440
<v Speaker 1>Boeing didn't show up. The company has remained silent about

0:40:27.480 --> 0:40:30.319
<v Speaker 1>the star Liner in the weeks following the landing. Two

0:40:30.360 --> 0:40:32.879
<v Speaker 1>months have gone by and we haven't really received any

0:40:32.960 --> 0:40:36.759
<v Speaker 1>updates on it. Berger explains that, you know, here's what

0:40:36.800 --> 0:40:40.440
<v Speaker 1>we know, here's what folks suspect about the spacecraft moving

0:40:40.480 --> 0:40:45.080
<v Speaker 1>forward or maybe not moving forward, and so that one's

0:40:45.120 --> 0:40:47.880
<v Speaker 1>well worth a read. The other piece that I recommend

0:40:47.960 --> 0:40:52.120
<v Speaker 1>reading is Arianna Bindmann's piece in sf gait. It is

0:40:52.200 --> 0:40:56.800
<v Speaker 1>titled a Lot of Demoralized People. Ghost jobs are wreaking

0:40:56.880 --> 0:41:00.880
<v Speaker 1>havoc on tech workers. So this is about how companies

0:41:00.880 --> 0:41:04.440
<v Speaker 1>in general, but particularly in the tech space, will often

0:41:04.480 --> 0:41:08.560
<v Speaker 1>post jobs to various career sites, but those jobs aren't

0:41:08.640 --> 0:41:11.000
<v Speaker 1>really available now. It may be a case that the

0:41:11.000 --> 0:41:14.040
<v Speaker 1>company has already filled the positions in question. It may

0:41:14.080 --> 0:41:16.440
<v Speaker 1>be a case that they were never looking to hire

0:41:16.480 --> 0:41:21.280
<v Speaker 1>in the first place. And the article explains why companies

0:41:21.360 --> 0:41:24.360
<v Speaker 1>do this, and here's a spoiler alert, it's for awful,

0:41:24.640 --> 0:41:29.480
<v Speaker 1>cruel and selfish reasons. I highly recommend reading the article

0:41:29.600 --> 0:41:33.000
<v Speaker 1>if you have need of being really angry at corporations today.

0:41:33.239 --> 0:41:35.799
<v Speaker 1>This is a great way to get very mad at corporations.

0:41:35.840 --> 0:41:38.560
<v Speaker 1>It's also just a very good read in general. It's

0:41:38.560 --> 0:41:41.080
<v Speaker 1>also very important for anybody who might be in the

0:41:41.200 --> 0:41:44.680
<v Speaker 1>job market. If you're someone who has experienced the very

0:41:44.760 --> 0:41:49.400
<v Speaker 1>rough setback of having sent out countless resumes only to

0:41:49.480 --> 0:41:53.200
<v Speaker 1>hear nothing, this practice might be playing a part in

0:41:53.239 --> 0:41:58.400
<v Speaker 1>that this process of posting fake jobs to sites. Understanding

0:41:58.480 --> 0:42:02.919
<v Speaker 1>why that happens can also help explain maybe your lack

0:42:02.960 --> 0:42:05.600
<v Speaker 1>of traction if you've been job hunting and nothing's come back,

0:42:05.640 --> 0:42:09.879
<v Speaker 1>because that can be really demoralizing. It can really add

0:42:09.920 --> 0:42:13.799
<v Speaker 1>to stress and depression if you're constantly putting yourself out

0:42:13.840 --> 0:42:16.759
<v Speaker 1>there but you're not hearing anything back. Well, part of

0:42:16.800 --> 0:42:19.120
<v Speaker 1>the reason of that might be that the companies you're

0:42:19.160 --> 0:42:22.520
<v Speaker 1>applying to didn't actually have jobs available in the first place,

0:42:22.800 --> 0:42:25.640
<v Speaker 1>and this article explains why, so check that out as well.

0:42:26.080 --> 0:42:28.719
<v Speaker 1>That's it for me. I hope all of you had

0:42:28.800 --> 0:42:31.279
<v Speaker 1>a fantastic week. For those of you who were out

0:42:31.360 --> 0:42:33.800
<v Speaker 1>there trick or treating with the kiddo's or whatever, I

0:42:33.840 --> 0:42:37.200
<v Speaker 1>hope you had a great time. Enjoy some mounds and

0:42:37.280 --> 0:42:40.120
<v Speaker 1>almond joy on my behalf, and I'll talk to you

0:42:40.160 --> 0:42:50.640
<v Speaker 1>again really soon. Tech Stuff is an iHeartRadio production. For

0:42:50.800 --> 0:42:55.640
<v Speaker 1>more podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts,

0:42:55.760 --> 0:43:01.799
<v Speaker 1>or wherever you listen to your favorite shows. You