WEBVTT - Tech News: Meta Cuts 13% of Workforce

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to tech Stuff, a production from I Heart Radio.

0:00:11.840 --> 0:00:14.520
<v Speaker 1>Be there and welcome to tech Stuff. I'm your host

0:00:14.640 --> 0:00:17.520
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio.

0:00:17.600 --> 0:00:20.200
<v Speaker 1>And how the tech are you? Sime for the Tech

0:00:20.280 --> 0:00:24.640
<v Speaker 1>News for Thursday, November two thousand twenty two, And on

0:00:24.680 --> 0:00:27.920
<v Speaker 1>Tuesday I mentioned that folks were expecting Meta to hold

0:00:27.960 --> 0:00:32.960
<v Speaker 1>a round of layoffs, and then yesterday that happened. All told,

0:00:33.000 --> 0:00:36.880
<v Speaker 1>the company handed walking papers over to of its staff.

0:00:37.240 --> 0:00:42.440
<v Speaker 1>That's more than eleven thousand people. CEO Mark Zuckerberg sent

0:00:42.479 --> 0:00:45.720
<v Speaker 1>out a memo calling the layoffs a last resort, though

0:00:45.760 --> 0:00:48.680
<v Speaker 1>I'm not entirely sure he knows what last resort means,

0:00:48.720 --> 0:00:52.360
<v Speaker 1>because I suspect we haven't actually seen the last resort

0:00:52.600 --> 0:00:57.200
<v Speaker 1>from Meta. Zuckerberg also said he wanted to take accountability

0:00:57.240 --> 0:01:00.160
<v Speaker 1>for the decision and that he was a special lee.

0:01:00.280 --> 0:01:03.959
<v Speaker 1>Sorry to those impacted. So this is the same CEO

0:01:04.080 --> 0:01:06.600
<v Speaker 1>who back in June said there were people at Meta

0:01:06.640 --> 0:01:09.240
<v Speaker 1>who probably didn't need to be there, implying the company

0:01:09.280 --> 0:01:12.399
<v Speaker 1>had more staff than what was needed and that individual

0:01:12.440 --> 0:01:16.840
<v Speaker 1>productivity was down because of that. Zuckerberg further explained that

0:01:16.959 --> 0:01:19.039
<v Speaker 1>closer to the beginning of the pandemic, there was a

0:01:19.120 --> 0:01:22.000
<v Speaker 1>rush to spend more time online, and all of that

0:01:22.080 --> 0:01:24.120
<v Speaker 1>makes sense, but then he goes on to say that

0:01:24.160 --> 0:01:26.120
<v Speaker 1>he and his team all thought that that move to

0:01:26.160 --> 0:01:30.520
<v Speaker 1>be online more frequently would be a permanent thing that

0:01:30.560 --> 0:01:33.839
<v Speaker 1>people wouldn't ease off once local restrictions lifted and people

0:01:33.840 --> 0:01:37.640
<v Speaker 1>started feeling safe outside their homes. And who boy, were

0:01:37.680 --> 0:01:41.959
<v Speaker 1>they wrong about that one anyway, because the prediction was

0:01:42.040 --> 0:01:44.160
<v Speaker 1>that things were going to be all online all the time,

0:01:44.240 --> 0:01:47.600
<v Speaker 1>which honestly makes me think of the metaverse concept. Meadow

0:01:47.640 --> 0:01:50.760
<v Speaker 1>went on a hiring spree. According to the company's earnings

0:01:50.760 --> 0:01:53.800
<v Speaker 1>report in the third quarter, employee head count was almost

0:01:54.640 --> 0:01:58.880
<v Speaker 1>larger than it was this time last year. So when

0:01:58.880 --> 0:02:01.600
<v Speaker 1>you look at it that way, a thirteent reduction in

0:02:01.640 --> 0:02:05.600
<v Speaker 1>workforce still has met a significantly larger from a headcount

0:02:05.600 --> 0:02:09.799
<v Speaker 1>perspective than it was at the end of Now I'm

0:02:09.840 --> 0:02:14.760
<v Speaker 1>being pretty judge of Zuckerberg and his executive team, but

0:02:14.880 --> 0:02:17.840
<v Speaker 1>if I really want to be fair, Meta did need

0:02:17.919 --> 0:02:21.000
<v Speaker 1>to make some moves to correct course. I'm not entirely

0:02:21.040 --> 0:02:24.680
<v Speaker 1>convinced it has actually done that, because Zuckerberg still seems

0:02:24.720 --> 0:02:27.440
<v Speaker 1>determined to bring his vision of the Metaverse to realization.

0:02:28.200 --> 0:02:30.440
<v Speaker 1>That's gonna take a lot more time, a lot more money.

0:02:30.600 --> 0:02:32.880
<v Speaker 1>It's gonna be a really tough road to travel, and

0:02:32.919 --> 0:02:36.400
<v Speaker 1>even if the company gets there, I'm not yet convinced

0:02:36.400 --> 0:02:39.480
<v Speaker 1>that enough people actually want to use the metaverse to

0:02:39.520 --> 0:02:42.240
<v Speaker 1>make it all worthwhile. But then, Meta is a company

0:02:42.240 --> 0:02:46.080
<v Speaker 1>that is facing an existential crisis, has struggled to attract

0:02:46.320 --> 0:02:49.920
<v Speaker 1>younger users, and with its current user base steadily aging,

0:02:50.360 --> 0:02:53.400
<v Speaker 1>it's kind of like a ticking time bomb situation. So

0:02:53.440 --> 0:02:55.760
<v Speaker 1>I guess what I'm saying is I don't really believe

0:02:55.840 --> 0:02:59.520
<v Speaker 1>in Zuckerberg's mission. So with that in mind, I do

0:02:59.600 --> 0:03:02.520
<v Speaker 1>hold him accountable because it was the pursuit of that

0:03:02.600 --> 0:03:06.080
<v Speaker 1>mission that has really contributed heavily to Meta needing to

0:03:06.120 --> 0:03:09.280
<v Speaker 1>cut costs and scale down in the first place. All

0:03:09.280 --> 0:03:11.839
<v Speaker 1>that being said, you should keep in mind I am

0:03:11.960 --> 0:03:14.720
<v Speaker 1>by no means an expert in this stuff. This is

0:03:14.760 --> 0:03:17.800
<v Speaker 1>really just my opinion, and it's possible, I mean, it's

0:03:17.840 --> 0:03:21.799
<v Speaker 1>probably even likely that I'm totally off base. Maybe we'll

0:03:21.840 --> 0:03:24.680
<v Speaker 1>all be wearing headsets and spending countless hours working and

0:03:24.680 --> 0:03:30.160
<v Speaker 1>playing in the metaverse in a few years. The well, look,

0:03:30.360 --> 0:03:33.960
<v Speaker 1>I managed to put the Twitter stuff in the second

0:03:34.160 --> 0:03:37.200
<v Speaker 1>position for today's news episode instead of leading with it.

0:03:37.240 --> 0:03:42.840
<v Speaker 1>That's progress, I guess. Twitter launched its new blue check

0:03:42.920 --> 0:03:47.080
<v Speaker 1>mark verification strategy yesterday and after holding off because hey,

0:03:47.240 --> 0:03:50.120
<v Speaker 1>folks pointed out that having a verification system that doesn't

0:03:50.160 --> 0:03:54.720
<v Speaker 1>actually do any verification right before you hold an election

0:03:55.280 --> 0:03:58.200
<v Speaker 1>could be a bad idea. Of course, I live in

0:03:58.200 --> 0:04:00.120
<v Speaker 1>the state where we're going to have to have a

0:04:00.280 --> 0:04:03.320
<v Speaker 1>runoff election later on in December, so I look forward

0:04:03.360 --> 0:04:06.320
<v Speaker 1>to this broken approach having a massive impact on my

0:04:06.400 --> 0:04:09.560
<v Speaker 1>local politics in a month. And yes, it is my

0:04:09.720 --> 0:04:13.960
<v Speaker 1>opinion that the verification system as it now exists is

0:04:14.080 --> 0:04:18.720
<v Speaker 1>largely worthless, or, as tech crunches Lance Ulanov put it,

0:04:18.720 --> 0:04:21.599
<v Speaker 1>it's quote about to have as much value as a

0:04:21.640 --> 0:04:24.960
<v Speaker 1>sticker someone hands a child for behaving at the dentist

0:04:25.120 --> 0:04:29.239
<v Speaker 1>end quote. Okay, just in case you are not sure

0:04:29.279 --> 0:04:33.359
<v Speaker 1>what I'm even ranting about here, Previously, Twitter head a

0:04:33.400 --> 0:04:36.719
<v Speaker 1>system to check and make sure that the Twitter account

0:04:36.839 --> 0:04:40.720
<v Speaker 1>claiming to represent a known entity. You know, it might

0:04:40.760 --> 0:04:43.200
<v Speaker 1>be a celebrity, it might be a politician, it could

0:04:43.200 --> 0:04:46.839
<v Speaker 1>be the the Twitter feed for an official brand. That

0:04:46.960 --> 0:04:50.120
<v Speaker 1>kind of thing. They had to actually make sure that

0:04:50.120 --> 0:04:54.200
<v Speaker 1>those accounts belonged to those entities, that this wasn't a

