WEBVTT - Tech News: Apple Shares Its (Very Expensive) Vision

0:00:04.440 --> 0:00:12.360
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.400 --> 0:00:15.880
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:15.960 --> 0:00:19.479
<v Speaker 1>I'm an executive producer with iHeartRadio. And how the tech

0:00:19.520 --> 0:00:22.560
<v Speaker 1>are you. It's time for the tech news for Tuesday,

0:00:22.680 --> 0:00:26.560
<v Speaker 1>June sixth, twenty twenty three. And I'm sure you've already

0:00:26.760 --> 0:00:31.160
<v Speaker 1>heard all about it, but yesterday Apple finally unveiled one

0:00:31.160 --> 0:00:35.000
<v Speaker 1>of the worst kept secrets in the industry, the company's

0:00:35.159 --> 0:00:39.800
<v Speaker 1>mixed reality headset. Apple calls it the Vision Pro and

0:00:39.840 --> 0:00:42.879
<v Speaker 1>that pro part should tip you off that the company's

0:00:42.880 --> 0:00:48.159
<v Speaker 1>target audience is business users. Certainly, the three five hundred

0:00:48.200 --> 0:00:50.920
<v Speaker 1>dollars price tag puts it out of the reach for

0:00:51.000 --> 0:00:54.280
<v Speaker 1>most consumers, though I'm sure there will still be several

0:00:54.360 --> 0:00:57.320
<v Speaker 1>tech enthusiasts who have deep pockets who are going to

0:00:57.400 --> 0:00:58.920
<v Speaker 1>shell out the dough to be one of the first

0:00:58.920 --> 0:01:02.160
<v Speaker 1>to own the headset. By the way, Business Insider reports

0:01:02.160 --> 0:01:05.960
<v Speaker 1>that there was a collective grown in response to hearing

0:01:06.040 --> 0:01:10.560
<v Speaker 1>that price tag during the Worldwide Developer Conference, or WWDC

0:01:10.760 --> 0:01:14.480
<v Speaker 1>That's where this announcement happened. Apple ended up confirming a

0:01:14.680 --> 0:01:18.000
<v Speaker 1>lot of rumors that had been circulating about this headset

0:01:18.040 --> 0:01:21.920
<v Speaker 1>for months now. It is a pass through system that

0:01:22.040 --> 0:01:25.959
<v Speaker 1>means the headset has an opaque screen, like it's a

0:01:26.000 --> 0:01:28.880
<v Speaker 1>display that has a solid back to it, and it

0:01:29.000 --> 0:01:32.520
<v Speaker 1>uses cameras to capture live video and then feed that

0:01:32.720 --> 0:01:35.800
<v Speaker 1>to the display in front of the user's eyes, so

0:01:35.840 --> 0:01:39.000
<v Speaker 1>you're not actually looking through the headset, you're looking at

0:01:39.520 --> 0:01:42.199
<v Speaker 1>a live video feed on what's on the other side

0:01:42.200 --> 0:01:46.039
<v Speaker 1>of the headset, now, the opposite side from your peepers,

0:01:46.480 --> 0:01:49.000
<v Speaker 1>the part that other people can see. There is a

0:01:49.040 --> 0:01:52.840
<v Speaker 1>display that looks kind of like you're wearing ski goggles

0:01:52.960 --> 0:01:56.160
<v Speaker 1>on top of a headset, and this display can show

0:01:56.400 --> 0:01:59.080
<v Speaker 1>your eyes to people who are looking at you, or

0:01:59.120 --> 0:02:02.480
<v Speaker 1>rather an image of your eyes, so it doesn't look

0:02:02.520 --> 0:02:04.760
<v Speaker 1>like you just have a screen strapped to your face,

0:02:04.800 --> 0:02:08.040
<v Speaker 1>even though that's exactly what you do have personally. The

0:02:08.120 --> 0:02:11.960
<v Speaker 1>video demonstration I saw made it look kind of creepy,

0:02:12.120 --> 0:02:15.920
<v Speaker 1>kind of like Uncanny Valley ish, but that could just

0:02:15.960 --> 0:02:19.560
<v Speaker 1>be me. The system works with gesture controls. I think

0:02:19.600 --> 0:02:23.840
<v Speaker 1>these controls actually look really impressive. Like Apple's great at

0:02:23.840 --> 0:02:26.760
<v Speaker 1>things like user interfaces and gesture controls. One of their

0:02:26.800 --> 0:02:30.920
<v Speaker 1>strongest suits, I would argue is in their user interfaces,

0:02:31.400 --> 0:02:34.080
<v Speaker 1>and this seems to be no exception. I thought that

0:02:34.200 --> 0:02:38.720
<v Speaker 1>the gestures looked really compelling, like it was really cool

0:02:38.760 --> 0:02:41.960
<v Speaker 1>how you could navigate through the system, So I like

0:02:42.000 --> 0:02:45.280
<v Speaker 1>the interface as presented in Tim Cook's keynote. I still

0:02:45.320 --> 0:02:49.880
<v Speaker 1>don't think the technology really has the applicability for mainstream

0:02:49.919 --> 0:02:53.880
<v Speaker 1>audiences or even for most businesses. I don't think it

0:02:53.919 --> 0:02:57.880
<v Speaker 1>has enough utility to warrant being an actual thing yet,

0:02:58.320 --> 0:03:01.320
<v Speaker 1>but that could be a Chicken and the Egg sort

0:03:01.320 --> 0:03:04.119
<v Speaker 1>of problem. And by that I mean until we see

0:03:04.160 --> 0:03:07.600
<v Speaker 1>some really amazing features, you know, like killer apps that

0:03:07.639 --> 0:03:10.760
<v Speaker 1>are designed for the hardware, we can't fully grasp how

0:03:10.880 --> 0:03:14.600
<v Speaker 1>useful that hardware will be. But then unless there's a

0:03:14.760 --> 0:03:18.560
<v Speaker 1>good amount of support for the hardware and demand for

0:03:18.600 --> 0:03:22.720
<v Speaker 1>the hardware, well there'll be very little incentive for developers

0:03:22.720 --> 0:03:25.880
<v Speaker 1>to make those killer apps in the first place. I

0:03:25.880 --> 0:03:30.480
<v Speaker 1>think Apple's tech looks really impressive, limited in use, but

0:03:30.560 --> 0:03:32.400
<v Speaker 1>also price to a point where it will be a

0:03:32.440 --> 0:03:36.800
<v Speaker 1>real challenge to make it a success. And obviously this

0:03:36.840 --> 0:03:39.520
<v Speaker 1>is a big step down from what Tim Cook had

0:03:39.840 --> 0:03:43.560
<v Speaker 1>hoped for initially, namely a technology that would fit in

0:03:43.600 --> 0:03:46.880
<v Speaker 1>the form factor of a normal pair of eyeglasses that

0:03:46.960 --> 0:03:50.920
<v Speaker 1>actually have transparent lenses in them. But maybe this is

0:03:51.080 --> 0:03:53.840
<v Speaker 1>just a case of having to learn to crawl before

0:03:53.880 --> 0:03:56.640
<v Speaker 1>we can learn to walk, or run or even fly.

0:03:57.360 --> 0:04:00.360
<v Speaker 1>I'm very curious about whether this product is going to

0:04:00.440 --> 0:04:03.880
<v Speaker 1>end up being a foundational cornerstone of Apple's business in

0:04:03.920 --> 0:04:07.000
<v Speaker 1>the future. I have my doubts, but I would love

0:04:07.040 --> 0:04:10.800
<v Speaker 1>to be proven wrong, because despite all my skepticism, I

