WEBVTT - Tech News: When is a nanometer not a nanometer? 0:00:04.400 --> 0:00:07.800 Welcome to tech Stuff, a production from I Heart Radio. 0:00:11.800 --> 0:00:14.680 Hey there, and welcome to tech Stuff. I'm your host, 0:00:14.760 --> 0:00:17.640 Jonathan Strickland. I'm an executive producer with I Heart Radio 0:00:17.720 --> 0:00:21.680 and how the tech area. It's time for the tech 0:00:21.760 --> 0:00:26.800 news for Tuesday, August twenty three, two thousand twenty two. 0:00:27.640 --> 0:00:32.880 Apple's semiconductor chip manufacturing company of choice which is t SMC, 0:00:33.240 --> 0:00:35.440 and to be fair, that's kind of the choice for 0:00:35.479 --> 0:00:39.440 pretty much every company that's making advanced chips and is 0:00:39.720 --> 0:00:41.880 a problem in its own right, but that's a matter 0:00:41.920 --> 0:00:45.599 for a different podcast episode. It is reportedly working on 0:00:45.640 --> 0:00:51.000 a three nanometer chip for upcoming MacBook computers. Now, the 0:00:51.040 --> 0:00:54.400 reason I decided to include this was because I wanted 0:00:54.400 --> 0:00:58.400 to do a little deconstruction on the nomenclature we use 0:00:58.600 --> 0:01:05.360 for chips, because it is wildly misleading. So for ages, 0:01:05.720 --> 0:01:12.000 the semiconductor industry has differentiated chips by using the size 0:01:12.240 --> 0:01:16.480 of nodes as the naming convention, and by nodes, we're 0:01:16.520 --> 0:01:21.200 really talking about the length of transistor gates. So the 0:01:21.319 --> 0:01:26.119 length of the transistor gate in whatever unit was an 0:01:26.160 --> 0:01:31.400 indicator of the chips sophistication. Generally, think speaking, you know, 0:01:31.480 --> 0:01:33.959 the more you can cram onto a chip, the more 0:01:34.000 --> 0:01:36.280 powerful the chip can be. That's not always the case, 0:01:36.840 --> 0:01:39.240 but that was kind of the rule of thumb. Now, 0:01:40.400 --> 0:01:43.039 does this mean that a three nanometer chip has a 0:01:43.040 --> 0:01:47.640 transistor gate that is three nanometers long. No, it does not, 0:01:48.440 --> 0:01:51.960 because for more than a decade, companies have shifted away 0:01:51.960 --> 0:01:58.040 from focusing on reducing components size almost exclusively and looked 0:01:58.080 --> 0:02:01.880 more at stuff like chip arc a texture and increasing 0:02:01.920 --> 0:02:05.480 the density of transistors and that sort of thing. So 0:02:05.960 --> 0:02:09.800 chips are still getting more powerful and more sophisticated, but 0:02:09.919 --> 0:02:13.720 the transistor gates aren't shrinking at the same crazy rate 0:02:13.760 --> 0:02:19.360 that they were before. However, the naming convention that we 0:02:19.520 --> 0:02:23.040 use where we use that transistor gate size as the 0:02:23.160 --> 0:02:27.480 name for the next generation of manufacturing processes, has stuck around. 0:02:27.880 --> 0:02:31.040 So if your transistor gates aren't getting that much smaller, 0:02:31.160 --> 0:02:35.000 but you're still dependent upon that that naming convention, then 0:02:35.400 --> 0:02:39.679 things rapidly stop measuring out. So that means that ten 0:02:39.760 --> 0:02:43.160 nanometer chip doesn't necessarily have transistor gates that are ten 0:02:43.240 --> 0:02:46.280 nanometers long. In fact, some of them have transistor gates 0:02:46.320 --> 0:02:49.560 that are nearly twice as long as that, so it's 0:02:49.600 --> 0:02:52.520 really just a naming convention. But a lot of folks 0:02:52.639 --> 0:02:55.519 think that this naming convention is dumb because for one thing, 0:02:55.600 --> 0:02:58.720 you know, it's not accurate. For another, since we keep 0:02:58.760 --> 0:03:02.079 going down, you know, we're reducing the size, and now 0:03:02.120 --> 0:03:06.520 we're talking about a three nanometer process. We're running out 0:03:06.560 --> 0:03:11.000 of nanometers. We're about to get down to the atomic scale, y'all. 0:03:11.120 --> 0:03:14.800 Because a nanometer is one billionth of a meter. And 0:03:14.840 --> 0:03:17.400 that also means that consumers have been really confused for 0:03:17.400 --> 0:03:21.760 a while and often draw the wrong conclusions because you 0:03:21.800 --> 0:03:24.880 can have a so called ten nanometer chip from Company 0:03:24.960 --> 0:03:29.239 A and a seven nanometer chip from Company B. And 0:03:29.360 --> 0:03:33.480 because there's this implication that the smaller number means more 0:03:33.480 --> 0:03:37.520 powerful chips, you would naturally think the seven nanometer chip 0:03:37.600 --> 0:03:41.000 is superior. But that's not necessarily true because we're really 0:03:41.040 --> 0:03:46.880 talking about things like architecture and power efficiency, and even 0:03:46.960 --> 0:03:49.360 the size of the components of the ten nanometer chip 0:03:49.440 --> 0:03:53.440 could be smaller than that on the seven nanometer chip. 0:03:53.440 --> 0:03:55.360 Because you're talking about two different companies and you're just 0:03:55.400 --> 0:03:59.120 talking about them using a naming convention to market a 0:03:59.160 --> 0:04:04.240 new generation of semi conductor chip, it isn't actually measuring anything, 0:04:04.880 --> 0:04:09.000 so a ten ter chip and a seven nimeter chip 0:04:09.040 --> 0:04:11.800 from two different companies could be made in such a 0:04:11.840 --> 0:04:14.800 way that the ten nimeter isn't always superior to the 0:04:14.880 --> 0:04:18.279 seven nanometer. That's why I can get confusing. It's this 0:04:18.480 --> 0:04:24.800 marketing strategy that creates confusion, and it perpetuates confusion. So yes, 0:04:24.839 --> 0:04:26.680 I just used a news story to give a quick 0:04:26.760 --> 0:04:29.600 lesson on why the semi conductor industry is using misleading 0:04:29.640 --> 0:04:32.440 marketing material and you should do research before you choose 0:04:32.440 --> 0:04:35.080 a processor and not just do it based off the 0:04:35.120 --> 0:04:41.719 supposed node size. Former Apple employee Xiao Lang Jong has 0:04:41.800 --> 0:04:45.560 pled guilty of charges of stealing proprietary information from Apple 0:04:46.080 --> 0:04:49.880 for the purposes of sharing it with another company, one 0:04:49.920 --> 0:04:54.679 in China for that matter. Now, this story actually started 0:04:54.680 --> 0:05:00.320 back in when Jong was first arrested. Jeong had turned 0:05:00.400 --> 0:05:04.120 to Apple after taking a trip to China, and then 0:05:04.200 --> 0:05:08.000 not long after his return, he resigned from Apple, and 0:05:08.040 --> 0:05:11.279 he also started sending corporate documents to his wife's computer, 0:05:12.080 --> 0:05:16.040 including documents that, in fact, as far as I can tell, 0:05:16.040 --> 0:05:21.599 exclusively focusing on documents related to Apple's worst kept secret. 0:05:22.120 --> 0:05:26.000 It's you know, autonomous electric vehicle project that everyone knows about, 0:05:26.000 --> 0:05:29.800 but Apple is never publicly at knowledge that included a 0:05:29.880 --> 0:05:33.400 twenty five page document with detailed schematics of a circuit 0:05:33.440 --> 0:05:37.800 board that Apple was designing for the vehicle. Moreover, Jeong 0:05:37.960 --> 0:05:40.440 had told Apple that he was going to return to 0:05:40.520 --> 0:05:42.719 China and he was also going to work for a 0:05:42.760 --> 0:05:46.240 company called ex Paying Motors, which is an electric vehicle 0:05:46.279 --> 0:05:51.920 manufacturing company that's also developing an autonomous vehicle. Jong had 0:05:51.960 --> 0:05:56.040 previously led not guilty to the charges after being arrested, 0:05:56.480 --> 0:05:59.200 but now he has changed his flea to guilty, and 0:05:59.240 --> 0:06:01.839 he faces up to ten years in prison and a 0:06:01.920 --> 0:06:05.680 fine of up to two fifty thousand bucks. And you 0:06:05.760 --> 0:06:09.520 might remember the story of former Google employee Anthony Lewandowski, 0:06:09.760 --> 0:06:13.520 whom Google accused of stealing documents from its autonomous car 0:06:13.560 --> 0:06:18.920 project that would become way Mo. Lewandowski subsequently worked for Uber, 0:06:19.240 --> 0:06:21.880 and that led to a nasty court battle between Google 0:06:21.920 --> 0:06:26.960 and Uber plus, Uber unceremoniously ending its relationship with Lewandowski. 0:06:27.480 --> 0:06:32.800 Lewandowski was subsequently tried and convicted of stealing documents, but 0:06:32.880 --> 0:06:36.400 then former President Trump pardoned Lewandowski on the last day 0:06:36.440 --> 0:06:39.920 of his presidency. Anyway, it looks like autonomous vehicle research 0:06:40.279 --> 0:06:44.120 is the hottest target for industrial espionage in tech right now, 0:06:44.360 --> 0:06:48.840 so I guess it's fashionable. A senior fellow for the 0:06:48.920 --> 0:06:54.040 Irish Council for Civil Liberties named Johnny Ryan has spearheaded 0:06:54.120 --> 0:06:57.800 a class action lawsuit in the United States targeting the 0:06:57.800 --> 0:07:01.920 computer technology company Oracle. Now, in case you're not familiar 0:07:01.960 --> 0:07:05.360 with Oracle, it is primarily a A B two B 0:07:05.760 --> 0:07:08.800 kind of company, a business to business like Its clients 0:07:08.800 --> 0:07:12.880 are other businesses, and it works in software and database 0:07:12.920 --> 0:07:17.040 management and cloud services as well as hardware. Ryan's lawsuit 0:07:17.120 --> 0:07:21.040 alleges that Oracle has illegally been collecting the information of 0:07:21.080 --> 0:07:27.320 around five billion people. Essentially that Oracle is assembling dossiers 0:07:27.400 --> 0:07:30.560 on folks, and those dossiers can contain information that includes 0:07:30.600 --> 0:07:37.760 stuff like names, physical addresses, email addresses, political views, purchase history, 0:07:38.240 --> 0:07:43.120 geolocation data, meaning that Oracle has been tracking people or 0:07:43.120 --> 0:07:46.640 at least has access to tracking information so they know 0:07:46.760 --> 0:07:50.880 where people have been, as well as records of online activity. 0:07:51.000 --> 0:07:55.200 So essentially all the personal data stuff that we talk 0:07:55.320 --> 0:07:59.560 about in other you know, news articles and such. So 0:07:59.720 --> 0:08:03.880 Ryan disclaiming Oracle is collecting all of that and organizing 0:08:03.880 --> 0:08:07.520 it into what he calls dossier's Ryan has brought this 0:08:07.600 --> 0:08:11.120 lawsuit to California, probably because that is the U s 0:08:11.120 --> 0:08:15.120 state that has the most strict privacy laws, and this 0:08:15.240 --> 0:08:18.240 is a massive endeavor. It's too early to say how 0:08:18.280 --> 0:08:20.960 it's all going to turn out, but some folks at 0:08:21.040 --> 0:08:23.200 least suspect that this is a push to encourage the 0:08:23.240 --> 0:08:26.960 United States to adopt stronger privacy laws more in line 0:08:27.000 --> 0:08:31.040 with what we see over in the European Union. Joshua 0:08:31.120 --> 0:08:34.160 Benton at Nieman Lab dot org has a great article. 0:08:34.280 --> 0:08:38.160 It's titled are you legally Liable for the contents of 0:08:38.240 --> 0:08:42.439 every web page You linked? To? Australia finally gets sensible? 0:08:43.200 --> 0:08:46.439 All right, some backstory on this. So back in the 0:08:46.480 --> 0:08:50.240 first decade of this millennium, I just hate saying. The 0:08:50.280 --> 0:08:55.040 early two thousand's, an Australian lawyer named George Defterros was 0:08:55.520 --> 0:09:00.200 arrested and charged with conspiring to commit murder. Defterro was 0:09:00.280 --> 0:09:03.679 known as a lawyer who represented people accused of belonging 0:09:03.720 --> 0:09:08.800 to organized crime gangs. Anyway, an Australian newspaper published an 0:09:08.880 --> 0:09:13.440 article about defter Ros, alleging that he was in fact 0:09:14.320 --> 0:09:17.920 part of this conspiracy and such, and Google ended up 0:09:18.000 --> 0:09:21.360 linking to that article and its search results because Google 0:09:21.480 --> 0:09:24.839 indexes the web, and when people do searches for things, 0:09:25.920 --> 0:09:29.840 you get the links. Right. Well, flash forward many many years. 0:09:30.520 --> 0:09:34.480 The lawyers representing Defterros, who by the way, had all 0:09:34.559 --> 0:09:37.720 charges dropped against him, so he did not he did 0:09:37.720 --> 0:09:42.240 not stand for those those charges they were dropped. His 0:09:42.320 --> 0:09:46.200 lawyers were seeking to have this article removed from the 0:09:46.400 --> 0:09:49.880 from the Internet, and they went to the newspaper and 0:09:49.960 --> 0:09:53.000 demanded that the newspaper removed the article, and the newspaper 0:09:53.040 --> 0:09:56.800 said no. So when that proved fruitless, they then went 0:09:56.800 --> 0:10:00.760 after Google, and their argument was that Google, by publishing 0:10:00.840 --> 0:10:06.400 a link to this article, was kind of endorsing the article, 0:10:06.840 --> 0:10:10.000 that Google itself was acting as a publisher, and that 0:10:10.120 --> 0:10:12.440 it was almost as if the offending piece had come 0:10:12.520 --> 0:10:17.600 from Google because it was linking to it. So that's 0:10:17.760 --> 0:10:21.360 kind of wild, right, like that a link can somehow 0:10:21.440 --> 0:10:26.280 imply that you're responsible for the material that the link 0:10:26.400 --> 0:10:31.040 goes to. While initially a court in Australia ruled that 0:10:31.080 --> 0:10:35.520 Google was in fact responsible, but then it got appealed. 0:10:35.559 --> 0:10:38.200 It went to Australia's High Court and the High Court 0:10:38.240 --> 0:10:41.840 has reversed that ruling and essentially said this is ludicrous. 0:10:41.880 --> 0:10:45.280 If we follow this logic, anyone who links to anything 0:10:45.320 --> 0:10:49.480 that is later claimed, not even proven, just claimed to 0:10:49.559 --> 0:10:54.000 be defamatory, shares responsibility and therefore could be sued for liabel. 0:10:55.240 --> 0:10:58.559 That seems pretty extreme, doesn't it that a link alone 0:10:59.040 --> 0:11:02.959 could make you respond constable for libel. So what if 0:11:03.000 --> 0:11:05.400 you were to come across a link to a story 0:11:05.559 --> 0:11:09.600 and you shared it on your social media plat platforms 0:11:09.640 --> 0:11:12.760 like on Facebook or on Twitter. Maybe you saw the story, 0:11:12.800 --> 0:11:15.000 you just thought it was interesting you wanted to share it. Well, 0:11:15.200 --> 0:11:18.760 if this earlier court ruling had been upheld, it would 0:11:18.760 --> 0:11:21.319 have said a precedent that suggests you could be found 0:11:21.320 --> 0:11:25.560 guilty of libel yourself just by sharing the link, and 0:11:25.600 --> 0:11:28.319 that you could potentially face charges for it even though 0:11:28.360 --> 0:11:32.439 you didn't write the supposed defamatory material. By the way, 0:11:32.679 --> 0:11:35.120 a big part of this story is that while the 0:11:35.240 --> 0:11:40.800 lawyers were claiming that the article was found to be defamatory, 0:11:40.880 --> 0:11:44.000 it never actually went to court. It was settled out 0:11:44.000 --> 0:11:49.800 of court. So because of that, the claims were spurious, 0:11:50.200 --> 0:11:54.320 and yet they still went through UH and got this 0:11:54.400 --> 0:11:57.400 initial decision by the court that was then overturned by 0:11:57.400 --> 0:12:02.080 the High Court. So it's good that the High Court 0:12:02.200 --> 0:12:04.920 saw this for what it was, or at least five 0:12:04.960 --> 0:12:07.320 of the seven judges saw it for what it was. 0:12:07.600 --> 0:12:10.600 Two of them dissented and argued that Google was in 0:12:10.679 --> 0:12:16.280 fact responsible. Not sure what they were thinking. Okay, we've 0:12:16.320 --> 0:12:18.439 got a few more news stories to go, but before 0:12:18.440 --> 0:12:29.600 we get to that, let's take a quick break. We're 0:12:29.679 --> 0:12:33.880 back US automaker Ford announced it is laying off three 0:12:33.920 --> 0:12:38.080 thousand employees and includes around two thousand salaried positions and 0:12:38.160 --> 0:12:41.440 one thousand contractors, and the company says this is all 0:12:41.520 --> 0:12:44.200 part of its strategy to pivot from focusing primarily on 0:12:44.240 --> 0:12:47.600 internal combustion engine vehicles and to change to put more 0:12:47.640 --> 0:12:52.880 emphasis on electric vehicle production. Ford CEO Jump Farley denies 0:12:52.960 --> 0:12:56.240 that the cuts are a cost saving move, but rather 0:12:56.720 --> 0:13:00.319 they indicate how Ford is serious about fundamentally each changing 0:13:00.320 --> 0:13:03.840 course by committing to the future of electric vehicles. My 0:13:03.920 --> 0:13:05.560 heart goes out to all the folks who got their 0:13:05.600 --> 0:13:09.920 walking papers. It is an increasingly tough job market, particularly 0:13:10.000 --> 0:13:13.960 when other auto manufacturers like Tesla have also been laying 0:13:13.960 --> 0:13:17.160 off employees or making other kinds of cost saving cuts. 0:13:17.840 --> 0:13:21.960 The CEO of the cryptocurrency exchange company Binance, says that 0:13:22.080 --> 0:13:26.320 LinkedIn is absolutely swarming with people falsely claiming to be 0:13:26.559 --> 0:13:31.319 Binance employees. And I'm not joking about swarming. He says. 0:13:31.520 --> 0:13:36.199 There are about fifty real profiles belonging to Finance employees 0:13:36.280 --> 0:13:41.520 on LinkedIn, but in total it's closer to seven thousand 0:13:41.800 --> 0:13:46.360 claimed Binance employees, which is a big old yauza. So 0:13:46.800 --> 0:13:50.280 why would people be lying about working for Binance, Well, 0:13:50.320 --> 0:13:54.439 it's probably part of crypto scams. The scammers are likely 0:13:54.520 --> 0:13:58.000 listing Finance on LinkedIn to give themselves a sense of 0:13:58.080 --> 0:14:02.400 legitimacy when they're talking to their marks, their targets. They're 0:14:02.440 --> 0:14:06.280 tricking people into pouring money into various schemes. They're usually 0:14:06.559 --> 0:14:08.760 types of Ponzi schemes. If you don't know what a 0:14:08.800 --> 0:14:12.840 Ponzi scheme is, it's a subset of pyramid schemes. So 0:14:12.880 --> 0:14:16.080 a scammer convinces a group of investors to pour money 0:14:16.120 --> 0:14:18.400 into you know, whatever it is, in this case, a 0:14:18.440 --> 0:14:22.800 cryptocurrency scheme. Then the scammera convinces a second round of 0:14:22.840 --> 0:14:27.640 investors to do the same, and then pays a percentage 0:14:27.680 --> 0:14:31.480 out to the first round of investors to keep them 0:14:31.480 --> 0:14:34.720 happy while pocketing the rest of the money, and then 0:14:34.760 --> 0:14:36.800 they keep going and so on and so forth, and 0:14:36.880 --> 0:14:40.880 effective scammers can often convince investors to reinvest into the scheme, 0:14:40.960 --> 0:14:43.920 so they take the money that they're supposedly getting paid 0:14:43.960 --> 0:14:46.440 out as the scheme is paying off, and they put 0:14:46.480 --> 0:14:49.080 it back into it, which just gives more money to 0:14:49.120 --> 0:14:53.400 the scammers. And ultimately these schemes all collapse in on themselves. 0:14:53.400 --> 0:14:57.800 They cannot sustain themselves forever. And so the Binance CEO 0:14:58.320 --> 0:15:01.680 is warning followers not to assume someone really is a 0:15:01.720 --> 0:15:04.560 finance employee just because it might say so on a 0:15:04.600 --> 0:15:08.560 LinkedIn account, particularly if that supposed employee is trying to 0:15:08.560 --> 0:15:11.680 coerce people into pouring money into a crypto investment scheme. 0:15:12.400 --> 0:15:16.240 This is pretty tricky because LinkedIn doesn't verify work or 0:15:16.360 --> 0:15:20.800 education history. They do claim to respond to reports of 0:15:21.040 --> 0:15:26.560 false accounts, and they say that they look for false accounts, 0:15:26.560 --> 0:15:31.120 but yeah, this is a If it's seven thousand fake 0:15:31.200 --> 0:15:34.680 ones out there, that's a that's a pretty big problem. 0:15:34.720 --> 0:15:37.480 And you know, folks, fib on resumes all the time. 0:15:37.520 --> 0:15:40.560 I get it, But this goes well beyond that. Japanese 0:15:40.600 --> 0:15:44.600 company Fujitsu has partnered with reik In, a research institute, 0:15:44.920 --> 0:15:47.920 with the intent of developing and selling a quantum computer 0:15:48.120 --> 0:15:51.920 boasting sixty four cubits starting next year. Now, to brush 0:15:52.000 --> 0:15:56.040 up on quantum computers, the fundamental unit of classical computers 0:15:56.240 --> 0:15:58.960 is the bit, and a bit can either be a 0:15:59.160 --> 0:16:02.480 zero or a one. The fundamental unit of information in 0:16:02.480 --> 0:16:06.800 a quantum computer is a cubit, which, thanks to quantum effects, 0:16:07.520 --> 0:16:10.040 can essentially be a zero and a one at the 0:16:10.120 --> 0:16:14.720 same time under specific circumstances. And I'm being very high 0:16:14.760 --> 0:16:18.480 level with this, but when paired with the right algorithms, 0:16:18.520 --> 0:16:21.680 that kind of computer, a quantum computer can potentially solve 0:16:21.760 --> 0:16:25.960 a subset of computer problems far faster than a classical 0:16:25.960 --> 0:16:32.640 computer can. Uh. It's essentially solving for all potential solutions 0:16:32.680 --> 0:16:36.360 at the same time and then presenting the one that 0:16:36.520 --> 0:16:40.720 is most likely to be the best. It deals with probabilities, 0:16:40.800 --> 0:16:45.400 not certainties. It gets very wibbly wobbly, but uh. It's 0:16:45.400 --> 0:16:48.360 also important to remember quantum computers are no better than 0:16:48.440 --> 0:16:51.840 classical computers for other types of applications, other types of 0:16:51.880 --> 0:16:54.920 computer problems. You would not be using a quantum computer 0:16:54.960 --> 0:16:58.800 as a gaming rig for example, but they do potentially 0:16:59.680 --> 0:17:04.600 have the ability to change really important things that we 0:17:04.680 --> 0:17:09.160 depend upon, like encryption in the near future. NASA has 0:17:09.240 --> 0:17:13.040 narrowed down potential future lunar landing sites to thirteen regions, 0:17:13.080 --> 0:17:15.040 all of which are not too far from the Moon's 0:17:15.080 --> 0:17:17.159 south pole. I like to think they were on the 0:17:17.280 --> 0:17:21.159 lunar equivalent to Zillo at the time. Scientists believe that 0:17:21.200 --> 0:17:23.720 the region is perfect for future Moon missions because the 0:17:23.720 --> 0:17:26.639 deep craters in the area could potentially hold hydrogen and 0:17:26.720 --> 0:17:30.320 water ice. That kind of stuff would be useful if 0:17:30.359 --> 0:17:33.120 you wanted to make your own rocket fuel, for example, 0:17:33.240 --> 0:17:36.080 or if you wanted to perhaps process water ice to 0:17:36.119 --> 0:17:39.719 create not just water, but maybe oxygen. This falls in 0:17:39.760 --> 0:17:42.240 line with the goals of the Artemis campaign, which has 0:17:42.280 --> 0:17:46.240 some really ambitious targets, including creating a base of operations 0:17:46.320 --> 0:17:49.880 suitable for long term stays on the Moon. NASA has 0:17:49.920 --> 0:17:51.960 been planning this out for years, and in fact, the 0:17:52.080 --> 0:17:56.120 launch of Artemis one, which will be an unscrewed Orion 0:17:56.400 --> 0:17:59.840 vessel on top of the Space Launch System, which is 0:17:59.880 --> 0:18:03.760 a super heavy lift launch vehicle, is scheduled to launch 0:18:03.960 --> 0:18:07.240 on Monday of next week. If everything goes to plan. 0:18:07.840 --> 0:18:10.560 The actual return mission to the Moon in which humans 0:18:10.560 --> 0:18:13.480 will head back up there. That one is designated as 0:18:13.640 --> 0:18:17.119 Artemis three. That's not expected to launch until twenty twenty 0:18:17.200 --> 0:18:21.359 five at the earliest. Sony has announced via Instagram of 0:18:21.400 --> 0:18:24.760 all Things that's new generation of VR hardware for the 0:18:24.760 --> 0:18:29.720 PlayStation console is likely to launch in early This generation 0:18:29.720 --> 0:18:32.440 of hardware is going to work with the PlayStation five. 0:18:32.520 --> 0:18:36.560 It's reportedly softer with better ergonomic design than the earlier 0:18:36.600 --> 0:18:40.439 generation of Sony's VR peripherals, and Sony says the headset 0:18:40.440 --> 0:18:43.440 will display graphics at a four thousand by two thousand 0:18:43.480 --> 0:18:47.320 forty resolution per eye that breaks down to two thousand 0:18:47.400 --> 0:18:50.359 by twenty and it will have a refresh rate of 0:18:50.440 --> 0:18:54.400 nineties slash hurts. It's also gonna have a c through mode, 0:18:54.400 --> 0:18:56.200 so if you get too close to the wall, it'll 0:18:56.240 --> 0:18:58.520 show you so you don't bump your nose in there. 0:18:59.359 --> 0:19:01.480 They have not have any information on how much it 0:19:01.480 --> 0:19:03.120 will cost. My guess is it will be a few 0:19:03.160 --> 0:19:07.720 hundred dollars um, So here's hoping that we find out soon. 0:19:07.800 --> 0:19:12.840 We know that it's coming in early, and that's about it. Well, 0:19:13.600 --> 0:19:18.439 that is the news for Tuesday, August two. Hope you 0:19:18.480 --> 0:19:21.280 are all well, make sure you reach out to me 0:19:21.359 --> 0:19:24.399 with any suggestions you have for future episodes of tech Stuff. 0:19:24.440 --> 0:19:26.240 You can do that on the I Heart Radio app 0:19:26.760 --> 0:19:29.840 or on Twitter at tech stuff H s W and 0:19:29.840 --> 0:19:39.480 I'll talk to you again really soon. Text Stuff is 0:19:39.520 --> 0:19:42.639 an I Heart Radio production. For more podcasts from my 0:19:42.800 --> 0:19:46.400 Heart Radio, visit the i Heart Radio app, Apple Podcasts, 0:19:46.520 --> 0:19:48.480 or wherever you listen to your favorite shows.