0:04:54.200 --> 0:04:59.520
<v Speaker 1>case of someone impersonating a notable figure. If Twitter researchers

0:04:59.520 --> 0:05:03.599
<v Speaker 1>determine the YEP that account is legitimate, then they would

0:05:03.640 --> 0:05:06.720
<v Speaker 1>award a blue check mark to that account to show

0:05:06.720 --> 0:05:11.000
<v Speaker 1>everyone that this was the real deal. It gave users

0:05:11.040 --> 0:05:14.000
<v Speaker 1>the confidence to know that they were following an official

0:05:14.040 --> 0:05:17.239
<v Speaker 1>account that really represented who they thought they were following.

0:05:17.720 --> 0:05:20.560
<v Speaker 1>For reasons I still don't understand, I got one of

0:05:20.600 --> 0:05:23.279
<v Speaker 1>those blue check marks on my personal Twitter handle back

0:05:23.320 --> 0:05:26.919
<v Speaker 1>when I was still using Twitter. Technically I still have it,

0:05:27.000 --> 0:05:29.800
<v Speaker 1>but my accounts all protected now and I don't use

0:05:29.839 --> 0:05:34.400
<v Speaker 1>it anymore anyway. The news system is subscription based. If

0:05:34.400 --> 0:05:36.800
<v Speaker 1>you pay eight bucks a month, you have access to

0:05:36.920 --> 0:05:41.800
<v Speaker 1>Twitter Blue, and that includes the little blue checkmark. Twitter

0:05:41.880 --> 0:05:46.120
<v Speaker 1>briefly rolled out a gray badge that says official to

0:05:46.400 --> 0:05:49.599
<v Speaker 1>Twitter accounts. Uh. These were sort of like taking the

0:05:49.600 --> 0:05:53.480
<v Speaker 1>place of the old blue check marks for previously verified accounts,

0:05:53.520 --> 0:05:57.160
<v Speaker 1>at least for some of them originally. Ell It's reported

0:05:57.200 --> 0:06:00.000
<v Speaker 1>that the new official verification was kind of rolling out gradually.

0:06:00.040 --> 0:06:02.240
<v Speaker 1>I mean. Tech Crunch even pointed out that President Joe

0:06:02.320 --> 0:06:06.800
<v Speaker 1>Biden's personal account had the older blue check mark, but

0:06:06.960 --> 0:06:11.159
<v Speaker 1>not the official badge. But an hour after official badges

0:06:11.200 --> 0:06:15.159
<v Speaker 1>began to appear, they began to disappear. Meanwhile, we've already

0:06:15.200 --> 0:06:18.320
<v Speaker 1>seen folks exploit the new verification system to apparent sidate

0:06:18.560 --> 0:06:22.120
<v Speaker 1>high profile individuals and companies. For example, so In created

0:06:22.120 --> 0:06:26.400
<v Speaker 1>an account that was called Nintendo of Us you know

0:06:26.560 --> 0:06:31.000
<v Speaker 1>of us as a Nintendo America. That account has subsequently

0:06:31.000 --> 0:06:33.480
<v Speaker 1>been banned, but before it was banned and had the

0:06:33.600 --> 0:06:38.039
<v Speaker 1>verification check mark on there and uh it. The tweet

0:06:38.160 --> 0:06:40.960
<v Speaker 1>that they posted showed an image of Mario making a

0:06:42.400 --> 0:06:46.920
<v Speaker 1>famous rude hand gesture, not something Nintendo would be particularly

0:06:46.960 --> 0:06:51.520
<v Speaker 1>pleased to see. As Jason Schreier observed, quote, can't imagine

0:06:51.520 --> 0:06:54.600
<v Speaker 1>why all the advertisers are pulling out of Twitter L

0:06:54.839 --> 0:06:58.560
<v Speaker 1>m Ao end quote. Considering that Twitter took a huge

0:06:58.640 --> 0:07:01.880
<v Speaker 1>chunk out of its content ration team during the recent layoffs,

0:07:01.920 --> 0:07:04.920
<v Speaker 1>I imagine things have got to be really busy over

0:07:04.960 --> 0:07:08.400
<v Speaker 1>there as folks attempt to exploit the verification system. Behind

0:07:08.440 --> 0:07:11.280
<v Speaker 1>the scenes at Twitter, Elon Musk has made more changes

0:07:11.320 --> 0:07:15.480
<v Speaker 1>to the work environment, having now slashed headcount by around

0:07:15.800 --> 0:07:19.640
<v Speaker 1>Musk has eliminated Twitter's work from home policy and it's

0:07:20.040 --> 0:07:23.600
<v Speaker 1>days of rest policy, so the work from home policies

0:07:23.720 --> 0:07:27.280
<v Speaker 1>self explanatory. It's no surprise that Musk has shut that

0:07:27.320 --> 0:07:30.800
<v Speaker 1>down because he's had a similar stance in his other companies,

0:07:31.320 --> 0:07:34.120
<v Speaker 1>so stands the reason he would do the same at Twitter.

0:07:34.640 --> 0:07:36.920
<v Speaker 1>So in playce will have to come into the office.

0:07:37.040 --> 0:07:40.520
<v Speaker 1>They are no longer allowed to work remotely. The days

0:07:40.520 --> 0:07:43.560
<v Speaker 1>of rest policy was a benefit that would give employees

0:07:43.600 --> 0:07:46.720
<v Speaker 1>a little time off between major projects so that they

0:07:46.720 --> 0:07:51.120
<v Speaker 1>could recharge their batteries and avoid burnout. But now there

0:07:51.120 --> 0:07:53.720
<v Speaker 1>are half the people to do all the work. Not

0:07:53.760 --> 0:07:56.160
<v Speaker 1>to mention that Musk has added some projects with really

0:07:56.200 --> 0:07:59.840
<v Speaker 1>aggressive deadlines, so time off really isn't something Musk is

0:07:59.880 --> 0:08:02.120
<v Speaker 1>interested in. My guess is there are a lot of

0:08:02.160 --> 0:08:05.520
<v Speaker 1>folks over at Twitter we're dealing with a ton more

0:08:05.600 --> 0:08:09.600
<v Speaker 1>stress than they had to endure in recent years. So

0:08:10.000 --> 0:08:12.920
<v Speaker 1>my heart goes out to y'all. Things are looking grim

0:08:13.000 --> 0:08:16.320
<v Speaker 1>right now in the cryptocurrency world as numerous digital coins

0:08:16.360 --> 0:08:21.000
<v Speaker 1>take a tumble in value yet again. Bitcoin is currently

0:08:21.080 --> 0:08:24.800
<v Speaker 1>valued at around sixteen thousand, four hundred sixty bucks per coin,

0:08:24.880 --> 0:08:28.120
<v Speaker 1>and y'all, yeah, that's a lot of money. Sixteen grand,

0:08:29.000 --> 0:08:33.600
<v Speaker 1>almost sixteen and a half per bitcoin. That's expensive, but

0:08:34.040 --> 0:08:35.880
<v Speaker 1>when you think back a couple of years ago when

0:08:35.920 --> 0:08:40.480
<v Speaker 1>the currency hit around sixty thousand per coin, it is

0:08:40.600 --> 0:08:45.080
<v Speaker 1>a huge drop. Bitcoin had hit a low of fifteen thousand,

0:08:45.120 --> 0:08:48.080
<v Speaker 1>seven hundred fifty bucks yesterday, so it actually dip below

0:08:48.160 --> 0:08:51.160
<v Speaker 1>sixteen thousand for the first time in ages. That was

0:08:51.240 --> 0:08:53.360
<v Speaker 1>likely because of the next bit of news that we

0:08:53.400 --> 0:08:56.760
<v Speaker 1>have to cover, cryptocurrency exchange f t X is in

0:08:56.800 --> 0:09:00.280
<v Speaker 1>the middle of a real crisis. This require is a

0:09:00.280 --> 0:09:04.280
<v Speaker 1>little bit of background. So an entrepreneur named Sam Bankman

0:09:04.360 --> 0:09:07.280
<v Speaker 1>Freed a k A s b F that's what he

0:09:07.360 --> 0:09:11.760
<v Speaker 1>goes by. UH and Gary Wong co founded the f

0:09:11.800 --> 0:09:16.120
<v Speaker 1>t X exchange back in twenty nineteen, and an exchange

0:09:16.160 --> 0:09:19.240
<v Speaker 1>is a business that allows customers to trade cryptocurrencies for

0:09:19.280 --> 0:09:22.640
<v Speaker 1>other assets, which could include a different cryptocurrency or a

0:09:22.679 --> 0:09:28.160
<v Speaker 1>fiat currency. Similarly, you could buy into a cryptocurrency exchanging

0:09:28.400 --> 0:09:31.000
<v Speaker 1>fiat currency for a digital coin. That kind of thing.

0:09:31.080 --> 0:09:36.680
<v Speaker 1>That's what an exchange does. It handles that transaction well. Binance,

0:09:36.720 --> 0:09:40.040
<v Speaker 1>which is another cryptocurrency exchange and a huge competitor to

0:09:40.120 --> 0:09:43.080
<v Speaker 1>f t X, had a stake in f t X,

0:09:43.200 --> 0:09:47.080
<v Speaker 1>but last year Binance essentially converted its steak into f