0:04:10.840 --> 0:04:14.800
<v Speaker 1>really think augmented reality is super cool and potentially it's

0:04:14.840 --> 0:04:19.200
<v Speaker 1>a game changer for lots of different applications. Also, the

0:04:19.240 --> 0:04:22.920
<v Speaker 1>headset is technically capable of VR, but Apple kind of

0:04:23.040 --> 0:04:27.320
<v Speaker 1>ignored that in the presentation. From what I understand, representatives

0:04:27.360 --> 0:04:31.600
<v Speaker 1>were adamant about not talking about virtual reality at all.

0:04:31.640 --> 0:04:35.440
<v Speaker 1>It was pretty much all augmented reality or AR all

0:04:35.480 --> 0:04:39.320
<v Speaker 1>the time. Perhaps this was to highlight the pro stuff

0:04:39.839 --> 0:04:42.440
<v Speaker 1>even more because I think VR typically gets put into

0:04:42.480 --> 0:04:46.239
<v Speaker 1>a bucket that is associated with gaming, even though VR

0:04:46.279 --> 0:04:48.520
<v Speaker 1>can be more than just gaming, it's just that's what

0:04:48.560 --> 0:04:53.040
<v Speaker 1>it's primarily associated with. Anyway, if you've got three thousand,

0:04:53.200 --> 0:04:57.200
<v Speaker 1>four hundred ninety nine American dollars burning a hole in

0:04:57.240 --> 0:05:00.800
<v Speaker 1>your pocket, you can unburden yourself a that cash. In

0:05:00.920 --> 0:05:04.839
<v Speaker 1>early twenty twenty four to get a pair of the suckers.

0:05:05.279 --> 0:05:07.880
<v Speaker 1>I should add that the Vision Pro was really just

0:05:08.120 --> 0:05:14.320
<v Speaker 1>a one more thing moment at the WWDC, which harkens

0:05:14.360 --> 0:05:16.719
<v Speaker 1>back to how Steve Jobs would drop a bombshell of

0:05:16.720 --> 0:05:19.800
<v Speaker 1>an announcement at the end of lots of other announcements.

0:05:20.160 --> 0:05:22.720
<v Speaker 1>So that means that Apple also unveiled tons of other

0:05:22.760 --> 0:05:27.080
<v Speaker 1>stuff besides this mixed reality or if you prefer, augmented

0:05:27.120 --> 0:05:31.640
<v Speaker 1>reality headset. So that includes a new fifteen inch MacBook

0:05:31.680 --> 0:05:34.480
<v Speaker 1>air which will be available starting next week. You can

0:05:34.520 --> 0:05:38.320
<v Speaker 1>preorder it now for one two hundred and ninety nine dollars.

0:05:38.800 --> 0:05:41.160
<v Speaker 1>This would be the largest screen yet for the MacBook

0:05:41.240 --> 0:05:45.120
<v Speaker 1>air Line. The next generation of Mac Pro and the

0:05:45.200 --> 0:05:49.360
<v Speaker 1>Mac Studio computers will get Apple's latest M two Ultra

0:05:49.520 --> 0:05:54.520
<v Speaker 1>microprocessor that boosts the power of those two computers considerably.

0:05:55.400 --> 0:05:58.960
<v Speaker 1>The price tag on those really drive home the increase

0:05:59.000 --> 0:06:02.720
<v Speaker 1>in power, so Mac Studio comes in at a starting

0:06:02.760 --> 0:06:05.680
<v Speaker 1>price of two thousand dollars. That's the starting price for

0:06:05.720 --> 0:06:09.000
<v Speaker 1>the base model. If you're talking about the Mac Pro, well,

0:06:09.160 --> 0:06:14.320
<v Speaker 1>that starts at seven grand. Yowza. Apple also unveiled new

0:06:14.360 --> 0:06:18.840
<v Speaker 1>features for iOS seventeen, including a standby mode, so if

0:06:18.880 --> 0:06:21.599
<v Speaker 1>you are charging your iPhone and you have it mounted

0:06:21.760 --> 0:06:24.479
<v Speaker 1>so it's horizontal. It can act as a kind of

0:06:24.520 --> 0:06:29.640
<v Speaker 1>smart display if you want. Apple also showed off widgets. Hey,

0:06:30.160 --> 0:06:33.400
<v Speaker 1>y'all remember widgets, Like widgets were a big thing like

0:06:33.640 --> 0:06:37.960
<v Speaker 1>fifteen years ago. Well they're back, baby, just like POGs

0:06:38.440 --> 0:06:42.080
<v Speaker 1>out's back in pog form. Well they're on pretty much

0:06:43.080 --> 0:06:46.440
<v Speaker 1>everything now. Widgets are like Apple showed off widgets all

0:06:46.480 --> 0:06:50.400
<v Speaker 1>over the ding dang darn place, including the Apple Watch.

0:06:50.880 --> 0:06:53.200
<v Speaker 1>And there were a lot more announcements, but it gets

0:06:53.200 --> 0:06:55.640
<v Speaker 1>into some pretty nitty gritty stuff with Apple, and I've

0:06:55.680 --> 0:06:58.000
<v Speaker 1>got a lot more news to cover, so I'm just

0:06:58.040 --> 0:07:00.960
<v Speaker 1>gonna leave that for now, and people who are really

0:07:01.160 --> 0:07:04.760
<v Speaker 1>really into Apple can look into it further. There are

0:07:04.800 --> 0:07:08.200
<v Speaker 1>no shortage of articles out there about all the announcements

0:07:08.240 --> 0:07:14.120
<v Speaker 1>at WWDC. Moderators at stack overflow, which is a software

0:07:14.240 --> 0:07:17.600
<v Speaker 1>developer forum, are on strike, at least some of them

0:07:17.600 --> 0:07:22.480
<v Speaker 1>are now. First of all, these moderators are volunteers, so

0:07:22.600 --> 0:07:25.400
<v Speaker 1>it's not like they are paid to be moderators of

0:07:25.440 --> 0:07:29.800
<v Speaker 1>this forum. They're upset due to a change in forum

0:07:29.960 --> 0:07:35.720
<v Speaker 1>policy dictated by stack Exchange, which is organization that owns

0:07:36.160 --> 0:07:40.040
<v Speaker 1>stack Overflow and the moderators have been told that they

0:07:40.040 --> 0:07:43.400
<v Speaker 1>are not allowed to moderate AI generated content just for

0:07:43.480 --> 0:07:48.560
<v Speaker 1>being AI generated. So moderators have been arguing that generative

0:07:48.600 --> 0:07:53.480
<v Speaker 1>AI is untrustworthy, that it can present incorrect information but

0:07:53.680 --> 0:07:55.880
<v Speaker 1>do so in a way where it's acted as if

0:07:55.880 --> 0:08:01.120
<v Speaker 1>it's factual and reliable info, and that generative responses could

0:08:01.120 --> 0:08:05.840
<v Speaker 1>potentially include hallucinations just made up stuff. And that is

0:08:05.960 --> 0:08:09.600
<v Speaker 1>true as we've seen. Generative AI attempts to construct relevant

0:08:09.640 --> 0:08:14.200
<v Speaker 1>answers to queries, but can on occasion just make stuff

0:08:14.320 --> 0:08:18.960
<v Speaker 1>up if it lacks relevant information to use in its place. Plus,

0:08:19.440 --> 0:08:23.000
<v Speaker 1>as moderators have pointed out, it can also engage in plagiarism.

0:08:23.040 --> 0:08:26.800
<v Speaker 1>It can present work that others have created without giving

0:08:26.800 --> 0:08:29.880
<v Speaker 1>proper credit, which is a big no. Note. The moderators

