Hello gang, welcome to podcast 272. This is Jared and today, we're going to talk about Technical Debt. We extract one of the best laughs we can ever have on TSB and that is played at the end, and the line is part of the whole beginning too. We talk about some things from around the landscape, especially from what I have posted, so we'll keep our eyes on things. More blog posts later. More podcasts later. See you soon.
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
The opinions expressed are those of the show hosts and may not necessarily be of any company in which the show hosts may represent. The following podcast may contain some strong language. Parental discretion is advised. Welcome to the Security
Box Program 272. I'm Jared Reimer. Well, technical debt is the topic today. And it is very interesting because even I, your host, didn't really know really what this was all about. technical debt.
And we hope that you enjoy the program as much as we have bringing it to you. We talk about several of the news items that I posted. We check in to see if anything else was of value. And then, of course, In our Errata section, we go in and start pulling some things that may be
blogged in the near future. So, I hope that you enjoy the podcast as much as we brought it to you. And please take this line that Preston reads when it comes to human technical debt. As you get ready for Podcast 272. Email iMessageTech,
that's T -E -C -H, at M as in Mike, E -N -V -I dot org. Text or WhatsApp 804 -442 -6975. Or you may call the comment line at 888 -405 -7524. Now. Here is that line, read by Preston. Enjoy today's program, everybody. People slowly normalize
broken behavior. The workaround becomes standard procedure, but there is more. The failure becomes expected. The limitation becomes accepted. And eventually, nobody remembers the original problem anymore. Ugh. Welcome to TSB. This is program
272. You started with guitar tribute players getting good instrumental. 35 acoustic country hits, 2019. A 2019 release. Today, we are going
to go ahead and talk about something even I didn't know a whole lot about. And I was even lucky to get... iMessage J -A -R -E -D -R -I -M -E
-R at 986themix .com. Send a text or a WhatsApp message to 804 -442 -6975. Or call my comment line at 888 - 405 -7524. We've got one huge post.
I even posted another one this morning. May 6th. But... Sometimes you just gotta let the article speak for itself. I really think that people
should go after it. I hope that each and every one of you will enjoy the program as much as I am bringing it to you. It's going to get very
interesting. Interesting. I don't understand
what's happening here. Maybe I'm... What did
I just do here? So... As I said, we got a big story. Let's see if I can get myself... Mr. J,
am I... Audible? How are things? I must be having technical difficulties around here. Because I...
Let's... Alright, I'm trying to figure out what broke. Okay, so... Now I know what broke. Okay.
Things weren't reading right, and now I realized I didn't hit a setting. All right, let's try this again. No, I don't want sound events. Now let's see if I can get everything to work. Now... Now we're getting there. Didn't help that I was up at about 7 and didn't really want to get up,
even though I don't really want the maid to change times because of traffic coming from L .A. All right. And the only day I really need her to change is the fourth Wednesday. Because then that means I have to come, I have to get up early twice. And I really want to try not to do that because that makes two long days. Right. Okay,
Mr. J. A little bit of a rough start, but we're here. One big story. We published last week since TSB's last run. Have we heard anything else since
we ran it? sure that we have. I mean, I certainly haven't. I sort of did a glimpse this morning and I found one, but it's a completely different one. It is. The Muddy Waters. And the Muddy Waters, all I want people to know is that they're getting interesting. Yeah. No, I like just some of the
names that they've been given. Static Kitten. Ow! Don't touch the kitten! I got shocked by touching the kitten! Ow! There was another name that was really hilarious and there was like Mango something. Mango... Mango habanero something?
Yeah. It wasn't that, but... Oh, man. Yes, there was one in there. It was mango something. Mango lassie? Oh, it should have been. That would have been great for the name of a ransomware actor. But why would they... the worst pieces of ransomware
to decoy their activity. Easy. Throw them off the trail. Throw off security researchers and basically get everybody focused on the other group. You know, the... The developers of Chaos so that Muddy Waters can basically just keep
on doing what they're doing undetected. Yeah, makes total sense. I agree. That's why I asked. I wanted to hear what your thoughts are. You don't read this on a regular? No, that is true. You don't go and search it out like I do? Nope. But that does make sense. I agree. I actually
did it. Nick, I did everything. All my reports and the show notes. Yep. Wow. I've got 40s, 30s, and 20s available. Yes. And I just put together
the Day in the Life's April 30th excursion. Nice. That's 158 minutes. Maybe we'll play that after TSB. Are you interested? I still need to read
this. I was going to do it this morning, but I ended up deciding to try and take a nap because I have a long day today. So I took a bit of one. That's probably why I'm a little... Oops, I forgot to push the button. Would you like a copy of the 29 -page monthly slash quarterly report?
That's what I was trying to tell you about when you were trying to get everything set up. While I'm tempted, I'm not sure because February was so bad. Well, February was just normalized into percentages. That's part of the report. Right. But April... Which is the top half. Yeah. The
numbers are in. Um... Did... in my Metro folder. There's a one -page report I could email you. Oh, that? I'm more interested in that one, you know, because I'm sure it has, you know, a lot
of big highlights, and that's that I'm interested in. Well, it covers practically everything. Yeah. Okay. Then I can do that. Oh, it's not in that folder, Jared. It's in this one. Oh. You want
the April Accessibility Report one -page text file? Yes. Actually, instead of just shoving it in your Dropbox, I'll just do this. All right. While I do that, what's caught your attention?
Not a whole lot. Oh, I did just get a phone scam, actually, from... Advanced financial servicing again. Keyword again. Well, yes, because I actually called the legit company. And yeah, that was the first thing they said. Yeah, we've been getting complaints about that. This is a scam. Talk to
us about it, scam squad. Well, essentially, I think they're... So, do you want me to do it in the voice of Patty Keel, or do you want... Or of Christine. Of Christina. Let me see. I haven't really heard Christina much, so... Well,
then I got to give you, I got to shove some episodes up your ass. I'm subscribed, but I don't think I really pay much attention. I don't anymore. The show notes are shit these days. They don't really say anything. It says, scam squad, bank something, hub for podcasting. Okay. As an example. I mean, it's vague. Very, very vague. That's
what I'm saying. Could be anything. Yeah. I'm just using that as an example, but if you look at the podcast list, you'll see exactly what I mean. So, the way this scam works is I've been getting these advanced financial servicing quote -unquote calls, and it's, from what I can tell,
it's somebody trying to impersonate a debt collector, but there are mountains of red flags. Mountains of red flags. Well, there are tons of debt collectors, too. There are, but this shady one is doing things that most are not legally allowed to do, i .e., They sometimes give a callback number, but not always. And it always seems to change. That's
the other thing. Along with that, when they don't, it'll say, call the number shown on your caller ID. I don't think they're allowed to do that, for one. From what I know about debt collection agencies, thanks to the GPT of chat. And along with that... Go ahead. And along with that, they
use some telltale language, which is very questionable, i .e., your cooperation is required. I don't think so. Cooperation requested. Right. Well, this says required in this one, but yes, I get what you're saying. Okay. Oh, and then today, the message I got, this is a very time -sensitive and urgent matter. Well, isn't that the same
thing? Probably. Yeah, exactly. So I think somebody just plugged in crap into some... program, use an auto -dialer, and that's how I ended up with that BS. Yeah, I got a call from a guy in Virginia,
and now I'm actually thinking that he actually called my cell phone, but he said that I called him, and I said, I don't recognize the number you're calling from, but I can tell you kind of how these work. And I explained to him a little bit about places like Spoof Card and how I've played with it a little bit. I said, but it can sometimes be a lot more technical than that.
But the basis is that they use things like this to spoof a number, to make it look like... I'm calling you even though I didn't call. I don't even know who you are. Right. He's like, well, the number got blocked in my app, but I usually call people back, see if they called. So you won't hear anything from me anymore. Well, you're
not the problem, friend. You're not the problem. No. Whoever is... faking and impersonating my number is the problem. That's what I was trying to tell him. I said, I'm a tech. I can explain this, but before I could really talk about the program that I run that he could benefit from, he was gone, but I'm not going to call him back. He seemed friendly enough. And I wasn't going
to tell him the way that I work. Is that you have to contact me first. Or I get your number from somebody who you know. Right. And if you don't answer, I always leave a message. I will never just not call you. Unless... Like... There's
some technical problem, like what happened with Pressboy yesterday. I go to call him, but somehow I'm not hearing any audio anywhere. Hmm. Even when I switched settings, because it was on the setting when he was last on the air. I changed settings and I still didn't hear anything. That's... The only time. But then I'll try a second time.
And if I don't get you again, then I'll leave a message saying, sorry, I was going to leave you a message. Here's who I am. Here's what I need. Here's what company I represent. And here's what I want. Right. Okay. Okay. I kind of feel
sorry for those Scam Squad folks. They really don't know a lot. I know. Wait, there's a February Metro log in here? Why? Why did I copy these over? Copy that over. Okay. I do have the Metro
Logs folder on here, but I don't... It's not... Full February's and April's not here. Hmm. But I just sent you the attachment by email. Um... Have you seen some of the... scams coming through. Oh, gosh. Yes. They love Preston. They do. And
like I was saying in the group, why do you need to be 22? Yeah, what's up with that? I'm just going to copy it over just in case. In the latest one, yeah. And in the latest one, they don't even describe what you're doing. Yeah, that's a little... Yeah. I mean, the others are shady,
but they are at least up front about how shady they are with the whole boosting product visibility BS. Jared, you have to remember it's called this PC, not this computer. Uh -oh. So, when you hit
Windows E now, it goes into this whole recents area instead of opening the computer drive set. this PC. So I learned that you can hit Alt D and type this PC. Right. Oh. And it will open
up your drive set and show you your drives. Well, I typed this computer instead. So then it goes search, opens a web browser and starts searching. All right. Since we're talking a little bit Metro, where is... Here it is. All right. Summary. This
report summarizes accessibility observations recorded during April 2026 across both bus and rail services within the Los Angeles metro system. A total of, wait for it, 49 trips were observed. and evaluated based on the performance of onboard and external announcement systems, Mr. Ye. Okay.
Overall performance, Mr. Ye. Uh -oh. 63 % of trips were fully accessible. 20 % experienced accessibility failures. 16 % were inconclusive due to verification limitations. While overall system performance appears moderately strong,
this is primarily due to consistently reliable rail service. Bus performance remains the primary source of accessibility concerns. Oh, lovely. Ready? Uh -oh. Sure. Bus system performance. A total of 32 bus trips were observed. 44 % successful.
31 % failed. 25 % inconclusive. Wow. The most sad significant issue observed was the lack of
reliable external announcements which are critical for identifying roots and boarding independently common problems included no external announcements Announcements replaced by nonverbal indicators, such as blinker sounds. Inconsistent or partially
functioning announcements. Okay, great. Wonderful. Issues were observed across multiple lines including the 901 and the 150, indicating that this is not isolated to a single route but reflects broader inconsistencies across the bus fleet. Rail system
performance. A total of 17 rail trips were observed. 100 % successful. Rail service demonstrated consistent reliability with internal stop announcements functioning across all observed trips. While some variation exists in external or destination -based announcements, depending on vehicle type,
This did not impact overall usability, and that's only because we can't rely on that because of the mixed bag. Some of the A -line have a mix of gold cars plus the blue cars, so there's no consistency, while some of the real cars are all gold cars. So there's no real consistency.
Great. The newer fleet makes outside announcements, but they are the same as the inside announcements, which basically does us no good. Because when I transferred at 7th Street, I heard it say connection to the J line. I already knew what that meant, and that was part of the onboard inside announcement system. Key findings. Rail service continues
to provide a reliable accessibility baseline. Bus service remains inconsistent with fewer than half of trips fully meeting accessibility expectations. External announcements are the primary accessibility gap. System performance varies across vehicles,
indicating fleet -wide inconsistencies. A portion of trips could not be verified due to boarding position or environmental factors, highlighting usability limitations. Metro staff provided effective assistance when needed, though system reliability should not depend on staff intervention. Quarterly
context, February to April 2026. Mr. J? Across 133 total trips. 55 .6 % successful. 27 .8 % failed. 16 .5 % inconclusive. Trends across all
three months confirm that rail performance is consistently strong. Bus performance remains variable, particularly in external announcements. Summary. Accessibility performance across the metro system is not uniform. Rail service continues to perform reliably, while bus service demonstrates ongoing inconsistencies, particularly in external
announcements. Addressing these gaps is critical to ensuring equitable and independent access for all riders. Detailed observations are available in the attached report and logbook. Questions or requests for clarifications are welcome. And
I'm actually glad we're doing this now because parts of today's program, dealing with technical debt, will cover a little bit of transportation. So thank you for forcing me to read this now, even the one pager. Because now people will understand what we mean when we get to. the other side.
I'm trying to think. Is there anything else? I don't think so. Bad, good, indifferent. Did
we cover Scattered Spider on TSB in the latest? I think we did, but I'm not totally sure. So
the big company this time who got pilfered is a company that probably should know better. They are the oldest company still in business today. With the second oldest business being which one
that opened in 1902 according to the GPT of chat? That wouldn't happen to be Target, would it? Target is correct. Target. Some of it's... It could be called Target, but yeah, Target. Yes,
I've heard people do that. I have too. So we don't actually know when this company... Came into effect. But the latest that got breached is not their first rodeo. It's actually not their
second. No, it's not. We covered them back in 2024 when they broke. Right here on this program. I'm pretty sure I know who we're talking about. If I'm not mistaken, we're talking about our great friends at ADT. Which stands for? What?
As a trivia question this week. Didn't actually look that up, so shoot. So I'm going to say American Digital and Telegraph. Let's actually write this
down, do this right. Anyone who wants to participate, 888 -405 -7524. You said American Digital Telegraph. Yes. I believe you will find the answer within the aforementioned article. Just to give people a... because that's where I found it. We will
give you the answer next time. We will give you the answer next time. Go ahead. I don't know that I caught it in the article, but it could be there. It's the article that was linked in my write -up. Ah. Anybody can play along. It's
okay. Scattered Spider Pleads and Sentencing will be in Augusta. And we're looking at another
guy getting a possible 20 -year sentence, and we all know how this goes. This guy's been cooperating with authorities. He's been in custody already since at some point last year. It doesn't honestly matter. It's in the write -up. I already gave you this in chat. I forget the gentleman's name offhand. Before Augusta. Half the time? So, in
my write -up, I said 4 -9. Because half would be 5 -10. But since he's already been in custody for, let's just call it a year, 4 -9. I guess
we'll see in Augusto. We'll see what really happens. Did we cover the big time education breach? I think we did. I think we did. Well, at least on throwback. And actually, yeah, I think we did on here, too. McGraw Hill. McGraw Hill. Yes.
Okay. And for those who want to know more about what's going on in L .A., they missed their opportunity. to speak. Their last opportunity will be in May.
If they don't speak in this board meeting, God help them. It's not my job. Anything in the bites
of malware? I'm trying to think if there was anything, you know, that really was a standout. I mean, a lot of stuff that I saw was, you know, while interesting, I didn't think it was so newsworthy. It's like, oh my gosh, we've got to talk about it. Fair enough, fair enough. laughing at something
that's going on in another group. Sorry. You're okay. Let's just say that I think our source is using dictation and it is having a field day screwing up Herbie's name. Nice. Oops, I just...
Yeah, first it called him hubby. Now it called him hobby. It's like, what? Wow. Hi, hubby. Exactly.
Hubby actually texted me yesterday because he was asking about... He was asking about the server and the fact that I had taken the automation port because it was offered when I went to do my show on Sunday. So I gave it back to him yesterday.
Oh, I'm sorry about that. I just realized that the page numbers are wrong. Oops. It says 2472 .1. We're not on podcast 2472, Jared. That would be quite the number of broadcasts. As many broadcasts as I've been doing since 2006, it probably wouldn't
surprise me. Probably wouldn't surprise me if I've done over 2 ,400 podcasts by now. Including all of them. Music shows. Tech shows of all kinds.
Anything from Sean catch your eye? Not lately. I mean, I guess, you know, there have been a few updates. And he was kind of letting us know that he wouldn't be posting for a while, that kind of thing, but... Nothing way out of the ordinary. Alright. Well... I guess we'll, uh...
Step on the gas, and we will do a file switch. I think so. And when we come back, what is technical debt? And did you like what... Chat GPT gave me several different titles to choose from. Well,
I think, yeah. I liked what it chose when I told it to create the script after I gave it its prompt. Technical debt. The cost of, quote, We'll fix it later. Which I think is where we're headed right now. And it's not good. Yep. And then when
we get into this, you'll understand why I decided to go copy all the reports to read the one -pager on this podcast. A day in the life is going to get the full report because we need to talk about the full report. Okay. Do you need a song break?
Okay. Not sure if I do. I mean, I have some wonderful updates that look like they need to be installed. Not Windows updates, but Dell updates. But I don't know if it's... Phone updates should be just fine. Oh, no, no, no. Computer updates, not iOS. Oh, computer. They can... They'll happily
wait. True. Unless you'd like to go do that. I'm considering it. Then go do that. We'll play some tracks. Actually, it'll take a few minutes before I actually have to restart, so we can at least get started. Okay. File switch. We'll
be back in just a bit right here across the Jared Reimer Radio Network. Yep. All right. So I listened to the stupid fucker word. You did indicate that it was board two, that it was posted on, so on and so forth. So you did do that. The guy's reaction was awesome. That couldn't have been better. Because that was the same, those were the same
feelings I had. We do know that he gets food stamps, because if you recall, and I thought you would have said this, but you didn't mention this. Maybe you did that on purpose, I don't know. But if you do happen to recall, he was on the help board during the government shutdown, talking about having to leave because... He wouldn't get his food stamps and yada, yada, yada, yada, yada. So he does get those, apparently. So that's
my comments on that. And then I listened to part of the other. Maybe I'll finish it later. I did listen to some of the three -hour. I sped that shit up and got it down to like an hour and something, but I still didn't. I think it was like an hour
and a little over an hour and a half, and I got down to like 53 minutes, and I was like, eh. But I do have a few comments that I want to say, things I want to say. Where you guys were talking about developing an app, there are parts of what you guys were talking about that I certainly agree with. And while local storage might be
better in some ways, We must remember that not everybody is good with setting up their phones and backups and all that shit. So if you're going to have local storage, The problem with local
storage is that if somebody doesn't know that you have to turn on the backups and all that stuff, if their device is stolen or lost or whatever the case, or they get a new device. and they don't know how to transfer all that shit over
to the new device, then they're screwed. It was kind of like the situation that I had with Oppy, that app I used, and they are TNO, trust no one, and I... had a hell of a time getting back into my Facebook because of it and the only reason
I got into it was because I kind of told them a lie and said I didn't set that Aussie up and whatever else and I was able to get rid of that and get around it but that was the only reason I was able to do that. Otherwise, I would have lost my entire Facebook and had to create a new one. So stuff like that kind of makes me nervous.
So I don't necessarily like that. But, you know, I understand, you know, that that's the most secure. I get all that. But, you know, the problem is, you know, you have to remember that not everybody is tech savvy enough to be able to operate in
a situation like that where there's no way to recover this information if you lose access to it for whatever reason. So that's something that we have to remember and, you know, stuff like that. On to another thing that you guys were talking about within this same segment. You guys
were talking about the hospitals and everybody else who uses all these third -party programs. Stuff like that. And the thing I would say to you about that, the problem is that hospitals, doctor's offices, utility companies, take your pick, cell phone companies, whatever, everybody
has their expertise and their industry. So your medical companies, doctor's offices and all that, they don't necessarily specialize in software work, right? So doing these online chart services that most hospitals are offering now, you know.
and, you know, God knows what else, that's not their specialty. They, you know, they do their job, and then they buy third -party programs to do things that they are not equipped to do, such as, you know, software management and all of that. And so consequently, that's why you
see so much third -party stuff. I agree it would be nice if all of these third -party services that they had to use or they choose to use, it would be nice if we knew. who these people were and, you know, whatever. But, and you know, from
my recent experience with the hospital where I went, where the part of my treatment there was billed through that third provider, that imaging company. read the CAT scan and then I got billed through them and I didn't realize that that was separate so yeah I'll give you
what you're saying about all the third party stuff but unfortunately in the world in which we live in order for it to be as secure as it needs to be Everybody needs to manage all their own stuff and not use any third parties and not buy software. They need to program their own and all this kind of thing, basically. And the
big problem with that is that places like hospitals and stuff like that... who want to be able to provide these online charts and, you know, portals and all that that we have. And, you know, they want to be able to, you know, use a company that can do their billing, that understands all the
billing. standards that you have to meet to get these insurance companies to pay out. And they know how to, you know, they specialize in this where your doctor's office just treats you for whatever they treat you for and whatever else. And then they let somebody else do the stuff that they don't specialize in. And so because
of all that, that is the reason why there are so many third -party companies involved in everything we do. Welcome back to the program. Did you see
the potential for Steven? Oh boy, I think I did. So I guess... This means I must be renamed? I guess so. JR? I guess so. Chat said that would
be a perfect bit. Hey, Steven. And apparently, if you're Steven, you like... contributing to a bunch of political things. The problem is that this Steven has never donated to any political thing. This Steven has donated to a few different
things. But this one doesn't believe he donated To any political things. Yeah, certainly not to a school board or city council or any of those. No. Chat says that could be cross -contaminated
dated. Meaning they have a name. Actually, yes. They have a name, but they... Somehow got my number and put it together. I've gotten that with other political things, but what's funny is the stuff I've gotten is addressed to my dad in emails. Nice. Oh, yeah. But at least that's
not so bad. You could send it to him and be done. If he even wanted it. Yeah. But I'm saying you could. So. Well. This is one crazy show. Probably
have to go get my name legally changed to Steven now. I think that would be a good idea. Yeah, which Steven are you looking for? And I don't live in Glendale. Why? is like an hour and forever
away from here. A couple hours away from here, actually. Because I have to take the bus to Sepulveda, then get on the 183. Right. TSB 272. Technical debt. The cost of... We'll fix it later. I like
that one. That is so good. Welcome to the Security Box Podcast. This is Podcast 272. I am Jared Reimer. Today we're talking about technical debt. Now, before putting this program together, even I had heard the term many times without fully
understanding what it really meant. We hear engineers, developers... IT departments, security researchers, and even management use the term consistently. But most people outside the industry never really get a plain English explanation. So, let's fix
that. Technical debt is what happens when a person, company, agency, or development team chooses a shortcut, temporary fix, rushed deployment, incomplete implementation, or outdated system because there is not enough time, money, staffing,
testing, planning, or patience to do it correctly at the moment. Boy, that sounds like a company we know. Quite a few, actually. Hello, Mailman? Mailman? Oh, yeah. Definitely Mailman. That was bad. Microsoft? How many times through the years
have we said, this month's patch updates, you got a patch, but this might break, that might break. Those things are definitely cooked. Sometimes that is understandable. Emergencies happen. Deadlines
happen. Systems fail. People improvise. The problem comes later because eventually those temporary fixes become permanent infrastructure. That happens. The system starts charging interest. Here's what that means. There's a list of items. So this
file's got a lot of lists in here. The first item is things break more often. Microsoft. Oops. Accessibility problems pile up. Chat GPT. Talking to you. Uh -huh. Talking to you, OpenAI. I reported
findings in February. It's still broken. Can't recommend your app to any totally blind person. It's not usable. Updates become harder. Microsoft. Uh -huh. Documentation disappears. Mailman. Yep.
Staff create workarounds instead of solutions. Metro. Microsoft. Metro. Yep. Metro. How many times have I complained about your systems not working? Announcements. Yeah. Yeah. Security holes stay open, Microsoft. Oh, yeah. And eventually,
everyone forgets how the original system was supposed to work. It's supposed to work. Excuse me. There is an old saying in technology. There is nothing more permanent than a temporary fix. Yes. It said that. I love that. That was so good.
Oh, it is. That line may actually describe technical debt better than anything else. What are your thoughts on that quoted sentence? I would have to agree. And I see a percent code. Yeah, I do.
But I was going to say, I may be at the point where I'd like to restart, so I will... So should we break and allow you to do that before we get into section one? Well, no, because I can still get things hooked up on my phone so I can still hear you. Okay. Yeah. So I will do that and then
I will deal with all that wonderful stuff. Okay. We will. Push along. The intent. Was to. Do a page break here. And this way. Each section. Was on it's own. Starting on it's own page. By the way folks. If you. Do. want a copy of any
of the files and you would rather read, we are happy to send you Braille in 40 or 30 cell. If you want a particular language, Whether you want eBay or UEB, I can do it. Just let me know what
your needs are. Since we don't have a proper page break here, we'll do this. This is section number one. Accessibility. Technical debt. This is actually very interesting because chat has seen my issues and so So that's how it sort of
got everything. Because it can look back over conversations and sort of analyze everything. That's a good use, by the way, of the remember your cross -reference chats. That's how a lot of this was put together, by the way. Let's start with accessibility because this is an area where
technical debt becomes extremely visible. One of the biggest mistakes companies make is treating accessibility as something they can, quote, add later, end quote, open AI. Wait, are we really supposed to be naming companies while doing this? Oops. That almost never works well. Well, so
far, you all haven't fixed the bug. When accessibility is not built into the foundation of a product... Every future update becomes harder. Here comes another list. Every redesign becomes harder. Every screen becomes harder. Every workflow becomes
harder. Eventually, companies end up layering accessibility patches On top of inaccessible infrastructure, we have seen this repeatedly with security software. Norton? McAfee? AVG?
What else is out there these days? F -Secure? There might be a little bit of accessibility there. Trend Micro? Malwarebytes? You're accessible, but you're an interesting beast. There are antivirus
products that still remain difficult or impossible for screen reader users to navigate properly. And, in many cases, the problem is not the company hates accessibility. The problem is that accessibility was never built into the original architecture
of the software. Now years later, fixing it becomes expensive, difficult, and complicated. That is technical debt. We also something similar happened with Clubhouse. During the COVID era, many blind users joined the platform because portions of
it weren't accessible enough to use. If not all of it, I'll add. But over time, accessibility problems increased, navigation became harder, and many users eventually returned to platforms. that works more reliably. Again, technical debt. The same thing happens with websites. What is
this? Apps, kiosks, transit systems, ticket machines, and AI systems. If accessibility is ignored early, the cost of fixing it later grows larger and larger. And eventually users pay the price. If
accessibility is not built into the foundation, somebody eventually pays for that decision. So that is section number one. As Mr. Ye just rejoined
us. Yes, I did. Restart was very smooth, thank heavens, and now I'm back. Woo! And speaking of updates, there was an NVDA update that I downloaded, so that happened too. Okay. Perfect. Yep. Perfect.
Yep. It says 2472. Good job, Jared. I forgot to do a full number number section replace. Oops. That's the least of my worries. Right. But I
think I just fixed the two biggest things that I wanted to fix. Section number one, Mr. Ye, go. I think it's critical that you said what you said about companies not quote -unquote hating accessibility. Because I get it. When people are frustrated that something is all of a sudden
inaccessible or there's a new update, it is so freaking tempting in this community to just say, oh, they hate accessibility. As I told one of my buddies, I said... The company... Oh, that reminds me. I still have Michael's message still in my folder that I think I need to give you
guys from... Whoa, is it Podcast 269? Yes. Maybe I should grab that message and insert it. And it would have been inserted, I'll tell you that much. Into the podcast between the file switch. It's a little old, but I've been meaning to do it, but he's got some comments. So I will make sure that gets done. Just for those who are on
the podcast, if I don't get this released today, it will be released tomorrow. I... Promise you that. Okay? As I told Michael, he uses a Bible app, and I guess this Bible company makes the
majority of them. And let's just say it was once accessible. But now it's lackluster at best. I think I know the one he's talking about. Because I think I actually have it too. New version by any chance? Nope. Oh, it's not that one. Okay. Bible Gateway. Yeah. So he contacted them. And
I already read all this, so I'll just make it brief. The email basically was stating how it's not accessible with voiceover, and it used to be, and it's not usable. And they're giving him tap instructions on how to get... Like the Bible
selected and how to get it to play and so forth. But none of that works with voiceover running. Wow. So the company doesn't even know about accessibility. So then he posted a one -star review. On the
app store. And I guess. That led. To the. Company. Who. Apparently. Makes. All these. Various apps. And he said the same thing there. So I contacted
them, said the same thing, and they said, what's wrong? And he told them exactly what it was doing. We haven't heard anything since, but we think we've got the right path now. And should I remind everybody what happened with me with Google Docs
and iOS? Might as well. Might as well at this point. You can't use it with VoiceOver. End of VoiceOver. If you start a new document and you continue to write in it, you're good. Once you hit done, no more voiceover for you. Well, that's
just great. Even in my own temp logs, Mr. J, I would double tap and it said end of file or bottom of file. Wow. So I would write my entry. Then I gave it to chat and it goes, this entry's first. I said, I know. Never bother to write
Google about it because they don't care. Yeah, they're huge and they've got, what, six million departments it seems like. Yeah. And nobody by phone. Well, unless you want to speak to fake Google by phone. Yeah. Thank you for calling Google support. My name is William. How can I help you? You can't. But if you have a problem
with your Google account, sir, I can help you, sir. It's not with the account. It's with an app. So transfer me to the app department. And I think some of those scam operations are probably sophisticated enough that they could do that. Well, but I know the signs already, so... Alright. Are they transferred you to app department, sir?
Hello, thank you for calling Google App Support. My name is Ryan. How can I help you? Um, yes. Did you know your Google Docs app? is not accessible for people with disabilities? Sir, I did not know that, but in order to fix this problem, I will need access to your Google account, sir. No, you don't, sir. The Google app is separate from that, and you tie it into the account afterward.
End of discussion. Because that's how it works, right? They design it. Right. And you connect it to the account. And then it's usable. The account works fine. I can see all the files of
the account. Section number two, Mr. Ye. Okay.
Metro and infrastructure technical debt. Now you guys are going to understand why I decided to copy over the one -page report we read today.
Yep. Transit systems are another excellent example of technical debt. And by the way, just because I work with one Doesn't mean... That... They're bad. I'm sure they mean well. Now many of you...
That I... Many of you know... That I spend a lot of time... Evaluating... Metro systems... Announcements... Signage... Accessibility features... And writer experiences. No. You do not do that anymore. You stop that immediately, sir. The system works, sir. You prove that the system
works, sir. You're finished. That's it. now. It doesn't win your station evaluation. Oh, by the way, this isn't the report. One for five for station arrival announcements on newer stations.
I would actually give it a half a point because it only works if you're in the middle of the platform. If you're on either side, you're not getting anything. Yeah, it's bad. No, that's good, sir. That's great. We make sure you get on the right train. The signs tell you the right
train. You do not need announcements. Why am I in Phoenix? I'm not on the right train. You do not need announcements. No. We take them off. They do not do no good. They do no good. That's right. The visual indicators, those are fine. The visual indicators are fine. They have to
blow the whistle at every intersection. That doesn't do me any good. That's true. No, we scrapped that too. Okay, scammers, now you're talking about getting a bunch of people potentially killed. Yeah, great, great. Great, great. That's not
our fault they don't pay attention. And, yeah, you took off the announcements, so I don't know why I'm in Phoenix now. I thought I was on the right train. Yeah. Yeah. And one thing. Yes. Go ahead, please. Technically, you couldn't even go there because Amtrak only gets you to some
other part of Arizona, I think. Before you have to get on a bus to go to Phoenix. Yeah. But it's like, why am I now in... Glendale. North Palm Springs. Or Glendale. Glendale. There's a Glendale, Arizona. Oh, that's right. Yeah, thinking you're getting on the one to Glendale, California. And
it's like, oops. It's like, why is it taking so long to get there? I mean, I know there's traffic sometimes, but why is it taking so long? And why is it so hot? Although the winter's pretty mild. Right. Although... Now it's actually getting
pretty nasty, I think. Yeah. And one thing that becomes very obvious over time is how temporary operational decisions slowly become permanent long -term problems. Mm -hmm. Let's take announcements.
Internal. Internal announcements may work on one bus. External announcements may fail on another. One train line announces stations correctly. Another line still has missing station announcements months after opening. Sometimes systems partially
function. Sometimes they function inconsistently. Sometimes staff creates procedures to work around broken... infrastructure instead of fixing the underlying issue. Single. Okay. That is technical debt. Signage becomes another example. You may
have braille signs that do not match the printed signs. You may have outdated platform identifiers. You may have incomplete wayfinding systems. You may have accessibility information that was added
later instead of designed correctly from the beginning. And where the hell is fucking QC? Oops. Did I say that? Los Angeles is being the
crap out of Houston right now. Because I told them before this purple line opens, I want to know if signs will be checked before you install
them. And if you need somebody to read them, I'll read them for you. Once those systems spread across an entire transit network, correcting
them becomes a massive operational project. Now add budget limitations, staffing shortages, procurement cycles, contractors, software vendors, and aging infrastructure. The debt grows. And writers experience the interest payments every day. Maybe they're
going to try and get me off the system and then that's going to be the end of it. connections, confusing signage, inconsistent audio, broken elevators, temporary workarounds. Sometimes agencies
do not redesign the entire system. Wait, what? Well, what I have... Designing. Sometimes agencies do not fix the root problem. I see what happened. My display skipped. Yeah, my display skipped. I was going to say. Skip, skip, skip, skip, skip. Sometimes agencies do not fix the root problem because redesigning the entire system would be
far more expensive than maintaining the workaround, which there isn't one, by the way. So the workaround survives, which it doesn't. They want to know why people don't ride? That's why they don't ride. You know what the TSOs say? We've seen print signage mismatches. Yep. Yeah, but you
can look out the window and get that correction through your window. I don't have that choice. It's not acceptable. They can survive for years. Maybe they can sometimes survive for many decades. That is infrastructure technical. Go ahead, Mr.
J. That ends section two. Sadly, not surprising, given the other factors you included. budgets and procurement cycles, etc., etc., especially dealing with any agency that is connected to the city or state. Why don't you pick up with
security technical debt, Mr. J? Hey, happy to. So you just read it, but I might as well read off the title once again of Section 3, Security Technical Debt. Now let's move into cybersecurity. Because technical debt may be one of the biggest reasons breaches continue happening. A large percentage of breaches are not caused by some
magical elite hacker technique. Sadly, that's true. Breaches happen because organizations delay maintenance. Do you know what might... Do you know what might include? I think you... Probably meant, do you know what that might include? But that's just... Did I not... Oops, I thought I wrote that. Yeah, what I see here is, do you know what might include? I do see that. Yeah.
I was writing that. I wonder why my computer... Okay. It happens. Let's take the following examples. Yes. Let's take the following examples. Old servers remain online. We see that. Oh, yeah. We see that. Legacy software stays exposed. Definitely
see that. Go ahead. Authentication systems remain weak. Documentation becomes outdated. Yep. Mailman. Uh -huh. Permission. Yeah. Oh. Sorry. Had to
do that. That's okay. Permission. This is a pretty dangerous one, too, though. Permissions accumulate over time. Hello? Guy, what company was that? Somebody who got fired from some company? Yeah, because they still let him have freaking permissions,
and he was able to basically screw the system. Yeah, really smart, guys. Well, he got fired, and then he exfiltrated and deleted a bunch of data. Yep. And he's not the only one. We've covered a few of those. Uh -huh. Segwaying into the next one. Nobody removes old accounts. Well... We
knew that. Yeah. Old code keeps running because replacing it might break the business. Hello, hospitals? Well, I'm no different. I'm running a script. A podcast script, actually. Well, it's
across the network. But I bought it many years ago, and the guy retired. It stopped working, and somebody coaxed it to work. Mm -hmm. And it works. But how long? I don't know. Yeah, that's the problem. And the contact form I use... It's kind of old. Doesn't have modern technology built
in to deal with spam and things of that nature. But I found it. That copyright script I have has to be put in a certain way or it's broken. So yes, I'm no different. I'm admitting it. But I don't know how to write this stuff. So... It's
a little bit different. That is true. Go ahead with the paragraph. This means that eventually attackers find the weak point. We've seen this pattern repeatedly in breach reporting. Yes,
yes. A company delays upgrades because replacing the system would cost money. Another organization postpones security improvements. Because operations cannot tolerate downtime. Again, hello hospitals. Yeah, hospitals. Never can accept downtime. Yeah, right, right. But of course, again, they're in
a very difficult position because they're, like we were just saying, that cannot be allowed whatsoever. Another business continues using unsupported infrastructure because migrating away from it would take months. Hello, United States government. I knew that was coming. I knew that was coming.
I knew that was coming. I knew that was coming. And then we've got Sissa saying, oh, you need to upgrade. You need to update immediately. You need to get this patch against this new worm. But then, oh, we're not going to update. Yeah, we're going to keep running stuff that's on XP. Yeah. We'll be all right, but we're telling you
all what to do. Yep. Why do you think I'm going to stick content for as long as I can? Uh -huh. So they postpone it. And postpone it. And postpone it again. Until eventually it becomes tomorrow's headline. Which it already is. Oh, yeah. Security
debt eventually turns into breach headlines. Sometimes organizations know they have security debt. They simply cannot afford to stop operations long enough to repair it properly. Other times, leadership assumes, we'll fix it later. Then later never comes. When attackers arrive, the
accumulated debt becomes visible very quickly. And that's the end of that section. Yep, yep. The rest of my page breaks work. No, I'm still seeing a 2 ,472. Well, you're going to see that until I update files. I'm talking about the page
breaks where the sections are supposed to start. Ah, okay. You're not seeing any more percent page codes. No more of those, nope. I found the ones. We'll try and update the file tomorrow. All right. Podcasting and creator technical debt.
This is probably not me, but what did you first think of this section? Well, honestly, I'm a little surprised because the other sections, those seem totally logical, but this one, huh? Exactly. That's probably why I put it in here.
Right. You've talked to some people who you ask for something and they go, let me see if I have it. It's somewhere on my hard drive. And then it takes them 10 hours to go find it. Oh, I sometimes am one of those people. Because it's in... Some directory you never had time to sort. Oh. And
deal. Right. Terry says, oh, I've got a bunch of music that's not sorted yet. I said, get to work. I have all my independents in an independent folder. They're in Amazon, Apple, Magnetoon, CD Baby, Do It Yourself, eMusic. Do It Yourself
is for those who send to me or I find it on multiple sources and I don't know exactly where to shove it. And or it's a cycle somewhere. off of some website that somebody's using. Yeah, hello, Dogpile Audio. Yeah. Yeah, they... It's probably good.
I mean, while I am a bit bummed that it's gone because it exposed me to some pretty cool, weird audio, cybersecurity -wise, it's... linked to, I think, some pretty questionable sites. Like, there was this one song I found which I'm looking at it now and it's like, uh -oh, should not have gone there because it was on a .ru site. .ru by nature is not questionable. It's the content
on it itself. Right. The TLD means nothing. True. Although, if you're a .shop or a .top, you're a bad domain anyway. Yes, you are. .z -z -z -z -z -z -z -z -z -z -z -z -z. For transcription, it's X -Y -Z for the automated. X -Y -Z. I'm
sure that maybe there's going to be like .butt, like .butt. So, speaking of domains, Preston sent this very interesting message last week. And he sent it to me over on Google, too. And the TLD was... What? Exercise. Yoga. Yoga's correct.
I was like, you have to be fucking kidding me. Well, I'm thinking too, though, in terms of domains, if we have .top, maybe there's going to be .bottom. Yeah, it's longer, but... But maybe that's where .butt will come in to play. That's probably right. You know, there'll be a whole new generation of porn sites, maybe. Well, they already own the dot coms. They do. But hey, maybe some people
want to... Oh, they will. Dot butt, dot bottom, dot boob. Let's see. Dot pussy? Oh, I'm sure that would be in there. Oh, my. Yeah, I'm really going to go to some link sent to me from somebody who wants me to quote unquote go to the website and it's some dot pussy domain. Uh, no. Oh, no.
Hot dates dot pussy. That could get interesting. It could. Oh, yes. Speaking of that, I have been getting some of those spams. I haven't really reported on them because they're just so unfortunately part of the Internet these days. But it's a standard.
I would like you to match with me on the website. You know, my name is whatever. Like some fan or thong somebody. Oh, my. I love the ones Preston's getting these days. Those are good. I can travel to you and... Oh. So... Well, I got ChatGPT to
understand that we were fucking around with the group and not communicating with the scammer. But Terry sent this one. Did you, like, see my response? I think so. I couldn't resist. Uh,
yeah. And then Preston sent one and I had to say something. And then we all went back and forth on that one. Right. Yeah, it's like, why do... Why do we need to go on Telegram or Telecrap to get this info? Why can't we just... Why can't
you just call me? Why can't I just call you? Exactly. Actually, I did call one of those scammer numbers that texted me on my landline once. And it was some random, like I thought I heard, it sounded like somebody was at like a festival or like a drum circle and then they hung up.
It was weird. Hmm. So there's spoofing numbers too. Yeah, this was years ago, but yeah. Oh, my favorite one was the one I got from the lady on Clubhouse, supposedly named Susan, who sent
me a picture, which I don't even think was of her. I think the picture was according to what I got from... I'm trying to remember if it was... One of the apps I used, I can't remember which... Cannot remember which app it was. It would have been either Aira AI or Be My Eyes AI. This was 2018, I think, before that existed. So I don't remember what I used. What's the other one? Seeing
AI would be the third. Might have been that. Might have been that. So one of the first things it said was... picture of Alexis Texas. So it's like, that's not even you. It's somebody you stole an image from. Alexis Texas is a well -known, very well -known star in the industry. Uh -huh.
So again, that wasn't even you, Susan. It was some photo that you just grabbed from somewhere. And then I looked up that number. I don't even know where I dug deep to find this, but apparently the number she gave me, which was a Seattle area number, was the number for some payphone at some... I can't remember what it was. Well, you can go
to 411 .com or whitepages .com or any of these big name sites and do a reverse phone lookup. Oh, okay. Now let's make this personal. Independent creators build technical debt too. And honestly,
many of us do it because there simply are not enough hours in the day. I barely got this podcast done, by the way. Bullet time. Create a folder structure quickly because you need to publish an episode. You delay renaming files because
you are busy. You postpone transcript cleanup because another project appears. While I'm making it clear, I'm not cleaning up transcripts because I just don't have the time. It's automated. It's good enough. It works. Could you imagine doing that for a four to six hour program, Mr. J? Oh, geez. Like this one? Good grief. Wow. Like this
one? Yeah. No. Not sitting there for twice the amount of time to go figure it out. No. I mean, I could take it, go search for my last name, because it always screws up my last name, and go replace it. Like, do a copy and paste. Kind of like the thing I saw earlier. Herbie was now
Hubby and Hobby. Well, Hubby and I were... The Hubby Allen Show. Okay. Yeah, the Hubby Allen Show. I think I'm about to do a page break here. You copy assets into temporary directories and
promise yourself... You'll organize some later, Terry. Same page. Terry? Uh -huh? No, I had a page break coming because of my 20. Ah. Remember, it gave me one file. Okay, so the 20 cells are double the 40. Right. The 30 cells are probably...
A quarter of the 40. Right. I want my 40 back. Well, it came back. I want my 40 back, 40 back, 40 back. I want my 40 back, 40 back, 40. I want my 40. I want my 40 back, 40 back, 40 back, 40
back. I want my 40 back. So it came back. I unwrapped it out of its very wrapped packaging. And the first thing I noticed, Is that there's a dot sticking up. Uh -oh. And I said, W -T -A -F is
this. Oh, not to worry. It's just his calc. It's just his calc. So I go... Walking around with this calc out. That's why it's stuck. That's why it's stuck because that was his calc. Right. So I go to turn it on. And... I'm like, okay.
It has five, six... No, it says... Or did it say 5646 .6 SD card. Okay, this is interesting. So I hit the command to get to the menu. It's the middle dot and the... Dot one, or the up
arrow key. Right. And it said, fattery, 90%. Fattery? F -A -T -T -E -R -Y. So then I hit the down arrow to look at the options. You know, cursor, blink, whatever. Uh -huh. And then it
said... Fadio version. What the hell? So then... I go and open a file. Uh -oh. And I open like... One of these... TSB files. The centered item
was okay. Alright, well this stuff's a little annoying, but... Then I go to open up like the 2025 Cyclone list. And... I realized that I gotta go change a few settings like word wrap and a few other things, but... It wasn't reading right.
Like, instead of Aaron, it said... Like, C -E -R -R -I -N or something. I forget what it was. It was off. I'm like, okay? So... I emailed them and I said, thank you for my orbit. I just unboxed
this. And I think I have a dot problem. So that Friday. Remember, I was supposed to actually... I think it was last podcast, actually. I got the box at 4 o 'clock in the afternoon. Yep. That's what you told me. I had to ship it back
on Friday. That Friday. Hey, Amanda. Turn on Do Not Disturb for the rest of the day. So, what you're saying, Jairus, is you're going to be doing 20 self -files for the rest of eternity? I hope not. They received it last week. So, on the 30th, they received it. So, we will figure
it out. So the first one in this section was you copy assets into temporary directories and promise yourself you'll organize them later, Terry. Uh -huh. Oh, yeah, I have this Jerry and the Pacemakers somewhere on my hard drive. Somewhere on my hard drive, but... It's in my unorganized
category, and I haven't figured... I haven't found it yet. Why is... It's like, oh, I found it, but for some reason it's in my spreadsheets folder. Why is it there? For Preston's benefit, you can tell him what page you're on, Mr. G, because he has a 30. Let's see. So... Unfortunately, it says 2472, and I only found that out now.
Well, not now, but during... It's page 12. Okay. It'll be 2472 -12, and I'll get you guys corrected files on Friday. Okay. Thursday or Friday. Then six months pass. Then a year passes. Then you are searching through old folders wondering,
why did I name this file final underline, final underline, new underline 28. Oh, no. I'm sorry. Two. Two, two, two. Two. Two. I should have used CBC there, but it's okay. I can go correct that too, if you guys want. Every creator listening
to this program probably understands exactly what I mean. But that's not all. Let's continue. But before we actually continue, I've never actually done it that bad. I don't think I have either. Not until Dropbox came around when I was really able to organize a whole bunch of crap. Yeah. My SD card's that bad, though. I can't find shit
on my SD card. Oh. Holy shit. Yeah, that's a bit of a problem. Well, that's why I... Did some organization. Because I had SANS and I had everything in the route. And I'm like, why don't I just move SANS, TSB, the independent artist stuff, all into podcast. So that's exactly what I did.
So I'm fixing this problem. And it's stuck. Braille formatting. can become technical debt. Yes, it can. I'm dealing with a 20 right now, which has its own issues. I .e., when we ran into English, it put it on a separate line, mainly because
of the page. Team talk was sounding awful just now. You're good now, but wow, for a few minutes there. I wonder what Spectrum's doing. I don't know, but there was... You sounded like you were in a can or in a steel something. Not good. It
happens. When we were reading English, it actually broke it up into two lines because of the page break. Okay, so next one. Transcript correction
can become... Oh, here we go with the word separation again. I knew that was going to happen. Technical debt. Yep. That's why I'm making it clear. I'm not really going in and changing them. If I get around to looking at them and can find reasonable fixes, I can do that, but I'm not... Like, going to go through the whole thing and try and correct
every little item. No. No. Audio organization can become technical debt. I don't have that problem. I've got a whole podcast directory where all my raw files are. And I've got a directory of all of the completed files. All the merged ones. And even before I kept them long term, I always worked that way. Backup systems can
become technical debt. Even release schedules can create technical debt. You end up having to delay one recap episode. You think you're all set. Then another project overlaps. That's why Sans is becoming a problem these days. Yeah, you can say that again. Then another recording
session arrives. Did you get the other stuff done yet? I added that, by the way. You know, because I was too busy walking around with my couch out. He was walking around without a head, and somehow I pretty much had to let him know, hey, we missed a file in the transport. Well, remember, I had a hunch I missed a file in the
transport. I told you that. I know. I told you that. I know. And I knew where it was. And that was only because of the fact that I was doing customer service. But then I never turned the recorder on. But I knew that already. Then, several
unfinished projects start stacking together. Still didn't get the other stuff done yet. Eventually, the workflow itself becomes harder to manage. Now, multiply that across businesses with hundreds or thousands of employees. That is why technical debt, because such a serious long -term problem.
And that ends that section. Mr. G, welcome to TSB. Let us know what your thoughts are. Thank you. Please. Yeah, definitely. Sorry I'm a little late. Obviously, I was working and we had our first day of our statewide everyday lives conference for the Office of Developmental Programs. But yeah, I do believe technical debt is definitely a real thing. And just by listening to, you know,
the signs of what we just went through, anyone could experience technical debt. Mm -hmm. Yep.
And... Now my busy schedule. Busy schedule. These days. And before you know it, you hired me. So there's that. I hired you before all of that. I know. I know. I'm just trying to make myself accountable. That's why. I think I'm doing okay.
Do you want to comment on any of the other three sections, Miss Turgy? Yeah, just by reading it. I feel that those are definitely signs of tentacle debt. And I would say definitely disorganization
is a huge factor. Because what if you're working on a project and you thought you put something in the right directory? but somehow it got misplaced in the wrong tree item. So yeah, that's considered technical debt. I like your thinking. Okay. Mr.
Ye. I'm still looking for this Jerry and the Pacemakers stuff in this Jerry and the Pacemakers file. It's somewhere. Where? Oh, it's in my receipts folder. Why is Jerry and the Pacemakers in my receipts folder? That's not good. What else is
in here that's not supposed to be in my receipts folder? Oh, there's a... Let me see. There's a letter that I received from this company about... Oh, right. The PayPal charge that wasn't. Oops. Why did I save that there? Why did I even save
that at all is the better question. Yeah. I don't see anything on my PayPal account or my PayPi account that there was any kind of withdrawal of about $3 ,000 to buy that. Certainly don't
see anything on my credit crad either. Nope. Not here. Not on my crad. Let's see. Section
5. Now, this I thought was interesting when I asked ChatGPT, you know, go through my conversation history and come up with something for technical debt and start with an explanation of what it is. It came up with this one. AI and technical
debt. I thought that was interesting. Yeah. That's a good segue credit that we are in the generation of where we have it everywhere now. Yeah. I cannot help you, sir. That's right. But we can help
you. There is no technical debt. No. Turn off the podcast right now. The show is over. There's no technical debt. That's right. We can help you. No more podcast. We told you that already. That's right. Go ahead, keep using the Windows XP. Or Windows 9, or Windows Decrapper. Well,
that's a... Windows Decrapper is going to be in its own discussion. Right. In about a few episodes. Uh -oh. Who wants to read AI? I can do that. Okay. Go ahead, please. Artificial intelligence
may actually accelerate technical debt if companies are not careful. What do we mean here? Right now, many organizations are rushing AI products into production. Hello, McDonald's? With the... Oh, yeah, the AI hiring manager. The McHire. Yes, the... They can't get basic things right
and it's so frustrating to deal with that people are like, oh, screw it. Yeah, screw it. I'm going to go somewhere else. Yep, yep, at this point. That's, that's, that's why. We covered McHire. Oh, yes. I remember very well. Some of these systems are impressive. McHire not being one.
No, no, one bit. But chat GP not. I mean, T. It's actually pretty impressive. Yeah. Especially when I say, how come you told this person to commit suicide? Well, I'm not really built for that, but maybe this or that or the other could
get me or any other AI to do that. If you give it the right prompt, unfortunately. Yes. Go ahead. Okay. Some are useful. Some genuinely help people. Yes. Some genuinely help people. There are many organizations that are also treating AI as a
shortcut. McWoofies? Yes. Instead of fixing bad infrastructure, they layer AI systems on top of messy infrastructure. Instead of improving workflows, they automate broken workflows. Yeah, that's great. McHire? Great. And not broken.
Uh -huh. Uh -huh. No thanks. Instead of improving documentation, they ask AI to compensate for missing documentation. Oh, that always works. That always works well. Yep. Finally, In some
cases, organizations normalize hallucinations and inaccuracies because the systems are good enough, in quotes. Yeah. Yeah. Are they actually good enough? That creates a dangerous long -term situation, especially when accessibility testing, privacy protections... Moderation systems and security reviews are rushed or incomplete. No,
sir. Not good. That is perfect. What are you guys talking about? We told you to turn off the podcast. There's no problem here. The AI is doing the good things. You not say anything bad about
the AI. It's doing good things. How many of you, in all seriousness, thought that AI can now Make malware. I didn't at first. I didn't at first either. What made you guys change your mind?
Just given how easy it is to manipulate. How easy it is to basically just... pull vaults over those quote unquote safety features that are supposed to be in place to prevent that. And then the ability to basically write anything, ask it anything in any given way to get exactly
the result you want. Right. And, you know, the more things we've been seeing in the trades, I think that's also what caused our thinking to shift. Systems, Mr. G? I mean, Mr. J? Excuse
me? Okay. AI systems can absolutely create new forms of technical debt, particularly if organizations deploy them faster than they understand them. That's pretty much every organization, it seems like? Yeah, I think. I'm afraid it is. Oops. Except mine. Oops. Do you think I never go fully
AI? Yeah, micro crap. Oh yeah, with their co -pilot, which okay, sometimes is somewhat decent. I will say that, but not all the time. And did you see Some of these commercials where, like, somebody, oh, it was the pizza place. The guy.
Oh, no. The pizza place is, like, failing because, like, nobody's coming in. So he's thinking of bringing back the dollar slice. So he asks co -pilot. to look at his finances to determine if he could afford to do the $1 slice, and then everybody shows up. Oh, jeez. Oh, God. Remember that commercial? I don't remember that one, though.
I think. If I hear it, I'm going to have to tape it, even though it might not be that good quality, but I'll have to. tape that, Mr. J. Yeah, you should. Oh, definitely. And also, I mean, not technically dead here, but I think it's a little
wrong to say that it's quote -unquote creating music. No, somebody's generating a song based on input that it gave whatever AI model it was or program it was. And as we talked about on the Independent Artist Spotlight Program 400, the beats and the melodies it is using are those
that are already done. It cannot be a new one. On its own. No, it cannot. Nope. It can create you a song, and it can create you melody, and it can do a good job. But those are based on things it already has in the model. Yes. Five
minutes before Preston's brain goes. Set. Cook. Time. Cook. Time. Five minutes. I think our source has that. Our source does have that. Did have that. I don't think she does now, but... Oops. Oops. Yes, the one that our source had broke.
No more microwavable dinners anymore. I guess not. It's been that way for months. I can use my microwave. I don't have a talking one. I've got one I can use. I've had to learn the buttons and they're not labeled, but I know exactly where they are and I hit them and they work. Yeah.
But then I've got a little bit of vision. I don't know what I'd do without the vision I'd have. Probably would have to go spend that $1 ,000 microwave. Well, I mean, or... put dots over the buttons or braille over the buttons? I have, but then they fall off. Ah, yes, they do that. And Pug Pain, well, I mean, Pug Pain could work. Thankfully, it works on my oven here. We put
it on two months ago after the official movement. I put braille on my oven and the Arrow keys, the labels have fallen off. And there's only a couple of them left. Oh, jeez. Uh, section six. Human technical debt. Oh, oh boy. Can I
take this one? This sounds interesting. Uh, Yes, you can. Okay. Let me arrow down almost there. Page 17. I see it. 17. Yep, we got it. Okay. Human technical debt. Oh, boy. Here comes the
real issue. Now, here is the part many people forget. Technical debt is not only about computers. Human systems create technical debt, too. Sometimes an organization depends entirely on one person who understands how a system works. Bad idea. Yeah. Very. I said that. That's Braille 2000
right there, although that's one reason why I got into the business in 2018. Because if Bob goes boom, there's at least somebody that knows how it works. Yeah. Right. Because otherwise there'd be nobody. Correct. It's like, I don't know how that works. That looks weird. We're about to hit a list. So there is... Yep. There
is no documentation exists. No backup staff exists. No training exists. Only Bob knows how the system works. Then Bob retires or even he might decide to call it quits. It's possible he disappears. Now the organization has a crisis. That is human technical debt. Oh, and we know this all too
well. Burnout can be technical debt. Poor communication can become technical debt. Lack of documentation can be technical debt. As well as become, yeah. And over time, organizations normalize fragile systems because the systems continue functioning well enough. That may actually be the most dangerous
part of technical debt. People slowly normalize broken behavior. Workaround becomes standard procedure, but there is more. The failure becomes expected. The limitation becomes accepted. And eventually, nobody remembers the original problem anymore. I know. That was just... Yes. Yes. After
he read that, the response was classic. If there is a way you can edit, like, excerpt that out of the podcast and put that in there, it's like, so what do you think of this? Uh... Uh... Okay, so C -L -O -S -2 -4 -7 -2 -2 -7. Next line, you.
Oh, no. I -N -G. Sorry. Closing. Yes, I was going to say. But you talk about technical debt. This display is causing me technical debt. Yeah, skip, skip, skip, skip, skip, skip. No, it's not. It only skipped once. It's the words trying to fit on one line, but we're dealing with half of 40.
Oh, man. And Braille 2000 is doing it correctly, unfortunately. I don't know. I mean, based on the Braille rules, it's doing it correctly. Right? Because it's trying to figure out how to make it all work. You take a 40 cell and you divide it in half. Right. But I believe we have another
page or two to go. I know I have about two. Before we get to the closing, that was great. That was excellent, Preston. That was excellent. It was. Maybe I should try and add that to the intro.
Yeah, I think you should. Yeah. Kim, read the last sentence. And then... Yes. It was perfect, too, because neither one of us said anything, so it'll be a totally pure, clear recording. Yes. That was excellent. All right. Walking around
with my cow. That's what we think of that file, guys. Sorry. All right. It was good the first time we heard it. But even then, the first time we heard it was overdone. Like, after about half a second. And then it's like, okay, we get it. We get it. Yeah. We get it. Yeah, you're cork.
You're cork. Maybe I should play that at the end of the program. Yes. And even then, listeners are probably going, okay, stop already. We get it. technical debt is not always avoidable sometimes
emergencies require shortcuts sometimes resources are limited sometimes organizations simply do not have the ability to rebuild everything correctly all uh At once. At once. All at once. I want to make sure I read correctly and then it jumped backwards twice. But technical debt becomes dangerous
when temporary fixes quietly become permanent infrastructure. Eventually, the debt collector arrives. And the interest payment shows up as security breaches, accessibility failure, failures,
page change. See, another one of those technical debts. It said failure, then it gives me the page number, and it gives the S on the other line. Uh, And speaking of tentacle debt, we also had, well, O been like an underlined period for operational confusion. So I call that tentacle debt. A little bit. What's the letter O randomly
doing here? I thought I took that out. Nope, not on my copy. Where? So right after it was accessibility failures, broken systems. Right after broken systems. Yeah. Oh, I see what happened. I think what this was supposed to be was the bullet placement. Okay, I see where... Oh, yeah,
okay, got it. I see what's happening here. okay so i got one more thing to fix uh oh yeah so it it split the word in a weird way so it was supposed to be operational confusion yes but yeah so it's the bullet but somehow split up oh bullet so uh so oh bullet parational confusion all right let me uh I was kind of in a hurry
yesterday. I can't tell. Alright, so we were on... Is it page 19 I want to say now? No, I'm in the raw file. Right. Okay, I see it. So let's do... There. I've just fixed that. Okay, so,
operational confusion, staff burnout, I think I'm already done. I'm done. Yeah, I think so. I'm cooking. As I said, which is why I think that the security box is not, I hate to say this, going to last probably beyond 2027 early at Best.
Unless we find things that are actually of interest. Like brand new things we've never seen before. And that's not really what we're seeing, and nothing seems to change. No. It's all the same. This company... This company was breached the exact same way as the one we've talked about 15 times already. This company decided to leave
their database with sensitive information open to the internet, as did 55 others. As did 55 others we've covered through the years. Right. Staff burnout. Then we've got and frustrated users. Frustrated users. I think I'm one of those. I'm a frustrated user. I think I'm a frustrated
user and I'm burned out. Yeah. What I'm waiting for is for somebody to give some new ransomware group a name like Poached salmon. The poached salmon ransomware group. Now that I would love to eat. Yes. I'll try a half. I'll try a half.
I don't think your system really likes eating that very much, though. I've never had it poached. What would it be like? It's... Um... Well, granted, I've only had it from Gelson's. I think I've had it a few other places. It's got kind of like a softer texture from what I remember. I mean, you can still tell it's salmon. But it's... It's
a slightly softer texture from what I remember. And... It usually has some kind of sauce on it, and it's really good. Okay. Never had poached before. Never had poached eggs either. Had those, but not recently. Let me eat it. Technical debt
is ultimately the cost of delaying maintenance, planning, accessibility, documentation, and long -term thinking. Whether we are talking about software, transit systems, AI, podcast production, or cybersecurity. That lesson remains the same.
There is nothing more permanent than a temporary fix. Nice way to end it. Yes. And ChatGPT said exactly the same way. It said that is the way you should end it. That is the perfect line right there. Spot on. Spot on. This is Jared Reimer.
This is the Security Box podcast. Thanks for listening. And that leads me to the top of my 2472 29. And then, of course, we get the security box with Jared Reimer on KKMX. I love that promo.
Yeah. Gentlemen. Same here. What's closing thoughts? Well... Microcraft, get your act together. That's mine. Yeah, right. And actually, for the record, realize what technical debt you have and attempt
to do a temporary fix. No. Not a temporary fix. We need a permanent. fix. Not just some stupid patch that only sort of works and sort of solves the problem, but the app itself is still pretty broken. Now, besides the JRN issues in February
and March, has the JRN Really fallen into technical debt? Not really. Yeah, I don't think so. And that technical debt was one of those things that had nothing to do with, oh, we'll just get to this later, or oh, we'll fix this later. And
I never lost my data. All right. alpha on our
server. That had to be my best diatribe. Especially because it was scheduled to be an open forum week. Yes. That means I owe you guys an open
forum. Right? With the new format, I don't really know. Given that we're not really focusing on specific topics anymore, it's much more general concepts. You guys tell me. Do you want me to reorganize? And allow for an open forum? I don't
think there's really a need because technically we kind of do that. That's kind of what news and notes have turned into. And again, because these things are so much more general themed, I don't really think there's a need. Okay. Then I won't change it. You do not understand. We tell you no more podcast. That's right. No more
open forum at all. We don't have an open forum anymore. We haven't had any since then. Yeah. Stupid. You still should not have open forum. Okay. Technical debt. $273 ,000. Tool friction,
accessibility, and forced workarounds. Technical neglect debt. Uh -oh. Okay. Neglecting software. Hardware. Well, mainly software, I think. We'll do a definition set. I think that's important.
Because I don't even... When it mentioned this when I was talking to it, when it was helping me build these topics, by the way, I've never heard of technical neglect. I haven't either. So... We will find out together. Mr. G, thank you for your text message this morning. We now have that podcast ready to go. I just got to
do show notes for it. And then... We will read the full report. We read the one -page report into this podcast. So, a serious question. Is LA Metro as a company? I'm not talking about
me as any type of employee or other. insider type knowledge. I'm talking about me on the very outside just writing up a simple report. Are they experiencing technical debt? Without question,
yes. Yeah. Maybe still. Tell me why, Mr. J. Well, because you have... I know you weren't asking me to focus specifically on you as an employee or anything like that, but... Well, forget about me as an employee. Well, I'm not technically an employee. They could call me a contractor.
Yes. Okay, well, the way I can approach this then is to say the feedback they've been getting about, you know, the announcements and, you know, the various issues. The approach has been, oh, we'll sort of fix some of those sometimes, but it's never permanent. There's always a problem. And based on some of the reports and some of the numbers you're talking about. 46, or was it 44 % success? That's pretty terrible. In a
one month, you're talking specifically April, right? Yeah. Yes. There goes one of my podcasts, Pressboy. What do you mean? There went his brain. Yep, there it goes. There it goes. There it goes.
There goes his brain. You're talking about the 44 % success rate. Yes. Yes, that's what I'm talking about there. Yep. Yeah. There goes his phone. That's what I was... Go ahead, Mr. G. You weren't here for a majority of the podcast, so do you want to comment on any of the other
sections? Well, definitely, as I was going through, that definitely, you know, human tentacle death is a problem. Short staffing is a problem as well as the even the software is a big issue. We've already seen that. That's why, you know,
I think, you know, having all this combined is important to realize. And it's always good to have a permanent fix. Because. stopping changes will come and systems may resolve. But I think the bigger question is what are you going to do to maintain your identity? And I think they're
experiencing technical debt in terms of the way they are communicating about this cyber attack. We still don't know. Much of anything. Like I said, they lost their opportunity. Yes, they did. They have the board meeting in May. If they don't come the middle of June, that's it. It'll
be trust us or else. What other comments throughout the sections that you want to cover, Mr. G? Well,
I would say my favorite section out of all, well, every one of them was important. But I would say my favorite section out of them all was the podcast Tentacle Dent. Talk about it. I know it's always good to stay organized and beneficial, but whenever situations arise like, you know, you getting sick, you need to take time off,
you need to recruit another assistant, also known as chat GPT. I mean, I know that's adding to your workflow, but at the same time, it does help. So at least... You know. But is getting sick technically technical debt? I mean, I got sick. There was nothing I could do. No. Getting sick is not like an everyday thing. No, because
it wasn't like, I'm going to organize this directory. I'm going to put this here somewhere sometime. So how do you guys think about the way I organize your folders? I think it's good. I mean, yes, there's the roots section, which has pretty much anything under the sun. Well, I never got around to fixing that. That's fine, actually. No, that's
probably good, because some of it wouldn't quite... fit in with well it would it would be other misc is what that right right but but i've done that work in my own directory structure i don't have right bunches of shit in my root aside yeah aside from that though i think it is good i mean i got a bunch of shit in the root of dropbox A
lot of us do. I certainly do. I do too. I feel like we all do. But I mean, they're pretty easy to navigate. And I'm thankful that email alerts actually work. That way we know what's coming in, what's going out. It's just my phone. I've
been getting notifications all day. You're good. As for me, I'm glad, you know, our boss here is always on speed dial if I need a clarification on something. I was up early today, so I ended up taking an hour nap because I know I won't get one after a show. Yeah, after the security box with Jared Reimer. I love that thing. Yeah.
Let's see. else did I find that I thought maybe I'd cover, but maybe I just won't. Oh, we need to cover this. Student hacked Taiwan high -speed rail to trigger emergency brakes. Oh, jeez. Uh -oh. Yeah. The fact that they can do that, that's...
I think that popped into my Google alert, actually. Uh -oh. When I was... When I was... When I got that email earlier today. So I think I better open... That article. Instructure Hacker claims data theft from 8 ,800 schools, universities.
Do they really want me to go on a... No. On a fucking diatribe? Um, I hope not. We've been through students in education diatribes already in this series. Do they want more? Alright. Maybe they do. Maybe. Where was it? Why ransomware
attacks succeed when even backups exist? Well, they succeed because you click on shit. Yeah. That's why they succeed. And when backups exist, you can't restore anything because it's too massive. So, no, I'm not covering that. breach exposes
personal information of 119 ,000 people. Oh, geez. Do I really want to cover that one? No, it's too small. Fuck it. Much too small. Yeah. Much too small for my liking. And it's not hitting unless it becomes big news. Basically, no. I
saw a cPanel something this morning. Where did it go? Cloud Z malware abuses Microsoft phone link to steal SMS and OTPs. Oh, God. They don't
hack, they borrow. How fraudsters target credit unions. Wow. Sissa says copy fail flaw now exploited to root Linux systems. Hey, Nick. Oh, no. Just
as we suspected, Microsoft confirms April Windows updates cause backup failures. Oh, that's fun. That's... Wow. Uh -huh. Uh -huh. Oh. Microsoft D... Crapper. Wrongly flags DigiCert certs as
Trojan. Hey, Nick. Telegram mini apps. Abuse for crypto scrams. Oh, geez. Android malware delivery. Oh, here we are. Critical C panel flaw.
Mass exploited in sorry ransomware attacks. That's what I want. Holy shoot. That's the one I want. That's the one I was looking for. Wouldn't surprise
me if I started blogging tomorrow, folks. Yep, I'm afraid not. We'll schedule things left and right before the meeting. Oh, gee. My phone's gonna get pinged over lunch. This and this and this. Oh, boy. Yep. Fifteen -year -old. Detained
over French govt agency data breach. What the hell? They're in a third world country for God's sakes. Microsoft fixes remote desktop warnings
displaying incorrectly. Great. Another problem. Yeah. Oh, we covered this, right? U .S. negotiators, ransomware negotiators get four years in prison
for black cat attacks? I think so, yeah. I think so. City and digital mint? Yep. That was another... possible 20 year sentence. I think this is an update. I think this is an update. Because I
believe we covered when that came out when sentencing was coming and remember they said they were looking at 20 years? Romanian leader of online swatting ring gets four years. Oh, God. Should be 20 or
30. That's the most dangerous thing. You could ever get into. Right. Yeah. I'm talking swatting now. Swatting. Yeah. No, thank you. Jeez. FBI
links cyber criminals to sharp surge in cargo theft. We've covered Some of this. Okay. Critical C panel, WHX panel at zero day. POC now available.
Yeah. Disband nine crypto scam centers. Arrest 276 suspects. So that's why, for the moment, I'm not getting as many crypto scams. That's not the article you're supposed to read. No.
You're not supposed to read that. That's a lie. They're not telling the truth about that. All right. I've gone three pages in. I think that's big enough, right? That's plenty. Okay. I got plenty of windows open. Yep. We'll be all right. I think we're good. I think we're good. 273.
Tool friction. Accessibility and forced work around. Technical neglect debt. Why do defenses behave the way they do? 274. That's where Windows D. Crapper will come in. Security burnout. Oh, yes. The human cost of the security landscape.
Podcast 275. Like we're all going to have in the next few years. Oops. Like I'm already having because I've been in it for 20. Oops. I know. 276. Park domains, why they are bad to have. Thank you, Terry. Appreciate you, buddy. Podcast
277, local storage architecture. Why would it actually be better to build apps? Especially when you know you're handling personal information to be local storage only. Could that actually
be a good thing? Or a bad thing? Something to think about. I'm in Simple Notes, so is there any other items that I should put in the podcast
list? Let me see. Anything at all. I don't think
so. I don't think I have any more. Okay. Yeah, I can't think of anything major, but I guess we'll be monitoring. Very good. Great. I'm putting
a few tracks in. Yep. Yep. Where is that track?
There's the track I'm looking for. We're going to end with Jerry Berlongieri's Breach, which is a 14 -minute track coming from his 2003 album Alter Echo Original Soundtrack. Also, Ion Future Forever. From the 2006 -07 album, Future Forever,
Farscape, and one of my favorites that we actually used for the intro for A Day in the Life's April 30th podcast, Flying Over Blue Water, and Voyager. So we're going to play four from that album. In the aforementioned Jerry Berlongieri track.
Gentlemen. Okay. Is there anything else that you want to add before I do the file switch? I don't believe so. Nope, I don't think so. Let's go right off to the sunset, rest and recoup for a few weeks time then. Take me out. Take me out.
I shall. Folks, this has been Security Box. We say thank you for listening and participating. We know you have choices and we say thank you for choosing us week in, week out or whenever you can. That's why we call this a podcast. There's plenty of material to go around. As always, if you miss any portion of today's show, please look up Jared's Technology Podcast Network and your preferred podcast app of choice. And subscribe, share, and follow to get the latest content. And definitely stay tuned for more. You can also
bookmark jaredtech .help and email hostsecurity .com for latest in blogs, podcasts, music, and other entities. And if you do want to see what Jared's products are up to, you can go to jaredreimer .net. And you're also invited to join us every Saturday for the Thrill Buster Night on 98 .6 MX server number 3, where we give you good music, good content, and good stuff you need to learn and get yourself educated on with security hire
at 9 p .m. Eastern and 6 p .m. Pacific every Saturday, unless schedules permit. And all that. So, we say thank you for listening. Please stay tuned to the Security Box email list and all forms of communication for updates. And until we see you again, this has been Security Box. I'm Preston. He's Nick. And he's Jared at the controls. And we say thank you for listening.
Stay safe. Stay well. And stay informed. And as always, watch those links and watch your technical debt. Thank you and make it a good day. Goodbye for now. Would you like to join us on the security
box email list? Several of us will post articles, several may comment on the articles, and you're welcome to join us to talk about what interests you. Post articles, join the discussion, and maybe learn something that you might not have learned before. The subscription process is fairly easy. Just send a blank email to thesecuritybox -subscribe at 986themix .com or find a link to
the security box at 986themix .com under the list for social media. This service is part of 986themix's email list. Come join us. Want to
join us each week? Well, join us on Team Talk on Wednesday. 11 a .m. Pacific Time, 1 p .m. Central Time, where you can participate on the live taping of the Security Box. What server are we going to be on? Great question. We're going to be on 98 .6 The Mix's Team Talk server,
whose information can be found at 98 .6 The Mix. You do need to have an account on this server, and if you don't, follow the instructions to get one. So come join us each week. 986themix .com, our Team Talk server in the Security Box channel. And thank you so much for listening
to the podcast edition. of our program. We would like to thank the following podcasts and or news websites for the articles in which we may use or blog. You may find links to these under podcasts
and sources we use on our website at emailhostsecurity .com Ars Technica Bleeping Computer Cybernews .com Cybercrime Radio CyberScoop, Krabs on Security, Kim Commando, the Digital Goddess, The Cyber
Wire from N2K Networks, and the Fish Labs blog. If you have found something... that is not listed here that we should be looking at, please let us know by sending an email with the link to the main webpage. You may either send your email
to J -A -R -E -D -R -I -M -E -R at 986themix .com or tech, that's T -E -C -H at N -E -N -V -I dot O -R -G Thanks, resources, for all you do to put the information out so we can share what you and others have to say in this industry.
Thank you for listening to the Security Box. This is Jared Reimer. We hope you enjoyed today's program. And we hope to see you again on another edition of the program next time. We would like to thank the following affiliates for airing our program. The main network, 98 .6 The Mix
on the independent channel. You are airing our program and your network is not listed here. And you would like us to give you credit for airing our program, please contact me. I would like to do my best to make sure that all affiliates get credit for airing the program. please feel
free to contact me using the contact information given during the program. It is open to all listeners, no matter what network you're listening on. Now, stay tuned for a few tracks on the independent artist side to round out the podcast. See you next week. And thanks again for listening. People
slowly normalize broken behavior. The workaround becomes standard procedure. But there is more. The failure becomes expected. The limitation becomes accepted. And eventually, nobody remembers the original problem anymore. Ugh. I know. That
was just... Yes. Yes. After he read that, the response was classic. If there is a way you can edit, like, excerpt that out of the podcast and put that in there, it's like, so what do you think of this? Ugh. Ugh.
Welcome to podcast 280 Intermediate D. I'm Jared and the podcast is now available for everyone. On this podcast, the Evolution of Cyber Security, part 3: Organized cybercrime and social engineering, part 5. The podcast...
Hello gang, welcome to the security box, program 280 Intermediate E. On this program, we're covering something called PHP2Shell two vulnerabilities that were disclosed the same day. Not only that, we have a third vuln...
Welcome to Sans, episode 43 where your blood may decide to boil. I'm Jared, and this episode will cover the Newsletter that was released on October 13, 2026. On this newsletter, there will be some good news items that...
Welcome to podcast 280 Intermediate D. I'm Jared and the podcast is now available for everyone. On this podcast, the Evolution of Cyber Security, part 3: Organized cybercrime and social engineering, part 5. The podcast...
Welcome to Sans, Episode 42. Its been awhile, and this episode explains why. I hope that we can continue Sans, I'm going to start on the next issue very soon now. If you want to read the newsletter, please use this link...