0:09:47.240 --> 0:09:51.120
<v Speaker 1>t T, and f t T is the native cryptocurrency

0:09:51.160 --> 0:09:54.000
<v Speaker 1>on the f t X exchange, so you could buy

0:09:54.040 --> 0:09:56.439
<v Speaker 1>into f t T and then convert the f t

0:09:56.440 --> 0:10:00.000
<v Speaker 1>T into other stuff like bitcoin or whatever. As cryptome

0:10:00.000 --> 0:10:05.560
<v Speaker 1>markets have encountered rough waters, SPF, through his trading firm,

0:10:05.600 --> 0:10:09.160
<v Speaker 1>Alameda Research, began to save or at least attempt to

0:10:09.240 --> 0:10:12.680
<v Speaker 1>save struggling crypto firms that were on the verge of

0:10:12.720 --> 0:10:17.240
<v Speaker 1>collapse and that may have overextended SPF. Then you flash

0:10:17.280 --> 0:10:21.280
<v Speaker 1>forward to this week when Binance CEO and sometimes are

0:10:21.520 --> 0:10:26.040
<v Speaker 1>nemesis to SPF, Chong Peng Shao said that the company

0:10:26.160 --> 0:10:29.200
<v Speaker 1>was going to cash out of its stock of f

0:10:29.320 --> 0:10:34.360
<v Speaker 1>t T. Now, this would mean that the typically low

0:10:34.480 --> 0:10:39.360
<v Speaker 1>trading market for ft T would suddenly get flooded by

0:10:39.360 --> 0:10:44.560
<v Speaker 1>Binances vault of FTT currency once they unloaded their share,

0:10:44.840 --> 0:10:47.560
<v Speaker 1>that in turn would drive down the value of f

0:10:47.720 --> 0:10:50.480
<v Speaker 1>t T. Right, if you flood a market with currency,

0:10:50.520 --> 0:10:53.800
<v Speaker 1>then the currency becomes devalued. So then you had a

0:10:53.800 --> 0:10:55.920
<v Speaker 1>bunch of folks wanting to cash out of their FTT

0:10:56.160 --> 0:10:58.840
<v Speaker 1>because they don't want to see their currency lose tons

0:10:58.880 --> 0:11:02.319
<v Speaker 1>of value. That that's investment for them, and it essentially

0:11:02.320 --> 0:11:05.000
<v Speaker 1>became a run on the bank, and suddenly fd X

0:11:05.040 --> 0:11:08.320
<v Speaker 1>found itself in a liquidity crunch. Finance at one point

0:11:08.320 --> 0:11:11.480
<v Speaker 1>indicate it would actually acquire fd X, which would at

0:11:11.520 --> 0:11:13.520
<v Speaker 1>least help settle things down, but it would be a

0:11:13.520 --> 0:11:16.880
<v Speaker 1>real power move because SPF and Chong Peng had been

0:11:16.920 --> 0:11:21.320
<v Speaker 1>feuding extensively in the past. But then Binance backdown of

0:11:21.360 --> 0:11:24.520
<v Speaker 1>the agreement, which was, you know, never formalized, so no

0:11:24.600 --> 0:11:28.160
<v Speaker 1>problem there, and said that fd x is financial situation

0:11:28.280 --> 0:11:32.319
<v Speaker 1>was way worse than first suspected. Now SBF and f

0:11:32.480 --> 0:11:35.240
<v Speaker 1>d X are searching for another lifeline, and meanwhile the

0:11:35.240 --> 0:11:38.679
<v Speaker 1>crypto market in general is taking another hit. Seeing a

0:11:38.720 --> 0:11:41.560
<v Speaker 1>major exchange in trouble tends to have a ripple effect

0:11:41.559 --> 0:11:45.360
<v Speaker 1>on people's confidence in the overall market, so crypto continues

0:11:45.400 --> 0:11:47.560
<v Speaker 1>to have a rough time of it as it has

0:11:47.640 --> 0:11:52.560
<v Speaker 1>for a while now. Market Watch reports that TikTok has

0:11:52.720 --> 0:11:57.080
<v Speaker 1>secret scores assigned to influencers. These scores reflect how well

0:11:57.600 --> 0:12:02.760
<v Speaker 1>content creators are at from products or showing enthusiasm for sponsors,

0:12:02.760 --> 0:12:04.200
<v Speaker 1>that kind of thing, So it's kind of like a

0:12:04.240 --> 0:12:08.120
<v Speaker 1>secret system to evaluate how likely a given content creator

0:12:08.200 --> 0:12:10.600
<v Speaker 1>is to play ball and to do it well. I

0:12:10.640 --> 0:12:14.600
<v Speaker 1>suppose presumably creators who have higher scores will get more opportunities,

0:12:14.640 --> 0:12:18.040
<v Speaker 1>perhaps with more prestigious brands. I'd like to think that

0:12:18.080 --> 0:12:21.920
<v Speaker 1>the score indicates just how influential are you, oh, influencer,

0:12:22.640 --> 0:12:25.840
<v Speaker 1>but it does look at things like diligence and cooperation,

0:12:25.880 --> 0:12:28.360
<v Speaker 1>which is just their way of saying how frequently will

0:12:28.400 --> 0:12:30.640
<v Speaker 1>they post and do they put up a fuss about it.

0:12:31.240 --> 0:12:34.040
<v Speaker 1>The scoring system apparently doesn't really apply here in the

0:12:34.120 --> 0:12:38.080
<v Speaker 1>United States because TikTok is really looking to leverage the

0:12:38.120 --> 0:12:41.160
<v Speaker 1>social network into a shopping experience, and those efforts have

0:12:41.400 --> 0:12:44.040
<v Speaker 1>not really taken off here in the US. It has

0:12:44.320 --> 0:12:46.080
<v Speaker 1>in other parts of the world, so in places like

0:12:46.120 --> 0:12:49.880
<v Speaker 1>Southeast Asia, the system appears to be fully deployed. According

0:12:49.880 --> 0:12:52.680
<v Speaker 1>to market Watch, TikTok has been holding discussions in the

0:12:52.760 --> 0:12:55.560
<v Speaker 1>UK about using the scores to partner with creators, and

0:12:55.559 --> 0:12:57.960
<v Speaker 1>I want to be clear, I don't necessarily think this

0:12:58.040 --> 0:13:01.360
<v Speaker 1>is a bad system. Uh. Some brands might have a

0:13:01.360 --> 0:13:04.160
<v Speaker 1>particular influencer in mind when they want to engage in

0:13:04.160 --> 0:13:08.120
<v Speaker 1>a in a TikTok campaign, but others might not have

0:13:08.160 --> 0:13:11.040
<v Speaker 1>any idea of who they would want to represent. Their brand,

0:13:11.480 --> 0:13:13.560
<v Speaker 1>and having a scoring system could be a quick way

0:13:13.559 --> 0:13:17.600
<v Speaker 1>to at least get eyeballs in front of particular influencers

0:13:17.640 --> 0:13:20.880
<v Speaker 1>to get an idea who's a good match. It is

0:13:20.920 --> 0:13:24.320
<v Speaker 1>a little creepy because TikTok's parent company, byte Dance, is

0:13:24.360 --> 0:13:27.560
<v Speaker 1>in China, and China has been developing a social credit

0:13:27.679 --> 0:13:32.240
<v Speaker 1>score policy that potentially could see citizens receive social scores

0:13:32.240 --> 0:13:36.480
<v Speaker 1>that could impact everything from job prospects to travel bands. Now,

0:13:37.000 --> 0:13:40.439
<v Speaker 1>so far, the social credit program has really applied to businesses,

0:13:40.480 --> 0:13:43.360
<v Speaker 1>not individuals, and various regions in China have rolled out

0:13:43.360 --> 0:13:45.520
<v Speaker 1>their own version of this, so it's not like there's

0:13:45.559 --> 0:13:51.000
<v Speaker 1>a unified national program in place. So I don't want

0:13:51.040 --> 0:13:55.360
<v Speaker 1>to pay a dystopian picture the way often we will

0:13:55.440 --> 0:13:57.880
<v Speaker 1>often hear when we talk about the social credit score.

0:13:58.400 --> 0:14:02.240
<v Speaker 1>But um, yeah, it's possible that that could change in

0:14:02.280 --> 0:14:06.000
<v Speaker 1>the future. Okay, we have more to talk about, but

0:14:06.080 --> 0:14:18.640
<v Speaker 1>before we get to that, let's take a quick break. Okay,

0:14:18.640 --> 0:14:22.720
<v Speaker 1>we're back. So Variety, which mentally is an outlet that

0:14:22.760 --> 0:14:26.240
<v Speaker 1>I do not reference often on this show, reported that,

0:14:26.480 --> 0:14:30.400
<v Speaker 1>according to a YouTube representative, eighty million people are now

0:14:30.440 --> 0:14:35.080
<v Speaker 1>subscribed to YouTube's music and premium services and that's up

0:14:35.120 --> 0:14:39.600
<v Speaker 1>from fifty million last year. Subscribers are able to watch

0:14:39.760 --> 0:14:43.800
<v Speaker 1>videos ad free, though obviously any baked in ads like

0:14:43.840 --> 0:14:47.280
<v Speaker 1>a host red sponsorship within a video will still be there.