0:08:29.880 --> 0:08:33.679
<v Speaker 1>are also concerned that the policy will mean that the

0:08:33.840 --> 0:08:38.080
<v Speaker 1>value of information across the forums will go into decline,

0:08:38.640 --> 0:08:41.680
<v Speaker 1>that there won't be guardrails place to prevent misinformation and

0:08:41.760 --> 0:08:45.960
<v Speaker 1>mistakes from proliferating across the forums that in turn could

0:08:46.000 --> 0:08:48.679
<v Speaker 1>help developers as they try to create the next generation

0:08:48.760 --> 0:08:52.360
<v Speaker 1>of apps and software. So the moderators also have said

0:08:52.360 --> 0:08:55.240
<v Speaker 1>that this change in policy was communicated one way in

0:08:55.360 --> 0:08:59.400
<v Speaker 1>private to the moderators themselves, but in a totally different

0:08:59.440 --> 0:09:02.880
<v Speaker 1>way when it was communicated to the public at large

0:09:02.960 --> 0:09:06.040
<v Speaker 1>within the forums, and they say that this is a

0:09:06.200 --> 0:09:11.880
<v Speaker 1>problem with transparency within the organization. Stack Overflow says that

0:09:12.040 --> 0:09:15.680
<v Speaker 1>only slightly more than ten percent of moderators have refused

0:09:15.720 --> 0:09:19.360
<v Speaker 1>to work as part of this strike. And further, the

0:09:19.440 --> 0:09:23.800
<v Speaker 1>change in policy wasn't due to misplaced trust in AI.

0:09:23.920 --> 0:09:27.920
<v Speaker 1>It's not to say, oh no, we totally trust AI

0:09:28.040 --> 0:09:30.480
<v Speaker 1>to give the right answers. Instead, it was more an

0:09:30.480 --> 0:09:36.079
<v Speaker 1>indication that stack overflows AI detection duel is not very good,

0:09:36.640 --> 0:09:40.600
<v Speaker 1>that their detection duel creates a lot of false positives,

0:09:40.640 --> 0:09:44.800
<v Speaker 1>meaning it will flag posts that were actually written by

0:09:44.800 --> 0:09:48.920
<v Speaker 1>a real human being as being AI generated. So, in

0:09:48.960 --> 0:09:52.120
<v Speaker 1>other words, the concern is that moderators could end up

0:09:52.320 --> 0:09:55.640
<v Speaker 1>removing posts that were written by people simply because a

0:09:55.720 --> 0:10:00.120
<v Speaker 1>faulty tool said it had been created by AI. And

0:10:00.480 --> 0:10:03.280
<v Speaker 1>this just creates a very complicated problem. We see here

0:10:03.559 --> 0:10:06.280
<v Speaker 1>that the moderators have a good point, right, you don't

0:10:06.320 --> 0:10:10.320
<v Speaker 1>want misinformation to spread across your forums and to make

0:10:10.360 --> 0:10:13.360
<v Speaker 1>life more difficult for developers. On the flip side, you

0:10:13.400 --> 0:10:18.320
<v Speaker 1>don't want to start striking content off the forums because

0:10:18.360 --> 0:10:20.400
<v Speaker 1>a tool told you it was made by AI, when

0:10:20.400 --> 0:10:23.880
<v Speaker 1>in fact it was created by people. So yeah, complicated

0:10:24.000 --> 0:10:26.400
<v Speaker 1>issue here. Okay, we're going to take a quick break.

0:10:26.400 --> 0:10:28.760
<v Speaker 1>When we come back, we've got some more tech news

0:10:28.800 --> 0:10:42.160
<v Speaker 1>to talk about. We're back. So this week marks the

0:10:42.320 --> 0:10:48.040
<v Speaker 1>first week for Linda Yakarino as Twitter's new CEO. Elon

0:10:48.160 --> 0:10:51.640
<v Speaker 1>Musk has relinquished control. I mean, he's staying on at

0:10:51.640 --> 0:10:55.960
<v Speaker 1>Twitter in various capacities, So maybe it's a bit grandiose

0:10:55.960 --> 0:10:58.600
<v Speaker 1>for me to say he's relinquished control, but he's at

0:10:58.679 --> 0:11:03.280
<v Speaker 1>least stepped back from the chief leadership position at the company,

0:11:03.679 --> 0:11:06.280
<v Speaker 1>and it is also a notable step in Twitter's journey

0:11:06.320 --> 0:11:10.360
<v Speaker 1>toward trying to re establish confidence with advertisers and users.

0:11:10.800 --> 0:11:16.480
<v Speaker 1>Musk also intends for Twitter to transform into an everything app,

0:11:16.880 --> 0:11:22.200
<v Speaker 1>something that encompasses everything from communication to commerce and beyond,

0:11:22.840 --> 0:11:24.600
<v Speaker 1>and this is something he's talked about a lot in

0:11:24.600 --> 0:11:26.680
<v Speaker 1>the past, So he says that's part of Linda's job

0:11:26.720 --> 0:11:30.640
<v Speaker 1>is to kind of guide Twitter through this transition, which

0:11:30.720 --> 0:11:34.080
<v Speaker 1>maybe that'll still happen, but I feel like it's going

0:11:34.160 --> 0:11:37.160
<v Speaker 1>to take an awful lot of work to repair Twitter's

0:11:37.240 --> 0:11:42.240
<v Speaker 1>image to make that a successful app. It is very

0:11:42.240 --> 0:11:45.920
<v Speaker 1>hard to be a successful app if you have alienated

0:11:46.480 --> 0:11:50.360
<v Speaker 1>a ton of the user base and corporate partners. Right,

0:11:50.480 --> 0:11:53.760
<v Speaker 1>there's a lot of bad blood between Twitter and tons

0:11:53.800 --> 0:11:58.640
<v Speaker 1>of different other entities. So this is a pretty tall

0:11:59.640 --> 0:12:03.840
<v Speaker 1>mountain to climb. So hopefully Linda Yakarina will be able

0:12:03.840 --> 0:12:06.600
<v Speaker 1>to do this. I actually I wish her all the best.

0:12:06.640 --> 0:12:09.520
<v Speaker 1>I hope Musk isn't too involved in day to day decisions.

0:12:10.040 --> 0:12:12.800
<v Speaker 1>I also assume Tesla stockholders are hoping for that as well.

0:12:12.840 --> 0:12:16.040
<v Speaker 1>They've long been complaining that Elon Musk has spent way

0:12:16.040 --> 0:12:18.440
<v Speaker 1>too much of his time and energy on Twitter at

0:12:18.440 --> 0:12:24.040
<v Speaker 1>the expense of Tesla. So let us be cautiously optimistic

0:12:24.120 --> 0:12:26.680
<v Speaker 1>that things will change for the better, and we'll just

0:12:26.720 --> 0:12:30.319
<v Speaker 1>have to keep eyes on it in the meantime. Last

0:12:30.320 --> 0:12:33.200
<v Speaker 1>week I mentioned that a developer who created a third

0:12:33.240 --> 0:12:35.240
<v Speaker 1>party Reddit app said he was going to have to

0:12:35.280 --> 0:12:38.440
<v Speaker 1>shut down the app due to reddits change with its

0:12:38.480 --> 0:12:43.360
<v Speaker 1>policy for its API or application programming interface. So Reddit

0:12:43.600 --> 0:12:48.080
<v Speaker 1>is going to charge developers for requests that are made

0:12:48.160 --> 0:12:51.080
<v Speaker 1>to the Reddit platform. And by that I mean the

0:12:51.160 --> 0:12:55.480
<v Speaker 1>more frequently an app references Reddit, and the more people

