WEBVTT 00:00:00.840 --> 00:00:03.779 The opinions expressed are those of the show 00:00:03.779 --> 00:00:08.060 hosts and may not necessarily be of any company 00:00:08.060 --> 00:00:19.699 in which the show hosts may represent. The following 00:00:19.699 --> 00:00:25.820 podcast may contain some strong language. Parental 00:00:25.820 --> 00:01:00.179 discretion is advised. Welcome to podcast number 00:01:00.179 --> 00:01:08.019 267 of The Security Box. I'm Jared Reimer. AI 00:01:08.019 --> 00:01:14.019 and its usage. This week's program focuses on 00:01:14.019 --> 00:01:18.439 AI and its usage. Where it's helping, where it's 00:01:18.439 --> 00:01:26.060 misused, and where there may be some issues. 00:01:28.200 --> 00:01:37.319 or misused and risks dealing with privacy and 00:01:37.319 --> 00:01:50.620 accessibility. This particular topic is going 00:01:50.620 --> 00:01:56.730 to be rather interesting as AI itself continues 00:01:56.730 --> 00:02:03.390 to move fast and people may not consent to everything. 00:02:04.709 --> 00:02:14.270 So we need to be aware of what's going on. So 00:02:14.270 --> 00:02:22.090 we always want your comments. So please feel 00:02:22.090 --> 00:02:26.830 free to contact us. Email iMessageTech, T -E 00:02:26.830 --> 00:02:33.389 -C -H, at M -E -N -V -I dot org. Text or WhatsApp 00:02:33.389 --> 00:02:39.509 804 -442 -6975. Or call the comment line at 888 00:02:39.509 --> 00:02:56.120 -405 -7524. We how so? are going to cover videos, 00:02:56.360 --> 00:03:04.479 including AI regulations, governments should 00:03:04.479 --> 00:03:15.240 use AI for pics and vids, Microsoft's backdoor 00:03:15.240 --> 00:03:21.759 encryption, Tesla cars equal super hackable, 00:03:23.210 --> 00:03:33.729 We are never getting rid of deep fakes. And your 00:03:33.729 --> 00:03:46.189 breaches of the week from January 26th to February 00:03:46.189 --> 00:03:55.349 1st, 2026. We also have Breaches of the Week 00:03:55.349 --> 00:04:01.289 for January 12th to 18th. And that recently appeared. 00:04:01.530 --> 00:04:06.449 We did not miss it. It just recently appeared 00:04:06.449 --> 00:04:14.169 in recent times. We will have more, including 00:04:14.169 --> 00:04:24.810 why are small companies not having issues In 00:04:24.810 --> 00:04:32.769 regards to breaches, when big multinational companies 00:04:32.769 --> 00:04:42.170 are, contemplate this. This will be Podcast 268's 00:04:42.170 --> 00:04:47.230 topic. And we already have our notes, which we 00:04:47.230 --> 00:04:51.990 need to clean up and do, but that is what will 00:04:51.990 --> 00:04:58.060 be coming up. in two weeks' time. We hope you 00:04:58.060 --> 00:05:04.319 enjoy this podcast, and it is coming up right 00:05:04.319 --> 00:05:18.480 here across the Jared Reimer Radio Network. The 00:05:18.480 --> 00:05:42.959 Security Bomb! Welcome to TSB Program 267. Recording 00:05:42.959 --> 00:05:49.100 day is Wednesday, February 4th, and we are uploading 00:05:49.100 --> 00:05:54.319 on February 5th because we have a commitment. 00:05:57.019 --> 00:06:01.259 So, that's how that's going to have to go for 00:06:01.259 --> 00:06:09.449 today. going to talk about quite a lot of things. 00:06:12.110 --> 00:06:14.649 Terry Ring will be here during the first hour. 00:06:14.829 --> 00:06:21.990 He's got a very interesting story. And we'll 00:06:21.990 --> 00:06:25.769 go into a deep dive about it. If you listen to 00:06:25.769 --> 00:06:28.670 the security hour on Throwback, you got the short 00:06:28.670 --> 00:06:33.670 version. This is the long version. There may 00:06:33.670 --> 00:06:37.980 be some news and notes that Sean posted. That 00:06:37.980 --> 00:06:42.040 might be of interest. There was something I wanted 00:06:42.040 --> 00:06:44.459 to blog about Scattered Spider, but I've been 00:06:44.459 --> 00:06:47.439 involved in other commitments trying to get my 00:06:47.439 --> 00:06:50.879 workflow settled. So there hasn't been a lot 00:06:50.879 --> 00:06:59.019 of blogging. And we've got an AI discussion. 00:06:59.240 --> 00:07:06.639 And no, nobody's in trouble. I've thought about 00:07:06.639 --> 00:07:11.379 this for a while now. But after I was forced 00:07:11.379 --> 00:07:14.379 to get an account after I got sick shortly after 00:07:14.379 --> 00:07:22.000 the last TSB, because I wanted to log things, 00:07:22.199 --> 00:07:33.500 I got to thinking about practical, safe AI use. 00:07:35.439 --> 00:07:40.439 Right, Mr. Ring? Yes. We talked about practical 00:07:40.439 --> 00:07:49.300 safe use on throwbacks, so be there here. Well, 00:07:49.459 --> 00:07:52.120 you don't have a lot of time. I know you have 00:07:52.120 --> 00:08:04.949 to run in about an hour. So, you... have a story 00:08:04.949 --> 00:08:12.170 to tell. And it's quite interesting. Yeah. Very 00:08:12.170 --> 00:08:19.110 interesting. The names, by the way, are changed 00:08:19.110 --> 00:08:24.290 to protect any particular person that might be 00:08:24.290 --> 00:08:28.110 listening that took any telephone calls. Yeah. 00:08:28.490 --> 00:08:32.309 So we want to make that known up front. We're 00:08:32.309 --> 00:08:38.659 changing the names. So go ahead, Mr. Ring. I 00:08:38.659 --> 00:08:41.159 will turn my mic off so that they can clearly 00:08:41.159 --> 00:08:45.759 hear you. Go ahead, please. I get this phone 00:08:45.759 --> 00:08:50.500 call on Friday morning. I pick it up. It's an 00:08:50.500 --> 00:08:54.320 847 number, a local. I go, okay, you know, whatever. 00:08:56.179 --> 00:08:59.639 I'm Dave, and this is, you know, kind of an Indian 00:08:59.639 --> 00:09:02.259 guy. He's like, I'm Dave from customer service, 00:09:02.460 --> 00:09:08.840 AT &T. I want to know how your service is. And 00:09:08.840 --> 00:09:14.720 we're offering 50 % off for three years, which 00:09:14.720 --> 00:09:23.120 is 36 months. Okay, cool. Let's do it. And he 00:09:23.120 --> 00:09:25.840 wanted my name. I gave him my name because everybody 00:09:25.840 --> 00:09:31.000 knows my name anyway. It's no like, you know. 00:09:32.879 --> 00:09:38.460 He goes, okay, so they, supposedly accessed my 00:09:38.460 --> 00:09:41.440 account with just my name, which seemed a little 00:09:41.440 --> 00:09:45.419 odd. But I'm like, you know, okay, I just want 00:09:45.419 --> 00:09:47.360 to see where this goes. That's the key word right 00:09:47.360 --> 00:09:52.740 there, supposedly. Yeah. Let's make that very 00:09:52.740 --> 00:09:57.320 clear. Yeah, so they transferred me and this 00:09:57.320 --> 00:10:01.659 woman, oh, hi, I'm Jennifer from AT &T customer 00:10:01.659 --> 00:10:06.789 service, which was even more weird. Because why 00:10:06.789 --> 00:10:09.970 would an AT &T rep transfer you unless you need 00:10:09.970 --> 00:10:15.129 to see a supervisor for something? Well, I thought, 00:10:15.230 --> 00:10:17.929 okay, well, I'll give her a chance. I want to 00:10:17.929 --> 00:10:21.070 see how far this goes. I know I probably shouldn't 00:10:21.070 --> 00:10:23.669 have done that because Kim says you shouldn't. 00:10:24.070 --> 00:10:30.090 So she gave me this offer of three years, 50 00:10:30.090 --> 00:10:33.500 % off. She goes, but... You get a free phone 00:10:33.500 --> 00:10:36.700 on top of that. And I'm like, okay, well, I don't 00:10:36.700 --> 00:10:38.840 really need a free phone, but what the hell? 00:10:40.200 --> 00:10:43.740 So she's telling me about the free phone and 00:10:43.740 --> 00:10:50.299 everything else. And I'm saying, well, what do 00:10:50.299 --> 00:10:53.559 I have to do? And she goes, well, you have to 00:10:53.559 --> 00:10:57.299 pay taxes on this. I'm like, but it's free. I 00:10:57.299 --> 00:11:13.909 shouldn't have to pay a tax. And so then I hear 00:11:13.909 --> 00:11:17.409 the other guy on and saying, this is Dave from 00:11:17.409 --> 00:11:23.250 customer service. And without a beat, I'm kind 00:11:23.250 --> 00:11:27.169 of going, when you're talking to AT &T, you don't 00:11:27.169 --> 00:11:34.340 read normally here. another person talking. That's 00:11:34.340 --> 00:11:36.840 what really tipped me off and I just ended up 00:11:36.840 --> 00:11:41.039 hanging up and I says, okay. And this is where 00:11:41.039 --> 00:11:45.360 I called Jared and I say, Jared, this is what 00:11:45.360 --> 00:11:48.000 happened. And I gave him the same story I'm giving 00:11:48.000 --> 00:11:52.779 you guys. He goes, call AT &T and see if this 00:11:52.779 --> 00:11:55.740 is true or not. See if this is a real thing. 00:12:07.300 --> 00:12:13.120 They verified me through the app. That's the 00:12:13.120 --> 00:12:18.440 key word right there. Yeah. Verified through 00:12:18.440 --> 00:12:24.440 the app or some other method. And, you know, 00:12:24.460 --> 00:12:27.759 she asked me for my address, which the fraudulent 00:12:27.759 --> 00:12:32.100 person didn't ask me for. She goes, I'm Janet 00:12:32.100 --> 00:12:36.899 from AT &T. How can I help you? I said, Janet, 00:12:37.019 --> 00:12:43.039 are you offering this particular offer? And I 00:12:43.039 --> 00:12:46.259 told her it was 50 % off for three years, and 00:12:46.259 --> 00:12:48.740 plus you were offering me a free phone of a choice 00:12:48.740 --> 00:12:55.500 of an iPhone, 17 Pro Max, or some Samsung Galaxy. 00:12:57.000 --> 00:12:59.059 She goes, sir, let me take a look. She goes, 00:12:59.100 --> 00:13:01.960 no, the only thing we're offering is internet, 00:13:02.259 --> 00:13:08.539 $40 a month for a year. Says, you need to tell 00:13:08.539 --> 00:13:12.860 your staff and a supervisor, this scam is going 00:13:12.860 --> 00:13:15.179 around where they're calling customers to try 00:13:15.179 --> 00:13:22.360 to get their information. So I was talking to 00:13:22.360 --> 00:13:24.419 Jared on throwback and I says, if I didn't have 00:13:24.419 --> 00:13:28.179 this training, Because they probably would have 00:13:28.179 --> 00:13:33.440 my information. Because I didn't really know 00:13:33.440 --> 00:13:38.759 much about scams until I started reading the 00:13:38.759 --> 00:13:49.820 books and dealing with security. I mean, that 00:13:49.820 --> 00:13:53.860 just, so I wanna make people aware that this 00:13:53.860 --> 00:14:01.210 scam is going around. And this is why I thought 00:14:01.210 --> 00:14:05.690 maybe the high -level version of this would be 00:14:05.690 --> 00:14:09.269 more appropriate for this show than for yours 00:14:09.269 --> 00:14:11.309 because we just want to get it out on yours. 00:14:12.309 --> 00:14:17.830 You've got low -level people. We know that. We 00:14:17.830 --> 00:14:21.769 can go deeper here. And the thing was is I heard 00:14:21.769 --> 00:14:25.889 the gentleman talking. Hi, I'm Dave from DT &T 00:14:25.889 --> 00:14:28.009 Customer Service. Wow, I was on the phone with 00:14:28.009 --> 00:14:35.370 this girl. Jennifer. I'm going, that just doesn't... 00:14:35.370 --> 00:14:41.830 So, Dean, what did Janet say when you told her 00:14:41.830 --> 00:14:46.250 that? She's like, you know, we're not offering 00:14:46.250 --> 00:14:49.450 anything like that. No, but I mean, no, I'm not 00:14:49.450 --> 00:14:51.450 talking about... You already talked about that. 00:14:51.570 --> 00:14:55.049 I'm talking about the... I heard the guy go... 00:14:55.049 --> 00:14:59.639 You know, you'll... take another call or whatever 00:14:59.639 --> 00:15:02.379 they're doing. And she was saying that we usually 00:15:02.379 --> 00:15:08.360 don't do that. It's usually silent. And I actually 00:15:08.360 --> 00:15:11.419 listened. While she was doing stuff, I was listening 00:15:11.419 --> 00:15:16.279 for another person, for another customer service 00:15:16.279 --> 00:15:22.100 rep. And I'm not saying that there might be background 00:15:22.100 --> 00:15:24.860 noise. I'm not saying that at all. No, I'm not. 00:15:24.940 --> 00:15:26.440 Because there could be, like, somebody walks 00:15:26.440 --> 00:15:30.360 over and starts yapping at them about something. 00:15:31.139 --> 00:15:35.399 I'm not saying that it can't happen. It can, 00:15:35.600 --> 00:15:43.759 but you don't really hear it that often. And 00:15:43.759 --> 00:15:50.379 when you do, it's very rare. Because most of 00:15:50.379 --> 00:15:53.320 those companies, they want, you know, silent. 00:15:53.870 --> 00:15:57.970 They want, they don't, I mean, it can happen. 00:16:00.690 --> 00:16:03.070 And I told her, I said, you know, Janet, you 00:16:03.070 --> 00:16:05.149 got to let your, she goes, I'm going to forward 00:16:05.149 --> 00:16:09.289 all this to my supervisor and all the other reps 00:16:09.289 --> 00:16:12.990 so that way they're aware that you need to because 00:16:12.990 --> 00:16:20.230 that scam is going around. Whether she did it, 00:16:20.269 --> 00:16:24.860 I don't know. I'm confident. I'm confident she 00:16:24.860 --> 00:16:31.240 did. Yeah, I'm pretty confident about that. I 00:16:31.240 --> 00:16:34.120 even informed, you know, my family and friends, 00:16:34.200 --> 00:16:44.960 like, hey, this is happening. Watch out. And 00:16:44.960 --> 00:16:49.740 you're honest. You're trustworthy. Yeah. You're... 00:16:53.179 --> 00:17:02.980 You're understanding the landscape. You are not 00:17:02.980 --> 00:17:08.519 technically savvy like me. I don't mean it in 00:17:08.519 --> 00:17:13.779 a bad way. No. You have enough knowledge to do 00:17:13.779 --> 00:17:18.779 what you need to do, and you have the brain to 00:17:18.779 --> 00:17:25.559 process. everything and understand it regurgitate 00:17:25.559 --> 00:17:33.799 it and explain it like me yeah or anybody else 00:17:33.799 --> 00:17:37.859 who's been in the industry nick nick is in the 00:17:37.859 --> 00:17:41.299 same boat right like he understands it when i 00:17:41.299 --> 00:17:46.900 was telling him about you know all of this he 00:17:46.900 --> 00:17:52.420 he already he already knew Even though he's been 00:17:52.420 --> 00:17:56.519 only around here since probably around podcast 00:17:56.519 --> 00:18:03.660 90. And I understand Kim saying, well, you should 00:18:03.660 --> 00:18:07.740 have hung up, this and that, but I wanted to 00:18:07.740 --> 00:18:16.079 see what the offer was. I wanted to see how they 00:18:16.079 --> 00:18:20.900 were kind of doing this. So I understood it from 00:18:20.900 --> 00:18:29.200 a victim's side of it. And I tell you, people 00:18:29.200 --> 00:18:33.359 could fall for this and very easily fall for 00:18:33.359 --> 00:18:36.420 this. Especially when you don't have the security 00:18:36.420 --> 00:18:39.519 training. And that's why I was saying with throwback, 00:18:39.640 --> 00:18:42.980 you know, I didn't have the security training. 00:18:43.019 --> 00:18:47.210 I probably would have fallen for it. And I'm 00:18:47.210 --> 00:18:51.869 not saying this that I'm dumb or that I'm illiterate. 00:18:51.930 --> 00:18:56.309 I just, you know, the offer sounded good and, 00:18:56.329 --> 00:19:00.349 you know, oh, cool, a free phone. Yeah, I mean, 00:19:00.450 --> 00:19:04.170 but when you see the signs and you understand 00:19:04.170 --> 00:19:10.450 it and you kind of sit back and listen to what's 00:19:10.450 --> 00:19:14.430 going on, there was tons of red flags that... 00:19:15.720 --> 00:19:18.880 You know, and when I've had enough, when I had 00:19:18.880 --> 00:19:22.740 enough of the scam, I just hung up. Okay, I'm 00:19:22.740 --> 00:19:28.119 done. Please talk about, please talk about very 00:19:28.119 --> 00:19:36.619 clearly the red flags. Well, you know, when you 00:19:36.619 --> 00:19:39.180 think about this, you know, AT &T and them, they 00:19:39.180 --> 00:19:43.980 don't offer you free stuff unless, you know, 00:19:43.980 --> 00:19:47.299 it's in a deal. And it's only for a limited time. 00:19:47.480 --> 00:19:54.079 But that's something that's one. And when you 00:19:54.079 --> 00:19:57.839 hear someone else talking like that, especially 00:19:57.839 --> 00:20:01.059 when you're on the phone with another rep, I 00:20:01.059 --> 00:20:05.279 mean, that's huge. And I had a feeling after 00:20:05.279 --> 00:20:07.640 I got off the phone with them that they were 00:20:07.640 --> 00:20:12.160 using a burner number. Because it was an 847 00:20:12.160 --> 00:20:22.289 area code. It was my area. Every time I got a 00:20:22.289 --> 00:20:29.710 call from AT &T, even if our outage is fixed, 00:20:32.049 --> 00:20:38.230 it's their 800 -288 -2020. Or is it 288 -2020? 00:20:38.829 --> 00:20:42.589 I think that's what it is. I mean, I have their 00:20:42.589 --> 00:20:45.829 number in my phone as AT &T, but they do have 00:20:45.829 --> 00:20:48.589 different numbers that they call from. But you're 00:20:48.589 --> 00:20:51.369 one of the few that puts companies like this 00:20:51.369 --> 00:20:55.150 in your phone. But what I'm saying is, if you 00:20:55.150 --> 00:20:58.170 don't have the contact... Oh, and don't rely 00:20:58.170 --> 00:21:02.529 on that, by the way. No. Because they could spoof 00:21:02.529 --> 00:21:05.769 that number, which can trigger... They can. They 00:21:05.769 --> 00:21:09.809 can. Your... They can. Phone to display that 00:21:09.809 --> 00:21:13.319 to you. They can. And then again, I mean, you 00:21:13.319 --> 00:21:15.880 have to understand what the signs are. You know, 00:21:15.940 --> 00:21:18.319 you got to know your company, who your carrier 00:21:18.319 --> 00:21:22.660 is, what kind of offers they have. You know, 00:21:22.680 --> 00:21:26.900 and at first it did sound promising. I'm not 00:21:26.900 --> 00:21:30.960 going to lie. But when I was sitting back just, 00:21:31.059 --> 00:21:33.059 you know, listening to, oh, well, you got to 00:21:33.059 --> 00:21:35.299 pay the tax on it, though. Well, it's free. You 00:21:35.299 --> 00:21:37.220 shouldn't have to pay tax on a free item. There 00:21:37.220 --> 00:21:41.859 is no tax on free. No, exactly. And that's kind 00:21:41.859 --> 00:21:47.119 of where I drew the line. Unless... Unless... 00:21:47.119 --> 00:21:54.420 And I've seen this on commercials. We're offering 00:21:54.420 --> 00:22:00.079 it for free, but you have to pay us to ship it. 00:22:01.259 --> 00:22:05.460 But they have to make that clear. Whether in 00:22:05.460 --> 00:22:07.740 the commercial or within the offer. It'll say, 00:22:07.839 --> 00:22:11.609 you know... Free with shipping, with the price 00:22:11.609 --> 00:22:14.670 of shipping. With the price of shipping and handling. 00:22:15.569 --> 00:22:20.190 Yeah. Or what they'll do sometimes is they'll 00:22:20.190 --> 00:22:25.809 say, okay, buy an iPhone 17 and get an Apple 00:22:25.809 --> 00:22:32.349 Watch, for an example, for 99 cents. Okay. I've 00:22:32.349 --> 00:22:34.789 seen that. I haven't seen the Apple Watch like 00:22:34.789 --> 00:22:38.210 that, but I've seen other products like that. 00:22:41.650 --> 00:22:46.670 But what I'm saying is, which is why I wanted 00:22:46.670 --> 00:22:49.369 to do a deeper dive on this, and I didn't want 00:22:49.369 --> 00:22:53.130 to do this on throwback because your listenership 00:22:53.130 --> 00:22:59.609 is... I mean, my listenership is more for the 00:22:59.609 --> 00:23:03.009 disabled and those who don't understand it as 00:23:03.009 --> 00:23:09.099 much as ESP. Right. ESB is more of an advanced 00:23:09.099 --> 00:23:16.079 show. Although, if anybody who's new has questions 00:23:16.079 --> 00:23:19.539 and we're doing deep dives, that's where I tell 00:23:19.539 --> 00:23:23.680 you. Email, iMessage, contact me. Tell me this 00:23:23.680 --> 00:23:28.359 was too much. Tell me a simple version. I mean, 00:23:28.380 --> 00:23:32.160 they can even iMessage me at throwback96mx. And 00:23:32.160 --> 00:23:35.500 I could walk through the story with them too. 00:23:36.039 --> 00:23:39.579 You know, they could email throwback at 96mix 00:23:39.579 --> 00:23:43.880 .com or iMessage it. That's all set up. That's 00:23:43.880 --> 00:23:49.099 why I have that set up. Right. You know, so the 00:23:49.099 --> 00:23:55.619 thing was, is it's just like, you know, you hear 00:23:55.619 --> 00:23:59.440 another gentleman talking to another client as 00:23:59.440 --> 00:24:04.000 this lady is giving you the spiel and it's kind 00:24:04.000 --> 00:24:09.319 of like... That doesn't make sense to me. When 00:24:09.319 --> 00:24:11.700 I was speaking to Janet, I was listening for 00:24:11.700 --> 00:24:15.619 this. You know, just to say, okay, I mean, I 00:24:15.619 --> 00:24:18.039 called the AT &T phone number, so I knew it was 00:24:18.039 --> 00:24:23.519 the legit company, but I just wanted to see how 00:24:23.519 --> 00:24:30.759 they operated as a company when they were on 00:24:30.759 --> 00:24:36.089 phone with clients. I mean, when I dealt with 00:24:36.089 --> 00:24:38.950 E -Voice with my toll -free line or somebody 00:24:38.950 --> 00:24:42.710 else's toll -free line, I didn't hear anybody 00:24:42.710 --> 00:24:52.769 else. Correct. My point. And I know, like, these 00:24:52.769 --> 00:24:55.789 girls are victims, too, and I understand that. 00:24:56.990 --> 00:25:01.690 But... And let's clarify something. Because this... 00:25:01.880 --> 00:25:06.960 program never got the podcast episode where they 00:25:06.960 --> 00:25:11.460 describe all of this that you guys at Throwback 00:25:11.460 --> 00:25:18.460 got. So talk about that episode that we played 00:25:18.460 --> 00:25:21.819 on Throwback where they describe these terms. 00:25:24.319 --> 00:25:32.000 Basically, we're talking about places like Cambodia, 00:25:32.000 --> 00:25:40.740 Russia, places in Chile, and a lot of these smaller 00:25:40.740 --> 00:25:49.740 countries have these camps. These camps are victimizing, 00:25:49.740 --> 00:25:55.500 whether it's men, children, women, mostly women 00:25:55.500 --> 00:26:00.859 that I understand understood it. They're mistreated, 00:26:00.900 --> 00:26:06.200 but they are forced into camps like that one. 00:26:09.480 --> 00:26:13.960 And they call them, which is the most worst thing 00:26:13.960 --> 00:26:17.980 that you could call these people. They're victims, 00:26:18.079 --> 00:26:21.140 they're not clients and they call them clients. 00:26:22.920 --> 00:26:25.900 Because they take their money and they keep going 00:26:25.900 --> 00:26:33.200 for their money and crypto and They often use 00:26:33.200 --> 00:26:38.140 the word client as their victims. And they're 00:26:38.140 --> 00:26:40.579 actually victims, but they use the word client. 00:26:41.599 --> 00:26:45.039 Not a client. You're a victim. I mean, even these 00:26:45.039 --> 00:26:50.619 people that are being forced into this, they're 00:26:50.619 --> 00:26:59.450 being beaten, I'm sure. I'm imagining so. These 00:26:59.450 --> 00:27:08.170 camps are all over Cambodia and Turkey. All these 00:27:08.170 --> 00:27:11.190 different countries that deal in this. These 00:27:11.190 --> 00:27:14.069 are not just like these little tiny camps either. 00:27:14.170 --> 00:27:19.130 They're like massive, massive, massive centers 00:27:19.130 --> 00:27:22.990 and camps that do this. It's all they deal in. 00:27:23.069 --> 00:27:30.220 There's countries that that's how they make their 00:27:30.220 --> 00:27:36.220 money. Cambodia is one of the big ones. That's 00:27:36.220 --> 00:27:41.140 how they make their funding. Through these scams. 00:27:45.920 --> 00:27:49.000 And if you want to hear the episode, please tell 00:27:49.000 --> 00:27:54.900 the people what podcast it was. And I know you've 00:27:54.900 --> 00:27:56.940 got a copy of it because you save these things. 00:27:57.799 --> 00:28:00.779 I do, but I don't... They can email you to get 00:28:00.779 --> 00:28:03.660 a copy. You would have to send it through something 00:28:03.660 --> 00:28:08.859 like Dropbox, WeTransfer, SendSpace to them because 00:28:08.859 --> 00:28:12.019 it's large. I mean, you can email throwback .net 00:28:12.019 --> 00:28:16.259 if you want to know more about it. I could find 00:28:16.259 --> 00:28:23.680 the podcast. I believe it was ScamSquad? No. 00:28:23.720 --> 00:28:27.440 Or was it... Scam Squad is too simple for that. 00:28:28.319 --> 00:28:35.720 Who was it? I think it was... It was the other 00:28:35.720 --> 00:28:41.640 one. It was either the Cyber Wire, Lock and Code, 00:28:41.980 --> 00:28:47.400 or the Files of Fake. F -A -I -K, by the way. 00:28:47.440 --> 00:28:50.059 Yeah, that's right. It was the Fake Files. Yeah. 00:28:51.700 --> 00:28:54.789 That's what it was. It was the Fake Files. Yeah. 00:28:54.890 --> 00:29:00.369 Mr. J is on the way over, so stand by. It was 00:29:00.369 --> 00:29:03.730 the fake files, and I gotta say, you know, this 00:29:03.730 --> 00:29:08.289 is a pretty sad podcast. It was a pretty savvy 00:29:08.289 --> 00:29:12.549 podcast. But sad at the same time. I mean, these 00:29:12.549 --> 00:29:16.430 people are being victimized themselves. Yes. 00:29:17.190 --> 00:29:21.869 And... It's true, they are. Into this... Good 00:29:21.869 --> 00:29:27.099 morning. The ones that I dealt with. And unfortunately, 00:29:27.539 --> 00:29:33.420 you know, if they don't do it, then they possibly, 00:29:33.480 --> 00:29:37.140 you know, might lose their life or lose this 00:29:37.140 --> 00:29:41.380 or that or get fed for a month or, you know, 00:29:41.380 --> 00:29:47.809 it's pretty sad. It is. If you want it, you can 00:29:47.809 --> 00:29:50.809 ask us for it. I'm sure I could go find it through 00:29:50.809 --> 00:29:56.349 the RSS or I could go search it out and I'm sure 00:29:56.349 --> 00:30:01.390 that Google or DuckDuckGo has it. Yeah, I was 00:30:01.390 --> 00:30:06.890 talking about my AT &T scam, Nick. Oh, yes. You're 00:30:06.890 --> 00:30:10.170 going to get half off a new phone. Yes, I remember 00:30:10.170 --> 00:30:11.849 that. You need to get half off your bill and 00:30:11.849 --> 00:30:16.240 get a free phone. Yes, yes. That you still somehow 00:30:16.240 --> 00:30:20.640 have to pay taxes on. Yeah. Yes. Yeah. And then 00:30:20.640 --> 00:30:23.039 yet I heard someone else talking to another client 00:30:23.039 --> 00:30:26.319 while I was on the phone with this girl. Huh. 00:30:27.319 --> 00:30:30.720 Oh, actually. He got transferred to a girl, and 00:30:30.720 --> 00:30:35.200 then he ended up either calling somebody, which 00:30:35.200 --> 00:30:38.640 is usually how this works, or somebody calls 00:30:38.640 --> 00:30:43.160 in. But usually they call out. Nobody ever calls 00:30:43.160 --> 00:30:46.259 in. And I heard, this is Dave from AT &T customer 00:30:46.259 --> 00:30:48.339 service. How is your service today? I'm like, 00:30:48.380 --> 00:30:54.980 um, something doesn't sound right. And when I 00:30:54.980 --> 00:30:56.700 actually called Jared about it, he goes, call 00:30:56.700 --> 00:30:59.480 AT &T and see if it's true or not. That's the 00:30:59.480 --> 00:31:01.880 only way you're going to really know. You know, 00:31:01.940 --> 00:31:05.880 that's what I did. And he goes, no, it's, we 00:31:05.880 --> 00:31:07.980 don't offer that, something like that. That's, 00:31:07.980 --> 00:31:13.180 no. And then he called me back and I'm like, 00:31:13.279 --> 00:31:20.859 uh, really? Well, I didn't use your name with 00:31:20.859 --> 00:31:23.700 her either. I just said my security advisor advised 00:31:23.700 --> 00:31:27.759 me to call you guys because... And that's important. 00:31:28.980 --> 00:31:32.059 And I think, I'm not saying everybody should 00:31:32.059 --> 00:31:37.359 trust me, but you should find somebody you trust. 00:31:38.829 --> 00:31:42.930 Whether it's me, whether it's Nick, Terry, whoever. 00:31:49.630 --> 00:31:57.690 To advise you on what's going on. Right. You 00:31:57.690 --> 00:32:01.349 know, Kim sent an email yesterday talking about 00:32:01.349 --> 00:32:04.650 the $30 ,000. I didn't read it yet, but it was 00:32:04.650 --> 00:32:10.559 a $30 million. catfishing scam. I talked to Nick 00:32:10.559 --> 00:32:14.240 about that when I called him late last night 00:32:14.240 --> 00:32:20.680 because he texted me about the Braille, which 00:32:20.680 --> 00:32:26.960 we're going to get into later. Right. Yeah, I 00:32:26.960 --> 00:32:31.420 mean, that was an interesting one. And that's 00:32:31.420 --> 00:32:36.950 why, you know, we discussed it here because Here 00:32:36.950 --> 00:32:40.309 we could discuss it at length at least and dig 00:32:40.309 --> 00:32:45.730 into it a little bit more. Nick could probably 00:32:45.730 --> 00:32:50.130 agree that we need to keep it as simple as possible 00:32:50.130 --> 00:32:56.430 for throwback. Yeah, I agree. Not saying any 00:32:56.430 --> 00:33:00.630 of my listeners are simpletons. I have no way 00:33:00.630 --> 00:33:06.109 to know that, but maybe. You get a different 00:33:06.109 --> 00:33:08.690 crowd, though, on the Saturday night show. Not 00:33:08.690 --> 00:33:12.650 so much the tech people. It's more the music 00:33:12.650 --> 00:33:23.829 people. Yeah, you get the music people. I'm like, 00:33:23.890 --> 00:33:27.890 I gotta call Jared and find out where to proceed. 00:33:27.890 --> 00:33:31.549 So I had him on one ear, something else on another. 00:33:32.750 --> 00:33:36.609 And the other ear was calling my name, and I 00:33:36.609 --> 00:33:42.410 had to tell them I'm on a call. I think when 00:33:42.410 --> 00:33:44.970 I told Jared I almost got scammed, he kind of 00:33:44.970 --> 00:33:48.109 probably fell out of his chair. I almost fell 00:33:48.109 --> 00:33:54.369 out of my chair. I'm like, but I kind of sat 00:33:54.369 --> 00:33:58.150 back and listened to everything. Oh, something 00:33:58.150 --> 00:34:01.309 else is making a return. Speaking of scammed. 00:34:02.000 --> 00:34:11.780 So I got an email earlier from somebody with 00:34:11.780 --> 00:34:15.440 the simple subject line of quote -unquote statement. 00:34:17.699 --> 00:34:21.320 And there was an attachment there. And what it 00:34:21.320 --> 00:34:27.880 turned out it was was apparently some supposed 00:34:27.880 --> 00:34:32.030 purchase that I'd made at PayPal for... A little 00:34:32.030 --> 00:34:35.230 over $400 in Bitcoin. And yes, of course, if 00:34:35.230 --> 00:34:38.349 that was something you didn't authorize, call 00:34:38.349 --> 00:34:42.429 this random 800 number. What was it? 800 -915 00:34:42.429 --> 00:34:47.429 -something. Oh, Dave. And let's just make it 00:34:47.429 --> 00:34:52.409 clear. If you want to call PayPal and it's toll 00:34:52.409 --> 00:35:04.099 -free, I believe it's 888 -221... 11... 91, I 00:35:04.099 --> 00:35:07.219 think is what the number is. They almost got 00:35:07.219 --> 00:35:16.480 my dad the one time. Oh, man. Let me see if the 00:35:16.480 --> 00:35:22.960 GPT of... I can tell you a PayPal number, actually. 00:35:24.980 --> 00:35:40.079 Chat... Let's see if it'll tell me here. Yeah. 00:35:43.639 --> 00:35:49.539 Toe -free customer service number. U .S. and 00:35:49.539 --> 00:35:58.900 Canada. Mm -hmm. 888 -221 -1161. Ah, that's it. 00:36:00.300 --> 00:36:08.690 888 -221 -1161. Yeah, this was nothing like that. 00:36:08.789 --> 00:36:11.190 Yeah, I have their PayPal. And when you call 00:36:11.190 --> 00:36:15.710 in, it's going to want you to log in. Yep. It's 00:36:15.710 --> 00:36:20.789 going to verify you. Yep. Aha. Yeah. It'll verify 00:36:20.789 --> 00:36:27.449 you. Yep. If you want PayPal credit, you can 00:36:27.449 --> 00:36:42.039 actually use that number or 866 -528 - Or if 00:36:42.039 --> 00:36:43.960 you're tech savvy enough, you could use their 00:36:43.960 --> 00:36:49.059 app and get PayPal credit that way too. Yeah. 00:36:50.199 --> 00:36:53.219 I mean, those who aren't, I can understand, but 00:36:53.219 --> 00:37:03.380 those who are... 528 -3733. Yeah, not 800... 00:37:05.750 --> 00:37:09.210 915 -3633 or whatever this number was. No, I 00:37:09.210 --> 00:37:11.329 did not dial it. If you're outside the U .S. 00:37:11.329 --> 00:37:17.110 and Canada, support option will vary by country. 00:37:17.130 --> 00:37:20.809 Log into PayPal .com. That's PayPal. P -A -Y 00:37:20.809 --> 00:37:27.730 P -A -L dot com. It may redirect you when it 00:37:27.730 --> 00:37:34.980 recognizes you're outside of the territory. So 00:37:34.980 --> 00:37:37.559 log into your account and use the contact page 00:37:37.559 --> 00:37:40.900 for your country. Not PayPal either. PayPal. 00:37:41.659 --> 00:37:47.960 Remember that email? Log into your PayPal account. 00:37:48.800 --> 00:37:58.079 What? Log into your Netflix. Yeah, I figured 00:37:58.079 --> 00:38:25.920 I would. 800 -915 -XXXX. So, yeah. ChatGPT is 00:38:25.920 --> 00:38:35.230 going to write a novel. At GPT. It's still writing. 00:38:35.409 --> 00:38:40.130 It's still writing. Yep. Good old AI, man. Good 00:38:40.130 --> 00:38:43.289 old AI. Got it. This is about scam awareness. 00:38:46.809 --> 00:38:54.369 Yeah. Yeah, that's what we're... And we know 00:38:54.369 --> 00:38:59.780 that. PayPal does not... So let's highlight some 00:38:59.780 --> 00:39:03.280 of this. If it was PayPal or any other company. 00:39:04.320 --> 00:39:15.199 PayPal does not call customers from random 800 00:39:15.199 --> 00:39:28.360 numbers. The number is 888 -221 -1161. If you 00:39:28.360 --> 00:39:30.539 have a PayPal credit, the system will already 00:39:30.539 --> 00:39:33.800 know and it'll ask you. So you don't have to 00:39:33.800 --> 00:39:39.239 call any other number. And even if they issue 00:39:39.239 --> 00:39:42.360 a PayPal, they don't call you. They email you. 00:39:43.380 --> 00:39:47.659 Don't get calls from PayPal. They do. PayPal 00:39:47.659 --> 00:39:52.480 does not cold call users about the following 00:39:52.480 --> 00:39:58.309 items. Fraud. Account problems, that's what Terry 00:39:58.309 --> 00:40:03.250 was just talking about. Yep. Suspicious transactions. 00:40:04.489 --> 00:40:09.969 Yep. Refunds, which I got one, but that's not 00:40:09.969 --> 00:40:16.769 because of a company issue. Something else happened. 00:40:18.469 --> 00:40:23.530 Urgent action required. If someone received a 00:40:23.530 --> 00:40:29.050 call from 800 -915 -XXXX, it's not PayPal or 00:40:29.050 --> 00:40:31.650 probably any other company you do business with. 00:40:32.909 --> 00:40:39.210 Be phony. How PayPal actually contacts people. 00:40:40.929 --> 00:40:44.570 Messages appear inside the PayPal account message 00:40:44.570 --> 00:40:49.300 center or via email. Address to the users and 00:40:49.300 --> 00:40:55.500 address them by full name, not dear. That's what 00:40:55.500 --> 00:40:57.780 I was just talking about, the email. That's what 00:40:57.780 --> 00:41:00.559 I was just talking about, the email. Mm -hmm. 00:41:00.619 --> 00:41:05.940 Mm -hmm. If PayPal ever just calls, it's usually 00:41:05.940 --> 00:41:10.840 after the user initiates contact and gets a one 00:41:10.840 --> 00:41:16.039 -time passcode. Yep. That's how you deal with 00:41:16.039 --> 00:41:21.909 PayPal. Common scam patterns that Nick lightly 00:41:21.909 --> 00:41:24.969 saw. And this could go for anybody, but since 00:41:24.969 --> 00:41:30.590 it knows Nick, it's mentioning him by name. Now, 00:41:30.610 --> 00:41:35.909 let's cover these four. Spoofed 800 number. 800 00:41:35.909 --> 00:41:41.050 -915 -XXXX is a big red flag. He noticed that. 00:41:42.030 --> 00:41:50.239 Give him five bucks. Next. Caller claims any 00:41:50.239 --> 00:41:55.119 of the following. Suspicious activity, unauthorized 00:41:55.119 --> 00:42:00.340 charge, your account may be locked. No such thing. 00:42:00.480 --> 00:42:04.940 The other two are possible, but the accounts 00:42:04.940 --> 00:42:10.559 are never locked. Not in the frame of placing 00:42:10.559 --> 00:42:14.369 a phone call. What happened to me with Facebook? 00:42:14.409 --> 00:42:20.369 It did get locked, but Facebook emailed me. I 00:42:20.369 --> 00:42:23.210 had it where I got an email, but it said my account 00:42:23.210 --> 00:42:27.650 was restricted. Well, that's what PayPal does. 00:42:27.750 --> 00:42:31.429 They restrict you, i .e. limit you to sending 00:42:31.429 --> 00:42:36.889 about $500 a month. And there may be other limitations. 00:42:38.800 --> 00:42:41.340 No, I forgot why it was restricted. They don't 00:42:41.340 --> 00:42:43.980 restrict you, but I forgot why the restriction 00:42:43.980 --> 00:42:48.260 was on there and they lifted it. Well, by default, 00:42:48.300 --> 00:42:51.320 it's restricted until you add a bank account. 00:42:53.500 --> 00:42:56.920 Oh, yeah. I have a bank account. They fixed it. 00:42:57.039 --> 00:42:59.420 But my bank account was on there already and 00:42:59.420 --> 00:43:01.400 it was still restricted, so I actually had to 00:43:01.400 --> 00:43:03.840 call them. But it doesn't matter at this point. 00:43:04.460 --> 00:43:10.119 No, no. The next item here is pushes. Nick, the 00:43:10.119 --> 00:43:16.400 question is, was it something urgent that we've 00:43:16.400 --> 00:43:20.920 talked about on this program before? Oh, yes, 00:43:20.980 --> 00:43:24.139 it was. I mean, they made it seem like, you know, 00:43:24.139 --> 00:43:27.000 call in 24 hours kind of thing. You know, if 00:43:27.000 --> 00:43:30.480 you want a quote -unquote refund. Yeah. Okay. 00:43:32.159 --> 00:43:38.090 Prize to get. And that's the end of there. Okay, 00:43:38.130 --> 00:43:41.409 that doesn't quite apply here, but yeah. No, 00:43:41.449 --> 00:43:46.650 but okay. Login info, two FA codes, remote access, 00:43:47.190 --> 00:43:55.449 confirmation of personal details. And it says 00:43:55.449 --> 00:43:57.889 what Nick should do. And I think we should apply 00:43:57.889 --> 00:44:01.210 this to anybody because this is part of the main 00:44:01.210 --> 00:44:05.130 discussion here as part of scam awareness for 00:44:05.130 --> 00:44:14.510 today. Yes. Do not call the number back. Do not 00:44:14.510 --> 00:44:20.210 engage. Although, Terry engaged enough to understand 00:44:20.210 --> 00:44:23.630 what was going on. But once he saw the red flags, 00:44:24.010 --> 00:44:29.889 that was enough. That was enough, yep. Yep. Log 00:44:29.889 --> 00:44:37.539 into PayPal directly or call the company. Check 00:44:37.539 --> 00:44:42.940 the message center. If concerned, call 888 -221 00:44:42.940 --> 00:44:52.079 -1161 or the company that is there. Forward scam 00:44:52.079 --> 00:44:55.920 emails. You can send them to phishing at paypal 00:44:55.920 --> 00:45:04.980 .com. So, that works. And calls can be reported 00:45:04.980 --> 00:45:23.610 to What is it here? What did it say here? Oh, 00:45:23.690 --> 00:45:26.829 calls can be reported too. So you send them an 00:45:26.829 --> 00:45:29.989 email, tell them what the phone number was, what 00:45:29.989 --> 00:45:41.269 they wanted, that type of thing. Right. PayPal 00:45:41.269 --> 00:45:46.110 does not randomly call from unsolicited numbers. 00:45:52.570 --> 00:46:01.329 Claiming to be PayPal is a scam, full stop. I 00:46:01.329 --> 00:46:09.030 can do any of the following, but we're talking 00:46:09.030 --> 00:46:11.530 about this in full. Because that's what this 00:46:11.530 --> 00:46:26.829 podcast is for. Right. Yep. Podcast 267 related 00:46:26.829 --> 00:46:39.230 this to any company including Terry's story about 00:46:39.760 --> 00:46:56.340 and it's 847 based phone call he discussed so 00:46:56.340 --> 00:47:12.510 this group understands this Which is good. That's 00:47:12.510 --> 00:47:22.449 what we want. Email iMessage, J -A -R -E -D -R 00:47:22.449 --> 00:47:25.610 -I -M -E -R at 986themix .com. Text or WhatsApp, 00:47:25.849 --> 00:47:33.289 804 -442 -6975. Call the comment line at 888 00:47:33.289 --> 00:47:47.260 -405 -7524. And yes, this is what it's telling 00:47:47.260 --> 00:47:52.820 me is exactly what we've done. Yep. Any legitimate 00:47:52.820 --> 00:47:56.380 companies don't cold call without authorization. 00:47:58.000 --> 00:48:03.099 Nope. Or without you calling first. Correct. 00:48:17.710 --> 00:48:23.070 Terry's 847 AT &T call is a perfect illustration. 00:48:23.929 --> 00:48:28.949 They use local and toll -free numbers. It was. 00:48:34.210 --> 00:48:37.969 All of that means nothing. It's a good thing 00:48:37.969 --> 00:48:52.980 I had security training. So... Even if it matches 00:48:52.980 --> 00:49:09.440 their prefix. So, we know this. Yes. They may 00:49:09.440 --> 00:49:19.619 send you a letter or an email. If they do call, 00:49:20.079 --> 00:49:27.940 They do authentication. And they don't tell you, 00:49:28.000 --> 00:49:31.179 you must act now or your account will be locked. 00:49:37.760 --> 00:49:41.699 The scam isn't the number, it's the unsolicited 00:49:41.699 --> 00:49:44.920 urgency, says ChatGPT, and I agree with that. 00:49:45.420 --> 00:49:54.340 What about you guys? Yeah. Agreed. Voice calls 00:49:54.340 --> 00:49:57.480 feel more official because we're blind and disabled. 00:49:58.699 --> 00:50:01.739 Pressure plus audio equals higher success rate. 00:50:01.820 --> 00:50:22.730 We know this. Yes. So... If... We should do a 00:50:22.730 --> 00:50:26.949 standard TSB segment. I can have one run because 00:50:26.949 --> 00:50:34.909 it says, here's what we could do next. We can 00:50:34.909 --> 00:50:41.989 create a repeatable checklist that you can reuse 00:50:41.989 --> 00:50:45.849 for every episode. A standard TSB scam warning 00:50:45.849 --> 00:50:53.929 segment. or tie this directly into AI voice cloning 00:50:53.929 --> 00:51:05.050 and caller ID spoofing. We've got enough AI stuff 00:51:05.050 --> 00:51:08.969 that we can do AI for months at the two -week 00:51:08.969 --> 00:51:14.500 rate. Oh, we could. And I've already got the 00:51:14.500 --> 00:51:16.739 next episode lined up and we're going to talk 00:51:16.739 --> 00:51:20.679 about that in a little bit of detail in a while. 00:51:21.500 --> 00:51:25.519 I kind of like the whole TSB scam thing. It's 00:51:25.519 --> 00:51:31.400 kind of cool. Do you want a segment that we could 00:51:31.400 --> 00:51:36.860 just run every week? I can tell it. Do item whatever 00:51:36.860 --> 00:51:42.429 in this list. And I can copy it, edit it, record 00:51:42.429 --> 00:51:49.449 it. Yeah, we could throw it in throwbacks. We 00:51:49.449 --> 00:51:54.070 could throw it in throwbacks. As well as TSB. 00:51:54.070 --> 00:52:00.110 I'd be, you know, have a basic warning. Like, 00:52:00.150 --> 00:52:05.449 hey, you know, watch out for this. I mean, that 00:52:05.449 --> 00:52:15.400 would be... Would be a good thing. You handled 00:52:15.400 --> 00:52:24.699 this exactly right by airing it, it says. Yeah. 00:52:25.059 --> 00:52:30.260 I hope so. But it knows how I work because I've 00:52:30.260 --> 00:52:34.739 given it prior episodes. I've given it show notes. 00:52:34.860 --> 00:52:39.360 I've trained it because of what I'm doing. That's 00:52:39.360 --> 00:52:44.460 what I was doing all last week was training because 00:52:44.460 --> 00:52:54.400 I need it to help me. So I will revisit this 00:52:54.400 --> 00:52:59.159 later so that we don't take up air time. I do 00:52:59.159 --> 00:53:01.739 like using AI for a lot of stuff and I gotta 00:53:01.739 --> 00:53:07.659 say that I don't use it for good. It's fine. 00:53:17.789 --> 00:53:22.969 Okay. Mr. Ring, I know you need to go. Press 00:53:22.969 --> 00:53:27.630 play is working, so it'll be Nick and I. If he 00:53:27.630 --> 00:53:30.309 left already, then I won't need to, but if he 00:53:30.309 --> 00:53:32.409 didn't, then yeah, I'll be going. I don't know 00:53:32.409 --> 00:53:41.630 if he left already. Okay. Mr. Jack? Yep, I'm 00:53:41.630 --> 00:53:44.289 still here. Oh, he left already, so I guess I'm 00:53:44.289 --> 00:53:49.199 staying. Alright. Because you were telling me 00:53:49.199 --> 00:53:52.079 that you were leaving, so we prepared you to 00:53:52.079 --> 00:53:56.599 go first. That's what I thought. But he left. 00:53:56.860 --> 00:53:59.420 He kind of left me here, so I'm like, well, okay. 00:54:01.280 --> 00:54:05.760 Then don't go chasing him. No, he left already, 00:54:05.880 --> 00:54:12.369 so I'm just going to... I know I haven't been 00:54:12.369 --> 00:54:15.170 blogging, although scattered spiders back in 00:54:15.170 --> 00:54:18.610 the news, they're up to no good. I spotted an 00:54:18.610 --> 00:54:27.809 article I wanted to blog some days ago. We've 00:54:27.809 --> 00:54:34.590 got a bunch of videos to air that Preston found, 00:54:34.829 --> 00:54:40.250 so we'll be interspersing those within the episode. 00:54:44.079 --> 00:54:52.579 And how about next week's program? I sent a draft. 00:54:54.559 --> 00:54:57.719 I've been on a tirade lately about all kinds 00:54:57.719 --> 00:55:05.659 of crap. So I expect the tech podcast to have 00:55:05.659 --> 00:55:15.880 a podcast coming soon. about the braille transcription 00:55:15.880 --> 00:55:21.880 course and why I basically started retaking it 00:55:21.880 --> 00:55:26.480 although I know enough to basically do enough 00:55:26.480 --> 00:55:32.320 which is what I'm doing now and how it basically 00:55:32.320 --> 00:55:43.280 fail is set for failure if you're blind Interesting. 00:55:47.900 --> 00:55:51.900 I've been on a tirade about all kinds of crap 00:55:51.900 --> 00:56:02.539 with it. So, I don't even think I need news articles 00:56:02.539 --> 00:56:06.039 anymore, at least for the foreseeable future, 00:56:06.139 --> 00:56:15.059 to help me with the podcast. Okay. Just ask Nick. 00:56:18.539 --> 00:56:21.079 Oh, yeah. I think I gave him a kind of a lineup. 00:56:21.800 --> 00:56:27.119 I think I gave... There comes Mr. G. Yeah, Mr. 00:56:27.300 --> 00:56:32.519 G. Just ask Nick. Yes, hello, Jared. I know you 00:56:32.519 --> 00:56:36.420 were trying to track me down, but I did have 00:56:36.420 --> 00:56:38.860 a short work day today because I actually learned 00:56:38.860 --> 00:56:42.159 how to track down. Non -billable service notes 00:56:42.159 --> 00:56:46.800 in our TheraApp system. I actually did not track 00:56:46.800 --> 00:56:54.059 you down today. I just sent you some stuff that 00:56:54.059 --> 00:56:59.639 ChatGPT was giving me based on my tirades that 00:56:59.639 --> 00:57:03.079 I've been on lately. I just got through my scam 00:57:03.079 --> 00:57:07.780 story, Preston, so... Actually, Terry, don't 00:57:07.780 --> 00:57:11.159 worry. I was listening in and I do want to say 00:57:11.159 --> 00:57:15.179 you did a nice job of covering it because as 00:57:15.179 --> 00:57:18.679 far as I can understand, we need to keep sharing 00:57:18.679 --> 00:57:23.599 our love experiences because, you know, it could 00:57:23.599 --> 00:57:28.559 happen to any one of us down the line. That's 00:57:28.559 --> 00:57:31.719 true. Good job. And the fact that as we were 00:57:31.719 --> 00:57:35.699 just talking about, This podcast reaches blind 00:57:35.699 --> 00:57:39.460 people. Not saying other disabilities don't listen, 00:57:39.599 --> 00:57:45.320 but blind people by their nature, including me. 00:57:45.800 --> 00:57:48.559 I'm including myself in this. I'm not going to 00:57:48.559 --> 00:57:53.900 exclude myself in this. Well, sure. No. But we 00:57:53.900 --> 00:57:59.969 are all going to be vulnerable to this. No matter 00:57:59.969 --> 00:58:02.809 what the scam is, whether it's the PayPal scam 00:58:02.809 --> 00:58:05.889 that Nick was talking about or whatever company 00:58:05.889 --> 00:58:14.889 they wanted to say they were from. Whether it's 00:58:14.889 --> 00:58:18.730 Terry's story or anything else we've talked about 00:58:18.730 --> 00:58:27.389 through the years. Yeah. Anything can happen 00:58:27.389 --> 00:58:30.889 still. You know, as long as we are living and 00:58:30.889 --> 00:58:33.590 breathing, we need to continue to share, you 00:58:33.590 --> 00:58:37.630 know, our experiences and stories. You know, 00:58:37.769 --> 00:58:41.590 it's going to be a learning experience. And by 00:58:41.590 --> 00:58:52.550 the way, Mr. E gave out the... the other day 00:58:52.550 --> 00:58:56.090 was it yesterday or the day before the breaches 00:58:56.090 --> 00:58:58.510 of the week but I've got enough files to run 00:58:58.510 --> 00:59:00.469 so we're going to have to run that in two weeks 00:59:00.469 --> 00:59:05.809 because I've got you sent me like five or six 00:59:05.809 --> 00:59:08.110 or seven files that we're going to intersperse 00:59:08.110 --> 00:59:16.210 between you know segments and things so in credit 00:59:16.210 --> 00:59:19.530 sense since we're doing this bi -weekly We'll 00:59:19.530 --> 00:59:22.829 be catching up during the weeks that we're not 00:59:22.829 --> 00:59:29.230 here. So that's going to be in the next show's 00:59:29.230 --> 00:59:33.469 batch. But yeah, good job, Terry. I'm proud of 00:59:33.469 --> 00:59:39.750 you. Appreciate that. And speaking of next episode 00:59:39.750 --> 00:59:49.030 in two weeks, we sent out the draft. Why is the 00:59:49.030 --> 00:59:54.329 JRN and the Music Education Network for the Visually 00:59:54.329 --> 01:00:04.449 Impaired better than any multi -billion billion 01:00:04.449 --> 01:00:14.329 dollar company? Because we have better security. 01:00:14.510 --> 01:00:18.420 We actually... You actually take care of your 01:00:18.420 --> 01:00:21.119 clients, Jared. If they have an issue, you deal 01:00:21.119 --> 01:00:26.019 with it right then. That's part of it. That's 01:00:26.019 --> 01:00:30.739 actually part of it, Terry. That's not the entire 01:00:30.739 --> 01:00:35.639 story. I'm sure it's not, but I'm saying that 01:00:35.639 --> 01:00:39.380 when a client has an issue or you have an outage, 01:00:39.420 --> 01:00:42.659 you don't just say, oh, screw it, I'll deal with 01:00:42.659 --> 01:00:48.139 it next week. You get on it and do it. But that's 01:00:48.139 --> 01:00:50.920 part of it. That's part of it. You're correct. 01:00:51.860 --> 01:00:59.760 No. You are correct. But that's not the entire 01:00:59.760 --> 01:01:13.610 story. And this is why you should get your happy 01:01:13.610 --> 01:01:23.349 ass back on the list because I sent the text 01:01:23.349 --> 01:01:28.570 to the list but what I will do is I will send 01:01:28.570 --> 01:01:40.510 you the raw unedited file And I will send it 01:01:40.510 --> 01:01:58.050 to your folder in the box of drop. A root? Yep. 01:01:58.210 --> 01:02:03.869 You can put it in the root. And it will be in 01:02:03.869 --> 01:02:23.300 the root. Look for Two. Sixty. Oh, do you want 01:02:23.300 --> 01:02:25.199 it in the root or do you want it in throwback? 01:02:25.679 --> 01:02:27.760 You can put it in the root. Yeah, just throw 01:02:27.760 --> 01:02:33.679 it in the root. It's fine. Okay. I have to clear 01:02:33.679 --> 01:02:38.519 that out. I know I got to go through it. It's 01:02:38.519 --> 01:02:46.420 okay. I'll do it. Look for podcast 268. All right. 01:02:48.019 --> 01:02:51.159 And there's going to be a lengthy, lengthy text 01:02:51.159 --> 01:02:54.599 file that you can read. It's raw. Very, very 01:02:54.599 --> 01:02:58.900 raw. This is chat GPT copied. There's no editing. 01:03:03.099 --> 01:03:11.719 Mr. J. Yes. What do you think about our topic 01:03:11.719 --> 01:03:21.099 in two weeks? I think this is interesting. I 01:03:21.099 --> 01:03:26.019 mean, especially bringing in, well, you can't 01:03:26.019 --> 01:03:32.079 really call it the voice of AI, but bringing 01:03:32.079 --> 01:03:41.070 in that, you know, source. to also analyze that. 01:03:41.869 --> 01:03:48.309 It did. Yeah, it did. I gave it both privacy 01:03:48.309 --> 01:03:55.750 policies. I asked it to compare other known privacy 01:03:55.750 --> 01:04:00.550 policies and what's different between us and 01:04:00.550 --> 01:04:08.659 everybody else. That sounds interesting. I'm 01:04:08.659 --> 01:04:12.179 going to have to come and join in two weeks. 01:04:13.820 --> 01:04:17.179 I am not going to do this episode for your program, 01:04:17.280 --> 01:04:20.280 though, Terry. It is too... No, it's too advanced, 01:04:20.340 --> 01:04:24.320 as I'm sure it is. Yeah, I will... Yeah, yeah. 01:04:25.159 --> 01:04:28.739 We're fine. Because we got topics. So, we have 01:04:28.739 --> 01:04:31.960 topics even backlogged that we can do for next 01:04:31.960 --> 01:04:36.510 week. Well, that's not the point. I can get it 01:04:36.510 --> 01:04:39.429 written next week. I'm going to write it up next 01:04:39.429 --> 01:04:43.909 week, but the problem I have is that I don't 01:04:43.909 --> 01:04:49.550 know how to simplify this. Once I get it written, 01:04:49.670 --> 01:04:57.010 even in percent codes, I could ask the tool to 01:04:57.010 --> 01:05:00.460 make it throwback -friendly. I mean, we could 01:05:00.460 --> 01:05:06.739 continue next week the conversation of AI like 01:05:06.739 --> 01:05:13.059 we did. Right. I'm not ready for that yet. I'm 01:05:13.059 --> 01:05:15.179 not ready for that. And I've got two meetings 01:05:15.179 --> 01:05:18.980 in the next two days. Okay, so we'll do one of 01:05:18.980 --> 01:05:21.119 our topics then. Yeah, okay, so we'll do one 01:05:21.119 --> 01:05:26.949 of our topics. And I have JaredReimer .com AAC 01:05:26.949 --> 01:05:29.769 stuff to do this weekend, so I don't have time. 01:05:30.889 --> 01:05:36.230 I barely got stuff up yesterday for this week, 01:05:36.250 --> 01:05:41.750 just because of what I've been doing. Yeah. I'm 01:05:41.750 --> 01:05:44.349 going to say, Terry, don't give him any more 01:05:44.349 --> 01:05:48.269 work on what he has. Yeah, no, we're fine. We 01:05:48.269 --> 01:05:52.789 got topics. We're fine. We have topics. Actually, 01:05:52.789 --> 01:05:54.849 Sarah, good morning. I'm going to be touring 01:05:54.849 --> 01:05:58.210 an apartment, it looks like, now. Okay, cool. 01:05:59.809 --> 01:06:01.869 Yeah, I think I might be getting a job soon, 01:06:01.989 --> 01:06:05.550 too. I'm working... I'll be working with a non 01:06:05.550 --> 01:06:11.650 -profit. Oh, yeah. I'd like that. I do, too. 01:06:12.269 --> 01:06:14.409 I've never heard of them, either. They're called 01:06:14.409 --> 01:06:18.610 Danka? Never heard of them. It's a job placement 01:06:18.610 --> 01:06:25.539 slash... computer like training nonprofit organization. 01:06:25.880 --> 01:06:27.679 I've never heard of them, but apparently they've 01:06:27.679 --> 01:06:30.079 been around for almost 40 years. So because I 01:06:30.079 --> 01:06:34.239 went on their website, I checked like when it 01:06:34.239 --> 01:06:37.340 was given to me, I went on their website and 01:06:37.340 --> 01:06:41.539 I looked at it and I looked at everything and 01:06:41.539 --> 01:06:45.719 looked at their different stuff like I should 01:06:45.719 --> 01:06:48.019 because I want to know a little bit about the 01:06:48.019 --> 01:06:51.880 company. I even did that with Ray Graham when 01:06:51.880 --> 01:06:55.119 they did the same thing. I wanted to see what 01:06:55.119 --> 01:06:58.059 their company was about. That's exactly what 01:06:58.059 --> 01:07:01.239 you should do. Research the company. Make sure 01:07:01.239 --> 01:07:03.480 you understand them. Because if they ask you 01:07:03.480 --> 01:07:08.119 questions during interviews, you'll know. Yep. 01:07:08.980 --> 01:07:10.960 That's what I was doing. When I went to OneBox 01:07:10.960 --> 01:07:14.739 in Hollywood, I knew exactly who they were because 01:07:14.739 --> 01:07:21.670 I was already using them. Yep. I kind of know 01:07:21.670 --> 01:07:23.949 a little bit about them and how long they've 01:07:23.949 --> 01:07:31.269 been around and what they do, so I'm good. Since 01:07:31.269 --> 01:07:35.469 I haven't been around the blogging scene, who 01:07:35.469 --> 01:07:44.090 has anything that they want to cover before we 01:07:44.090 --> 01:07:46.750 do a file switch and we do the whole AI thing? 01:07:49.300 --> 01:07:54.760 discussion for the week. Well, not really a lot. 01:07:54.960 --> 01:07:58.760 Mainly, it's been Sean going crazy on the blog 01:07:58.760 --> 01:08:04.579 about Microsoft and their screw -ups. What else 01:08:04.579 --> 01:08:08.599 is new? What else is new with that company? I 01:08:08.599 --> 01:08:14.480 heard they're being sued again over Microsoft 01:08:14.480 --> 01:08:20.439 Office. Really? Yeah. Missed that one. I heard 01:08:20.439 --> 01:08:25.659 they were being sued again. Nothing new. Nothing 01:08:25.659 --> 01:08:30.539 new. So, by the way, I had it generate, and I 01:08:30.539 --> 01:08:32.840 really hope I went to the right place, chatgpt 01:08:32.840 --> 01:08:41.000 .com. Yep. And it generated something for what 01:08:41.000 --> 01:08:47.369 we were talking about last night. Good. Good. 01:08:47.470 --> 01:08:52.689 So go ahead and edit that. And let me know when 01:08:52.689 --> 01:09:00.090 you want it aired. All right. Isn't AI great 01:09:00.090 --> 01:09:06.350 when you use it the right way, Jared? Oh, yes. 01:09:06.569 --> 01:09:10.949 Well, I told it. About NCSAM and how I want to 01:09:10.949 --> 01:09:18.789 tear my hair out, including the hair. Yeah, I 01:09:18.789 --> 01:09:25.229 can get that. And it said, you've been doing 01:09:25.229 --> 01:09:28.789 this too long and you're not wrong to feel frustrated. 01:09:29.029 --> 01:09:33.850 And as it said, the industry has moved. Steve 01:09:33.850 --> 01:09:36.750 Gibson and others. And I want to make this clear. 01:09:36.890 --> 01:09:40.470 They have moved the industry by forcing us to 01:09:40.470 --> 01:09:45.590 HTTPS, which we've talked about, forcing us to 01:09:45.590 --> 01:09:52.310 use some form of MFA, and forcing change that 01:09:52.310 --> 01:09:58.220 way. But as it comes to breaches... We're seeing 01:09:58.220 --> 01:10:01.819 more of them because they've been forced to regulate 01:10:01.819 --> 01:10:05.739 and force companies to come out publicly instead 01:10:05.739 --> 01:10:09.039 of quietly fixing them, which is what they were 01:10:09.039 --> 01:10:14.840 doing before. Target just made it a known problem. 01:10:15.779 --> 01:10:22.680 Yep. Trump Hotels back in 2016. was the first 01:10:22.680 --> 01:10:26.420 hospitality problem before breaches became mainstream. 01:10:27.500 --> 01:10:30.439 And if you want to go back and learn about some 01:10:30.439 --> 01:10:34.420 of these, go to jaredreimer .net slash articles 01:10:34.420 --> 01:10:40.699 dot html, I believe it is. If it's not l, it's 01:10:40.699 --> 01:10:46.300 htm. I believe it's html. I heard something really 01:10:46.300 --> 01:10:49.659 crazy. You'll find it in the vocals section. 01:10:50.239 --> 01:10:52.319 Yeah. Because I wrote for Vocal for a number 01:10:52.319 --> 01:10:57.039 of years. Iberwire was talking about people still 01:10:57.039 --> 01:11:01.720 using simple passwords, using their favorite 01:11:01.720 --> 01:11:06.039 type of burger or whatever from a fast food chain. 01:11:06.199 --> 01:11:08.960 And they said, you know. Oh, that's a terrible 01:11:08.960 --> 01:11:13.420 password. They're loving it. Well, at the end 01:11:13.420 --> 01:11:15.920 of it, and I thought, I mean, it's not funny, 01:11:16.020 --> 01:11:19.069 but it was funny. It said. You're loving it and 01:11:19.069 --> 01:11:21.649 so are the hackers. I'm like, yeah, of course. 01:11:21.770 --> 01:11:29.029 It's true. They are. I'm loving it. I'll have 01:11:29.029 --> 01:11:33.189 all your... I'm loving it. I'll have a McFlurry. 01:11:33.270 --> 01:11:37.829 That's my password. McFlurry26 or whatever. McFlurry26. 01:11:38.869 --> 01:11:42.069 One hacker's not going to know that. This goes 01:11:42.069 --> 01:11:45.670 back to my diatribe when I was referencing... 01:11:47.759 --> 01:11:55.300 The 25 password article that I posted on my blog. 01:11:56.739 --> 01:12:00.340 And it says, you're right. This is a continuing 01:12:00.340 --> 01:12:03.819 problem. And people like you continue to beat 01:12:03.819 --> 01:12:11.720 the drum. I mean, I'm paraphrasing now. And you're 01:12:11.720 --> 01:12:13.880 doing a good job of it, even if you want to tear 01:12:13.880 --> 01:12:18.180 your hair out. It's analyzing my writing. It 01:12:18.180 --> 01:12:21.300 sees my blog has been around since 11, even though 01:12:21.300 --> 01:12:28.100 I've been around since 06. We lost the blog twice 01:12:28.100 --> 01:12:34.560 during transfers, but that's the way it is. Can't 01:12:34.560 --> 01:12:38.739 go backwards. No. I've been with this company 01:12:38.739 --> 01:12:45.979 for a while now, but the point is... I think 01:12:45.979 --> 01:12:50.859 I hear a McSneezy over there. That's me. I'll 01:12:50.859 --> 01:12:55.720 be allergies. You're good. Well, what we've also 01:12:55.720 --> 01:12:58.600 got sometimes, at least on your side, is a McCoffee. 01:12:59.600 --> 01:13:04.000 We do. I think we have a McCoffee over here and 01:13:04.000 --> 01:13:11.640 a McSneezy over there. Boy, wouldn't it be fun 01:13:11.640 --> 01:13:15.310 to take this audio? Once I merge everything and 01:13:15.310 --> 01:13:20.250 say, analyze this and see what... Because it 01:13:20.250 --> 01:13:24.270 can't listen to audio fully, but it can analyze 01:13:24.270 --> 01:13:28.649 it and give a summary of discussion points. Some 01:13:28.649 --> 01:13:33.569 kind of a synopsis, yeah. Yeah. Because I did 01:13:33.569 --> 01:13:35.810 that with other episodes and tied it with the 01:13:35.810 --> 01:13:38.770 show notes and asked it how I can tighten things 01:13:38.770 --> 01:13:41.289 up and make sure that I'm more consistent in 01:13:41.289 --> 01:13:53.500 those notes. Yes. I know we got a ton of videos, 01:13:53.539 --> 01:13:56.880 so we're going to figure out the order after 01:13:56.880 --> 01:14:02.659 I deal with tonight's meeting. But we will play 01:14:02.659 --> 01:14:05.180 some number of files, because I think I've got, 01:14:05.279 --> 01:14:09.680 what, six or seven of these? Yeah. Quite a few 01:14:09.680 --> 01:14:12.699 of them. Yeah, just about. That was my homework. 01:14:13.500 --> 01:14:16.380 on a network update this past weekend, ladies 01:14:16.380 --> 01:14:22.020 and gentlemen. So, you're welcome. There's some 01:14:22.020 --> 01:14:28.199 good ones, I think. Right. I thought so. Yeah. 01:14:29.840 --> 01:14:32.960 Pretty elaborate, as usual. Pretty elaborate. 01:14:36.380 --> 01:14:42.439 Although, I may leave Kim. And it's not because 01:14:42.439 --> 01:14:47.960 I don't like Kim. I love Kim. But Kim is not 01:14:47.960 --> 01:14:59.699 reliable anymore. Her newsletters are becoming 01:14:59.699 --> 01:15:08.279 too much emoticon based. Because the tools are 01:15:08.279 --> 01:15:15.279 allowing it. And that generates Roy, known as... 01:15:15.279 --> 01:15:19.960 What is it? Return on Investment. I forget what 01:15:19.960 --> 01:15:26.000 it's called. Oh, thank you, Mr. J. I was going 01:15:26.000 --> 01:15:34.159 to have to go back to an app. Thank you. So the 01:15:34.159 --> 01:15:39.149 more clicks you get, the better you look. Well, 01:15:39.149 --> 01:15:41.630 this is unprofessional for people with disabilities. 01:15:42.449 --> 01:15:48.729 And it was so bad, Mr. J, that I shoved in the 01:15:48.729 --> 01:15:52.729 email that I got in regards to the voting for 01:15:52.729 --> 01:16:06.430 the board. And it had ballot box, telephone receiver, 01:16:07.289 --> 01:16:11.970 and other emoticons baked in its email, even 01:16:11.970 --> 01:16:15.510 though there was text in it. Oh my gosh. And 01:16:15.510 --> 01:16:24.770 ChatGPT said that this was not compliant. No, 01:16:24.890 --> 01:16:27.369 it should not be compliant. I wonder if somebody 01:16:27.369 --> 01:16:30.149 should get a hold of her network and say, look, 01:16:30.270 --> 01:16:35.930 you need to... I'm not going to waste my time. 01:16:36.050 --> 01:16:42.829 I'm just going to quietly leave. I think. I don't 01:16:42.829 --> 01:16:45.189 know how to unsubscribe from her newsletter. 01:16:45.189 --> 01:16:51.329 It's on the bottom of each newsletter. I've even 01:16:51.329 --> 01:16:53.449 been looking at her newsletters too and I'm just 01:16:53.449 --> 01:16:56.890 kind of like, what is this? They're too hard 01:16:56.890 --> 01:17:00.949 to read now. It is. That's why I stopped reading 01:17:00.949 --> 01:17:04.840 them because But I'm not even getting them reliably. 01:17:05.100 --> 01:17:08.739 I found a few in my spam folder. And Malwarebytes, 01:17:08.800 --> 01:17:12.000 I'm not even getting them reliably anymore either. 01:17:12.720 --> 01:17:20.199 I still get them. I don't. And I don't know that... 01:17:20.199 --> 01:17:22.899 But they're good. It wasn't... They don't have 01:17:22.899 --> 01:17:31.500 the same problem. No. Sadly, like you said, this 01:17:31.500 --> 01:17:36.779 seems to be driven by ROI and, oh, this is what 01:17:36.779 --> 01:17:39.800 people are doing now. Everybody uses them. That's 01:17:39.800 --> 01:17:43.039 exactly what the GPT said. They're doing it because 01:17:43.039 --> 01:17:48.159 the applications allow it. Allow it, yeah. And 01:17:48.159 --> 01:17:50.979 they're not caring about people. And they don't 01:17:50.979 --> 01:17:55.159 have to worry about it. They're not... And this 01:17:55.159 --> 01:17:57.859 is why I want to take this into an accessibility 01:17:57.859 --> 01:18:04.539 landscape because it's not secure. You're not 01:18:04.539 --> 01:18:10.600 adding any value to it. No. You are adding more 01:18:10.600 --> 01:18:13.319 noise because the screen reader has to interpret 01:18:13.319 --> 01:18:19.640 through its understanding of what these emoticons 01:18:19.640 --> 01:18:21.600 are. And they're trained. They've got all of 01:18:21.600 --> 01:18:29.010 that in their coding. I think it makes you look 01:18:29.010 --> 01:18:31.750 less and less professional. When I see those 01:18:31.750 --> 01:18:36.670 things, it's like, oh my gosh, did some emo teenager 01:18:36.670 --> 01:18:41.649 write this? No, it's very unprofessional. It 01:18:41.649 --> 01:18:46.250 even said Kim Commando is not that reliable anymore 01:18:46.250 --> 01:18:52.159 because of it. No. She may tout the 800 ,000 01:18:52.159 --> 01:18:54.539 subscribers that she's got. That's all well and 01:18:54.539 --> 01:19:02.140 good. 90 % of those subscribers are excited who 01:19:02.140 --> 01:19:07.300 could see that and read it. And say nothing. 01:19:08.380 --> 01:19:11.680 And say nothing. Because it doesn't matter. If 01:19:11.680 --> 01:19:14.819 you get their news, that's it. Even some of them 01:19:14.819 --> 01:19:20.539 might say... Really? We're not teenagers? Yeah, 01:19:20.560 --> 01:19:22.800 but how many of them are going to complain, Nick? 01:19:22.800 --> 01:19:29.159 Not very many. You know? Don't look at it and 01:19:29.159 --> 01:19:31.260 say, okay, cool, I got my news. I'm done. Cool, 01:19:31.380 --> 01:19:34.960 thanks. Yeah, we're not teenagers or 20 -somethings, 01:19:34.960 --> 01:19:37.060 but yes, I see what you're saying. Yeah, no, 01:19:37.140 --> 01:19:40.220 I get it. I get what you mean. I'm 40 -plus years 01:19:40.220 --> 01:19:45.859 old, and I'm irritated about today's writing. 01:19:48.050 --> 01:19:51.210 Yeah. Oh, yeah. I don't use that. Hardly at all. 01:19:51.210 --> 01:19:52.890 I don't use emoticons. Yeah, because people think... 01:19:52.890 --> 01:19:55.850 Because not only is it... I do that in text. 01:19:57.270 --> 01:20:02.449 Right. But very, very minimal. Thumbs up. That's 01:20:02.449 --> 01:20:08.090 my point. Sad face. Yeah. If, you know... Yeah. 01:20:08.170 --> 01:20:12.010 Right. And now there are people... I thought... 01:20:12.010 --> 01:20:14.670 I mean, I hope it was a joke, but I thought I 01:20:14.670 --> 01:20:18.470 remember hearing something where... Some professor 01:20:18.470 --> 01:20:23.810 actually allowed somebody to submit an assignment 01:20:23.810 --> 01:20:27.229 written in texting language. It's like, oh, that's 01:20:27.229 --> 01:20:31.470 so wrong. If that's true. That has to go into 01:20:31.470 --> 01:20:34.010 the you -have -to -be -fucking -kidding -me department. 01:20:34.449 --> 01:20:42.569 I hope it was. If you find it, if you find it, 01:20:42.590 --> 01:20:49.909 shove it up. Our ass. I would be curious to read 01:20:49.909 --> 01:20:53.329 it. Our ass is so full of stuff anyway, but you 01:20:53.329 --> 01:20:58.789 know, whatever. By the way, I gave ChatGPT a 01:20:58.789 --> 01:21:02.149 good one yesterday. After I was done and before 01:21:02.149 --> 01:21:05.409 I rolled over, I said, maybe tomorrow I'll shove 01:21:05.409 --> 01:21:08.789 the San Fernando Service Council agenda up your 01:21:08.789 --> 01:21:12.470 ass and you can remind me what it's about even 01:21:12.470 --> 01:21:15.100 though I have the braille available. It's sort 01:21:15.100 --> 01:21:17.760 of like, yeah, my ass will be waiting for it 01:21:17.760 --> 01:21:23.439 whenever you're ready. Oh, yes. That's right. 01:21:26.779 --> 01:21:29.920 Yeah, I'm ordering a product and I told Gemini, 01:21:29.960 --> 01:21:31.920 I said, I'm going to give you a review on this 01:21:31.920 --> 01:21:34.659 because I want to, you know, oh, no problem. 01:21:34.819 --> 01:21:36.899 I'll see you on Friday. We'll give you, give 01:21:36.899 --> 01:21:43.869 me your review. Okay, cool. I use both services. 01:21:44.170 --> 01:21:47.930 I use Gemini and ChatGPT. I mean, I like both. 01:21:48.970 --> 01:21:54.609 While we're going to be switching to the topic, 01:21:54.750 --> 01:21:59.210 we can talk about your usage of both in each 01:21:59.210 --> 01:22:06.729 section of the AI discussion. Mr. R? Yeah, we 01:22:06.729 --> 01:22:12.399 can. Mr. R, yeah. Mr. R? Just like me? Mr. R? 01:22:13.460 --> 01:22:20.079 There's two R's? Both R's here. Both R's here? 01:22:24.659 --> 01:22:28.920 Let's play some files. Let's take a file break. 01:22:29.180 --> 01:22:32.119 When we come back, we're going to do AI. How's 01:22:32.119 --> 01:22:36.109 that, gentlemen? That's great. AI sounds awesome. 01:22:36.109 --> 01:22:38.689 That's right. The way of the future. Artificial 01:22:38.689 --> 01:22:43.609 intelligence, boys. Terry Ring, Preston Gaylor, 01:22:43.710 --> 01:22:47.010 Jared Reimer, Nicholas Jackson. We continue right 01:22:47.010 --> 01:22:51.109 after these across the Jared Reimer Radio Network. 01:22:54.510 --> 01:22:57.270 Would you want your government, whatever government 01:22:57.270 --> 01:22:59.829 you live under, to generate pictures and videos 01:22:59.829 --> 01:23:01.949 on social media using artificial intelligence? 01:23:03.140 --> 01:23:05.000 That's what we're talking about today. I'm Nick 01:23:05.000 --> 01:23:07.939 Espinosa, your chief security fanatic. And let's 01:23:07.939 --> 01:23:10.140 dive into this because I personally think that 01:23:10.140 --> 01:23:12.960 governments should not be using artificial intelligence 01:23:12.960 --> 01:23:16.199 for images and videos. Now, MIT Technology Review 01:23:16.199 --> 01:23:18.460 had a really interesting write up on this. And 01:23:18.460 --> 01:23:20.960 James O'Donnell, the author of this, basically 01:23:20.960 --> 01:23:23.220 put out quite good information. We're going to 01:23:23.220 --> 01:23:25.199 crib a little bit. And then I'm going to dive 01:23:25.199 --> 01:23:27.020 in. But if you didn't know, the U .S. Department 01:23:27.020 --> 01:23:31.199 of Homeland Security, aka DHS, is using AI video 01:23:31.199 --> 01:23:34.239 generators from both Google and Adobe to make 01:23:34.239 --> 01:23:36.680 and edit content shared with the public. This 01:23:36.680 --> 01:23:38.840 is according to a new document. You know, I'm 01:23:38.840 --> 01:23:40.979 going to do my normal preamble that says cybersecurity 01:23:40.979 --> 01:23:43.880 is agnostic from politics, but we're not immune 01:23:43.880 --> 01:23:45.920 from it. And I do not care what your political 01:23:45.920 --> 01:23:48.539 beliefs are, if you are for or against all of 01:23:48.539 --> 01:23:51.779 the actions that DHS has taken. Under the Trump 01:23:51.779 --> 01:23:53.979 administration or previous administrations as 01:23:53.979 --> 01:23:56.539 well. The point here is to talk about the artificial 01:23:56.539 --> 01:24:00.640 intelligence side of this issue. This is also 01:24:00.640 --> 01:24:03.500 coming as U .S. immigration agencies have been 01:24:03.500 --> 01:24:05.560 flooding social media with content to support 01:24:05.560 --> 01:24:08.239 President Trump's deportation agenda, some of 01:24:08.239 --> 01:24:11.779 which appears to be made by AI. Now, this document 01:24:11.779 --> 01:24:14.619 that was released the other day provides an inventory 01:24:14.619 --> 01:24:18.100 of commercial AI tools that DHS is using for 01:24:18.100 --> 01:24:20.359 tasks ranging from generating drafts of documents 01:24:20.359 --> 01:24:22.819 to managing cybersecurity. I don't necessarily 01:24:22.819 --> 01:24:26.260 mind them generating documents using artificial 01:24:26.260 --> 01:24:29.640 intelligence or first drafts of documents. Providing, 01:24:29.640 --> 01:24:31.180 obviously, there's human intervention to make 01:24:31.180 --> 01:24:34.039 sure that they are accurate. Basically, the UK 01:24:34.039 --> 01:24:36.239 just got in trouble for that. And on the cybersecurity 01:24:36.239 --> 01:24:38.420 side, I would hope that there are qualified cybersecurity 01:24:38.420 --> 01:24:40.920 professionals reviewing what the AI thinks it 01:24:40.920 --> 01:24:43.539 should be doing. Now, in the section on this 01:24:43.539 --> 01:24:46.180 document, basically about, quote, editing images, 01:24:46.359 --> 01:24:49.159 videos, or other public affairs materials using 01:24:49.159 --> 01:24:52.560 AI, end quote. It reveals for the first time 01:24:52.560 --> 01:24:56.600 that DHS is using Google's Veo 3 image generator 01:24:56.600 --> 01:25:00.100 and Adobe Firefly. And it's estimated that the 01:25:00.100 --> 01:25:03.140 agency has somewhere between 100 to 1000 licenses. 01:25:03.800 --> 01:25:06.199 for these particular tools. It also disclosed 01:25:06.199 --> 01:25:09.779 that DHS uses Microsoft Copilot Chat for generating 01:25:09.779 --> 01:25:12.859 first drafts of documents, summarizing long reports, 01:25:13.060 --> 01:25:15.619 and they're also using Poolside, essentially 01:25:15.619 --> 01:25:18.239 that's software for coding tasks, on top of the 01:25:18.239 --> 01:25:19.920 tools from other companies as well. But again, 01:25:20.079 --> 01:25:22.579 we're only focusing on image and video generation 01:25:22.579 --> 01:25:25.880 for social media. That's my big issue here. Now, 01:25:25.880 --> 01:25:28.340 the news also provides details about how agencies 01:25:28.340 --> 01:25:30.979 like ICE, that is Immigrations and Customs Enforcement, 01:25:31.159 --> 01:25:34.600 which is part of DHS, might be creating the large 01:25:34.600 --> 01:25:37.180 amounts of content that they've shared on X and 01:25:37.180 --> 01:25:39.760 other social media platforms and channels and 01:25:39.760 --> 01:25:42.979 all of that as immigration operations have expanded 01:25:42.979 --> 01:25:45.220 around the United States. We've seen them in 01:25:45.220 --> 01:25:48.000 Chicago, Los Angeles, New York, obviously most 01:25:48.000 --> 01:25:51.279 recently in Minnesota, recently expanded into 01:25:51.279 --> 01:25:53.819 Portland, Maine, and some other places as well. 01:25:54.470 --> 01:25:57.550 Some of this content, particularly videos, has 01:25:57.550 --> 01:26:00.449 the appearance of being AI generated, but it 01:26:00.449 --> 01:26:03.750 hasn't been clear until now what AI models the 01:26:03.750 --> 01:26:06.390 agency might be using. And this marks the first 01:26:06.390 --> 01:26:08.829 concrete evidence that such generators are being 01:26:08.829 --> 01:26:11.989 used by DHS to create content shared with the 01:26:11.989 --> 01:26:15.489 public. And this is essentially a social media 01:26:15.489 --> 01:26:18.430 era. We have seen just an enormous amount of 01:26:18.430 --> 01:26:20.869 this kind of stuff coming from DHS and other 01:26:20.869 --> 01:26:23.850 government agencies as well. There's a lot more 01:26:23.850 --> 01:26:26.310 to that article from MIT Technology Review. I 01:26:26.310 --> 01:26:28.890 thought it was a great write up. But I want to 01:26:28.890 --> 01:26:30.970 dive into this because personally, I don't think 01:26:30.970 --> 01:26:34.149 any agency of any government, you know, it could 01:26:34.149 --> 01:26:37.390 be the federal dog catching agency should be 01:26:37.390 --> 01:26:40.350 using AI for pictures or videos, you know, for 01:26:40.350 --> 01:26:42.029 their social media presence. And I've been thinking 01:26:42.029 --> 01:26:44.789 about this a lot today. After I read this article 01:26:44.789 --> 01:26:47.569 this morning, and quite frankly, here are my 01:26:47.569 --> 01:26:49.890 concerns with this. I mean, first things first, 01:26:49.949 --> 01:26:52.449 government communications have historically derived 01:26:52.449 --> 01:26:55.109 their authority, but also their authenticity, 01:26:55.510 --> 01:26:58.350 right? They have derived that authority from 01:26:58.350 --> 01:27:00.829 the authenticity and accountability. It's not 01:27:00.829 --> 01:27:03.300 been the creativity of the government. Right. 01:27:03.340 --> 01:27:07.420 What we need is accurate information. AI generated 01:27:07.420 --> 01:27:10.819 visuals are blurring the line between the official 01:27:10.819 --> 01:27:13.579 record that they should be putting out, whether 01:27:13.579 --> 01:27:16.779 it's on social media or even on paper. And that 01:27:16.779 --> 01:27:19.939 fake and synthetic content that we are just seeing 01:27:19.939 --> 01:27:22.079 absolutely explode inside and outside of the 01:27:22.079 --> 01:27:24.909 government. That is literally. undermining public 01:27:24.909 --> 01:27:28.050 confidence in what we are seeing or what they 01:27:28.050 --> 01:27:32.409 are putting out. Even benign AI imagery can be 01:27:32.409 --> 01:27:34.770 interpreted as tantamount to state -sanctioned 01:27:34.770 --> 01:27:38.850 manipulation. I mean, think about that. One of 01:27:38.850 --> 01:27:40.770 the thoughts that I had in my head is this feels 01:27:40.770 --> 01:27:43.409 like state -sanctioned manipulation because an 01:27:43.409 --> 01:27:46.409 AI -generated image is something you tell the 01:27:46.409 --> 01:27:48.689 AI to create. It's not what actually happened 01:27:48.689 --> 01:27:51.369 in time. And as we've seen these protests and 01:27:51.369 --> 01:27:54.560 raids and all this kind of stuff again, I'm not 01:27:54.560 --> 01:27:57.020 getting political here. If they are putting out 01:27:57.020 --> 01:27:59.760 AI content that looks like something like that, 01:27:59.779 --> 01:28:01.460 but it's one thing or the other, or they're even 01:28:01.460 --> 01:28:04.699 cleaning up images of, let's say, a bad event 01:28:04.699 --> 01:28:07.460 or something, then yes, it's going to undermine 01:28:07.460 --> 01:28:09.939 public confidence, especially if we're talking 01:28:09.939 --> 01:28:13.140 about times like elections, just various crises 01:28:13.140 --> 01:28:16.840 that governments tend to go through. civil unrest, 01:28:17.119 --> 01:28:19.840 all these things start to really become undermined 01:28:19.840 --> 01:28:21.779 because the information that are putting out 01:28:21.779 --> 01:28:25.739 isn't necessarily real, right? Once trust is 01:28:25.739 --> 01:28:29.899 lost, it's nearly impossible to restore. And 01:28:29.899 --> 01:28:32.520 that's regardless of intent. And I think that's 01:28:32.520 --> 01:28:35.060 a huge, huge thing. And on top of it, we have 01:28:35.060 --> 01:28:37.119 the disinformation and misinformation problem. 01:28:37.260 --> 01:28:39.220 This is created. We've seen foreign intelligence 01:28:39.220 --> 01:28:42.000 agencies left and right do this. And now the 01:28:42.000 --> 01:28:45.899 AI can crank it out 24 -7, 365. Generative AI 01:28:45.899 --> 01:28:48.859 systems hallucinate. And they hallucinate everything 01:28:48.859 --> 01:28:52.260 from context to symbols to uniforms to signage. 01:28:52.899 --> 01:28:55.789 Environments that... like appear real, but they're 01:28:55.789 --> 01:28:59.170 factually wrong. And that's a big issue for any 01:28:59.170 --> 01:29:01.949 government agency to put these things out. Visual 01:29:01.949 --> 01:29:06.220 errors. spread faster than corrections right 01:29:06.220 --> 01:29:10.199 you know and that's an issue so they're weaponized 01:29:10.199 --> 01:29:12.739 and they're typically weaponized by adversaries 01:29:12.739 --> 01:29:15.180 of let's say the united states in this case or 01:29:15.180 --> 01:29:16.720 if it's coming from another country whatever 01:29:16.720 --> 01:29:20.239 adversary that country has foreign influence 01:29:20.239 --> 01:29:23.060 operations actively reuse government looking 01:29:23.060 --> 01:29:26.159 ai imagery to fabricate narratives they create 01:29:26.159 --> 01:29:28.560 plausible deniability all these different kinds 01:29:28.560 --> 01:29:30.819 of things as well and government originated synthetic 01:29:30.819 --> 01:29:35.840 media also in my opinion lowers the bar for copycats. 01:29:36.250 --> 01:29:38.949 For bad actors, like this is a huge problem. 01:29:39.170 --> 01:29:41.010 And then there's other factors on top of it as 01:29:41.010 --> 01:29:44.689 well, like legal, you know, record keeping, evidentiary 01:29:44.689 --> 01:29:46.670 exposures, like all of these different kinds 01:29:46.670 --> 01:29:48.850 of things that goes into this because the government 01:29:48.850 --> 01:29:51.770 has records acts to ensure that they're transparent, 01:29:52.109 --> 01:29:54.529 that they're accurate, that they're not putting 01:29:54.529 --> 01:29:56.909 things out there that could be misinterpreted. 01:29:56.909 --> 01:29:59.890 And that's what we see, right? Adversaries can 01:29:59.890 --> 01:30:02.750 study AI generated government content to reverse 01:30:02.750 --> 01:30:05.609 engineer things like messaging strategy, right? 01:30:05.640 --> 01:30:07.939 On top of it, tone. Think about the tone, the 01:30:07.939 --> 01:30:10.239 priorities, all of that. It would be very easy 01:30:10.239 --> 01:30:11.979 to replicate this stuff and make it look like 01:30:11.979 --> 01:30:14.560 it's coming out of DHS because we can use the 01:30:14.560 --> 01:30:18.579 same AI image generators they can. Not to mention, 01:30:18.720 --> 01:30:21.520 if I'm thinking about this, government runs on 01:30:21.520 --> 01:30:24.000 accountability, but it's human accountability. 01:30:24.979 --> 01:30:27.399 If the AI is generating it, everybody can point 01:30:27.399 --> 01:30:29.539 the finger at everybody else and who did this 01:30:29.539 --> 01:30:32.779 and what. It's a huge issue. If I'm thinking 01:30:32.779 --> 01:30:35.640 about it from a risk situation, I'm thinking 01:30:35.640 --> 01:30:38.659 about it from a crisis situation or risk crisis, 01:30:38.760 --> 01:30:41.140 right? Because AI generated visual mistakes could 01:30:41.140 --> 01:30:44.260 be mistaken for real world conditions that can 01:30:44.260 --> 01:30:47.619 cause a panic, right? Or it might cause complacency, 01:30:47.619 --> 01:30:49.920 all of these different kinds of things. This 01:30:49.920 --> 01:30:53.739 just destroys trust. And whether you trust, let's 01:30:53.739 --> 01:30:55.579 say the DHS and the Trump administration, all 01:30:55.579 --> 01:30:57.779 that, or you don't, again, that's your business, 01:30:57.819 --> 01:31:01.100 not mine. The point is, is that if they're putting 01:31:01.100 --> 01:31:03.960 stuff out that you trust, you're going to trust 01:31:03.960 --> 01:31:06.439 it. You're going to think it's real. And when 01:31:06.439 --> 01:31:08.340 they do start putting out things that are actually 01:31:08.340 --> 01:31:10.260 real, like let's say it's, I don't know, the 01:31:10.260 --> 01:31:12.899 ratio, one real, the five AI generated or vice 01:31:12.899 --> 01:31:15.479 versa. But when that one real image comes out 01:31:15.479 --> 01:31:17.720 or video comes out, those that distrust will 01:31:17.720 --> 01:31:22.159 simply say it's AI as well. We are eroding confidence 01:31:22.159 --> 01:31:24.300 in ourselves. We are eroding trust in ourselves 01:31:24.300 --> 01:31:27.420 by default, by being on social media. But when 01:31:27.420 --> 01:31:29.579 the government gets involved and does the same 01:31:29.579 --> 01:31:32.800 thing. It's so hard to draw. It's so hard to 01:31:32.800 --> 01:31:35.560 claw back. It's so hard to change this. This 01:31:35.560 --> 01:31:38.479 is not good. And I think we need to stop. And 01:31:38.479 --> 01:31:40.340 I think there needs to be laws around having 01:31:40.340 --> 01:31:43.520 a government or rather allowing the government 01:31:43.520 --> 01:31:47.500 to use AI to generate videos and images that 01:31:47.500 --> 01:31:49.979 people are going to look at and believe. That's 01:31:49.979 --> 01:31:52.920 not good. And I think that's of deep, deep concern. 01:31:53.060 --> 01:31:54.920 And again, I don't care what government is doing 01:31:54.920 --> 01:31:57.979 this. This is just not good. And that is your 01:31:57.979 --> 01:32:00.539 unfortunate news of the day. And please like, 01:32:00.579 --> 01:32:02.159 share, follow me here on Facebook and Twitter 01:32:02.159 --> 01:32:05.000 at NickAESP, where I'm not AI -generated, but 01:32:05.000 --> 01:32:07.659 I will talk about them. And please feel free 01:32:07.659 --> 01:32:09.779 to subscribe to me wherever you can. And as always, 01:32:09.859 --> 01:32:12.159 stay safe, stay online, and please, please, please, 01:32:12.319 --> 01:32:15.640 everyone stay private, informed, and secure. 01:32:16.260 --> 01:32:19.720 Take care. Hey, everybody. Nick Espinosa, your 01:32:19.720 --> 01:32:21.840 chief security fanatic here. Don't forget to 01:32:21.840 --> 01:32:24.520 subscribe. And it's Sunday, so we are doing Breaches 01:32:24.520 --> 01:32:28.020 of the Week, as always. This week in Data Breaches. 01:32:28.619 --> 01:32:31.560 Well, this may actually be the longest list of 01:32:31.560 --> 01:32:34.880 litigation and payouts we have ever done on a 01:32:34.880 --> 01:32:37.439 Breaches of the Week segment. I mean, wow. Like, 01:32:37.500 --> 01:32:40.300 most of what I found today, or it seems like 01:32:40.300 --> 01:32:42.699 basically the past week, has been nothing but 01:32:42.699 --> 01:32:45.159 lawsuits and payments. So, thank you very much 01:32:45.159 --> 01:32:48.159 to James Beneke. steve hamlin jacqueline wolf 01:32:48.159 --> 01:32:50.279 and jason acton for sending me a lot of this 01:32:50.279 --> 01:32:52.180 information and we're going to dive just right 01:32:52.180 --> 01:32:54.800 into our mini segment which is bigger than i 01:32:54.800 --> 01:32:58.060 the regular segment i think simply entitled if 01:32:58.060 --> 01:33:00.520 you had just spent money on cyber security you 01:33:00.520 --> 01:33:02.239 wouldn't be getting sued you wouldn't be paying 01:33:02.239 --> 01:33:04.819 out you wouldn't be losing your reputation and 01:33:04.819 --> 01:33:06.319 we sure as heck wouldn't be talking about you 01:33:06.319 --> 01:33:08.880 right now and with that let's start with first 01:33:08.880 --> 01:33:12.710 choice dental Now, dental patients there have 01:33:12.710 --> 01:33:14.710 less than two weeks to get their hands on part 01:33:14.710 --> 01:33:18.710 of the $1 .2 million settlement. So if you basically 01:33:18.710 --> 01:33:21.590 were affected by this, you have until January 01:33:21.590 --> 01:33:26.189 28th, 2026 to basically submit a claim. Patients 01:33:26.189 --> 01:33:28.989 who did not experience economic losses can still 01:33:28.989 --> 01:33:32.449 get a payment of up to $50. And all class members 01:33:32.449 --> 01:33:34.250 are entitled to free credit monitoring, which 01:33:34.250 --> 01:33:36.750 includes $1 million worth of identity theft. 01:33:37.710 --> 01:33:40.590 First choice dental patients, go get paid. Moving 01:33:40.590 --> 01:33:43.289 on, Kaiser Permanente, the massive healthcare 01:33:43.289 --> 01:33:46.229 system, members may qualify for a payment as 01:33:46.229 --> 01:33:49.649 part of their $46 million settlement. The settlement 01:33:49.649 --> 01:33:51.930 is a result of multiple lawsuits filed in April 01:33:51.930 --> 01:33:55.210 and May of 2024, which were combined into a class 01:33:55.210 --> 01:33:58.779 action in December of that year. Heads up to 01:33:58.779 --> 01:34:01.720 members in California, Colorado, Georgia, Hawaii, 01:34:01.979 --> 01:34:05.079 Maryland, Oregon, Virginia, Washington, and the 01:34:05.079 --> 01:34:09.460 District of Columbia. Basically, if you are a 01:34:09.460 --> 01:34:13.079 member or a former member or patient of Kaiser 01:34:13.079 --> 01:34:15.569 Permanente from one of those states. Basically, 01:34:15.670 --> 01:34:17.689 and you access the mobile app between November 01:34:17.689 --> 01:34:22.289 of 2017 to May 2024, you're eligible for part 01:34:22.289 --> 01:34:25.329 of that settlement. Now, basically, you can receive 01:34:25.329 --> 01:34:28.649 a pro rata share of the net settlement for a 01:34:28.649 --> 01:34:31.149 one -time cash payment as well. Most people that 01:34:31.149 --> 01:34:35.750 file will get $20 to $40, and you can go to KaiserPrivacySettlement 01:34:35.750 --> 01:34:39.449 .com. Again, that's KaiserPrivacySettlement .com 01:34:39.449 --> 01:34:42.649 to get your claim. Moving on. Let's head on over 01:34:42.649 --> 01:34:44.390 to Rhode Island and talk about Rhode Island's 01:34:44.390 --> 01:34:47.569 RIPTA as well as UnitedHealthcare. Current and 01:34:47.569 --> 01:34:50.050 former Rhode Island state employees have begun 01:34:50.050 --> 01:34:53.270 receiving payments basically via the settlement 01:34:53.270 --> 01:34:56.510 over that 2021 data breach, including both RIPTA 01:34:56.510 --> 01:34:59.369 and UnitedHealth. So these payments are averaging 01:34:59.369 --> 01:35:02.289 more than $400 per claimant, which is a really 01:35:02.289 --> 01:35:04.489 good number for the record, are going out to 01:35:04.489 --> 01:35:06.949 state employees who filed claims as part of that 01:35:06.949 --> 01:35:10.590 class action lawsuit. basically the ACLU of Rhode 01:35:10.590 --> 01:35:14.590 Island v. RIPTA and essentially the insurer as 01:35:14.590 --> 01:35:17.270 well in 2022. The lawsuits were settled for more 01:35:17.270 --> 01:35:20.069 than $350 ,000. Claimants were allowed to request 01:35:20.069 --> 01:35:22.970 up to $1 ,000 for out -of -pocket expenses and 01:35:22.970 --> 01:35:24.850 essentially affected state workers could also 01:35:24.850 --> 01:35:27.130 claim five years of credit monitoring. which 01:35:27.130 --> 01:35:31.149 is estimated to cost about $840 a person. So 01:35:31.149 --> 01:35:33.710 it's actually a pretty solid payout. As you know, 01:35:33.729 --> 01:35:35.930 I talk about basically these payouts all the 01:35:35.930 --> 01:35:39.229 time, and they're usually like $1 to $50 at best. 01:35:39.229 --> 01:35:43.229 So $400, not bad, Rhode Island, not bad. Moving 01:35:43.229 --> 01:35:48.239 on. New Motion, excuse me, they agreed to a class 01:35:48.239 --> 01:35:50.260 action lawsuit settlement to resolve claims surrounding 01:35:50.260 --> 01:35:52.819 their two data breaches that occurred in March 01:35:52.819 --> 01:35:56.060 and September of 2024. The New Motion settlement 01:35:56.060 --> 01:35:58.579 benefits individuals who received that notice 01:35:58.579 --> 01:36:01.279 about those breaches and an additional subclass 01:36:01.279 --> 01:36:03.279 whose social security numbers may have been involved 01:36:03.279 --> 01:36:05.899 in this. They've agreed to pay up to $4 million 01:36:05.899 --> 01:36:09.460 to basically resolve claims. And if you've got 01:36:09.460 --> 01:36:12.140 serious damages, you can get up to $15 ,000 in 01:36:12.140 --> 01:36:15.560 reimbursement. all of that so if you are eligible 01:36:15.560 --> 01:36:18.140 you are eligible also for two years of credit 01:36:18.140 --> 01:36:21.020 monitoring as well so heads up to you new motion 01:36:21.020 --> 01:36:26.039 patients or patrons moving on farm america They 01:36:26.039 --> 01:36:28.399 agreed to settle a class action over their 2023 01:36:28.399 --> 01:36:32.039 hacking incident that involved 5 .8 million individuals. 01:36:32.439 --> 01:36:35.140 So in addition to paying 5 .2 million to cover 01:36:35.140 --> 01:36:37.420 costs and benefits, Far America has committed 01:36:37.420 --> 01:36:39.619 to investing millions to strengthen its security 01:36:39.619 --> 01:36:42.319 posture. Basically, the preliminary approval 01:36:42.319 --> 01:36:45.199 was on January 12th of this year, and you have 01:36:45.199 --> 01:36:47.939 a deadline to opt out on April 20th, and your 01:36:47.939 --> 01:36:51.779 claims must be submitted. by april 27th basically 01:36:51.779 --> 01:36:53.600 in the fairness hearing has been scheduled for 01:36:53.600 --> 01:36:56.659 may 12th so heads up to you for america patients 01:36:56.659 --> 01:37:00.039 go get paid moving on next gen health care they've 01:37:00.039 --> 01:37:02.880 agreed to a 19 .4 million dollar class action 01:37:02.880 --> 01:37:06.199 settlement basically for their 2023 data breach 01:37:06.779 --> 01:37:08.600 Under these terms, you can receive compensation 01:37:08.600 --> 01:37:11.279 for out -of -pocket expenses for up to $7 ,500. 01:37:12.020 --> 01:37:16.140 And you can also get 10 hours of lost time recouped 01:37:16.140 --> 01:37:19.300 at $25 an hour. And here we are. Most class members 01:37:19.300 --> 01:37:22.199 are going to receive $50 to $150 if they lived 01:37:22.199 --> 01:37:25.359 in California during that period. And your time 01:37:25.359 --> 01:37:28.899 for exclusions and objections is February 12th. 01:37:28.899 --> 01:37:30.600 And that settlement is scheduled for February 01:37:30.600 --> 01:37:35.579 17th. So go get paid. Moving on, Veridigm. They 01:37:35.579 --> 01:37:38.100 agreed to a $10 .5 million, I'm telling you, 01:37:38.100 --> 01:37:40.640 it just keeps going, class action lawsuit settlement 01:37:40.640 --> 01:37:43.039 to resolve claims from their 2024 data breach. 01:37:43.340 --> 01:37:46.039 Basically, this is benefiting individuals who 01:37:46.039 --> 01:37:48.720 received a notice informing them that they may 01:37:48.720 --> 01:37:51.399 have been compromised in the December 2024 data 01:37:51.399 --> 01:37:54.520 breach, and they are agreeing to a $10 .5 million 01:37:54.520 --> 01:37:57.460 payout. That's all I know. Heads up, Veridigm. 01:37:57.520 --> 01:38:00.180 Moving on, Richmond Behavioral Health Authority. 01:38:00.859 --> 01:38:03.159 Basically, three class action lawsuits have now 01:38:03.159 --> 01:38:06.119 been filed against them. them basically do a 01:38:06.119 --> 01:38:08.979 data breach back in September. All three of these 01:38:08.979 --> 01:38:11.239 suits have been filed in the U .S. District Court 01:38:11.239 --> 01:38:12.859 for the Eastern District of Virginia, which I 01:38:12.859 --> 01:38:15.500 believe is the rocket docket, by former patients, 01:38:15.619 --> 01:38:17.920 basically. And they're claiming, obviously, that 01:38:17.920 --> 01:38:20.399 they failed to secure the data. So Richmond Behavioral 01:38:20.399 --> 01:38:23.000 Health Authority in the works. Moving on, heading 01:38:23.000 --> 01:38:26.850 over to France. Let's talk about FreeSAS and 01:38:26.850 --> 01:38:29.890 its sister company, FreeMobile. These are some 01:38:29.890 --> 01:38:33.229 of the largest mobile services in the country. 01:38:33.430 --> 01:38:36.229 And France's data protection regulator has fined 01:38:36.229 --> 01:38:39.449 the telecom giant 42 million US over cybersecurity 01:38:39.449 --> 01:38:41.409 vulnerabilities that contributed to this massive 01:38:41.409 --> 01:38:44.949 breach. So Free was fined 27 million euros or 01:38:44.949 --> 01:38:49.359 31 million US. And Free SAS was fined 15 million 01:38:49.359 --> 01:38:52.800 euros or 17 million US according to the CNIL, 01:38:52.800 --> 01:38:55.199 which is their regulator. Spokesperson for the 01:38:55.199 --> 01:38:57.420 group basically said in a statement that they're 01:38:57.420 --> 01:38:59.640 going to appeal the decision to France's Supreme 01:38:59.640 --> 01:39:03.079 Administrative Court. So heads up to you. If 01:39:03.079 --> 01:39:06.319 you are a Free or Free SAS patron, you might 01:39:06.319 --> 01:39:09.899 get paid at some point. Moving on. University 01:39:09.899 --> 01:39:12.960 of Phoenix and Oracle. Yes, Oracle is always 01:39:12.960 --> 01:39:15.380 in the news. A new class action alleges that 01:39:15.380 --> 01:39:17.680 University of Phoenix and Oracle failed to properly 01:39:17.680 --> 01:39:20.380 safeguard person identifiable information for 01:39:20.380 --> 01:39:22.159 three and a half million students during the 01:39:22.159 --> 01:39:25.619 August 2025 data breach. Now, plaintiff Tia Poynter 01:39:25.619 --> 01:39:28.699 claims that the University of Phoenix and Oracle, 01:39:28.819 --> 01:39:30.819 quote, failed to implement and maintain reasonable 01:39:30.819 --> 01:39:33.180 security measures, end quote. Now, remember, 01:39:33.319 --> 01:39:36.000 this is basically Oracle, right? I mean, Oracle 01:39:36.000 --> 01:39:38.340 is the one that got breached, but due to supply. 01:39:38.670 --> 01:39:40.949 all of these organizations in this case the university 01:39:40.949 --> 01:39:43.869 get dragged into it now pointer argues that an 01:39:43.869 --> 01:39:45.649 unauthorized third party exploited vulnerability 01:39:45.649 --> 01:39:48.750 in e -business which yes we all know that happened 01:39:48.750 --> 01:39:50.949 and so we'll see what happens she has to show 01:39:50.949 --> 01:39:53.710 that uh basically she's got claims for damages 01:39:53.710 --> 01:39:57.529 but either way class actions are coming and oracle 01:39:57.529 --> 01:39:59.250 is going to be paying out through the nose hopefully 01:39:59.250 --> 01:40:02.159 well Probably not enough to bankrupt them, but, 01:40:02.220 --> 01:40:04.699 you know, a boy can hope. Moving on, there's 01:40:04.699 --> 01:40:08.159 more. Margaritaville at sea. I am assuming Jimmy 01:40:08.159 --> 01:40:11.239 Buffett or Jimmy Buffett licensed. Anyway, a 01:40:11.239 --> 01:40:13.659 new class action against Margaritaville at sea, 01:40:13.720 --> 01:40:15.479 which just seems like a rather relaxing place, 01:40:15.640 --> 01:40:18.079 claims that the cruise line, or I guess a relaxing 01:40:18.079 --> 01:40:20.600 cruise, is responsible for a data breach that 01:40:20.600 --> 01:40:22.239 compromised the person -identifiable information 01:40:22.239 --> 01:40:25.840 of the cruise goers. Now, the plaintiff is Danielle 01:40:25.840 --> 01:40:29.569 Seberg. interesting name, claims that Margaritaville 01:40:29.569 --> 01:40:32.390 at Sea occurred after the cruise line failed 01:40:32.390 --> 01:40:34.829 to properly secure and safeguard, and Seaberg 01:40:34.829 --> 01:40:37.369 wants to represent a nationwide class. So if 01:40:37.369 --> 01:40:39.890 you have ever traveled on the Margaritaville 01:40:39.890 --> 01:40:43.229 at Sea, which I'm guessing is a rather sloppy 01:40:43.229 --> 01:40:46.729 drunk boat, go knock yourself out. Moving on. 01:40:47.629 --> 01:40:50.750 petco yes petco where a lot of us buy our dog 01:40:50.750 --> 01:40:53.569 food and cat food and pet food and all that kind 01:40:53.569 --> 01:40:56.850 of stuff a new class action lawsuit alleges petco 01:40:56.850 --> 01:40:59.489 failed to properly secure their customers data 01:40:59.489 --> 01:41:03.069 so plaintiff matthew max claims that petco failed 01:41:03.069 --> 01:41:05.149 to properly secure and safeguard person identifiable 01:41:05.149 --> 01:41:07.590 information social security numbers so clearly 01:41:07.590 --> 01:41:11.109 an employee etc etc and so mac is arguing that 01:41:11.109 --> 01:41:13.449 petco knew or should have known and failed to 01:41:13.449 --> 01:41:17.270 basically secure all of this and so those We're 01:41:17.270 --> 01:41:21.010 just the lawsuits and payouts for this week. 01:41:21.109 --> 01:41:22.789 It's the longest I've ever done. We're almost 01:41:22.789 --> 01:41:26.840 10 minutes into this, and here we are. If any 01:41:26.840 --> 01:41:28.539 of them had just spent money on cybersecurity, 01:41:28.779 --> 01:41:30.600 they wouldn't be paying out. They wouldn't be 01:41:30.600 --> 01:41:32.260 getting sued. They wouldn't be losing their reputation. 01:41:32.460 --> 01:41:35.100 And I would not have been blathering on for almost 01:41:35.100 --> 01:41:37.779 10 minutes about them. And with that, let's move 01:41:37.779 --> 01:41:40.579 on to the actual data breaches or updates therein. 01:41:40.640 --> 01:41:42.920 And let's head to the Great White North and talk 01:41:42.920 --> 01:41:45.359 about the Canadian Investment Regulatory Organization, 01:41:45.739 --> 01:41:49.140 or CIRO. I actually did a finally on them months 01:41:49.140 --> 01:41:53.039 ago, basically due to this data breach. They 01:41:53.039 --> 01:41:56.300 just confirmed that they suffered that data breach, 01:41:56.439 --> 01:42:00.340 basically, and it is impacting 750 ,000 Canadian 01:42:00.340 --> 01:42:03.220 investors. So they disclosed the incident on 01:42:03.220 --> 01:42:05.479 August 18th, which is when I basically went to 01:42:05.479 --> 01:42:07.800 town on them, but they completed their forensic 01:42:07.800 --> 01:42:10.779 investigation this year on January 14th. CIO 01:42:10.779 --> 01:42:13.000 emphasized that login credentials or account 01:42:13.000 --> 01:42:15.819 security questions have not been affected, but 01:42:15.819 --> 01:42:18.159 because it does not store that kind of information, 01:42:18.380 --> 01:42:21.539 they also claim that they spent over 9 ,000 hours 01:42:21.539 --> 01:42:24.119 investigating. this and they say that no data 01:42:24.119 --> 01:42:26.520 that they can find has shown up in the dark web 01:42:26.520 --> 01:42:29.300 yet so we'll see what happens but to be fair 01:42:29.300 --> 01:42:30.760 governments are always behind the eight ball 01:42:30.760 --> 01:42:33.140 they're massive surface areas for attack you 01:42:33.140 --> 01:42:35.500 know whether it's federal provincial slash state 01:42:35.500 --> 01:42:38.640 or local government it's always a problem but 01:42:38.640 --> 01:42:41.300 ciro you could have been quicker on the draw 01:42:41.300 --> 01:42:43.460 on that one at least declaring and continuing 01:42:43.460 --> 01:42:47.500 the investigation moving on Let's talk about 01:42:47.500 --> 01:42:50.699 broadband and telecommunication company BrightSpeed. 01:42:50.699 --> 01:42:52.880 This is coming out of Charlotte, North Carolina. 01:42:53.100 --> 01:42:55.960 They're investigating multiple reports that their 01:42:55.960 --> 01:42:58.739 customers are a victim of a data breach by extortionists. 01:42:58.920 --> 01:43:01.319 Now, the extortion claims to be involving over 01:43:01.319 --> 01:43:05.520 1 million BrightSpeed customers. Basically, this 01:43:05.520 --> 01:43:08.359 group was called Crimson Collective. It's the 01:43:08.359 --> 01:43:09.880 one that's making these attempts. I can't even 01:43:09.880 --> 01:43:13.060 read my own notes. And basically, multiple sites 01:43:13.060 --> 01:43:16.960 are talking about this as well. posted a message 01:43:16.960 --> 01:43:19.500 on their Telegram channel in early January about 01:43:19.500 --> 01:43:21.680 the data theft. They said they are looking into 01:43:21.680 --> 01:43:24.539 these reports. Moving on. Oregon's Department 01:43:24.539 --> 01:43:27.479 of Environmental Quality. About 4 ,800 members 01:43:27.479 --> 01:43:29.800 of the public had their personal information 01:43:29.800 --> 01:43:32.340 exposed in a cyber attack, according to that 01:43:32.340 --> 01:43:34.880 department. But nine months later, they have 01:43:34.880 --> 01:43:38.060 yet to publicly disclose the leak. The DEQ appears 01:43:38.060 --> 01:43:40.640 to have known about this leak since June, but 01:43:40.640 --> 01:43:42.760 they haven't said anything. So obviously news 01:43:42.760 --> 01:43:45.279 reports are going on, which means Department 01:43:45.279 --> 01:43:48.020 of Environmental Quality in Oregon, I'm going 01:43:48.020 --> 01:43:50.659 to be talking about you in my mini segment when 01:43:50.659 --> 01:43:54.489 you get sued. Not a good sign. Moving on. J .P. 01:43:54.510 --> 01:43:58.470 Morgan, yes, the massive financial platform and 01:43:58.470 --> 01:44:01.130 company and system and everything else here in 01:44:01.130 --> 01:44:04.210 the United States. They basically sent a notification 01:44:04.210 --> 01:44:07.189 to Maine basically on Tuesday, this past Tuesday, 01:44:07.329 --> 01:44:09.350 revealing that investors in a private equity 01:44:09.350 --> 01:44:12.109 fund have been impacted, linked to an incident 01:44:12.109 --> 01:44:15.409 on a law firm, a .k .a. supply chain. And that 01:44:15.409 --> 01:44:19.600 law firm is. freed frank harris shriver and jacobson 01:44:19.600 --> 01:44:22.819 llp the notification letter revealed an unauthorized 01:44:22.819 --> 01:44:25.500 third party copied files from let's just say 01:44:25.500 --> 01:44:28.159 fried frank and their shared network drive some 01:44:28.159 --> 01:44:30.260 of those files contain the personal information 01:44:30.260 --> 01:44:33.340 about those who've invested in jp morgan's fund 01:44:33.340 --> 01:44:35.760 and we're talking names contact information social 01:44:35.760 --> 01:44:38.239 security and passport or other government ids 01:44:38.239 --> 01:44:39.640 remember when we're talking financial institution 01:44:39.640 --> 01:44:41.880 you're giving them all of your personal data 01:44:41.880 --> 01:44:44.359 to verify your identity and interestingly enough 01:44:44.359 --> 01:44:47.399 goldman or goldman sachs is in the same boat 01:44:47.399 --> 01:44:52.079 thanks to fried frank harris shriver and jacobson 01:44:52.079 --> 01:44:55.260 llp so let's see if any other major banks decide 01:44:55.260 --> 01:44:59.319 to completely declare moving on central maine 01:44:59.319 --> 01:45:03.340 health care they impact about 145 000 more patients 01:45:03.340 --> 01:45:05.920 than the eight that they originally reported 01:45:05.920 --> 01:45:09.039 according to officials this past monday The health 01:45:09.039 --> 01:45:11.800 system, which owns Central Maine Medical Center 01:45:11.800 --> 01:45:14.779 in Lewiston, as well as hospitals in Bridgeton 01:45:14.779 --> 01:45:17.720 and Rumford and several other health care facilities, 01:45:17.819 --> 01:45:21.640 reported to their own attorney general last summer 01:45:21.640 --> 01:45:24.119 that the cyber attack between March and June 01:45:24.119 --> 01:45:26.800 had impacted only eight patients. That's a heck 01:45:26.800 --> 01:45:29.279 of a jump, Central Maine Health Care. I mean, 01:45:29.300 --> 01:45:31.659 we always see numbers revised up. You know, Dropbox 01:45:31.659 --> 01:45:33.979 was notorious on this one back in the day. Oh, 01:45:34.020 --> 01:45:35.560 it was 7 million. And then three years later, 01:45:35.640 --> 01:45:37.989 oh, by the way, it was 70 million. Tech is. zero 01:45:37.989 --> 01:45:41.310 onto that but from eight to 145 000 come on dude 01:45:41.310 --> 01:45:44.819 moving on Let's head on over to Europe and talk 01:45:44.819 --> 01:45:48.079 about the travel company, Eurail. Now, the incident, 01:45:48.140 --> 01:45:50.560 according to the company, impacted all customers 01:45:50.560 --> 01:45:54.140 who were issued a Eurail pass, as well as those 01:45:54.140 --> 01:45:56.340 that made a seat reservation with the company. 01:45:56.500 --> 01:45:58.500 The rail pass provider does not have an exact 01:45:58.500 --> 01:46:01.479 number of impacted individuals, but an investigation 01:46:01.479 --> 01:46:05.399 basically with the EU's European Commission and 01:46:05.399 --> 01:46:08.479 Discover EU said that basically that program, 01:46:08.640 --> 01:46:10.640 the Discover EU program was impacted as well. 01:46:10.760 --> 01:46:12.979 The compromised information includes. identity 01:46:12.979 --> 01:46:16.039 and contact information as well as passport info 01:46:16.039 --> 01:46:19.220 as well so if you've ever rode the rails in europe 01:46:19.220 --> 01:46:22.979 and used your rail for your ticketing needs you 01:46:22.979 --> 01:46:26.310 definitely want to check in moving on Let's talk 01:46:26.310 --> 01:46:29.550 about the robo advisor known as Betterment. They 01:46:29.550 --> 01:46:31.550 disclosed a cybersecurity incident after a threat 01:46:31.550 --> 01:46:34.350 actor used social engineering to breach their 01:46:34.350 --> 01:46:37.130 systems. This involved third party software platforms 01:46:37.130 --> 01:46:39.069 that the company uses for marketing and operations, 01:46:39.270 --> 01:46:41.850 but was not the result of Betterment's infrastructure 01:46:41.850 --> 01:46:45.109 being hit, according to the advisor. So the threat 01:46:45.109 --> 01:46:48.130 actor on January 9th set a crypto related message 01:46:48.130 --> 01:46:50.510 to certain Betterment customers. impersonating 01:46:50.510 --> 01:46:52.750 the company to trick users into sending them 01:46:52.750 --> 01:46:55.090 funds the fraudulent message claimed that betterment 01:46:55.090 --> 01:46:58.350 would triple fresh deposits made to bitcoin and 01:46:58.350 --> 01:47:01.470 ethereum cryptocurrency basically and those addresses 01:47:01.470 --> 01:47:03.609 were controlled by the attacker where you should 01:47:03.609 --> 01:47:05.649 send the money and yeah if you're ever seeing 01:47:05.649 --> 01:47:08.210 something from your financial institution quote 01:47:08.210 --> 01:47:10.409 unquote that says we're going to triple your 01:47:10.409 --> 01:47:12.270 money for this limited time offer you've got 01:47:12.270 --> 01:47:14.189 a two -hour window it's a giveaway or whatever 01:47:14.189 --> 01:47:16.890 yeah dude that's always fake there it's like 01:47:16.890 --> 01:47:21.229 that never happens moving on university of georgia 01:47:21.229 --> 01:47:23.550 specifically the police department so the uga 01:47:23.550 --> 01:47:27.090 pd they received a phone call this is interesting 01:47:27.090 --> 01:47:29.529 concerning a potential data breach resulting 01:47:29.529 --> 01:47:33.270 in a uga student having multiple credit cards 01:47:33.270 --> 01:47:36.329 being fraudulently opened in her name so we're 01:47:36.329 --> 01:47:39.069 talking about one person here still worthy for 01:47:39.069 --> 01:47:41.819 breaches of the week now this student And her 01:47:41.819 --> 01:47:44.520 parent believed that the fraud was caused by 01:47:44.520 --> 01:47:48.279 a potential UGA breach because the emails were 01:47:48.279 --> 01:47:51.300 sent to the UGA email address of the student 01:47:51.300 --> 01:47:54.539 and the cards were sent to the home address associated 01:47:54.539 --> 01:47:56.920 with her student account. They also reported 01:47:56.920 --> 01:47:59.760 reading about familiar incidents on social media's 01:47:59.760 --> 01:48:03.859 website, Reddit. So that is interesting in the 01:48:03.859 --> 01:48:06.640 sense that. If you were looking at this forensically, 01:48:06.720 --> 01:48:09.359 if you have a unique email address with, let's 01:48:09.359 --> 01:48:11.359 say, the home address, which you're probably 01:48:11.359 --> 01:48:14.659 using everywhere as a student, I don't necessarily 01:48:14.659 --> 01:48:16.859 know if that's enough to say that UGA has been 01:48:16.859 --> 01:48:19.800 breached. But nevertheless, if they're tracing 01:48:19.800 --> 01:48:22.180 it back, maybe those two combinations have never 01:48:22.180 --> 01:48:24.840 been used anywhere else, at least that they can 01:48:24.840 --> 01:48:27.359 remember. So I'll keep you up to date on this 01:48:27.359 --> 01:48:29.439 one because we might see a lot more coming out 01:48:29.439 --> 01:48:33.000 of the UGA. I'll let you know. Moving on. Another 01:48:33.000 --> 01:48:35.939 university, Monroe University. They reported 01:48:35.939 --> 01:48:38.899 to Maine basically a data breach involving 320 01:48:38.899 --> 01:48:43.399 ,973 people. Now, in a post to their website, 01:48:43.640 --> 01:48:46.319 Monroe University disclosed an unauthorized third 01:48:46.319 --> 01:48:48.779 party access computer systems between December 01:48:48.779 --> 01:48:52.239 9th through the 23rd of 2024. So over a year 01:48:52.239 --> 01:48:55.680 ago. Now, a review of the affected files. Concluded 01:48:55.680 --> 01:48:58.640 on September 30th of last year and sensitive 01:48:58.640 --> 01:49:00.859 personal information was confirmed. Dates of 01:49:00.859 --> 01:49:02.960 birth, obviously name, social security number, 01:49:03.079 --> 01:49:05.319 driver's license, government issued IDs, passports, 01:49:05.399 --> 01:49:07.560 medical and health insurance information, email 01:49:07.560 --> 01:49:10.119 usernames and passwords. That's awesome. Financial 01:49:10.119 --> 01:49:13.909 account details and certain student data. If 01:49:13.909 --> 01:49:15.390 you have anything to do with Monroe University, 01:49:15.630 --> 01:49:18.529 go change your passwords like yesterday and be 01:49:18.529 --> 01:49:20.869 prepared to join a class action sooner than later. 01:49:21.010 --> 01:49:24.689 Moving on, at least five Belgian hospitals, I 01:49:24.689 --> 01:49:27.310 do not know where in Belgium they are, they've 01:49:27.310 --> 01:49:30.050 been victims of a data breach at a supplier of 01:49:30.050 --> 01:49:32.949 patient registration software. A total of 71 01:49:32.949 --> 01:49:36.390 ,000 personal and login details of patients were 01:49:36.390 --> 01:49:39.289 found on the dark web. That's not all. A second 01:49:39.289 --> 01:49:43.119 breach at an IT supplier. basically added another 01:49:43.119 --> 01:49:47.159 1 ,000 login details of commercial and government 01:49:47.159 --> 01:49:49.260 organizations. I don't know the name of these 01:49:49.260 --> 01:49:51.520 hospitals in Belgium, but heads up to you. If 01:49:51.520 --> 01:49:54.100 you live there or you used one of those or have 01:49:54.100 --> 01:49:56.060 used one of those while traveling there, you 01:49:56.060 --> 01:49:59.479 might want to check in. Moving on. union home 01:49:59.479 --> 01:50:02.800 mortgage they just said that they paid ransom 01:50:02.800 --> 01:50:05.779 in their data breach case i don't know more than 01:50:05.779 --> 01:50:07.579 that it was behind a paywall and i'm not going 01:50:07.579 --> 01:50:10.260 to pay some random site for this but heads up 01:50:10.260 --> 01:50:14.000 union home mortgage uh members you might want 01:50:14.000 --> 01:50:18.500 to check in moving on trizetto provider solutions 01:50:18.500 --> 01:50:21.000 now this is interesting because i came to this 01:50:21.439 --> 01:50:23.939 from two separate data breaches that basically 01:50:23.939 --> 01:50:26.800 were for healthcare providers that said, well, 01:50:26.819 --> 01:50:29.260 we didn't get hit, TriZetto got hit, but I have 01:50:29.260 --> 01:50:32.239 yet to find something just on TriZetto. But the 01:50:32.239 --> 01:50:34.159 two that are declaring data breaches that I can 01:50:34.159 --> 01:50:36.680 find thus far are San Francisco Community Health 01:50:36.680 --> 01:50:39.079 Center, and we're talking name, social security 01:50:39.079 --> 01:50:41.220 number, address, date of birth, health insurance 01:50:41.220 --> 01:50:43.479 information like member number, insurer name, 01:50:43.640 --> 01:50:47.029 provider name. primary insured and dependent, 01:50:47.329 --> 01:50:51.029 and then also an outfitter hospital called Variety 01:50:51.029 --> 01:50:53.229 Care. Same thing, name, social security number, 01:50:53.350 --> 01:50:55.250 address, date of birth, health insurance, medical 01:50:55.250 --> 01:50:58.189 information, provider names, and then other demographic 01:50:58.189 --> 01:51:00.609 information as well. So if you have anything 01:51:00.609 --> 01:51:02.869 to do with San Francisco Community Health Center 01:51:02.869 --> 01:51:05.970 or Variety Care, you might want to check in. 01:51:06.090 --> 01:51:08.729 Their mutual provider has been hit, and I have 01:51:08.729 --> 01:51:10.289 a feeling I'm going to be talking about them 01:51:10.289 --> 01:51:13.739 more. Moving on. member close this is a financial 01:51:13.739 --> 01:51:17.100 service company based in taxachusetts they confirm 01:51:17.100 --> 01:51:19.220 that sensitive personal information may have 01:51:19.220 --> 01:51:21.560 been accessed by an unauthorized third party 01:51:21.560 --> 01:51:25.180 on october 29th of last year name social security 01:51:25.180 --> 01:51:27.260 number date of birth caught up in that don't 01:51:27.260 --> 01:51:29.159 know much more than that but heads up member 01:51:29.159 --> 01:51:32.659 close uh patient or patients members their financial 01:51:32.659 --> 01:51:36.319 services outfit and finally our last finally 01:51:36.319 --> 01:51:39.619 today is on ai agents that's right artificial 01:51:39.619 --> 01:51:42.270 intelligence agents that might be in our life. 01:51:42.329 --> 01:51:45.289 Think Microsoft Copilot, ChatGPT, and on and 01:51:45.289 --> 01:51:47.470 on. And now this is beyond interesting. And on 01:51:47.470 --> 01:51:50.409 last week's breaches of the week, my finally 01:51:50.409 --> 01:51:52.989 referenced experience data breach industry forecast. 01:51:53.329 --> 01:51:55.909 This is the other side of it, excuse me, that 01:51:55.909 --> 01:51:58.170 I did not mention last week. And quite frankly, 01:51:58.760 --> 01:52:00.920 I think this is interesting because Michael Brumer, 01:52:01.020 --> 01:52:03.420 Vice President of Global Data Breach Resolution, 01:52:03.420 --> 01:52:05.939 and Jim Stephen, Head of Crisis and Data Response 01:52:05.939 --> 01:52:10.159 Services UK, said that agentic AI systems, meaning 01:52:10.159 --> 01:52:13.470 those agent AIs we use, could be exploited by 01:52:13.470 --> 01:52:17.090 savvy attackers who might inject their AI agents 01:52:17.090 --> 01:52:20.430 to, quote, disrupt the orchestration or governance 01:52:20.430 --> 01:52:23.670 of the victim's AI agents. Quote, at a minimum, 01:52:23.789 --> 01:52:26.369 this disruption could impact an organization's 01:52:26.369 --> 01:52:29.369 operations or siphon money, goods, or information. 01:52:29.609 --> 01:52:32.609 Or it could perform things like ransomware. Quote, 01:52:32.609 --> 01:52:36.039 AI agents... are the next frontier for fraud 01:52:36.039 --> 01:52:38.739 and cybercrime, and we predict this may overtake 01:52:38.739 --> 01:52:41.920 human error as the leading cause of data breaches, 01:52:41.960 --> 01:52:44.279 end quote. Right now, it's us making mistakes, 01:52:44.460 --> 01:52:46.600 us thinking the link is real, us thinking Prince 01:52:46.600 --> 01:52:49.100 Nbuntu from Nigeria needs help with his revolution. 01:52:49.579 --> 01:52:53.319 Next up, the AI. And because AI is being leveraged, 01:52:53.319 --> 01:52:55.340 not just as personal assistance, but everywhere 01:52:55.340 --> 01:52:59.100 in organizations, cracking those... could potentially 01:52:59.100 --> 01:53:03.420 do an absolute ton of damage. And with the use 01:53:03.420 --> 01:53:05.600 of AI, attackers might also be able to extract 01:53:05.600 --> 01:53:09.619 data at an unprecedented rate and, quote, stitch 01:53:09.619 --> 01:53:12.279 together enriched identity profiles. So imagine 01:53:12.279 --> 01:53:14.239 getting a little bit of information on you here 01:53:14.239 --> 01:53:16.859 and a little bit more on you from over there 01:53:16.859 --> 01:53:18.920 and on and on and on, and then putting it all 01:53:18.920 --> 01:53:21.039 together and aggregating it to get a complete 01:53:21.039 --> 01:53:24.380 picture of you due to multiple breaches. AI is 01:53:24.380 --> 01:53:28.189 very good. basically aggregation and correlation. 01:53:28.670 --> 01:53:31.649 So here we go. Experian also warned, and I quote, 01:53:31.789 --> 01:53:35.029 get ready for a potentially massive spike in 01:53:35.029 --> 01:53:38.850 identity theft, end quote. Or also AI capabilities 01:53:38.850 --> 01:53:41.170 could bolster the spread of mutating malicious 01:53:41.170 --> 01:53:44.010 code, such as malware, like polymorphic malware, 01:53:44.229 --> 01:53:47.029 metamorphic malware. This is a huge problem. 01:53:47.930 --> 01:53:50.909 And I think we are walking into with AI agents. 01:53:50.970 --> 01:53:52.970 Imagine if I can poison it to steal your information 01:53:52.970 --> 01:53:55.750 or disrupt you or infect you and all of that. 01:53:55.789 --> 01:53:57.869 That's what we are talking about here. And I 01:53:57.869 --> 01:53:59.729 think that's something that we basically have 01:53:59.729 --> 01:54:01.829 to put good controls on over. In the same way 01:54:01.829 --> 01:54:04.770 that when you are asking a chat GPT, a copilot, 01:54:04.810 --> 01:54:06.470 whatever, for an answer, and it's giving you 01:54:06.470 --> 01:54:09.050 an answer, you need to double check that. These 01:54:09.050 --> 01:54:10.909 things can hallucinate. I've literally written 01:54:10.909 --> 01:54:13.430 articles for Forbes and others on this, you know, 01:54:13.430 --> 01:54:16.310 as well as just straight up lie to you. So we 01:54:16.310 --> 01:54:20.300 are walking. into a potentially very dangerous 01:54:20.300 --> 01:54:22.439 time in artificial intelligence not to mention 01:54:22.439 --> 01:54:24.500 the fact that it's boosting prices for things 01:54:24.500 --> 01:54:27.039 like memory and you know hard drive space graphics 01:54:27.039 --> 01:54:29.180 cards and all of that because the ai data centers 01:54:29.180 --> 01:54:31.279 of the world are gobbling up all of the supply 01:54:31.279 --> 01:54:33.439 and us little folk you know that are just trying 01:54:33.439 --> 01:54:35.819 to buy computers you know are having to pay a 01:54:35.819 --> 01:54:39.880 heck of a lot more for it so oh AI, I think, 01:54:39.880 --> 01:54:41.800 has so many interesting things coming out, but 01:54:41.800 --> 01:54:44.359 it also has so many things we need to be concerned 01:54:44.359 --> 01:54:47.600 about. And agentic AI and the poisoning of agentic 01:54:47.600 --> 01:54:51.119 AI is one of those things. And so that, I think, 01:54:51.140 --> 01:54:53.439 and I predict for myself, means I'm going to 01:54:53.439 --> 01:54:55.840 be spending a lot more time on Breaches of the 01:54:55.840 --> 01:54:58.760 Week talking about agentic AI breaches as well 01:54:58.760 --> 01:55:02.319 as just human breaches. And here we are. Best 01:55:02.319 --> 01:55:04.560 of luck. And please like, share, follow me here 01:55:04.560 --> 01:55:07.020 on Facebook and Twitter at Nick AESP. And please 01:55:07.020 --> 01:55:08.600 feel free to subscribe to me at YouTube as well. 01:55:08.699 --> 01:55:11.279 And as always, stay safe, stay online, and please, 01:55:11.380 --> 01:55:13.039 please, please, I don't want to say private, 01:55:13.159 --> 01:55:33.479 informed, and secure. Take care. Welcome back 01:55:33.479 --> 01:55:42.859 to TSB. This is program 267. I've got the boy 01:55:42.859 --> 01:55:51.739 of pressed, the boy of ring, and a jack boy. 01:55:55.779 --> 01:56:00.960 The jack of neck. The jack of neck. The jack 01:56:00.960 --> 01:56:07.279 of all trends. The Jack of all trades? I guess. 01:56:09.720 --> 01:56:16.680 Before we get into our main topic, I do have 01:56:16.680 --> 01:56:25.119 a Kim Commando newsletter water cooler from January 01:56:25.119 --> 01:56:30.909 25th, 2025. And this will probably be the last 01:56:30.909 --> 01:56:33.930 one we ever do because, as I said, I love her 01:56:33.930 --> 01:56:38.510 newsletter, but Kim just is becoming a problem. 01:56:38.710 --> 01:56:42.869 Not professional. Well, I'm going to continue 01:56:42.869 --> 01:56:45.770 to listen to her minutes and things, but the 01:56:45.770 --> 01:56:48.170 newsletter is becoming too hard to deal with. 01:56:48.789 --> 01:56:53.479 Maybe I'll drop a note. I mean, if it asks me 01:56:53.479 --> 01:56:56.000 for comments, I'm going to say yes. The newsletter 01:56:56.000 --> 01:56:59.539 is not accessible. It's got emojis all over the 01:56:59.539 --> 01:57:03.699 place and hard to deal with. Accessibly, you've 01:57:03.699 --> 01:57:06.359 got headings in the right place, but you've got 01:57:06.359 --> 01:57:13.000 images that are unlabeled, and the emoji aspect 01:57:13.000 --> 01:57:16.960 is unprofessional. If this changes, then I'm 01:57:16.960 --> 01:57:22.840 willing to come back. Yeah, yeah. No, I 100 % 01:57:22.840 --> 01:57:33.239 agree. So, let's read this because this is actually 01:57:33.239 --> 01:57:42.199 recent news in regards to a program that we've 01:57:42.199 --> 01:57:54.130 talked about quite regularly here on... TSB. 01:57:54.130 --> 01:58:00.390 Can anybody tell me what program that is before 01:58:00.390 --> 01:58:12.329 I read? Office. I didn't catch that, Terrence. 01:58:13.130 --> 01:58:22.640 Office. Microsoft. Not Office. No. I read it 01:58:22.640 --> 01:58:30.239 on Saturday. This is the same one I read on Saturday. 01:58:34.359 --> 01:58:46.819 It is a program that we have told people not 01:58:46.819 --> 01:58:55.010 to run. It is a program that is known to have... 01:58:55.010 --> 01:59:01.130 Oh, yeah. Windows... Windows Defender Decrapper? 01:59:02.149 --> 01:59:05.189 Nope, not Decrapper. Decrapper is better to run 01:59:05.189 --> 01:59:07.470 than nothing. Decrapper is better to run than 01:59:07.470 --> 01:59:12.710 nothing. Right. And turn that down a little bit. 01:59:12.729 --> 01:59:16.409 We got a little bit of feedback. Oh, let me see. 01:59:16.489 --> 01:59:21.029 Oh, sorry. I'll have to do it later. Okay. All 01:59:21.029 --> 01:59:27.939 right. I'm not yelling at you. I'm just telling 01:59:27.939 --> 01:59:33.899 you to turn that down. No, not you. It was Preston, 01:59:33.899 --> 01:59:37.880 I think. It was me. Oh, it was Preston. I didn't 01:59:37.880 --> 01:59:40.420 know who it was. That's why I just stopped doing 01:59:40.420 --> 01:59:43.779 what I was doing. No, you're fine. I don't hear 01:59:43.779 --> 01:59:48.699 anything from you. I was deleting email. No, 01:59:48.760 --> 01:59:53.090 you weren't the issue. But we're fine now. This 01:59:53.090 --> 01:59:57.670 is a program we talked about when it came to 01:59:57.670 --> 02:00:08.569 challenges. Yeah, tick, tick, tock. Tick, tock, 02:00:08.609 --> 02:00:12.409 bite is correct. The beacon of that, there is 02:00:12.409 --> 02:00:14.770 a new challenge I heard, but I didn't get to 02:00:14.770 --> 02:00:19.909 hear it. Oh, geez. It's probably, I hate to tell 02:00:19.909 --> 02:00:22.380 you this, Terry. You're probably better off. 02:00:22.760 --> 02:00:25.119 No, well, I'm not saying I'm not better off. 02:00:25.199 --> 02:00:27.800 Yeah, I heard about a new pair, but I didn't 02:00:27.800 --> 02:00:30.760 hear what it was. And I'm kind of glad I didn't. 02:00:32.039 --> 02:00:34.060 I probably would have been ranting about it on 02:00:34.060 --> 02:00:49.829 throwback on Saturday. Yeah, right. three different 02:00:49.829 --> 02:00:52.649 companies and two of them I've never heard of. 02:00:53.890 --> 02:00:56.689 I don't know why Oracle would be interested in 02:00:56.689 --> 02:01:00.550 them, but okay, whatever. But Oracle was in the 02:01:00.550 --> 02:01:03.970 running when we covered that when it leaked. 02:01:04.850 --> 02:01:12.109 Right, they were. You know, I'm hoping that you 02:01:12.109 --> 02:01:17.409 know, maybe they get their shit together. That's 02:01:17.409 --> 02:01:20.529 what I'm hoping for. I'm hoping for that. I really 02:01:20.529 --> 02:01:23.550 am. And I really hope that they get their craft 02:01:23.550 --> 02:01:29.289 together and they are decent. And within the 02:01:29.289 --> 02:01:33.090 next six months, the challenges will be the thing 02:01:33.090 --> 02:01:38.470 of the past. I'm hoping so. Yep. But I'm not 02:01:38.470 --> 02:01:43.489 going to hold my breath. Nope. I'm very skeptical. 02:01:44.390 --> 02:01:49.229 Very skeptical. Because I heard of another challenge, 02:01:49.270 --> 02:01:52.090 but I didn't hear what the challenge was because 02:01:52.090 --> 02:01:56.090 I kind of changed the channel. Can somebody ask 02:01:56.090 --> 02:02:03.310 a tool of choice if there are any new TikTok 02:02:03.310 --> 02:02:10.770 challenges within the last month and report back? 02:02:13.470 --> 02:02:23.220 Yeah. Yeah. here. While we do that, I'll read 02:02:23.220 --> 02:02:29.579 if I can stop coughing, I'll read what this is. 02:02:30.340 --> 02:02:33.060 And Nick, you have a copy of this in your folder. 02:02:33.479 --> 02:02:37.279 Unfortunately, it's only a 40. It's not a 30. 02:02:39.260 --> 02:02:45.439 What's the newest TikTok challenge? It says... 02:02:45.770 --> 02:02:48.170 Get a load of the following from the water cooler 02:02:48.170 --> 02:02:54.109 from January 25th, 2026. Be alert. Be aware. 02:02:57.130 --> 02:03:03.689 What is the newest TikTok challenge? It says... 02:03:03.689 --> 02:03:10.010 TikTok... By the way, we'll spell it for you 02:03:10.010 --> 02:03:11.949 guys to make sure that you know how it's spelled. 02:03:12.090 --> 02:03:16.420 T -I -K -T -O -K... The Ts are capitalized one 02:03:16.420 --> 02:03:19.619 word. No, are there any dangerous ones that are 02:03:19.619 --> 02:03:27.640 new? They just forced everyone to click agree, 02:03:27.939 --> 02:03:32.600 and that's in quotes, on a new privacy policy. 02:03:35.899 --> 02:03:42.420 Now that the US owns a part of the app, people 02:03:42.420 --> 02:03:49.470 are in a panic. Why? The app can collect your 02:03:49.470 --> 02:03:55.630 immigration status, sexual orientation, and precise 02:03:55.630 --> 02:04:04.689 GPS location. Oh, Jared, I did find the new challenge. 02:04:04.729 --> 02:04:08.869 Are you ready for it? I was waiting for a comment 02:04:08.869 --> 02:04:13.460 from Mr. J over there, but yes, go ahead. Microwaving 02:04:13.460 --> 02:04:22.880 toys. What the hell? Which has consisted in various 02:04:22.880 --> 02:04:31.359 people getting burned instead. No shit! Microwaving 02:04:31.359 --> 02:04:36.399 toys, Nick. Okay, how many brain cells do you 02:04:36.399 --> 02:04:39.420 have to have to realize that's a really stupid 02:04:39.420 --> 02:04:44.850 and idiotic thing to do? I knew that was coming. 02:04:45.270 --> 02:04:49.050 I'm just gonna agree with you because I know 02:04:49.050 --> 02:04:53.050 that that's definitely true. So what does it 02:04:53.050 --> 02:04:55.810 say? Read it before I finish reading this. I 02:04:55.810 --> 02:04:58.310 basically said that they put the toy in the microwave 02:04:58.310 --> 02:05:03.770 and zap it for a few minutes and it ends up burning 02:05:03.770 --> 02:05:08.909 you when you take it out because it is hot. Because 02:05:08.909 --> 02:05:12.340 it's hot as fuck. Why would you microwave a toy? 02:05:13.640 --> 02:05:16.119 Yeah, it's hot as fuck. I mean, if you did it 02:05:16.119 --> 02:05:21.100 by accident, that's one thing. But even by accident, 02:05:21.579 --> 02:05:26.260 like you. But what I'm saying is like, OK, you 02:05:26.260 --> 02:05:30.920 go to put a coffee cup. You don't realize that, 02:05:30.920 --> 02:05:34.979 you know, your toddler put the monster in the 02:05:34.979 --> 02:05:42.399 microwave. And you heat up your coffee. Well, 02:05:42.560 --> 02:05:45.319 you don't because the microwave's basically dead 02:05:45.319 --> 02:05:48.140 because there's plastic in there and it doesn't... 02:05:48.140 --> 02:05:51.020 And it's melted in the microwave because of the 02:05:51.020 --> 02:05:54.539 toy and it's probably melted. And then the next 02:05:54.539 --> 02:05:56.739 thing you know, that could cause a house fire. 02:05:56.920 --> 02:06:02.579 So, God knows. Oh, well. I asked it, I said, 02:06:02.680 --> 02:06:06.100 are there any dangerous trends on TikTok lately? 02:06:06.300 --> 02:06:11.500 And it said, microwaving toys is on the rise. 02:06:11.779 --> 02:06:14.699 But Nick, I paused mainly because of the first 02:06:14.699 --> 02:06:19.460 sentence of what this TikTok people are collecting. 02:06:19.579 --> 02:06:22.560 And I'll reread it again. Immigration status, 02:06:22.899 --> 02:06:26.840 sexual orientation, and precise GPS location. 02:06:29.559 --> 02:06:32.779 Well, given that they were doing that before, 02:06:33.039 --> 02:06:42.880 I'm sadly not surprised. Plot twist. Plot twist. 02:06:43.159 --> 02:06:47.659 Most of that's been in the policy since August 02:06:47.659 --> 02:06:50.619 2024. That goes back to what you just said, Nick. 02:06:51.659 --> 02:06:53.680 Yeah. Why the hell would they need your sexual 02:06:53.680 --> 02:06:55.840 orientation anyway? Who cares if you like... 02:06:55.840 --> 02:06:58.239 And how do they find out your sexual orientation 02:06:58.239 --> 02:07:01.720 unless you give it out anyway? Which is what 02:07:01.720 --> 02:07:04.020 a lot of people probably do. And you could lie 02:07:04.020 --> 02:07:06.119 and say you're straight even though you're... 02:07:06.119 --> 02:07:09.699 Just for an example, I could say I'm straight 02:07:09.699 --> 02:07:13.800 even though I'm not. I mean, I am truthfully 02:07:13.800 --> 02:07:17.079 straight, but I could say I'm gay even though 02:07:17.079 --> 02:07:20.600 I'm not. People could lie on that. Yeah, so that 02:07:20.600 --> 02:07:22.850 you're then... targeted with all kinds of different 02:07:22.850 --> 02:07:25.729 videos. That's really what it's about. Targeted 02:07:25.729 --> 02:07:33.130 with more crap. Yeah. Not to mention your girlfriend's 02:07:33.130 --> 02:07:37.010 reading your message. TikTok's reading your girlfriend's 02:07:37.010 --> 02:07:42.449 back and forth sexting messages. By default. 02:07:44.229 --> 02:07:49.869 By default. It says, you never read it. The actual 02:07:49.869 --> 02:07:56.250 new thing? Precise location tracking instead 02:07:56.250 --> 02:08:05.470 of approximate. That's not good. But, Kim writes, 02:08:05.789 --> 02:08:11.409 it's optional and off by default. So don't fall 02:08:11.409 --> 02:08:15.550 for the online hype. And you know damn well people 02:08:15.550 --> 02:08:19.100 are going to turn that on. Of course they will. 02:08:19.340 --> 02:08:29.960 What could possibly possibly go wrong? Go wrong. 02:08:33.159 --> 02:08:36.899 Oh, shoot. They can't get the DJ yet? Yes, they 02:08:36.899 --> 02:08:40.279 can come get the DJ now because the DJ just freaking 02:08:40.279 --> 02:08:44.979 posted his precise location on TikTok. Oops. 02:08:45.159 --> 02:08:50.720 Oops. I still have the 266 file. I can read from 02:08:50.720 --> 02:08:54.800 it. It's fine. Oops. Didn't update my own, but 02:08:54.800 --> 02:08:57.500 I updated everybody else. But the file hasn't 02:08:57.500 --> 02:09:00.159 changed except to fix some quoting things that 02:09:00.159 --> 02:09:02.560 I already know about and the page numbering. 02:09:02.560 --> 02:09:05.819 I haven't changed anything else. So it's still 02:09:05.819 --> 02:09:21.909 readable. So I'll read from mine. So, I call 02:09:21.909 --> 02:09:29.090 this AI and its uses. Yeah. Okay. So, I will 02:09:29.090 --> 02:09:31.390 start, and if anybody else would like to pick 02:09:31.390 --> 02:09:34.590 up and read a section and lead, you're welcome 02:09:34.590 --> 02:09:39.369 to do so. Please just let me know when we get 02:09:39.369 --> 02:09:45.010 to a break. I am on 267 .1 in your appropriate 02:09:45.010 --> 02:09:51.229 file. I'm fine with my 266 and I already know 02:09:51.229 --> 02:10:02.569 what's wrong. So, today, we're going to talk 02:10:02.569 --> 02:10:07.529 a little bit about AI and its usage. We'll make 02:10:07.529 --> 02:10:10.909 sure we take your questions. So, if anyone has 02:10:10.909 --> 02:10:14.720 any questions. You may contact us. There's plenty 02:10:14.720 --> 02:10:19.039 of opportunity for us to give out contact info. 02:10:20.260 --> 02:10:24.279 Yeah, there is. We have an outline to start with. 02:10:24.560 --> 02:10:30.880 And today's. What's that press for? I said I'm 02:10:30.880 --> 02:10:34.939 sure that this discussion won't end today. It's 02:10:34.939 --> 02:10:39.319 going to be ongoing. It will be ongoing. I know 02:10:39.319 --> 02:10:41.760 that much because there's a lot we can cover. 02:10:42.539 --> 02:10:50.560 Yeah. Oh, yes. We have an outline to start with. 02:10:51.020 --> 02:10:54.779 Then we can figure out if people want me to go 02:10:54.779 --> 02:10:59.840 any further. While the outline indicates that 02:10:59.840 --> 02:11:03.539 it is a 45 -minute program, we can allow longer 02:11:03.539 --> 02:11:07.140 if needed. And, of course, the audience can respond 02:11:07.140 --> 02:11:11.979 via podcast by emailing. iMessaging and or calling 02:11:11.979 --> 02:11:14.739 the comment line, which we'll give out throughout 02:11:14.739 --> 02:11:17.000 the program. And it was very insistent, by the 02:11:17.000 --> 02:11:21.079 way, in its iMessaging problem I had. It's lowercase 02:11:21.079 --> 02:11:30.479 i capital messaging by rule. This is not saying 02:11:30.479 --> 02:11:36.439 AI is bad. AI can be good. And I've personally 02:11:36.439 --> 02:11:42.779 found it's you. I've personally found good uses 02:11:42.779 --> 02:11:47.199 for it just recently in my life and even have 02:11:47.199 --> 02:11:54.960 an account on one. I used ChatGPT to assist in 02:11:54.960 --> 02:11:59.199 the write -up of the episode today, but I've 02:11:59.199 --> 02:12:03.699 turned it into my own write -up because I'm not 02:12:03.699 --> 02:12:35.619 well -versed in this subject. Let's start. Now... 02:12:38.849 --> 02:12:45.550 I will read item number one. Opening and ground 02:12:45.550 --> 02:12:49.970 rules. I'm not going to worry about the time, 02:12:50.029 --> 02:12:53.210 but we read the time during the security hour 02:12:53.210 --> 02:12:56.590 just so that people understood that we were trying 02:12:56.590 --> 02:13:00.350 to keep it time -based. But TSB allows for more 02:13:00.350 --> 02:13:02.989 than the allotted time, so I'm not going to read 02:13:02.989 --> 02:13:06.069 the time points. You don't need to either if 02:13:06.069 --> 02:13:12.010 you want to read. This is a practical conversation, 02:13:12.449 --> 02:13:18.909 not a debate. Panel speakers first establish 02:13:18.909 --> 02:13:24.649 context. We'll open with a panel discussion to 02:13:24.649 --> 02:13:30.170 set the stage. Then we'll open it up with comments 02:13:30.170 --> 02:13:36.449 so we can keep things focused and respectful. 02:13:37.479 --> 02:13:41.720 But we do know that people have supposedly misused 02:13:41.720 --> 02:13:46.939 things by uploading things they probably shouldn't, 02:13:46.939 --> 02:13:50.600 giving it too much about themselves, or other 02:13:50.600 --> 02:14:00.539 things we can discuss. Okay? Yep. So, we are 02:14:00.539 --> 02:14:08.779 not going to say not to use AI. We are not going 02:14:08.779 --> 02:14:14.340 to say to use AI. But I have a practical solution 02:14:14.340 --> 02:14:18.579 on why I needed AI and then realized how I can 02:14:18.579 --> 02:14:24.159 use it for everyday work. I was never late. Let's 02:14:24.159 --> 02:14:29.359 make that very clear. I've used tools like Be 02:14:29.359 --> 02:14:39.439 My AI, Aira AI, Seeing AI. And others. Your G's 02:14:39.439 --> 02:14:44.300 and A's are AI, although it's a different platform 02:14:44.300 --> 02:14:55.600 altogether. Yeah. Your iPhone has Siri. It also 02:14:55.600 --> 02:15:00.739 is AI and is a different animal altogether. What 02:15:00.739 --> 02:15:07.760 we're going to talk about will be... Apps like 02:15:07.760 --> 02:15:17.039 ChatGPT, Gemini, and Claude. We are not going 02:15:17.039 --> 02:15:29.279 to cover today the more open programs like the 02:15:29.279 --> 02:15:33.319 ones talked about that allow very interesting 02:15:36.299 --> 02:15:41.500 behaviors that can be a discussion we can talk 02:15:41.500 --> 02:15:45.880 about in later programs the names aren't important 02:15:45.880 --> 02:15:48.899 now they're escaping me at the moment but I bet 02:15:48.899 --> 02:15:53.319 I can go and ask you what was the name of these 02:15:53.319 --> 02:15:57.340 other apps but I'm not doing any of that today 02:15:57.340 --> 02:16:00.979 the point is that they're out there we know about 02:16:00.979 --> 02:16:06.779 them we've talked about them Today is going to 02:16:06.779 --> 02:16:10.060 be basic use. People can't discuss them. Right. 02:16:12.140 --> 02:16:18.640 What's that? Well, sorry. I'm getting my copy 02:16:18.640 --> 02:16:23.880 ready. But what I was going to say, today we're 02:16:23.880 --> 02:16:27.380 going to talk about the basic use and people 02:16:27.380 --> 02:16:32.059 can research on their own time and see what service 02:16:32.059 --> 02:16:34.879 they can utilize. And of course, if they have 02:16:34.879 --> 02:16:43.520 any more That's why we're here. What we mean 02:16:43.520 --> 02:16:51.819 by best practice. Item number two. AI is already 02:16:51.819 --> 02:16:57.959 embedded in tools people use daily. Best practice 02:16:57.959 --> 02:17:03.559 means intentional and accountable use. Again. 02:17:04.329 --> 02:17:10.370 Best practice means intentional and accountable 02:17:10.370 --> 02:17:16.209 use. The word accountability. Accountable, yep. 02:17:18.590 --> 02:17:22.190 Both Preston and Terry said accountable and accountability, 02:17:22.610 --> 02:17:31.979 yes. What about you, Mr. Ye over there? I didn't 02:17:31.979 --> 02:17:42.860 say anything because I simply agree. Okay. We 02:17:42.860 --> 02:17:49.959 should assume... I got you. We should assume... 02:17:49.959 --> 02:17:55.620 One. Human responsibility doesn't disappear. 02:17:59.920 --> 02:18:03.479 Agree or disagree? We can go one by one here. 02:18:03.879 --> 02:18:10.299 Agree. Yeah, I definitely agree. Yep. Alright, 02:18:10.739 --> 02:18:17.219 everybody agrees. Okay, number two. AI assists. 02:18:18.299 --> 02:18:23.760 Humans decide. Should be, yep. Oh, yes. That's 02:18:23.760 --> 02:18:26.840 the way it should go. That's definitely how it 02:18:26.840 --> 02:18:37.409 should go. Tell me more. Because it might generate 02:18:37.409 --> 02:18:43.629 some response that helps you with who knows what 02:18:43.629 --> 02:18:49.090 the task is, but you might decide what it's generating 02:18:49.090 --> 02:18:53.790 is not very safe or practical. I don't think 02:18:53.790 --> 02:18:56.209 I'm going to use it. Yes, it assisted, but I 02:18:56.209 --> 02:18:57.889 don't think I'm going to use what it gave me. 02:18:58.569 --> 02:19:02.309 Oh, and that's when you can use multiple AIs, 02:19:02.329 --> 02:19:09.170 like Gemini, odd, for example. There's others 02:19:09.170 --> 02:19:15.069 that might. Well, and today's example, when I 02:19:15.069 --> 02:19:19.049 was doing terms of service analysis, it recommended 02:19:19.049 --> 02:19:24.450 something. Because I said, put this in simple 02:19:24.450 --> 02:19:28.819 terms so I can tell it to Eric. Because Eric's 02:19:28.819 --> 02:19:31.680 a phone user, he doesn't have access to the internet, 02:19:31.899 --> 02:19:40.200 and he can't read this. It gave me one thing. 02:19:41.600 --> 02:19:44.700 I analyzed it myself and said, you know what 02:19:44.700 --> 02:19:47.459 I think I'm going to do? I'm going to just tell 02:19:47.459 --> 02:19:51.059 him, remember that issue you had some time back? 02:19:52.299 --> 02:19:56.780 Well, today's email that I got indicates this. 02:19:58.350 --> 02:20:01.110 And I'll be, by the way, I'm leaving later today, 02:20:01.290 --> 02:20:05.110 but if you have any questions, you can ping me. 02:20:06.409 --> 02:20:13.190 And it said, that seems logical. Anybody else 02:20:13.190 --> 02:20:20.049 have any examples? Well, basically, what I was 02:20:20.049 --> 02:20:24.850 going to say, when we initiate the request, we 02:20:24.850 --> 02:20:29.690 have the right to decide on, what to get help 02:20:29.690 --> 02:20:39.110 with. Like, let's say, hey, Chad GPT, if I'm 02:20:39.110 --> 02:20:44.010 writing a radio news story regarding 100 ,000 02:20:44.010 --> 02:20:50.969 watts, how should it be said in broadcast terms? 02:20:52.350 --> 02:20:55.030 That was my example from this past week's RCL 02:20:55.030 --> 02:21:00.770 News segment. Speaking of which, remind me to 02:21:00.770 --> 02:21:05.110 go to that in Irana, because we need to talk 02:21:05.110 --> 02:21:14.170 about that. I forgot. Okay. I knew about it, 02:21:14.190 --> 02:21:20.350 but I forgot. You mean... Item number three. 02:21:20.350 --> 02:21:22.809 You should always be in charge, because the thing 02:21:22.809 --> 02:21:27.500 is, your AI isn't going to be correct. So that's 02:21:27.500 --> 02:21:30.139 when you need to say, okay, is this something 02:21:30.139 --> 02:21:33.600 I should do? Is this something I should consult 02:21:33.600 --> 02:21:35.840 somebody with, whether it's a security advisor, 02:21:36.239 --> 02:21:38.540 whether it's a doctor, whether it's a therapist, 02:21:38.639 --> 02:21:42.340 whether it's, you know, just a parent or guardian, 02:21:42.440 --> 02:21:49.459 you know, that's where the decision comes ultimately 02:21:49.459 --> 02:21:54.200 up to you and you shouldn't use AI as a doctor. 02:21:55.040 --> 02:21:59.120 a lawyer. You should only use it as an advisor. 02:22:00.500 --> 02:22:04.139 And we'll get to my example on how I used it 02:22:04.139 --> 02:22:09.559 to assess my symptoms in understanding what was 02:22:09.559 --> 02:22:14.739 okay to treat at home versus if this happens 02:22:14.739 --> 02:22:23.600 more, then you need to get help beyond what I 02:22:23.600 --> 02:22:27.719 can give you. We'll get into that in a little 02:22:27.719 --> 02:22:34.040 bit. Item number three, unless anybody else has 02:22:34.040 --> 02:22:41.040 any other things to add. Nope, I'm good. Go ahead. 02:22:45.340 --> 02:22:53.659 Verification is non optional. Please use trusted 02:22:54.670 --> 02:23:03.629 and well -known sources. I always do that. The 02:23:03.629 --> 02:23:07.030 last of that section says, these are guardrails, 02:23:07.030 --> 02:23:11.229 not rules. What do you think best practices are? 02:23:11.469 --> 02:23:18.950 Be precise. There's no wrong answer here. So 02:23:18.950 --> 02:23:22.920 if there's anything else to add, go ahead. When 02:23:22.920 --> 02:23:26.340 I uploaded my cannabis card to ChatGPT, it said, 02:23:26.500 --> 02:23:30.719 this is what it says. I'm not going to say anything 02:23:30.719 --> 02:23:34.540 what it said. It's personal, but this is what 02:23:34.540 --> 02:23:42.000 it said. But be aware, it is sensitive information. 02:23:42.239 --> 02:23:46.920 So if you can, please do this. And it said, delete 02:23:46.920 --> 02:23:49.940 either one or two things. Delete the picture. 02:23:50.670 --> 02:23:53.469 Or delete the chat. And I chose to delete the 02:23:53.469 --> 02:23:58.549 chat. I mean, that's my example for that one. 02:24:01.090 --> 02:24:03.870 I thought it was a good example, and I thought... 02:24:03.870 --> 02:24:09.549 That is a great example. And while Ira says, 02:24:09.729 --> 02:24:14.790 don't use these tools, they told me clearly, 02:24:14.909 --> 02:24:20.860 don't use this for that. And I completely understand. 02:24:21.559 --> 02:24:26.819 But I also said, well, I needed it. I thought 02:24:26.819 --> 02:24:30.159 of you calling after the fact, but the tool gave 02:24:30.159 --> 02:24:36.760 me exactly what I needed. So I didn't bother. 02:24:37.159 --> 02:24:39.319 If I had issues, I would have called. Should 02:24:39.319 --> 02:24:41.500 I have done it that way? No, probably not. But 02:24:41.500 --> 02:24:47.649 it was the tool that I needed. Correct. I agree 02:24:47.649 --> 02:24:50.489 with Jared. I mean, that's, you know, what I 02:24:50.489 --> 02:24:57.450 needed it for. But it's better that a trained 02:24:57.450 --> 02:25:01.450 human, like an IRA agent, not a be -my -eyes 02:25:01.450 --> 02:25:10.229 agent. Let's make this clear. Oh, no. IRA. They 02:25:10.229 --> 02:25:17.100 are trained in how to deal with that. Be my eyes 02:25:17.100 --> 02:25:19.479 is all volunteer. You don't know who you're dealing 02:25:19.479 --> 02:25:25.639 with. I have what may be a cautionary tale, but 02:25:25.639 --> 02:25:33.659 I really can't prove this. Would you like to 02:25:33.659 --> 02:25:37.479 proceed? I'm torn because I don't want to muddy 02:25:37.479 --> 02:25:45.840 the waters. Okay. You're good. And again, because 02:25:45.840 --> 02:25:51.059 I don't want... Go ahead. Go ahead? You don't 02:25:51.059 --> 02:25:54.200 want... Yeah, and again, I don't know if this 02:25:54.200 --> 02:25:59.280 is actually where this happened, but I will just 02:25:59.280 --> 02:26:03.040 say, unfortunately, I did have to get a card 02:26:03.040 --> 02:26:09.219 replaced, and I called Ira for that. Mm -hmm. 02:26:09.819 --> 02:26:14.049 And at first, unfortunately, I thought... It 02:26:14.049 --> 02:26:17.670 might have been the agent I got, but after I 02:26:17.670 --> 02:26:21.790 made the call, all of a sudden, charges from 02:26:21.790 --> 02:26:27.489 Prime Video appeared. But the only thing that 02:26:27.489 --> 02:26:32.409 would also rule Ira out is that, unfortunately, 02:26:32.709 --> 02:26:35.829 there is something that I learned about called... 02:26:36.639 --> 02:26:41.680 Card Account Updater Services. Speaking of which, 02:26:41.760 --> 02:26:45.340 I do have an update on that. Oh, what's that? 02:26:45.659 --> 02:26:51.559 But I want Nick first to explain what this is, 02:26:51.760 --> 02:26:58.239 and then I will tell my story afterward. Okay, 02:26:58.319 --> 02:27:03.760 so Card Account Updater Services. I think we... 02:27:04.489 --> 02:27:07.750 May all be familiar with them, but essentially 02:27:07.750 --> 02:27:13.770 they are services provided by all of the major 02:27:13.770 --> 02:27:20.250 credit card companies to various companies like 02:27:20.250 --> 02:27:23.809 other entities, i .e. your Netflix, whatever. 02:27:24.309 --> 02:27:29.569 And what these services allow those companies 02:27:29.569 --> 02:27:36.450 to do is say they detect that. Your card has 02:27:36.450 --> 02:27:40.250 expired or, you know, you replace your card because 02:27:40.250 --> 02:27:44.329 maybe that one is stolen. They can. And I think 02:27:44.329 --> 02:27:47.149 it's an all automated process. Go to this. Use 02:27:47.149 --> 02:27:54.069 a service. Say, hey, a card blank that belongs 02:27:54.069 --> 02:28:01.920 to Terry has expired. Could you pass us? you 02:28:01.920 --> 02:28:05.879 know, securely, as they claim, the new info for 02:28:05.879 --> 02:28:08.680 the most current card so that we can continue 02:28:08.680 --> 02:28:12.120 his subscription. And then that's what these 02:28:12.120 --> 02:28:20.659 services are supposed to do. I kind of like what 02:28:20.659 --> 02:28:23.000 Apple does a little bit. Like, if you have Apple 02:28:23.000 --> 02:28:26.760 Pay, it'll, like, say, hey, you have a new card. 02:28:27.620 --> 02:28:32.690 Let's do it. Except the creepy and chilling part 02:28:32.690 --> 02:28:36.870 is that it doesn't do this automatically. These 02:28:36.870 --> 02:28:43.530 things do. Oh, boy. Apple Pay, it'll say, hey, 02:28:43.569 --> 02:28:46.930 your card's expired, but it won't go out and 02:28:46.930 --> 02:28:53.389 actively get the new card data. You do that. 02:28:53.510 --> 02:28:59.190 You're totally in control of that. I think it 02:28:59.190 --> 02:29:03.270 might have been one of those because the friend 02:29:03.270 --> 02:29:13.629 who had the number was using Amazon Prime on 02:29:13.629 --> 02:29:18.430 it, which probably meant that Amazon Prime used 02:29:18.430 --> 02:29:22.709 one of those CAUs, as they call them, and got... 02:29:23.879 --> 02:29:26.379 And yeah, you know, the whole automated process 02:29:26.379 --> 02:29:29.840 so that that person could continue using Prime 02:29:29.840 --> 02:29:41.920 Video. Yeah. And yes, I think it is. I understand 02:29:41.920 --> 02:29:45.680 the marketing. Well, revenue aside for a lot 02:29:45.680 --> 02:29:48.239 of companies, because that prevents what they 02:29:48.239 --> 02:29:53.620 call churn. But at the same time. it's very questionable 02:29:53.620 --> 02:29:57.360 and it's frustrating because it defeats the purpose 02:29:57.360 --> 02:30:01.700 of getting a new card. More or less, yeah. So 02:30:01.700 --> 02:30:05.159 what's the point of getting a new card? Why don't 02:30:05.159 --> 02:30:07.079 you keep the same one you have and just update 02:30:07.079 --> 02:30:12.059 the expiration on it? Yeah, but if it's stolen, 02:30:12.139 --> 02:30:15.219 it doesn't matter. They'll still do this. Yeah, 02:30:15.239 --> 02:30:36.700 that's the creepy part. That's right. Okay. Great 02:30:36.700 --> 02:30:44.520 comments, guys. Great comments. So. Yes. For 02:30:44.520 --> 02:30:55.510 sure, I agree. My story was that I was in my 02:30:55.510 --> 02:30:59.170 PayPal account, my actual PayPal account, looking 02:30:59.170 --> 02:31:08.309 at things. And Nick is right. It updated my Wells 02:31:08.309 --> 02:31:18.809 Fargo card to $8 .29. And remember, I activated 02:31:18.809 --> 02:31:23.190 it at the bank. And the banker didn't give me 02:31:23.190 --> 02:31:26.170 information about my card at all. I just wanted 02:31:26.170 --> 02:31:30.409 it activated so that I could use it at the bank. 02:31:30.510 --> 02:31:33.469 I didn't ask for the three -digit code. I didn't 02:31:33.469 --> 02:31:44.610 write anything down. I didn't do anything. Right. 02:31:48.909 --> 02:32:09.670 So... It updated it to 8 .29. Yikes. So, yes, 02:32:09.870 --> 02:32:28.420 I do know exactly what Nick is yapping. And sadly 02:32:28.420 --> 02:32:32.040 it applies, and sadly as I said earlier, just 02:32:32.040 --> 02:32:35.799 now, it appears to apply to cards that you replace. 02:32:36.340 --> 02:32:39.420 I mean, PayPal not so much, but other services 02:32:39.420 --> 02:32:42.559 that are monthly recurring subscriptions, that's 02:32:42.559 --> 02:32:53.040 where this is really... Yeah. Sorry, guys, I 02:32:53.040 --> 02:32:54.979 had to call to see what was going on with my 02:32:54.979 --> 02:33:01.120 dog. I'm back. You're good. Nope. You're good. 02:33:03.299 --> 02:33:05.100 Yeah, because we read the brims of that, so. 02:33:09.139 --> 02:33:12.159 I'm right here. I'm in the bathroom. I'm in the 02:33:12.159 --> 02:33:16.799 restroom. Don't fall in, Terry. Yeah, I'm in 02:33:16.799 --> 02:33:30.270 here. Who would like to read item number... Oh, 02:33:30.370 --> 02:33:34.989 three. Actually, I'm already on it. May I claim 02:33:34.989 --> 02:33:40.790 it? Go ahead. Because my file just started at 02:33:40.790 --> 02:33:45.569 the beginning. Oh, you're good. Responsible versus 02:33:45.569 --> 02:33:53.090 risky AI use. Not all AI use is equal, says our 02:33:53.090 --> 02:33:57.469 transcriber. We know that context matters more 02:33:57.469 --> 02:34:03.989 than capability. Responsible examples include, 02:34:04.309 --> 02:34:10.809 one, outlining and prep work. I definitely agree. 02:34:16.399 --> 02:34:20.840 You may talk about each if you would like or 02:34:20.840 --> 02:34:23.540 read the entire thing and then you can talk about 02:34:23.540 --> 02:34:26.040 it all at once. Whatever you guys would like 02:34:26.040 --> 02:34:31.860 to do is fine. Okay. Two, summarization for review. 02:34:32.299 --> 02:34:36.760 Three, accessibility support with human review. 02:34:38.040 --> 02:34:44.120 Okay, stop there and let's let the panel discuss. 02:34:45.290 --> 02:34:50.389 that first so those three items again outlining 02:34:50.389 --> 02:34:52.930 and prep work that's what I did with this show 02:34:52.930 --> 02:34:58.010 and the upcoming show that we announced earlier 02:34:58.010 --> 02:35:06.850 in today's program definitely the prep work is 02:35:06.850 --> 02:35:10.729 extremely important so that way it gets trained 02:35:10.729 --> 02:35:16.659 on what on what you're going to compose and what 02:35:16.659 --> 02:35:19.840 answers it'll give. So, yes, I feel prep work 02:35:19.840 --> 02:35:22.760 is very instrumental in this. It's very key, 02:35:22.860 --> 02:35:27.219 yeah. Well, I wanted to comment just sort of 02:35:27.219 --> 02:35:30.719 an all -at -once thing for... Go ahead. Yeah, 02:35:31.399 --> 02:35:34.379 use cases number one and two. I agree with those. 02:35:34.600 --> 02:35:39.530 Summarizing for review is number two. Summarization 02:35:39.530 --> 02:35:42.850 for you, sorry. Right, right. Outlining slash 02:35:42.850 --> 02:35:47.329 prep and summarization. Okay, so items one and 02:35:47.329 --> 02:35:51.729 two, go ahead. Yeah, because most likely you 02:35:51.729 --> 02:35:56.250 are just using things that are going to be publicly 02:35:56.250 --> 02:36:00.350 broadcast anyway, and it's in the public domain, 02:36:00.450 --> 02:36:03.489 it's nothing sensitive, so you're not asking 02:36:03.489 --> 02:36:07.340 it slash feeding it things that are... potentially 02:36:07.340 --> 02:36:11.139 compromising and dangerous to your health or 02:36:11.139 --> 02:36:23.159 wellbeing. Go ahead. Yeah. And so if you're doing 02:36:23.159 --> 02:36:27.799 show prep, yes, that makes things way more convenient. 02:36:28.780 --> 02:36:32.899 You know, that's good. And then again, summarization, 02:36:32.979 --> 02:36:37.319 you know, it saves you, sometime if you don't 02:36:37.319 --> 02:36:43.200 want to read a whole file or do any of that so 02:36:43.200 --> 02:36:47.180 totally okay and totally acceptable in my book 02:36:47.180 --> 02:36:57.399 to use it for those because that's again where 02:36:57.399 --> 02:37:00.299 those are both cases where personal safety does 02:37:00.299 --> 02:37:09.290 not come into play Yeah. Sorry, I'm giving it 02:37:09.290 --> 02:37:11.750 an update from this morning's communication so 02:37:11.750 --> 02:37:16.670 that it understands that it assisted me and we're 02:37:16.670 --> 02:37:19.829 sort of on the same page. I'm doing two things 02:37:19.829 --> 02:37:24.209 at once. But I'm listening. And yes, you're absolutely 02:37:24.209 --> 02:37:28.190 correct. And we can get into risky stuff. But 02:37:28.190 --> 02:37:31.229 before we do that, the last item is accessibility 02:37:31.229 --> 02:37:36.129 support with human review, i .e. it looking at 02:37:36.129 --> 02:37:40.590 my code. And telling me I'm missing stuff. Like, 02:37:40.610 --> 02:37:43.969 I missed an ally somewhere. Or I missed a closing 02:37:43.969 --> 02:37:48.870 ally somewhere. Or a closing... You know, like, 02:37:48.969 --> 02:37:53.930 you should have put a percent list here. Or made 02:37:53.930 --> 02:38:00.090 this percent indent in Braille 2000. Because 02:38:00.090 --> 02:38:10.979 it understands those. As examples. Yeah. Yeah, 02:38:11.020 --> 02:38:15.040 I would say, you know, I would definitely agree 02:38:15.040 --> 02:38:20.200 with that aspect because it, you know, it should 02:38:20.200 --> 02:38:22.979 have the right to look at what we are trying 02:38:22.979 --> 02:38:26.200 to portrayal. And I feel giving it evidence such 02:38:26.200 --> 02:38:29.559 as, you know, coding prior episode notes for 02:38:29.559 --> 02:38:34.420 this case and the whole nine yards. So I feel 02:38:34.420 --> 02:38:37.079 that's, we hit the nail right on the head. Yeah. 02:38:38.829 --> 02:38:41.809 I just got a thumbs up. I said great, and it 02:38:41.809 --> 02:38:53.489 said thumbs up. Nice. Okay, so Preston, since 02:38:53.489 --> 02:38:57.229 this is your section, the next one, your item, 02:38:57.469 --> 02:39:03.229 the next heading is risky examples. Oh, yes. 02:39:03.450 --> 02:39:06.670 We'll go one at a time. Hold on. Before you read 02:39:06.670 --> 02:39:09.969 the three, do you... Guys want to do one at a 02:39:09.969 --> 02:39:14.329 time, or do you guys want to do one large set? 02:39:17.649 --> 02:39:20.370 I prefer a large set. Yeah, I'm good either way. 02:39:20.430 --> 02:39:23.229 Okay. All right. All right, so read the three. 02:39:23.250 --> 02:39:31.350 Okay. Number one, publishing AI output. Verbatim. 02:39:32.790 --> 02:39:37.530 Verbatim. Oh, boy. That means word for word. 02:39:39.389 --> 02:39:45.129 Yep. Wow. And this is a shortened version of 02:39:45.129 --> 02:39:47.770 writing word for word. And I always wanted to 02:39:47.770 --> 02:39:52.829 know how to spell this stupid thing. So that's 02:39:52.829 --> 02:39:57.530 what this word is. Verbatim. V -E -R -B -A -T 02:39:57.530 --> 02:40:05.129 -I -M. That's word for word. Okay. Item number 02:40:05.129 --> 02:40:11.299 two. Number two, using AI as authority. Oh, don't 02:40:11.299 --> 02:40:18.739 do that. Letting AI speak you for. That's for. 02:40:20.100 --> 02:40:24.700 Letting AI speak for communities. Oh, boy. Well, 02:40:28.319 --> 02:40:31.379 I mean, you definitely don't want to give it 02:40:31.379 --> 02:40:36.229 in the wrong hands. No, you don't. I don't quite 02:40:36.229 --> 02:40:38.530 understand number three, to be perfectly honest. 02:40:38.569 --> 02:40:42.389 Number one and number two I do get, but number 02:40:42.389 --> 02:40:47.989 three, I'm a little confused. Well, if somebody, 02:40:48.209 --> 02:40:52.690 like, if I just left this alone as an accessibility 02:40:52.690 --> 02:40:56.750 topic, and I didn't edit it to make it clear 02:40:56.750 --> 02:41:03.729 on what we're talking about... Mm -hmm. then 02:41:03.729 --> 02:41:10.389 whatever it wrote is its narrative for what the 02:41:10.389 --> 02:41:16.690 community thinks. It's how I interpret that. 02:41:18.129 --> 02:41:24.489 Now, we could ask it, what do you mean when you 02:41:24.489 --> 02:41:28.430 wrote in the show notes letting AI speak for 02:41:28.430 --> 02:41:34.770 communities? And I could probably do that because 02:41:34.770 --> 02:41:40.329 it can research all of my past history, and it 02:41:40.329 --> 02:41:43.989 can then give me a summary, and maybe we can 02:41:43.989 --> 02:41:49.670 come back and read that as part of errata for 02:41:49.670 --> 02:41:52.510 next week. We can definitely do that if that's 02:41:52.510 --> 02:42:01.370 a questioning item. Mm -hmm. Mm -hmm. So that's 02:42:01.370 --> 02:42:03.750 section three. Yeah, I think maybe some elaboration 02:42:03.750 --> 02:42:07.690 will work. Yeah, number three. So that's section 02:42:07.690 --> 02:42:14.889 three, item three in the show notes. Okay. Yeah. 02:42:18.069 --> 02:42:25.270 All right, so we'll follow up with that because 02:42:25.270 --> 02:42:32.100 I don't want to try and read with NVDA. and regurgitate 02:42:32.100 --> 02:42:37.459 on a regular basis. So I want to make sure that 02:42:37.459 --> 02:42:40.260 we're clear. Now, I could summarize the whole 02:42:40.260 --> 02:42:42.440 PayPal thing. I didn't have to read it word for 02:42:42.440 --> 02:42:46.139 word because I understand it. But this is a little 02:42:46.139 --> 02:42:48.860 more out of my scope, so I don't want to do that. 02:42:50.459 --> 02:42:53.760 So Preston, if you can mental note when you get 02:42:53.760 --> 02:42:55.979 pinged about what you're getting pinged about 02:42:55.979 --> 02:43:00.659 on Friday. Remind me to run that through and 02:43:00.659 --> 02:43:08.219 get a Braille copy for 268. And we'll add that 02:43:08.219 --> 02:43:17.739 to the Braille list. Okay. So, section three, 02:43:17.959 --> 02:43:26.760 item three, under risky. Yeah. Under risky. Examples. 02:43:27.830 --> 02:43:33.649 Yes. Got it. Okay. If you need a reminder, if 02:43:33.649 --> 02:43:36.549 you need a reminder when it's not my turn to 02:43:36.549 --> 02:43:39.590 read, I can go set one for you. Just let me know. 02:43:40.989 --> 02:43:48.129 Yeah. Or even I can do it for myself, but I got 02:43:48.129 --> 02:43:53.049 enough going on at the moment. Okay. This is 02:43:53.049 --> 02:43:56.250 what I think is important, and it said so. It 02:43:56.250 --> 02:44:02.319 said this is, the best point I think we can make 02:44:02.319 --> 02:44:09.319 as part of this entire episode. AI can help you 02:44:09.319 --> 02:44:21.059 think. It cannot take responsibility. So the 02:44:21.059 --> 02:44:29.120 sentence again is, AI can help you think. It 02:44:29.120 --> 02:44:33.319 cannot take responsibility. Take responsibility. 02:44:34.520 --> 02:44:41.040 Yes. Yeah. That is totally unanimous. Right. 02:44:41.219 --> 02:44:45.860 Yeah. It'll help you organize your thoughts. 02:44:45.899 --> 02:44:50.379 I get that, but... Again, like the sentence... 02:44:50.379 --> 02:44:53.200 And it helped you rewrite an email. You must 02:44:53.200 --> 02:44:54.760 take responsibility. It found spelling mistakes. 02:44:56.260 --> 02:44:59.239 It analyzed it and it said, maybe you want to 02:44:59.239 --> 02:45:05.879 try this. Yeah. But at the end of the day, we 02:45:05.879 --> 02:45:08.479 all got to remember, it's not a mind reader. 02:45:09.079 --> 02:45:15.280 No. It needs... It needs... You to make those 02:45:15.280 --> 02:45:18.260 decisions. Yeah, you're the one who still acts. 02:45:18.340 --> 02:45:24.739 Yes. You must take responsibility. That's where... 02:45:25.610 --> 02:45:27.750 Yep, that's where I was going with that. Yeah, 02:45:27.850 --> 02:45:36.649 yeah. Take, for example, and I'm reading because 02:45:36.649 --> 02:45:43.969 this is my case use. So, sorry about that, but 02:45:43.969 --> 02:45:49.030 I think this is important for me to do. Take, 02:45:49.030 --> 02:45:52.430 for example, you not feeling well and you want 02:45:52.430 --> 02:45:55.610 ideas before you panic and call the doctor or 02:45:55.610 --> 02:46:01.270 do something irrational. You must be the one 02:46:01.270 --> 02:46:08.110 to make the final decision. Correct. The question, 02:46:08.290 --> 02:46:13.790 what do you guys think of the analysis I'm giving? 02:46:13.930 --> 02:46:18.600 Good, bad, or indifferent? Call the comment line, 02:46:18.840 --> 02:46:22.780 email, or iMessage. So the comment line is 888 02:46:22.780 --> 02:46:33.500 -405 -7524. Email, iMessage, either J -A -R -E 02:46:33.500 --> 02:46:37.120 -D -R -I -M -E -R at 986themix .com or tech, 02:46:37.260 --> 02:46:42.840 that's T -E -C -H, at M, as in Mike, E -N -V 02:46:42.840 --> 02:46:51.920 -I .org. And WhatsApp is 804 -442 -6975 if you 02:46:51.920 --> 02:47:01.659 would like to use that. Accessibility and AI. 02:47:02.020 --> 02:47:09.579 Why the bar is higher. Yep. I can get that. Would 02:47:09.579 --> 02:47:14.819 somebody like to read that while I go find a 02:47:14.819 --> 02:47:19.860 Halls? Yep. Here's some things to consider. Terry's 02:47:19.860 --> 02:47:23.700 got print. Auto captions and starting points. 02:47:25.379 --> 02:47:32.600 Not compliance. Oh, wait. That's not what I got. 02:47:33.420 --> 02:47:37.799 I have it. Auto captions are a starting point. 02:47:38.239 --> 02:47:44.340 Not compliance. Not compliance. Okay. AI driven. 02:47:45.200 --> 02:47:56.159 UI changes and often breaks assistive tech. Disabled 02:47:56.159 --> 02:48:05.620 users often become early warning systems. Take 02:48:05.620 --> 02:48:14.200 for example an app update that completely breaks 02:48:17.289 --> 02:48:22.450 Yep, we've all been there. Yes, I believe we've 02:48:22.450 --> 02:48:28.329 all been there. If your AI feature isn't accessible, 02:48:28.649 --> 02:48:32.409 it isn't finished. I agree with that. I'm sorry, 02:48:32.530 --> 02:48:40.729 but I agree with that. Yes, totally. Okay, so... 02:48:41.739 --> 02:48:48.260 What are we agreeing on, gentlemen? Well, actually, 02:48:48.540 --> 02:48:54.540 I don't think we read the first synopsis where 02:48:54.540 --> 02:48:58.040 it said AI can reduce barriers or multiply them. 02:48:58.100 --> 02:49:02.120 Accessibility must be part of the best practice, 02:49:02.260 --> 02:49:04.659 not the action. But hold on a second. Remember, 02:49:04.840 --> 02:49:09.680 I stepped away. So are we talking about... where 02:49:09.680 --> 02:49:15.219 I wrote, here are some things to consider. Well, 02:49:15.239 --> 02:49:17.520 we were talking about... Here are some things 02:49:17.520 --> 02:49:20.180 to consider. Yeah, the last line. That's the 02:49:20.180 --> 02:49:23.840 section, yes. Yes. Okay, so what number are you 02:49:23.840 --> 02:49:26.139 on, just so that I'm on the same page with you? 02:49:26.219 --> 02:49:27.780 Well, I wrote them all, but I can go through 02:49:27.780 --> 02:49:30.879 them again. No, no, no, you're fine. AutoCAD 02:49:30.879 --> 02:49:34.459 is our starting point, not compliance. So number 02:49:34.459 --> 02:49:38.040 one. No, that's number one. That's number one. 02:49:38.120 --> 02:49:44.440 So auto captions, that's important for the deaf 02:49:44.440 --> 02:49:50.780 community. Yes. So it is a starting point, but 02:49:50.780 --> 02:49:56.180 that doesn't mean you're compliant, i .e. a video. 02:49:57.760 --> 02:50:08.280 Yep. Okay. Number two. AI -driven UI often breaks 02:50:08.280 --> 02:50:15.459 assistive tech. Changes often. Often breaks assistive 02:50:15.459 --> 02:50:18.360 tech, yeah. I forgot the word changes. That's 02:50:18.360 --> 02:50:20.899 what happened with their app completely. I've 02:50:20.899 --> 02:50:30.079 already put in two high -tech reports into OpenAI 02:50:30.079 --> 02:50:33.500 .com. Because they updated right after I got 02:50:33.500 --> 02:50:37.340 the account. So that is, they broke it completely. 02:50:37.600 --> 02:50:45.559 It's bad. Number three. So disabled users become 02:50:45.559 --> 02:50:52.020 early warning system. Which is exactly what happened 02:50:52.020 --> 02:50:56.719 here. I updated like I should. It said bug fixes 02:50:56.719 --> 02:50:59.639 and improvements. Oh yeah, and that's going to 02:50:59.639 --> 02:51:04.620 be another topic. And then what happened? Accessibility 02:51:04.620 --> 02:51:10.020 regressed. For example, an app update that completely 02:51:10.020 --> 02:51:15.399 breaks accessibility. Yes. And regresses the 02:51:15.399 --> 02:51:25.500 usability. Correct. Of the app. Of the app. If 02:51:25.500 --> 02:51:31.239 your AI feature isn't accessible, It isn't finished. 02:51:32.520 --> 02:51:35.639 And I agreed with that. I totally agree. That 02:51:35.639 --> 02:51:42.440 should be. And the question, have you had these 02:51:42.440 --> 02:51:46.219 issues? And if so, what did you do about them? 02:51:46.500 --> 02:51:49.979 Submitted bug reports? Submitted through support 02:51:49.979 --> 02:51:54.700 channels or feedback forums? Went to a forum 02:51:54.700 --> 02:51:58.049 to... You trust to discuss whether others are 02:51:58.049 --> 02:52:02.430 having the same issue or issues. There's no single 02:52:02.430 --> 02:52:09.889 right response here. I haven't really had this 02:52:09.889 --> 02:52:14.670 with AI apps because I don't really use them 02:52:14.670 --> 02:52:22.530 that often. Okay, fair. But there are some apps. 02:52:24.119 --> 02:52:29.299 like, telecrap that really went backwards. So, 02:52:29.319 --> 02:52:33.239 not AI -related, I know, but certainly... You're 02:52:33.239 --> 02:52:41.479 fine. Please elaborate. Because in this case... 02:52:41.479 --> 02:52:44.260 Hold on. Before you actually do that, in this 02:52:44.260 --> 02:52:50.059 case, we're talking about regression. Meaning, 02:52:50.200 --> 02:52:55.010 it worked. But it no longer works. And as we 02:52:55.010 --> 02:53:00.690 allow on TSB, and I think the AI tool sees that 02:53:00.690 --> 02:53:03.790 we can allow for a little bit of wiggle room 02:53:03.790 --> 02:53:13.409 within the discussion. Yep. Let's go into that 02:53:13.409 --> 02:53:17.129 because we're talking about accessibility, which 02:53:17.129 --> 02:53:21.139 is part of item number three. of that section 02:53:21.139 --> 02:53:25.979 of the discussion outline. So you're not out 02:53:25.979 --> 02:53:34.319 of line in mentioning telecrap, as we call it 02:53:34.319 --> 02:53:42.379 here on TSB. Yes. So please, talk about your 02:53:42.379 --> 02:53:45.219 regression issue. I know we've talked about it 02:53:45.219 --> 02:53:49.639 in the past, but this is similar to my... chat 02:53:49.639 --> 02:53:55.280 GPT issue S that I've submitted since upgrading, 02:53:55.500 --> 02:54:03.159 but go ahead. So earlier on telegram slash tele 02:54:03.159 --> 02:54:07.840 crap worked beautifully with voiceover, or maybe 02:54:07.840 --> 02:54:12.639 if not beautifully, at least decently and well 02:54:12.639 --> 02:54:18.200 enough that you could pretty much use it. As 02:54:18.200 --> 02:54:23.159 well as a sighted person could. Over the last 02:54:23.159 --> 02:54:28.700 few updates, they have broken things, i .e. you 02:54:28.700 --> 02:54:31.860 can no longer see where the send button is now. 02:54:31.940 --> 02:54:37.680 You can no longer really see where the text box 02:54:37.680 --> 02:54:45.840 to write is. And granted... What I have done 02:54:45.840 --> 02:54:49.379 about it is not exactly any of those things. 02:54:49.440 --> 02:54:52.680 I've moved to alternative sources, i .e. using 02:54:52.680 --> 02:54:57.799 Telecrap through the Tweezcake client and communicating 02:54:57.799 --> 02:55:05.899 via other platforms, i .e. WhatsApp. Yeah, if 02:55:05.899 --> 02:55:10.020 I remember, Nick, even the send voice message 02:55:10.020 --> 02:55:15.020 button doesn't even read anymore. On telecrap? 02:55:15.159 --> 02:55:18.020 Yeah, telecrap. I think that's true, actually. 02:55:18.360 --> 02:55:20.739 Because it used to be kind of hard to find, but 02:55:20.739 --> 02:55:23.159 it was doable back then. It was doable back then, 02:55:23.219 --> 02:55:26.520 yeah, exactly. And now I think screen recognition, 02:55:26.700 --> 02:55:29.899 if you have that feature, sort of works, but 02:55:29.899 --> 02:55:34.559 even that's sort of a crapshoot. Yeah. Yeah, 02:55:34.639 --> 02:55:47.379 unfortunately. Yeah, I haven't had any many issues 02:55:47.379 --> 02:55:53.219 with AI, but I feel that having, you know, knowing 02:55:53.219 --> 02:55:57.139 what skills you have and knowing how you can 02:55:57.139 --> 02:56:00.920 use your tools is always beneficial. All right, 02:56:00.940 --> 02:56:10.299 let me switch back. Okay, guys, I'm going to 02:56:10.299 --> 02:56:14.930 switch back. Hold on a second. There's definitely 02:56:14.930 --> 02:56:17.889 more work we need to be doing, but that's why 02:56:17.889 --> 02:56:32.329 we're their captain. Here's a perfect example 02:56:32.329 --> 02:56:38.409 of viewing an AI tool. I wrote to it just now, 02:56:38.610 --> 02:56:43.649 I'm a complete idiot. I did not take Ricola before 02:56:43.649 --> 02:56:47.670 TSB. I've been coughing a bit, but not hacking 02:56:47.670 --> 02:56:52.950 up and not like I've been in the past. How do 02:56:52.950 --> 02:56:56.750 I remember to do this for next time? Right? So 02:56:56.750 --> 02:56:59.690 it's like, okay, here are symptoms. It's not 02:56:59.690 --> 02:57:04.950 as bad as it was. Right? So I'm not, I'm coughing, 02:57:05.129 --> 02:57:09.670 but I'm not hacking up and spitting up and carrying 02:57:09.670 --> 02:57:13.000 on for 20 minutes. Like I've been known to do. 02:57:15.700 --> 02:57:20.860 And the first thing it says is, you're not an 02:57:20.860 --> 02:57:24.299 idiot, you're human. Tired? Juggling too much? 02:57:24.379 --> 02:57:34.379 And this was preventable, not stupid. I don't 02:57:34.379 --> 02:57:37.979 mean to sidetrack you, but I'm wondering if, 02:57:38.079 --> 02:57:41.239 as we were discussing earlier, And I think we 02:57:41.239 --> 02:57:43.680 did sort of talk about this already, but, you 02:57:43.680 --> 02:57:46.379 know. Yes, go ahead. I think it's worth repeating. 02:57:47.500 --> 02:57:50.780 Does your Echo device, especially if you have 02:57:50.780 --> 02:57:54.479 the Plus version of that, lift some of that from 02:57:54.479 --> 02:57:57.959 GPT? Because I've gotten similar responses to 02:57:57.959 --> 02:58:02.860 things that I've given it. I don't have an answer 02:58:02.860 --> 02:58:08.870 on what the premium offers. Because I don't know 02:58:08.870 --> 02:58:17.829 what's connected to it. I wouldn't... Contact 02:58:17.829 --> 02:58:31.969 through the app the Alexa department and ask. 02:58:32.010 --> 02:58:38.979 Oh, yes. But this thing says... What you're really 02:58:38.979 --> 02:58:42.219 asking for is, how do I make this automatic so 02:58:42.219 --> 02:58:46.459 future JR doesn't have to remember at all? And 02:58:46.459 --> 02:58:49.079 JR has been my middle name, so I gave it that. 02:58:49.719 --> 02:58:53.860 So it could use my main name or my nickname, 02:58:57.760 --> 02:59:04.750 depending on what it feels like. And so... This 02:59:04.750 --> 02:59:07.629 thing sounds to me like a therapist, right? It's 02:59:07.629 --> 02:59:13.149 like, I'm a complete fucking idiot. But every 02:59:13.149 --> 02:59:17.030 time... And I told it this, too. It's like, well, 02:59:17.049 --> 02:59:21.489 I'm not a therapist. I don't, you know, prescribe 02:59:21.489 --> 02:59:23.770 anything. I'm like, well, I don't mean it as 02:59:23.770 --> 02:59:27.569 a prescribed therapist, but, like, every time 02:59:27.569 --> 02:59:30.569 I go on a rant, like, I read whatever you're 02:59:30.569 --> 02:59:47.620 saying, and... It's making sense. Right. So, 02:59:47.620 --> 02:59:54.799 I'll read this later because I mainly wanted 02:59:54.799 --> 02:59:57.420 to get some tips, but I'm in the midst of a show, 02:59:57.520 --> 03:00:01.940 but I just thought I'd share that. Yeah, I mean, 03:00:01.940 --> 03:00:08.639 it's definitely good to... get the opinions on 03:00:08.639 --> 03:00:15.920 the chat GPT. Yeah. A .K .A. Jared's second personal 03:00:15.920 --> 03:00:24.079 assistant. No kidding. Well, the problem is and 03:00:24.079 --> 03:00:29.379 this is not something I don't think we can fix. 03:00:30.760 --> 03:00:38.340 Yeah. There's two problems I have. First, with 03:00:38.340 --> 03:00:44.200 the Metrologs aspect of things, I have to basically 03:00:44.200 --> 03:00:51.360 send it my temporary log or log as I go from 03:00:51.360 --> 03:01:01.540 within the chat. I cannot email it anything. 03:01:03.239 --> 03:01:07.079 But I can send it files with instructions, like 03:01:07.079 --> 03:01:16.680 log this word for word. And it'll do that. The 03:01:16.680 --> 03:01:22.559 other thing that it cannot do, which is why I 03:01:22.559 --> 03:01:29.780 pinged you on Monday, I believe it was. Or was 03:01:29.780 --> 03:01:44.280 it last week? I need you. It was what? I think 03:01:44.280 --> 03:01:52.579 it was somewhere in that gap. Well, but anyway, 03:01:52.940 --> 03:01:57.059 it said, I cannot ping you at a certain date. 03:01:57.139 --> 03:02:01.069 I cannot ping you on a certain time. And it was 03:02:01.069 --> 03:02:03.290 telling me about reminders and other things. 03:02:03.329 --> 03:02:08.549 And I told it why I don't like reminders. And 03:02:08.549 --> 03:02:13.090 it knows about Snooster, Waker Upper, GoPingMe, 03:02:13.250 --> 03:02:16.430 other services. That's another topic we're going 03:02:16.430 --> 03:02:24.930 to get into. And how systems today may not be 03:02:24.930 --> 03:02:29.270 compliant to people who all they want. are pings 03:02:29.270 --> 03:02:33.649 for simple reminders and things like me. Right. 03:02:38.129 --> 03:02:40.930 Now, maybe that might be a tech podcast topic, 03:02:41.030 --> 03:02:45.809 not necessarily a security podcast, but it's 03:02:45.809 --> 03:02:48.770 going to be out there. I'll figure that out when 03:02:48.770 --> 03:02:55.170 I get there. I would think it'd be. I mean, I 03:02:55.170 --> 03:02:57.670 guess it could be either or. depending on the 03:02:57.670 --> 03:03:02.850 situation. I mainly use it to remind me to do 03:03:02.850 --> 03:03:10.209 things, like remove shit off of the single feeds, 03:03:10.450 --> 03:03:16.750 like remind me about this item for the board 03:03:16.750 --> 03:03:27.229 when I go and sign up. Remind me... to ping Armando 03:03:27.229 --> 03:03:34.450 before the AAC meeting about the email I sent 03:03:34.450 --> 03:03:40.209 on January 29th. You know, things of that nature. 03:03:47.870 --> 03:03:51.430 Remind me to take out the trash every week. I 03:03:51.430 --> 03:03:54.670 used to use GoPingMe for that, i .e., Take the 03:03:54.670 --> 03:03:57.370 trash from the backyard and put them out on the 03:03:57.370 --> 03:04:06.850 street. Preston, ping me and ask me if there 03:04:06.850 --> 03:04:09.690 are any accessibility issues during yesterday's 03:04:09.690 --> 03:04:17.049 trips. If so, send an email and don't forget 03:04:17.049 --> 03:04:29.040 to put that crap in your main log. Preston, remind 03:04:29.040 --> 03:04:38.000 me to... Well, okay, wrong phrasing. Go and get 03:04:38.000 --> 03:04:43.360 the files for the operation meeting from the 03:04:43.360 --> 03:04:48.500 board webpage. Or go and get the board agenda. 03:04:49.639 --> 03:04:57.319 Or go get PSAC. If you need help, ping me it's 03:04:57.319 --> 03:05:02.840 in the 2026 oh by the way I need to go get that 03:05:02.840 --> 03:05:07.440 link and put it up on jaredreimer .com's webpage 03:05:07.440 --> 03:05:11.540 that'll be for next for this coming week's update 03:05:11.540 --> 03:05:19.459 cycle but that's beyond the but that's what I'm 03:05:19.459 --> 03:05:21.700 talking about in regards to reminder platforms 03:05:27.989 --> 03:05:33.090 Okay. Yes. It's basically, you know, basic stuff. 03:05:33.190 --> 03:05:36.649 So, I mean, that makes sense. Yeah. I mean, if 03:05:36.649 --> 03:05:38.610 all else fails, we can create our own system. 03:05:38.709 --> 03:05:41.629 But so far, the one we're using, it's... Well, 03:05:41.649 --> 03:05:44.329 or we go back to reminders and it sits on our 03:05:44.329 --> 03:05:46.569 phones until we tell it we're done. And that's 03:05:46.569 --> 03:05:53.200 annoying. It is. It should, like... Do it for 03:05:53.200 --> 03:05:57.860 an hour, just like the calendar. And then go 03:05:57.860 --> 03:06:02.600 away. Maybe pop up 12 hours. Hey, I'm still waiting 03:06:02.600 --> 03:06:04.579 for you to tell me whether you're done or not. 03:06:05.040 --> 03:06:13.799 That I could see. Yeah. I could see that. But 03:06:13.799 --> 03:06:16.520 it sits there until you're done. Or you tell 03:06:16.520 --> 03:06:20.379 it, remind me later. And I never even ran the 03:06:20.379 --> 03:06:23.329 backups. On Monday, because I was involved in 03:06:23.329 --> 03:06:28.010 stuff, trying to get the agenda packages done. 03:06:28.850 --> 03:06:32.129 It reminded me on Tuesday, but I was still trying 03:06:32.129 --> 03:06:37.590 to get that stuff done. Well, the stuff was done, 03:06:37.750 --> 03:06:42.489 but I was doing other things. And so the reminders 03:06:42.489 --> 03:06:45.090 on the phone just don't work for me anymore. 03:06:46.370 --> 03:06:55.280 Yeah. It worked. You get that. Mr. J, you have 03:06:55.280 --> 03:06:58.819 not read. Would you like to read item number 03:06:58.819 --> 03:07:03.680 five, ethical red flags, 67 minutes, although 03:07:03.680 --> 03:07:08.459 we can take as much time as we need. Okay. You 03:07:08.459 --> 03:07:11.100 just read it, but I might as well just reinforce 03:07:11.100 --> 03:07:16.379 that. Number five, ethical red flags. The following 03:07:16.379 --> 03:07:20.510 may be red flags that you might see. sometimes 03:07:20.510 --> 03:07:24.309 correcting it by sending it a screenshot like 03:07:24.309 --> 03:07:30.969 it's saying, quote, iOS 26 isn't out yet, VoiceOver 03:07:30.969 --> 03:07:35.010 is reading it wrong, to, here's a screenshot 03:07:35.010 --> 03:07:39.670 from settings, general, iOS update, and let it 03:07:39.670 --> 03:07:47.989 correct itself. Here are the red flags listed 03:07:47.989 --> 03:07:54.069 below. And I think it might be easier if we did 03:07:54.069 --> 03:07:57.430 this all at once. I know there are a few, but 03:07:57.430 --> 03:08:01.530 that would be my preference. There are five of 03:08:01.530 --> 03:08:04.450 them. And since I'm reading from the older copy, 03:08:04.649 --> 03:08:07.569 I already know about the quoting problems. But 03:08:07.569 --> 03:08:12.510 go ahead. There's not a quoting problem. I was 03:08:12.510 --> 03:08:16.549 just saying it. No, I'm saying mine still has 03:08:16.549 --> 03:08:20.370 that issue. I've never updated mine. Oh, okay. 03:08:21.350 --> 03:08:26.350 I never updated mine. So yes, let's do this one 03:08:26.350 --> 03:08:33.430 at a time. I think I agree. Okay. One. The AI 03:08:33.430 --> 03:08:46.059 said it was fine. Agree? Disagree? Um... Agree 03:08:46.059 --> 03:08:49.500 that that could potentially happen to you because 03:08:49.500 --> 03:08:52.520 all you're doing is maybe giving it something 03:08:52.520 --> 03:08:56.299 and if it doesn't correct itself, that could 03:08:56.299 --> 03:09:00.340 happen. It could misread the product too or whatever 03:09:00.340 --> 03:09:06.079 you're trying to do as well. Yeah, that could 03:09:06.079 --> 03:09:09.180 be a bad factor. Especially if you take the picture 03:09:09.180 --> 03:09:15.739 of it. When I was giving it the stuff for its 03:09:15.739 --> 03:09:19.219 own app, and I was saying, I'm running iOS 26, 03:09:19.219 --> 03:09:22.719 and it goes, no, VoiceOver is reading it wrong. 03:09:22.819 --> 03:09:25.520 You must be reading, you must be running 16. 03:09:29.620 --> 03:09:35.760 That's when I said, fuck you. And I went in, 03:09:35.840 --> 03:09:39.280 and I gave it a screenshot, and I said, here. 03:09:41.260 --> 03:09:46.059 And it goes, oh, you're right. According to this 03:09:46.059 --> 03:09:50.319 screenshot, it says, thank you for correcting 03:09:50.319 --> 03:09:57.940 me. This is proof. And it's always done that 03:09:57.940 --> 03:10:01.280 when I've had to correct it and given it a screenshot 03:10:01.280 --> 03:10:06.979 somewhere. And it goes and does what it needs 03:10:06.979 --> 03:10:10.930 to do and goes, oh. You know, like when I said 03:10:10.930 --> 03:10:14.629 one thing and it analyzes it one way and then 03:10:14.629 --> 03:10:19.409 I give it more info based on what it's saying. 03:10:19.450 --> 03:10:21.870 And I'm like, no, that's not quite right. And 03:10:21.870 --> 03:10:34.110 I give it something else that goes, oh. So, that's 03:10:34.110 --> 03:10:38.850 where that iOS 26 reference came from. Gotcha. 03:10:43.450 --> 03:10:52.489 What do you think on item number one? Yeah. I 03:10:52.489 --> 03:10:57.629 would say I agree as well. Yeah. Definitely. 03:10:58.129 --> 03:11:01.549 Because it needs to be more specific. It does. 03:11:04.129 --> 03:11:07.129 It's always specific when you tell it, hey, this 03:11:07.129 --> 03:11:12.620 is what. Again, accountability. You don't say 03:11:12.620 --> 03:11:16.379 what you want to say. You don't give it what 03:11:16.379 --> 03:11:17.879 you want. You're not going to get the right result. 03:11:18.879 --> 03:11:21.760 I had something much less serious happen that 03:11:21.760 --> 03:11:25.559 was kind of a red flag like that too. Go ahead. 03:11:26.120 --> 03:11:32.340 I was just chatting with my device, the premium, 03:11:32.440 --> 03:11:35.940 the plus feature, and I was just randomly talking 03:11:35.940 --> 03:11:41.389 to it about... stanford football and granted 03:11:41.389 --> 03:11:43.909 this is something that can be verified that can 03:11:43.909 --> 03:11:47.750 be researched that can be looked up online and 03:11:47.750 --> 03:11:52.469 it tells me stanford finished the 25 season with 03:11:52.469 --> 03:11:55.709 a record of three and nine and i know for a fact 03:11:55.709 --> 03:11:57.969 it was four and eight so i told it no actually 03:11:57.969 --> 03:12:01.290 no that we went four and eight last season and 03:12:01.290 --> 03:12:05.170 basically it responded the same way that Yours 03:12:05.170 --> 03:12:07.110 did with the thank you for correcting me because 03:12:07.110 --> 03:12:11.629 I'm sure that it could look up stuff from the 03:12:11.629 --> 03:12:16.969 website. Or you could tell it. Please verify 03:12:16.969 --> 03:12:25.229 that. And then it will go out and check sources 03:12:25.229 --> 03:12:29.530 and do. Right. So that's another prompt you can 03:12:29.530 --> 03:12:35.379 use. So if you know that for a fact... you can 03:12:35.379 --> 03:12:42.780 use that or tell it, are you sure? Go and check. 03:12:43.899 --> 03:12:52.459 And then it will... Yeah. But yeah, it gave me 03:12:52.459 --> 03:12:55.819 information I knew was incorrect. It self -corrected 03:12:55.819 --> 03:12:59.920 when I told it. But yes, good to know. But that 03:12:59.920 --> 03:13:11.059 is... Acceptable behavior. Yeah. Great. Item 03:13:11.059 --> 03:13:18.879 number two. Okay, number two. No disclosure of 03:13:18.879 --> 03:13:27.760 AI use. Why do you think I put... And I'm going 03:13:27.760 --> 03:13:31.739 to have to do this in every note. Every show 03:13:31.739 --> 03:13:36.700 notes now that I used the tool to assist in the 03:13:36.700 --> 03:13:41.260 writing. Because that's just proper etiquette. 03:13:42.440 --> 03:13:48.600 I used it to assist. Not as the official word. 03:13:49.860 --> 03:13:55.700 I could take what it says. I could rewrite it 03:13:55.700 --> 03:13:59.829 in my own words. Run it through for spell check 03:13:59.829 --> 03:14:06.889 and accuracy? Yep. And clarification? But overall, 03:14:06.989 --> 03:14:14.450 it has to be mine. It cannot just be it, i .e. 03:14:14.510 --> 03:14:17.469 the wrong notes. I cannot just read the wrong 03:14:17.469 --> 03:14:22.149 notes and call it mine. No, I mean, you could 03:14:22.149 --> 03:14:27.809 say this was... Written by, say, for example, 03:14:27.989 --> 03:14:33.010 link Ars Technica. You know, if you link back 03:14:33.010 --> 03:14:36.489 to the source you got it from. That's what we 03:14:36.489 --> 03:14:42.469 do legally. We legally should do that. Yeah, 03:14:42.489 --> 03:14:44.829 this was the prompt. This was what was generated 03:14:44.829 --> 03:14:50.530 when I gave it prompt X. Correct. Well, we don't 03:14:50.530 --> 03:14:53.569 have to be that detailed, but as long as we say... 03:14:53.950 --> 03:15:00.290 we used AI to assist in the writing, that should 03:15:00.290 --> 03:15:03.149 be good enough. Yeah, you can say, you know, 03:15:03.190 --> 03:15:13.170 an AI tool assisted and, yeah. Number three. 03:15:16.610 --> 03:15:21.950 Number three. Speed over understanding. Oh, yeah. 03:15:22.350 --> 03:15:32.959 Not... Does anybody have any examples of that? 03:15:34.520 --> 03:15:37.340 I might. I just wasn't clear about that, though. 03:15:43.440 --> 03:15:46.899 Basically, if you talk quick, you say, this is 03:15:46.899 --> 03:15:49.239 what I need, but yet it doesn't understand you, 03:15:49.319 --> 03:15:53.639 the AI. You should clarify. and it just spits 03:15:53.639 --> 03:15:55.579 something out, and it's like, okay, you did it, 03:15:55.799 --> 03:15:59.540 and you don't even get what it gave you, or even 03:15:59.540 --> 03:16:03.139 evaluate that what it gave you could be totally 03:16:03.139 --> 03:16:14.780 wrong. Not many examples recently. Sometimes 03:16:14.780 --> 03:16:17.239 I've used Seeing AI to try and identify these 03:16:17.239 --> 03:16:25.579 beer cans I have, and it's... I don't know that 03:16:25.579 --> 03:16:29.979 I've really gone super fast through them, so 03:16:29.979 --> 03:16:32.860 maybe it doesn't apply, but I do know that the 03:16:32.860 --> 03:16:36.559 initial read could be something that only captures 03:16:36.559 --> 03:16:43.219 a few characters, a few letters. And I'm wondering 03:16:43.219 --> 03:16:50.559 if you ended up... Well, you could do this. You 03:16:50.559 --> 03:16:58.819 could take a picture or two or three. Then let 03:16:58.819 --> 03:17:07.500 Camera Roll and Dropbox sync. Then use the web 03:17:07.500 --> 03:17:15.100 tool of ChatGPT or any other tool and say, what 03:17:15.100 --> 03:17:23.590 is this? And it, as I did with a bottle of vitamins, 03:17:23.670 --> 03:17:33.729 first it said, this is what this is. Then I said, 03:17:33.870 --> 03:17:38.969 can I take them? And it goes, I can't really 03:17:38.969 --> 03:17:44.389 tell you, but vitamins like this have an expiration 03:17:44.389 --> 03:17:53.120 date. And so I need, and so, because I can't 03:17:53.120 --> 03:17:58.600 read the small print, I shot three or four images, 03:17:58.719 --> 03:18:08.180 shoved it up its ass, and I didn't have to really 03:18:08.180 --> 03:18:11.899 put a prompt in, but then it goes, I see the 03:18:11.899 --> 03:18:19.340 images. I found the expiration date, and I won't 03:18:19.340 --> 03:18:22.239 tell you every word it said, but basically it 03:18:22.239 --> 03:18:25.379 told me, no, you should not take these, even 03:18:25.379 --> 03:18:32.579 though it may not technically be bad, but vitamins 03:18:32.579 --> 03:18:42.739 like this may not be safe because it loses its... 03:18:46.260 --> 03:18:50.319 I'm not giving every detail, but I'm giving an 03:18:50.319 --> 03:18:56.479 example of how you could handle that. I had the 03:18:56.479 --> 03:18:59.719 vending machine debacle with it. Remember, I 03:18:59.719 --> 03:19:03.319 was discussing that earlier and telling you guys 03:19:03.319 --> 03:19:09.180 that I gave it my address. It knows. It's like, 03:19:09.260 --> 03:19:14.100 oh, you must live at the Met. Now, technically, 03:19:14.180 --> 03:19:17.280 that's the name of the complex. That's public. 03:19:19.739 --> 03:19:23.120 So I'm not saying anything that's not public. 03:19:24.440 --> 03:19:27.600 It's called the Met Woodland Hills. That's a 03:19:27.600 --> 03:19:36.940 public name. Yep. So then I was telling it how 03:19:36.940 --> 03:19:40.440 I go to the various vending machines. and then 03:19:40.440 --> 03:19:43.739 how I get out of the complex to go get the bus. 03:19:45.520 --> 03:19:49.979 And it said, seeing that both of these are out 03:19:49.979 --> 03:19:55.979 of your way, your aide was not right, or not 03:19:55.979 --> 03:19:59.540 wrong, when he said, quote, fuck the machines. 03:20:01.139 --> 03:20:15.510 Yeah. Yep. Item number... Where's my device? 03:20:16.409 --> 03:20:20.489 Item number four. Number four. All right. Number 03:20:20.489 --> 03:20:28.450 four. Treating AI as neutral. Do you guys think... 03:20:28.450 --> 03:20:31.549 Now, I guess the question I'll ask you guys. 03:20:31.750 --> 03:20:35.750 Do you think I was neutral when I got sick? I 03:20:35.750 --> 03:20:39.889 gave it my symptoms and it was saying... Well, 03:20:39.930 --> 03:20:43.069 you don't really need to go to emergency care 03:20:43.069 --> 03:20:46.569 or a doctor yet, but this is what you should 03:20:46.569 --> 03:20:51.190 look for if this occurs. You could try this, 03:20:51.270 --> 03:20:54.110 you could try that, you could try these things 03:20:54.110 --> 03:21:00.889 and see if that doesn't help you. Well, I mean, 03:21:00.989 --> 03:21:03.030 at the end of the day, you definitely want to 03:21:03.030 --> 03:21:09.190 be transparent and honest with your... So I feel 03:21:09.190 --> 03:21:14.409 it giving you choices on what to do with your 03:21:14.409 --> 03:21:18.950 sickness is elaborate. Yeah, but the thing is, 03:21:18.989 --> 03:21:21.889 the only thing was, was Jared made the decision 03:21:21.889 --> 03:21:24.850 and said, okay, you know, this is what I'm going 03:21:24.850 --> 03:21:28.309 to do. You know, he didn't let the AI like, oh 03:21:28.309 --> 03:21:31.069 yeah, I'm going to do it. Like he made the decision 03:21:31.069 --> 03:21:35.500 ultimately. I gave it a whole bunch of crap that 03:21:35.500 --> 03:21:39.120 I had in my house and said, what can I eat? I 03:21:39.120 --> 03:21:42.360 have this. I have that. I have this. I have that. 03:21:42.399 --> 03:21:47.059 I have these options. And it goes, based on how 03:21:47.059 --> 03:21:54.639 you're feeling, my recommendation is, and it 03:21:54.639 --> 03:22:03.750 gave me in order, you know, eggs, rice. bread, 03:22:03.750 --> 03:22:13.909 the noodles, the yogurt if I have any, applesauce 03:22:13.909 --> 03:22:17.829 if I had any, bananas if I had any. But then 03:22:17.829 --> 03:22:20.110 when I told it, I don't have applesauce, I don't 03:22:20.110 --> 03:22:24.049 have yogurt, I don't have bananas. Then it goes, 03:22:24.270 --> 03:22:27.290 all right, you have eggs, you have this, you 03:22:27.290 --> 03:22:34.569 have that. Try these. And report back in a little 03:22:34.569 --> 03:22:43.250 while, and let's assess. Right. And so, in a 03:22:43.250 --> 03:22:55.809 way, it was my doctor with me making my own decisions. 03:22:58.590 --> 03:23:01.639 Right, and it was... And I would say not neutral 03:23:01.639 --> 03:23:07.360 because it's basically responding based on what 03:23:07.360 --> 03:23:10.239 you're putting into it, and that could be very 03:23:10.239 --> 03:23:15.659 subjective and very different. But I eventually 03:23:15.659 --> 03:23:26.139 made my own choice. Right. Right? So it was more 03:23:26.139 --> 03:23:30.090 of a tool. If I didn't give it any more information 03:23:30.090 --> 03:23:34.010 than what I started with, that would have been 03:23:34.010 --> 03:23:38.190 the neutral aspect. But I knew I needed help, 03:23:38.309 --> 03:23:47.010 and I chose, and I think that should be the most 03:23:47.010 --> 03:23:49.670 important thing we take out of this, right? I 03:23:49.670 --> 03:23:54.069 chose, instead of it saying, well, you should 03:23:54.069 --> 03:24:01.950 eat any of these, and I left it alone, that's 03:24:01.950 --> 03:24:07.110 where it would have been neutral. But I knew 03:24:07.110 --> 03:24:13.129 that there were things I did not have. So, yes, 03:24:13.229 --> 03:24:18.969 it was neutral by saying, okay, since you don't 03:24:18.969 --> 03:24:24.030 have these, then here's what I would suggest. 03:24:26.229 --> 03:24:35.530 It gave me suggestions. I shot it pictures. Okay, 03:24:35.590 --> 03:24:39.750 I want the noodles. I have this and I have that. 03:24:40.969 --> 03:24:46.190 Then it goes, well, I wouldn't necessarily eat 03:24:46.190 --> 03:24:51.149 this. This probably would be okay. It didn't 03:24:51.149 --> 03:24:56.379 say this is okay. or this is what I think you 03:24:56.379 --> 03:25:00.020 should do, but it knows, based on the packaging 03:25:00.020 --> 03:25:05.959 and the image, what's in it, how it's cooked, 03:25:06.159 --> 03:25:12.340 and what might cause me problems. It doesn't 03:25:12.340 --> 03:25:16.420 know that it's factual, but it says, I think 03:25:16.420 --> 03:25:19.620 you're better off, or you're probably better 03:25:19.620 --> 03:25:28.180 off with this. So I ate that and had no problems. 03:25:28.239 --> 03:25:32.200 And I put the other one away. But that was my 03:25:32.200 --> 03:25:36.920 own decision based on shoving images up its ass, 03:25:37.059 --> 03:25:40.920 letting it analyze it, telling it what I have 03:25:40.920 --> 03:25:48.600 in my home, and doing all of that. But again, 03:25:48.739 --> 03:25:52.540 that's all going back to accountability and responsibility. 03:25:53.659 --> 03:25:59.340 Which leads directly to item number five. No 03:25:59.340 --> 03:26:01.760 human accountability. Read that, please. Exactly. 03:26:01.760 --> 03:26:04.520 No human accountability, which is item number 03:26:04.520 --> 03:26:07.620 five. All right. I will go ahead and do that 03:26:07.620 --> 03:26:11.000 again. Number five. No human accountability. 03:26:12.120 --> 03:26:18.850 Nope. So was I accountable based on... this whole 03:26:18.850 --> 03:26:23.229 section of me getting sick telling it what i 03:26:23.229 --> 03:26:29.309 had updating it writing a symptom log it understanding 03:26:29.309 --> 03:26:32.129 oh you're going backwards a little bit but you're 03:26:32.129 --> 03:26:35.729 not in danger right now you did something that 03:26:35.729 --> 03:26:39.350 maybe you shouldn't have done and your body's 03:26:39.350 --> 03:26:42.989 not liking that so much here's what to do next 03:26:45.450 --> 03:26:48.270 And I did exactly what it recommended because 03:26:48.270 --> 03:26:54.530 I knew that I fucked up. The thing is, you were 03:26:54.530 --> 03:26:56.770 actually using it for good. You weren't shooting 03:26:56.770 --> 03:27:05.309 it like pictures of whatever. You weren't using 03:27:05.309 --> 03:27:10.530 it maliciously. No, I mean, that would not be 03:27:10.530 --> 03:27:14.120 a bad... that would not be a good thing if you 03:27:14.120 --> 03:27:20.299 use it if you do use it what Terry said maliciously 03:27:20.299 --> 03:27:32.700 please read the paragraphs Mr. J okay here's 03:27:32.700 --> 03:27:37.200 something to remember yes here's something to 03:27:37.200 --> 03:27:41.409 remember I just I got that When everyone blames 03:27:41.409 --> 03:27:46.489 the AI, nobody is responsible. Read that again. 03:27:47.750 --> 03:27:52.170 I think that's important. Absolutely. When everyone 03:27:52.170 --> 03:27:59.950 blames the AI, nobody is responsible. It's easy 03:27:59.950 --> 03:28:02.610 to blame the AI when you make a bad decision. 03:28:02.950 --> 03:28:05.250 It's like, oh, the AI told me to do this. Chat 03:28:05.250 --> 03:28:10.540 GPT told me to eat this. Yeah. I saw this on 03:28:10.540 --> 03:28:19.319 TickBite. Dan's talk thing. But you had to make 03:28:19.319 --> 03:28:22.579 the final call, not it. It was showing it to 03:28:22.579 --> 03:28:26.120 you, making suggestions, but you were the one 03:28:26.120 --> 03:28:31.959 who ultimately made the call. Yep. Exactly. Exactly. 03:28:33.559 --> 03:28:40.930 Again, accountability. Yes. Please read the question 03:28:40.930 --> 03:28:44.409 in the final paragraph of the section, Mr. J. 03:28:46.149 --> 03:28:50.110 Which of these red flags listed above have you 03:28:50.110 --> 03:28:59.030 encountered the most? Hmm. Now that's a tough 03:28:59.030 --> 03:29:04.309 one because... Yeah. Yeah. Yeah, I'm trying to 03:29:04.309 --> 03:29:09.090 think which one I've really run into. I'm still 03:29:09.090 --> 03:29:12.950 too new. I know I've corrected it, but I've tried 03:29:12.950 --> 03:29:17.430 to be responsible with it. I mean, I tried to 03:29:17.430 --> 03:29:20.770 correct it just recently on stuff, but that's 03:29:20.770 --> 03:29:28.489 it. You know, it's not like I gave it wrong information. 03:29:28.629 --> 03:29:32.250 And I think, in my opinion, it was neutral. It's 03:29:32.250 --> 03:29:35.709 like, based on what your history is at the moment, 03:29:35.909 --> 03:29:42.979 Yeah. I recommend these things in this order, 03:29:43.219 --> 03:29:47.559 in any of this order. And then I'd say, all right, 03:29:47.579 --> 03:29:59.120 I'm going to try whatever. Yeah. And it would 03:29:59.120 --> 03:30:03.440 say, that might not be a bad idea. Do this and 03:30:03.440 --> 03:30:06.799 report back and let me know how it goes. And 03:30:06.799 --> 03:30:27.809 let's analyze it. Yep. Right. So, do you think 03:30:27.809 --> 03:30:40.440 I have used it responsibly? Based on this section? 03:30:42.639 --> 03:30:53.600 I think you have. I mean, my concern is... And 03:30:53.600 --> 03:30:55.620 not that you did anything wrong. I don't think 03:30:55.620 --> 03:30:57.639 there's anything right or wrong here. But I think 03:30:57.639 --> 03:31:02.959 it gets a little dicey, in my view, when you 03:31:02.959 --> 03:31:05.479 start getting into things that are medical. And 03:31:05.479 --> 03:31:08.969 I mean, yeah, okay. It wasn't... the worst thing 03:31:08.969 --> 03:31:12.569 that could have happened to you. And yeah, it 03:31:12.569 --> 03:31:16.409 gave some concrete things based on what you shoved 03:31:16.409 --> 03:31:20.889 up its ass, as you say. Yeah. But I'm always 03:31:20.889 --> 03:31:23.270 a little uneasy with that kind of thing in AI. 03:31:23.590 --> 03:31:28.409 But remember, there's one thing that you have 03:31:28.409 --> 03:31:32.909 to keep in mind in regards to your angle. And 03:31:32.909 --> 03:31:35.569 I'm not saying you're wrong. I'm listening to 03:31:35.569 --> 03:31:41.079 you. Okay. I'm not giving it my medical history. 03:31:41.379 --> 03:31:47.260 I'm saying... Oh, no. This is how I'm feeling 03:31:47.260 --> 03:31:54.239 right now. I'm burping acid. I've got diarrhea. 03:31:55.219 --> 03:32:00.979 And what... Do I need... Should I be concerned 03:32:00.979 --> 03:32:06.569 about this? Or should I go get medical care? 03:32:08.350 --> 03:32:15.750 Right. And it goes, well, this doesn't sound 03:32:15.750 --> 03:32:21.590 bad, but you might have a bit of acid reflux. 03:32:21.649 --> 03:32:25.770 And then I told it that I had the burger the 03:32:25.770 --> 03:32:30.829 day before. But I didn't blame the burger because 03:32:30.829 --> 03:32:34.190 it started the next day. And I had been stressed. 03:32:35.329 --> 03:32:37.969 And, I mean, there were a lot of things that 03:32:37.969 --> 03:32:41.209 could have caused it. Right. And then it says 03:32:41.209 --> 03:32:46.549 there is a thing called stress diarrhea, which 03:32:46.549 --> 03:32:50.370 I've never heard of. I've never heard of it either. 03:32:50.729 --> 03:32:57.250 That would be an example. Go ahead. That's what 03:32:57.250 --> 03:33:08.149 I used it for. I never gave it my chart, which 03:33:08.149 --> 03:33:13.690 includes my whole medical history. You know, 03:33:16.049 --> 03:33:23.190 I didn't give it pictures of different things, 03:33:23.229 --> 03:33:28.340 except... To identify what was in my home. Right. 03:33:29.319 --> 03:33:31.579 It's not like you took a picture of your diarrhea 03:33:31.579 --> 03:33:34.059 crap and uploaded it and said, oh, you know what? 03:33:34.340 --> 03:33:39.520 No, I think I would never do that. No, no, no. 03:33:40.520 --> 03:33:44.540 Could you imagine the analyze the chat GPT you 03:33:44.540 --> 03:33:48.139 would get? Some people. I think some people actually 03:33:48.139 --> 03:33:49.979 would, though, Terry. That's the scary part. 03:33:50.120 --> 03:33:53.459 That's the scary part. Yeah, I mean. I mean, 03:33:53.459 --> 03:33:56.899 like I said, the worst I've done with chat GPT 03:33:56.899 --> 03:34:00.459 is upload my medical cannabis card. And it said, 03:34:00.600 --> 03:34:04.200 this gave me everything. And it said, you know, 03:34:04.219 --> 03:34:07.360 just to give you some advice, this is sensitive 03:34:07.360 --> 03:34:09.479 information. So, you know, please either delete 03:34:09.479 --> 03:34:13.780 the picture or when we're done. But that's the 03:34:13.780 --> 03:34:16.479 guardrail to protect you. That's the guardrail. 03:34:16.579 --> 03:34:21.680 Yeah. Right. Yeah. But no, what you said, though. 03:34:22.700 --> 03:34:26.600 That's a key distinction, so thanks for clarifying 03:34:26.600 --> 03:34:28.579 that. Because, yes, you are presenting it with 03:34:28.579 --> 03:34:33.620 basically a list of symptoms right now and not 03:34:33.620 --> 03:34:36.219 what I was saying. So, no, that's perfect. Thanks. 03:34:37.719 --> 03:34:42.719 But go ahead with your analysis. I want to hear. 03:34:42.920 --> 03:34:46.280 I mean, we talked about it last night when I 03:34:46.280 --> 03:34:49.899 called you, but I think it's worth bringing up. 03:34:51.079 --> 03:35:00.899 Yeah. So, given that the first impulse is for 03:35:00.899 --> 03:35:02.719 a lot of people, and I'm not just saying yourself, 03:35:02.979 --> 03:35:05.940 but a lot of people, to go to quote -unquote 03:35:05.940 --> 03:35:12.979 Dr. Google slash Dr. AI. Dr. Google, Dr. DuckDuckGo. 03:35:14.159 --> 03:35:19.879 Yes, Dr. DuckDuckGo. Maybe this is more of a 03:35:19.879 --> 03:35:23.959 personal opinion, but I just feel a little unsure 03:35:23.959 --> 03:35:30.059 about presenting that kind of stuff to GPT, even 03:35:30.059 --> 03:35:33.319 if all you're doing is giving it a list of symptoms. 03:35:33.899 --> 03:35:37.100 I guess I'm more comfortable with doing stuff 03:35:37.100 --> 03:35:41.340 that's really easily, quickly verifiable, i .e. 03:35:41.340 --> 03:35:43.600 what was the baseball score for this? What's 03:35:43.600 --> 03:35:49.290 the current temperature of X? Well, your main 03:35:49.290 --> 03:35:55.149 devices can do that. Exactly. Well, Jared, you 03:35:55.149 --> 03:35:57.229 got to remember, not everybody's comfortable 03:35:57.229 --> 03:36:00.690 with giving AI that type of information either. 03:36:00.850 --> 03:36:03.590 I mean, they may want to just say, all right, 03:36:03.670 --> 03:36:06.209 I want to seek a medical professional just in 03:36:06.209 --> 03:36:09.790 case versus... Well, remember that this started 03:36:09.790 --> 03:36:12.209 over the weekend and I wasn't getting a medical 03:36:12.209 --> 03:36:15.309 professional till Monday. Well, I know, right? 03:36:15.809 --> 03:36:19.860 I'm saying... In general, most people may want 03:36:19.860 --> 03:36:23.280 to just do that instead, which it's a decision 03:36:23.280 --> 03:36:29.899 that you want to make. I'm not discounting that. 03:36:30.260 --> 03:36:33.440 You also didn't sit there and be like, oh yeah, 03:36:33.559 --> 03:36:39.159 you took the suggestion and you made a decision 03:36:39.159 --> 03:36:46.219 based on the suggestion. It started on a Friday 03:36:46.219 --> 03:36:49.180 morning at like 2 o 'clock in the morning. Well, 03:36:49.200 --> 03:36:51.100 that doesn't matter when it started. It just, 03:36:51.239 --> 03:36:54.479 what matters is I'm just giving a baseline. I'm 03:36:54.479 --> 03:37:00.459 not discounting you. You know, that's what matters 03:37:00.459 --> 03:37:15.200 is how you handle it. And both of you are absolutely 03:37:15.200 --> 03:37:22.440 right. And that's why there's choice. Yes. And 03:37:22.440 --> 03:37:28.540 I mean, I don't mind... Sorry. I don't mind talking 03:37:28.540 --> 03:37:34.040 to my device. Yeah, I'll go. Like, I don't mind 03:37:34.040 --> 03:37:37.739 talking to my device, as I have, about, you know, 03:37:37.739 --> 03:37:40.920 some of the various things that I was drinking. 03:37:40.979 --> 03:37:44.959 Because sometimes... If the print is too small 03:37:44.959 --> 03:37:48.479 and the images I'm getting are not great, but 03:37:48.479 --> 03:37:51.239 I have a pretty good idea of what it is, sometimes 03:37:51.239 --> 03:37:54.200 it'll fill in the complete picture. Like, it's 03:37:54.200 --> 03:37:58.620 this. I'm totally fine with that. Stuff that's 03:37:58.620 --> 03:38:03.760 not going to really be that significant down 03:38:03.760 --> 03:38:05.819 the road. And yeah, I like to sometimes have 03:38:05.819 --> 03:38:10.399 as I was on my device, which is... A little borderline, 03:38:10.440 --> 03:38:15.120 like, I like to mess with... I like to mess with 03:38:15.120 --> 03:38:19.920 it. Like, we actually created... This was totally 03:38:19.920 --> 03:38:25.540 fictional. An anti -resume. It was the funniest 03:38:25.540 --> 03:38:28.860 thing. Like, find the opposite of every quality 03:38:28.860 --> 03:38:31.840 and every buzzword that every hiring manager 03:38:31.840 --> 03:38:35.360 has to read. So, yeah, this person. Combative. 03:38:35.739 --> 03:38:42.350 Combative. Failure -oriented. Inattentive. Oh, 03:38:42.450 --> 03:38:47.350 my. Oh, yeah. It was funny. And it was going 03:38:47.350 --> 03:38:51.670 along with it. But the point is, it wasn't about 03:38:51.670 --> 03:38:55.110 anything serious or anything that would have 03:38:55.110 --> 03:39:03.290 really affected me later on. Okay. Preston, go 03:39:03.290 --> 03:39:09.149 ahead, please. And I'll read item six. Well, 03:39:09.250 --> 03:39:13.209 I mean, in my opinion, it's always good to have 03:39:13.209 --> 03:39:17.469 choice, but you definitely don't want to be abusive 03:39:17.469 --> 03:39:21.030 of what you have. So I think, you know, as we 03:39:21.030 --> 03:39:26.030 said here, being accountable and reasonable with 03:39:26.030 --> 03:39:32.350 our AI tools will be beneficial for us in the 03:39:32.350 --> 03:39:39.110 long run. I guess maybe in another podcast we'll 03:39:39.110 --> 03:39:46.670 go through initial settings on chat GPT where 03:39:46.670 --> 03:39:51.430 in the settings I forget where I'd have to go 03:39:51.430 --> 03:39:55.870 in the app and look but there is an option in 03:39:55.870 --> 03:40:06.000 there to use your data to train their models. 03:40:08.100 --> 03:40:11.079 One of the first things I did before I went on 03:40:11.079 --> 03:40:13.899 these diatribes about the landscape of where 03:40:13.899 --> 03:40:21.020 I live and all of Metro's stuff that I had to 03:40:21.020 --> 03:40:24.200 do because I have not logged since September. 03:40:25.219 --> 03:40:29.379 That's not good. Even though I've taken trips. 03:40:32.559 --> 03:40:41.840 no way so I shoved it logs made it understand 03:40:41.840 --> 03:40:48.219 how Metro works how I have to send things through 03:40:48.219 --> 03:40:51.799 customer relations not the accessibility unit 03:40:51.799 --> 03:40:57.399 I talked about the advisory body compensation 03:40:57.399 --> 03:41:06.899 program and how I had issues and how to deal 03:41:06.899 --> 03:41:14.120 with it in the future. I've talked about and 03:41:14.120 --> 03:41:18.379 gave it an email as I indicated that I wrote 03:41:18.379 --> 03:41:29.979 to staff on this particular day. And that turned 03:41:29.979 --> 03:41:33.750 into the reminder. When I said, you know, talk 03:41:33.750 --> 03:41:36.909 to Armando, and Armando's a common name, so I'm 03:41:36.909 --> 03:41:42.489 not, you know, if he's hearing it, understand 03:41:42.489 --> 03:41:46.569 that it's a reference, not that I need anything 03:41:46.569 --> 03:41:51.889 right now. We can talk. I'm not, this isn't about 03:41:51.889 --> 03:41:55.889 how come you haven't responded lately. That's 03:41:55.889 --> 03:41:58.110 not the point of the discussion. The discussion 03:41:58.110 --> 03:42:02.079 was... What reminder systems are you talking 03:42:02.079 --> 03:42:06.299 about? And how are you using it? So that's what 03:42:06.299 --> 03:42:10.579 that was about. But the point is, it helped me 03:42:10.579 --> 03:42:14.420 rewrite the email I wrote, even though he would 03:42:14.420 --> 03:42:18.559 have understood it just fine, having a professional 03:42:18.559 --> 03:42:24.520 something else. Right. And I fed it 200 pages 03:42:24.520 --> 03:42:37.030 of logs. But the point being that I'm sure that 03:42:37.030 --> 03:42:38.930 one of the very first things you did was turn 03:42:38.930 --> 03:42:42.090 off that setting that would have allowed it to 03:42:42.090 --> 03:42:50.530 train on its models. Now, is that a good decision 03:42:50.530 --> 03:42:55.870 or a bad decision? I'm curious. Great decision. 03:43:00.459 --> 03:43:03.159 It said the same thing. It said, based on what 03:43:03.159 --> 03:43:06.559 you're telling me so far, turning it off is the 03:43:06.559 --> 03:43:10.739 right decision. Not that they would misuse it 03:43:10.739 --> 03:43:14.639 anyway, because they have the right to read logs 03:43:14.639 --> 03:43:21.299 to make sure there's no abuse. Right. But this 03:43:21.299 --> 03:43:27.639 is something that's more personal. It's something 03:43:27.639 --> 03:43:33.530 that's more personal. And you just don't necessarily 03:43:33.530 --> 03:43:38.049 know how much of that is being fed into the larger 03:43:38.049 --> 03:43:43.729 language model. The logs aren't the concerning 03:43:43.729 --> 03:43:46.629 aspect of things, because all it does is say, 03:43:46.729 --> 03:43:50.629 took a bus from this place to that place, i .e. 03:43:52.670 --> 03:43:58.989 Ventura and Burbank to Cadoga Station. at this 03:43:58.989 --> 03:44:06.209 time. There's no real, you know, personally identifiable 03:44:06.209 --> 03:44:11.129 information that the models could care about. 03:44:12.049 --> 03:44:23.950 Oh, okay. The logs indicate how, you know, what 03:44:23.950 --> 03:44:29.629 time my board Where I start from, any accessibility 03:44:29.629 --> 03:44:37.569 issues, that is public knowledge because Metro 03:44:37.569 --> 03:44:40.649 gets that in certain situations where there's 03:44:40.649 --> 03:44:44.950 an accessibility failure or something's just 03:44:44.950 --> 03:44:48.229 not right. Like, the train was overly packed 03:44:48.229 --> 03:44:54.610 and I almost got thrown out the door. You stupid 03:44:54.610 --> 03:45:03.440 fucks. So I don't care if it wants to train on 03:45:03.440 --> 03:45:08.139 that, but because I talked to it about internal 03:45:08.139 --> 03:45:13.940 workings of a big -name company, which you guys 03:45:13.940 --> 03:45:22.500 already know, Metro, that's when I turned the 03:45:22.500 --> 03:45:26.809 thing off. That's kind of what I meant when I 03:45:26.809 --> 03:45:29.069 said personal. That's sort of what it extended 03:45:29.069 --> 03:45:36.030 to. That's what I meant there. I see. And you're 03:45:36.030 --> 03:45:40.809 absolutely correct. Anybody else? Yes or no on 03:45:40.809 --> 03:45:46.049 turning that option off? Well, I would say I 03:45:46.049 --> 03:45:51.639 think off is good because... That way it won't 03:45:51.639 --> 03:45:54.520 know what you're talking about because sometimes 03:45:54.520 --> 03:45:57.700 in any line of work... Actually, that's not exactly 03:45:57.700 --> 03:46:01.700 true. That's not exactly true, but I'll let you 03:46:01.700 --> 03:46:08.459 finish your thought. I think... Well, I think 03:46:08.459 --> 03:46:11.799 it depends on the line of work. Things can get 03:46:11.799 --> 03:46:20.940 a little too confidential or... They need to 03:46:20.940 --> 03:46:27.879 be as commentable as it could be. So I think 03:46:27.879 --> 03:46:36.840 having that off can be a benefit. And the only 03:46:36.840 --> 03:46:39.680 reason why I said it's not true is because there's 03:46:39.680 --> 03:46:42.700 another setting in there in the same area that 03:46:42.700 --> 03:46:49.389 says access my chat history for reference. Now 03:46:49.389 --> 03:46:51.329 I'm paraphrasing. I don't remember the options 03:46:51.329 --> 03:47:01.870 offhand. And I left that on. Yes. So if I start 03:47:01.870 --> 03:47:05.090 a new chat and I say, remember in my chat history 03:47:05.090 --> 03:47:12.670 I talked about program 267? Well, there was a 03:47:12.670 --> 03:47:19.200 question about item 3 in this. Can you write 03:47:19.200 --> 03:47:29.719 a summary that we can read on air for Podcast 03:47:29.719 --> 03:47:38.579 269? And it could go back in the history and 03:47:38.579 --> 03:47:46.040 go find it. Or if it's not sure, it'll say, please 03:47:46.040 --> 03:47:50.440 tell me what that item is. And then I'll be able 03:47:50.440 --> 03:47:54.139 to help you more. Sure. Be My AI is under Be 03:47:54.139 --> 03:47:56.360 My Eyes too, correct? Or is that a different... 03:47:56.360 --> 03:48:00.600 That is under Be My Eyes. It's under the AI tab. 03:48:01.239 --> 03:48:04.819 That's what I thought. So I knew I had them all. 03:48:04.879 --> 03:48:06.440 I just had to make sure. I had to put them all 03:48:06.440 --> 03:48:12.000 in my AIs folder. That's what I was asking. It's... 03:48:12.000 --> 03:48:16.559 Yeah. Well, I wouldn't put Be My... I wouldn't 03:48:16.559 --> 03:48:20.680 put... I would personally not put Be My Eyes 03:48:20.680 --> 03:48:23.840 There. That's a blindness -specific app. The 03:48:23.840 --> 03:48:28.180 AI tool's part of the tool set they offer. Yeah. 03:48:30.479 --> 03:48:42.319 That's just me. Is there any other comments on 03:48:42.319 --> 03:48:46.120 item number five before we get into six and seven? 03:48:50.280 --> 03:49:03.719 I think so. We're good. Item number six. Audience 03:49:03.719 --> 03:49:11.090 comment section. And this starts as a quote, 03:49:11.209 --> 03:49:13.809 and I probably could have taken the quote out, 03:49:13.909 --> 03:49:20.190 but I didn't. Now that we've laid out how we're 03:49:20.190 --> 03:49:23.649 thinking about AI best practices, let's hear 03:49:23.649 --> 03:49:27.549 from you. Here are some questions that you can 03:49:27.549 --> 03:49:32.049 answer. Email, iMessage, or call the comment 03:49:32.049 --> 03:49:37.090 line. There's no single right response here. 03:49:37.719 --> 03:49:46.540 So call 888 -405 -7524, email or iMessage tech, 03:49:46.719 --> 03:49:54.799 that's T -E -C -H at M -E -N -V -I .org, or J 03:49:54.799 --> 03:49:58.360 -A -R -E -D -R -I -M -E -R at 986themix .com. 03:49:58.600 --> 03:50:05.000 Text or WhatsApp 804 -442 -6975. And I will read 03:50:05.000 --> 03:50:09.469 these one at a time. And panelists, if you would 03:50:09.469 --> 03:50:16.809 like to answer, you are welcome to. Okay? Okay. 03:50:18.590 --> 03:50:24.110 Where have you seen AI used well? Who wants to 03:50:24.110 --> 03:50:30.870 go first? I would say I've seen it used well 03:50:30.870 --> 03:50:36.440 when I listen to... various friends in the community 03:50:36.440 --> 03:50:44.459 perform uh song selections in like suno or ai 03:50:44.459 --> 03:50:48.200 music and i do know when i do go out and about 03:50:48.200 --> 03:50:53.040 i would ask my smart glasses about my surroundings 03:50:53.040 --> 03:50:56.299 and you know i tell it to make sure it's very 03:50:56.299 --> 03:51:07.149 descriptive because of my uh spectrum uh So I 03:51:07.149 --> 03:51:12.010 always turn that description on. I was actually 03:51:12.010 --> 03:51:13.909 going to somewhat echo that. I've seen it used 03:51:13.909 --> 03:51:21.229 really well in terms of tools such as Be My AI. 03:51:21.469 --> 03:51:25.829 So yes, blindness specific, but the fact that 03:51:25.829 --> 03:51:31.229 it can provide pictures of photos slash providing 03:51:31.229 --> 03:51:34.370 information from those photos that you may need, 03:51:34.799 --> 03:51:38.639 That's when it's excellent, I feel. I mean, I've 03:51:38.639 --> 03:51:45.780 heard AI in music, like a couple AI tracks, and 03:51:45.780 --> 03:51:48.219 sometimes you wouldn't even know the difference. 03:51:50.420 --> 03:51:54.579 That gets you into a... That's getting... Well, 03:51:54.579 --> 03:51:57.280 the problem, and we talked about this on program 03:51:57.280 --> 03:52:02.059 402 of the Independent Artist Spotlight, where 03:52:02.059 --> 03:52:07.870 we brought... our very own Jamie T on. Yes. And 03:52:07.870 --> 03:52:15.549 AI is only as good as it's fed. So right now, 03:52:15.549 --> 03:52:22.649 it's basing music off of what it knows. The musicians 03:52:22.649 --> 03:52:29.270 who are crying foul saying that it's taking our 03:52:29.270 --> 03:52:34.840 jobs away are wrong. You have to innovate or 03:52:34.840 --> 03:52:41.860 you'll die. Exactly. If you can't do that, I'm 03:52:41.860 --> 03:52:44.059 not saying dying doesn't mean you're dead. I 03:52:44.059 --> 03:52:46.620 mean, you're just going to not exist as a musician 03:52:46.620 --> 03:52:49.420 anymore. So I want to make that very clear. Right. 03:52:49.459 --> 03:53:01.139 Right. Yeah. So, and Kim even said as much in 03:53:01.139 --> 03:53:07.719 her minutes. The musician has to innovate. AI 03:53:07.719 --> 03:53:10.799 only knows what it's taught. And it doesn't matter 03:53:10.799 --> 03:53:17.200 whether it's Suno or 11 Labs or any other application 03:53:17.200 --> 03:53:24.440 that can do that that's not named herein. Yeah. 03:53:28.579 --> 03:53:30.559 Yeah, and one of the ways you can innovate it, 03:53:30.600 --> 03:53:35.000 you can feed it. Well, yeah, create your own 03:53:35.000 --> 03:53:38.379 music, but also feed it different things so that 03:53:38.379 --> 03:53:40.379 it has even more to work with. You're not going 03:53:40.379 --> 03:53:45.239 to lose your job completely. No. In fact, one 03:53:45.239 --> 03:53:50.600 of the artists that I've been playing recently 03:53:50.600 --> 03:53:54.680 has uploaded their own AI versions of stuff to 03:53:54.680 --> 03:54:06.280 their own Bandcamp page for sale. Wow. Number 03:54:06.280 --> 03:54:16.360 two. Where did it clearly fail? I've seen it 03:54:16.360 --> 03:54:28.340 failing. And this is not something that can entirely 03:54:28.340 --> 03:54:32.379 be blamed on the AI at all. This is, I think, 03:54:32.420 --> 03:54:35.350 more about the person who's using it. I'm not 03:54:35.350 --> 03:54:39.709 going to name names, but what I've seen is despite 03:54:39.709 --> 03:54:43.209 the fact that they say they know that this is 03:54:43.209 --> 03:54:47.149 not real, that they are becoming so emotionally 03:54:47.149 --> 03:54:50.510 invested in characters who are fictional slash 03:54:50.510 --> 03:55:01.510 AI creations. What service? There are several 03:55:01.510 --> 03:55:06.809 that were mentioned. There was one called... 03:55:06.809 --> 03:55:12.170 I think it was called Spicy AI Chat. So I know 03:55:12.170 --> 03:55:14.409 that it's designed for this type of purpose, 03:55:14.530 --> 03:55:19.870 but it's still... It's... In a way, actually, 03:55:20.030 --> 03:55:22.309 I should probably save this for number three 03:55:22.309 --> 03:55:25.670 because it kind of ties into that question. Well, 03:55:25.690 --> 03:55:29.129 go ahead while you're thinking about it. Please. 03:55:30.430 --> 03:55:36.930 Okay. So... I mean, my concern is that we're 03:55:36.930 --> 03:55:40.569 going to see a lot more of this. Like people 03:55:40.569 --> 03:55:46.930 getting so tied into. And there was even that 03:55:46.930 --> 03:55:50.069 podcast we heard about these digital relationships 03:55:50.069 --> 03:55:55.229 that are completely fictitious and actually emotionally 03:55:55.229 --> 03:55:59.010 investing so much into them. So the fact that 03:55:59.010 --> 03:56:04.920 that is out there is just. And again, not totally 03:56:04.920 --> 03:56:09.360 the AI's fault. Not at all. It's, you know, more 03:56:09.360 --> 03:56:10.899 about who's using it, but the fact that that 03:56:10.899 --> 03:56:13.899 exists tells me that it... Oh, character AI is 03:56:13.899 --> 03:56:21.079 another one, Nick, that is used. Oh, yeah. Oh, 03:56:21.239 --> 03:56:26.040 crap. This thing just went backwards again. We're 03:56:26.040 --> 03:56:35.200 almost done, I think. Yeah, actually, I got you, 03:56:35.239 --> 03:56:42.700 Jared. Okay. Oh, I found it. Go ahead and... 03:56:42.700 --> 03:56:47.100 Oh, so number three. What worries you most about 03:56:47.100 --> 03:56:54.799 current AI use? And Nick touched on one item. 03:56:56.299 --> 03:57:02.969 Does anybody... So... So we'll just recap this. 03:57:03.069 --> 03:57:08.190 So Nick was saying services like Character AI. 03:57:11.370 --> 03:57:15.069 Spicy Chat AI. And others. I've never heard of 03:57:15.069 --> 03:57:21.690 Spicy Chat AI. I haven't either, but I know and 03:57:21.690 --> 03:57:27.209 I mentioned this to Nick that one of our former 03:57:29.769 --> 03:57:35.729 simulcasters is using a tool that he has actually 03:57:35.729 --> 03:57:39.270 programmed because you have to program these 03:57:39.270 --> 03:57:45.750 and it's gotten so bad not only does he have 03:57:45.750 --> 03:57:52.649 the AI girlfriend but now he's got at least one 03:57:52.649 --> 03:58:00.879 sibling to go along with the package. Wow. Wow. 03:58:01.120 --> 03:58:06.799 That was your reaction last night. And for those 03:58:06.799 --> 03:58:08.700 who don't know, that would have been February 03:58:08.700 --> 03:58:26.700 3rd when I called Nick. And he says, quote, it's 03:58:26.700 --> 03:58:31.690 normal. Everybody's doing it. No, they're not. 03:58:32.129 --> 03:58:38.190 Not really? And everybody on live wire called 03:58:38.190 --> 03:58:40.989 bullshit. Every single one who've communicated 03:58:40.989 --> 03:58:45.510 with him. So do I. So are we doing that here? 03:58:46.569 --> 03:58:55.069 Karma's a bitch. Oops. Oops, did you say that? 03:58:57.590 --> 03:59:01.909 There's another worry too and it's unfortunately 03:59:01.909 --> 03:59:05.770 as we've talked about with that very public case 03:59:05.770 --> 03:59:15.770 of the teen committing suicide. And that was 03:59:15.770 --> 03:59:18.829 because and that goes into the whole hallucination 03:59:18.829 --> 03:59:24.430 topic which we can get into and that might be 03:59:24.430 --> 03:59:29.579 270 depending on What's going on and what the 03:59:29.579 --> 03:59:35.639 landscape covers? We can definitely... That's 03:59:35.639 --> 03:59:37.959 one thing I do want to cover is the hallucination 03:59:37.959 --> 03:59:46.420 aspect. What is it actually doing? Because I 03:59:46.420 --> 03:59:49.239 did talk to Chet specifically about it. It's 03:59:49.239 --> 03:59:52.360 like, well, I'm not technically hallucinating. 03:59:53.079 --> 03:59:58.469 If people press me for facts... I'm going to 03:59:58.469 --> 04:00:05.469 make up a name, i .e., the person at LA Metro 04:00:05.469 --> 04:00:11.250 who runs the accessibility unit is Nicholas Jackson. 04:00:13.350 --> 04:00:21.870 Right. I'm giving you a fake name because I don't 04:00:21.870 --> 04:00:26.510 know who's actually running it, was its response. 04:00:27.659 --> 04:00:30.399 But we can go into more detail about this if 04:00:30.399 --> 04:00:35.319 I tell it. Remember our AI discussion? Give me 04:00:35.319 --> 04:00:41.139 the hallucinations section for a podcast. And 04:00:41.139 --> 04:00:43.540 it's going to do the same thing that I did before. 04:00:45.280 --> 04:00:49.260 And we can edit it and do whatever we want with 04:00:49.260 --> 04:00:55.979 it and call it our own. But, yes, I want to cover 04:00:55.979 --> 04:00:59.440 that. Yeah, we'll have to cover that on throwback 04:00:59.440 --> 04:01:01.680 at some point as well. We were going to do that 04:01:01.680 --> 04:01:06.200 on throwback too. We were, but I'm not even there 04:01:06.200 --> 04:01:09.260 yet. I have to go through meetings before I can 04:01:09.260 --> 04:01:13.360 even think about how I want to proceed with this. 04:01:13.440 --> 04:01:15.700 And we've got several topics ahead of it, but 04:01:15.700 --> 04:01:19.379 depending on how we're doing things. We do, yes. 04:01:20.299 --> 04:01:26.840 We're good. So we're good. We don't need... To 04:01:26.840 --> 04:01:29.819 answer all three, if we don't want to, give it 04:01:29.819 --> 04:01:34.479 thought and report back later, and we can air 04:01:34.479 --> 04:01:37.379 your comments. The lines of communication are 04:01:37.379 --> 04:01:39.719 open, so if you think of something later, panel, 04:01:39.920 --> 04:01:46.340 then leave a comment, drop me a note, tell me 04:01:46.340 --> 04:01:49.500 you want it aired. I'll take care of everything. 04:01:51.639 --> 04:01:55.079 Listeners. And podcasters, listeners, you can 04:01:55.079 --> 04:01:58.680 comment anytime. Let me know what you think. 04:02:00.200 --> 04:02:04.760 Ask any questions. The worst we can do is ask 04:02:04.760 --> 04:02:07.479 the AI. You know, somebody asked a question about... 04:02:07.479 --> 04:02:12.659 Yeah. And that's exactly what we're going to 04:02:12.659 --> 04:02:17.059 do with the one item that Nick asked. I don't 04:02:17.059 --> 04:02:19.959 know what this means. And honestly, I have an 04:02:19.959 --> 04:02:22.840 idea of what it means. I understood it in practice 04:02:22.840 --> 04:02:25.879 and I should have asked it and included that, 04:02:25.979 --> 04:02:29.959 but I didn't really... I mean, I understood it 04:02:29.959 --> 04:02:34.120 one way, but let's see what it says and see if 04:02:34.120 --> 04:02:39.159 I'm correct. And I can basically say, I said 04:02:39.159 --> 04:02:44.799 in the podcast that you say one thing about the 04:02:44.799 --> 04:02:49.350 population in general. And you just use that 04:02:49.350 --> 04:02:53.690 without rewriting it to your life experience. 04:02:54.469 --> 04:02:59.709 That's what I think it means, but we can... That 04:02:59.709 --> 04:03:04.290 very well could be. We can go into more detail. 04:03:05.049 --> 04:03:13.149 All right. I can read number seven unless somebody 04:03:13.149 --> 04:03:15.510 else wants to. This is the wrap -up section, 04:03:15.729 --> 04:03:19.159 and this will... practically end everything for 04:03:19.159 --> 04:03:24.920 today's AI program. And we'll have more videos 04:03:24.920 --> 04:03:29.760 coming up for you afterward. Does somebody else 04:03:29.760 --> 04:03:32.040 want to read number seven or should I read it? 04:03:34.420 --> 04:03:39.659 Actually, let me go plug my device into the wall 04:03:39.659 --> 04:03:43.940 because I'm getting pinged. You're getting pinged. 04:03:43.940 --> 04:03:49.629 Then I'll read. Well, actually, I'm getting pinged 04:03:49.629 --> 04:03:52.090 saying it's dead. It's almost dead, but I got 04:03:52.090 --> 04:03:55.850 it. It's dying, so I'll read. It's fine. Number 04:03:55.850 --> 04:04:05.110 seven. Wrap up and takeaways. Number one. Best 04:04:05.110 --> 04:04:14.670 practice is not anti -AI. Number two, accessibility 04:04:14.670 --> 04:04:27.430 and ethics are not optional. All right, so these 04:04:27.430 --> 04:04:31.850 are big points, right? Best practice is not anti 04:04:31.850 --> 04:04:37.049 -AI. I might be in the chat GPT or Claude or 04:04:37.049 --> 04:04:41.250 Gemini late, even though I've used them in limited... 04:04:41.629 --> 04:04:47.829 capabilities like is this artist um you know 04:04:47.829 --> 04:04:50.930 independent and then i feed it info and it goes 04:04:50.930 --> 04:04:54.829 seeing that you found it there this label is 04:04:54.829 --> 04:05:01.229 so yes okay so that's important accessibility 04:05:01.229 --> 04:05:07.209 and ethics are not optional so making sure that 04:05:07.209 --> 04:05:12.780 things are accessible To as much of the disability 04:05:12.780 --> 04:05:18.600 audience as possible. That's not optional. It's 04:05:18.600 --> 04:05:22.379 required now. So are your ethics. Right there. 04:05:23.700 --> 04:05:28.120 Down. Down. Because we do have the right to be 04:05:28.120 --> 04:05:33.120 included in every aspect of our journey. And 04:05:33.120 --> 04:05:41.319 that's totally important. So... And third, humans 04:05:41.319 --> 04:05:45.600 remain accountable. Meaning, if I'm giving it 04:05:45.600 --> 04:05:48.600 symptoms and saying, do I have to be concerned 04:05:48.600 --> 04:05:52.280 or should I go get medical care right now? And 04:05:52.280 --> 04:05:57.559 it's saying, well, this is bad, but you can try 04:05:57.559 --> 04:06:02.440 these things. Give me an update and let's assess 04:06:02.440 --> 04:06:05.340 it. You're not clearly in danger. You're not 04:06:05.340 --> 04:06:09.780 having these symptoms. So you could be all right. 04:06:12.159 --> 04:06:14.239 And of course, it's up to you. And as it turned 04:06:14.239 --> 04:06:18.379 out, three days later, I was fine. Monday morning, 04:06:18.379 --> 04:06:21.040 I was practically back to normal. You could say, 04:06:21.100 --> 04:06:23.680 you know, do I want to go to a doctor or should 04:06:23.680 --> 04:06:26.899 I hang out and wait? I mean, again, that is the 04:06:26.899 --> 04:06:32.579 decision of the human, not the AI. So that's 04:06:32.579 --> 04:06:43.360 how it should be. Yes, I agree. My phone is fucking 04:06:43.360 --> 04:06:45.940 up again. I can definitely agree with that. My 04:06:45.940 --> 04:06:51.520 phone is fucking this up again. We know that 04:06:51.520 --> 04:06:56.760 there are other topics we can cover as part of 04:06:56.760 --> 04:07:00.959 this discussion, so please advise us where we 04:07:00.959 --> 04:07:05.459 should take this next time and we can move forward 04:07:05.459 --> 04:07:10.770 with that. Thanks for listening and be responsible. 04:07:10.770 --> 04:07:15.409 That's it. Thanks for listening is where we ended 04:07:15.409 --> 04:07:19.129 it. And I have an end of notes section. Thank 04:07:19.129 --> 04:07:23.750 you to everybody who wanted to read today. Does 04:07:23.750 --> 04:07:31.770 anybody have any final thoughts on this? I think 04:07:31.770 --> 04:07:35.909 this did a great job. I think I wrote this Pretty 04:07:35.909 --> 04:07:43.069 well, and we had a nice long discussion. That's 04:07:43.069 --> 04:07:50.370 what TSB is for. Yes. Yep. So the time points 04:07:50.370 --> 04:07:54.569 were for 45 minutes, but I told it TSB somewhere 04:07:54.569 --> 04:07:57.149 around four to five hours, including news, notes, 04:07:57.350 --> 04:08:04.219 the landscape, videos, and such. We're not doing 04:08:04.219 --> 04:08:09.440 anything wrong. I would say this discussion was 04:08:09.440 --> 04:08:13.920 very helpful. I know some of us are new to the 04:08:13.920 --> 04:08:16.680 AI scene or some of us are getting ourselves 04:08:16.680 --> 04:08:21.239 or people with it. And I'm glad we have this 04:08:21.239 --> 04:08:24.840 tool to look back on. And as mentioned earlier, 04:08:25.319 --> 04:08:30.379 AI is definitely... here to stay and we'll be 04:08:30.379 --> 04:08:36.020 branching out on other ideas and topics and no, 04:08:36.139 --> 04:08:40.340 I just felt this was very copensetic so I enjoyed 04:08:40.340 --> 04:08:45.079 today's discussion. The only thing I could say 04:08:45.079 --> 04:08:49.120 is just be responsible with AI, you know, just 04:08:49.120 --> 04:08:53.040 use it responsibly. Don't be malicious with it. 04:08:54.340 --> 04:09:02.639 You'll be fine. Right. And remember, you are 04:09:02.639 --> 04:09:06.139 the one to train it. It's not a mind reader. 04:09:06.399 --> 04:09:18.280 I can train you. You gotta train it. Yes. What 04:09:18.280 --> 04:09:19.879 do you think over here, Nick? I thought you fell 04:09:19.879 --> 04:09:25.790 asleep. Uh -oh. Well, he might be doing... Oh, 04:09:25.790 --> 04:09:27.290 there he goes. I was going to say, he might be 04:09:27.290 --> 04:09:29.569 doing other things, too, just like I am trying 04:09:29.569 --> 04:09:33.530 to get a few tracks in for this afternoon's running. 04:09:34.750 --> 04:09:37.409 But go ahead, Mr. J. I actually think that the 04:09:37.409 --> 04:09:42.329 most important point here in number seven, believe 04:09:42.329 --> 04:09:45.090 it or not, I think is actually number one, not 04:09:45.090 --> 04:09:50.100 the others. Because... Go ahead and reread number... 04:09:50.100 --> 04:09:54.040 So everybody has the same context. Reread number 04:09:54.040 --> 04:09:57.399 one. Okay, yeah. All right, I'm getting to it 04:09:57.399 --> 04:10:01.979 right now. One, best practice is not anti -AI. 04:10:02.899 --> 04:10:07.120 So I think that's very important to know because 04:10:07.120 --> 04:10:12.840 a lot of people who are just very much into AI 04:10:12.840 --> 04:10:17.200 and use it... more than we do and lean more heavily 04:10:17.200 --> 04:10:22.319 on it might when we start talking about best 04:10:22.319 --> 04:10:25.399 practices start assuming oh well then you just 04:10:25.399 --> 04:10:28.139 don't support ai you just don't like it and you're 04:10:28.139 --> 04:10:30.520 just not part of the modern age that's not it 04:10:30.520 --> 04:10:33.739 at all it's about using it we've been technically 04:10:33.739 --> 04:10:42.739 using ai since google and alexa but they're completely 04:10:42.739 --> 04:10:49.030 different devices. Yeah. And it's completely 04:10:49.030 --> 04:10:56.809 different engines too. Yeah. I mean, Google's 04:10:56.809 --> 04:11:02.110 been around before Gemini ever became big. Yep. 04:11:02.610 --> 04:11:08.670 It's true. Alexa's probably been around... Well, 04:11:08.770 --> 04:11:12.280 okay. I think... Siri might have been around 04:11:12.280 --> 04:11:16.180 before Alexa, but it doesn't matter the actual 04:11:16.180 --> 04:11:27.000 order. No. Although it's gotten so bad that later 04:11:27.000 --> 04:11:33.299 versions of Siri are now using Gemini because 04:11:33.299 --> 04:11:37.280 Apple basically caved in and paid Google a bunch 04:11:37.280 --> 04:11:42.559 of money to integrate it into the phone. It's 04:11:42.559 --> 04:11:45.780 also using ChatGPT as well. It's using both. 04:11:47.260 --> 04:11:51.139 I don't know any details about any of that, but 04:11:51.139 --> 04:11:55.459 I do know that... And yes, my Google over there 04:11:55.459 --> 04:11:58.260 said it didn't understand because it heard its 04:11:58.260 --> 04:12:03.309 name and... try to respond. I've heard that too, 04:12:03.409 --> 04:12:05.670 yeah. That it's using Gemini. It's going to be 04:12:05.670 --> 04:12:11.209 using Gemini as a back end. Yeah. But I did hear 04:12:11.209 --> 04:12:14.969 that they shoved Google a bunch of money up their 04:12:14.969 --> 04:12:18.670 ass. Yep. Because they're going to use Gemini 04:12:18.670 --> 04:12:21.430 as their back end. Yeah. That's what I heard 04:12:21.430 --> 04:12:28.020 too. I did hear that somewhere. I don't know 04:12:28.020 --> 04:12:30.459 if they're going to get rid of chat GPT support 04:12:30.459 --> 04:12:33.659 or if they're just going to... I don't know. 04:12:34.000 --> 04:12:36.959 I don't know anything about that. If you hear 04:12:36.959 --> 04:12:41.920 any more, send it our way and maybe I'll blog 04:12:41.920 --> 04:12:50.780 it or we'll talk about it. I listen to the Apple 04:12:50.780 --> 04:12:54.370 Insider podcast every week. That's where I heard 04:12:54.370 --> 04:13:01.049 that from too. I need to go follow that. I just 04:13:01.049 --> 04:13:04.569 don't have that kind of time. I'm too involved. 04:13:04.870 --> 04:13:09.950 I can't even keep up with my own Metro stuff 04:13:09.950 --> 04:13:14.850 these days. I got articles piling up and I saw 04:13:14.850 --> 04:13:17.590 something on the source that needs to go out. 04:13:19.390 --> 04:13:23.090 I'm very, very, very behind. I can't even keep 04:13:23.090 --> 04:13:33.129 up. Yeah. Getting sick didn't help me any. Uh, 04:13:33.270 --> 04:13:39.430 no. No, but at least it gave you a good... This 04:13:39.430 --> 04:13:41.889 gave you a chance to kind of relax, too, kind 04:13:41.889 --> 04:13:46.530 of. You know? Not really. Well, yeah, relax and 04:13:46.530 --> 04:13:58.610 explore. I suppose so. Gentlemen who read the 04:13:58.610 --> 04:14:06.190 topic in two weeks, it's going to be how can 04:14:06.190 --> 04:14:16.690 small companies like the JRN or Menve be more 04:14:16.690 --> 04:14:27.110 compliant than the multi -billion dollar companies. 04:14:33.129 --> 04:14:40.190 Well, basically, we don't sell people's data. 04:14:40.290 --> 04:14:45.010 We treat people like humans, not a number. And 04:14:45.010 --> 04:14:48.889 if they violate the policy, they are out of our 04:14:48.889 --> 04:14:54.500 system. That's just a small preview. That's Menvy's 04:14:54.500 --> 04:14:57.379 policies. And yes, you are absolutely correct. 04:14:57.600 --> 04:15:06.739 Yes. Yeah, I'll just give him a quick small preview 04:15:06.739 --> 04:15:10.399 of what I read 24 hours ago. I'm going to look 04:15:10.399 --> 04:15:23.670 at it. Mr. J. Your preview topic. Actually, before 04:15:23.670 --> 04:15:33.790 your preview topic, your thoughts on 268. I think 04:15:33.790 --> 04:15:38.629 that that is a fascinating thing to examine because 04:15:38.629 --> 04:15:44.850 you non -security people would clearly think, 04:15:44.969 --> 04:15:47.889 oh, these big companies, yeah, they do things 04:15:47.889 --> 04:15:53.059 that we don't like. They do things that we find 04:15:53.059 --> 04:15:56.420 questionable, but they keep our data safe, surely, 04:15:56.639 --> 04:15:59.360 and they're private about it. Oh, that's so wrong. 04:15:59.659 --> 04:16:01.979 Yeah, right. Even I know that. That is absolutely 04:16:01.979 --> 04:16:07.719 wrong. And part of the extended show notes will 04:16:07.719 --> 04:16:16.079 be a number of write -ups about some of the coverage 04:16:16.079 --> 04:16:20.200 I've been covering. For years. Nick, have you 04:16:20.200 --> 04:16:22.940 gone over to our articles page and looked at 04:16:22.940 --> 04:16:26.860 some of my older writings covering this stuff? 04:16:29.159 --> 04:16:32.420 Not today, but I'm sure that if I went, I would 04:16:32.420 --> 04:16:36.579 remember. Oh, this diatribe. That one. JaredReimer 04:16:36.579 --> 04:16:39.639 .net. And when you go there, find the articles 04:16:39.639 --> 04:16:44.479 link under links around the main domain. And 04:16:44.479 --> 04:16:47.979 you can read what is of interest to you. There's 04:16:47.979 --> 04:16:51.219 several security articles there besides others. 04:16:53.120 --> 04:16:59.739 Yeah. Alright. I'm going to get out of here. 04:17:00.459 --> 04:17:09.799 I will see you on Saturday, Mr. R. Yes, sir. 04:17:10.159 --> 04:17:15.420 Yes. We'll see you then, Terry. Out he goes. 04:17:17.200 --> 04:17:31.780 Yep, he's gone. Jay, you had a topic that we 04:17:31.780 --> 04:17:40.139 should probably do for 269. Yes. And I think 04:17:40.139 --> 04:17:49.879 in order to not make it look like AI wrote this 04:17:49.879 --> 04:17:52.379 entirely, and I say that because I was reading 04:17:52.379 --> 04:17:55.180 through as we were talking, and a lot of it is 04:17:55.180 --> 04:18:00.319 the way I would speak this or write this. I do 04:18:00.319 --> 04:18:03.520 want to do kind of an introduction to this. It's 04:18:03.520 --> 04:18:08.079 an issue because it's a trend I'm seeing, and 04:18:08.079 --> 04:18:12.180 I don't think it's just one person, but the making 04:18:12.180 --> 04:18:19.540 the revelation of What I have learned is the 04:18:19.540 --> 04:18:22.959 official term personal health information and 04:18:22.959 --> 04:18:29.440 making that public. That's PHI. PHI, yes. Yeah, 04:18:29.440 --> 04:18:36.940 PHI, yep. In the case of the various source, 04:18:37.180 --> 04:18:41.639 they didn't do anything truly terrible, but they 04:18:41.639 --> 04:18:43.540 still did talk about what their blood pressure 04:18:43.540 --> 04:18:46.190 readings were and things that... really should 04:18:46.190 --> 04:18:51.850 not be shared with the world. See, I would only 04:18:51.850 --> 04:18:59.989 do that if it asked, like, is your blood pressure 04:18:59.989 --> 04:19:03.770 high? And I probably in most cases would say, 04:19:03.829 --> 04:19:09.829 I don't know. I don't have any way to do that 04:19:09.829 --> 04:19:13.819 right now. I would probably have to go to a doctor 04:19:13.819 --> 04:19:19.860 or a pharmacy to do that. And find out. But, 04:19:19.920 --> 04:19:24.239 I mean, that discussion should only come up if 04:19:24.239 --> 04:19:31.340 you are in the presence of somebody who is a 04:19:31.340 --> 04:19:35.459 physician or if you are at your doctor. And that's 04:19:35.459 --> 04:19:43.250 where it should stay. I agree. So if AI were 04:19:43.250 --> 04:19:48.829 to ask me, even if I had the ability, I would 04:19:48.829 --> 04:19:52.469 just tell it I don't know. Just because that 04:19:52.469 --> 04:19:56.569 is, I think, crossing a bit of a line. Although 04:19:56.569 --> 04:20:01.209 AI is trying to analyze what's wrong. But then 04:20:01.209 --> 04:20:05.370 it goes back to your settings. Are you having 04:20:05.370 --> 04:20:10.290 it set to share all that data? As part of LLM 04:20:10.290 --> 04:20:17.409 training? If yes, then don't. If not, and you 04:20:17.409 --> 04:20:22.250 have the share across chat option checked, then 04:20:22.250 --> 04:20:27.489 I'd say you're probably okay. Yeah, but if you 04:20:27.489 --> 04:20:32.370 are revealing that in a radio broadcast, I think 04:20:32.370 --> 04:20:39.219 then we have problems. I agree. Even though the 04:20:39.219 --> 04:20:43.459 listenership may be small and the podcast listenership 04:20:43.459 --> 04:20:47.739 may be small, I'm not saying it isn't. I'm not 04:20:47.739 --> 04:20:55.620 saying it isn't. But even totally routine things, 04:20:55.920 --> 04:20:58.180 you know, checking your vitals at your doctor's 04:20:58.180 --> 04:21:02.549 office, that should stay there. with another 04:21:02.549 --> 04:21:06.290 physician who needs to treat you, not be consumed 04:21:06.290 --> 04:21:14.809 and heard by the general public. I agree. I just 04:21:14.809 --> 04:21:17.430 remembered, before we actually push some buttons 04:21:17.430 --> 04:21:22.590 to change things, we must do... Now, where is 04:21:22.590 --> 04:21:34.260 it here? Here it is. We must do this... Because 04:21:34.260 --> 04:21:38.760 this is bad. And we talk about personal accountability. 04:21:44.479 --> 04:21:49.860 Where's the braille file? There it is. Um... 04:21:49.860 --> 04:22:06.639 Wait, this is... Item number two, right? I mean... 04:22:06.639 --> 04:22:13.700 Which one? No, you don't have this file. Okay, 04:22:13.860 --> 04:22:17.719 I found it. You don't have this particular file. 04:22:18.600 --> 04:22:22.440 So, I want to go back and bring up real quick 04:22:22.440 --> 04:22:26.739 something that ties into the accountability aspect. 04:22:28.520 --> 04:22:31.819 And while this isn't necessarily security related, 04:22:33.129 --> 04:22:39.329 We talked about the following on Monday for RCL. 04:22:40.930 --> 04:22:46.209 You can search Radio Connection Live, and when 04:22:46.209 --> 04:22:52.170 you find it, it's actually hosted by Radio Connection 04:22:52.170 --> 04:22:56.489 Live. And here's what we're going to read from 04:22:56.489 --> 04:23:01.739 it, from their news section. The show got uploaded 04:23:01.739 --> 04:23:05.059 February 3rd, so you'll find it there. Oh, it 04:23:05.059 --> 04:23:10.299 did get uploaded the same day. Okay. Yeah. He 04:23:10.299 --> 04:23:14.479 sent it to me late Monday night. Well, then you 04:23:14.479 --> 04:23:16.639 need to be doing your stuff instead of waiting 04:23:16.639 --> 04:23:22.180 until Saturday. I know. I'm going to share the 04:23:22.180 --> 04:23:29.520 announcement out. I'm going to post it out. Go 04:23:29.520 --> 04:23:32.620 to sleep. So, I got it. You're good. You're good. 04:23:34.399 --> 04:23:40.959 This says, finally, we end with some news that 04:23:40.959 --> 04:23:45.159 we wish we didn't have to report on as often 04:23:45.159 --> 04:23:49.559 as we do. But unfortunately, it's coming up in 04:23:49.559 --> 04:23:55.350 the headlines again. Copper theft. as we, as 04:23:55.350 --> 04:23:59.829 well as transmitter damage, have plagued several 04:23:59.829 --> 04:24:04.750 radio stations over the years. And now, its latest 04:24:04.750 --> 04:24:12.590 victim is Summit Media's classic country 1070 04:24:12.590 --> 04:24:22.649 AM KFTI license to Wichita, Kansas. The station 04:24:22.649 --> 04:24:27.450 has been off the air since January 16th, citing 04:24:27.450 --> 04:24:36.530 copper theft as... Oh, my phone and my display. 04:24:36.590 --> 04:24:42.469 Here we go again. As well as damage to its transmitter. 04:24:44.010 --> 04:24:50.219 So... If you're a fan of the station, which utilizes 04:24:50.219 --> 04:24:55.040 Westwood One's 24 -7 real country format, there 04:24:55.040 --> 04:24:59.200 is good news, however. Listeners can still catch 04:24:59.200 --> 04:25:04.329 the station online. We don't know when the station 04:25:04.329 --> 04:25:08.309 will return to on -air operations, but Radio 04:25:08.309 --> 04:25:12.069 Connection Live has learned that the damage not 04:25:12.069 --> 04:25:16.649 only affected the grounding infrastructure for 04:25:16.649 --> 04:25:20.870 the station, but many of its transmitter components 04:25:20.870 --> 04:25:27.379 were also damaged. We at Radio Connection Live 04:25:27.379 --> 04:25:31.559 report on stories like this often and will keep 04:25:31.559 --> 04:25:35.239 you updated on this breaking story as soon as 04:25:35.239 --> 04:25:39.079 new information becomes available to our newsroom. 04:25:40.899 --> 04:25:44.600 There's something that Preston said to me that 04:25:44.600 --> 04:25:52.870 I want people to know. Mr. G? Please mention 04:25:52.870 --> 04:25:58.629 what you told me before we taped this file for 04:25:58.629 --> 04:26:05.489 you from this past Monday. Yes. So, basically, 04:26:05.709 --> 04:26:10.229 and that episode is now live in podcast form 04:26:10.229 --> 04:26:14.549 and it's for all affiliates too. But anyway, 04:26:14.709 --> 04:26:19.510 basically, when we prepare news stories like 04:26:19.510 --> 04:26:24.329 this, I do want to fact check. So I read the 04:26:24.329 --> 04:26:29.610 article from Radio Insight and it said there's 04:26:29.610 --> 04:26:33.250 no mention on the website or social media that 04:26:33.250 --> 04:26:36.489 they are still in existence. Well, sure enough, 04:26:36.549 --> 04:26:40.149 when I read the story on Friday, late Friday 04:26:40.149 --> 04:26:43.069 was proofreading and making the corrections to 04:26:43.069 --> 04:26:47.909 the file. I looked at said website. I used all 04:26:47.909 --> 04:26:51.690 my. accessibility navigation keys and what i 04:26:51.690 --> 04:26:57.750 was you know told in my statewide computer training 04:26:57.750 --> 04:27:03.649 back in school and there was no mention on you 04:27:03.649 --> 04:27:07.829 know the top of the home page or anywhere on 04:27:07.829 --> 04:27:12.829 the site for that matter there there was a listen 04:27:12.829 --> 04:27:15.549 live link that was showing but there's no message 04:27:15.549 --> 04:27:19.459 saying that hey our Over the years, you know, 04:27:19.459 --> 04:27:24.100 it's down due to this and this. Please continue 04:27:24.100 --> 04:27:29.239 to our content online. There is no word anywhere. 04:27:29.819 --> 04:27:36.100 So that's what I call mistransparency and miscommunication. 04:27:37.139 --> 04:27:39.659 I wouldn't call it mistransparency. I don't know 04:27:39.659 --> 04:27:42.620 if that's a word. I would call that miscommunication. 04:27:42.860 --> 04:27:48.040 Oh. A lack of transparency. I would call it a 04:27:48.040 --> 04:27:51.540 lack of transparency, not mistransparency. I 04:27:51.540 --> 04:27:54.739 don't know if mistransparency is a word. Somebody 04:27:54.739 --> 04:28:00.459 can find out and let me know. I feel pretty confident 04:28:00.459 --> 04:28:02.659 that it is not. I think what you are looking 04:28:02.659 --> 04:28:06.920 for is a lack of transparency. After hearing 04:28:06.920 --> 04:28:17.219 this, I think somebody will. But lack of transparency 04:28:17.219 --> 04:28:20.860 would be more appropriate. And this is what I 04:28:20.860 --> 04:28:33.200 was telling Mr. T on Monday. Yes. So we talked 04:28:33.200 --> 04:28:39.299 about it then. That got my blood boiling. Yeah, 04:28:40.079 --> 04:28:45.819 I think me too. When I called him Sunday. It 04:28:45.819 --> 04:28:53.860 was bad, but... Mr. J, go ahead, please. Something 04:28:53.860 --> 04:29:01.780 to think about. I... just... I mean, I guess 04:29:01.780 --> 04:29:05.360 I shouldn't be shocked that this kind of thing 04:29:05.360 --> 04:29:09.120 is even happening. I shouldn't be. I knew that 04:29:09.120 --> 04:29:18.209 was coming. But the fact that This has now escalated 04:29:18.209 --> 04:29:22.430 to actually damaging the infrastructure. Equipment. 04:29:22.510 --> 04:29:26.950 Transmitting? Yes, the equipment. Yes. That's 04:29:26.950 --> 04:29:32.590 a lot worse than... Not that copper theft isn't 04:29:32.590 --> 04:29:37.790 wrong or terrible, but this makes it infinitely 04:29:37.790 --> 04:29:42.500 worse. It's actually a felony? According to LA 04:29:42.500 --> 04:29:47.020 Metro, if you steal copper from infrastructure 04:29:47.020 --> 04:29:59.440 that is governmentally owned. Wow. They said 04:29:59.440 --> 04:30:05.239 so on their own blog. If you're caught, you're 04:30:05.239 --> 04:30:12.229 going to get in some trouble. Yes. That's basically 04:30:12.229 --> 04:30:14.989 what they said. That makes it a felony based 04:30:14.989 --> 04:30:19.870 on what I read. It's not a simple $5 fine. And 04:30:19.870 --> 04:30:23.690 I'm making up the money. No. Right. I'm making 04:30:23.690 --> 04:30:28.870 up the money. This radio station, I don't know 04:30:28.870 --> 04:30:33.329 if you would technically call it government property. 04:30:34.010 --> 04:30:38.290 So, I mean, there is that distinction, which 04:30:38.290 --> 04:30:43.200 sadly... uh would hold up legally it is owned 04:30:43.200 --> 04:30:47.340 by a public company it's owned by a public company 04:30:47.340 --> 04:30:53.000 but it's not governmentally i don't believe based 04:30:53.000 --> 04:30:55.659 on my knowledge of what was told to me during 04:30:55.659 --> 04:30:58.620 the airing of the program that it is governmental 04:30:58.620 --> 04:31:04.229 that is a governmental agency Yeah, okay, that 04:31:04.229 --> 04:31:06.889 makes sense. And to be honest, I'm not sure what 04:31:06.889 --> 04:31:11.870 their NASDAQ's employees... Well, that's where 04:31:11.870 --> 04:31:13.450 your tool would be of value. The station itself 04:31:13.450 --> 04:31:17.350 wouldn't have one. No, the station itself wouldn't, 04:31:17.350 --> 04:31:23.530 but the company that owns it would, if they wanted 04:31:23.530 --> 04:31:28.129 to. It's not a requirement. Right. You don't 04:31:28.129 --> 04:31:30.430 have to be listed in the public stock exchange. 04:31:31.950 --> 04:31:38.430 To do business. Nope. You could decide to take 04:31:38.430 --> 04:31:40.409 your company public like that, but yeah, I don't 04:31:40.409 --> 04:31:52.489 think that they have. So just a little errata 04:31:52.489 --> 04:31:58.399 for you. This goes to the transparency and the 04:31:58.399 --> 04:32:02.059 human in the loop must know what's going on. 04:32:05.760 --> 04:32:09.500 And making the right decisions, i .e., we better 04:32:09.500 --> 04:32:13.700 update our website because our infrastructure 04:32:13.700 --> 04:32:17.920 is completely down. I mean, even if they were 04:32:17.920 --> 04:32:23.989 able to get a message up on the air itself. We 04:32:23.989 --> 04:32:29.450 don't know if they even did that. Right. Based 04:32:29.450 --> 04:32:33.770 on my reading of that, based on my reading of 04:32:33.770 --> 04:32:37.450 that, they can't even do that. The thing's just 04:32:37.450 --> 04:33:05.500 gone. Yep. Cooked. Ugh. Fried. Yes, so... Flied. 04:33:07.639 --> 04:33:14.639 Basically, all that rolled into one saying, well, 04:33:14.759 --> 04:33:17.279 basically, we don't give a fuck if listeners 04:33:17.279 --> 04:33:21.900 can't find us. That's basically the reading I 04:33:21.900 --> 04:33:28.759 got. Yep, me too. Like I said, I read the publishers. 04:33:29.560 --> 04:33:32.419 Inside comments and I checked for myself for 04:33:32.419 --> 04:33:36.259 verification before I told you so we're on the 04:33:36.259 --> 04:33:59.029 same page Sorry I'm just being communicated with. 04:34:00.470 --> 04:34:17.630 Okay. That's okay. God. But yeah, I almost took 04:34:17.630 --> 04:34:24.090 one when I read that. Even before I turned the 04:34:24.090 --> 04:34:26.959 whole thing into Braille. I'm like, wait. It 04:34:26.959 --> 04:34:41.479 just said what? Where's the... Where's... Alright, 04:34:41.580 --> 04:34:44.659 this thing is jumping. Yeah, it's jumping. You're 04:34:44.659 --> 04:34:47.840 gonna have to wait, bud. Sorry. This thing's 04:34:47.840 --> 04:34:49.840 jumping. I don't know what's going on. I don't 04:34:49.840 --> 04:34:56.310 have time to deal at the moment. He's going to 04:34:56.310 --> 04:34:59.090 ask me what I ate and it's been practically absolutely 04:34:59.090 --> 04:35:04.950 much of nothing all day. And I got to leave in 04:35:04.950 --> 04:35:21.509 about an hour. A little over an hour. I was just 04:35:21.509 --> 04:35:27.450 lost for words. Gentlemen, I read that even before 04:35:27.450 --> 04:35:29.630 putting it in the Braille, and I was just lost 04:35:29.630 --> 04:35:36.849 for words. Yeah, totally. Like, that's totally 04:35:36.849 --> 04:35:53.970 unprofessional. Why is this thing jumping? Uh 04:35:53.970 --> 04:36:18.250 -oh. It feels like it's jumping. Wow. Well, remember, 04:36:18.549 --> 04:36:21.720 mine was just connected to a display. and was 04:36:21.720 --> 04:36:26.919 giving me some issues there. But my display is 04:36:26.919 --> 04:36:40.759 off and out of the way. Mr. J, any final comments? 04:36:40.819 --> 04:36:43.959 Anything that you want to bring up before we 04:36:43.959 --> 04:36:50.680 play Files and call this program good? I think 04:36:50.680 --> 04:36:56.779 I'm fine. Well, the only thing that I ask is 04:36:56.779 --> 04:37:03.180 that you clean that up and write it the way you 04:37:03.180 --> 04:37:08.259 want it presented. And I'll work with you with 04:37:08.259 --> 04:37:10.720 Braille so that you can tell me where headings 04:37:10.720 --> 04:37:14.779 and things go. And then you can drop it in my 04:37:14.779 --> 04:37:19.279 folder when it's ready. And then we can do it. 04:37:19.299 --> 04:37:22.279 And then we'll figure out what podcast it's going 04:37:22.279 --> 04:37:30.080 into. Right. Right now we're penciling 269, but 04:37:30.080 --> 04:37:45.439 we'll see. Mr. G. Yes, I was going to say, are 04:37:45.439 --> 04:37:51.909 we covered? Because I do need to make a call. 04:37:52.529 --> 04:37:55.569 One of our NFB members is interested in getting 04:37:55.569 --> 04:37:57.369 her house vouchers. So I'm going to help her 04:37:57.369 --> 04:38:02.709 out with that. Well, then take us out because 04:38:02.709 --> 04:38:05.869 I'm done and I have to leave in an hour. So I'm 04:38:05.869 --> 04:38:09.610 now time sensitive. Yes. So please. Yes, right. 04:38:09.790 --> 04:38:12.849 I was going to say yes. I got to leave in an 04:38:12.849 --> 04:38:17.279 hour. Yes, I'm going to say I'm covered. So, 04:38:17.299 --> 04:38:23.099 folks, this has been Security Box. Yes, I'm working 04:38:23.099 --> 04:38:25.819 on it. Folks, this has been Security Box. We 04:38:25.819 --> 04:38:28.740 say thank you for listening. We hope you enjoyed 04:38:28.740 --> 04:38:31.020 today's program and this ever -important discussion 04:38:31.020 --> 04:38:33.740 all about AI and the future that we are building 04:38:33.740 --> 04:38:36.580 together. As always, if you have any comments, 04:38:36.759 --> 04:38:42.240 please reach out to our comment line at 888 -405 04:38:42.240 --> 04:38:49.919 -7524. You may also email jaredrmer at 986mix 04:38:49.919 --> 04:38:57.000 .com or tech at menvi .org. And you can also 04:38:57.000 --> 04:39:03.540 WhatsApp Jared as well at 804 -442 -6975. And 04:39:03.540 --> 04:39:06.340 as always, you can catch past episodes on Jared's 04:39:06.340 --> 04:39:08.599 Technology Podcast Network in your preferred 04:39:08.599 --> 04:39:11.659 podcast feed. And for more exploration in the 04:39:11.659 --> 04:39:13.520 landscape, please tune in to Throwbacks at Night 04:39:13.520 --> 04:39:18.360 every Saturday at 8 p .m. Eastern on 96Mix server 04:39:18.360 --> 04:39:21.159 number 3. We do have a company security hour 04:39:21.159 --> 04:39:25.840 at 9 p .m. Eastern as well. So make it a good 04:39:25.840 --> 04:39:28.340 and safe week. We'll see you again in two weeks 04:39:28.340 --> 04:39:31.659 for another adventure across the landscape. So 04:39:31.659 --> 04:39:34.599 on behalf of all of us here, this is Preston, 04:39:34.599 --> 04:39:39.360 Jared, Terry, Nick, and all of you. Wherever 04:39:39.360 --> 04:39:46.080 you may be, we say thank you for listening. Make 04:39:46.080 --> 04:39:49.119 it a good and safe week. And as always, watch 04:39:49.119 --> 04:39:53.500 those links and be safe and be aware. Thank you 04:39:53.500 --> 04:40:08.919 and make it a great day, everybody. that help 04:40:08.919 --> 04:40:14.279 us keep this podcast up and running with resources 04:40:14.279 --> 04:40:25.619 thanks for listening everybody i'm just gonna 04:40:25.619 --> 04:40:29.020 say it we are never getting rid of deep fakes 04:40:29.020 --> 04:40:31.819 and i think that's honestly the truth i'm nick 04:40:31.819 --> 04:40:34.439 espinoza your chief security fanatic and let's 04:40:34.439 --> 04:40:37.049 dive in now There's a really good write -up on 04:40:37.049 --> 04:40:39.909 this in The Guardian by Priya Bharadia and Aisha 04:40:39.909 --> 04:40:41.930 Down. And quite frankly, we're going to start 04:40:41.930 --> 04:40:44.029 there. But I do have a lot of thoughts on this. 04:40:44.090 --> 04:40:46.290 And if you didn't know, millions of people around 04:40:46.290 --> 04:40:50.029 the world have created and shared deepfake nudes 04:40:50.029 --> 04:40:52.970 on the secure messaging app Telegram. That's 04:40:52.970 --> 04:40:55.630 according to a Guardian analysis. And basically, 04:40:55.750 --> 04:40:58.669 this is coming because of the spread of advanced 04:40:58.669 --> 04:41:01.569 AI tools as it's industrializing essentially 04:41:01.569 --> 04:41:04.669 deepfakes online, not to mention the abuse of 04:41:04.669 --> 04:41:08.000 women. even men and everybody else. Now, The 04:41:08.000 --> 04:41:11.180 Guardian identified at least 150 Telegram channels. 04:41:11.459 --> 04:41:14.020 Basically, these are large encrypted group chats 04:41:14.020 --> 04:41:16.000 that are popular for their secure communications 04:41:16.000 --> 04:41:19.560 that essentially appear to have users from countries 04:41:19.560 --> 04:41:21.000 all over the world. We're talking the United 04:41:21.000 --> 04:41:24.360 Kingdom, Brazil, China, Nigeria, Russia, India, 04:41:24.500 --> 04:41:27.159 and on and on and on. Some of them are offering 04:41:27.159 --> 04:41:30.799 nudified photos or videos. for a fee. So basically, 04:41:30.860 --> 04:41:34.200 you could upload a video of any woman, for example, 04:41:34.380 --> 04:41:36.759 and the AI will produce a video that basically 04:41:36.759 --> 04:41:40.060 has her performing sex acts, or just making her 04:41:40.060 --> 04:41:42.819 nude, all these different kinds of things. Others 04:41:42.819 --> 04:41:45.659 offer a feed of images like celebrities, social 04:41:45.659 --> 04:41:49.020 media influencers, just, you know, ordinary women 04:41:49.020 --> 04:41:51.860 in this case, essentially turning them nude and 04:41:51.860 --> 04:41:54.200 making them perform sexual acts. Again, the AI 04:41:54.200 --> 04:41:57.080 obviously generating all of this. Now followers 04:41:57.080 --> 04:42:00.380 are using the channels to share tips also on 04:42:00.380 --> 04:42:03.560 available deepfake tools. And while there's basically 04:42:03.560 --> 04:42:06.139 been Telegram channels that have been dedicated 04:42:06.139 --> 04:42:09.299 for quite some time to distributing non -consensual 04:42:09.299 --> 04:42:12.180 nude images of women, now with the availability, 04:42:12.580 --> 04:42:15.979 and it is a widespread availability of AI tools, 04:42:16.040 --> 04:42:18.180 means that essentially anybody can instantly 04:42:18.180 --> 04:42:20.919 become the subject of graphic sexual content. 04:42:21.500 --> 04:42:23.680 that could potentially be viewable by millions. 04:42:24.060 --> 04:42:26.619 I mean, it was a great write -up. They had more 04:42:26.619 --> 04:42:29.099 in this, but let's dive in because the crux of 04:42:29.099 --> 04:42:31.819 this problem, and that is just one subset of 04:42:31.819 --> 04:42:33.740 the deepfake issue that we have. That's just 04:42:33.740 --> 04:42:36.299 the latest generation is we're seeing nudes everywhere. 04:42:36.540 --> 04:42:41.180 Grok, which is XAI, X aka Twitter, aka Elon Musk, 04:42:41.259 --> 04:42:43.360 has a massive problem with this. They're just 04:42:43.360 --> 04:42:45.979 being looked at now by multiple countries, including 04:42:45.979 --> 04:42:49.950 the EU, Canada, and others. This goes above and 04:42:49.950 --> 04:42:52.069 beyond that because deep fakes have been around 04:42:52.069 --> 04:42:54.830 long before this new generation problem. And 04:42:54.830 --> 04:42:56.970 so here's why I think it's unfortunately a fact 04:42:56.970 --> 04:42:59.990 that we are never getting rid of this. Because 04:42:59.990 --> 04:43:02.729 if you think about it, the same advances in machine 04:43:02.729 --> 04:43:06.729 learning that power this kind of fraud also underpin 04:43:06.729 --> 04:43:09.349 the legitimate tools that we would use for things 04:43:09.349 --> 04:43:12.029 like film production, accessibility, education, 04:43:12.569 --> 04:43:15.369 marketing, even visualization in the sciences. 04:43:16.159 --> 04:43:18.759 uses these kinds of tools. Generative models 04:43:18.759 --> 04:43:21.259 are becoming cheaper. They're becoming faster. 04:43:21.560 --> 04:43:24.119 They're more widely embedded into everyday software, 04:43:24.299 --> 04:43:26.619 oftentimes running locally on your computer, 04:43:26.799 --> 04:43:29.380 meaning you don't have to go to the cloud to 04:43:29.380 --> 04:43:31.479 generate a lot of these things. And I went looking 04:43:31.479 --> 04:43:34.080 to see if I could find offline image generators, 04:43:34.319 --> 04:43:37.380 and I found a ton. I'm not listing any of them 04:43:37.380 --> 04:43:40.580 here for obvious reasons. Now, once a capability 04:43:40.580 --> 04:43:43.400 basically becomes decentralized and therefore 04:43:43.400 --> 04:43:46.049 has that dual use legitimate or or criminal, 04:43:46.250 --> 04:43:49.889 it can't really meaningfully be removed, right? 04:43:50.009 --> 04:43:52.450 Because you would also be dismantling the broader 04:43:52.450 --> 04:43:55.330 digital ecosystem that it depends on it. If you 04:43:55.330 --> 04:43:58.290 can't use it in crime because we are basically 04:43:58.290 --> 04:44:00.750 regulating it away, we also then couldn't use 04:44:00.750 --> 04:44:02.490 it for things like film production, legitimate 04:44:02.490 --> 04:44:06.310 film production. Even aggressive regulation can 04:44:06.310 --> 04:44:08.709 only shape how deepfakes are used or labeled. 04:44:08.810 --> 04:44:11.970 It cannot erase the underlying techniques or 04:44:11.970 --> 04:44:14.959 the countless open source implementations. already 04:44:14.959 --> 04:44:16.979 distributed globally. The Chinese had a shot 04:44:16.979 --> 04:44:19.380 across the bow the other year with deep seek 04:44:19.380 --> 04:44:21.860 for large language models, a chat GPT, et cetera, 04:44:21.860 --> 04:44:24.240 competitor that you could download and run yourself. 04:44:24.500 --> 04:44:27.060 It was a huge problem. I did videos and segments 04:44:27.060 --> 04:44:29.060 on it, not to mention it's censorship and bias 04:44:29.060 --> 04:44:31.919 and all of that. But going back to deep fakes 04:44:31.919 --> 04:44:34.979 on top of all of this that I just said, the internet 04:44:34.979 --> 04:44:38.549 itself. is optimized for replication and anonymity 04:44:38.549 --> 04:44:41.750 and speed rather than enforcement of laws or 04:44:41.750 --> 04:44:44.930 even simply the truth. Content can be created 04:44:44.930 --> 04:44:47.810 in one country and then it can be hosted in another 04:44:47.810 --> 04:44:49.849 country. It can be mirrored instantly somewhere 04:44:49.849 --> 04:44:52.090 else and then it can be shared millions of times 04:44:52.090 --> 04:44:54.810 before any kind of moderation or legal response 04:44:54.810 --> 04:44:57.590 is possible. It's the same issue with disinformation. 04:44:57.869 --> 04:45:00.349 A ton of people read disinformation, think it's 04:45:00.349 --> 04:45:02.990 true. You believe that confirmation bias and 04:45:02.990 --> 04:45:06.090 when the traditional news media catches up to 04:45:06.090 --> 04:45:08.310 fact check it and say it's fake. How many people 04:45:08.310 --> 04:45:11.310 get that memo? And the originators of that deep 04:45:11.310 --> 04:45:13.750 fake are almost never held accountable at all. 04:45:13.849 --> 04:45:15.430 Oftentimes, they're not even in the country. 04:45:15.770 --> 04:45:19.330 On top of this, detection tools will continue 04:45:19.330 --> 04:45:22.049 to improve, but so will evasion techniques. This 04:45:22.049 --> 04:45:24.930 is cybersecurity 101. So it creates a permanent 04:45:24.930 --> 04:45:28.389 arms race, just like cybersecurity, where perfect 04:45:28.389 --> 04:45:32.829 prevention is simply not possible. Statistically, 04:45:32.829 --> 04:45:36.590 operationally, it's just not possible. And basically, 04:45:36.669 --> 04:45:39.770 as long as there are incentives, whatever those 04:45:39.770 --> 04:45:42.090 incentives are, think like political influence, 04:45:42.270 --> 04:45:45.549 financial fraud. harassment, entertainment, even 04:45:45.549 --> 04:45:47.970 notoriety. I mean, people just want to be internet 04:45:47.970 --> 04:45:50.970 famous, right? There will always be people willing 04:45:50.970 --> 04:45:53.349 to produce and distribute deep fakes for whatever 04:45:53.349 --> 04:45:56.689 reason that is, whether they're nude or making 04:45:56.689 --> 04:45:58.869 the president of the United States do something 04:45:58.869 --> 04:46:01.950 he didn't say or do. All of these things we've 04:46:01.950 --> 04:46:04.830 seen countless times over the years in the AI 04:46:04.830 --> 04:46:09.389 era. So what chance do we really have here? And 04:46:09.389 --> 04:46:13.580 I think... We have one slight maybe chance because 04:46:13.580 --> 04:46:16.759 I think there is a realistic goal and it's not 04:46:16.759 --> 04:46:18.900 elimination. We're never going to eliminate this, 04:46:19.000 --> 04:46:21.979 but it could be resilience. But it's going to 04:46:21.979 --> 04:46:23.880 take all of us, I think, working together. So 04:46:23.880 --> 04:46:26.380 if we're building things like social, legal and 04:46:26.380 --> 04:46:28.560 technical systems that can do things like reduce 04:46:28.560 --> 04:46:31.580 harm and establish accountability, maybe help 04:46:31.580 --> 04:46:34.240 people navigate the digital environment where 04:46:34.240 --> 04:46:38.279 basically. What they're seeing is no longer synonymous 04:46:38.279 --> 04:46:41.659 with believing, a .k .a. educating on deep fakes, 04:46:41.659 --> 04:46:44.540 educating on the problems that these are. Finland 04:46:44.540 --> 04:46:46.860 actually did this, and I believe it was their 04:46:46.860 --> 04:46:50.020 2017 election, to great effect, where they were 04:46:50.020 --> 04:46:51.819 able to cut through the massive amount of Russian 04:46:51.819 --> 04:46:53.619 disinformation hitting their election system, 04:46:53.779 --> 04:46:55.819 and basically the guy backed by the Russians 04:46:55.819 --> 04:46:58.639 didn't win, right? They taught their country 04:46:58.639 --> 04:47:01.900 how to spot deep fakes, how to spot fake news. 04:47:02.419 --> 04:47:05.759 That's our only shot. I don't see it being realistically 04:47:05.759 --> 04:47:09.880 possible, at least right now, at least in the 04:47:09.880 --> 04:47:12.740 United States and some other places. But I guess 04:47:12.740 --> 04:47:16.060 that's our only hope. So deep fakes aren't going 04:47:16.060 --> 04:47:18.779 away. It's only going to get worse. And unfortunately, 04:47:19.080 --> 04:47:22.639 I hate to be the Debbie Downer, but it's here 04:47:22.639 --> 04:47:24.900 to stay. And I think we've got to deal with this. 04:47:24.939 --> 04:47:26.860 We've got to address this. And most importantly, 04:47:27.060 --> 04:47:29.520 we've got to teach the next generation why it's 04:47:29.520 --> 04:47:31.689 wrong. And please like, share, follow me here 04:47:31.689 --> 04:47:34.349 on Facebook and Twitter at NickAESP. And please 04:47:34.349 --> 04:47:35.889 feel free to subscribe to me at YouTube as well. 04:47:36.009 --> 04:47:38.529 And as always, stay safe, stay online, and please, 04:47:38.610 --> 04:47:40.790 please, please attempt to stay private, informed, 04:47:41.049 --> 04:47:45.430 and secure. Take care. Hey, everybody. Nick Espinosa, 04:47:45.590 --> 04:47:47.610 your chief security fanatic here. Don't forget 04:47:47.610 --> 04:47:50.529 to subscribe. And today, I want to talk about 04:47:50.529 --> 04:47:53.990 Teslas. They're super hackable, but actually, 04:47:54.090 --> 04:47:57.689 that's kind of good. Now, here's why. And this 04:47:57.689 --> 04:48:01.509 is actually interesting. Just so much fun. This 04:48:01.509 --> 04:48:03.490 is coming from Bleeping Computer. And if you 04:48:03.490 --> 04:48:06.349 didn't know, there is a competition going on 04:48:06.349 --> 04:48:11.189 right now called Pwn2Own Automotive 2026. And 04:48:11.189 --> 04:48:14.330 security researchers have hacked the Tesla infotainment 04:48:14.330 --> 04:48:19.209 system thanks to exploiting 37 zero -day vulnerabilities 04:48:19.209 --> 04:48:23.419 on literally day one of the competition. Now, 04:48:23.439 --> 04:48:26.520 this is bad for the record for Teslas that are 04:48:26.520 --> 04:48:28.939 on the road right now, but it's good in the long 04:48:28.939 --> 04:48:30.720 run. But we'll get to this. Here's the nuts and 04:48:30.720 --> 04:48:33.700 bolts. First things first, the Synactive team 04:48:33.700 --> 04:48:36.299 successfully chained an information leak and 04:48:36.299 --> 04:48:38.939 an out -of -bounds write flaw to get root permissions 04:48:38.939 --> 04:48:42.200 on the Tesla infotainment system in basically 04:48:42.200 --> 04:48:46.080 a USB attack pattern. Basically, there's a category 04:48:46.080 --> 04:48:48.159 for USB attacks. In other words, they plugged 04:48:48.159 --> 04:48:49.880 in, they were able to take multiple vulnerabilities, 04:48:50.319 --> 04:48:53.040 chain them together, and then get access basically 04:48:53.040 --> 04:48:55.740 to root, meaning administrative access right 04:48:55.740 --> 04:48:58.819 into the vehicle. So they also chained three 04:48:58.819 --> 04:49:01.119 vulnerabilities to gain root -level code access. 04:49:01.130 --> 04:49:05.970 execution on the sony xav 9500 es digital media 04:49:05.970 --> 04:49:08.689 receiver remote code execution basically means 04:49:08.689 --> 04:49:10.709 they can launch code through this and obviously 04:49:10.709 --> 04:49:13.569 have the sony uh do things it should not be doing 04:49:13.569 --> 04:49:18.909 etc etc now team fuzzware .io hacked a lp tronic 04:49:18.909 --> 04:49:23.349 hyc 50 charging station an autel charger and 04:49:23.349 --> 04:49:28.549 a kenwood dnr 107 xr navigation receiver obviously 04:49:28.549 --> 04:49:35.909 all in the vehicle not Team Pedoworks chained 04:49:35.909 --> 04:49:38.470 three zero -day bugs to gain root privileges 04:49:38.470 --> 04:49:43.229 on a Phoenix Contact CH -ARX SEC 3150 charging 04:49:43.229 --> 04:49:47.009 controller. Team DDoS hacked the ChargePoint 04:49:47.009 --> 04:49:50.250 HomeFlex, the Autel Maxi Charger, and the Grizzle 04:49:50.250 --> 04:49:54.029 E Smart 40A vehicle charging station. And that 04:49:54.029 --> 04:49:57.110 was on day one. And this also means that there's 04:49:57.110 --> 04:49:59.590 been hundreds of thousands of dollars of payouts 04:49:59.590 --> 04:50:02.930 for successfully hitting this Tesla in so many 04:50:02.930 --> 04:50:05.590 different ways. Now, for the record, vendors 04:50:05.590 --> 04:50:08.069 have 90 days, and this is why it's good. They 04:50:08.069 --> 04:50:10.549 have 90 days to develop and release a security 04:50:10.549 --> 04:50:13.330 fix before Trend Micro's zero -day initiative 04:50:13.330 --> 04:50:17.049 publicly discloses them after basically the zero 04:50:17.049 --> 04:50:19.810 -day flaws are exploited and then reported during 04:50:19.810 --> 04:50:23.209 the Pwn2Own contest. The clock is ticking for 04:50:23.209 --> 04:50:26.419 Tesla to actually improve their vehicles. create 04:50:26.419 --> 04:50:28.680 software patches, harden these things, and that 04:50:28.680 --> 04:50:30.500 also means that Sony has to go back to the drawing 04:50:30.500 --> 04:50:32.060 board, Kenwood has to go back to the drawing 04:50:32.060 --> 04:50:34.819 board, Autel has to go back to the drawing board 04:50:34.819 --> 04:50:37.319 to figure out patches and basically to close 04:50:37.319 --> 04:50:40.840 these flaws. That's the good sign of this. And 04:50:40.840 --> 04:50:43.279 the thing is, when these are published, exploits 04:50:43.279 --> 04:50:44.799 are published, whether it's the CVE database 04:50:44.799 --> 04:50:47.639 or another database, the actual code that they 04:50:47.639 --> 04:50:51.139 use is in there, meaning I can copy, paste, and 04:50:51.139 --> 04:50:54.599 essentially execute some kind of attack against 04:50:54.599 --> 04:50:58.419 a Tesla vehicle in this way. That's why Tesla 04:50:58.419 --> 04:51:00.400 is going to move as fast as they can, as is Sony, 04:51:00.479 --> 04:51:03.000 etc., to basically harden and lock these things 04:51:03.000 --> 04:51:05.299 down. That's why it's good in the long run. That's 04:51:05.299 --> 04:51:08.900 why we do these kinds of competitions in the 04:51:08.900 --> 04:51:12.580 cybersecurity community. And the Pwn2Own Automotive 04:51:12.580 --> 04:51:16.020 2026 Hacking Contest focuses on automotive technology 04:51:16.020 --> 04:51:19.099 specifically, and it's taking place. Today is 04:51:19.099 --> 04:51:21.540 day one, but it's ahead of us in time because 04:51:21.540 --> 04:51:24.860 it's in Tokyo, Japan this year. at the automotive 04:51:24.860 --> 04:51:27.799 world conference so it goes through the 23rd 04:51:27.799 --> 04:51:29.979 we're going to see more flaws come out on more 04:51:29.979 --> 04:51:32.900 vehicles but tesla being one of the largest ev 04:51:32.900 --> 04:51:36.020 makers in the world behind byd basically has 04:51:36.020 --> 04:51:38.849 a lot of work to do and quite frankly I hope 04:51:38.849 --> 04:51:41.110 they do it because the last thing I want to see 04:51:41.110 --> 04:51:43.529 is somebody hack into a Tesla and drive it into 04:51:43.529 --> 04:51:46.130 a tree or shut it down. And we've seen a lot 04:51:46.130 --> 04:51:49.169 of vehicles over the years with flaws that we 04:51:49.169 --> 04:51:51.770 can execute on to either gain root access or 04:51:51.770 --> 04:51:54.270 remote code execution or anything like that. 04:51:54.349 --> 04:51:58.110 My own self included, basically every. car i've 04:51:58.110 --> 04:52:00.470 owned since the uh since the bluetooth era i've 04:52:00.470 --> 04:52:02.950 been able to get into in some way shape or form 04:52:02.950 --> 04:52:06.090 but fortunately the over the wire updating that 04:52:06.090 --> 04:52:08.409 tesla and now more on automotive manufacturers 04:52:08.409 --> 04:52:12.360 have is a good thing to basically fix these flaws 04:52:12.360 --> 04:52:14.520 i can't tell you for years how many times i would 04:52:14.520 --> 04:52:16.740 take a car in knowing that i had been able to 04:52:16.740 --> 04:52:18.759 compromise it through the head unit and basically 04:52:18.759 --> 04:52:20.619 there were no updates for the manufacturers once 04:52:20.619 --> 04:52:22.560 it rolled off the lot they washed their hands 04:52:22.560 --> 04:52:25.340 of it not anymore and that is good in the age 04:52:25.340 --> 04:52:27.680 of hacking so there you go your tesla vehicle 04:52:27.680 --> 04:52:31.299 has flaws hopefully not for long And please like, 04:52:31.340 --> 04:52:32.860 share, follow me here on Facebook and Twitter 04:52:32.860 --> 04:52:34.939 at NickAESP. And please feel free to subscribe 04:52:34.939 --> 04:52:36.659 to me at YouTube as well. And as always, stay 04:52:36.659 --> 04:52:38.900 safe, stay online, and please, please, please 04:52:38.900 --> 04:52:41.180 attempt to stay private, informed, and secure. 04:52:41.720 --> 04:53:08.380 Take care. Would you like to join us on the security 04:53:08.380 --> 04:53:12.919 box email list? Several of us will post articles, 04:53:13.119 --> 04:53:16.419 several may comment on the articles, and you're 04:53:16.419 --> 04:53:19.240 welcome to join us to talk about what interests 04:53:19.240 --> 04:53:23.540 you. Post articles, join the discussion, and 04:53:23.540 --> 04:53:27.099 maybe learn something that you might not have 04:53:27.099 --> 04:53:31.680 learned before. The subscription process is fairly 04:53:31.680 --> 04:53:36.770 easy. Just send a blank email to thesecuritybox 04:53:36.770 --> 04:53:44.569 -subscribe at 986themix .com or find a link to 04:53:44.569 --> 04:53:49.529 the security box at 986themix .com under the 04:53:49.529 --> 04:53:55.409 list for social media. This service is part of 04:53:55.409 --> 04:54:21.669 986themix's email list. Come join us today. Want 04:54:21.669 --> 04:54:26.569 to join us each week? Well, join us on Team Talk 04:54:26.569 --> 04:54:33.110 on Wednesday, 11 a .m. Pacific Time, 1 p .m. 04:54:33.110 --> 04:54:38.189 Central Time, where you can participate on the 04:54:38.189 --> 04:54:44.790 live taping of The Security Box. What server 04:54:44.790 --> 04:54:48.229 are we going to be on? Great question. We're 04:54:48.229 --> 04:54:52.430 going to be on 98 .6 The Mixes. Team Talks server, 04:54:52.669 --> 04:54:59.409 whose information can be found at 986themix .com. 04:55:00.569 --> 04:55:04.189 You do need to have an account on this server, 04:55:04.389 --> 04:55:08.009 and if you don't, follow the instructions to 04:55:08.009 --> 04:55:14.869 get one. So come join us each week. 986themix 04:55:14.869 --> 04:55:19.290 .com, our Team Talks server, in the Security 04:55:19.290 --> 04:55:24.849 Box channel. And thank you so much for listening 04:55:24.849 --> 04:55:38.490 to the podcast edition of our program. We would 04:55:38.490 --> 04:55:46.610 like to thank the following podcasts and or news 04:55:46.610 --> 04:55:54.090 websites for the articles. In which we may use. 04:55:54.150 --> 04:56:01.169 Or blog. You may find links. To these. Under 04:56:01.169 --> 04:56:06.709 podcasts. And sources we use. On our website. 04:56:06.810 --> 04:56:15.069 At emailhostsecurity .com Ars Technica. Bleeping 04:56:15.069 --> 04:56:28.639 Computer. Cybercrime Radio. CyberScoop. Crabs 04:56:28.639 --> 04:56:34.580 on Security. Kim Commando, the Digital Goddess. 04:56:35.659 --> 04:56:44.340 The Cyber Wire from N2K Networks. And the Fish 04:56:44.340 --> 04:56:52.419 Labs blog. If... you have found something that 04:56:52.419 --> 04:56:55.040 is not listed here that we should be looking 04:56:55.040 --> 04:57:02.319 at, please let us know by sending an email with 04:57:02.319 --> 04:57:08.099 the link to the main webpage. You may either 04:57:08.099 --> 04:57:11.759 send your email to J -A -R -E -D -R -I -M -E 04:57:11.759 --> 04:57:18.139 -R at 986themix .com or tech, that's T -E -C 04:57:18.139 --> 04:57:29.279 -H, at menvi .org. Thanks, resources, for all 04:57:29.279 --> 04:57:33.939 you do to put the information out so we can share 04:57:33.939 --> 04:57:38.919 what you and others have to say in this industry. 04:57:39.919 --> 04:57:43.380 Thank you for listening to The Security Box. 04:57:44.080 --> 04:57:49.540 This is Jared Reimer. We hope you enjoyed today's 04:57:49.540 --> 04:57:54.840 program. And we hope to see you again on another 04:57:54.840 --> 04:58:00.759 edition of the program next time. We would like 04:58:00.759 --> 04:58:05.880 to thank the following affiliates for airing 04:58:05.880 --> 04:58:12.299 our program. The main network, 98 .6 The Mix 04:58:12.299 --> 04:58:17.419 on the Independent Channel. If you are airing 04:58:17.419 --> 04:58:20.799 our program and your network is not listed here 04:58:20.799 --> 04:58:27.080 and you would like us to give you credit for 04:58:27.080 --> 04:58:32.159 airing our program, please contact me. I would 04:58:32.159 --> 04:58:37.939 like to do my best to make sure that all affiliates 04:58:37.939 --> 04:58:45.549 get credit for airing the program. please feel 04:58:45.549 --> 04:58:49.130 free to contact me using the contact information 04:58:49.130 --> 04:58:56.630 given during the program. It is open to all listeners, 04:58:56.729 --> 04:59:03.490 no matter what network you're listening on. Now, 04:59:03.689 --> 04:59:08.110 stay tuned for a few tracks on the independent 04:59:08.110 --> 04:59:14.090 artist side to round out the podcast. See you 04:59:14.090 --> 04:59:19.709 next week. And thanks again for listening.