0:14:47.800 --> 0:14:49.800
<v Speaker 1>They can also do stuff like play videos in the

0:14:49.840 --> 0:14:54.280
<v Speaker 1>background and download for offline viewing, so you know there's

0:14:54.320 --> 0:14:57.520
<v Speaker 1>some neat things there. The background video means that you

0:14:57.560 --> 0:14:59.960
<v Speaker 1>could say, launch a video on your phone and then

0:15:00.040 --> 0:15:02.200
<v Speaker 1>set your phone screen to sleep mode and still be

0:15:02.280 --> 0:15:04.160
<v Speaker 1>able to listen to the video, which comes in handy

0:15:04.160 --> 0:15:06.320
<v Speaker 1>for me because I like listening to a S m

0:15:06.480 --> 0:15:08.760
<v Speaker 1>R as it go to sleep, and I would prefer

0:15:08.840 --> 0:15:11.760
<v Speaker 1>the screen not stay lit up so that way it's

0:15:11.760 --> 0:15:15.840
<v Speaker 1>not distracting me before I can not off. Anyway, While

0:15:15.880 --> 0:15:19.000
<v Speaker 1>a thirty million subscriber increases great the amount of revenue

0:15:19.000 --> 0:15:22.040
<v Speaker 1>those subscriptions generate, which is somewhere around eleven billion per

0:15:22.120 --> 0:15:25.800
<v Speaker 1>year according to Android Headlines, it's still less than half

0:15:25.840 --> 0:15:29.720
<v Speaker 1>of what the company's reported revenue is. It's understandable why

0:15:29.720 --> 0:15:32.760
<v Speaker 1>YouTube would push for folks to subscribe. A subscription is

0:15:32.800 --> 0:15:38.120
<v Speaker 1>reliable revenue month over month. The advertising market fluctuates, particularly

0:15:38.160 --> 0:15:41.520
<v Speaker 1>in times of economic uncertainty, as companies start to curb

0:15:41.640 --> 0:15:45.200
<v Speaker 1>spending Plus, YouTube doesn't have to worry so much about

0:15:45.280 --> 0:15:47.880
<v Speaker 1>pairing ads with a video that the advertiser would object

0:15:47.880 --> 0:15:51.760
<v Speaker 1>to if you're subscribed, right, so they don't have to

0:15:51.760 --> 0:15:54.440
<v Speaker 1>worry about the kinds of situations that have happened in

0:15:54.440 --> 0:15:56.720
<v Speaker 1>the past. You know, there's nothing like a brand getting

0:15:56.720 --> 0:15:58.600
<v Speaker 1>word that one of their ads has gone up on

0:15:58.640 --> 0:16:01.720
<v Speaker 1>a video that, for example, includes hate speech or some

0:16:01.880 --> 0:16:06.280
<v Speaker 1>other objectionable content that causes a big problem. So if

0:16:06.320 --> 0:16:09.920
<v Speaker 1>you can push people over to subscribe and then rely

0:16:10.200 --> 0:16:15.880
<v Speaker 1>less and less on ads, then you remove that impediment. Anyway,

0:16:15.920 --> 0:16:18.200
<v Speaker 1>It'll be interesting to see if YouTube can continue to

0:16:18.200 --> 0:16:21.520
<v Speaker 1>convince people to subscribe for a service when they can

0:16:21.560 --> 0:16:25.240
<v Speaker 1>watch the content for free otherwise. I mean, eighty million subscribers,

0:16:25.240 --> 0:16:29.520
<v Speaker 1>that's a lot, but YouTube has more than two billion

0:16:29.680 --> 0:16:35.320
<v Speaker 1>active users, so it's it's not even a blink of

0:16:35.360 --> 0:16:38.600
<v Speaker 1>the eye for the overall number. Also, I feel like,

0:16:38.640 --> 0:16:40.680
<v Speaker 1>in the interest of full disclosure, I should say, yeah,

0:16:40.760 --> 0:16:44.120
<v Speaker 1>I am a subscriber to YouTube stuff. I subscribed actually

0:16:44.200 --> 0:16:48.840
<v Speaker 1>to an earlier Google product that ultimately, surprise, surprise, got

0:16:48.880 --> 0:16:52.840
<v Speaker 1>shut down and Google kind of rolled my subscription over

0:16:52.920 --> 0:16:55.400
<v Speaker 1>to YouTube, and I liked it. So I just stuck

0:16:55.440 --> 0:16:59.600
<v Speaker 1>with it. Last month, Australian health insurance company Meta Bank

0:16:59.720 --> 0:17:03.160
<v Speaker 1>was hit with a cyber attack that included a massive

0:17:03.240 --> 0:17:06.680
<v Speaker 1>data breach. Now a hacker or a group of hackers

0:17:06.680 --> 0:17:10.000
<v Speaker 1>are demanding extortion payments or else they're going to release

0:17:10.119 --> 0:17:14.200
<v Speaker 1>private medical information belonging to Meta banks clients. The hacker

0:17:14.280 --> 0:17:17.800
<v Speaker 1>demands that Meta Bank handover a dollar for every customer affected,

0:17:17.840 --> 0:17:22.000
<v Speaker 1>and that would be nine point seven million dollars. And

0:17:22.119 --> 0:17:26.000
<v Speaker 1>the hacker has already released what it calls a naughty list,

0:17:26.400 --> 0:17:30.520
<v Speaker 1>which is beyond messed up. When you hear about the

0:17:30.600 --> 0:17:33.680
<v Speaker 1>kinds of folks that are on this list, it's a

0:17:34.800 --> 0:17:37.679
<v Speaker 1>it's able list, to say the least. The list includes

0:17:37.760 --> 0:17:40.320
<v Speaker 1>names of customers who, according to the hacker, have sought

0:17:40.400 --> 0:17:45.520
<v Speaker 1>treatments that range from mental health sessions, to drug addiction services,

0:17:45.560 --> 0:17:50.680
<v Speaker 1>to HIV treatment to abortions. Meta Bank so far has

0:17:50.720 --> 0:17:54.200
<v Speaker 1>refused to pay the hacker, which I'm sure was a

0:17:54.320 --> 0:17:59.919
<v Speaker 1>really difficult decision based upon the nature of this information,

0:18:00.359 --> 0:18:03.360
<v Speaker 1>but in my opinion, it is also the right decision

0:18:03.440 --> 0:18:08.520
<v Speaker 1>to make. Paying cybercriminals simply reinforces that their activities are profitable,

0:18:09.280 --> 0:18:11.680
<v Speaker 1>and it also doesn't guarantee that you'll actually see an

0:18:11.760 --> 0:18:15.440
<v Speaker 1>end to the problems. You might pay and still be tormented.

0:18:16.000 --> 0:18:18.160
<v Speaker 1>But Meta Bank has had to reach out to customers

0:18:18.160 --> 0:18:22.080
<v Speaker 1>to apologize for the issue. And it is a difficult

0:18:22.119 --> 0:18:25.880
<v Speaker 1>fact that innocent people are facing the prospect of public

0:18:25.960 --> 0:18:29.560
<v Speaker 1>shaming for stuff that frankly is no one's business. I

0:18:29.640 --> 0:18:32.920
<v Speaker 1>agree with Australia's Home Affairs Minister Claire O'Neill, who is

0:18:32.960 --> 0:18:38.159
<v Speaker 1>called the hackers quote scummy criminals end quote sounds legit

0:18:38.200 --> 0:18:41.960
<v Speaker 1>to me. If you're on Cloud nine, you better get off.

0:18:42.600 --> 0:18:45.800
<v Speaker 1>In this context, Cloud nine refers to a malicious Google

0:18:45.880 --> 0:18:49.000
<v Speaker 1>Chrome extension that does a lot of nasty stuff like

0:18:49.359 --> 0:18:53.359
<v Speaker 1>key logging. That's when a program that is on your

0:18:53.359 --> 0:18:57.800
<v Speaker 1>computer and it records or logs every key stroke you make.

0:18:58.520 --> 0:19:02.200
<v Speaker 1>Hackers use key loggers to get information like log in credentials,

0:19:02.200 --> 0:19:06.400
<v Speaker 1>credit card numbers, bank account information, etcetera. It's really really

0:19:06.440 --> 0:19:09.600
<v Speaker 1>bad news. Cloud nine can also access your copy and

0:19:09.640 --> 0:19:12.480
<v Speaker 1>paste data. So maybe you don't type in your password,

0:19:12.480 --> 0:19:16.040
<v Speaker 1>maybe you copy it over from like a password vault. Well,

0:19:16.080 --> 0:19:18.600
<v Speaker 1>this tool nullifies that approach as well, or at least

0:19:18.920 --> 0:19:21.399
<v Speaker 1>makes it just as risky. It can also direct your

0:19:21.440 --> 0:19:25.520
<v Speaker 1>computer to mine for cryptocurrencies, so an infected system could

0:19:25.560 --> 0:19:28.280
<v Speaker 1>join a larger bought net dedicated to mining for bitcoin

0:19:28.359 --> 0:19:31.800
<v Speaker 1>or whatever, or you know, more likely some lower value

0:19:31.800 --> 0:19:36.200
<v Speaker 1>crypto because bitcoin still requires some pretty hefty equipment and

0:19:36.280 --> 0:19:40.520
<v Speaker 1>it can allow hackers to remotely execute code on your machine.