0:12:55.520 --> 0:12:59.000
<v Speaker 1>who are using the app, the more expensive it will

0:12:59.000 --> 0:13:02.080
<v Speaker 1>be for them to to maintain that relationship. The developers

0:13:02.120 --> 0:13:07.720
<v Speaker 1>will be made held responsible for paying a bill. Essentially,

0:13:08.679 --> 0:13:13.000
<v Speaker 1>Reddits Tim Rathschmidt said the reason for this decision is

0:13:13.000 --> 0:13:15.280
<v Speaker 1>that the company has to spend millions of dollars in

0:13:15.360 --> 0:13:19.720
<v Speaker 1>hosting fees, and that means that the more people use

0:13:19.840 --> 0:13:23.800
<v Speaker 1>the platform, the more expensive it is to run the platform,

0:13:24.440 --> 0:13:28.600
<v Speaker 1>and that these third party apps can drive up that

0:13:29.280 --> 0:13:34.199
<v Speaker 1>usage quite a bit, and thus Reddit needs to offset

0:13:34.240 --> 0:13:39.520
<v Speaker 1>the costs by billing the app developers. If the apps

0:13:39.520 --> 0:13:42.040
<v Speaker 1>weren't so dang popular, it wouldn't be as expensive for

0:13:42.080 --> 0:13:45.240
<v Speaker 1>Reddit to be Reddit, but because of the increase in activity,

0:13:45.280 --> 0:13:48.679
<v Speaker 1>Reddit needs to charge developers to recoup costs. That's essentially

0:13:48.760 --> 0:13:52.280
<v Speaker 1>the argument that Reddit is making. That explanation hasn't really

0:13:52.320 --> 0:13:55.280
<v Speaker 1>satisfied a lot of Reddit users, though, and several subreddits

0:13:55.280 --> 0:13:57.360
<v Speaker 1>are playing to go dark for a couple of days

0:13:57.400 --> 0:14:01.320
<v Speaker 1>this month to raise awareness and prote the change in policy.

0:14:01.840 --> 0:14:04.400
<v Speaker 1>And again, this comes down to a pretty complicated matter.

0:14:04.679 --> 0:14:08.400
<v Speaker 1>Reddit is not a not for profit organization. It's trying

0:14:08.440 --> 0:14:11.200
<v Speaker 1>to generate revenue. It's a business, and it does have

0:14:11.240 --> 0:14:13.680
<v Speaker 1>to pay hosting fees and if apps are driving those

0:14:13.720 --> 0:14:16.079
<v Speaker 1>fees up, the money to pay for those fees has

0:14:16.120 --> 0:14:20.240
<v Speaker 1>to come from somewhere. On the other hand, really useful

0:14:20.280 --> 0:14:23.520
<v Speaker 1>apps may not have a way to generate enough revenue

0:14:23.880 --> 0:14:28.080
<v Speaker 1>to pay what Reddit is demanding, So if they can't

0:14:28.440 --> 0:14:32.320
<v Speaker 1>raise the money to pay those fees and be a

0:14:32.360 --> 0:14:35.640
<v Speaker 1>coherent business on their own, they have to fold. It

0:14:35.680 --> 0:14:38.320
<v Speaker 1>may be that the app is incredibly useful, but it's

0:14:38.440 --> 0:14:42.120
<v Speaker 1>not necessarily a big revenue generator, and thus it'll just

0:14:42.160 --> 0:14:45.720
<v Speaker 1>go away. That can ultimately lead to a situation where

0:14:45.880 --> 0:14:49.480
<v Speaker 1>users have no options other than the official Reddit app

0:14:49.880 --> 0:14:53.960
<v Speaker 1>to access Reddit, and then you get into a situation

0:14:54.040 --> 0:14:57.320
<v Speaker 1>where you're looking at non competitive practices and a potential

0:14:57.320 --> 0:15:02.160
<v Speaker 1>monopoly which would get Reddit in trouble with regulators. So again,

0:15:02.280 --> 0:15:05.640
<v Speaker 1>it's super complicated, and I can't pretend to have the

0:15:05.680 --> 0:15:09.960
<v Speaker 1>answers here. I don't have a solution that would solve

0:15:10.280 --> 0:15:15.720
<v Speaker 1>all of these issues across the board. Now it's crypto time. Gosh,

0:15:15.760 --> 0:15:17.280
<v Speaker 1>it feels like it's been a while since I've had

0:15:17.280 --> 0:15:20.880
<v Speaker 1>a bunch of cryptocurrency related stories. Once the fallout from

0:15:21.080 --> 0:15:23.960
<v Speaker 1>FTX collapsing kind of settled, things went a little quiet,

0:15:24.000 --> 0:15:26.640
<v Speaker 1>but we are off to the races again. So first up,

0:15:26.960 --> 0:15:31.040
<v Speaker 1>the United States Securities Exchange Commission or SEC has filed

0:15:31.080 --> 0:15:35.440
<v Speaker 1>more than a dozen charges against Binance, the world's largest

0:15:35.480 --> 0:15:42.240
<v Speaker 1>crypto exchange, and its founder, Chong pen Jao akacz So.

0:15:42.400 --> 0:15:45.800
<v Speaker 1>Among those charges are that Binance has operated as an

0:15:45.880 --> 0:15:49.720
<v Speaker 1>unlicensed securities exchange and also that the company has co

0:15:49.880 --> 0:15:54.400
<v Speaker 1>mingled customer funds with the company's own funds. That's not

0:15:54.480 --> 0:15:57.200
<v Speaker 1>that different from what was going on over at FTX

0:15:57.240 --> 0:16:00.680
<v Speaker 1>before it collapsed. By the way, there are also accusations

0:16:00.680 --> 0:16:06.040
<v Speaker 1>that Binance has used its US subsidiary, Aabinance dot Us

0:16:06.600 --> 0:16:09.800
<v Speaker 1>as a kind of smoke screen, that Binance dot Us

0:16:10.040 --> 0:16:14.240
<v Speaker 1>was created to make an illusion of obeying the law,

0:16:14.720 --> 0:16:18.720
<v Speaker 1>but then the larger international Binance was operating outside of

0:16:18.760 --> 0:16:21.160
<v Speaker 1>the law and was actually pulling all the strings. All

0:16:21.160 --> 0:16:24.880
<v Speaker 1>the transactions were really happening at this higher layer where

0:16:24.920 --> 0:16:27.280
<v Speaker 1>it's the wild West. Actually I would say it's not

0:16:27.280 --> 0:16:29.160
<v Speaker 1>even the wild West, because even in the wild West

0:16:29.240 --> 0:16:33.440
<v Speaker 1>you still had laws. Anyway, these charges appeared to be

0:16:33.480 --> 0:16:37.880
<v Speaker 1>supported by the testimony of two previous CEOs for Binance

0:16:37.920 --> 0:16:42.440
<v Speaker 1>dot Us. That's not good. These two CEOs, who were

0:16:42.480 --> 0:16:47.480
<v Speaker 1>not named but were former CEOs of the company said

0:16:47.560 --> 0:16:49.920
<v Speaker 1>it became pretty clear that they were a little more

0:16:49.960 --> 0:16:52.520
<v Speaker 1>than window dressing and that CZ was really the guy

0:16:52.640 --> 0:16:55.880
<v Speaker 1>calling the shots, or, as one of the two unnamed

0:16:55.960 --> 0:16:59.960
<v Speaker 1>CEOs apparently said, quote, I'm not actually the one right

0:17:00.280 --> 0:17:03.080
<v Speaker 1>this company and the mission that I believe I signed

0:17:03.160 --> 0:17:05.600
<v Speaker 1>up for isn't the mission And as soon as I

