WEBVTT - Tech News: Microsoft Says Goodbye to Internet Explorer 0:00:04.440 --> 0:00:07.840 Welcome to tex Stuff, a production from I Heart Radio. 0:00:11.680 --> 0:00:14.160 Hey there, and welcome to tech Stuff. I'm your host 0:00:14.280 --> 0:00:17.000 Jonathan Strickland. I'm an executive producer with I Heart Radio. 0:00:17.079 --> 0:00:19.560 And how the tech are you. It's time for the 0:00:19.600 --> 0:00:24.799 tech news for Tuesday, June two thousand twenty two. Our 0:00:25.000 --> 0:00:30.440 first news item is about Google's conversation model AI that's 0:00:30.480 --> 0:00:34.280 called Lambda L A M D A. Now I covered 0:00:34.280 --> 0:00:37.400 this in yesterday's tech Stuff episode, but in case you 0:00:37.440 --> 0:00:41.479 missed it, here is the short version. An engineer at 0:00:41.520 --> 0:00:46.640 Google working in the Responsible AI division was suspended from 0:00:46.680 --> 0:00:52.160 his job after saying the AI might be sentient. The engineer, 0:00:52.280 --> 0:00:56.080 Blake Lemouan, shared a transcript of a few conversations that 0:00:56.160 --> 0:00:59.400 he and a colleague of his had with the conversation engine, 0:01:00.080 --> 0:01:03.760 during which the engine argued that it was conscious and 0:01:03.840 --> 0:01:08.360 that it experienced emotions. Google suspended the engineer for violating 0:01:08.400 --> 0:01:13.120 a confidentiality policy, which undoubtedly helped fuel speculation about the 0:01:13.160 --> 0:01:17.480 model's alleged sentience. Now, several AI experts have weighed in 0:01:17.520 --> 0:01:20.520 on this, and the general consensus is that Lambda is 0:01:20.560 --> 0:01:24.919 nowhere close to being sentient or conscious. It's just good 0:01:24.959 --> 0:01:27.520 at what it's supposed to do, which is to generate 0:01:27.520 --> 0:01:31.840 conversational dialogue. But as Gary Marcus, who is the founder 0:01:31.880 --> 0:01:35.360 of geometric intelligence, put it, what that really does is 0:01:35.400 --> 0:01:38.840 it just means Lambda is a very advanced version of 0:01:38.959 --> 0:01:44.240 auto complete. Lambda uses statistics to determine what to say next. 0:01:44.600 --> 0:01:49.040 So imagine you had a truly enormous database that contains 0:01:49.280 --> 0:01:53.360 practically all the conversations that have ever been recorded, and 0:01:53.440 --> 0:01:56.880 you could see which responses were more prevalent to particular 0:01:56.960 --> 0:02:00.760 lines of conversation, weigh them against each other, and create 0:02:00.760 --> 0:02:04.080 an engine that could select the appropriate one at the 0:02:04.080 --> 0:02:07.480 appropriate time. So you use a very complicated version of 0:02:07.520 --> 0:02:11.240 this general approach and you get something like lambda. It's 0:02:11.240 --> 0:02:14.640 a process that can construct sentences that seem natural because 0:02:14.639 --> 0:02:19.760 they are drawn from natural conversations, not you know, verbatim, 0:02:19.800 --> 0:02:23.000 but that's what is being used to model it. It's 0:02:23.040 --> 0:02:27.120 a very cool technology, but it's not sentient AI. As 0:02:27.160 --> 0:02:29.960 I mentioned yesterday, we humans have a tendency to ascribe 0:02:30.120 --> 0:02:34.480 human like traits to non human things, whether that be animals, 0:02:34.840 --> 0:02:39.160 your car, or a chatbot. We imagine there's a mind 0:02:39.360 --> 0:02:42.800 at work, when in many cases no such mind exists. 0:02:43.320 --> 0:02:46.079 I still think this raises questions about what it will 0:02:46.120 --> 0:02:49.280 take for us to conclude that an AI has gained 0:02:49.400 --> 0:02:52.080 some form of consciousness, And I don't know what the 0:02:52.120 --> 0:02:54.800 answer is to that, But then I'm not an AI expert, 0:02:54.840 --> 0:02:57.360 and I imagine the folks who are really deep in 0:02:57.400 --> 0:02:59.760 this research have a much better grasp of what it 0:02:59.800 --> 0:03:01.920 would take for us to consider any evidence to be 0:03:01.960 --> 0:03:06.600 close to conclusive. Google has agreed to a one eighteen 0:03:06.639 --> 0:03:10.560 million dollar settlement in a class action lawsuit brought against 0:03:10.560 --> 0:03:14.040 it by employees, namely women who worked for Google since 0:03:14.080 --> 0:03:16.760 two thousand thirteen. And these are women who say they 0:03:16.800 --> 0:03:20.400 were paid significantly less than their male counterparts who were 0:03:20.400 --> 0:03:23.720 working in the same kind of jobs. Specifically, on average, 0:03:23.720 --> 0:03:28.200 women were paid sixteen thousand, seven hundred ninety four dollars 0:03:28.280 --> 0:03:31.560 less than men in similar positions. On average. That includes 0:03:31.760 --> 0:03:34.480 not just base compensation, but also stuff like bonuses and 0:03:34.520 --> 0:03:38.760 stock options. In addition, the lawsuit accused Google of placing 0:03:38.800 --> 0:03:42.200 women in lower level positions than men with similar experience, 0:03:42.680 --> 0:03:45.800 and that when employees were leaving the company, Google failed 0:03:45.840 --> 0:03:47.960 to pay out the full amount that was owed to 0:03:48.000 --> 0:03:51.240 those employees. This was a pretty big lawsuit. There were 0:03:51.240 --> 0:03:54.120 more than fifteen thousand women who had worked for Google 0:03:54.120 --> 0:03:56.880 since twenty that were part of it. Four of the 0:03:56.920 --> 0:04:02.080 women will receive significant payouts. Kelly List will receive seventy dollars, 0:04:02.400 --> 0:04:05.320 three others will get fifty tho each, and the rest 0:04:05.360 --> 0:04:07.880 of those fifteen thousand plus women will get on average 0:04:07.880 --> 0:04:12.000 around five thousand dollars. The rest of the cash goes to, 0:04:12.200 --> 0:04:15.840 of course, you know, lawyers, legal fees, that kind of thing. 0:04:16.320 --> 0:04:18.440 So does this mean that we're going to see some 0:04:18.520 --> 0:04:23.479 massive changes at Google. Well, this was a settlement, not 0:04:23.760 --> 0:04:27.480 a legal judgment, and Google has not admitted to any 0:04:27.600 --> 0:04:31.760 kind of wrongdoing. Rather, Google reps say that the company 0:04:31.760 --> 0:04:35.760 frequently reviews compensation and whenever it finds inequities, it makes 0:04:35.839 --> 0:04:40.520 quote unquote upward adjustments to remove those inequities. I certainly 0:04:40.560 --> 0:04:44.840 hope that Google Walks that walk, Google Talk a k 0:04:45.040 --> 0:04:48.520 A g Chat is finally right off to that there, 0:04:48.680 --> 0:04:52.600 sunset alright, settle in. This gets confusing because, let's face it, 0:04:53.240 --> 0:04:57.159 Google is not great at introducing and then continuing to 0:04:57.240 --> 0:05:01.359 support its various products. The company as an incredibly long 0:05:01.400 --> 0:05:04.640 list of services that have long since gone away. And 0:05:04.720 --> 0:05:08.360 let's just pause and think for a moment about some 0:05:08.440 --> 0:05:14.200 of those services like Google Wave, Google Buzz, and Google Plus. 0:05:14.760 --> 0:05:19.159 So Google Talk g Chat was an instant messaging service 0:05:19.279 --> 0:05:22.560 nested within Gmail. You could pop into your Gmail account 0:05:22.960 --> 0:05:26.680 and send messages to your various contacts through Talk rather 0:05:26.720 --> 0:05:30.360 than type out a full email. Well, Google would later 0:05:30.440 --> 0:05:36.600 introduce a similar service called Hangouts, and in Google pushed 0:05:36.720 --> 0:05:42.520 Gmail users from Talk to Hangouts. However, Talk itself technically 0:05:42.640 --> 0:05:46.040 still stuck around, not really as its own thing. People 0:05:46.040 --> 0:05:50.760 weren't going to that independently that much. Instead, it was 0:05:50.880 --> 0:05:54.880 a platform that other apps depended upon, like Pigeon was 0:05:54.920 --> 0:05:57.039 one of those apps, p I, d G I N. 0:05:57.800 --> 0:06:02.080 But on the Google is finally pulling the plug on Talk. 0:06:02.520 --> 0:06:06.440 As for Hangouts, well, Hangout technically became Google Chat in 0:06:07.520 --> 0:06:10.440 so what will it be tomorrow? I don't even think 0:06:10.440 --> 0:06:13.640 Google knows the answer to that. Speaking of legacy services 0:06:13.680 --> 0:06:17.960 getting the plug pulled on them, let's talk about Internet Explorer, 0:06:18.320 --> 0:06:23.160 once the king of all web browsers, Microsoft will finally 0:06:23.320 --> 0:06:27.680 end all support for Internet Explorer tomorrow, which is June two, 0:06:28.080 --> 0:06:30.279 twenty two if you're listening to this news episode in 0:06:30.320 --> 0:06:34.520 the future. For some reason, I E first debuted in 0:06:36.240 --> 0:06:39.080 and it was a major part of Microsoft strategy as 0:06:39.120 --> 0:06:43.040 Windows was dominating the PC space. It was also a 0:06:43.080 --> 0:06:45.960 part of what would bring Microsoft under fire for anti 0:06:46.040 --> 0:06:50.279 competitive practices, as other organizations like Mozilla would argue that 0:06:50.360 --> 0:06:53.680 Microsoft was discouraging people from using any browser other than 0:06:53.760 --> 0:06:57.240 i E and that customers were being forced to buy 0:06:57.440 --> 0:06:59.960 two products even if they just wanted one, they had 0:07:00.000 --> 0:07:03.880 to get both Windows and Internet Explorer because they were 0:07:03.920 --> 0:07:08.160 bundled together, they were inseparable. So these were some arguments 0:07:08.200 --> 0:07:12.520 being made, and ultimately the initial court demanded that Microsoft 0:07:12.920 --> 0:07:15.840 not just stop all this, but that the company be 0:07:16.000 --> 0:07:19.320 broken up by the government because it was representing an 0:07:19.360 --> 0:07:23.920 anti competitive force of monopoly, but that decision would later 0:07:24.120 --> 0:07:28.520 be overturned on appeal. Anyway, i E was a dominant 0:07:28.520 --> 0:07:32.680 browser for a few years, although Chrome would eventually overtake 0:07:32.720 --> 0:07:36.560 and pass Internet Explorer around two thousand twelve, and from 0:07:36.560 --> 0:07:40.720 then on I E had a long slow decline. In 0:07:40.840 --> 0:07:44.440 twenty fift Microsoft introduced the Edge Browser, which was meant 0:07:44.440 --> 0:07:48.200 to be the successor to Internet Explorer, and Microsoft has 0:07:48.240 --> 0:07:51.720 been pulling support for i E through various platforms for 0:07:51.760 --> 0:07:53.800 the last couple of years, so this isn't like a 0:07:53.840 --> 0:07:57.440 massive surprise or anything, and tomorrow all support ends. I 0:07:57.560 --> 0:08:00.920 E is officially discontinued. I suspect some of you all 0:08:00.960 --> 0:08:04.040 listening have probably never even used Internet Explorer, And to you, 0:08:04.160 --> 0:08:07.280 I say, you aren't missing much. I mean, I do 0:08:07.360 --> 0:08:10.760 remember a time when a certain web based interface that 0:08:10.880 --> 0:08:14.120 I had to use was only compatible with Internet Explorer, 0:08:14.280 --> 0:08:16.080 and how frustrating that was. It was the only reason 0:08:16.120 --> 0:08:18.960 I would keep Internet Explorer on my computer. There was 0:08:19.040 --> 0:08:22.480 a CMS content management system that I had to work 0:08:22.520 --> 0:08:25.360 on about a decade ago, and it would only properly 0:08:25.400 --> 0:08:29.080 work with i E. That was frustrating. So yeah, there's 0:08:29.120 --> 0:08:33.079 some legacy systems that may still require i E because 0:08:33.559 --> 0:08:38.520 they never got updated to be more compatible with other browsers. 0:08:38.920 --> 0:08:41.680 But for the most part, you can say Internet Explorer 0:08:42.120 --> 0:08:45.720 is finally going to be dead as of tomorrow. Microsoft 0:08:45.760 --> 0:08:49.000 has entered into a labor neutrality agreement with the Communications 0:08:49.040 --> 0:08:52.480 Workers of America, That, in turn is the union that 0:08:52.559 --> 0:08:56.520 has been assisting Activision Blizzard employees in their various efforts 0:08:56.520 --> 0:09:00.560 to unionize. All right, so quick refresher. Activision Blizz is 0:09:00.600 --> 0:09:03.760 a massive video game company, and it has had a 0:09:03.840 --> 0:09:06.880 tumultuous couple of years for lots of reasons. I mean, 0:09:07.280 --> 0:09:10.120 there have been a largely negative reception to some of 0:09:10.120 --> 0:09:13.560 the high profile games the company has released recently, there 0:09:13.559 --> 0:09:17.680 have been serious and disturbing allegations regarding a toxic corporate 0:09:17.760 --> 0:09:23.240 culture that facilitates harassment and sexual discrimination, and the company 0:09:23.360 --> 0:09:28.840 has allegedly discouraged employees from organizing, essentially using union busting tactics. 0:09:29.200 --> 0:09:34.200 And of course, Microsoft is on track to acquire Activision Blizzard, 0:09:34.559 --> 0:09:38.720 which would seriously boost Microsoft's already impressive presence in gaming. 0:09:39.240 --> 0:09:42.280 So Microsoft agreeing to remain a neutral party is an 0:09:42.280 --> 0:09:47.400 important step for Activision Blizzard employees. Microsoft traditionally itself hasn't 0:09:47.440 --> 0:09:50.960 been super keen on unions, like a lot of other 0:09:51.040 --> 0:09:54.200 tech companies and companies in general really, but more recently, 0:09:54.600 --> 0:09:58.400 Brad Smith, the president of Microsoft, said that the company 0:09:58.440 --> 0:10:01.760 would be supportive of potential unions, and this will mean 0:10:01.800 --> 0:10:05.640 that once Microsoft completes its acquisition employees that Activision Blizzards 0:10:05.679 --> 0:10:10.160 should theoretically encounter no resistance or discouragement if they should 0:10:10.200 --> 0:10:14.000 wish to pursue organizing into a union. That's pretty encouraging 0:10:14.040 --> 0:10:17.200 news for those employees, although that acquisition still has to 0:10:17.200 --> 0:10:20.760 go through several more stages before it is official. Well, 0:10:20.840 --> 0:10:23.000 we've got some more news items to cover, but before 0:10:23.040 --> 0:10:35.720 we get to that, let's take a quick break. We're back. 0:10:36.320 --> 0:10:39.400 MAC rumors reports that LG is working on the second 0:10:39.520 --> 0:10:43.880 generation mixed reality headset for Apple, which is probably news 0:10:43.920 --> 0:10:45.760 to a lot of folks because Apple has yet to 0:10:45.840 --> 0:10:49.760 officially announced the first generation. Had said it's been a 0:10:49.880 --> 0:10:52.280 poorly kept secret for a few years now that Apple 0:10:52.320 --> 0:10:55.920 has been working on some sort of mixed reality hardware. However, 0:10:56.160 --> 0:11:00.439 we have never seen Apple acknowledged this publicly in any 0:11:00.480 --> 0:11:04.040 of its marketing events or conferences that it has held 0:11:04.360 --> 0:11:08.199 since those rumors started to circulate. Now that, in itself 0:11:08.320 --> 0:11:14.040 isn't unusual. Apple has a reputation for secrecy, and longtime 0:11:14.120 --> 0:11:17.400 Apple fans know that the company has sat on plans 0:11:17.440 --> 0:11:21.239 for years before finally being ready to move on them. 0:11:21.360 --> 0:11:24.559 That doesn't stop leaks from occasionally happening, sometimes from within 0:11:24.640 --> 0:11:28.880 Apple itself, sometimes it's through one of Apple's manufacturing partners, 0:11:28.920 --> 0:11:31.640 but anyway, the rumor is that l G is going 0:11:31.679 --> 0:11:34.800 to provide micro O l E D displays for the 0:11:34.920 --> 0:11:38.520 second generation headset, and that l G also contributed components 0:11:38.559 --> 0:11:42.640 to the first generation system. MAC Rumors says that, according 0:11:42.640 --> 0:11:46.760 to analyst Ming Chi Kuo, this second generation device will 0:11:46.800 --> 0:11:50.400 not hit the market until the second half of twenty 0:11:50.600 --> 0:11:54.480 twenty four. I'm sure several people were disappointed that Apple 0:11:54.600 --> 0:11:58.000 had made no mention of mixed reality during w w 0:11:58.240 --> 0:12:02.400 d C twenty twenty two, that's their Worldwide Developer Conference. 0:12:03.200 --> 0:12:06.160 But maybe we will finally get a glimpse of the 0:12:06.200 --> 0:12:10.040 mixed reality headset this fall, which is when Apple typically 0:12:10.080 --> 0:12:14.440 holds its iPhone event. Most rumors say that the mixed 0:12:14.440 --> 0:12:18.559 reality headset was going to be ready for sale by 0:12:18.559 --> 0:12:20.760 the end of this year, you know, for the holiday season. 0:12:21.240 --> 0:12:24.200 So if we don't see it by September, it sounds 0:12:24.200 --> 0:12:26.600 to me like it's not going to be a thing 0:12:26.679 --> 0:12:29.400 at all. So we'll have to wait and see. Telegram 0:12:29.440 --> 0:12:33.200 founder Pavel Durov is throwing hands at Apple, saying that 0:12:33.240 --> 0:12:37.800 the company purposefully restricts web app features. So here's what 0:12:38.000 --> 0:12:41.520 telegrams issue actually is. The messaging and chat service has 0:12:41.559 --> 0:12:45.320 an iOS app, but that app sometimes has issues because 0:12:45.440 --> 0:12:48.280 Telegram has kind of a hands off approach to moderation, 0:12:48.520 --> 0:12:53.160 it does not restrict content in public channels. That is 0:12:53.320 --> 0:12:57.160 bad form in the eyes of Apple. Apple wants content moderation. 0:12:57.360 --> 0:13:01.680 They want they want to ensure that the material being 0:13:01.720 --> 0:13:04.959 looked at on their phones meets Apple's high standards, even 0:13:05.000 --> 0:13:07.679 if it's not coming from Apple itself, So the Telegram 0:13:07.720 --> 0:13:11.640 app isn't the fully featured Telegram. However, Telegram also has 0:13:11.679 --> 0:13:14.720 a web based version that users could go to instead. 0:13:14.720 --> 0:13:18.720 They could just navigate there via Safari, but then Apple 0:13:18.760 --> 0:13:22.680 restricts all iOS developers to use the Apple WebKit, which 0:13:22.880 --> 0:13:27.000 means the web based version of Telegram is lacking certain 0:13:27.040 --> 0:13:31.559 features like push notifications, although the latest version of iOS 0:13:31.600 --> 0:13:35.720 will enable those. So in the UK, Apple faces more 0:13:35.760 --> 0:13:39.880 antitrust reviews, with various agencies and companies accusing Apple of 0:13:39.920 --> 0:13:43.719 purposefully restricting competitors from being able to provide alternatives to 0:13:43.800 --> 0:13:47.360 Apple's own services on iOS devices. That has been a 0:13:47.400 --> 0:13:51.520 major ongoing story for Apple, this battle with regulators, especially 0:13:51.520 --> 0:13:55.920 in the European Union. Meanwhile, the EU is also moving 0:13:55.960 --> 0:13:58.560 to hold big tech companies more accountable for creating and 0:13:58.640 --> 0:14:03.840 enforcing policies quote regarding impermissible manipulative behaviors and practices on 0:14:03.880 --> 0:14:07.480 their services based on the latest evidence on the conducts 0:14:07.480 --> 0:14:12.760 and tactics, techniques and procedures t tps employed by malicious 0:14:12.800 --> 0:14:16.720 actors end quote. So that includes stuff like misinformation campaigns 0:14:16.720 --> 0:14:19.080 that are pushed by legions of fake accounts, but it 0:14:19.120 --> 0:14:23.720 also includes more recent tactics things like deep fake images 0:14:23.800 --> 0:14:27.520 and deep fake videos. Should companies fail to adhere to 0:14:27.600 --> 0:14:30.480 this code, they could be liable for fines up to 0:14:30.640 --> 0:14:34.320 six percent of global turnover. And in this context you 0:14:34.320 --> 0:14:37.360 can think of turnover as more or less being global revenue. 0:14:37.800 --> 0:14:40.360 So for the really big, big tech companies out there, 0:14:40.400 --> 0:14:44.000 six percent would be in the billions of dollars neighborhood, 0:14:44.040 --> 0:14:47.920 which is serious stuff. So there are major companies that 0:14:47.960 --> 0:14:50.840 have already kind of agreed to these kind of of 0:14:51.000 --> 0:14:53.880 demands in the past, like Meta and Twitter. We'll have 0:14:53.960 --> 0:14:56.960 to see if that continues and what you know, what 0:14:57.120 --> 0:15:01.600 tactics the sites and services will employ to detect and 0:15:01.680 --> 0:15:04.560 remove this kind of content and the EU we've been 0:15:04.560 --> 0:15:06.760 seeing signs in the tech sector for a while now 0:15:06.800 --> 0:15:10.040 that companies are getting a bit concerned, from hiring freezes 0:15:10.080 --> 0:15:13.000 to layoffs two rescinded job offers. The trend appears to 0:15:13.000 --> 0:15:15.400 be a slow down in the tech industry as companies 0:15:15.440 --> 0:15:19.040 deal with a slowing economy. Since many analysts treat the 0:15:19.080 --> 0:15:21.360 tech sector is kind of a canary in a coal mine. 0:15:21.920 --> 0:15:24.680 This has led to predictions of a larger slowed down 0:15:24.760 --> 0:15:29.240 and downsizing in general across different industries, and startups might 0:15:29.280 --> 0:15:31.480 find it harder to get off the ground as investors 0:15:31.520 --> 0:15:34.440 have a more difficult time borrowing money that they can 0:15:34.440 --> 0:15:39.080 then pour into moonshot opportunities. So things are probably going 0:15:39.120 --> 0:15:41.760 to get worse before they get better. So I do 0:15:41.840 --> 0:15:44.240 have a couple of cool items to close out this episode. 0:15:44.600 --> 0:15:47.080 One is that researchers at M I T have developed 0:15:47.080 --> 0:15:49.760 a sensor that can tell the difference between bacterial and 0:15:49.920 --> 0:15:52.920 viral pneumonia. And you might think, well, what's the big 0:15:52.960 --> 0:15:56.680 deal there, Well, here's the problem. Pneumonia can be caused 0:15:56.680 --> 0:16:00.200 by either a bacterial infection or a viral infect action. 0:16:00.600 --> 0:16:04.200 There's not just one pathway to pneumonia. And you can 0:16:04.240 --> 0:16:08.000 treat a bacterial infection with antibiotics, but antibiotics do not 0:16:08.120 --> 0:16:10.800 have an effect on viruses, So doctors need a way 0:16:10.840 --> 0:16:15.280 to differentiate the type of infection that caused pneumonia in 0:16:15.400 --> 0:16:18.040 order to prescribe an effective treatment for it. Otherwise you 0:16:18.040 --> 0:16:20.680 can only treat the symptoms. Plus you know you don't 0:16:20.680 --> 0:16:25.080 want to overuse antibiotics, because through overuse, bacteria can develop 0:16:25.120 --> 0:16:28.960 immunity to those kinds of medications. That makes future treatments 0:16:29.040 --> 0:16:33.800 much more challenging. Anyway, the researchers created a nanoparticle sensor 0:16:34.200 --> 0:16:37.000 that looks for something really interesting rather than trying to 0:16:37.040 --> 0:16:39.920 seek out the pathogen itself, you know, that is, rather 0:16:39.960 --> 0:16:43.480 than looking for the root cause of the pneumonia, the 0:16:43.560 --> 0:16:48.080 sensors actually detect the body's response to the infection. The 0:16:48.160 --> 0:16:52.120 research team identified thirty nine different enzymes that react differently 0:16:52.200 --> 0:16:55.880 to different kinds of infections. So by detecting what the 0:16:55.920 --> 0:16:59.680 body is doing in response to the infection, the sensors 0:16:59.680 --> 0:17:03.360 can help scientists determine the nature of the infection itself. 0:17:03.560 --> 0:17:05.359 And I think that's a really cool way to tackle 0:17:05.400 --> 0:17:08.480 the problem. So far, the team has seen successful results 0:17:08.520 --> 0:17:11.240 while testing on mice. Of course, there's a pretty big 0:17:11.320 --> 0:17:14.080 leap between a mouse and a person, at least for 0:17:14.119 --> 0:17:16.320 most people, so a lot more work is going to 0:17:16.359 --> 0:17:17.840 have to be done to see if this method will 0:17:17.880 --> 0:17:21.440 translate to human patients. If it does, it could become 0:17:21.440 --> 0:17:24.439 a standard practice for treating pneumonia, as doctors determine if 0:17:24.480 --> 0:17:28.000 antibiotic or anti viral medication is best suited for the 0:17:28.040 --> 0:17:33.120 individual case. And finally, SpaceX is just a little bit 0:17:33.160 --> 0:17:36.920 closer to Mars. US regulators have sent SpaceX a message 0:17:37.160 --> 0:17:40.000 as long as the company can guarantee compliance with seventy 0:17:40.000 --> 0:17:44.959 five mitigating actions, the company's enormous starship rocket should receive 0:17:45.000 --> 0:17:48.800 clearance to blast off toward Mars from these regulators. So 0:17:48.880 --> 0:17:52.680 the mitigating actions range from stuff like ensuring local wildlife 0:17:52.680 --> 0:17:57.440 habitats remain protected, to cleaning up after launches, to even 0:17:57.480 --> 0:18:01.080 avoiding launches on weekends and holidays because as locals and 0:18:01.119 --> 0:18:03.359 Texas would like to be able to access the beach 0:18:03.440 --> 0:18:06.520 that's close to the launch site, and that beach would 0:18:06.520 --> 0:18:10.320 be shut down on any launch day, so just launched 0:18:10.359 --> 0:18:13.359 during the work week, you'll when people should be at work. Anyway, 0:18:13.920 --> 0:18:17.080 There's still more reviews to follow from other agencies, so 0:18:17.240 --> 0:18:21.200 this is not a signed deal. It's not carte blanche 0:18:21.240 --> 0:18:24.560 for SpaceX just yet. They're gonna have to pass safety 0:18:24.800 --> 0:18:27.960 tests and lots of other reviews before it can actually 0:18:28.160 --> 0:18:32.199 go forward with test launches of the spacecraft. But it 0:18:32.359 --> 0:18:34.800 is one more step towards the company getting permission to 0:18:34.840 --> 0:18:38.040 head off to the Red Planet, and that's it for 0:18:38.160 --> 0:18:41.320 the news for Tuesday, June fourteenth, two thousand twenty two. 0:18:41.560 --> 0:18:43.480 If you have anything you would like to send me, 0:18:43.560 --> 0:18:46.280 you can do so either with the talkback feature on 0:18:46.320 --> 0:18:48.600 the I heart Radio app. Just go to tech Stuff 0:18:49.000 --> 0:18:51.000 use a little microphone icon you can leave up to 0:18:51.080 --> 0:18:54.440 a thirty second voice message to me, or, as always, 0:18:54.440 --> 0:18:56.600 you can reach out on Twitter. The handle for the 0:18:56.600 --> 0:18:59.800 show is text stuff hs W and I will talk 0:18:59.840 --> 0:19:07.840 to you again really soon. Tech Stuff is an i 0:19:07.960 --> 0:19:11.600 heart Radio production. For more podcasts from I Heart Radio, 0:19:11.960 --> 0:19:15.119 visit the i Heart Radio app, Apple Podcasts, or wherever 0:19:15.200 --> 0:19:16.760 you listen to your favorite shows.