0:19:40.720 --> 0:19:43.680
<v Speaker 1>So they could potentially use Cloud nine to run some

0:19:43.800 --> 0:19:46.919
<v Speaker 1>other form of malicious software on an infected machine. So

0:19:46.960 --> 0:19:51.720
<v Speaker 1>that's bad news. Now here is the good news. According

0:19:51.720 --> 0:19:57.439
<v Speaker 1>to zimperium z Labs, which published a report about this extension,

0:19:58.200 --> 0:20:03.600
<v Speaker 1>you cannot find Cloud nine in the official Chrome extension store. Instead,

0:20:04.000 --> 0:20:07.240
<v Speaker 1>folks who are trying to infect computers are using other means,

0:20:07.280 --> 0:20:10.280
<v Speaker 1>such as disguising Cloud nine as a supposed update to

0:20:10.440 --> 0:20:13.320
<v Speaker 1>Adobe Flash and then including the link to this quote

0:20:13.359 --> 0:20:16.920
<v Speaker 1>unquote update on sites that claim to have some form

0:20:16.960 --> 0:20:19.480
<v Speaker 1>of content on them that you might want to see.

0:20:19.760 --> 0:20:23.040
<v Speaker 1>So a person looking for this particular type of content,

0:20:23.119 --> 0:20:29.359
<v Speaker 1>which now is not exclusively the domain of adult video,

0:20:29.520 --> 0:20:33.520
<v Speaker 1>but frequently falls in that category, they end up seeing

0:20:33.520 --> 0:20:35.520
<v Speaker 1>a little window and says, hey, you can't view this

0:20:35.560 --> 0:20:37.760
<v Speaker 1>because you're Flash players out of date, So just to

0:20:37.960 --> 0:20:40.320
<v Speaker 1>click here and download this update and we'll get you

0:20:40.359 --> 0:20:43.240
<v Speaker 1>all set. Except it's not really an update to a

0:20:43.320 --> 0:20:47.320
<v Speaker 1>video player. It is this malicious browser extension, which, once installed,

0:20:48.080 --> 0:20:50.280
<v Speaker 1>starts logging all those key strokes. Now, this is a

0:20:50.280 --> 0:20:52.560
<v Speaker 1>big reason why folks need to be careful before they

0:20:52.600 --> 0:20:56.879
<v Speaker 1>install stuff outside of official stores. Like even in official

0:20:56.920 --> 0:21:01.040
<v Speaker 1>stores can be tricky. Occasionally stuff will slip in without

0:21:01.560 --> 0:21:04.600
<v Speaker 1>the powers that be noticing, but definitely if you're going

0:21:04.640 --> 0:21:08.320
<v Speaker 1>outside official stores, which is something Chrome allows, it's called

0:21:08.440 --> 0:21:12.880
<v Speaker 1>sideloading Chrome. Essentially, what Google is saying is we we

0:21:13.280 --> 0:21:16.359
<v Speaker 1>expect you're an adult and you can make your own decisions,

0:21:16.760 --> 0:21:19.159
<v Speaker 1>so just make good ones or else you're gonna regret it,

0:21:19.320 --> 0:21:22.040
<v Speaker 1>whereas Apple says, we don't think you're adults, so we

0:21:22.080 --> 0:21:26.560
<v Speaker 1>don't let you make decisions. It's putting words into Apple's mouth,

0:21:26.640 --> 0:21:28.720
<v Speaker 1>but it's kind of how it comes across to me.

0:21:28.840 --> 0:21:31.840
<v Speaker 1>Sometimes either way, you have to be really careful, and

0:21:31.880 --> 0:21:34.119
<v Speaker 1>if you're not, then you can end up with something

0:21:34.200 --> 0:21:37.560
<v Speaker 1>like Cloud nine installed on your browser and then next

0:21:37.600 --> 0:21:41.360
<v Speaker 1>thing you know, you've got this enormous headache on your

0:21:41.359 --> 0:21:44.000
<v Speaker 1>hands or I guess not on your hands. It's in

0:21:44.040 --> 0:21:47.480
<v Speaker 1>your head about the fact that you've got this um

0:21:47.680 --> 0:21:51.720
<v Speaker 1>browser that's logging all your key strokes. So yeah, just

0:21:51.880 --> 0:21:55.560
<v Speaker 1>make sure you're being super careful when you're using your computer,

0:21:56.240 --> 0:21:58.400
<v Speaker 1>make sure you know what you're getting into when you're

0:21:58.440 --> 0:22:01.520
<v Speaker 1>side loading. And it's just good to be aware that

0:22:01.560 --> 0:22:03.680
<v Speaker 1>these kind of tools are out there because it might

0:22:03.720 --> 0:22:07.080
<v Speaker 1>make you think twice before you download something and install

0:22:07.160 --> 0:22:11.320
<v Speaker 1>it without really looking into it further. IBM s Asprey

0:22:11.480 --> 0:22:15.560
<v Speaker 1>is ready to take Flight, which is a a pun

0:22:15.600 --> 0:22:18.320
<v Speaker 1>that doesn't really work because it's not an aircraft. Asprey

0:22:18.400 --> 0:22:22.480
<v Speaker 1>in this case is at one of IBMS quantum processors.

0:22:22.920 --> 0:22:25.679
<v Speaker 1>The company has been using bird names for their quantum

0:22:25.720 --> 0:22:27.560
<v Speaker 1>processors for a while. I think the one that came

0:22:27.560 --> 0:22:31.399
<v Speaker 1>out before this one was called Eagle and Osprey is

0:22:31.440 --> 0:22:35.879
<v Speaker 1>a quantum processor that has four hundred thirty three cubits

0:22:36.560 --> 0:22:40.159
<v Speaker 1>q U b I T, so the cubit for quantum

0:22:40.200 --> 0:22:45.120
<v Speaker 1>computers is the basic unit of information. With a traditional computer,

0:22:45.520 --> 0:22:49.679
<v Speaker 1>your basic unit of information is the bit, the binary digit,

0:22:50.040 --> 0:22:52.600
<v Speaker 1>which can by be either a zero or a one.

0:22:52.760 --> 0:22:54.960
<v Speaker 1>It cannot be both. It's one or the other, so

0:22:55.000 --> 0:22:58.120
<v Speaker 1>it's off or on that kind of thing. But a cubit,

0:22:59.119 --> 0:23:03.960
<v Speaker 1>because of superposition, can essentially be both zero and one

0:23:04.000 --> 0:23:07.200
<v Speaker 1>at the same time and technically all values in between.

0:23:07.960 --> 0:23:10.800
<v Speaker 1>This is because of a quantum effect, and it's not

0:23:10.880 --> 0:23:13.960
<v Speaker 1>something you you observe in classical systems, but it's possible

0:23:13.960 --> 0:23:17.119
<v Speaker 1>in a quantum system. So if you have enough cubits

0:23:17.480 --> 0:23:20.199
<v Speaker 1>and you have the right kind of algorithm designed to

0:23:20.320 --> 0:23:24.440
<v Speaker 1>run on a quantum machine, you can potentially solve extremely

0:23:24.760 --> 0:23:29.600
<v Speaker 1>difficult computational problems from a classical computing perspective. That is,

0:23:29.680 --> 0:23:33.880
<v Speaker 1>and it's only a subset of very difficult computational problems.

0:23:33.920 --> 0:23:38.600
<v Speaker 1>It's not every computational problem, but for a subset. For example,

0:23:38.920 --> 0:23:41.800
<v Speaker 1>if you wanted to try and decrypt something and you

0:23:41.840 --> 0:23:46.520
<v Speaker 1>didn't know the two extremely large prime numbers that were

0:23:46.600 --> 0:23:50.679
<v Speaker 1>used to multiply together and get a certain product, well,

0:23:51.000 --> 0:23:55.680
<v Speaker 1>a quantum computer could, in theory solve that problem much much,

0:23:55.800 --> 0:23:59.000
<v Speaker 1>much more quickly than a classical computer for a really

0:23:59.080 --> 0:24:02.199
<v Speaker 1>large number. Classical computer might take more time than the

0:24:02.320 --> 0:24:05.240
<v Speaker 1>universe has been around, whereas with a quantum computer you

0:24:05.320 --> 0:24:07.600
<v Speaker 1>might be talking about, I don't know, a few minutes,

0:24:07.640 --> 0:24:11.840
<v Speaker 1>depending upon again how sophisticated that quantum computer is. We

0:24:11.920 --> 0:24:15.719
<v Speaker 1>are not at that level yet. That's where we're headed towards,

0:24:16.000 --> 0:24:19.679
<v Speaker 1>but we're not there now. Four three cubits is a

0:24:19.720 --> 0:24:22.960
<v Speaker 1>brand new record. That's an enormous number of cubits. When

0:24:23.000 --> 0:24:26.080
<v Speaker 1>I first started talking about quantum systems, when I when

0:24:26.119 --> 0:24:29.200
<v Speaker 1>I first learned that they were even a thing, we

0:24:29.200 --> 0:24:32.720
<v Speaker 1>were working our way towards building a system that had

0:24:32.760 --> 0:24:37.720
<v Speaker 1>just forty cubits. So we've already gone ten times that