0:17:05.640 --> 0:17:09.080
<v Speaker 1>realize that I left end quote. Seems to be a

0:17:09.080 --> 0:17:11.560
<v Speaker 1>pretty big blow to Binance's claims that everything is on

0:17:11.600 --> 0:17:14.640
<v Speaker 1>the up and up. CZ for his part, denies all

0:17:14.640 --> 0:17:18.360
<v Speaker 1>these charges. He says they are meritless, that Binance operates

0:17:18.400 --> 0:17:21.040
<v Speaker 1>within the boundaries of the law and has been cooperative

0:17:21.080 --> 0:17:24.080
<v Speaker 1>with the SEC, and that there's nothing to see here.

0:17:25.600 --> 0:17:30.000
<v Speaker 1>We'll see about that. This also has not satisfied some investors,

0:17:30.040 --> 0:17:33.440
<v Speaker 1>who understandably are a little bit concerned about the whole thing,

0:17:33.480 --> 0:17:37.439
<v Speaker 1>particularly after the drama that was ftx's collapse and the

0:17:37.440 --> 0:17:40.480
<v Speaker 1>collapse of several other crypto related companies in the past year.

0:17:41.119 --> 0:17:46.160
<v Speaker 1>Reuter's reports that since the SEC filed those charges, investors

0:17:46.200 --> 0:17:49.720
<v Speaker 1>have pulled nearly eight hundred million dollars of assets from

0:17:49.760 --> 0:17:52.600
<v Speaker 1>the crypto exchange. Now that's not to say that money

0:17:52.680 --> 0:17:55.879
<v Speaker 1>isn't also flowing in. It is. It's just that, at

0:17:55.960 --> 0:17:59.360
<v Speaker 1>least for some cryptocurrencies, more money is going out than

0:17:59.440 --> 0:18:02.840
<v Speaker 1>is coming in. So, namely, in Ethereum, seven hundred and

0:18:02.880 --> 0:18:07.640
<v Speaker 1>seventy eight point six million dollars have left the exchange

0:18:08.280 --> 0:18:11.560
<v Speaker 1>in a net loss. So eight hundred and seventy one

0:18:11.640 --> 0:18:15.840
<v Speaker 1>million in ethereum entered Binance, but more than one point

0:18:15.920 --> 0:18:20.200
<v Speaker 1>six billion in ethereum left it. Now, it's too early

0:18:20.240 --> 0:18:23.280
<v Speaker 1>to say what the long term effects, if any, the

0:18:23.320 --> 0:18:26.840
<v Speaker 1>SEC's charges are going to have to Binance. It may

0:18:27.000 --> 0:18:29.879
<v Speaker 1>just be another little roadbump for Binance. It could be

0:18:29.960 --> 0:18:33.960
<v Speaker 1>something much more serious, which I know comes across as

0:18:33.960 --> 0:18:37.280
<v Speaker 1>super wishy washy, but literally, I think it's too early

0:18:37.359 --> 0:18:40.400
<v Speaker 1>to draw any conclusions. I'm not ready to say, oh,

0:18:40.440 --> 0:18:43.480
<v Speaker 1>this is the beginning of the end, because it may

0:18:43.560 --> 0:18:46.560
<v Speaker 1>not be. Binance has been through a lot and has

0:18:46.640 --> 0:18:49.359
<v Speaker 1>stuck around, so whether or not this will just be

0:18:49.400 --> 0:18:54.159
<v Speaker 1>another little footnote in its history remains to be seen. However,

0:18:54.200 --> 0:18:57.840
<v Speaker 1>Binance is not the only crypto exchange in SEC's crosshairs.

0:18:58.400 --> 0:19:02.639
<v Speaker 1>The agency also sued Coinbase this morning, accusing the company

0:19:02.640 --> 0:19:07.160
<v Speaker 1>of behaving as an unregistered broker and exchange. SEC chair

0:19:07.440 --> 0:19:11.280
<v Speaker 1>Gary Ginsler elaborated on this and pointed out that the

0:19:11.280 --> 0:19:14.879
<v Speaker 1>New York Stock Exchange is not allowed to operate both

0:19:15.000 --> 0:19:19.040
<v Speaker 1>as a stock exchange and also a hedge fund company,

0:19:19.400 --> 0:19:23.280
<v Speaker 1>but that Coinbase combines a lot of services across different

0:19:23.320 --> 0:19:27.280
<v Speaker 1>financial institutions that effectively means they're trying to be all

0:19:27.359 --> 0:19:30.679
<v Speaker 1>things to all investors, despite the fact that regulations would

0:19:31.080 --> 0:19:33.840
<v Speaker 1>say that that's not allowed. So the complaint says that

0:19:33.920 --> 0:19:39.119
<v Speaker 1>Coinbase's core businesses break securities laws. Now, again, this is

0:19:39.160 --> 0:19:42.040
<v Speaker 1>in the very early stages of a legal process, so

0:19:42.119 --> 0:19:44.600
<v Speaker 1>it is too soon to predict how this is going

0:19:44.680 --> 0:19:49.320
<v Speaker 1>to affect Coinbase in particular and the larger crypto community

0:19:49.400 --> 0:19:53.320
<v Speaker 1>in general. It could be that the process forces Coinbase

0:19:53.400 --> 0:19:58.280
<v Speaker 1>to fundamentally change how it operates, or also to pay

0:19:58.480 --> 0:20:02.560
<v Speaker 1>a settlement perhaps a side Maybe it would go even

0:20:02.600 --> 0:20:05.480
<v Speaker 1>more extreme, maybe Coinbase would be forced to shut down.

0:20:06.160 --> 0:20:09.239
<v Speaker 1>Or it could pan out that Coinbase successfully argues it

0:20:09.240 --> 0:20:12.719
<v Speaker 1>hasn't broken any laws at all. However, one thing that

0:20:12.840 --> 0:20:16.120
<v Speaker 1>is clear is the struggle between regulators and the crypto

0:20:16.160 --> 0:20:20.080
<v Speaker 1>community is going on strong. It's not going to stop

0:20:20.359 --> 0:20:25.800
<v Speaker 1>anytime soon. Okay, I've got a couple of bizarre stories

0:20:26.160 --> 0:20:28.639
<v Speaker 1>that I need to talk about. But before we get

0:20:28.680 --> 0:20:40.640
<v Speaker 1>to those, let's take another quick break. Okay, y'all. I'm

0:20:40.680 --> 0:20:43.080
<v Speaker 1>actually kind of reluctant to talk about these next couple

0:20:43.080 --> 0:20:47.280
<v Speaker 1>of stories because I feel like it's very difficult to

0:20:47.359 --> 0:20:50.679
<v Speaker 1>approach them in a way that is responsible. But at

0:20:50.720 --> 0:20:52.280
<v Speaker 1>the same time, I feel like I have to or

0:20:52.320 --> 0:20:54.920
<v Speaker 1>else people will ask me why I didn't talk about them.

0:20:54.960 --> 0:20:59.439
<v Speaker 1>So first up, NASA held its first public meeting about

0:20:59.520 --> 0:21:05.480
<v Speaker 1>unexploed anomalous phenomena or UAP. So once upon a time

0:21:05.800 --> 0:21:09.440
<v Speaker 1>we would refer to this stuff as UFOs or unidentified

0:21:09.440 --> 0:21:15.399
<v Speaker 1>flying objects. I actually prefer unexplained anomalous phenomena because, for

0:21:15.440 --> 0:21:19.480
<v Speaker 1>one thing, not every UFO incident is actually involving an object.

0:21:19.960 --> 0:21:23.280
<v Speaker 1>Sometimes it's not an object, it's an illusion, and an

