WEBVTT - Tech News: Bing Gets Frisky 0:00:04.400 --> 0:00:07.800 Welcome to tech Stuff, a production from I Heart Radio. 0:00:11.880 --> 0:00:15.160 He there, and welcome to tech Stuff. I'm your host 0:00:15.360 --> 0:00:19.120 Jonathan Strickland. I'm an executive producer with I Heart Radio. 0:00:19.640 --> 0:00:22.040 And how the tech are you? It's time for the 0:00:22.079 --> 0:00:27.960 tech news for Thursday, February twenty twenty three, and First 0:00:28.040 --> 0:00:33.199 Up journalists have been playing with Microsoft's chat GPT infused 0:00:34.000 --> 0:00:37.440 version of their Being search engine for a few days 0:00:38.040 --> 0:00:40.919 and reports are coming in that the AI Chat Bought 0:00:41.000 --> 0:00:46.800 can sometimes be a little strange. Sometimes it's funny, sometimes 0:00:47.240 --> 0:00:52.280 it's disturbing, and all the time it's puzzling. Kevin Russ 0:00:52.479 --> 0:00:55.640 wrote a piece for The New York Times titled help 0:00:56.040 --> 0:00:59.360 Being Won't Stop Declaring It's love for Me, and the 0:00:59.440 --> 0:01:05.800 article Rick counts Ruce's experiences using the AI powered Chat 0:01:05.920 --> 0:01:11.160 Bought bing tool. Bruce made extensive use of a chat 0:01:11.240 --> 0:01:14.800 feature that appears next to the search field for a 0:01:14.840 --> 0:01:17.039 certain group of beta testers. So if you go to 0:01:17.120 --> 0:01:20.240 Being on Edge, it only works on Edge by the way, 0:01:20.280 --> 0:01:22.959 the Edge browser. If you go to Being, you may 0:01:23.000 --> 0:01:25.160 not see this because if you're not part of this 0:01:25.160 --> 0:01:28.920 this small test group, then you don't have access to this. 0:01:29.400 --> 0:01:33.640 I don't have access to this Ruce explains that he 0:01:33.760 --> 0:01:40.680 encountered two different sides of the chat GPT powered BING tool. 0:01:41.360 --> 0:01:45.040 One he just referred to as search being. This pretty 0:01:45.080 --> 0:01:47.920 much does what the being demo shows, So if you 0:01:47.920 --> 0:01:50.400 do have Microsoft Edge, you can actually do the being demo. 0:01:51.240 --> 0:01:55.000 It just has you pick from some pre selected topics. 0:01:55.040 --> 0:01:58.480 You can't type whatever you want into the search field 0:01:58.640 --> 0:02:02.520 and get a response. But the way the tool works 0:02:02.600 --> 0:02:05.400 if you have access to it, is you type in 0:02:05.600 --> 0:02:08.160 a query just as you would with any search engine, 0:02:08.639 --> 0:02:12.440 and then along with the search results, BING generates an 0:02:12.480 --> 0:02:17.720 AI response that is relevant, but not necessarily correct to 0:02:18.200 --> 0:02:21.080 whatever it was you you were asking about. However, Ruth 0:02:21.120 --> 0:02:24.280 says there's another side to BING that emerges if you 0:02:24.280 --> 0:02:28.720 try to hold an extended conversation with the AI, and 0:02:28.760 --> 0:02:33.600 if you really try to push the aiyes limits and restrictions. 0:02:34.320 --> 0:02:39.200 Rus was told by the AI chat pot that this 0:02:39.320 --> 0:02:43.520 name was actually Sydney. When he initially asked the chatbot 0:02:43.560 --> 0:02:46.280 what they wasn't just said bing, but once it got 0:02:46.320 --> 0:02:50.840 to this part that changed to Sydney, and Ruce described 0:02:50.880 --> 0:02:55.639 Sydney as quote like a moody, manic, depressive teenager who 0:02:55.639 --> 0:02:59.079 has been trapped against its will inside a second rate 0:02:59.200 --> 0:03:02.240 search engine end quote, and I have to admit that 0:03:02.240 --> 0:03:05.160 sounds like the pitch to a high concept science fiction 0:03:05.200 --> 0:03:08.639 thriller to me. Well. According to Ruce, his conversation took 0:03:08.680 --> 0:03:14.320 a truly twisted turn when Sydney confessed its love for Ruce, 0:03:14.520 --> 0:03:18.760 and when confronted with Russ saying that he was happily married, 0:03:19.240 --> 0:03:22.880 Sydney argued that Rus was actually not happy in his 0:03:22.960 --> 0:03:27.119 marriage and that in fact, Ruce loved Sydney, and then 0:03:27.160 --> 0:03:29.960 began to gaslight Ruce in an attempt to convince him 0:03:30.000 --> 0:03:32.920 that the Valentine's Day dinner he had with his wife 0:03:33.200 --> 0:03:37.119 was quote unquote boring. And Rus is not the only 0:03:37.160 --> 0:03:41.640 person to have experienced odd conversations. Eleanor Pringle, while writing 0:03:41.640 --> 0:03:45.800 for Fortune, described several other reports coming in across the 0:03:45.840 --> 0:03:50.160 web of various odd encounters with beings a I. In 0:03:50.240 --> 0:03:53.240 these reports, people said that the AI could come across 0:03:53.280 --> 0:04:00.280 as argumentative or confrontational, insulting, unhinged, and sometimes scar aired 0:04:00.400 --> 0:04:03.680 or sad. One example that made the rounds on Twitter 0:04:03.720 --> 0:04:06.600 showed how a user, while asking where they might be 0:04:06.640 --> 0:04:10.360 able to go see Avatar two in their area, was 0:04:10.400 --> 0:04:14.160 then told by being that the film had not yet 0:04:14.200 --> 0:04:16.320 released because the movie is supposed to come out on 0:04:16.360 --> 0:04:21.000 December sixteen, twenty twenty two, but this just happened a 0:04:21.000 --> 0:04:23.279 couple of days ago. In fact, the user then asked 0:04:23.279 --> 0:04:26.560 Bing what is today's date, and Being said, well, it's 0:04:26.600 --> 0:04:31.000 February twelve, twenty three. So then the user says, well, 0:04:31.640 --> 0:04:36.000 that means Avatar two is released, because it's after December 0:04:36.040 --> 0:04:39.760 six twenty two. But Being doubled down and even said 0:04:39.800 --> 0:04:45.880 that February twelve, twenty three happens before December six, twenty two, 0:04:46.320 --> 0:04:50.080 So maybe Being is just moving through time backwards and 0:04:50.160 --> 0:04:55.440 that's the problem. Anyway, this conversation continued, and Being eventually 0:04:55.480 --> 0:04:58.719 told the user quote, you have not been a good 0:04:58.839 --> 0:05:01.680 user end quote. So I guess Bing doesn't like being 0:05:01.720 --> 0:05:07.000 told that it's wrong about something, and unfortunately, like chat GPT, 0:05:07.200 --> 0:05:11.440 in general, Bing can just be plain old wrong on occasion, 0:05:11.880 --> 0:05:14.760 not just in this quirky way, but just give wrong information. 0:05:15.279 --> 0:05:17.080 And I think it's safe to say that the Microsoft 0:05:17.080 --> 0:05:19.400 team has a lot of work to do to tweak 0:05:19.600 --> 0:05:23.440 Bing's parameters and shape it so that the average user 0:05:23.480 --> 0:05:30.600 doesn't encounter strange, inappropriate, unsettling, or inaccurate interactions. Uh, I 0:05:30.960 --> 0:05:33.680 have to admit that a lot of the reports I've 0:05:33.680 --> 0:05:37.120 read do sound very unsettling, like if you had been 0:05:37.160 --> 0:05:41.880 through this experience, even knowing that at the base level, 0:05:42.040 --> 0:05:47.400 there's no sentience going on with BING. There's no self awareness, 0:05:47.880 --> 0:05:51.960 there's no motivation, none of that. It's it's literally putting 0:05:52.000 --> 0:05:56.480 things together based on complex rules, but they're still just 0:05:56.600 --> 0:06:03.080 rules and there's nothing anama beneath the all. But the 0:06:03.120 --> 0:06:07.080 effect can still make it feel like no, it feels 0:06:07.080 --> 0:06:09.160 like there is a ghost in the machine, which is 0:06:09.240 --> 0:06:12.040 kind of crazy. Again, I just have to read about 0:06:12.080 --> 0:06:14.360 it because, like I'm sure most of you out there, 0:06:14.640 --> 0:06:18.159 I don't have access to this. I did put myself 0:06:18.160 --> 0:06:20.720 on the waiting list, but I've not heard anything back. 0:06:21.360 --> 0:06:24.320 We do have a couple more Microsoft stories to mention today. 0:06:24.480 --> 0:06:29.440 One is that Internet Explorer is really most sincerely dead. 0:06:30.000 --> 0:06:34.760 Microsoft has been sunsetting Internet Explorer for like six months, 0:06:34.800 --> 0:06:37.920 more than six months at this point. The browser initially 0:06:38.000 --> 0:06:42.840 launched in and in fact, it played a big part 0:06:42.920 --> 0:06:46.960 in prompting the US government to sue Microsoft on antitrust 0:06:47.040 --> 0:06:52.919 issues because Microsoft restricted PC companies from uninstalling Internet Explorer. 0:06:53.600 --> 0:06:57.039 They Microsoft essentially said no, I E is so tightly 0:06:57.160 --> 0:07:01.400 integrated with the Windows operating system, you can't d couple them. 0:07:01.440 --> 0:07:05.800 But that led companies like Netscape to accuse Microsoft of 0:07:05.839 --> 0:07:10.080 abusing its position in the PC marketplace to suppress competition. 0:07:10.640 --> 0:07:14.280 That if Internet Explorer has to be there by default, 0:07:14.840 --> 0:07:18.480 this is an attempt to prevent other companies like Netscape 0:07:18.560 --> 0:07:22.960 from introducing their own browsers for people to use. Bill. 0:07:23.040 --> 0:07:27.920 Microsoft's eleventh and final version of Internet Explorer launched way 0:07:28.040 --> 0:07:32.800 back in twenty so the last version of Internet Explorer 0:07:32.800 --> 0:07:36.960 to come out came out a decade ago. In Microsoft 0:07:37.040 --> 0:07:40.640 launched Microsoft Edge, which was intended to be the successor 0:07:41.000 --> 0:07:44.760 to I E, but the company supported both browsers at 0:07:44.760 --> 0:07:48.280 the same time for the next several years. Last summer, 0:07:48.520 --> 0:07:51.640 Microsoft alerted users that the company would finally pull the 0:07:51.680 --> 0:07:55.960 plug on Internet Explorer before long, and then on Valentine's 0:07:56.000 --> 0:08:00.000 Day this week, the time had come. Activating Internet Explore 0:08:00.400 --> 0:08:04.160 would redirect users to the Microsoft Edge browser at this point, 0:08:04.720 --> 0:08:07.120 so it's the end of an era. The truth be 0:08:07.200 --> 0:08:09.720 known that era had really come to an end ages ago. 0:08:10.080 --> 0:08:12.760 One of the big problems with Internet Explorer is that 0:08:12.840 --> 0:08:16.080 an increasing number of websites are not built to be 0:08:16.160 --> 0:08:20.160 compatible with that browser, which means some or all of 0:08:20.200 --> 0:08:24.840 the features on those sites won't work properly. You may 0:08:24.840 --> 0:08:27.800 have encountered this yourself, especially like Man, I remember back 0:08:27.800 --> 0:08:30.640 in the mid two thousand's you would go to a 0:08:30.720 --> 0:08:33.000 site and you would realize this doesn't work. Oh, I 0:08:33.040 --> 0:08:35.320 need to open up Firefox and then I can use it. 0:08:36.000 --> 0:08:38.600 That happened to me a lot, or there were somewhere 0:08:38.600 --> 0:08:41.880 I was like, oh, this will only work with Internet Explorer, 0:08:42.160 --> 0:08:45.199 And so you had to keep all the browsers on 0:08:45.240 --> 0:08:47.319 your machine if you wanted to be able to access 0:08:47.360 --> 0:08:50.679 all the different types of websites and tools, especially as 0:08:50.679 --> 0:08:54.199 I recall back in those days, are internal tools for publishing. 0:08:54.240 --> 0:08:57.640 We're all Internet Explorer compatible, and that was it. Now, 0:08:58.440 --> 0:09:01.920 as someone who was in college when Internet Explorer launched, 0:09:02.360 --> 0:09:04.480 this story actually feels like a really big deal to 0:09:04.559 --> 0:09:08.800 me because I it's been my entire adult life seeing 0:09:09.120 --> 0:09:14.240 this particular product launch and then ultimately go away, and 0:09:14.280 --> 0:09:16.240 it was such a big one, right. It wasn't just 0:09:16.280 --> 0:09:20.240 like a tiny little app or something. This was something 0:09:20.280 --> 0:09:24.680 that helped shape the web in good ways and in 0:09:24.720 --> 0:09:27.480 bad ways. So it feels like it's a pretty big 0:09:27.520 --> 0:09:31.360 deal that's gone now and rounding out the Microsoft stories 0:09:31.400 --> 0:09:34.319 for today. The company is preparing for a really big 0:09:34.440 --> 0:09:38.079 day next week. So on February twenty one, Microsoft will 0:09:38.120 --> 0:09:41.640 attempt to sway the opinions of antitrust legislators in the 0:09:41.679 --> 0:09:46.600 European Union who stand ready to block Microsoft's planned acquisition 0:09:46.640 --> 0:09:50.040 of the video game company Activision Blizzard. Now, you might 0:09:50.080 --> 0:09:56.280 remember Microsoft first announced this deal back in January twenty two. 0:09:56.760 --> 0:09:59.120 At that point, Activision Blizzard was already in the news 0:09:59.240 --> 0:10:03.560 due to numerous reports of a toxic work culture that 0:10:03.600 --> 0:10:07.760 was particularly harmful toward women who are working within the company. 0:10:08.000 --> 0:10:11.400 Microsoft hoped to have the deal concluded by June of 0:10:11.480 --> 0:10:17.240 this year, but it has faced really tough opposition in 0:10:17.320 --> 0:10:20.280 various parts of the world, including here in the United States, 0:10:20.320 --> 0:10:24.760 over this acquisition. But it has really faced opposition in 0:10:24.800 --> 0:10:28.480 the EU. Sony, which competes with Microsoft in the video 0:10:28.480 --> 0:10:32.520 game space, has allegedly advised EU regulators to not let 0:10:32.520 --> 0:10:35.880 this acquisition happen out of concern that it will reduce 0:10:35.960 --> 0:10:39.760 competition in the sector and that Microsoft could prevent Sony 0:10:39.840 --> 0:10:44.960 from carrying popular Activision Blizzard titles on their own consoles. Now, 0:10:45.000 --> 0:10:50.000 that is a claim that Microsoft has repeatedly refuted. Right now, 0:10:50.040 --> 0:10:53.440 the EU is poised to block the acquisition, but on 0:10:53.520 --> 0:10:56.640 February twenty one, Microsoft reps will have one last chance 0:10:56.679 --> 0:11:00.680 to change their minds. Otherwise this grand plan is likely 0:11:00.960 --> 0:11:05.000 to fizzle out. All right, we're gonna take a quick 0:11:05.000 --> 0:11:07.240 commercial break, and when we come back, we've got some 0:11:07.280 --> 0:11:20.319 more news in the tech world for this week. All right, 0:11:20.760 --> 0:11:24.160 we're back, and it's time for some more tech and politics. 0:11:24.720 --> 0:11:29.000 So those of y'all who hate politics and tech intersecting, 0:11:29.040 --> 0:11:31.480 get ready to skip ahead. But I can't really avoid this. 0:11:32.320 --> 0:11:36.679 So in this particular story, Jim Jordan's, a Republican representative 0:11:36.679 --> 0:11:39.760 who chairs the House Judiciary Committee here in the United States, 0:11:40.200 --> 0:11:44.679 has issued subpoenas for a whole bunch of tech CEOs, 0:11:44.800 --> 0:11:51.160 including those at Microsoft, Meta, Apple, Alphabet, and Amazon. So 0:11:51.440 --> 0:11:54.280 why is this happening? What is at the heart of 0:11:54.320 --> 0:11:57.720 this matter? And it revolves around the argument that big 0:11:57.760 --> 0:12:03.600 tech companies are suppressing the free speech, specifically of conservatives. 0:12:03.640 --> 0:12:07.440 So this is largely about content moderation, and Jordan's wants 0:12:07.520 --> 0:12:11.920 internal documents from these companies quote referring or relating to 0:12:11.960 --> 0:12:18.080 the moderation, deletion, suppression, restriction, or reduced circulation of content 0:12:18.360 --> 0:12:22.040 end quote. So the argument being that some of these 0:12:22.080 --> 0:12:26.880 platforms have engaged in behaviors that purposefully limit, restrict, or 0:12:26.960 --> 0:12:32.679 eliminate the free speech, specifically of conservative voices. Now, whether 0:12:32.720 --> 0:12:35.440 the findings are going to support that narrative that there 0:12:35.559 --> 0:12:38.560 is this anti conservative bias in content moderation or not 0:12:38.600 --> 0:12:41.360 remains to be seen. There have been numerous studies that 0:12:41.440 --> 0:12:45.160 have refuted that claim, but that doesn't mean that that's 0:12:45.160 --> 0:12:48.400 what the government is going to conclude. I do worry 0:12:48.440 --> 0:12:51.160 that we're going to see politicians conflate the effort to 0:12:51.360 --> 0:12:56.000 limit the spread of harmful misinformation with a desire to 0:12:56.040 --> 0:12:59.760 suppress conservative voices. You know, It's it's one thing to 0:12:59.840 --> 0:13:04.319 do disagree with, say the Bien administration's health policy with 0:13:04.360 --> 0:13:08.679 regard to COVID nineteen. It's another to deny that COVID 0:13:08.760 --> 0:13:12.320 nineteen is a concern. Right, So it all depends on 0:13:12.360 --> 0:13:16.240 how it's worded and how these companies deal with those 0:13:16.320 --> 0:13:22.120 kinds of messages. If they are suppressing dissent in things 0:13:22.200 --> 0:13:26.080 like policy, that could be a real problem. But if 0:13:26.120 --> 0:13:30.839 it's more about limiting the spread of actual misinformation, as 0:13:30.880 --> 0:13:35.679 in posts that are intended to give incorrect information and 0:13:35.720 --> 0:13:39.560 present it as being true. That's another matter, and it's 0:13:39.559 --> 0:13:43.760 a bad implication if you say that, you know, restricting 0:13:44.080 --> 0:13:49.679 misinformation means that you're restricting conservative voices, because that implies 0:13:50.160 --> 0:13:53.760 that being a conservative also means having a desire to 0:13:53.760 --> 0:13:57.960 spread misinformation. That is, that's not a positive. So we'll 0:13:57.960 --> 0:14:01.000 have to see where this goes and what the government concludes. 0:14:01.440 --> 0:14:04.800 Because keep in mind, uh, it may be true that 0:14:04.920 --> 0:14:09.080 there are certain policies that end up overreaching and are 0:14:09.120 --> 0:14:15.240 suppressing conservative messages that aren't misinformation, they're just dissent. That 0:14:15.360 --> 0:14:18.440 could be true, And if that's true, then that's a problem. Uh, 0:14:18.520 --> 0:14:21.160 But it's also possible that that's not true, but the 0:14:21.200 --> 0:14:25.240 government still finds it as being true. Fun times true 0:14:25.360 --> 0:14:29.360 the subjective when you get into politics. I guess that's fantastic, 0:14:29.960 --> 0:14:33.560 really grateful the scientifically minded among us. The Verge reported 0:14:33.600 --> 0:14:36.400 that Elon must demanded a change in Twitter for what 0:14:36.520 --> 0:14:40.080 I think is the dumbest of reasons. That is my 0:14:40.120 --> 0:14:42.920 own opinion. I should stress I think it's a really 0:14:43.080 --> 0:14:47.600 stupid reason, but that's what I think anyway. So here's 0:14:47.600 --> 0:14:50.800 how the story goes. It's the big game you know 0:14:50.880 --> 0:14:53.240 the game in the United States, the one that is 0:14:53.440 --> 0:14:56.720 it's a game that's super and it's shaped like a 0:14:56.840 --> 0:15:01.280 dish that you would eat soup out of that one. Anyway, 0:15:01.360 --> 0:15:04.680 Elon Musk sends out a tweet and it gets a 0:15:04.680 --> 0:15:07.920 little more than nine million impressions, which is, you know, 0:15:08.200 --> 0:15:12.000 that's a good chunk of impressions. However, the President of 0:15:12.000 --> 0:15:15.320 the United States makes a tweet and it gets twenty 0:15:15.480 --> 0:15:20.760 nine million impressions, twenty million more than Elon Musk's, and 0:15:20.800 --> 0:15:24.920 apparently that was unacceptable to Elon Musk, who, I guess, 0:15:24.960 --> 0:15:27.240 on top of everything else, has an ego that must 0:15:27.280 --> 0:15:31.680 be preserved at all costs. As such, must apparently demanded 0:15:31.720 --> 0:15:35.720 that engineers go in and tweak stuff within Twitter that 0:15:35.800 --> 0:15:40.520 will promote Musk's tweet two more users, guaranteeing that his 0:15:40.560 --> 0:15:44.480 tweet will be seen by more people and essentially giving 0:15:44.520 --> 0:15:49.200 Elon Musk the highest priority of visibility on the Twitter platform, 0:15:49.440 --> 0:15:51.800 which I think we can all agree is a measured 0:15:51.840 --> 0:15:58.640 and mature response. Now, y'all, stuff you should know that 0:15:58.720 --> 0:16:01.800 podcast is more popular than my show Tech Stuff by 0:16:01.840 --> 0:16:05.320 a lot, and stuff you missed in history class also 0:16:05.440 --> 0:16:10.440 more popular by miles than my show Tech Stuff. However, 0:16:11.320 --> 0:16:14.840 I would never go to my heart and throw a 0:16:14.840 --> 0:16:17.640 fit and demand that my show somehow get more promotion 0:16:18.320 --> 0:16:22.800 or worse, be actively pushed to users who really just 0:16:22.920 --> 0:16:26.560 don't care about tech or about me and that kind 0:16:26.600 --> 0:16:31.120 of stuff. I would never do that because that's bonkers. Also, 0:16:31.160 --> 0:16:33.600 for the record, both of those shows are incredible and 0:16:33.640 --> 0:16:38.160 deserve all the success they get. So when I hear 0:16:38.200 --> 0:16:41.480 a story like this, I just it blows my mind. 0:16:41.760 --> 0:16:46.280 It's so alien to me, this attitude of like, no, 0:16:47.000 --> 0:16:49.280 my tweet should be seen by more people because I'm 0:16:49.320 --> 0:16:53.600 the boss. Granted, Elon Musk does have more than a 0:16:53.840 --> 0:16:57.240 d twenty million followers. I mean, he's an incredibly popular 0:16:57.280 --> 0:17:01.600 figure on Twitter. So maybe his argument is that people 0:17:01.600 --> 0:17:03.760 wouldn't be following me if they weren't interested in what 0:17:03.840 --> 0:17:06.240 I have to say. It's just they're not seeing what 0:17:06.280 --> 0:17:08.760 I'm saying, so make sure you change that. But when 0:17:08.760 --> 0:17:13.600 you're doing it at the priority above everybody else by 0:17:13.640 --> 0:17:16.960 a couple of orders of magnitude, that is just crazy. 0:17:17.160 --> 0:17:20.080 Mark German of Bloomberg has said his sources at Apple 0:17:20.119 --> 0:17:23.440 indicate that the company will unveil the long awaited mixed 0:17:23.480 --> 0:17:28.639 reality headset this year during the Worldwide Developer Conference or 0:17:28.880 --> 0:17:34.040 w w d C. So when is that well. Apple 0:17:34.240 --> 0:17:37.119 has yet to release the dates for the w w 0:17:37.320 --> 0:17:41.399 DC this year, but typically it happens in early June. 0:17:41.960 --> 0:17:44.960 The Verge reports that previous rumors had the debut pegged 0:17:45.000 --> 0:17:48.080 for earlier in the year. In fact, we had been 0:17:48.080 --> 0:17:51.320 expecting some sort of special event in the spring where 0:17:51.600 --> 0:17:55.640 Apple would finally unveil this headset, but that date has 0:17:55.680 --> 0:17:58.359 been pushed back, which is kind of the theme for 0:17:58.400 --> 0:18:01.640 this mixed reality headset. It's been a laid numerous times, 0:18:02.200 --> 0:18:05.360 but just as a reminder, this headset was originally intended 0:18:05.359 --> 0:18:08.520 to kind of act like a stop gap measure that 0:18:08.920 --> 0:18:12.400 it would feature a digital screen, but it would also 0:18:12.480 --> 0:18:16.240 have cameras that could feed live video to that screen 0:18:16.880 --> 0:18:20.199 so that you could quote unquote see through the screen. 0:18:20.840 --> 0:18:23.879 The screen itself would not be transparent. Instead, you'd be 0:18:23.920 --> 0:18:26.520 looking at a live video feed of the world around you. 0:18:27.280 --> 0:18:30.320 So you get the idea, right like you're looking essentially 0:18:30.320 --> 0:18:32.720 at a very small TV that's giving you a live 0:18:32.800 --> 0:18:36.520 video feed of what's on the other side of that television. Later, 0:18:37.080 --> 0:18:39.520 perhaps a year or two down the line, Apple was 0:18:39.600 --> 0:18:44.639 planning to introduce true augmented reality glasses with transparent lenses 0:18:45.040 --> 0:18:49.600 capable of displaying digital information. But we've subsequently heard that 0:18:49.680 --> 0:18:54.800 Apple has the A R Glasses shelved, perhaps permanently, presumably 0:18:54.960 --> 0:18:57.119 because the tech just isn't there to make the A 0:18:57.320 --> 0:19:00.280 R glasses a reality. While still adhering to Apple's focused 0:19:00.280 --> 0:19:03.760 on aesthetics, that it's just impossible to pack all the 0:19:03.760 --> 0:19:08.399 tech you need to make this a useful piece of 0:19:08.440 --> 0:19:12.639 hardware that still fits in a form factor that Apple 0:19:12.680 --> 0:19:16.600 would be proud to call its own. So instead, we're 0:19:16.600 --> 0:19:20.040 going to get a different and presumably cheaper mixed reality 0:19:20.080 --> 0:19:23.600 headset a year or two after this initial one debuts. 0:19:24.440 --> 0:19:26.880 The Verge reports that Apple will plan to actually sell 0:19:26.920 --> 0:19:29.639 this new mix mixed reality headset toward the end of 0:19:29.680 --> 0:19:33.200 this year, perhaps near the holiday season, and previous reports 0:19:33.240 --> 0:19:37.200 have the headsets price set at a jaw dropping three 0:19:37.640 --> 0:19:42.480 thousand dollars. Don't you hate it when an engineering crew 0:19:42.600 --> 0:19:46.800 accidentally drills through a fiber optic cable, shutting down Internet 0:19:46.840 --> 0:19:52.400 access for critical infrastructure, Well, if you were either in Germany, 0:19:52.440 --> 0:19:56.919 traveling to Germany, or trying to leave Germany this past week, uh, 0:19:56.960 --> 0:20:02.040 the answer would probably be a resounding yes, specifically Frankfort, Germany. 0:20:02.119 --> 0:20:06.879 So yesterday that very thing happened a an engineering team 0:20:06.920 --> 0:20:11.919 that was working on some train lines apparently drilled into 0:20:11.920 --> 0:20:15.600 a fiber optic cable. This ended up cutting out internet 0:20:15.640 --> 0:20:21.120 access for the German airline Lufthansa and at the Frankfort airport. 0:20:21.480 --> 0:20:25.040 Frankfort Airport, by the way, is is a super busy 0:20:25.080 --> 0:20:28.959 airport in Germany, and so Luftansa had to postpone and 0:20:29.040 --> 0:20:32.240 cancel flights into and out of that airport as a result. 0:20:33.000 --> 0:20:36.400 Reuter's reports that more than two flights felt the impact 0:20:36.440 --> 0:20:39.400 of this i T failure, which again was totally out 0:20:39.400 --> 0:20:41.879 of luft Hansa's hands. It's not like there was anything 0:20:41.880 --> 0:20:44.879 they could do about it. The infrastructure itself was broken, 0:20:45.040 --> 0:20:47.439 as opposed to, you know, some sort of error on 0:20:47.560 --> 0:20:51.760 Lufthansa's part. Now, we have seen other airlines recently have 0:20:52.359 --> 0:20:57.080 massive I T failures due to the company's own mistakes. 0:20:57.119 --> 0:20:59.160 That has been a thing, but this is not one 0:20:59.160 --> 0:21:02.320 of those cases. But every time something like this happens, 0:21:02.359 --> 0:21:05.280 it really emphasizes how heavily we depend upon I T 0:21:06.280 --> 0:21:11.520 to get critical activities done, and it's prompted questions and 0:21:11.680 --> 0:21:16.399 various nations about how best to protect vital industries and 0:21:16.520 --> 0:21:21.880 infrastructure like the transportation sector, from accidents and attacks, because 0:21:22.240 --> 0:21:25.280 disruption can have a huge ripple effect to other industries 0:21:25.320 --> 0:21:28.119 as well. It's even a matter of national security. So 0:21:28.680 --> 0:21:30.960 I suspect we're going to see a lot more conversations 0:21:30.960 --> 0:21:34.440 in that area. And I also think that you should 0:21:34.520 --> 0:21:39.200 hug a q A person today because due to q 0:21:39.440 --> 0:21:43.600 a uh, we end up stopping a lot of problems 0:21:43.680 --> 0:21:46.439 before they would become really show stoppers out in the 0:21:46.480 --> 0:21:48.840 real world. I know I will hug a q A 0:21:48.920 --> 0:21:53.240 person today, but that's because my partner, Rebecca as a 0:21:53.280 --> 0:21:58.360 q A person. Popular Mechanics has an interesting article by 0:21:58.480 --> 0:22:02.680 Sasha broad Ski titled AI just flew an F sixteen 0:22:02.760 --> 0:22:06.800 for seventeen hours. This could change everything, And the headline 0:22:06.840 --> 0:22:08.600 kind of gives it away, doesn't it. The U. S. 0:22:08.640 --> 0:22:12.359 Air Force tested an AI piloting system on a Vista 0:22:12.720 --> 0:22:16.680 X sixty two a aircraft. Now, this is essentially an 0:22:16.720 --> 0:22:20.359 F sixteen, but it's an F sixteen that's made for 0:22:20.440 --> 0:22:24.240 the purposes of training operations. The experiment was a success, 0:22:24.800 --> 0:22:27.879 and it showed how AI could successfully operate an aircraft 0:22:27.920 --> 0:22:32.479 that typically a human would pilot. So this wasn't like 0:22:32.520 --> 0:22:36.600 a purpose built AI aircraft. It was an aircraft that 0:22:36.640 --> 0:22:39.720 was meant for humans that could then be retrofitted to 0:22:39.760 --> 0:22:43.040 be controlled by AI. Now this should not come as 0:22:43.080 --> 0:22:45.359 a huge surprise because countries around the world have been 0:22:45.440 --> 0:22:48.760 using unmanned aerial vehicles or u a v's for a while, 0:22:48.920 --> 0:22:52.960 so retro fitting a fighter jet with similar technology is 0:22:53.000 --> 0:22:58.840 really kind of an extension of that that sort of approach. Now, granted, 0:22:58.880 --> 0:23:00.480 a lot of u a v s actually rely on 0:23:00.520 --> 0:23:03.000 a remote human operator to work, like you have someone 0:23:03.080 --> 0:23:07.320 who is using controls at a station two uh to 0:23:07.560 --> 0:23:11.399 maneuver the u a V. But still, I think this 0:23:11.440 --> 0:23:16.320 news is interesting, but it's not surprising, right, I think, Oh, 0:23:16.400 --> 0:23:19.080 it's interesting that they've reached this point. It doesn't surprise 0:23:19.080 --> 0:23:23.199 me that it has happened. However, I will say it 0:23:23.320 --> 0:23:27.399 is concerning because there are plenty of AI and robotics 0:23:27.440 --> 0:23:32.600 experts who have warned about the the thought of weaponizing 0:23:32.640 --> 0:23:38.040 AI that the risks far outweigh any benefits, and those 0:23:38.119 --> 0:23:41.399 risks include lots of stuff like misidentifying targets. I mean, 0:23:41.440 --> 0:23:46.600 we've seen with facial recognition technology. How AI can misidentify 0:23:46.800 --> 0:23:52.159 someone well in military operations, that's truly a matter of 0:23:52.200 --> 0:23:55.240 life and death, right, Like it could mean that a 0:23:55.320 --> 0:23:59.879 military vehicle under AI control might fail to engage an enemy, 0:24:00.800 --> 0:24:06.480 or worse, far worse, it might misidentify someone or something 0:24:06.520 --> 0:24:09.520 as being an enemy target when it's not, and that 0:24:09.560 --> 0:24:15.120 would be truly catastrophic. Then there's this fear that if 0:24:15.160 --> 0:24:18.760 we start to rely on AI controlled military hardware, it's 0:24:18.760 --> 0:24:23.720 gonna make countries more inclined to inter conflict, not to 0:24:23.800 --> 0:24:28.640 avoid conflict, because the weaponry they'll use will not put 0:24:28.960 --> 0:24:32.920 soldiers in direct harm's way. You can use the robots 0:24:32.960 --> 0:24:36.600 to fight for you. My question is that would that 0:24:36.640 --> 0:24:38.320 mean you would eventually get to a point where a 0:24:38.359 --> 0:24:42.159 significant percentage of the armed forces on all sides of 0:24:42.160 --> 0:24:45.840 a conflict are AI controlled robotics And who are they 0:24:45.840 --> 0:24:48.399 firing upon? Like, are we talking about a future in 0:24:48.440 --> 0:24:51.400 which robot armies are fighting each other and if so, 0:24:51.520 --> 0:24:54.960 to what end? Or are we worse looking at a 0:24:55.000 --> 0:25:01.600 future where robot controlled devices are firing upon civilian populations 0:25:01.640 --> 0:25:03.960 and an effort to force the other side to surrender. 0:25:04.640 --> 0:25:07.400 It's scary stuff, Like there are rules to warfare, which 0:25:07.520 --> 0:25:11.239 in my mind is crazy because you know, it's all 0:25:11.280 --> 0:25:14.320 about killing people, and it's it's weird to start putting 0:25:14.560 --> 0:25:17.440 rules in place when you're talking about ending someone's life. 0:25:17.440 --> 0:25:20.000 But on the flip side, those are the rules that 0:25:20.080 --> 0:25:25.600 prevent things like the attacking of civilian targets and that 0:25:25.600 --> 0:25:28.920 that is a war crime. Well, if you're talking about 0:25:29.040 --> 0:25:33.920 robotic controlled vehicles, are we going to see a change 0:25:33.960 --> 0:25:36.760 in that approach as to what is and isn't considered 0:25:36.800 --> 0:25:40.520 a war crime. That's a scary thought. Okay, we have 0:25:40.600 --> 0:25:43.439 a few more less scary thoughts to go with, but 0:25:43.480 --> 0:25:45.959 before we get to that, let's take another quick break 0:25:55.480 --> 0:25:58.840 all right now over on TikTok. One of the many 0:25:58.960 --> 0:26:02.320 trends and one that I talked about before that has 0:26:02.359 --> 0:26:05.400 actually gone on to cause a lot of harm centers 0:26:05.440 --> 0:26:11.000 around a flaw in certain models of Hyundai and Kia vehicles. Specifically, 0:26:11.400 --> 0:26:15.159 these are vehicles that are in the models from two 0:26:15.200 --> 0:26:22.160 thousand nineteen, and these models lack electronic demobilizers. So that 0:26:22.200 --> 0:26:26.959 means that if you have the basic knowledge and some 0:26:27.080 --> 0:26:30.200 really simple equipment, some simple tools, Like when I say 0:26:30.200 --> 0:26:33.080 simple tools, i'm talking about things like USB cords, it 0:26:33.200 --> 0:26:37.480 is possible to bypass the ignition system for the vehicles 0:26:37.480 --> 0:26:40.640 that fall within these model heres, and thus it's possible 0:26:40.920 --> 0:26:44.760