0:24:37.840 --> 0:24:40.880
<v Speaker 1>number since I started talking about quantum computers a few

0:24:40.920 --> 0:24:44.879
<v Speaker 1>years ago. And i VM expects to release a quantum

0:24:44.920 --> 0:24:49.840
<v Speaker 1>processor with one thousand cubits on it next year. That's

0:24:49.880 --> 0:24:54.600
<v Speaker 1>a level of of doubling that that is astonishing. That

0:24:54.640 --> 0:24:59.760
<v Speaker 1>actually outpaces Moore's law, which is pretty incredible. Now, we

0:25:00.000 --> 0:25:01.720
<v Speaker 1>still have a lot of other things that have to

0:25:01.720 --> 0:25:05.000
<v Speaker 1>fall into place before quantum computer has become the new

0:25:05.840 --> 0:25:10.840
<v Speaker 1>UH defining factor for how we encrypt things moving forward,

0:25:11.119 --> 0:25:13.520
<v Speaker 1>because obviously one of the things that we worry about

0:25:13.520 --> 0:25:16.840
<v Speaker 1>with quantum computers is that encryption, the current methods of

0:25:16.920 --> 0:25:20.560
<v Speaker 1>encryption that we rely upon, will be nullified, and that

0:25:21.080 --> 0:25:24.240
<v Speaker 1>everything from that point forward could be decrypted assuming it

0:25:24.280 --> 0:25:28.440
<v Speaker 1>was using this traditional form of encryption. But to do that,

0:25:28.520 --> 0:25:31.280
<v Speaker 1>you have to have not just a most powerful computer

0:25:31.359 --> 0:25:33.480
<v Speaker 1>system that can do it, but you also have to

0:25:33.560 --> 0:25:37.040
<v Speaker 1>have the algorithm, and you have to have a way

0:25:37.080 --> 0:25:41.760
<v Speaker 1>of reducing error rate so that you're not uncertain of

0:25:41.800 --> 0:25:44.760
<v Speaker 1>the answer. And we haven't gotten there yet, but this

0:25:44.840 --> 0:25:47.880
<v Speaker 1>is an incredible achievement and I'm really excited to see

0:25:47.920 --> 0:25:51.560
<v Speaker 1>what happens next. Speaking of what happens next, let's take

0:25:51.560 --> 0:26:05.520
<v Speaker 1>another quick break. Okay, we're back and interesting full disclosure

0:26:05.560 --> 0:26:08.920
<v Speaker 1>of y'all, I was at a training session for most

0:26:08.920 --> 0:26:11.880
<v Speaker 1>of the day today, and so this bit of news

0:26:11.920 --> 0:26:15.520
<v Speaker 1>has actually coming out since I started writing the episode,

0:26:15.560 --> 0:26:18.199
<v Speaker 1>which was early, early, early in the morning. And so

0:26:18.240 --> 0:26:20.160
<v Speaker 1>we've got some updates that I want to talk about,

0:26:20.200 --> 0:26:23.280
<v Speaker 1>which means, unfortunately that I have to talk about Twitter

0:26:23.440 --> 0:26:26.560
<v Speaker 1>some more, which I didn't plan on doing. But there

0:26:26.600 --> 0:26:31.000
<v Speaker 1>are some updates. One thing is that as of right

0:26:31.040 --> 0:26:36.640
<v Speaker 1>now over on Twitter, any any account that was made

0:26:36.760 --> 0:26:40.920
<v Speaker 1>after Wednesday, November nine, will not be able to subscribe

0:26:40.960 --> 0:26:46.320
<v Speaker 1>to Twitter Blue for now, because there was this rash

0:26:46.560 --> 0:26:51.960
<v Speaker 1>of new accounts that we're seeking verification and then impersonating

0:26:52.480 --> 0:26:56.239
<v Speaker 1>notable people and brands, and so Twitter had to do

0:26:56.320 --> 0:27:00.000
<v Speaker 1>something about that, and the reaction was all right, well,

0:27:00.040 --> 0:27:04.040
<v Speaker 1>it's locked down any any new accounts from being able

0:27:04.080 --> 0:27:07.879
<v Speaker 1>to do this right all the Gate. So the question

0:27:07.960 --> 0:27:11.159
<v Speaker 1>is when will those accounts be allowed to seek Twitter

0:27:11.320 --> 0:27:15.119
<v Speaker 1>Blue verification. We don't know yet. I don't think anyone

0:27:15.200 --> 0:27:17.600
<v Speaker 1>at Twitter knows yet. I think that this is all

0:27:17.720 --> 0:27:25.800
<v Speaker 1>very reactionary, understandably so, because that flood of impersonations obviously

0:27:26.000 --> 0:27:30.880
<v Speaker 1>posed a real threat to Twitter's revenue, as advertisers do

0:27:31.000 --> 0:27:36.760
<v Speaker 1>not want to see fake accounts claiming to be them

0:27:36.800 --> 0:27:39.440
<v Speaker 1>with a little check Martin next to them doing things

0:27:39.520 --> 0:27:43.000
<v Speaker 1>like posting a picture of Mario flipping off everybody on Twitter.

0:27:43.520 --> 0:27:47.560
<v Speaker 1>So yeah, not a surprise that this has happened. It

0:27:47.680 --> 0:27:51.720
<v Speaker 1>does really paint a picture of how quickly things are

0:27:51.760 --> 0:27:56.840
<v Speaker 1>developing at Twitter, how chaotic things must be over there. Also,

0:27:57.760 --> 0:27:59.919
<v Speaker 1>I know, I'm pretty sure every single one of you

0:28:00.040 --> 0:28:03.560
<v Speaker 1>out there, I feel certain, I'll say this, every single

0:28:03.600 --> 0:28:06.560
<v Speaker 1>one of you out there would have predicted that this

0:28:06.600 --> 0:28:10.240
<v Speaker 1>would have happened, right that if you have a verification

0:28:10.280 --> 0:28:13.760
<v Speaker 1>system that the only barrier of entry is having eight

0:28:13.760 --> 0:28:16.880
<v Speaker 1>dollars a month to spend to have it, you were

0:28:17.080 --> 0:28:19.400
<v Speaker 1>ultimately going to see a lot of people, a lot

0:28:19.400 --> 0:28:22.480
<v Speaker 1>of troublemakers take advantage of that, whether it was going

0:28:22.520 --> 0:28:24.800
<v Speaker 1>to be a ton or you know, just a few

0:28:24.840 --> 0:28:27.320
<v Speaker 1>thousand or whatever it may be. You knew that was

0:28:27.320 --> 0:28:29.520
<v Speaker 1>going to happen, right like I knew that was going

0:28:29.560 --> 0:28:33.240
<v Speaker 1>to happen. It's shocking to me that Elon Musk didn't

0:28:33.280 --> 0:28:36.520
<v Speaker 1>think that was going to happen, or perhaps didn't care

0:28:36.640 --> 0:28:39.880
<v Speaker 1>or didn't understand what the consequences of that would be

0:28:40.320 --> 0:28:46.280
<v Speaker 1>on Twitter's reputation and ability to attract advertisers. So yeah,

0:28:46.320 --> 0:28:50.480
<v Speaker 1>this is at best a temporary solution to heading off

0:28:50.560 --> 0:28:56.560
<v Speaker 1>future rushes to to create impersonation accounts, And uh, I

0:28:56.600 --> 0:29:00.520
<v Speaker 1>think that's wise, But I honestly you think that the

0:29:00.560 --> 0:29:03.080
<v Speaker 1>whole eight dollar verification thing was a bad idea to

0:29:03.120 --> 0:29:04.920
<v Speaker 1>start with. It may very will be that we'll see

0:29:04.960 --> 0:29:09.920
<v Speaker 1>them reverse that decision that the Twitter Blue subscription will

0:29:10.000 --> 0:29:12.680
<v Speaker 1>no longer include the check mark, or maybe it will

0:29:12.720 --> 0:29:18.440
<v Speaker 1>include some other kind of badge to differentiate a Twitter

0:29:18.520 --> 0:29:22.600
<v Speaker 1>Blue subscriber from a normal Twitter user. But yeah, that

0:29:22.680 --> 0:29:26.360
<v Speaker 1>check mark not a great idea because it just set

0:29:26.440 --> 0:29:30.440
<v Speaker 1>the stage for that kind of abuse. So that's update

0:29:30.600 --> 0:29:35.840
<v Speaker 1>number one. In update number two, the US Treasury Department

0:29:36.200 --> 0:29:41.720
<v Speaker 1>Financial Crimes Enforcement Network has UH posted a filing that

0:29:41.760 --> 0:29:47.440
<v Speaker 1>shows that Twitter has applied to become a money service business. Now,

0:29:47.480 --> 0:29:49.960
<v Speaker 1>those of you all who know Elon Musk's history know

0:29:50.200 --> 0:29:54.040
<v Speaker 1>that he was part of x which would eventually become PayPal,

0:29:54.840 --> 0:29:57.640
<v Speaker 1>and also that he has talked in the past about

0:29:57.920 --> 0:30:02.640
<v Speaker 1>aspirations to turn Twitter into a kind of catch all

0:30:03.160 --> 0:30:06.600
<v Speaker 1>service where there would be multiple things you could do

0:30:06.640 --> 0:30:09.120
<v Speaker 1>on it, not just send out a tweet, you know,

