 Hi, this is Allison Sheridan of the NoSylicast podcast, hosted at podfeed.com, a technology podcast with an ever so slight Apple bias. Today is Sunday, October 1st, 2023, and this is show number 960. I know everybody's playing with their new iPhones and all that and playing with the new operating systems. And I wanted to tell you just one quick thing that I'm doing differently than I've ever done before. I'm setting up my iPhone from scratch. I did essentially a clean install and I've never done that before. And it's kind of interesting because I think I actually got started using it faster than Steve did doing the transfers. So I am spending a lot of time installing new apps, but I know that I just, I've installed 8 million things. Sorry, Steve, I'm exaggerating. He says I always exaggerate, but I don't always exaggerate. Anyway, I have a ton of apps that I never use and I know it's really hard to clean them up, but I decided this time I'm gonna do it from scratch and it really wasn't that bad. It was kind of fun because it made it feel like new. Thought it was a really fun way to go. Anyway, let's get into a couple of fun things here. If you've been listening to the Nosella Cast for a long time or maybe even a short time, you will have heard me mention Stephen Getz many, many times. We became friends through the podcast, but I don't actually remember how long ago that was. I'm thinking like 10 years ago, but maybe longer. Anyway, over the years, I've leaned on him for about a zillion tech questions. I can get him to research just about anything for me. He's got a particular affinity for photography questions, but this research that he does also extends to things as complex as setting up a Synology. He helped me pick mine out. He helped me know how to format the discs. It was a lot of fun and we have a lot of fun together. We chat at least three times a day. I'm sorry, three times a week probably through Telegram. Well, you might be wondering why I'm talking about Stephen Getz so much. It's because last Friday, we got to meet Stephen Getz in person. Steve, our daughter, Lindsey, and I all traveled to upstate New York to a wedding. I realized it was two hours from Niagara Falls and that Stephen lives two hours from Niagara Falls up in Canada. So we started plotting together whether we could pull off a meetup. Did months ago, we started working on this. Now the ironic thing about this meetup is that Lindsey and her husband Nolan were in Toronto a few years ago and Stephen drove out to meet them there so Lindsey actually met Stephen before I did. Anyway, we had a great time even though we got to only spend a few hours together. I keep saying that I never expected so many crazy cool things from doing the podcast and I have to say that my friendship with Stephen is one of the most precious and unexpected of all. If you take a look at the show notes, I put a couple of photos in there so you can see us in the classic blue ponchos at Niagara Falls and one of Stephen and me just together. It was a great time and I'm so happy he took the time to meet us there. This week, I had the great pleasure of being a guest on Tom Merritt's show called A Word with Tom Merritt. It's an interesting show. He and the guest choose a single word to have a conversation about. There's no structure to speak of and it's great fun because, well, Tom, it's just great fun to talk to. We chose for our conversation the word demo and I'll leave it to you to find out where we went with that. Now I put a direct link to this episode in the show notes but I highly recommend that you subscribe to A Word with Tom Merritt in your podcatcher of choice. Now, I'd like you to take a look on the ACAST website where the link is because he published an extra episode of A Word that's audio that landed on the cutting room floor in the official episode. I have not yet listened to that part. I'm a little worried about what might be in that. Also this week, I got to play with Micah Sargent and Dan Moran on Clockwise Again, this time joined by the awesome Jeremy Burge. As always, the four panelists bring four topics to the group and this time we talked about, first of all, our favorite or least favorite macOS Sonoma features, our harrowing AppleCare stories. This one was my topic and you'll hear why. Whether we use smartphone cases and did we upgrade to the iPhone 15? Jeremy is hilarious and I adore Dan and Micah so it's an awful lot of fun. Check out Clockwise number 522 called Take That Jason Snell and you can look for that in your podcatcher of choice. Now that I'm done plugging my own appearances, I also want to plug a fantastic episode of the Kilowatt podcast with Bodie Grimm. Bart joined Bodie for part three of his awesome super awesome EV journey. Bart is a Tesla Model 3 driver and he's going to be replacing it early next year. He's gone on a quest to find a car that's at least as good as the Model 3 and yet isn't under the capricious control of Elon Musk. This episode is part three of his journey as I mentioned and it looks like he may very well have found his next car. You can find this episode at the link in the show notes or birdie at just subscribe to Kilowatt in your podcatcher of choice. A couple of years ago, Steve started having a problem with his iPhone while connected via Bluetooth to his Tesla Model Y's entertainment system. If while actively playing a podcast, he received a phone call, the iPhone would disconnect from Bluetooth, which would of course stop the podcast and it would answer instead on the iPhone's speaker. As annoying as that was, when he hung up the phone, the phone did not reconnect to Bluetooth and instead would play his podcast out of the speakerphone. This is obviously not what he wanted. He took his car into Tesla service for some other small ailment and while he was there, he asked them to check it out to see if they could figure out why the Tesla system was acting this way. They were unable to find the root cause or even reproduce the problem. Over the last few years, I've got to have a really good reason to call Steve while he's driving because I know that until he stops his car, he won't be able to get his podcast playing properly again until he ends his drive. Now, not everyone else is as courteous as me so he was often in this annoying situation. Now, to be fair, we don't get all that many phone calls but these days, but it sure did really bother him when it did happen. We did a ton of experiments with my phone in his car and his phone in my car because they're both Teslas and there seemed to be something wrong with his phone rather than his car. But for the life of us, we could not figure out what was causing it. Now, in the time he's been suffering this issue, he's upgraded his phone twice and the problem trotted along following him but we couldn't think of any more experiments to run to narrow down what was causing his frustrating behavior. This last week, we were on a plane and we just landed in Los Angeles. Steve received a phone call and did the annoyance of everyone around him when he answered it, it was on speakerphone. When he got off his call, I asked him, how did that happen? And he said, oh, my phone always answers on speaker. It's really annoying. Now, even though we hadn't talked about the problem in his car for many months, I suddenly wondered whether the two things could be connected rather than searching the internet for iPhone Tesla Bluetooth disconnect as we had been doing, which got us no help at all. This time, I searched for stop iPhone from answering on speaker. Now, it was rewarded with the opposite answer, how to enable speaker on answer, but luckily I'm clever enough to read instructions backwards. It turns out there's a setting that controls this behavior and you would simply never find it accidentally or on your own. If you have the use of your hands, you'd naturally look in the iPhone settings but this feature isn't for people without mobility challenges. Imagine you're a quadriplegic and you can't answer the phone by touching a button. Wouldn't it be swell if it just answered on speakerphone automatically? That word touch is your clue for where to look. The setting to control this function is in settings, accessibility, and then go into touch. Not nothing to do with a phone, just go into touch. Within that section, you look for something called call audio routing. When we looked at Steve's phone, call audio routing was set to speaker. The other two options are Bluetooth headset and automatic. When we looked at my phone, it was set to automatic. We changed Steve's to automatic and we were quite anxious to get home and find out whether we'd finally solved his problem. When we got home from our trip, our new iPhones 15 were waiting for us thanks to our dear friend Pat Engler who picked them up and delivered them to us while we were gone. We spent our first evening home setting up the new phones with the light. The next morning, Steve went out for a drive and he asked me to call him while he was listening to a podcast to see if we'd fixed it. The Tesla app lets me see his car, see exactly where it is and I can even see whether he's listening to audio. Not only that, I can actually see what he's playing and I can even mess with it. Like I could rewind a bunch of times or something, but I haven't taken the opportunity to just keep hitting rewind remotely to see if I can get him to lose his mind, but I could. Well, one reason I don't do it is I've given him access to my car in his Tesla app. Anyway, I digress. When I called him on the phone, he was positively giddy that the phone answered on the car's speaker over Bluetooth. And even better, when I hung up, the car's audio system resumed playing his podcast. But then I realized something. He had a brand new phone. It's possible we had fixed it, but we had not definitively done a properly controlled test. Rather than move his eSIM back to his iPhone 14 Pro to run the test, he suggested he just toggle the touch setting and accessibility back to speaker to see if it went back to the old behavior. Sure enough, that setting caused his phone to answer over the iPhone speaker, just like it says in the tin. He put it back to automatic and Bluetooth was again, happily working. Now, remember up front I said that I had done a clean install on my phone? One of the things I'm learning by doing that is I'm learning how things work again. Because each time you learn a new trick, you do it, you know, you implement it all on your phone, but then you forget it about it years later how it works. This is the kind of thing that followed Steve because he was doing the migration each time. So it would have gone away if he had done a clean install. I'm not saying anybody else should do a clean install like I'm doing, but it is very interesting to get to learn how these things work again and have to figure it out because you have to know how to do it in order to get this to work. Anyway, this is one of those obscure tips that may just help one person someday if they come across this article, but it made Steve so happy we wanted to share. It's been quite a while since I gave you an update on my seemingly never-ending battery saga with my 14-inch M1 Max MacBook Pro. I haven't talked about it because I've pretty much hit an impasse with Apple. Allow me to do a quick recap to bring everyone up to speed. I bought the MacBook Pro in October of 2021, the day they were released. Within a few months, I noticed that the battery life was nothing like the promised up to 11 hours of wireless web. After several months of working with Apple, they gave me a new battery and at the same time, they politely erased my machine. So I did a clean install of all my apps and within a very short time, my battery life was nothing like that promised. In April of 2023, I began taking metrics as I worked with Apple because it was happening again. The laptop gets around six hours of battery life on wireless web, which, you know, that's amazing compared to an Intel machine, but it's barely half of what it should be getting. I would like to, you know, we often have these views of what should be true and then a company will go, well, that's not what we really meant. In this case, every person I've talked to at Apple have said that this is not right. Something is definitely wrong. Now, my main concern is that while using the laptop, I lose about 15% per hour. But what became even more interesting during our testing was that it also loses 15% overnight when it's asleep. This happens when it's disconnected from power and all peripherals. Over 23 phone calls and visits to Apple, we've tested on different networks. We've tested with them without iCloud logged in. It happens without Time Machine. It happens with sharing services disabled. We removed all of my internet accounts. We tested it with Wi-Fi disabled. We even ran malware bytes, which was actually recommended by Apple. So I thought that was interesting. Finally, we installed a fresh version of macOS Ventura on a new APFS volume, transferred none of my apps, settings, or data, and logged into iCloud, and it lost 14% over 12 hours while asleep. Now, when it was logged out of iCloud, not out in iCloud, the MacBook Pro lost 0% overnight while sleeping. So clean install, logged into iCloud, lose 14%, not logged into iCloud, loses nothing. Seems to me that a clean install on a separate volume really pointed either to hardware or to iCloud. Now Apple seemed to agree because at that point I discovered the engineer that was working behind the scenes on this was this on the software side, and he kind of threw it over to the hardware engineering side. But that was in May, and we are no closer to figuring out the root cause than we were in April. At this point, Apple engineering have declared that the only solution is for me to do a full nuke and pave where I don't migrate any apps or settings. Now, you know, I'm a fan of that, and it's the kind of thing I would do, but they haven't given me a satisfactory explanation of why this is any different than the clean install they had me do on a separate volume. With Sonoma finally here, I think I'm probably gonna go ahead and do that nuke and pave. But I have a problem with what they want me to do after I do the clean install. They want me to install each of my apps one by one, and after each app install, run a battery test. They say this is the only way we'll know which of my apps is causing the problem. So let's do a little bit of math here. I have 181 apps installed on my MacBook Pro. We know Apple pre-installed 40 apps, which means I have to do 161 battery tests. I mean, potentially could be the first thing I installed that does it, but up to 161. I've been doing these tests overnight, which is the best way to really measure, you know, get a consistent measurement, and that's where it loses 15%. So that would mean I would have to test for 161 days. That could be as much as five and a half months of testing. As I said earlier, Apple have not given me any reason why doing a full clean install on my Mac is any different from doing it on a new volume, but I had the opportunity to talk to a friend of mine who recently retired from Apple working on the server hardware side of the business. And he said that at a very low level, there is a difference between a full clean install and just doing it on a new volume. That's the only reason I'm gonna follow their instructions. Now, Margo, the wonderful and dedicated Apple Senior Advisor, who's been with me for so many months, she suggested that we get some data before I do the reinstall of my apps that could potentially reveal something interesting for engineering. So Mac's, iPhone's, iPads, Apple Watches, and even Apple TVs can run a self-diagnostic called SysDiagnose, and the files generated are what engineering pour over to try to figure out what's going wrong. Over these many moons, Margo's been sending me what she calls a captured data, which is a file that she sends me, and it contains code to run the SysDiagnose. In all this time, I've always waited for her to send me the captured data so I can run the SysDiagnose and send the files back to her. But in my research, I've discovered that you can actually do this on your own. The reason you might wanna know about this is because if you wanna submit a bug report to Apple, adding a SysDiagnose will help them work on it for you. If they choose to look at it, of course. Now, you can search the web for instructions on how to run a SysDiagnose for your particular device. I also found a company called HCS Technology Group who published a single PDF with fabulous instructions on how to run a SysDiagnose for every Apple device I just listed. They even have pictures of the keyboard highlighting what keys to hold down or which buttons to press on other devices. Now that I know I can run a SysDiagnose on my own without waiting for Margo to send me instructions, I can run the early test she suggested. Here's what she suggested I do before I start installing apps. As soon as Sonoma's available, I create an installer file on an external drive. Wipe my entire drive. Next, install Sonoma from scratch. At this point, without doing anything else, put the Mac to sleep for enough time to see how it does in the sleep department. Now, it usually takes a couple of hours before I can tell if it's draining, especially if I started 100%. If it's down a little bit, it goes down faster, but if it's 100%, it takes a little while. So I might even have to do that first test overnight. After the first sleep test is complete, she wants me to run a SysDiagnose and send it to her. Then, and only then, she wants me to log into iCloud, then put it to sleep again for sufficient time to test whether it loses battery, run the SysDiagnose again, and send both of them to her. Now, I'll record battery levels during this process for my own record, but she says at that point, I'm free to start installing apps. On a good week, it takes me about a week to get my Mac back into fighting form with all of the settings and messing around I do. I actually made her screen share with me so I could show her my mind map of Doom, of everything I do when I do a reinstall, and she was suitably amazed at how much stuff I would have to do. Now, you've been maybe wondering how I've been able to create the podcast and enjoy my Mac happy life with my MacBook Pro, tied up doing so many battery experiments. A few months ago, I broke down on about an M2 MacBook Air. It's the only reason I haven't thrown in the towel and just lived with a $4,000 laptop getting half the battery life promised. David Roth keeps telling me to just go down to the beach and throw it in the ocean and get on with my life, but I can't quite do that. Anyway, the MacBook Air is a delightful machine, and for now my MacBook Pro is essentially a super powerful desktop computer. I'm anxious to do the new compabe of my MacBook Pro and to see if we learn anything at all. I have a feeling everything will be dandy at first and then at some point, which I won't be able to readily notice and therefore document and reproduce, things will go belly up again. I'll see you on the other side after Mac OS Sonoma is installed and I'll let you know what I learned. After I wrote up this story, Dan Wiedler wrote a comment on the blog post and he said, it was nice that Margot tried. I believe that if you send a note to Tim Cook explaining all the things you've gone through with and without support, it might get swapped out. I've seen that happen numerous times and the amount of time you've spent on it should make it a no-brainer for Apple. And Dan's exactly right. I've had problems like this before where I've begged for help from Tim Cook and it usually gets obviously sent to somebody else who can help solve the problem. So I wrote what I thought was a very carefully written short email to Tim Cook where I gave kind of the too long didn't read part so that he could just see what the problem was or his aides could see what the problem was asking for somebody to help me. I didn't ask for a new laptop. I just said, we gotta get something else. The solution isn't gonna work for me. And I would like to read to you the email I received back this time. I have gotten out before. This is what I got this time. Hello, Allison. Thank you for your recent correspondence to Apple due to the nature and complexity of technical issues Apple does not offer support through written correspondence but we have several resources for you to explore. For any queries regarding your Apple products you may also visit our official Apple support site at support.apple.com. We regret that you've experienced issues with your MacBook Pro. Although we are committed to providing the best experience to our customers Apple does not warrant that the operations of the product will be uninterrupted or error-free. Technical support is available over the phone but calling Apple support at blah, blah, blah, blah, blah help us available seven days a week. And you can also provide feedback to Apple by going to apple.com slash feedback. We appreciate your support of Apple's products and services. So in other words, pound sand. We'll see what happens next. When the first Apple Silicon-based MacBook Pros came out we had a lot of options to choose from but we had very little information on the repercussions of those decisions. The possible configurations were so vast that I wrote an article to accommodate a diagram I created called M1 Pro and M1 Max Decision Tree a diagram of every configuration. I'm rather proud of that diagram because I published it right when people needed to make the decision of what to buy. There was just one problem with my diagram. Well, it did a great job of showing you that if you say chose an M1 Pro you'd only be able to get a 14 or 16 core GPU but if you went for the M1 Max you could get a 24 or 32 core GPU. It didn't tell you whether you needed a 32 core GPU. It showed you the M1 Pro was limited to 200 gigabytes per second of memory bandwidth while the M1 Max could go up to 400 gigabytes per second of memory bandwidth. How do you know whether your applications require that much memory bandwidth? I suspect there are people out there who positively know that they need the GPU cores and or the memory bandwidth. And there are people who know they have simple needs and don't need any of those. But in between those two sets of folks sit the rest of us. Nerds that will have FOMO, fear of missing out if they buy the wrong thing. Now, while Steve does some video encoding and manages the live video show from his laptop on the road and I do a lot of audio recording obviously and some video encoding with my screencast online tutorial videos does that mean we needed double the GPU cores and memory bandwidth? Well, we feel like we're pros so we must have needed the M1 Pro Max but do we even know we need a MacBook Pro in the first place? How do we know the MacBook Air couldn't do just what we needed to do? Well, I used to be able to justify the MacBook Pro because it had four Thunderbolt ports instead of just two on the MacBook Air but they took one of my precious Thunderbolt ports away and replaced it with a MagSafe connector. I know other people love MagSafe but on a laptop that gets 20 hours battery life is it really that important to replace the more versatile Thunderbolt port that can also charge? Anyway, as it turns out because of the mess that is my M1 MacBook Pro Max's ongoing battery issues, I've had the opportunity to use the M2 MacBook Air I bought as my primary laptop and the MacBook Pro has been relegated to that desktop position for now. The good news is that my M2 MacBook Air is a hearty little machine that can honestly do everything the MacBook Pro can do albeit just slightly slower on only the heaviest lifting. In my world, heavy lifting consists of transcoding audio from uncompressed multi-track recordings down to mono, mono compressed files I should say, processing audio for noise removal, transcribing audio with large language model artificial intelligence and transcoding screen flow video files to compressed versions. So I ran five tests on the MacBook Pro and the MacBook Air to compare speed. Let's talk first about the specs of the two machines so you understand the context of this. The MacBook Pro is an M1 Max Apple Silicon processor because I knew I needed that. So it has a 10 core CPU, 24 core, I'm sorry, 10 core CPU, 24 core GPU, 64 gigabytes of RAM. It's got that 400 gigabytes per second of memory bandwidth that I'm positive I needed. And the price out the door with a four terabyte SSD and AppleCare was around $5,000. Yeah, just a minute ago I said 4,000 but it was really $5,000. So the specs on the MacBook Air in comparison are an M2 where the other one was an M1 but it's an M2 Apple Silicon processor, no Max, no Pro, just plain old M2. It has an eight core CPU. So 20% fewer than the MacBook Pro. It has a 10 core GPU, less than half the cores of the MacBook Pro. It's only got 16 gigabytes of RAM which is a quarter of what the MacBook Pro has. And that memory bandwidth, it's only a hundred gigabytes per second not 400 like the MacBook Pro. Price out the door with a two terabyte SSD and AppleCare was $2,500. So I'm comparing a $5,000 machine to a $2,500 machine with a lot lower specs. For the audio and coding timing tests, I used the audio from my Mac stock presentation which was 25 minutes long and it was a little bit over 50 megabytes. For the video transcoding test, I used a 1.2 gigabyte screen flow file about the application shotter. So I ran hush to reduce the noise. I ran the small language model from Mac Whisper to do a transcription. Then I ran the large language model from Mac Whisper to do the same transcription but it takes longer with the large language model. Then I transcoded the uncompressed audio to an M4A using Hinedberg. And finally I transcoded the screen cast and screen flow to a compressed MP4. The performance varied between tests in a kind of surprising way. The MacBook Pro was 33 to 40% faster than the MacBook Air on the more challenging audio tests with noise removal and transcription. But the MacBook Pro was only 18% faster transcoding that huge video file in screen flow. But there's a better way to look at this. If I add up all of the tests together, the MacBook Pro saved me a total of nine minutes. The MacBook Pro took 18 minutes for all of these tests and the MacBook Air took 27 minutes. If I take out the large language model transcription from the tests, I only save three minutes with the MacBook Pro over the MacBook Air. So let's recap. The MacBook Pro cost me twice as much money. It has more CPU cores, more than double this GPU cores, four times as much RAM and four times the memory bandwidth. And on my most challenging work, I saved less than 10 minutes. It's also important to note that every one of these operations is something I run in the background and I'm able to still keep using my Mac while it's churning away. The MacBook Air is a delightful machine to carry around on travel and moving about the house. It has a smaller screen than the 14-inch MacBook Pro but it's not that much small. It's only six-tenths of an inch smaller because the 13 is really a 13.6. But you know, so in any case, I don't miss that extra inch. Now it does have one fewer Thunderbolt port, boo. And it doesn't have HDMI and it doesn't have an SD card slot which doesn't bother me at all. The one thing that is a downside of the MacBook Air is that it only goes up to a two terabyte SSD. I have a huge photos library. Between photos and video, it's over 100,000 items and so I can't keep the originals on the disk of the MacBook Air. So I ask you, am I a pro or am I not a pro? I'm pretty sure I don't need a MacBook Pro and I'm 100% certain I don't need that Mac's processor at all. So ask yourself, next time you're gonna buy a machine, do you really need a MacBook Pro or would a lovely little MacBook Air be a great machine for you? And I should point out that right now I'm recording this podcast, the live show with all of my equipment plugged in. I've got an external display attached. I've got an iPhone being used as my camera. I've got a light attached. I've got an XLR microphone with an XLR interface. I'm running Thunderbolt through a Thunderbolt dock and this little MacBook Air has not choked at all. So it really does do everything I need. If you enjoy the no silicast, chitchat across the pond or programming by stealth or all three and you find that you get value out of the shows, it would be terrific if you would consider supporting the show financially. Turns out servers, software and hardware to make the show are not free. So the folks who donate regularly through podfee.com slash Patreon and those who do one time donations through podfee.com slash PayPal are those who keep the show afloat. Join them and gain my undying gratitude. Well, it's that time of the week again. It's time for security bits with BartBoo shots and I'm not going to ask Bart how he is because his voice has been flagging a little bit. So we're gonna get stuck right in without any faffin' about this week. Indeedy, well, let us start down with some follow-up from a long running story. LastPass have decided that now is a good time to force everyone to strengthen their master password. Oh my gosh, cart, horse, gone. Now we'll lock the barn doors. It's funny you should say that because Brian Krebs has chosen headline was last pass, horse, gone, barn bolted is strong password. No way. Oh, this is so funny. I did not read ahead in the show notes to see that. That is so funny. I thought it was so funny. Are they also retroactively changing the number of passes on everybody's account to what was it, 200,000 what's not? Yes, yes, but forcing a password reset and having the new default that also has the effect that that new password kicks in with the right number of rounds of PBDFK. Okay, so the seven users they have left who didn't leave after the last couple, that's great. Oh, that's disappointing. The thing to bear in mind is that if you think that there are going to be people who think that this solves the problem and they don't have to worry about the stuff in their vault that they lost, this, no effect. You still have to change all of your passwords if you want to be safe or you can trust that you're unlikely to be targeted. But yeah, I do feel lucky. Yeah, exactly. In better news, Passkeys continue their march into the mainstream. One Passroot have rolled out first class Passkeys support in their desktop iOS and iPadOS clients and their browser extensions. So you can now sync Passkeys cross-platform. So not just within the Apple ecosystem, but between ecosystems. This is nice. Because how is it between ecosystems? Because one password would run on Windows and one on the Mac. Oh, that's right. Yeah, so now you really, yeah. And of course with one password you have family sharing and stuff. It does run on Linux? I don't believe I said so because I don't think it does. Okay, okay, you said yes, right? It's probably a syncing issue here. Okay, that's good. I have got to find some other sites to start trusting to try Passkey because I have ended up in a world of hurt with Google. It's still, I often simply can't log in, but I don't think it's Passkeys that it's causing it. I had my my alicenapodfeed.com address through Google domains and I now have it through iCloud. So I don't have a login at Google for alicenapodfeed.com, but I can't get rid of it. So I go into, I go to Google, some Google service and it says, okay, alicenapodfeed.com and I have to say no, open a different account and I say, okay, do a different account. It says, okay, do you want to use your Passkey? Yes, I want to use my Passkey. It says you don't have a Passkey for alicenapodfeed.com and I get stuck in this circle and sometimes I break out or break in, I can get it to work and then sometimes I can't. I wonder where that stuck because that is your browser is remembering and now dead account. Yeah, well, it's not so much my browser. Google still thinks it exists. It's still there in some vampire zombie mode and I need to spend some quality time in Google. It's just like with Microsoft, I accidentally created a business account and backed out and I can never get rid of that. So I always have to bypass it and go know my personal account because there is no business account. And I think I need to spend some quality time in Google trying to figure out how to get rid of alicenapodfeed.com. Yeah, because you moved the domain but you didn't delete the Google account. Right. So that means that the account does exist. Well, you don't have a login to it. Should be exactly like you left us. Yes, I agree. Should be, okay, yeah, okay. Oh, and if you could do password reset. But because of the passkey, that's how I run into trouble. If I could just enter my password, which I can eventually get it to give me but I have to fight my, I'm just like climbing through jungle stuff. So I swear at passkeys every time and I don't think it's passkeys fault. GitHub, that's your chance to do passkeys on a nice site. Okay, I'll try that. And an important one. So there you go. Yeah, well, good news. One password across. So this is all with iOS 17 and up. This is, that's 17. Yeah, so the iOS, yeah, the iOS and the iPad versions are for iOS 17 plus and the Mac version, I'm not, I think the Mac version is the last two versions of Mac OS if memory serves and then the browser plugins are the browser plugins. Okay, cause I know when I, I'm still on Ventura and I did get offered something about one password and passkeys and I went, and I closed the window. You're right. Yeah, so that proves it cause I did too and this machine has not been upgraded because this is my podcasting machine and you do not do this one early. My work laptop was updated last thing Friday. So tomorrow morning, I would have to have a great day and work with a new OS or a very bad Monday morning. One of the two. Wow, our work laptops were always the last thing on earth. In fact, there's probably still Windows XP machines where I used to work. Oh no, everyone else in works is not updated. I'm the guinea pig. Okay, good. I work in IT, I get to go first. Oh, I worked in IT and I wouldn't. Anyway, we don't want to go down that rat hole. No. All right, do we have a deep dive? We have two. So we're doing bad news, good news I guess. So deep dive one is about a fairly nasty bug. Now, I do get to say TLDR, too long didn't read. If it's an app, the talks of the internet, make sure it's fully patched. That is really the takeaway here, patchy, patchy, patch patch, right? If it doesn't matter if it's a browser, if it's any other app, if it's asking you for an update and it in any way talks to the internet, just say yes now because there is a very low level open source library called Lib Web P and the web probably gives away that it likes to talk to the internet. It's actually a Google thing which they have succeeded in convincing Apple and others to start using. It's an image codec designed to be better for the internet because it is, and I quote, a modern image format that provides superior, lossless and lossy compression for images on the web. Using WebP, webmasters and web developers can create smaller, richer images that make the web faster. WebP lossless is 26% smaller than PNG and WebP lossy is 25 to 34% smaller than JPEG. Wow. This is quite good by the sense of it. That sounds great. Yeah. Problem is, Lib WebP had a nasty bug in it and people didn't know that's where the problem was. So two weeks ago, we talked about Pegasus making a very unwelcome return and we said that Apple had patched Safari. Apple had actually patched WebKit and what they really patched was LibP in WebKit. Google patched Chrome the next day after we recorded but they had actually patched Lib WebP in Chrome. All of the Chromium browsers then got the update from Google and then someone dug a little deeper and went, guys, why did you put the metadata of Chromium on this? This is Lib WebP. Lib WebP is used outside of Chromium. This is an open source project. And so Google refiled a brand new CVE number with the correct information and when it was scored, it got a vulnerability score of 10 out of 10. Oh geez. I didn't know they had a vulnerability score. It's a perfect bug. Yeah, that's not good. Anything above eight? So there's something called the CVSS. The, it's a standard rating for bugs and basically zero means not a problem. 10 means auga, auga, auga and anything above 8.0 is officially called critical. So when someone says a critical bug in, there's actually a number. It's an 8.0 or higher. This is a 10. Anyway, the point is it's two years, it's two weeks more patch than we would expect because for two weeks we thought it was a Chromium problem. So one password is an electron app. That got its update ages ago. As soon as people realized it was WebP, another very important piece dropped, Firefox realized they had a problem. So Firefox has now been patched as well. All the Chromium browsers have been patched but really electron apps like Discord and stuff, they've also been patched. You'd need to make sure you're on the latest versions. And then the last one people may now think of is Libra Office that also got a patch. So are you saying that electron apps are Chromium? No, well yes, actually under the hood that's so. Electron apps or JavaScript, electron apps are basically web pages stuck pretending to be an app. And the JavaScript brain of an electron app is the JavaScript brain from Chromium. So when they patched Chromium to, well two weeks ago they patched what? Chromium or? Or two weeks ago they patched Chromium and WebKit. Which would have patched the electron apps. And then electron pulls the latest version of Chromium into electron and then the electron apps would have been able to get the latest version of electron into themselves. Got that, got that. Okay, so that's why they would have been ahead of it but since it's not just Chromium, Firefox and Libra Office and other Linux distros, they didn't get it. Right, because they didn't know they didn't get it. Yeah, they thought it was a Chromium problem until Google fixed the metadata on the bug report and they was like, oh my, ooh, here we use that. We need to patchy, patchy, patch patch. A zero day, 10 out of 10 critical bug that they mistakenly let sit out there for two extra weeks. Yeah, oops. By putting the wrong label on it, yeah. So everyone was in a rush to fix it. Yeah, there's no fire extinguisher because that didn't seem quite right but you just, if you stay patched, you are fine and you have been fine. It's just, be extra careful that if there's something with a little badge saying, please update me, yes. Just say yes, it's a little bit of hassle. Always true, super always true right now. Exactly. Now, happy deep dive. We have new operating systems to play with and they have lots of fun features, which is always nice and people who don't buy new hardware get to play along too. As do people who live in countries where Apple's web store collapsed in a heap and they couldn't order their new toys until half past the hour when they were all gone. My iPhone arrives in two weeks. I ordered it the minute the store in Ireland was not broken. So, I have a watch though, so I'm happy about my watch, but I have no phone. So anyway, we all get to play the lessons. You're changing phones dramatically, but to be honest, going from a 14 Pro to a 15 Pro, I think I will have talked about this by this time in the show, but I did a clean install on my phone just so that it'll feel more different. So that tells you you're upgrading too often when you have to do something to make it feel more different. But what feels more different is some of the iOS 17 stuff. Yeah, my phone feels quite different and it's the same phone because I don't have a new phone yet. But I have managed to convince myself that my phone is small. I now mentally see my phone as small. My phone isn't any smaller than it used to be, but I'm preparing myself for my first ever Macs. Good luck. Good luck, yeah. I flinched, I almost did it. I'm very fed up with fingerprints on stainless steel. I've been busy ignoring them for years even though they've been under the hood annoying me, but apparently the titanium doesn't do that. Yeah, just don't buy the ever the midnight blue MacBook Air. When they say fingerprint magnet, I have fingers that are so dry I never have to clean my iPhone screen unless someone else's touches it. That's how dry my fingers are. And my laptop looks like a Doberman licked it at all times. It looks terrible. So yeah, they're not creating. That was my space gray laptops because I don't know why I'm really boring. Like I want a really blue iPhone and Apple never make it blue enough but on a laptop, I don't know. I just want it. Yeah. Anyway, so what's fun in the deep dive area for this? Right, so we have all the cool features but actually we also have a whole bunch of security and privacy features. And we talked about them at WWDC because they were shiny but that's the start of the summer and we're now into the fall. I don't know about you but I've forgotten a lot of stuff that Tim Cook said all of it. So I figure how's about we look at the highlights of what just arrived on our Apple devices whether we got new devices or not. So the big thing is that if you have friends and family who don't need the very advanced features of a password manager like one password you can now do almost everything through Apple's built-in ecosystem because you now have sharing of past keys and passwords within the Apple ecosystem. So you can make a group inside the key chain where you can put other Apple IDs and then you can add any password you'd like to that group or past key and then everyone in that group gets that in their key chain. So it's basically like family sharing within one password. So I thought past keys were device specific. No, they're public private key pairs and there are rules for how they are protected and one of the ways that the specs is you can protect them with a biometric so people think that they're a biometric but actually they can be shared and they are already synchronized. If you've been using past keys on the Mac for the last couple of months they have already been synchronizing between your Macs through Apple key chain. Sorry, through iCloud key chain if you enabled it and now they can synchronize to your iOS devices with iOS 17 and you can share them with friends and family within the Apple ecosystem with. But they are just public private key pairs. So I've proven that I have not gotten the hang of this yet, if I see previous comments but I know that when I've tried to use my Google login that I have to keep going through something when I try it on, like when I got my new phone I had to do something, I had to do stuff which makes sense, I wanna have to do stuff but. So unless you move that private key around in a secure way, you have to set a different private key in every device. You don't use iCloud key chain if memory serves. Oh, that's correct. Therefore you do not have anything moving your private keys for you. So you have to have a separate private key in every machine. Okay, oh good, that helps me understand it then. So if I do whatever switches need to be done over in one password, I could avoid having to do that. You could indeed, because one password can then manage the private key for you and it can move it not just between your iOS devices but it could move it to the Windows which you don't have anymore or you could share one or more of your past keys with Steve through the family share. That's cool, yeah. Yeah, yeah, that would be handy. Okay, good. Actually, yeah, so I'm really happy with that and now we have basically, it's not as many bells and whistles as one password and I'm not gonna stop you. I would never say that a business should stop using a service like one password but for a lot of people, there's now enough here in the basic ecosystem especially because they now have a plugin on Windows for Chrome as well as for Edge. So even Windows people can get into the Apple ecosystem now. So if you have an iPhone, an iPad or whatever, you can still sync your past keys to your Windows machine as long as you use Edge or Chrome. Yeah, so that's pretty good. We also have much better privacy in Safari and this is a bit of a sleeper feature because it's very difficult to make it sound exciting but Safari now has the ability to give you multiple instances of itself where, so if you think of Safari up to now, you have had a copy of Safari with a jar of cookies, a set of plugins, basically a set of everything. You can now have as many of those as you want and they do not talk to each other. It is like we used to say, use Firefox to log in as your personal self and Safari to log in as your work self. You can now use Safari profile one to be your work self and Safari profile two to be your personal self and there is no crosstalk between these profiles. So they're completely separate but they're all in the same beautiful UI. So you can have right next to each other a Google tab where you are logged in as your personal self and a Google tab where you're logged in as your work self and they are just perfectly happy with each other as long as each window is in a different profile. And that's convenient. Is that, so this is in Sonoma. Or iOS 17. iOS 17, iPadOS 17 would probably be a more likely place to try to do something like that but you can, how do you switch profiles? Is that you go into preferences and say, now I wanna be in this other profile? So you've kind of had to think of it like this. You used to have the choice between private windows and not private windows. Now in that same interface, you now have the choice of public windows, private windows or any other mention, every profile you create just shows up on that list now. It's funny, I noticed that on my iPhone, I don't ever notice it on my Mac. I'm sure it's in there, but I don't think I've ever. I haven't had a chance to create an incognito window. Right, but whatever mechanism you used to use for switching between public and not public, you can now use that to switch between your profiles. And you can even have different plugins and the different profiles and they're completely separate. They do not see each other's cookies, they don't see anything of each other. So I'm gonna use this for something that nobody else will probably think of using it for because I don't have two personas. I'm sort of me all the time everywhere and don't worry about that. But what I have a problem with is caching in Safari or in WordPress or in a web browser app where I'm making changes to my code and it's not reflecting in like either it keeps working when it shouldn't or it doesn't get fixed when it should because I've made some change. And I have a heck of a time saying no, no, I really need refresh. I could now open another Safari window and it would be a new Safari experience, right? If I had another profile. Yeah, but then you end up caching, you'd have a different cache in both profiles. So it's not really a way of helping caching. Where I think people, so it's convenient from the point of view of people who have two Microsoft accounts or two Google accounts or two Slack accounts. I mean, there's all these services that we have corporate identities and personal identities and they can now live side by side, which is nice. But there's a security angle here. So sites like Facebook, they track you around the web because you log into Facebook and you, if you were to log out every time and then browse the rest of the internet, the little Facebook buttons wouldn't be following you. Well, if you make a profile called spying evil apps and you log into Facebook in spying evil apps profile, that Facebook login is not in any other of your profiles. So you can browse the web with all the Facebook like buttons and none of them are tracking you because it's in a completely separate persona or a certain separate profile. How many identities can you have? Infinity, really. The other useful thing to do, so it is generally a good idea to have your banking stuff be completely separate from everything else in case there's some sort of cross-site scripting issue or something. So you can just make a persona called banking and in there you might do your bank and your PayPal or one or two things, but just those very few things that never log into anything else but your banking stuff in that profile, keep it nice and safe. So at the moment I use a different browser for banking but now I can just do it all in Safari with different profiles. Now, sadly, I know this happened to me and it happened to somebody else I was talking to recently. The bank that I was using, which I no longer use, uses a third party to process, I forget what it was, whether it was bank transfers or something like that. So you had to allow cross-site scripting. Well, that's perfect because, that's perfect because you can do that. Yeah, you keep it inside that one. I would say in my banking Safari allow the cross-site scripting but in all my other browsing, okay, okay, cool. And if all you do is banking, then yeah, in theory, it has access to everything you do but there is no anything else. Problem solved. Yeah, yeah. Like I say, it's not being peddled as a security feature but it's a security feature. It's a really nice way to isolate things. The other big change then is sensitive content protection has gone from a parental control to an opt-in feature for everyone. So for the last year and a half or so, if you set up an iPhone as being a child's iPhone within an iCloud family plan, you can put limitations on that child's phone. One of the limitations was it could use on-device AI to scan within messages any photos to see if they were probably nude images. And it would blur the image and it would give a very child-friendly warning saying, look, you've received this image. It's not your fault. You have nothing wrong. If you think it's wrong, by all means you can have a look. We're not gonna tattle tail on you but it makes you very good. We got help from child protection agencies and stuff with the wording. It was very nicely done. That same intelligence has now been expanded. It's not just in messages anymore. It's also very importantly, when you enable it, it also gets enabled for contact posters because you can now tell other people what to show when you phone them which is open to abuse, potential, right? So especially since there's so many spam phone calls. So you could have a contact card come up from Spamber Bob or Spamber Sally and it's a photo that you really didn't wanna see. Correct, exactly. So now this protects those, which is cool. It also protects the other thing that's been horribly abused, AirDrop. So we have had lots of issues of people on airplanes getting all sorts of stuff AirDrop.them they didn't want. So it also kicks into AirDrop. Better still, it's now an API that's available as part of the core operating system so any other app on your Mac can choose to make use of this API. So other messaging services, anything you like, any other developer can then make use of this. So because people don't like AI turned on without their permission, this is an opt-in feature. So if you would like to opt in, you go into settings, into the privacy area and you turn it on and then it will have your back in any app that uses the API and all of Apple's, all the places Apple would sensibly put it, they have put it and more and more third-party apps will start using it. So. Very cool. Oh, I like that. I did not, I don't remember hearing about that one. I'm not sure they made as big a noise about it because people conflated with the scanning stuff in iCloud, which is completely different and that that Apple got in so much hot water overdoing. So I think they're being a little quieter about it than they would otherwise. Completely unrelated feature, but people conflate things because they're not, right, we're not, yeah. So the name of it is under privacy and security, it's called sensitive content warning and it says, detect nude photos and videos before they are viewed on your iPhone, receive guidance to help make a safe choice. Apple does not have access to the photos or videos. So I can turn that on on my phone and now it's turned on for airdrop, contacts, messages and video messages. And you can allow analytics if you want, but again, that's a separate opt-out. Yeah. Again, notice the wording, careful. Yeah, notice how careful they were at the wording to say that, you know, we don't get to see what's being scanned and they're being very careful on this one, which is sensible. Another important one to remind ourselves of is the check-in feature. So this is an advanced variant of location sharing designed to solve the problem of, I am leaving my friends out, we've had a nice dinner in a restaurant, I am walking home or I am taking public transit home and we're all a little bit worried, did I make it home safely? And so instead of having to proactively check every couple of minutes as your friend's safe, you can actually have Apple sort of make the whole process smoother for you. And so the person who's doing the traveling is in full control and when you go to leave, you basically set it up. So you start a messages thread with the people you want to check in with and then you click the little plus button where the apps are. And then one of the apps in there is check-in. And when you click that, you'll be guided through a quick little wizard to sort of ask you, you know, how much do you want to share? How often do you want to share? Where is your intended destination? And then once that's done, Apple sort of take care of letting people know proactively what's going on. So when you get home safely, Apple will tell all of the people you had as your check-in people, yeah, part me at home safely. If you stop making progress towards your specified destination, Apple will proactively let the people who you're checking in with know that you've stopped making progress. If your phone, it captures extra data like your current battery level or sorry, the last scene battery level, the last scene location, all those kinds of sensible things you might want to know are also included. So it's a tweaked better version of location sharing for this specific problem. And that's now not... I really like the battery part because if your battery dies, you will look like you stopped moving. Exactly, false positive. It was at 1%. It's like, eh, she's still coming. She just let her battery die. Exactly. I mean, it is actually very important to know. So it's a very well thought out feature and that is now live. And so I think we just need to remind people about it. I didn't realize you had to start a message thread. That's kind of interesting. I just went through the process and you do have to... So there's a list of standard things that you can normally do when you hit the plus button on the left side. So it's camera, photo sticker, Apple cash, audio location, but then it says more and you have to go down into more to get to check-in, which as Bart says, it's a little yellow circle with a check mark in it. I wonder if that list updates over time to the stuff you actually use. Might, might do, yeah. I really like that interface better. The sliding sideways was always dodgy and they would get big and small and I didn't like that. Yeah, I think it looks a lot better. I always hit them while trying to do other things and they said, what, where am I? What am I? What just happened? Where's my keyboard? What? So it wasn't just me. Oh no, oh no. There's a mastodon client I have that every time I try to type, I end up suddenly in the completely wrong window because the buttons are too close to the top of the keyboard. I hate it, I hate it. Anyway, something which is more of a don't panic. People got very worried about the name drop feature. So this is this cool thing where if you take two iPhones or an iPhone or an iPad or whatever and you put them nose, you sort of touch them off each other, you can initiate a contact chair. You can basically, I think Samsung used to do this and they used to call it bumping. Well, there was a third party app that was called bump. Ah, yes. Okay, that's what it was. I knew there was a bump. Yeah, I knew there was a bump. All the cool kids used it for about a minute. I didn't have anyone to bump with, sad. Anyway, name drop is kind of a similar feature. And there was a lot of concern that what if you're in a crowd? Couldn't people just steal your contact data? Well, no is the answer. So basically Apple designed this well. So no one can name drop with you without your explicit update. Like it can't happen by mistake. You absolutely have to be an active participant in the transaction. So when you touch them off each other, it effectively starts a request, but you then have to be face ID recognized. And then you get basically an option saying receive or send and receive. So if you bump each other and both of you say receive only, then nothing will happen because no one is sending anything so that may be the end of that. If one of you choose to send and receive and the other one chooses just to receive, then you get a one way transaction. Or if you both choose to send and receive, then it goes both ways. So it is very much confused by this. Well, one of the, if you haven't gotten a chance to play with it, it's super fun. You push the two phones together and there's this sort of watery, glowy thing that happens. It's super fun. Steve and I actually turned it off because whenever we tried to show each other something on our phones, if the other person's phone was near, it would go bloop and it was actually covering the thing we were trying to show. It might be over time. It wouldn't be a problem, but it was right while we were setting up our new phones and it just kept constantly getting in our way. Probably turn it back on. My understanding is you can also do AirDrop that way, not just NameDrop. Right. Sure, but with AirDrop, again, you're proactively sending in file and then you have to choose to receive it. So it's the same concept where people are extra worried about NameDrop because it's your contact information, right? Imagine if this was done badly and you were in a crowded tube, sorry, subway tube, whatever, whether they were in London or New York or on the BART, like it would be terrible if that, all you had to do was just knock into someone while you were adjusting in a carriage or something and you had their email address, their phone number, their name. I mean, it would be catastrophic. No one should be surprised Apple did this right, but just in case it won't read. It's a shocking way. Yeah. Good, good. Apple did it right. So they are- I like the order you did those stories, that was definitely the way to go. I'm all happy and smiley. That was the intention. Lots of links in the show notes for more information, including actually Ken Ray did a nice summing up on the checklist podcast number 345, which is a cool number. So there you go. Action alerts. Apple have patched everything for a bunch of zero days. No, this is not the web P once. This is a whole different set of zero days. Oh, I was hoping you can say that was kidding. They are actively being exploited. Yeah. They're actively being exploited by spyware. No, not Pegasus. One of Pegasus' competitors called Predator, which is probably a more accurate name actually, Predator. Sounds appropriately scary. Anyway, Apple have patched all of their stuff. And so you need to be sure you're on the latest version of iOS 17, 16.7, Safari's been patched. Basically everything all over the place has been patched, including iOS 16. However, if you are too far back, right? So watchOS 9, you're fine. WatchOS 8, you are not fine. iOS 16, you're fine. iOS 15, you are not fine. In terms of the Mac, it's even further back. It was, where is it? By not fine, do you mean there's no patch form? Yep, that's what I mean. Why? Because Apple only go back one version of iOS. So it's 16 and 17. Oh. But on the Mac, they go back further. So on the Mac, it's as far back as Big Sur. So you have Monterey and Big Sur and Wine Country, Sonoma. I don't know who was, I heard say, they were joking before the keynote. Oh, yeah, Mac OS Wine Country. And then it came up and it was Sonoma. I was like, yeah, Mac OS Wine Country. So patchy, patchy, patch, patch, basically again, these are nasty bugs being actively exploited. So patch, patch, patch. Also a related story I thought it was worth mentioning is that if you are upgrading to a new iPhone 15, there is a nasty bug that will not fully brick but make your life very awkward. And there's a link in the show notes to how to unbrick your phone if you do this. But if you try to upgrade before you hit 17.0.2 on your old phone, the transfer will go terribly, horribly wrong and you'll end up in a giant big mess that you can recover from, but it won't be pleasant. Apparently the old phone has to go to 17.0.2 before you go to transfer to a new phone. Yes, so get your old phone fully patched and then initiate the process, whether you're using it through an iCloud backup restore or whatever you're doing it, make sure your old phone gets all the way to 17.0.2 before you do the transfer. Apparently Apple have proactively added a warning before you hit this exact bug. It doesn't affect every mechanism for transferring. So apparently people won't get it by accident unless you're very, very unlucky. But either way, I would say just go to 17.0.2 because there's a known issue and then you should be, you're not treading into minefield. Okay. Lindsay is getting our, Lindsay and Nolan are getting our iPhone 14s and she just, just before I got on the call, she said, should I update the phone, my old phone before, whatever the end of that sentence is, yes. Yes. Yeah. Definitely. I ended up on the virtual version of the, what is it you call it, the counter of sadness or? Yeah. Well, there's the phone call of sadness, the chat of sadness, the table of sadness is the original. Yeah. So I ended up on the phone of sadness three times before I got my watch working because I was before they had released the very latest versions of everything. And I think I may have gotten snagged up in some of this shenanigans, but it got very bad. I ended up with a watch that couldn't go forward or backward. And it just kept on saying, continue on your phone. And the phone was like, no, no watch here. Oh no. Oh no. Anyway, I got there in the end. I have a really, I'm really happy with my Ultra 2. So we are out there in the end, but it was three calls, including getting escalated, which was nice. Escalating? The person was much more knowledgeable. Anyway, another related note, there is a nice little how-to from Cult of Mac. How to reset your iPhone before trading it in or selling it so that you protect your privacy. It's not difficult. So is the Cult of Mac's article different than what Apple tells you to do? No, they just tell you in friendlier ways. Okay. All right. Moving on then to worthy warnings. This, I'm taking this as a timely reminder that you should turn on multi-factor authentication or two-factor authentication everywhere you can because passwords get leaked like there's no tomorrow. There is, ironically, a cybersecurity company called Darkbeam. And as one of the services to their customers, they track password leaks so they can warn their customers if they've been caught up in a password leak. It's like a private version of Have I Been Pwned. They forgot to password protect their database of passwords. They accidentally exposed billions with a B of username and password combinations that work from all over the internet. All sorts of data breaches previously known and not previously known. So basically, like the Yahoo one, there's loads of passwords out there now. So two-factor auth everywhere you can. Because that is your protection for this condition, Annigans. I think this is a first. There was no notable news. Everything sort of fit into action alerts and worthy warnings. Also have no top tips, no excellent explainers, but I do have an interesting insight which is a little bit of podcast listening you may enjoy. There is a fantastic NPR podcast called Fresh Air which is an interview show. So it really could be about anyone because it's talking to people who've done stuff at school. Well, the interview I'm linking to is by a new, I think she's New York Times. She did a deep expose on Clearview AI, the very controversial company that basically hoovered up everyone's faces from all of the social media and sell it to, well, they say law enforcement but it does include some rather dodgy regimes. It's a very interesting expose on what's going on. I think it's good to know. It won't make you feel happy, happy, joy, joy, but it is good to know what's going on and it's a very clear interview, not intimidating at all. So I will recommend that episode. And that set us up very well for some pallet cleansing because we definitely need it after listening to that. So I have a strange podcast recommendation. One of my favorite recent discoveries is going on hiatus. Therefore I'm recommending it to you which sounds a little strange, right? The podcast is called Patented or Patented, History of Inventions. And it's a whole bunch of half hour episodes that dive deep into the invention of something you might think of as simple, like the pencil or the refrigerator or a whole range of interesting episodes, completely timeless because these things have been around for decades or hundreds of years or whatever. So you can dig into the back catalog and thoroughly enjoy every minute of it. So the show's going on hiatus. So I figure now's a great time to scroll through the back catalog and stick into your queue, anything that takes your fancy. And then you can just enjoy it over the next couple of weeks or months, you know, road trip or whatever. If you're curious- So the invention of the refrigerator isn't going to change if you listen to it two years after that episode comes out? But precisely, I mean, we may develop a whole new refrigerator that does something amazingly different, but probably not. And even then everything in that episode is still true. It's just not the whole truth, right? They're always really, basically, the host is an interesting chap. He's called Dallas Taylor. He's a Briss who's spent most of his life in America and he's called Dallas, which means there's a very transatlantic podcast, which is why he actually constantly goes between patented and patented. He says it twice in every episode, which is always funny. But he interviews a guest who's written about the invention and it's always a, it's a very, it's a very fun sort of a tone he sets. It's very playful, casual, but you learn a lot and you don't realize you have really enjoyable shows. The final episode is completely different to every other episode, and yet is the perfect example of the show's feel. So the final episode is about the invention of a parody or a joke philosophy called residentialism, which is the philosophy that our devices are proactively resisting human progress. It is with, it's an interview with the daughter of the columnist who wrote the parody. It's fantastic. He wrote it before we had computers, so he would be swearing at his lawnmower, but the concept that our things are out to get us is it feels as true today, doesn't it? Oh, well, let's just talk photocopiers for a minute, right? We know they have evil intent. I did, this is slightly different than that, but I just saw a little quick meme on Mastodon that said that it helps to think of autocorrect as a very helpful and engaging elf that's sitting inside your phone helping you, except they just happen to be drunk. I kind of liked it. I like it, I like it a lot. All right, well, I've got a pallet cleanser for us too, and Alistar posted this in our Slack at podfeed.com.slack and the Delete Me channel, which Alistar basically owns. I sometimes try to compete and get something good, but Alistar rocks it. It's a link to a pod, sorry, an XKD cartoon, and I don't have the XKD URL unfortunately, but this really resonated to me. It's a little line drawing of a person with a phone in their hand and they got headphones on and they're thinking, I need more podcasts to listen to while doing chores. Hey, someone should do a podcast, would they just like read through a book? And then each podcast could be an episode, each chapter could be an episode. And then below it it says, every now and then I reinvent audio books from first principles. And of course there's always hover text. I've been working my way through this 1950s podcast by someone named John Tolkien called Lord of the Rings. It's a deep dive into this fictional world he created. Good stuff, really bingeable. I love it, I didn't get the hover, I always forget about that, but this also reminded me of Kyle my son Kyle, it just sees through things and says what I need to be told. I was telling him about this really cool technology many years ago, he was like 12 years old or something and I said, I saw it's this really cool thing where you record your voice and then it turns it into text and then it sends the text to someone but when it gets to the other side it comes out in audio and he said, so you mean like a phone call? Shut up Kyle, nobody likes you anyway. I was gonna say voicemail. Yeah, voicemail that would be, maybe it was voicemail he said, in any case, well this worked out and your voice actually lasted Bart, I'm sounding a little gravelly, but you sound great. Yeah, I would say I have about five minutes left by the feel of it, but yeah, perfect. Yeah, we're done, we have all of our stuff, but remember, yeah, and remember, it's extra, extra, extra important this time, stay patched, so you stay secure. All right, wait everybody, before you go, two weeks from now, we are gonna be going to see an annual eclipse in Utah and we will be gone for the weekend, so there won't be any live show, but there's also, we're gonna be gone a bunch of days, so believe it or not, I am begging for content again. I think this might be the last trip, I think so, the last one that's gonna really make it hard for me to do the show, so if you've got something you can record, I would really appreciate it, but that is gonna wind us up for this week. Do you know you can email me at alisonatpodfeed.com anytime you like, that's where you can send in those reviews. If you have a question or suggestion, just send it on over. You can follow me on mastodon at podfeed at chaos.social. Remember, everything good starts with podfeed.com. If you wanna join in the conversation, you can join our Slack community at podfeed.com slash slack, where you can talk to me and all the other lovely, no-silly castaways. You can support the show at podfeed.com slash Patreon or with a one-time donation, podfeed.com slash PayPal. And if you wanna join in the fun of the live show, head on over to podfeed.com slash live on Sunday nights at five p.m. Pacific time and join the friendly and enthusiastic no-silly castaways. If you're lucky, you get to see CNN Forbes talking in the chat room. Thanks for listening and stay subscribed.