WEBVTT - Tech News: The Future of Search is AI 0:00:04.480 --> 0:00:12.479 Welcome to Tech Stuff, a production from iHeartRadio. Hey therein 0:00:12.600 --> 0:00:16.079 Welcome to Tech Stuff. I'm your host, Jonathan Strickland. I'm 0:00:16.079 --> 0:00:19.639 an executive producer with iHeart Podcasts and how the tech 0:00:19.680 --> 0:00:21.959 are you. It's time for the tech news for the 0:00:22.000 --> 0:00:26.279 week ending on Friday May seventeenth, twenty twenty four. And 0:00:26.400 --> 0:00:30.240 this was a pretty big week in tech news. There 0:00:30.240 --> 0:00:33.879 were a couple of large companies that made major announcements, 0:00:34.120 --> 0:00:36.239 and then there were tons of other things going on. 0:00:36.600 --> 0:00:39.080 So we're going to start off with open ai, the 0:00:39.120 --> 0:00:44.680 company that is behind the chat GPT chatbot, among many 0:00:44.720 --> 0:00:48.920 other things. I mentioned last week that the rumor mill 0:00:49.440 --> 0:00:54.200 said open ai was on the verge of announcing an 0:00:54.240 --> 0:00:57.640 AI powered search tool, which would pretty much be akin 0:00:57.760 --> 0:01:02.040 to putting Google dead in the center of open AI's crosshairs, 0:01:02.200 --> 0:01:05.320 because Google was just about to have it's Google Io 0:01:05.440 --> 0:01:08.040 Developers conference, which we'll talk about in a second. And 0:01:08.160 --> 0:01:11.679 open ai did release an announcement for a new AI 0:01:11.880 --> 0:01:16.400 model that's called GPT four O and I think that's 0:01:16.440 --> 0:01:20.480 the letter oh, not a zero. Anyway, this model is 0:01:20.520 --> 0:01:24.400 meant to allow for actual voice conversations between human and 0:01:24.600 --> 0:01:28.880 AI eventually, and open Ai says it'll also work across 0:01:28.920 --> 0:01:32.039 image and video related tasks. So this is what they 0:01:32.080 --> 0:01:35.520 call a multi modal approach to AI. It's not just 0:01:35.840 --> 0:01:40.960 text based, it's other stuff too, And the concept is 0:01:41.040 --> 0:01:43.440 kind of like you could have an image of something 0:01:43.680 --> 0:01:46.520 or a video of something. You could be looking at 0:01:46.560 --> 0:01:51.520 things through say your camera app on your phone, and 0:01:51.640 --> 0:01:56.720 then talk to the AI assistant and try to get 0:01:56.760 --> 0:01:59.520 information about what it is you're seeing. So we've seen 0:01:59.720 --> 0:02:02.320 stuff like this or related to this in the past, 0:02:02.440 --> 0:02:05.760 like holding your phone up to look at a sign 0:02:05.800 --> 0:02:09.240 that's written in another language and have real time translation 0:02:09.400 --> 0:02:12.519 to translate that into whatever your native language is. We've 0:02:12.520 --> 0:02:15.960 seen that in the past. This would be more advanced, 0:02:16.040 --> 0:02:18.320 much more advanced than that, you know. The example I 0:02:18.320 --> 0:02:21.320 would think of is I would imagine like, say you're 0:02:21.400 --> 0:02:24.519 starting up your car and the engines making a weird noise, 0:02:24.960 --> 0:02:28.400 and so you turn your car off, you pop the 0:02:28.760 --> 0:02:31.960 hood of your engine, and you're turning the car on 0:02:32.040 --> 0:02:33.720 and you're trying to take a look and see what 0:02:33.760 --> 0:02:36.720 it is that's possibly going wrong. Well, if you're like me, 0:02:37.240 --> 0:02:41.520 you may only have a passing familiarity with that particular engine. 0:02:41.639 --> 0:02:46.440 So an app that could hear and see the same 0:02:46.480 --> 0:02:49.840 things that you do, but have access to an entire 0:02:50.440 --> 0:02:53.520 world of information would be really useful. It could tell you, hey, 0:02:53.639 --> 0:02:55.640 this is something you don't need to worry about right now, 0:02:55.800 --> 0:02:57.799 or maybe it would tell you you need to get 0:02:57.840 --> 0:03:00.960 your vehicle checked right away, or maybe even give you 0:03:01.480 --> 0:03:04.960 a quick fix, if such a thing as even possible now. 0:03:05.520 --> 0:03:07.800 In some ways, you could argue open ai is doing 0:03:08.280 --> 0:03:11.799 kind of similar stuff to what we're seeing with other 0:03:11.960 --> 0:03:16.200 personal digital assistants like Google Assistant or Siri or Alexa, 0:03:16.320 --> 0:03:20.080 but just turbocharged. Open Ai did a real time demonstration 0:03:20.639 --> 0:03:26.640 of the model's capabilities, something that would loom over Google 0:03:26.680 --> 0:03:29.520 a little bit for their io event, but we'll get 0:03:29.560 --> 0:03:32.400 to them in a second. Anyway. Chat GPT four oh 0:03:32.520 --> 0:03:35.600 is rolling out now, but not all features are available 0:03:35.680 --> 0:03:38.320 rail of the gate, so for example, it is not 0:03:38.480 --> 0:03:40.320 able to talk to you just yet, or at least 0:03:40.320 --> 0:03:43.120 not to me. I actually check to see if I 0:03:43.240 --> 0:03:46.520 have access to Chat GPT four oh. I have a 0:03:46.960 --> 0:03:50.680 chat GPT account that I never use, and so I 0:03:50.680 --> 0:03:52.680 think I logged onto it for the first time in 0:03:52.920 --> 0:03:55.600 maybe a year and found out that sure enough, I've 0:03:55.640 --> 0:03:59.000 got access to it. But it doesn't talk to me yet. 0:03:59.240 --> 0:04:01.480 The rollout is also going to be happening in batches, 0:04:01.600 --> 0:04:03.840 So if you don't have access to it yet, even 0:04:03.880 --> 0:04:06.800 though you have a chat gpt account, it is coming. 0:04:07.080 --> 0:04:10.400 You can actually sign in now by going to chatgpt 0:04:10.640 --> 0:04:15.280 dot com. They created that URL, so that's where the 0:04:15.360 --> 0:04:18.159 service lives now. I think that kind of is a 0:04:18.200 --> 0:04:22.640 sly indicator that they are transitioning from something that is 0:04:22.760 --> 0:04:25.839 largely talked about as kind of a test product into 0:04:25.880 --> 0:04:30.560 something that's an actual product. Existing chat gpt account holders 0:04:30.560 --> 0:04:33.320 will receive access to four O capabilities over the next 0:04:33.320 --> 0:04:35.560 several days if they don't have it already. And I 0:04:35.680 --> 0:04:38.080 want to echo a warning that I've seen a lot 0:04:38.120 --> 0:04:40.479 of other people make, because I think it's wise to 0:04:40.520 --> 0:04:45.320 remember be careful if in your interactions with chat gpt 0:04:45.560 --> 0:04:49.960 it suggests links to stuff, because apparently at least some 0:04:50.720 --> 0:04:54.919 malicious folks have found ways to get chat gpt to 0:04:55.880 --> 0:05:00.279 suggest links that ultimately lead to malicious website it's and 0:05:00.320 --> 0:05:06.360 malicious software. So don't trust everything Chad Gbt says, particularly 0:05:06.400 --> 0:05:09.040 when it comes to links. I think it's a really 0:05:09.080 --> 0:05:12.360 interesting interaction that you can have with this thing. I 0:05:12.400 --> 0:05:17.960 don't fully like it. I have concerns, and we'll talk 0:05:18.000 --> 0:05:21.800 more about that in just a second. But beyond the 0:05:22.200 --> 0:05:25.880 announcement that open ai made, they also managed to close 0:05:25.960 --> 0:05:29.159 a deal with Reddit, which will give open ai permission 0:05:29.200 --> 0:05:33.800 to train AI models on Reddit and subreddit posts. That's 0:05:33.800 --> 0:05:37.000 something that folks had suspected open ai was already doing, 0:05:37.400 --> 0:05:39.719 just you know, without the part about having permission to 0:05:39.760 --> 0:05:43.200 do so. Reddit will in return get some access to 0:05:43.279 --> 0:05:46.200 AI powered tools that can then be incorporated into the 0:05:46.320 --> 0:05:49.560 platform in various ways. So Reddit is saying, hey, don't worry, 0:05:49.600 --> 0:05:53.159 you're gonna have enhanced ways to interact with Reddit. Though 0:05:53.839 --> 0:05:57.680 what those will actually be haven't, you know, been fully disclosed, 0:05:57.800 --> 0:06:00.680 if you recall. Open Ai similarly sign to deal with 0:06:00.720 --> 0:06:03.760 stack overflow not too long ago, which caused a bit 0:06:03.760 --> 0:06:05.880 of a tiff in that community because a lot of 0:06:05.880 --> 0:06:08.960 folks said they preferred their work not be used for 0:06:09.040 --> 0:06:12.719 training AI. But the terms of service for stack overflow 0:06:12.720 --> 0:06:16.360 are such that essentially, once you post something to the platform, 0:06:16.480 --> 0:06:19.560 it doesn't belong to you anymore. It's the platforms. So 0:06:20.200 --> 0:06:22.880 while you might object to your work being used to 0:06:22.880 --> 0:06:25.800 train AI, you don't have any authority to deny it 0:06:25.839 --> 0:06:30.520 from happening. Some people tried to deface or delete old posts, 0:06:30.560 --> 0:06:33.560 but that's exactly that's against the terms of service on 0:06:33.600 --> 0:06:37.560 stack overflow. So many of those people subsequently found themselves banned, 0:06:37.720 --> 0:06:40.640 at least temporarily from that site. It'll be interesting to 0:06:40.640 --> 0:06:43.120 see if there will be a similar backlash in the 0:06:43.120 --> 0:06:47.839 Reddit community. That community is already kind of predisposed to 0:06:48.080 --> 0:06:52.360 not liking the corporate leadership of Reddit. There's already pretty 0:06:52.400 --> 0:06:56.120 low opinion of the company's leaders, largely because of changes 0:06:56.160 --> 0:06:59.640 that Reddit made to its API like a year ago, 0:06:59.800 --> 0:07:03.600 and apparently that's not the case with investors. Investors on 0:07:03.640 --> 0:07:07.080 the flip side are pretty darn happy. Reuters reported that 0:07:07.160 --> 0:07:11.120 shares were trading fourteen percent higher today than they were 0:07:11.240 --> 0:07:15.120 yesterday in the wake of this news. Not all the 0:07:15.160 --> 0:07:18.840 news is good news for open ai. Between announcements and partnerships, 0:07:18.840 --> 0:07:22.480 two prominent individuals in the organization resigned from the company 0:07:22.520 --> 0:07:26.000 this week. That would be Ilia Sutzkiver, who is a 0:07:26.040 --> 0:07:29.640 co founder of open ai, one of the original members 0:07:29.880 --> 0:07:33.440 of the non profit version of open ai, and the 0:07:33.480 --> 0:07:36.680 other one is Jan Leika, an executive who gave a 0:07:36.720 --> 0:07:41.400 pretty straightforward announcement on x their announcement. Just read quote 0:07:41.840 --> 0:07:45.080 I resigned end quote. Now the alarming thing is both 0:07:45.120 --> 0:07:48.720 Laikah and Sutzkiver worked for a department within open ai 0:07:48.920 --> 0:07:53.280 called super Alignment, and essentially they were assigned a task 0:07:53.720 --> 0:07:56.560 that was the need to make sure AI evolves in 0:07:56.600 --> 0:07:59.440 a way that is helpful but not harmful. This was 0:07:59.520 --> 0:08:04.239 kind of the central premise, the reison deetre of open 0:08:04.280 --> 0:08:07.680 ai when it was first founded as a nonprofit organization. 0:08:07.840 --> 0:08:10.400 The founders wanted to make certain that AI would be 0:08:10.440 --> 0:08:15.240 developed in a responsible and accountable and transparent way in 0:08:15.360 --> 0:08:18.880 order to maximize its benefits to humanity and minimize or 0:08:18.880 --> 0:08:23.640 eliminate any risks. But it turns out AI is really expensive. 0:08:24.000 --> 0:08:27.560 Like it's expensive to develop, it's expensive to implement and 0:08:27.600 --> 0:08:31.600 to run and to maintain, and without a near constant 0:08:31.680 --> 0:08:35.680 cash injection, open ai just wouldn't be around for very long, 0:08:35.880 --> 0:08:38.960 which is why the organization ultimately spun off a for 0:08:39.240 --> 0:08:42.280 profit arm, which is the version of open ai most 0:08:42.320 --> 0:08:46.120 of us talk about today, like, it's not the nonprofit version, 0:08:46.160 --> 0:08:50.520 it's the very aggressive for profit version that makes the 0:08:50.559 --> 0:08:55.680 news and that created conflict within the organization. It led 0:08:55.760 --> 0:08:57.680 up to the brief period in which the board of 0:08:57.720 --> 0:09:02.400 directors removed Sam Altman as CEO of Open Ai, before 0:09:02.400 --> 0:09:04.680 being pressured to turn around and put him right back 0:09:04.679 --> 0:09:08.000 in charge again, and then subsequently the board of directors 0:09:08.320 --> 0:09:12.440 essentially dissolved and reformed with new people. Sutzkever was actually 0:09:12.440 --> 0:09:15.880 part of the effort to remove Altman, although he subsequently 0:09:16.080 --> 0:09:18.679 apologized for that, so I don't think it's really a 0:09:18.679 --> 0:09:21.920 big surprise that he has now left the company. But 0:09:21.960 --> 0:09:24.680 I think anyone who is concerned about ethical approaches to 0:09:24.760 --> 0:09:28.120 AI should really be aware that a lot of red 0:09:28.200 --> 0:09:32.760 flags are going up right now. Okay, with that fun note, 0:09:33.080 --> 0:09:45.520 let's take a quick break to thank our sponsors. We're back, 0:09:45.600 --> 0:09:48.160 and now let us shift to Google, which, as I 0:09:48.240 --> 0:09:52.480 mentioned earlier, held its annual IO Developer conference this week, and, 0:09:52.679 --> 0:09:56.440 to the surprise of literally no one, much of the 0:09:56.480 --> 0:10:00.199 conference touched on artificial intelligence. Now there are do you 0:10:00.240 --> 0:10:04.640 have great headlines out there like Google aio or even 0:10:04.920 --> 0:10:09.720 Google aiaio, et cetera. So there's so many out there, 0:10:09.880 --> 0:10:11.600 I'm kind of sad that none are left for me. 0:10:11.640 --> 0:10:15.200 But enough about that. Google announced an update to its 0:10:15.280 --> 0:10:20.200 AI model Gemini. The company revealed that both the basic version, 0:10:20.280 --> 0:10:23.680 called Gemini one point five Flash and the pro version 0:10:23.760 --> 0:10:27.360 are available for public preview now. The primary function of 0:10:27.400 --> 0:10:31.640 these specific AI models is to help developers create stuff, 0:10:31.920 --> 0:10:34.640 so if a developer is working on an app, they 0:10:34.640 --> 0:10:38.920 can make use of these models to help boost those efforts, 0:10:39.160 --> 0:10:43.679 whether it's encoding or whatever. Google also revealed an updated 0:10:43.760 --> 0:10:47.960 version of its assistant called Project Astra. Google showed a 0:10:48.000 --> 0:10:51.800 pre recorded demonstration of the assistant's ability, and a Googler 0:10:51.960 --> 0:10:54.800 was taking her phone around an office and asking questions 0:10:55.120 --> 0:10:59.320 and having the camera app activated on her phone so 0:10:59.360 --> 0:11:02.320 she could point the camera at something and ask a 0:11:02.480 --> 0:11:05.920 question about the thing that's on screen, and the an 0:11:05.960 --> 0:11:09.160 Astra would answer. So one point, for example, she asks 0:11:09.200 --> 0:11:12.360 the assistant to point out anything that makes sound, and 0:11:12.400 --> 0:11:15.880 she scans a desk, and when she brings the camera 0:11:15.960 --> 0:11:18.800 in view of a speaker, the assistant says, that's a speaker, 0:11:19.080 --> 0:11:22.960 and then she actually uses a markup feature to circle 0:11:23.320 --> 0:11:25.880 the tweeter on the speaker, and she asks a follow 0:11:25.960 --> 0:11:28.240 up question saying what is this part of the speaker called, 0:11:28.520 --> 0:11:31.079 and the assistant says, that's the tweeter. Then it explains 0:11:31.120 --> 0:11:33.520 what the tweeter does, which is to playback you know, 0:11:33.720 --> 0:11:36.960 higher pitched sounds, higher frequency sounds, so it was a 0:11:37.000 --> 0:11:40.280 cool demonstration. She pointed out the window and asked, you know, 0:11:40.360 --> 0:11:43.960 essentially like what's this neighborhood? And the assistant answered, and 0:11:44.520 --> 0:11:47.600 she at one point even said that she had misplaced 0:11:47.640 --> 0:11:50.120 her glasses and asked the assistant if it knew where 0:11:50.160 --> 0:11:53.200 her glasses were, And because she had been walking through 0:11:53.200 --> 0:11:56.280 the office with the camera on, the app was able 0:11:56.320 --> 0:12:00.280 to reference that information and it was able to pick 0:12:00.280 --> 0:12:03.920 out a moment where the camera saw some glasses on 0:12:04.160 --> 0:12:07.520 a desk, and it directed her to those glasses, which, 0:12:07.760 --> 0:12:10.160 from what I understand, that's what got the biggest reaction 0:12:10.360 --> 0:12:12.720 from the crowd, which was kind of cool. I mean, 0:12:12.920 --> 0:12:15.880 goodness knows, I misplaced things all the time, so it'd 0:12:15.880 --> 0:12:19.280 be good to have, you know, an assistant that could 0:12:19.320 --> 0:12:21.400 tell me, yeah, no, that's in your hand. You'd do 0:12:21.559 --> 0:12:26.280 fas anyway. Later on, Googler Michael Chang somewhat cheekily shared 0:12:26.280 --> 0:12:29.439 on X now known as you know X it used 0:12:29.480 --> 0:12:31.720 to be known as Twitter that he had watched the 0:12:31.840 --> 0:12:36.720 Open AI announcement on Monday with Astra, which is kind 0:12:36.760 --> 0:12:38.800 of funny because you know, the whole thing was that 0:12:38.840 --> 0:12:41.640 Open AI was doing this sort of to undermine Google 0:12:41.720 --> 0:12:44.360 and that Michael Chang saying, yeah, I watched it along 0:12:44.360 --> 0:12:48.040 with Project Astra, and Project Astra made a real time 0:12:48.520 --> 0:12:53.240 transcript of that presentation, complete with attributions for each speaker, 0:12:53.360 --> 0:12:57.200 so identifying who was speaking in the transcript as it 0:12:57.280 --> 0:13:00.280 was going on. That's pretty impressive, and also giving some 0:13:00.320 --> 0:13:04.560 commentary about the presentation as it went on. The demonstration 0:13:04.600 --> 0:13:08.000 of the AI interpreting images and giving relevant responses was 0:13:08.120 --> 0:13:10.680 really interesting, but again, it was pre recorded. It wasn't 0:13:10.720 --> 0:13:13.720 like it was a live demo. Google also demonstrate an 0:13:13.800 --> 0:13:18.360 updated image generation AI model called imagen three. On top 0:13:18.400 --> 0:13:22.280 of images, Google showed off a music AI sandbox to 0:13:22.360 --> 0:13:25.360 let folks use AI to put musicians and composers out 0:13:25.360 --> 0:13:28.480 of a job. No, I'm sorry, that's not a messaging 0:13:28.520 --> 0:13:32.199 they wanted. I mean to help artists elevate their creativity 0:13:32.400 --> 0:13:35.320 through the use of AI. I looked at these I 0:13:35.400 --> 0:13:37.920 just got to see demos. I don't have access to 0:13:37.960 --> 0:13:41.320 the tools themselves because I'm not a notable musician. I'm 0:13:41.320 --> 0:13:43.840 not really a musician at all, so I don't have 0:13:43.920 --> 0:13:48.520 access to these things. But it's both fascinating and concerning. 0:13:48.840 --> 0:13:53.120 Because I have a lot of respect for actual musical artists, 0:13:53.160 --> 0:13:57.319 and I don't like the idea of people who are 0:13:57.320 --> 0:14:01.760 really talented and creative potentially getting pushed aside for something 0:14:01.880 --> 0:14:07.120 that is perhaps easier to access and maybe cheaper. That's 0:14:07.160 --> 0:14:10.600 not great. I think people's talent and time is worth money, 0:14:10.880 --> 0:14:13.040 like I think it's worth paying for and that you know, 0:14:13.080 --> 0:14:15.920 you can't just expect something for free, and anything that 0:14:16.000 --> 0:14:19.920 undercuts that really concerns me a lot. Google also announced 0:14:20.000 --> 0:14:23.680 video FX, which you guessed it uses generative AI to 0:14:23.760 --> 0:14:28.120 create video clips, which again raise lots of concerns, like 0:14:28.480 --> 0:14:31.120 the more you're seeing of AI generated content, the more 0:14:31.120 --> 0:14:36.080 you're worried about how reliable is the stuff you are seeing. 0:14:36.600 --> 0:14:40.320 Whether it's you know, a listing for a real estate property, 0:14:40.680 --> 0:14:43.320 like who's to say it wasn't a picture that was 0:14:43.360 --> 0:14:46.840 then enhanced by AI to make the house look way 0:14:47.000 --> 0:14:50.760 nicer than it really is, Or maybe it's something where 0:14:50.880 --> 0:14:53.080 it's a it's a video clip that seems to put 0:14:53.160 --> 0:14:57.640 a public figure in a bad light, and you start wondering, Okay, 0:14:57.640 --> 0:14:59.720 well is this real or is this something that was 0:14:59.760 --> 0:15:02.000 created by someone who just has an axe to grind 0:15:02.040 --> 0:15:04.640 for whatever reason these are things that are getting more 0:15:04.680 --> 0:15:09.280 and more relevant. Arguably they are incredibly relevant right now. Now. 0:15:09.320 --> 0:15:11.880 The thing that is probably going to have the largest impact, 0:15:12.160 --> 0:15:15.520 at least the earliest for most folks, is Google implementing 0:15:15.560 --> 0:15:19.000 more AI into its search tool, which is of course 0:15:19.040 --> 0:15:22.720 what Google is primarily known for, even though it's arguably 0:15:22.760 --> 0:15:26.040 really an advertising company, it's known for search. The company 0:15:26.040 --> 0:15:30.000 announced that AI overviews in search is going to be 0:15:30.480 --> 0:15:32.880 rolling out nationwide in the United States this week, so 0:15:33.040 --> 0:15:35.400 if you live in the United States, you probably have 0:15:35.560 --> 0:15:39.880 this incorporated in your search right now. Google also said 0:15:39.920 --> 0:15:43.560 that multi step reasoning capabilities are coming soon, which means 0:15:43.600 --> 0:15:46.800 that you'll be able to ask more complex questions in 0:15:46.840 --> 0:15:50.360 your search query and to get relevant answers. So, like, 0:15:50.960 --> 0:15:53.360 here's an example I just made up, how do I 0:15:53.400 --> 0:15:56.280 make a lasagna? And what cheese is a good substitute 0:15:56.320 --> 0:15:59.040 if I don't have ricotta? Right, Because that's a two 0:15:59.080 --> 0:16:01.840 part question. It's one asking what are the steps to 0:16:01.840 --> 0:16:04.440 make a lasagna? And I know I already know I 0:16:04.520 --> 0:16:08.560 don't have an ingredient that's in a lot of lasagna recipes, 0:16:08.680 --> 0:16:12.000 So what is a good substitute? That's the sort of 0:16:12.040 --> 0:16:15.040 thing that you can expect to be able to access 0:16:15.160 --> 0:16:17.840 in the not too distant future. The various keynotes and 0:16:17.880 --> 0:16:22.640 presentations stretched across multiple days, so there was so much 0:16:22.680 --> 0:16:25.640 more brought up during the IO event. But I think 0:16:25.680 --> 0:16:27.960 the real message for most of us, the people who 0:16:28.000 --> 0:16:30.720 aren't like actively developers, that we should take home is 0:16:30.840 --> 0:16:32.680 just that AI is going to be all up in 0:16:32.720 --> 0:16:38.960 your business and soon. Google hasn't just been talking to developers, however, 0:16:39.200 --> 0:16:42.040 the company has also been pushing out updates to its browser, 0:16:42.280 --> 0:16:45.800 Google Chrome, and this is not part of its all AI, 0:16:46.080 --> 0:16:50.680 all the time strategy. Instead, Google is addressing some zero 0:16:50.760 --> 0:16:53.600 day vulnerabilities that have come to light over the last 0:16:53.640 --> 0:16:56.600 couple of weeks, three of them in fact, recently. These 0:16:56.680 --> 0:17:00.400 vulnerabilities are severe. Potentially hackers would be able to quote 0:17:00.440 --> 0:17:03.560 perform an out of bounds memory right via a crafted 0:17:03.680 --> 0:17:07.399 HTML page end quote that's from Google. That's not good. 0:17:07.680 --> 0:17:11.639 It could mean that you could have a vulnerability activated 0:17:11.680 --> 0:17:14.879 and then you visit a malicious website and then either 0:17:14.920 --> 0:17:18.560 get malware downloaded to your computer or worse. So this 0:17:18.640 --> 0:17:21.920 is a gentle reminder to all of y'all that it's 0:17:22.040 --> 0:17:25.040 never a good idea to just push off installing updates 0:17:25.080 --> 0:17:28.760 on stuff like web browsers and operating systems, because doing 0:17:28.800 --> 0:17:31.520 that puts you at risk for malware or worse. I 0:17:31.560 --> 0:17:34.239 know it's a hassle to have to update, especially if 0:17:34.320 --> 0:17:36.639 you get to your machine and you've got like a 0:17:36.680 --> 0:17:38.480 specific thing you need to do, and then the first 0:17:38.520 --> 0:17:41.080 thing you see is a notification saying that you should 0:17:41.119 --> 0:17:43.320 run an update. I know that's a hassle. It happens 0:17:43.320 --> 0:17:45.480 to me too, and I hate it too, But it's 0:17:45.520 --> 0:17:47.520 a good idea to go ahead and do the update 0:17:48.400 --> 0:17:50.920 ninety nine times out of one hundred. One time out 0:17:50.920 --> 0:17:52.640 of one hundred, it ends up being the wrong thing 0:17:52.680 --> 0:17:55.959 to do, But when it's a ninety nine percent success, right, 0:17:56.000 --> 0:17:58.760 you should probably do it. Also, hey, fun concept AI 0:17:58.840 --> 0:18:03.080 can now help hackers discover and exploit vulnerabilities, So it's 0:18:03.240 --> 0:18:06.119 just gonna get worse. Brave New World and all that 0:18:06.200 --> 0:18:10.040 kind of stuff. Apple iOS beta testers say that iOS 0:18:10.040 --> 0:18:13.600 build seventeen point five has a disturbing habit of bringing 0:18:13.640 --> 0:18:15.800 the dead back to life. And so I'm not talking 0:18:15.840 --> 0:18:21.000 about reanimated goules here. I'm talking about deleted material, like 0:18:21.080 --> 0:18:25.119 deleted photos or deleted voicemails. According to a Reddit thread, 0:18:25.400 --> 0:18:28.960 some users have reported iOS digging up old and sometimes 0:18:29.000 --> 0:18:32.240 deleted photos and then showcasing them as if they are 0:18:32.359 --> 0:18:36.280 recent images. So you pull up your app and say, huh, 0:18:36.520 --> 0:18:40.440 according to this, this picture I took seven years ago 0:18:40.680 --> 0:18:44.560 is a new one. Apparently in some cases this has 0:18:44.680 --> 0:18:48.440 included images that people once took but long since deleted, 0:18:48.560 --> 0:18:55.000 including nudes. Nude photos. That should be a massive concern 0:18:55.119 --> 0:18:59.080 because Apple's stated practice is that once you delete a photo, 0:18:59.680 --> 0:19:02.840 then you have thirty days in which you can recover 0:19:02.960 --> 0:19:06.520 the deleted photo. But after thirty days, that photo is 0:19:06.560 --> 0:19:10.600 supposed to be deleted for good. So if, as some 0:19:10.640 --> 0:19:14.959 people have claimed, some of these photos have reappeared reportedly 0:19:15.160 --> 0:19:19.760 years after they were first deleted, that raises serious privacy questions. 0:19:20.080 --> 0:19:23.160 Right Like, if you took a nude photo seven years ago, 0:19:23.480 --> 0:19:26.520 then like six and a half years ago, you deleted it. 0:19:26.800 --> 0:19:29.199 You do not expect that seven year old photo to 0:19:29.240 --> 0:19:33.240 come bouncing back today. That would be really shocking, and 0:19:33.280 --> 0:19:36.800 it does again raise real questions about data retention and 0:19:36.840 --> 0:19:40.480 privacy and security. At least one Reddit user claimed that 0:19:40.560 --> 0:19:43.520 they had sold an old iPad to a friend of theirs, 0:19:43.680 --> 0:19:47.560 but they had gone through Apple's process to wipe their 0:19:47.600 --> 0:19:51.000 own personal data off of the iPad before selling it. So, 0:19:51.000 --> 0:19:53.880 in other words, just making sure that you're reverting back 0:19:53.920 --> 0:19:57.560 to like factory settings and deleting all personal information, but 0:19:57.720 --> 0:20:02.000 that some of their old not safe for work photographs 0:20:02.040 --> 0:20:05.440 have been popping back up on their friend's device. Now 0:20:05.800 --> 0:20:08.760 surprise friend that you didn't expect to see your buddy 0:20:09.480 --> 0:20:14.240 in their glory. This is not good news at all, 0:20:14.520 --> 0:20:16.720 if in fact it is true. So I have to 0:20:16.800 --> 0:20:19.479 keep on stressing if it is true, because I haven't 0:20:19.520 --> 0:20:24.199 seen confirmation from anyone other than people commenting on Reddit. 0:20:24.400 --> 0:20:26.359 I don't know if you know this, but sometimes people 0:20:26.359 --> 0:20:29.040 on Reddit say things that are perhaps not one hundred 0:20:29.040 --> 0:20:33.080 percent true. A lot of subreddits are almost exclusively made 0:20:33.160 --> 0:20:36.840 up of fiction anyway. Wes Davis of The Verge extends 0:20:37.040 --> 0:20:39.880 some grace to Apple and points out that this might 0:20:39.920 --> 0:20:43.639 not be a case of Apple doing something insidious or 0:20:43.680 --> 0:20:48.720 being really negligent. That deleted data is never really gone 0:20:49.000 --> 0:20:52.600 until some other information gets overwritten on top of what 0:20:52.880 --> 0:20:55.960 once was there. And that's true if you delete something 0:20:56.000 --> 0:20:59.080 off your hard drive, but you don't overwrite information on 0:20:59.160 --> 0:21:03.320 top of where that drive was, you know, storing stuff 0:21:03.600 --> 0:21:06.800 it can be possible to recover the deleted information. So 0:21:06.960 --> 0:21:09.959 maybe that's what's happened at Apple, just you know, on 0:21:10.000 --> 0:21:13.000 a much much larger scale. Now, personally, I find that 0:21:13.040 --> 0:21:16.200 a little hard to swallow because the trend has been 0:21:16.280 --> 0:21:19.560 for more folks to use more Apple services over time. 0:21:20.040 --> 0:21:23.159 So you would think if more people are using those services, 0:21:23.400 --> 0:21:27.600 that stuff would be overwritten all the time, because otherwise 0:21:27.640 --> 0:21:31.160 Apple would just have to keep on adding additional servers 0:21:31.160 --> 0:21:34.920 to handle incoming images and voicemails and all the other stuff, 0:21:35.160 --> 0:21:37.760 because you know the otherwise. The implication is that, well, 0:21:37.800 --> 0:21:41.960 we haven't overwritten everything that you know has been freed 0:21:42.040 --> 0:21:44.919 up since people have deleted things. I can't even be 0:21:45.000 --> 0:21:47.360 sure that the claims that are being made are accurate. 0:21:47.480 --> 0:21:50.040 So it's possible that some of these quote unquote deleted 0:21:50.080 --> 0:21:52.919 files weren't really deleted at all. Maybe they were just 0:21:52.960 --> 0:21:56.760 forgotten about, because goodness knows that happens too. But the 0:21:56.880 --> 0:22:00.600 story about the wipe dipad in particular is trouble if 0:22:00.720 --> 0:22:04.800 it is true, So just something to be aware of. Again, 0:22:04.840 --> 0:22:08.040 that's for iOS seventeen point five, and it's in beta, 0:22:08.119 --> 0:22:11.440 so if you're not beta testing, then this isn't likely 0:22:11.520 --> 0:22:15.280 to affect you if you're an iOS user, but I'm 0:22:15.280 --> 0:22:17.800 sure it's something that Apple is looking into to figure 0:22:17.800 --> 0:22:22.600 out before iOS eighteen goes out. All right, we got 0:22:22.840 --> 0:22:25.480 more stories to cover, but before we can get to 0:22:25.520 --> 0:22:37.719 all of those, let's take another quick break. We're back, 0:22:37.960 --> 0:22:42.000 and here's a story that hit like deja vus this 0:22:42.080 --> 0:22:44.880 week at centers around the company game Stop, and it's 0:22:45.080 --> 0:22:48.760 stock price. So you might remember that back in twenty 0:22:48.800 --> 0:22:51.480 twenty one, a collection of folks decided to stick it 0:22:51.520 --> 0:22:55.080 to some hedge funds by investing in game Stop because 0:22:55.119 --> 0:22:58.200 word got out that some massive hedge funds were short 0:22:58.240 --> 0:23:02.040 selling game Stop. By driving the price of the stock up, 0:23:02.119 --> 0:23:04.640 the investors could do two things. One, they could see 0:23:04.640 --> 0:23:06.919 a return on their own investment, right because if the 0:23:06.920 --> 0:23:11.040 stock goes up, then you're making profit. And two, they 0:23:11.040 --> 0:23:15.200 could cause serious financial hardship for these massive hedge funds 0:23:15.200 --> 0:23:18.840 that typically hold a tremendous amount of power in the 0:23:18.880 --> 0:23:21.840 stock market. Now, if you're not familiar with how short 0:23:21.880 --> 0:23:25.440 selling goes, let me give you a very basic description, 0:23:25.600 --> 0:23:28.720 and I'm glossing over a lot of details here. Let's 0:23:28.720 --> 0:23:32.800 say that you believe a particular stock is going to 0:23:32.880 --> 0:23:36.280 decline in value. So you decide, hey, I'm going to 0:23:36.320 --> 0:23:38.560 make some money with stock going down. I'm going to 0:23:38.720 --> 0:23:41.520 sell stock that I don't actually own, and i'm going 0:23:41.560 --> 0:23:44.000 to sell it at what it is currently trading for. 0:23:44.240 --> 0:23:46.959 So let's say that it's currently trading for ten dollars 0:23:46.960 --> 0:23:49.960 per share. So you sell one hundred shares at ten 0:23:50.040 --> 0:23:53.000 dollars per share, but you don't own those shares, So 0:23:53.000 --> 0:23:55.720 you're literally selling stock you do not own, but you 0:23:55.760 --> 0:23:59.439