0:30:09.200 --> 0:30:11.640
<v Speaker 1>talking about what you had for breakfast, like we used

0:30:11.640 --> 0:30:14.600
<v Speaker 1>to do in the old days, but to perhaps transfer

0:30:14.720 --> 0:30:20.080
<v Speaker 1>funds using Twitter. There's also been some speculation that this

0:30:20.200 --> 0:30:23.720
<v Speaker 1>might mean that Twitter will have some form of of

0:30:23.920 --> 0:30:29.400
<v Speaker 1>relationship with cryptocurrency, but honestly, I don't know if that

0:30:29.640 --> 0:30:32.480
<v Speaker 1>is actually the case. We do know, obviously, Elon Musk

0:30:32.520 --> 0:30:35.200
<v Speaker 1>has been interested in cryptocurrency. There was a while where

0:30:35.480 --> 0:30:40.880
<v Speaker 1>Tesla would accept bitcoin for payment for for a new

0:30:40.960 --> 0:30:49.560
<v Speaker 1>Tesla vehicle. Elon Musk famously promoted doge coin um, which

0:30:49.760 --> 0:30:53.000
<v Speaker 1>did not did not last very long. Like it it,

0:30:53.000 --> 0:30:57.160
<v Speaker 1>It pumped the doge coin value briefly, but doge coin

0:30:57.240 --> 0:31:00.320
<v Speaker 1>has since been back down to just a few sense

0:31:00.400 --> 0:31:04.880
<v Speaker 1>per coin. And uh, yeah, I don't know if this

0:31:04.920 --> 0:31:07.959
<v Speaker 1>means we're going to see Twitter get more involved in

0:31:08.000 --> 0:31:11.800
<v Speaker 1>the crypto world or not. I wouldn't be shocked if

0:31:11.840 --> 0:31:15.760
<v Speaker 1>that were the case. But certainly this is an example

0:31:16.000 --> 0:31:22.440
<v Speaker 1>of Twitter getting interested in becoming more of a um

0:31:22.760 --> 0:31:26.520
<v Speaker 1>a payment services platform, and this is the first step

0:31:26.520 --> 0:31:28.720
<v Speaker 1>to doing it, but obviously a lot more steps have

0:31:28.800 --> 0:31:33.400
<v Speaker 1>to happen before it actually comes to fruition. Next, Twitter

0:31:33.480 --> 0:31:39.560
<v Speaker 1>chief information security officer Leah Kissner leaves Twitter, so Casey

0:31:39.600 --> 0:31:44.680
<v Speaker 1>Newton was the first to report this. Uh. Kissner said

0:31:44.760 --> 0:31:47.880
<v Speaker 1>that this was a hard decision, so it appears to

0:31:47.880 --> 0:31:52.520
<v Speaker 1>be their decision to leave Twitter, not the company's, but

0:31:52.760 --> 0:31:57.040
<v Speaker 1>did not elaborate, did not explain why that decision was

0:31:57.240 --> 0:32:02.480
<v Speaker 1>arrived at I mean, obviously things are again really chaotic

0:32:02.480 --> 0:32:06.840
<v Speaker 1>at Twitter, and that many of the departments have been

0:32:07.680 --> 0:32:10.920
<v Speaker 1>decimated by the layoffs, and I would not be surprised

0:32:10.920 --> 0:32:13.440
<v Speaker 1>to learn that cybersecurity was one of those. It does

0:32:13.480 --> 0:32:16.840
<v Speaker 1>sound like a lot of a lot of divisions within

0:32:16.880 --> 0:32:21.120
<v Speaker 1>Twitter are are working under skeleton crew type situations at

0:32:21.120 --> 0:32:26.320
<v Speaker 1>this point. But yes, seeing Kissner depart is not, uh,

0:32:26.440 --> 0:32:32.640
<v Speaker 1>not something that I find very encouraging. Um it is

0:32:33.200 --> 0:32:37.240
<v Speaker 1>scary because cybersecurity is a very serious matter, and obviously

0:32:38.280 --> 0:32:44.040
<v Speaker 1>social media in general has been a target for different

0:32:44.600 --> 0:32:49.760
<v Speaker 1>agencies out there attempting to spread misinformation and disinformation, to

0:32:50.480 --> 0:32:56.840
<v Speaker 1>so discontent, to spread messages of hate, and to see

0:32:56.880 --> 0:33:02.600
<v Speaker 1>someone who had seignori in a cybersecurity department leave like

0:33:02.680 --> 0:33:10.600
<v Speaker 1>that is troubling. Hopefully Twitter is able to account for

0:33:10.640 --> 0:33:14.840
<v Speaker 1>this and be able to adapt, And I also really

0:33:14.880 --> 0:33:19.160
<v Speaker 1>hope that Kissner is able to find a new opportunity,

0:33:19.200 --> 0:33:22.280
<v Speaker 1>a new place to fit in. They indicated that they

0:33:22.320 --> 0:33:25.360
<v Speaker 1>don't have anything lined up right now. In fact, they said,

0:33:25.440 --> 0:33:28.640
<v Speaker 1>I'm looking forward to figuring out what's next, starting with

0:33:28.680 --> 0:33:35.000
<v Speaker 1>my reviews for US next Security. So that, um, that's

0:33:35.000 --> 0:33:38.400
<v Speaker 1>that's incredible, Like that, it's a it's such a big

0:33:38.440 --> 0:33:43.680
<v Speaker 1>deal for anyone to leave without having another backup plan.

0:33:43.800 --> 0:33:46.120
<v Speaker 1>That was always something that when I was in my

0:33:46.200 --> 0:33:49.680
<v Speaker 1>earlier career, I just felt I couldn't leave something unless

0:33:49.680 --> 0:33:52.240
<v Speaker 1>I had another thing lined up. So it's got to

0:33:52.320 --> 0:33:57.360
<v Speaker 1>be pretty a pretty big reason to leave a high ranking,

0:33:58.120 --> 0:34:02.000
<v Speaker 1>you know, position within a company and not have something

0:34:02.040 --> 0:34:06.120
<v Speaker 1>else right behind it. Uh, chances are Kisseners going to

0:34:06.160 --> 0:34:11.560
<v Speaker 1>find other opportunities pretty quickly. Cybersecurity is obviously important for

0:34:11.600 --> 0:34:16.480
<v Speaker 1>all companies that are in the digital age, so probably

0:34:16.480 --> 0:34:19.120
<v Speaker 1>going to be okay in the long run. But yeah,

0:34:19.400 --> 0:34:23.920
<v Speaker 1>another concerning bit of news for Twitter. What else is

0:34:24.000 --> 0:34:27.440
<v Speaker 1>do now? Twitter, of course, is not the only company

0:34:27.560 --> 0:34:30.759
<v Speaker 1>that's going through rough times. We talked about Meta being

0:34:31.160 --> 0:34:34.279
<v Speaker 1>in that same situation. Really, all the big tech companies

0:34:34.640 --> 0:34:40.520
<v Speaker 1>are looking at making cuts and finding costs savings pretty

0:34:40.600 --> 0:34:45.799
<v Speaker 1>much across the board, and Amazon is no stranger to this. Reportedly,

0:34:46.719 --> 0:34:52.200
<v Speaker 1>Amazon is considering making some cuts in their division that

0:34:52.600 --> 0:34:56.319
<v Speaker 1>involves their voice assistant tool, whose name I won't say

0:34:56.360 --> 0:34:58.640
<v Speaker 1>in case you happen to be listening on one of

0:34:58.640 --> 0:35:02.640
<v Speaker 1>those devices, but uh, it's it's a woman's name that

0:35:02.800 --> 0:35:06.400
<v Speaker 1>starts with A and it ends with A and it

0:35:06.520 --> 0:35:12.120
<v Speaker 1>has lex in the middle. Anyway, Apparently that division has

0:35:12.360 --> 0:35:16.400
<v Speaker 1>had an operating loss of more than five billion dollars

0:35:16.520 --> 0:35:20.920
<v Speaker 1>in recent years, according to the Wall Street Journal, which

0:35:21.400 --> 0:35:24.319
<v Speaker 1>that's a lot of that's a lot of money. Obviously.

0:35:24.560 --> 0:35:29.239
<v Speaker 1>It's interesting to me because the voice assistant feature was

0:35:29.320 --> 0:35:33.279
<v Speaker 1>one that just a few years ago was really being

0:35:33.320 --> 0:35:39.279
<v Speaker 1>promoted across multiple companies Amazon, Google, Apple as being a

0:35:39.400 --> 0:35:43.440
<v Speaker 1>game changing technology, a new way to interact with our

0:35:43.520 --> 0:35:48.560
<v Speaker 1>devices that removes the barriers that would otherwise exist. Being

0:35:48.600 --> 0:35:51.480
<v Speaker 1>able to speak to a computer system and have it

0:35:51.800 --> 0:35:54.120
<v Speaker 1>understand what you want and to do whatever it is

0:35:54.160 --> 0:35:56.359
<v Speaker 1>you were asking of it. That was a big deal,

0:35:56.480 --> 0:36:00.560
<v Speaker 1>Like that's like Star Trek kind of stuff. But if

0:36:00.560 --> 0:36:05.280
<v Speaker 1>it's not driving revenue, it becomes harder and harder to justify,