0:21:23.320 --> 0:21:27.399
<v Speaker 1>illusion is not a thing, so object is a misleading term.

0:21:27.760 --> 0:21:30.880
<v Speaker 1>For another, not every incident actually involves something that's flying,

0:21:31.640 --> 0:21:35.760
<v Speaker 1>so flying can be an inaccurate term. Some UAP ends

0:21:35.840 --> 0:21:41.879
<v Speaker 1>up being just a really mundane situation that can be misinterpreted.

0:21:42.320 --> 0:21:45.760
<v Speaker 1>So here's an example. There can be a pilot who's

0:21:45.800 --> 0:21:50.800
<v Speaker 1>flying at night over the ocean on a particularly cloudy evening,

0:21:51.400 --> 0:21:54.600
<v Speaker 1>and the clouds could obscure the pilot's view of the Moon,

0:21:54.960 --> 0:21:58.160
<v Speaker 1>but the Moon's light might still hit the water at

0:21:58.160 --> 0:22:01.080
<v Speaker 1>some distance and create a reflection. Now, the pilot can't

0:22:01.119 --> 0:22:03.800
<v Speaker 1>see the Moon, but the pilot can see the reflection,

0:22:04.200 --> 0:22:06.439
<v Speaker 1>and because it's dark, it might not be easy to

0:22:06.480 --> 0:22:08.719
<v Speaker 1>tell that this is just a reflection on the surface

0:22:08.760 --> 0:22:11.119
<v Speaker 1>of the water. It's just to the pilot it looks

0:22:11.119 --> 0:22:14.560
<v Speaker 1>like a light off on the horizon. And next thing

0:22:14.560 --> 0:22:18.200
<v Speaker 1>the pilot knows, this light seems to be traveling with them,

0:22:18.720 --> 0:22:21.480
<v Speaker 1>and it seems to maneuver in strange ways as the

0:22:21.520 --> 0:22:26.560
<v Speaker 1>pilot moves course. But in fact there's nothing flying at all,

0:22:26.880 --> 0:22:30.280
<v Speaker 1>unless you count the Moon. I don't the moon already

0:22:30.280 --> 0:22:34.080
<v Speaker 1>thinks it's so big? Yeah, I see you, Moon, not

0:22:34.080 --> 0:22:38.040
<v Speaker 1>getting any props from me anyway. According to the report

0:22:38.240 --> 0:22:41.879
<v Speaker 1>that NASA gave at this meeting, all but two to

0:22:42.040 --> 0:22:47.960
<v Speaker 1>five percent of the hundreds of UAP reports are something

0:22:48.000 --> 0:22:51.280
<v Speaker 1>that we could easily explain, right, All but two to

0:22:51.280 --> 0:22:55.600
<v Speaker 1>five percent of those those remaining incidents quote display signatures

0:22:55.600 --> 0:22:59.120
<v Speaker 1>that could be anomalous end too quote. Now, of course

0:22:59.119 --> 0:23:03.280
<v Speaker 1>that doesn't mean anything, right. They could be anomalist or

0:23:03.320 --> 0:23:07.439
<v Speaker 1>they could be totally normal. And mundane. We lack the

0:23:07.560 --> 0:23:12.560
<v Speaker 1>information to be able to make a judgment. So saying

0:23:12.560 --> 0:23:14.680
<v Speaker 1>that we don't have enough information isn't the same as

0:23:14.680 --> 0:23:19.240
<v Speaker 1>saying there's stuff out there that defies explanation and must

0:23:19.280 --> 0:23:22.080
<v Speaker 1>be non terrestrial or at least non human in origin.

0:23:22.560 --> 0:23:26.080
<v Speaker 1>I'm sure some people are frustrated that NASA didn't go

0:23:26.160 --> 0:23:28.320
<v Speaker 1>so far as to say, I don't know, maybe it's aliens,

0:23:29.000 --> 0:23:32.600
<v Speaker 1>but to go that far would require extraordinary proof. Now

0:23:33.080 --> 0:23:34.840
<v Speaker 1>there's another story that I feel I have to tell

0:23:34.880 --> 0:23:38.760
<v Speaker 1>that ties into this kind of concept as well, and

0:23:38.800 --> 0:23:41.560
<v Speaker 1>it's because it's getting a lot of circulation as I'm

0:23:41.600 --> 0:23:46.680
<v Speaker 1>recording this episode. So The Debrief published a very long

0:23:46.800 --> 0:23:51.439
<v Speaker 1>article by Leslie Keene and Ralph Blumenthal this week that

0:23:51.680 --> 0:23:58.800
<v Speaker 1>details claims from a person they name as David Charles Grush, who,

0:23:59.080 --> 0:24:02.400
<v Speaker 1>according to the article, is a former Department of Defense operative.

0:24:02.840 --> 0:24:05.680
<v Speaker 1>He worked for the Department of Defense in various capacities

0:24:06.119 --> 0:24:08.600
<v Speaker 1>and has said that the United States has in its

0:24:08.680 --> 0:24:13.920
<v Speaker 1>possession intact vehicles and parts of vehicles of quote unquote

0:24:14.040 --> 0:24:19.280
<v Speaker 1>exotic origin, meaning created by non human intelligence. That is

0:24:19.359 --> 0:24:23.600
<v Speaker 1>obviously a truly extraordinary claim, and the report, like I said,

0:24:23.640 --> 0:24:27.560
<v Speaker 1>it's spreading like wildfire. As I record this episode, everyone

0:24:27.600 --> 0:24:31.600
<v Speaker 1>seems to just be referencing this one article, Like, I

0:24:31.640 --> 0:24:37.880
<v Speaker 1>haven't seen any investigative journalism that went to verify this article.

0:24:38.160 --> 0:24:40.800
<v Speaker 1>They're just kind of using the article as the foundation

0:24:41.000 --> 0:24:43.959
<v Speaker 1>and then repeating claims that were made in it. So

0:24:44.280 --> 0:24:48.000
<v Speaker 1>I want to raise a couple of red flags. None

0:24:48.040 --> 0:24:52.159
<v Speaker 1>of this is to say that the article is inherently untrustworthy.

0:24:52.240 --> 0:24:55.960
<v Speaker 1>It's just stuff that makes me a little skeptical. So,

0:24:56.080 --> 0:24:59.639
<v Speaker 1>first off, the authors of this article, Leslie Keane and

0:24:59.720 --> 0:25:03.280
<v Speaker 1>Ralph Blumenthal, they are both notable journalists, all right, They

0:25:03.280 --> 0:25:08.320
<v Speaker 1>have long careers in journalism, distinguished careers. However, they are

0:25:08.400 --> 0:25:11.879
<v Speaker 1>also both published authors who have written books in the

0:25:12.040 --> 0:25:17.359
<v Speaker 1>UFO and aliens space. So that raises some red flags

0:25:17.359 --> 0:25:20.480
<v Speaker 1>for me immediately. I don't know if that means they

0:25:20.480 --> 0:25:25.919
<v Speaker 1>are predisposed to believing extraordinary claims that involve things like

0:25:26.320 --> 0:25:30.760
<v Speaker 1>UFOs or UAPs, but it does concern me because they've

0:25:30.840 --> 0:25:35.000
<v Speaker 1>already been writing about this stuff for a while and

0:25:36.440 --> 0:25:40.760
<v Speaker 1>these claims never seem to ever produce anything, right. We

0:25:40.840 --> 0:25:44.960
<v Speaker 1>hear about them occasionally, but we never actually see anything produced. Secondly,

0:25:45.640 --> 0:25:49.440
<v Speaker 1>I tried to find some information about David Grush earlier