0:36:05.520 --> 0:36:12.520
<v Speaker 1>especially in times of economic uncertainty. So, uh, here's hoping

0:36:13.280 --> 0:36:16.960
<v Speaker 1>that there won't be too many people affected by layoffs

0:36:17.640 --> 0:36:21.719
<v Speaker 1>if there are going to be massive cuts across Amazon,

0:36:22.320 --> 0:36:26.680
<v Speaker 1>And uh yeah, I'll be really interested to see how

0:36:26.840 --> 0:36:30.839
<v Speaker 1>we go from here, Like what else are we going

0:36:30.920 --> 0:36:34.799
<v Speaker 1>to see from voice assistants or will we will those

0:36:34.840 --> 0:36:38.120
<v Speaker 1>fade away and they just won't have really made a

0:36:38.239 --> 0:36:41.480
<v Speaker 1>huge impact. I know I use a voice assistant pretty regularly,

0:36:41.560 --> 0:36:43.680
<v Speaker 1>but I do it to do like three different things,

0:36:44.239 --> 0:36:46.880
<v Speaker 1>and it's the same three things pretty much every day,

0:36:46.960 --> 0:36:52.279
<v Speaker 1>and that's it. So arguably I'm not really making good

0:36:52.400 --> 0:36:55.280
<v Speaker 1>use of the voice assistant feature. And maybe I wouldn't

0:36:55.320 --> 0:36:57.520
<v Speaker 1>even notice if it were gone, except then I'd have

0:36:57.600 --> 0:36:59.560
<v Speaker 1>to figure out how to turn my lights on and off.

0:37:02.280 --> 0:37:03.719
<v Speaker 1>Used to be a time where I knew how to

0:37:03.760 --> 0:37:08.280
<v Speaker 1>do that. I guess there's that switch on the wall. Anyway.

0:37:08.680 --> 0:37:11.560
<v Speaker 1>Last little bit of news that I have this is

0:37:11.600 --> 0:37:14.600
<v Speaker 1>another update that came out while I was in training.

0:37:15.320 --> 0:37:18.160
<v Speaker 1>The bit of news is that Kaspersky is going to

0:37:18.239 --> 0:37:23.799
<v Speaker 1>have to stop the operation of its VPN product within Russia. Now,

0:37:23.880 --> 0:37:27.760
<v Speaker 1>Kaspersky itself is a Russian company. It's known for making

0:37:27.880 --> 0:37:32.680
<v Speaker 1>security software UH, anti virus, that kind of stuff, as

0:37:32.719 --> 0:37:38.240
<v Speaker 1>well as VPNs or virtual private networks, and UH, Russia

0:37:38.280 --> 0:37:43.600
<v Speaker 1>had already cracked down on most VPNs last year. Uh

0:37:44.120 --> 0:37:47.399
<v Speaker 1>those would be companies that were or VPNs that were

0:37:47.400 --> 0:37:50.720
<v Speaker 1>from companies that were not themselves located out of Russia,

0:37:51.120 --> 0:37:56.080
<v Speaker 1>So things like Nord VPN, Express VPN, Proton VPN, you've

0:37:56.120 --> 0:37:59.640
<v Speaker 1>probably heard of some of these. Those were kind of

0:38:00.560 --> 0:38:05.839
<v Speaker 1>band last year, and a big reason for that is

0:38:05.880 --> 0:38:10.080
<v Speaker 1>that Russia was trying to force these companies to make

0:38:10.120 --> 0:38:15.040
<v Speaker 1>sure that the Russian government would be able to censor

0:38:15.520 --> 0:38:19.840
<v Speaker 1>information across these VPNs, which isn't really what the VPNs

0:38:19.880 --> 0:38:24.040
<v Speaker 1>are for. Uh So Russia is trying to control the

0:38:24.120 --> 0:38:28.839
<v Speaker 1>narrative right there, trying to control the info that their

0:38:28.920 --> 0:38:32.880
<v Speaker 1>citizens can easily access. Not quite to the same level

0:38:32.880 --> 0:38:36.440
<v Speaker 1>that we see in China, but there is some pretty

0:38:36.480 --> 0:38:40.080
<v Speaker 1>heavy censorship going on on the government level in Russia

0:38:40.200 --> 0:38:45.239
<v Speaker 1>regarding Internet information and UM. Yeah, and also they wanted

0:38:45.280 --> 0:38:47.240
<v Speaker 1>to be able to see who was seeing what again,

0:38:47.920 --> 0:38:51.560
<v Speaker 1>that's the VPNs are supposed to be the cure for that.

0:38:51.880 --> 0:38:54.640
<v Speaker 1>You're supposed to use a VPN so that people who

0:38:54.640 --> 0:38:57.440
<v Speaker 1>are snooping on you don't know what sights you're going to.

0:38:57.560 --> 0:39:02.799
<v Speaker 1>It can be absolutely of critical importance in in work right,

0:39:02.880 --> 0:39:05.160
<v Speaker 1>you might be working for a company where you need

0:39:05.200 --> 0:39:09.280
<v Speaker 1>to log into a VPN first before you access company

0:39:10.200 --> 0:39:14.120
<v Speaker 1>assets because the company wants to protect those assets from

0:39:14.120 --> 0:39:16.759
<v Speaker 1>many snoops. They don't want anyone to be able to

0:39:17.600 --> 0:39:22.080
<v Speaker 1>figure out uh proprietary secrets. For example, the Russian government

0:39:22.120 --> 0:39:25.799
<v Speaker 1>does not really like secrets that aren't there's so there

0:39:25.880 --> 0:39:28.520
<v Speaker 1>was a real push for this. Well, now Kaspersky itself,

0:39:28.560 --> 0:39:32.440
<v Speaker 1>a Russian company, has decided to end the VPN service

0:39:32.480 --> 0:39:36.600
<v Speaker 1>within Russia because I guess it has found that it's

0:39:36.640 --> 0:39:41.400
<v Speaker 1>really difficult to provide VPN services and also meet the

0:39:41.480 --> 0:39:45.200
<v Speaker 1>expectations of the Russian government. That these two things are

0:39:45.239 --> 0:39:49.359
<v Speaker 1>antithetical to one another, they counteract each other, and yeah,

0:39:49.520 --> 0:39:54.120
<v Speaker 1>that's where we're at there. It's pretty severe. Uh, I

0:39:54.200 --> 0:40:00.279
<v Speaker 1>don't know how many VPN services are legally available bowl

0:40:00.320 --> 0:40:02.920
<v Speaker 1>in Russia at this point. I'm sure that there are

0:40:02.960 --> 0:40:06.000
<v Speaker 1>no shortage of people who are accessing them illegally, but

0:40:06.120 --> 0:40:09.920
<v Speaker 1>that obviously brings with it some risk. Yeah, that's it.

0:40:10.480 --> 0:40:13.480
<v Speaker 1>That's the last little update that I came across before

0:40:13.600 --> 0:40:17.040
<v Speaker 1>I was ready to send us off to super producer Tari.

0:40:17.680 --> 0:40:20.759
<v Speaker 1>So I hope you are all well. Thank you so

0:40:20.840 --> 0:40:22.920
<v Speaker 1>much for listening. If you would like to reach out

0:40:23.000 --> 0:40:24.279
<v Speaker 1>to the show, there are a couple of ways to

0:40:24.320 --> 0:40:27.400
<v Speaker 1>do that. One is that you can download the I

0:40:27.520 --> 0:40:30.600
<v Speaker 1>Heart Radio app. You can navigate over to the tech

0:40:30.640 --> 0:40:32.640
<v Speaker 1>stuff page. Just put tech Stuff in the little search

0:40:32.680 --> 0:40:38.160
<v Speaker 1>file and you can use the microphone icon click on

0:40:38.239 --> 0:40:42.360
<v Speaker 1>that and you can leave a message up to thirty

0:40:42.520 --> 0:40:46.960
<v Speaker 1>seconds in length and uh that way, I will know

0:40:47.000 --> 0:40:48.400
<v Speaker 1>what it is you would like to hear. And if

0:40:48.400 --> 0:40:50.239
<v Speaker 1>you would like me to use that message in a

0:40:50.239 --> 0:40:53.880
<v Speaker 1>future episode, well just go on ahead and let me

0:40:53.960 --> 0:40:57.600
<v Speaker 1>know in that message, because it's all about opt in. Secondly,

0:40:58.040 --> 0:41:00.400
<v Speaker 1>that if you would prefer to reach out in a

0:41:00.440 --> 0:41:02.960
<v Speaker 1>way that doesn't require you to speak, you can always

0:41:03.000 --> 0:41:05.960
<v Speaker 1>send me a message via Twitter. The handle for the

0:41:05.960 --> 0:41:09.879
<v Speaker 1>show is tech Stuff h s W. Now I'll talk

0:41:09.880 --> 0:41:19.200
<v Speaker 1>to you again really soon, y. Tech Stuff is an

0:41:19.200 --> 0:41:22.880
<v Speaker 1>I Heart Radio production. For more podcasts from I Heart radio,

0:41:23.239 --> 0:41:26.400
<v Speaker 1>visit the I heart Radio app, Apple podcasts, or wherever

0:41:26.480 --> 0:41:28.000
<v Speaker 1>you listen to your favorite shows.