0:25:49.640 --> 0:25:53.480
<v Speaker 1>before I started writing this episode. But my search has

0:25:53.520 --> 0:25:58.119
<v Speaker 1>pulled up nothing other than variations of this article. So,

0:25:58.240 --> 0:26:00.240
<v Speaker 1>like I said, it's spreading like wildfire right now. So

0:26:00.240 --> 0:26:02.119
<v Speaker 1>when I did a search for his name, I just

0:26:02.160 --> 0:26:06.639
<v Speaker 1>got countless versions of this story, and again it all

0:26:06.680 --> 0:26:09.919
<v Speaker 1>seemed like they were kind of summarizing what was already

0:26:09.920 --> 0:26:14.600
<v Speaker 1>published in the debrief, but not verifying anything other than

0:26:14.640 --> 0:26:18.760
<v Speaker 1>one exception. I did find one web page on a

0:26:18.840 --> 0:26:24.800
<v Speaker 1>defunct Space Force website for the Shriever Space Force Base

0:26:25.600 --> 0:26:29.960
<v Speaker 1>that had a person named David Grush who was promoted

0:26:30.000 --> 0:26:33.359
<v Speaker 1>to the rank of captain. David Grush was one name,

0:26:33.520 --> 0:26:36.960
<v Speaker 1>along with dozens of others of lieutenants who had received

0:26:36.960 --> 0:26:40.359
<v Speaker 1>this promotion. That's the only other instance I could find

0:26:40.520 --> 0:26:43.240
<v Speaker 1>of David Grush's name. That's not to say that other

0:26:43.240 --> 0:26:46.400
<v Speaker 1>stuff doesn't exist out there, maybe it's just buried under

0:26:46.440 --> 0:26:49.640
<v Speaker 1>these recent reports. But what I'm saying is these sort

0:26:49.680 --> 0:26:52.840
<v Speaker 1>of things make me remain skeptical. Now. If it comes

0:26:52.840 --> 0:26:57.399
<v Speaker 1>to pass that these are in fact real reports of

0:26:57.640 --> 0:27:03.119
<v Speaker 1>real vehicles from non human intelligence, that would be beyond disruptive.

0:27:03.200 --> 0:27:06.360
<v Speaker 1>As it stands, it would be pretty darn and credible

0:27:07.080 --> 0:27:10.399
<v Speaker 1>because it would mean either some sort of non terrestrial

0:27:10.640 --> 0:27:14.879
<v Speaker 1>entity has visited us, and you know, we haven't detected

0:27:14.920 --> 0:27:20.159
<v Speaker 1>any evidence of intelligent life anywhere within our vicinity, and

0:27:20.200 --> 0:27:22.879
<v Speaker 1>our own history of radio communications only dates back a

0:27:22.880 --> 0:27:26.520
<v Speaker 1>little more than a century, which means for anyone to

0:27:26.640 --> 0:27:30.840
<v Speaker 1>have known about us, to know that we exist, would

0:27:30.920 --> 0:27:34.080
<v Speaker 1>require them to be within say a hundred light years

0:27:34.280 --> 0:27:37.920
<v Speaker 1>of Earth. That then you have to think about actually

0:27:38.000 --> 0:27:43.440
<v Speaker 1>traveling to Earth, Right, Why would anyone travel to Earth randomly?

0:27:43.800 --> 0:27:46.879
<v Speaker 1>I mean, maybe just by chance, but that seems to

0:27:47.000 --> 0:27:50.520
<v Speaker 1>be pretty crazy to think about. But if they're coming

0:27:50.560 --> 0:27:54.360
<v Speaker 1>here because they've detected life, well then they would need

0:27:54.400 --> 0:27:57.359
<v Speaker 1>to be you know, probably within a hundred light years

0:27:57.400 --> 0:27:59.399
<v Speaker 1>of us, and then they would have to have some

0:27:59.520 --> 0:28:02.439
<v Speaker 1>means of try travel that could take them to Earth

0:28:03.119 --> 0:28:08.080
<v Speaker 1>within you know, one hundred one hundred years, and that

0:28:08.200 --> 0:28:11.760
<v Speaker 1>just seems like that's a big commitment. It's just it's

0:28:11.880 --> 0:28:17.280
<v Speaker 1>hard to align all of this so that it makes sense,

0:28:18.000 --> 0:28:20.080
<v Speaker 1>because to travel to Earth would require a lot of time.

0:28:20.119 --> 0:28:22.880
<v Speaker 1>We know that matter cannot travel at the speed of light,

0:28:23.280 --> 0:28:25.639
<v Speaker 1>so if something's one hundred light years away, it's going

0:28:25.680 --> 0:28:29.040
<v Speaker 1>to take way way, way longer. For a physical craft

0:28:29.440 --> 0:28:35.520
<v Speaker 1>to travel that distance, barring some weird wormhole technology, which

0:28:35.800 --> 0:28:39.560
<v Speaker 1>I guess is possibly within the realm of possibility, but

0:28:39.640 --> 0:28:43.000
<v Speaker 1>would require such an enormous amount of energy that, again,

0:28:43.560 --> 0:28:47.080
<v Speaker 1>the investment to going to Earth would be so great

0:28:47.880 --> 0:28:51.040
<v Speaker 1>that it's hard to imagine why anyone would agree to

0:28:51.080 --> 0:28:52.920
<v Speaker 1>do it. So I guess what I'm saying is that

0:28:52.960 --> 0:28:56.320
<v Speaker 1>there are a ton of factors that would have to

0:28:56.360 --> 0:28:59.560
<v Speaker 1>fall into place, some of which appear to contradict our

0:28:59.640 --> 0:29:03.040
<v Speaker 1>understand ending how the universe works for this to actually

0:29:03.680 --> 0:29:08.120
<v Speaker 1>be true. Now, there is another possibility. You could argue, well,

0:29:08.200 --> 0:29:13.920
<v Speaker 1>maybe the discovery of non human intelligence created materials doesn't

0:29:13.920 --> 0:29:16.440
<v Speaker 1>mean that it came from outside of Earth. It just

0:29:16.480 --> 0:29:19.320
<v Speaker 1>means there was some sort of non human intelligence present

0:29:19.400 --> 0:29:22.480
<v Speaker 1>on Earth at some point that made a vehicle. That

0:29:22.520 --> 0:29:25.280
<v Speaker 1>also seems unlikely to me, because you would think that

0:29:25.320 --> 0:29:27.600
<v Speaker 1>there would be more evidence that would have been uncovered

0:29:27.640 --> 0:29:31.880
<v Speaker 1>independently of these activities, and that not all of those

0:29:31.920 --> 0:29:35.840
<v Speaker 1>could potentially have been kept quiet by some cabal of

0:29:35.840 --> 0:29:44.560
<v Speaker 1>official government agencies. So I'm just saying red flags abound. Now,

0:29:44.840 --> 0:29:49.480
<v Speaker 1>maybe the whole story is true. Maybe it is, but

0:29:49.600 --> 0:29:55.440
<v Speaker 1>it will require extraordinary proof to actually have me, you know,

0:29:55.560 --> 0:29:59.240
<v Speaker 1>come around to that. As it stands, I remain very

0:29:59.360 --> 0:30:03.680
<v Speaker 1>very skeptic, and uh yeah, I'm not even saying that

0:30:03.720 --> 0:30:10.600
<v Speaker 1>anyone is telling an outright lie necessarily, just that it

0:30:10.680 --> 0:30:14.440
<v Speaker 1>doesn't it doesn't pass the smell test for me. But

0:30:15.200 --> 0:30:18.280
<v Speaker 1>I also admit that I could be completely wrong about this.

0:30:18.760 --> 0:30:21.760
<v Speaker 1>I don't feel like I am, but I could be. Now.

0:30:21.760 --> 0:30:25.000
<v Speaker 1>Our last story is partly goofy and partly a warning

0:30:25.040 --> 0:30:29.480
<v Speaker 1>about the excesses of venture capital activity. The information reports

0:30:29.600 --> 0:30:35.000
<v Speaker 1>that the company Zoom spelled zume is no more, and

0:30:35.040 --> 0:30:38.400
<v Speaker 1>that is notable because that startup launched in twenty fifteen

0:30:38.480 --> 0:30:43.040
<v Speaker 1>and raised nearly four hundred and fifty million dollars in funding,

0:30:44.000 --> 0:30:46.920
<v Speaker 1>and yet has now gone out of business. Initially, the

0:30:46.920 --> 0:30:50.280
<v Speaker 1>company aimed to bring pizza delivery into the future, so

0:30:50.360 --> 0:30:54.680
<v Speaker 1>the business model would combine robotics with essentially food trucks.

0:30:54.880 --> 0:30:57.800
<v Speaker 1>So the idea was that a customer would order a pizza,

0:30:57.920 --> 0:31:00.400
<v Speaker 1>you know, like through an app or whatever, and the

0:31:00.400 --> 0:31:03.840
<v Speaker 1>food truck driver would get a notification to drive to

0:31:03.880 --> 0:31:08.040
<v Speaker 1>that customer's location. Meanwhile, in the food truck part, a

0:31:08.120 --> 0:31:12.560
<v Speaker 1>robot in the truck would actually make the pizza so

0:31:12.600 --> 0:31:15.400
<v Speaker 1>it'd be cooked to order, so you get a really

0:31:15.440 --> 0:31:18.320
<v Speaker 1>fresh pizza this way, right, the pizza's actually being cooked

0:31:18.400 --> 0:31:21.600
<v Speaker 1>as it's being delivered to you. Apparently, this business model

0:31:21.640 --> 0:31:24.600
<v Speaker 1>was a bust. The company spent way more money than

0:31:24.640 --> 0:31:28.160
<v Speaker 1>it was generating in revenue, and apparently part of the

0:31:28.200 --> 0:31:30.440
<v Speaker 1>problem was that the cheese would slide it all over

0:31:30.480 --> 0:31:32.800
<v Speaker 1>the place if the truck hit any bumps in the road,

0:31:32.840 --> 0:31:35.880
<v Speaker 1>so you would end up with a substandard pizza as

0:31:35.880 --> 0:31:38.880
<v Speaker 1>a result of all this, so that is an issue.

0:31:39.280 --> 0:31:41.560
<v Speaker 1>The company attempted to pivot by going to a more

0:31:41.600 --> 0:31:47.040
<v Speaker 1>traditional like stationary food truck route with still maybe using delivery,

0:31:47.120 --> 0:31:49.920
<v Speaker 1>but the food truck itself wasn't the one moving around.

0:31:50.000 --> 0:31:52.360
<v Speaker 1>You would have the food truck be stationary with the

0:31:52.440 --> 0:31:56.440
<v Speaker 1>robot making its pizzas. But this also didn't end up

0:31:56.440 --> 0:32:00.880
<v Speaker 1>being a sustainable business. Then the company changed directions completely.

0:32:01.320 --> 0:32:05.240
<v Speaker 1>It totally dumped the pizza business and instead switched to

0:32:05.280 --> 0:32:09.600
<v Speaker 1>designing sustainable packaging. That is a pretty big change in

0:32:09.640 --> 0:32:12.760
<v Speaker 1>your business model. Anyway, that didn't work either, and last

0:32:12.760 --> 0:32:16.120
<v Speaker 1>month the company folded, according to the information. So the

0:32:16.200 --> 0:32:19.520
<v Speaker 1>story illustrates that venture capital can frequently dump a ton

0:32:19.560 --> 0:32:24.600
<v Speaker 1>of money into businesses that aren't really viable. And you

0:32:24.680 --> 0:32:26.920
<v Speaker 1>might think at first that too much money isn't really

0:32:26.920 --> 0:32:29.280
<v Speaker 1>that bad of a problem, but it definitely can be.

0:32:29.440 --> 0:32:31.800
<v Speaker 1>It can lead to very bad decisions that in the

0:32:31.840 --> 0:32:35.760
<v Speaker 1>long run, will doom a startup. We saw it again

0:32:35.880 --> 0:32:39.240
<v Speaker 1>and again leading up to the dot com bubble bursting

0:32:39.400 --> 0:32:41.840
<v Speaker 1>a couple of decades ago, and yet it seems as

0:32:41.880 --> 0:32:45.040
<v Speaker 1>though the investment world hasn't really taken those lessons to heart.

0:32:45.720 --> 0:32:49.720
<v Speaker 1>Well in the meantime, farewell zoom, we hardly knew ye,

0:32:50.240 --> 0:32:53.760
<v Speaker 1>And now I'm craving pizza. Finally, I would like to

0:32:53.800 --> 0:32:57.360
<v Speaker 1>recommend an article that is a really good piece to read,

0:32:57.400 --> 0:33:00.880
<v Speaker 1>but it kind of goes beyond a news item. So

0:33:00.920 --> 0:33:03.800
<v Speaker 1>today I want to recommend an article that was published

0:33:03.920 --> 0:33:07.680
<v Speaker 1>June first in The New Yorker. It's titled A Confession

0:33:07.800 --> 0:33:13.680
<v Speaker 1>Exposes India's Secret Hacking Industry. It was written by David D. Kirkpatrick.

0:33:14.120 --> 0:33:17.400
<v Speaker 1>It explains how India is the source or maybe I

0:33:17.440 --> 0:33:21.520
<v Speaker 1>should say outsource of hacking assets used by various entities

0:33:21.560 --> 0:33:24.520
<v Speaker 1>around the world. It's a good read and you should

0:33:24.560 --> 0:33:27.560
<v Speaker 1>definitely check it out again. That is A Confession exposes

0:33:27.720 --> 0:33:31.320
<v Speaker 1>India's secret hacking industry in the New Yorker, and as

0:33:31.360 --> 0:33:33.960
<v Speaker 1>always I have no connection to the New Yorker. I

0:33:34.080 --> 0:33:37.360
<v Speaker 1>do not know David Kirkpatrick. This was just an article

0:33:37.400 --> 0:33:40.600
<v Speaker 1>I thought was worth reading. That's it for today's news episode.

0:33:40.640 --> 0:33:43.000
<v Speaker 1>I hope you are all well. We will not have

0:33:43.120 --> 0:33:46.240
<v Speaker 1>a news episode on Thursday. If all goes as planned,

0:33:46.240 --> 0:33:49.440
<v Speaker 1>we will have a full length tech Stuff episode in

0:33:49.480 --> 0:33:54.840
<v Speaker 1>its place, unless things change. But as it stands right now,

0:33:55.400 --> 0:33:58.520
<v Speaker 1>that's the plan because that's what I recorded. But we

0:33:58.600 --> 0:34:01.360
<v Speaker 1>will see. I hope everything's going well for you, like

0:34:01.440 --> 0:34:03.600
<v Speaker 1>I said that already, and I'll talk to you again

0:34:04.360 --> 0:34:14.120
<v Speaker 1>really soon. Tech Stuff is an iHeartRadio production. For more

0:34:14.200 --> 0:34:18.960
<v Speaker 1>podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts, or

0:34:18.960 --> 0:34:20.920
<v Speaker 1>wherever you listen to your favorite shows.