1 00:00:02,279 --> 00:00:03,500 Hey, what's up everybody? 2 00:00:04,620 --> 00:00:06,300 What's up, what's up, what's up? 3 00:00:08,000 --> 00:00:08,680 Hey, hey, hey. 4 00:00:10,220 --> 00:00:12,500 Letting everybody in for Freedom Tech. 5 00:00:14,059 --> 00:00:15,520 Okay, we are live. 6 00:00:17,020 --> 00:00:18,220 Welcome to Freedom Tech Weekend. 7 00:00:18,360 --> 00:00:19,240 My name is Marks. 8 00:00:20,300 --> 00:00:23,820 This is actually the final episode of Season 1 of Freedom Tech Weekend. 9 00:00:24,500 --> 00:00:25,620 Why the end of Season 1? 10 00:00:25,880 --> 00:00:27,040 Well, I just made it up this morning. 11 00:00:27,380 --> 00:00:29,080 Actually, no, I've been thinking about it for like a week or so. 12 00:00:29,240 --> 00:00:32,540 So you might have noticed I did miss a week. 13 00:00:32,940 --> 00:00:33,780 I missed last week. 14 00:00:34,620 --> 00:00:37,920 I was trying to never miss a week, and I did, and I'm sorry. 15 00:00:38,360 --> 00:00:43,440 Even RHR missed, I think, one week in its whole history, so none of us are perfect. 16 00:00:44,799 --> 00:00:49,900 But I'm entering a very busy time of the year for Maple, 17 00:00:50,740 --> 00:00:55,760 and so I just don't know when I'm going to be able to do these on a regular basis. 18 00:00:57,240 --> 00:01:00,420 So for now, I'm just going to take a break. 19 00:01:00,580 --> 00:01:01,880 So this is going to be the end of season one. 20 00:01:02,500 --> 00:01:03,260 We're going to leave you. 21 00:01:03,760 --> 00:01:04,600 We're not going to leave you hanging. 22 00:01:04,860 --> 00:01:07,980 We're going to leave you with some tips and tricks 23 00:01:08,380 --> 00:01:11,060 and how you can carry this on yourself. 24 00:01:11,920 --> 00:01:13,920 We've been showing you tools week in and week out. 25 00:01:14,020 --> 00:01:15,840 We show you one tool you can play with this weekend. 26 00:01:16,620 --> 00:01:17,520 Well, now we're going to show you, 27 00:01:17,960 --> 00:01:19,340 instead of giving you a fish, 28 00:01:19,500 --> 00:01:21,340 we're going to try and teach you how to fish a little bit. 29 00:01:22,500 --> 00:01:26,000 But really, I think most of you are probably more educated 30 00:01:26,000 --> 00:01:32,240 than I am on a lot of this stuff. But we're here to share together. So hop in the chat. I would 31 00:01:32,260 --> 00:01:37,400 love for you to participate today. Share with me what kind of tips you've learned along the way. 32 00:01:37,920 --> 00:01:44,140 But today we are going to talk about these privacy services, not just privacy, but really any 33 00:01:44,820 --> 00:01:49,620 cloud service that we use or any service we use in general that tells us, hey, just trust me, 34 00:01:49,940 --> 00:01:56,500 your data is safe. The whole trust me bro phrase that we hear tossed around. And then we find out 35 00:01:56,660 --> 00:02:01,100 later that maybe our data wasn't as safe as we thought it was. So that is what we're going to 36 00:02:01,430 --> 00:02:08,679 be digging into today. I'm waiting for this to show up on zap.stream because I want to 37 00:02:09,619 --> 00:02:11,460 post about it on Noster. 38 00:02:14,600 --> 00:02:18,800 Zap.stream has just been behaving weird lately, unfortunately. 39 00:02:22,040 --> 00:02:23,200 I'm not seeing it. 40 00:02:28,440 --> 00:02:30,300 Now it's giving me an error. 41 00:02:31,010 --> 00:02:34,040 All right, well, maybe I crashed ZapStream. 42 00:02:35,620 --> 00:02:36,340 Who knows? 43 00:02:37,180 --> 00:02:39,840 All right, well, we are live anyways. 44 00:02:40,060 --> 00:02:44,540 We're live on X, TFTC X. 45 00:02:44,740 --> 00:02:46,740 We're live on TFTC YouTube. 46 00:02:47,000 --> 00:02:48,360 We're live on my own X. 47 00:02:48,880 --> 00:02:52,620 And we should be live on zap.stream, but who knows if we truly are. 48 00:02:53,240 --> 00:02:54,380 So thanks for joining in. 49 00:02:55,100 --> 00:02:56,620 Let's go ahead and dive in. 50 00:02:56,760 --> 00:03:01,980 Those who are catching up late, you can just hit 2X and listen to me on 2X 51 00:03:02,080 --> 00:03:05,500 because, frankly, that is so much better than listening to somebody on 1X. 52 00:03:05,880 --> 00:03:10,220 People talk so slow when you slow down the podcast to 1x. 53 00:03:11,240 --> 00:03:17,860 So sometimes tuning in live is not preferential because you end up like just being like, come on, please talk faster. 54 00:03:19,020 --> 00:03:20,420 OK, people sound weird, too. 55 00:03:20,600 --> 00:03:23,580 Sometimes I feel like they actually are talking slower than they do in real life. 56 00:03:24,440 --> 00:03:25,860 Let me go and share my screen. 57 00:03:26,700 --> 00:03:27,740 We're going to dive in. 58 00:03:27,860 --> 00:03:29,840 We're going to hit all sorts of stuff today. 59 00:03:29,980 --> 00:03:32,060 We're going to talk about VPNs. 60 00:03:32,100 --> 00:03:34,820 We're going to talk about AI. 61 00:03:35,120 --> 00:03:42,860 We're gonna talk about just in general services that you use email services anything that claims to treat your data correctly with 62 00:03:43,560 --> 00:03:45,640 encryption with security with 63 00:03:47,420 --> 00:03:51,000 You name it they claim that they are not spying on you 64 00:03:51,940 --> 00:03:58,860 Well, we're gonna talk about like are you they just ask you to trust them or do they give you ways to verify that yourself? 65 00:04:00,430 --> 00:04:04,399 So that's what we're gonna do BTC pins. Good morning, bud. Welcome in 66 00:04:04,400 --> 00:04:09,000 All right, let me share my screen. 67 00:04:16,500 --> 00:04:17,260 There we are. 68 00:04:23,259 --> 00:04:26,340 Okay, all right, we are viewing my screen here. 69 00:04:28,020 --> 00:04:32,980 We got 10 viewers so far on YouTube. 70 00:04:35,360 --> 00:04:36,760 How are we doing over on X? 71 00:04:36,950 --> 00:04:39,120 I just want to make sure that I'm catching everybody here. 72 00:04:41,740 --> 00:04:42,680 Give me my... 73 00:04:44,120 --> 00:04:44,580 There we go. 74 00:04:45,090 --> 00:04:45,300 All right. 75 00:04:57,419 --> 00:04:57,880 All right. 76 00:04:58,520 --> 00:05:00,360 We've got a couple hundred people watching. 77 00:05:01,440 --> 00:05:01,620 Great. 78 00:05:02,140 --> 00:05:05,080 Restream is not giving me correct stats, so I just won't trust Restream. 79 00:05:05,640 --> 00:05:07,120 I'm going to go with what my own eyes are telling me. 80 00:05:07,340 --> 00:05:07,920 Trust me, bro. 81 00:05:08,480 --> 00:05:09,740 All right, the stats aren't even correct. 82 00:05:10,340 --> 00:05:11,700 Okay, so what prompted this today? 83 00:05:11,900 --> 00:05:17,280 It's a topic that I've been thinking about for a little while, but Luck T, sorry, man, 84 00:05:17,390 --> 00:05:18,140 you're not the first comment. 85 00:05:18,900 --> 00:05:21,360 You got a GM from BTC pins right ahead of you. 86 00:05:22,600 --> 00:05:24,680 But hey, thanks for commenting anyways. 87 00:05:24,860 --> 00:05:25,300 Welcome in. 88 00:05:26,260 --> 00:05:29,200 Those of you who are here on the TFTC channel, hang around. 89 00:05:29,370 --> 00:05:31,800 Right after me is RHR, Rabbit Hole Recap. 90 00:05:32,000 --> 00:05:39,300 it's always a banger so what prompted this is Shawn Yeager on primal on 91 00:05:39,420 --> 00:05:44,600 Noster shared this morning about anthropic and that they've made some 92 00:05:44,680 --> 00:05:49,820 changes to their data retention policies and I left this up because there's these 93 00:05:49,900 --> 00:05:54,860 ads drive me crazy please disable your ad blocker please me 94 00:05:55,000 --> 00:05:58,859 familia you heard us when you don't okay whatever 95 00:05:58,860 --> 00:06:03,680 Anthropic users face a new choice opt out or share your chats for AI training 96 00:06:03,820 --> 00:06:09,680 so Anthropic is making a change on September 28th they're going to be 97 00:06:10,220 --> 00:06:13,920 retaining conversations to train the AI models frankly I thought this was 98 00:06:14,040 --> 00:06:20,280 already happening but there is a new toggle now that you can switch in fact 99 00:06:20,420 --> 00:06:29,920 Let's go to Anthony's ex page if it'll let me when I'm not logged in. 100 00:06:38,260 --> 00:06:41,640 Well the not logged in experience is different than being logged in so 101 00:06:41,760 --> 00:06:46,320 whatever. Anyways, yeah there's a toggle now in settings that you have to go 102 00:06:46,260 --> 00:06:51,580 in to opt out and turn off tracking but oh it's right here look at that you can help improve 103 00:06:51,920 --> 00:06:57,320 claude oh do your do your service do your duty right um turn that off if you don't want them to 104 00:06:57,840 --> 00:07:06,000 log your chats to help improve their ai right and then updates on retention i believe they're also 105 00:07:06,120 --> 00:07:10,700 saving it for five years let me just search for the word five there we go extended data retention 106 00:07:10,800 --> 00:07:14,899 we are also extending data retention to five years if you allow us to use your data for model 107 00:07:14,900 --> 00:07:19,160 training, this updated retention length will only apply to new or resumed chats and coding 108 00:07:19,320 --> 00:07:22,980 sessions and will allow us to better support model development and safety improvements. 109 00:07:23,740 --> 00:07:25,680 Okay, some of you might be like, I don't use Claude. 110 00:07:25,700 --> 00:07:27,460 Like, what the heck is Claude, right? 111 00:07:27,600 --> 00:07:28,880 Most people talk about ChatGPT. 112 00:07:30,720 --> 00:07:35,660 Claude is what almost every AI programmer uses now. 113 00:07:36,660 --> 00:07:42,420 Claude code has quickly become the standard for using AI in your coding efforts. 114 00:07:43,140 --> 00:07:46,620 It's used at huge companies as well as small companies. 115 00:07:47,750 --> 00:07:53,160 And so Claude is collecting all of the proprietary code that is being written, 116 00:07:53,710 --> 00:07:55,440 the code that gets written and then maybe thrown away, 117 00:07:55,650 --> 00:07:57,000 and then new code that's written. 118 00:07:57,660 --> 00:07:59,440 They're collecting it all, like everybody's source code, 119 00:08:00,360 --> 00:08:02,220 and they're going to train their models off of it. 120 00:08:02,430 --> 00:08:04,340 So there's a lot going on here. 121 00:08:04,470 --> 00:08:06,940 And yes, they also have regular chat where people can chat about anything, 122 00:08:07,130 --> 00:08:10,140 but they're expanding this. 123 00:08:10,820 --> 00:08:12,500 And who knows, to say they'll stop at five years, 124 00:08:13,120 --> 00:08:14,700 And also if that data is retained, 125 00:08:14,980 --> 00:08:16,180 it is now sitting on their servers 126 00:08:16,920 --> 00:08:19,460 and could be leaked out onto the internet at any moment. 127 00:08:19,900 --> 00:08:20,700 We got a comment in here. 128 00:08:20,800 --> 00:08:21,800 Tom Lee just gave an interview 129 00:08:21,920 --> 00:08:23,580 claiming that Ethereum could overtake Bitcoin. 130 00:08:23,940 --> 00:08:24,400 Okay, whatever. 131 00:08:26,660 --> 00:08:28,260 So, you know, they have your data. 132 00:08:28,380 --> 00:08:29,200 It could be leaked online. 133 00:08:29,720 --> 00:08:30,560 How would it get leaked online? 134 00:08:31,420 --> 00:08:32,099 They're very secure. 135 00:08:32,300 --> 00:08:33,159 The servers are super secure. 136 00:08:33,360 --> 00:08:36,640 Well, you might remember a couple stories here. 137 00:08:37,159 --> 00:08:37,680 Where is it? 138 00:08:38,400 --> 00:08:38,479 Okay. 139 00:08:39,939 --> 00:08:42,000 Both ChatGPT and Grok. 140 00:08:42,620 --> 00:08:43,780 Man, don't you love all these pop-ups? 141 00:08:44,720 --> 00:08:49,620 ChatGPT and Grok accidentally allowed Google 142 00:08:49,750 --> 00:08:51,260 to index some of the chats. 143 00:08:51,850 --> 00:08:53,740 Now these weren't chats 144 00:08:54,010 --> 00:08:54,840 that you were just having by yourself. 145 00:08:55,090 --> 00:08:56,340 It was if you hit the share button 146 00:08:56,850 --> 00:08:58,140 to send the chat to somebody else. 147 00:08:58,960 --> 00:09:00,680 That ended up getting indexed on Google 148 00:09:01,030 --> 00:09:02,440 and available on Google search results. 149 00:09:03,420 --> 00:09:05,880 That was not surface to the user 150 00:09:06,040 --> 00:09:08,240 as being a byproduct of hitting the share button. 151 00:09:08,510 --> 00:09:11,339 The share button was giving you a private link 152 00:09:11,340 --> 00:09:14,400 that you could text to somebody or email to somebody, right? 153 00:09:14,490 --> 00:09:16,560 And it was meant to be a one-to-one, 154 00:09:16,960 --> 00:09:18,520 I am sharing this chat with you. 155 00:09:18,870 --> 00:09:20,820 So there were people who were having very like 156 00:09:21,030 --> 00:09:23,100 deep conversations with ChatGPT and Grok 157 00:09:26,020 --> 00:09:27,540 about all sorts of things, right? 158 00:09:28,840 --> 00:09:33,400 Marriage advice or, you know, squabbles or who knows what, 159 00:09:33,590 --> 00:09:35,660 but those were being indexed by Google 160 00:09:35,820 --> 00:09:37,479 and then somebody would go search 161 00:09:37,480 --> 00:09:41,520 and your potential name, your details 162 00:09:41,840 --> 00:09:43,800 of what was going on in your life are now on Google. 163 00:09:44,080 --> 00:09:48,160 So they have since backtracked and turned that off, 164 00:09:48,800 --> 00:09:50,640 but then it was funny because those ended up 165 00:09:50,780 --> 00:09:52,740 on archive.org as well, 166 00:09:52,860 --> 00:09:54,360 and so then they had to go to archive.org 167 00:09:54,400 --> 00:09:55,040 and get them all removed. 168 00:09:57,119 --> 00:10:00,740 The underlying base principle here is that 169 00:10:01,560 --> 00:10:05,000 if somebody else has your data, it can get out. 170 00:10:05,560 --> 00:10:07,620 You have no control over what they do with that data. 171 00:10:08,040 --> 00:10:10,740 Sure, they might have policies in place. 172 00:10:10,980 --> 00:10:12,420 Sure, maybe you could go sue them 173 00:10:12,440 --> 00:10:13,980 if you want to get a lawyer involved, 174 00:10:14,620 --> 00:10:16,800 but that's like damage control after the fact. 175 00:10:18,280 --> 00:10:20,860 Wouldn't you rather do preventative upfront? 176 00:10:21,600 --> 00:10:24,660 So another example of this is ChachiBT is in a big lawsuit 177 00:10:24,880 --> 00:10:26,340 with the New York Times right now, 178 00:10:27,460 --> 00:10:30,920 and it might result in OpenAI 179 00:10:31,120 --> 00:10:32,840 having to retain user data longer. 180 00:10:33,540 --> 00:10:38,020 For example, if you use the temporary chat feature 181 00:10:38,260 --> 00:10:40,280 inside of ChatGPT, I put air quotes around it 182 00:10:40,320 --> 00:10:41,580 because it's not temporary. 183 00:10:42,180 --> 00:10:45,580 They retain that information for 30 days. 184 00:10:45,840 --> 00:10:47,780 So your chat that you do there is retained for 30 days. 185 00:10:48,700 --> 00:10:51,400 And then this lawsuit is saying that they might have 186 00:10:51,400 --> 00:10:53,060 to keep it for 90 days or indefinitely. 187 00:10:54,000 --> 00:10:57,400 It's still back and forth, but they call it temporary. 188 00:10:57,920 --> 00:10:59,800 And all that means is that it just doesn't show up 189 00:10:59,800 --> 00:11:00,880 in your history and your sidebar, 190 00:11:01,780 --> 00:11:02,620 but it stays on their servers 191 00:11:03,040 --> 00:11:05,720 and could be stored into a backup somewhere 192 00:11:06,220 --> 00:11:07,960 and that could eventually get leaked out. 193 00:11:08,180 --> 00:11:10,220 A lot of these data hacks that we see that happen online 194 00:11:10,820 --> 00:11:13,900 are actually people hacking into the backup servers 195 00:11:14,040 --> 00:11:14,840 and stealing the backups. 196 00:11:15,100 --> 00:11:17,520 They're not getting the live in-flight data. 197 00:11:18,440 --> 00:11:20,280 Those backups are very juicy, 198 00:11:20,560 --> 00:11:22,960 full of lots of treasure trove of information. 199 00:11:24,700 --> 00:11:25,660 Okay, cool. 200 00:11:26,300 --> 00:11:28,780 Let's, let me, I'm gonna hop over to just, 201 00:11:29,060 --> 00:11:31,280 I wanna keep watch of the chat. 202 00:11:34,380 --> 00:11:35,760 Restream is not giving me everything. 203 00:11:37,900 --> 00:11:38,720 So, okay. 204 00:11:39,070 --> 00:11:40,740 I just wanna make sure that I've got them all open here. 205 00:11:41,760 --> 00:11:42,200 Cool. 206 00:11:43,960 --> 00:11:44,940 Back to where we were. 207 00:11:45,570 --> 00:11:46,760 So let's keep walking through here. 208 00:11:48,840 --> 00:11:49,920 That was Anthropic. 209 00:11:53,560 --> 00:11:54,000 Okay. 210 00:11:55,800 --> 00:11:57,400 So what do we have here? 211 00:11:58,760 --> 00:12:00,260 Oh wait, this is what I wanted to click on. 212 00:12:00,400 --> 00:12:00,720 Wrong one. 213 00:12:00,940 --> 00:12:03,620 So we have these things with VPNs 214 00:12:03,700 --> 00:12:05,800 where VPNs claim that they don't log our data. 215 00:12:07,100 --> 00:12:08,760 They're not keeping track of what we do. 216 00:12:09,140 --> 00:12:10,800 It's a natural thing to say, 217 00:12:11,100 --> 00:12:14,340 hey, if my internet service provider 218 00:12:14,540 --> 00:12:17,060 is tracking all of my browsing history, 219 00:12:17,380 --> 00:12:18,520 then I will use a VPN 220 00:12:18,940 --> 00:12:21,380 and then I will hide my browsing history from them. 221 00:12:21,820 --> 00:12:22,360 That's great. 222 00:12:23,280 --> 00:12:24,160 If you look in the fine print 223 00:12:24,360 --> 00:12:25,660 of your internet service provider, 224 00:12:26,720 --> 00:12:29,700 It is buried in there that they are keeping track of all of your data. 225 00:12:30,460 --> 00:12:33,240 I don't know if there are any that don't. 226 00:12:34,840 --> 00:12:38,600 They claim they do it for legal reasons, but they also do it for lots of other reasons, 227 00:12:39,210 --> 00:12:44,460 like selling your data to third-party advertisers, which usually means also selling your data to governments. 228 00:12:46,140 --> 00:12:50,140 So people use VPNs to get around that. 229 00:12:50,350 --> 00:12:55,160 They also use it to get around maybe something that their government has imposed on their country. 230 00:12:55,440 --> 00:13:00,020 If you have a company firewall, we're seeing this right now, really hot topic in the UK 231 00:13:00,540 --> 00:13:07,120 where they're saying that for child safety reasons, you should not use VPNs because they 232 00:13:07,170 --> 00:13:13,780 want to put a gate on the internet in the UK where you have to verify your age in order 233 00:13:13,860 --> 00:13:15,940 to go on the internet and access certain websites. 234 00:13:16,900 --> 00:13:22,260 What that means is they just want to do, excuse me, let me get a drink here. 235 00:13:26,160 --> 00:13:30,180 They just wanted to know your customer identity verification. 236 00:13:31,580 --> 00:13:36,280 And eventually that leads to they control who can and cannot access the internet, 237 00:13:36,790 --> 00:13:38,220 who can and cannot access information. 238 00:13:39,600 --> 00:13:40,940 So VPNs are a big topic there. 239 00:13:41,010 --> 00:13:43,000 And they're coming out saying, oh, please don't use VPNs. 240 00:13:43,340 --> 00:13:45,560 Every time you use a VPN, you're hurting a child. 241 00:13:47,779 --> 00:13:51,380 It's the same old recycled FUD. 242 00:13:52,140 --> 00:13:57,100 Okay, so Torrent Freak is a website that's used by people 243 00:13:57,120 --> 00:14:00,420 who have been sharing files online for years and years, 244 00:14:01,420 --> 00:14:04,860 but they do this annual post where they email out 245 00:14:04,860 --> 00:14:07,860 to all the VPN providers and they want to ask, 246 00:14:08,160 --> 00:14:11,320 what are your security processes for your VPN? 247 00:14:12,040 --> 00:14:14,820 And the biggest question that people really care about is, 248 00:14:15,480 --> 00:14:19,220 do they keep logs of browsing activity? 249 00:14:20,240 --> 00:14:21,440 Can I trust this VPN? 250 00:14:22,519 --> 00:14:25,560 You know, all the questions are around, can I trust you? 251 00:14:26,320 --> 00:14:29,480 Number one, do you keep any data that would allow you 252 00:14:29,580 --> 00:14:31,580 to match an IP address or timestamp 253 00:14:31,820 --> 00:14:34,280 to a current or former user of your service? 254 00:14:34,640 --> 00:14:36,240 If so, exactly what information do you hold 255 00:14:36,240 --> 00:14:38,060 and share for how long, right? 256 00:14:38,240 --> 00:14:40,120 What is the name under which your company's incorporated? 257 00:14:40,940 --> 00:14:44,520 What tools do you use to monitor and mitigate things? 258 00:14:44,960 --> 00:14:46,480 What external email providers, 259 00:14:47,040 --> 00:14:48,600 analytics support tools do you use? 260 00:14:48,980 --> 00:14:49,900 So they go through all this stuff. 261 00:14:50,040 --> 00:14:51,480 It's really, really fascinating stuff. 262 00:14:52,200 --> 00:14:55,240 If you want to scrutinize a company, 263 00:14:56,540 --> 00:14:59,900 I would highlight and copy and paste this 264 00:15:00,220 --> 00:15:02,720 into a notes document you have. 265 00:15:04,040 --> 00:15:05,100 My goodness, sorry. 266 00:15:05,680 --> 00:15:08,740 Into a document and kind of ask yourself these questions 267 00:15:08,980 --> 00:15:11,160 when you go look at another service. 268 00:15:12,000 --> 00:15:14,020 You might not be able to get answers to these questions 269 00:15:14,280 --> 00:15:15,160 when you use their service, 270 00:15:15,730 --> 00:15:17,020 but you're thinking about it, right? 271 00:15:17,360 --> 00:15:19,020 For example, support. 272 00:15:19,580 --> 00:15:24,240 If you need to interact with their support, what third-party service are they using? 273 00:15:24,970 --> 00:15:28,900 Because your email address will likely be tracked there. 274 00:15:29,530 --> 00:15:34,960 And then if you engage with the support person and share any personal information about your account, 275 00:15:35,630 --> 00:15:38,660 that is now going to be stored on that third-party service as well. 276 00:15:39,740 --> 00:15:43,840 And could that data be pieced together to invade your privacy? 277 00:15:44,540 --> 00:15:47,400 Things to think about that a lot of people just don't consider. 278 00:15:47,960 --> 00:15:54,960 Because we've really grown up with this cloud computing phase that we're in right now. We've just grown to just trust everybody 279 00:15:55,560 --> 00:16:01,779 They say they have military-grade encryption on their website. So we just trust that nothing bad is gonna happen and 280 00:16:02,560 --> 00:16:07,260 A lot of the times we think that incentives are aligned and they have been fairly aligned, right? 281 00:16:07,420 --> 00:16:12,500 Like companies want to continue to operate and if they screw over their users, they're gonna go out of business 282 00:16:12,840 --> 00:16:14,739 That's the free market version of it 283 00:16:15,420 --> 00:16:21,600 However, we see data breaches pretty much every day pop up in the news and a lot of companies recover from those data breaches 284 00:16:22,940 --> 00:16:30,060 And so that's that's simply not enough anymore to just trust a company with your data. You need to do something more 285 00:16:30,860 --> 00:16:34,980 We need to verify we need to have ways to verify that 286 00:16:35,420 --> 00:16:38,959 Your data is safe. So I went and asked maple 287 00:16:40,680 --> 00:16:44,860 Maple is our private AI and we we follow don't trust verify 288 00:16:45,180 --> 00:16:49,740 We give you the verify ability that the ability to go verify for yourself that we are 289 00:16:50,360 --> 00:16:52,960 Not tracking you and not logging your data that kind of stuff 290 00:16:53,980 --> 00:16:58,100 But I asked it sorry, excuse our tables are kind of screwed up. We got to fix that 291 00:16:58,640 --> 00:17:02,900 I asked it for examples of times where there were VPNs that said that they were not 292 00:17:03,300 --> 00:17:05,319 Logging user data and not tracking user data 293 00:17:05,449 --> 00:17:10,260 but then it was later exposed that they were and so they pointed out a couple things to me one of them was a 294 00:17:10,160 --> 00:17:12,079 a company called PureVPN. 295 00:17:13,459 --> 00:17:14,640 This was back in 2017. 296 00:17:16,280 --> 00:17:18,800 NordVPN putting up an ad on this article, 297 00:17:19,130 --> 00:17:21,040 which NordVPN is the next one we're going to look at. 298 00:17:21,199 --> 00:17:21,959 That's a bit funny. 299 00:17:22,709 --> 00:17:24,699 But NordVPN back in 2017, 300 00:17:25,610 --> 00:17:27,839 they had all over the website that they don't keep logs 301 00:17:28,329 --> 00:17:29,020 and that kind of stuff. 302 00:17:29,450 --> 00:17:32,680 But then it came out that they indeed were. 303 00:17:35,240 --> 00:17:38,119 So PureVPN was recently caught red-handed 304 00:17:38,120 --> 00:17:43,540 further records from PureVPN show that the same email accounts, Lynn's Gmail and 305 00:17:43,600 --> 00:17:49,060 the Teleport FX Gmail account were accessed from the same security blah 306 00:17:49,060 --> 00:17:55,500 blah blah so they were keeping track of IP addresses. You can go back and look at 307 00:17:55,500 --> 00:18:00,700 this more yourself. But they said hey please trust us and then they weren't 308 00:18:00,780 --> 00:18:05,919 doing what they told you to trust them about. NordVPN, another big person 309 00:18:05,920 --> 00:18:12,500 claiming that they don't track stuff. They weren't caught like that. So I'm not going to say that 310 00:18:12,580 --> 00:18:17,100 they have been keeping user logs, but somebody gained access to one of their servers and was 311 00:18:17,380 --> 00:18:23,680 watching traffic come through. And they were in flight. They were tracking a little more 312 00:18:23,980 --> 00:18:30,479 information than maybe people thought they were. And so that hacker was able to get some personal 313 00:18:30,480 --> 00:18:36,680 information, IP address information from users. You can go look at the Verge article about this 314 00:18:36,820 --> 00:18:42,760 if you want to learn more about it. So yeah, NordVPN reveals server breach that could have 315 00:18:42,790 --> 00:18:49,080 led attacker monitor traffic. NordVPN, because of this, has been doing third-party audits. So 316 00:18:49,080 --> 00:18:53,840 the company's fifth audit is an important trust signal to current potential users that it really 317 00:18:53,970 --> 00:18:58,699 isn't logging your traffic. So they went to Deloitte, which is one of the big four accounting 318 00:18:58,700 --> 00:19:03,420 firms that do audits all over the world. And this is their solution. And this is frankly the 319 00:19:03,500 --> 00:19:08,720 solution for a lot of companies. They say, hey, trust us. And we're going to get somebody to come 320 00:19:08,740 --> 00:19:13,720 and look at the code. And then they're going to say that the code is good. So you can trust us 321 00:19:13,800 --> 00:19:18,860 because you can trust them. And if that's the model you want to operate on, you can do that. 322 00:19:19,680 --> 00:19:24,899 I'm not telling you, maybe I did already, but I'm trying not to tell you what's right and what's 323 00:19:24,900 --> 00:19:29,420 wrong. I'm trying to give you the tools here and you can choose what is your risk profile and what 324 00:19:29,420 --> 00:19:36,220 are you comfortable with. So if you're comfortable with trusting a third-party accounting firm that 325 00:19:36,320 --> 00:19:41,780 has an IT audit department, if they say it's good, then you trust them. Then that's another 326 00:19:42,960 --> 00:19:47,939 element you can put in, you know, another fact, another piece of information you can put into 327 00:19:47,940 --> 00:19:54,880 your formula. I do want to remind everybody if you go search about Enron and Arthur Anderson, 328 00:19:55,320 --> 00:20:01,840 Enron in 2001, it was one of the biggest energy providers in America and was committing all sorts 329 00:20:01,890 --> 00:20:07,460 of fraud. And Arthur Anderson was the accounting firm that was auditing them and publishing 330 00:20:07,840 --> 00:20:14,140 positive reports that Enron was doing fine and that we could trust them. 331 00:20:14,940 --> 00:20:21,160 Well, both Enron and Arthur Anderson went down because they were caught committing fraud together. 332 00:20:22,720 --> 00:20:36,320 So I'm not saying Deloitte and others are doing that, but there's a history of where people say that you can trust them, and then maybe they weren't doing exactly what you say. 333 00:20:37,340 --> 00:20:41,260 Apple last year launched their Apple private cloud compute, 334 00:20:42,600 --> 00:20:43,800 and they're really pushing. 335 00:20:43,980 --> 00:20:45,520 Apple pushes privacy really hard, 336 00:20:46,620 --> 00:20:48,400 and they've had some public spats, 337 00:20:48,840 --> 00:20:50,840 like famously with the FBI back in 2015. 338 00:20:51,300 --> 00:20:53,380 They wouldn't unlock a phone for the FBI. 339 00:20:53,460 --> 00:20:54,000 I think it was 2015. 340 00:20:55,360 --> 00:20:57,720 They would not push a new firmware update 341 00:20:58,120 --> 00:20:59,500 to put a back door in. 342 00:21:00,320 --> 00:21:01,800 So when they launched private cloud compute, 343 00:21:02,980 --> 00:21:06,200 they want to provide people with transparency, 344 00:21:07,120 --> 00:21:14,060 Their version of verifiable transparency is that they are making the images that they run on their servers 345 00:21:14,680 --> 00:21:20,940 Making them available to third-party researchers and then the researchers will audit and let us know that it's okay 346 00:21:21,440 --> 00:21:23,220 So again you as user have to trust 347 00:21:23,880 --> 00:21:30,380 That Apple's providing the right images and that the researchers are saying that these are in fact 348 00:21:36,460 --> 00:21:37,100 fine 349 00:21:37,100 --> 00:21:43,640 mechanisms exist, such as Intel SGX and AWS Nitro attestation. Hey, oh, that's what we're 350 00:21:43,740 --> 00:21:52,840 using at Maple. So I want to kind of end here. We've been going for 21 minutes now. I need 351 00:21:52,960 --> 00:21:58,880 to vacate the channel soon so that Rabbit Hole Recap can jump in. But I want to talk 352 00:21:59,000 --> 00:22:07,080 about we are in this new age now of AI companies that are giving all sorts of different privacy 353 00:22:07,080 --> 00:22:13,740 security guarantees. The biggest ones, ChatGPT, Anthropic, they have policies where if you pay 354 00:22:13,800 --> 00:22:17,060 them more money, if you pay them a lot of money, they will do what's called zero data retention, 355 00:22:18,159 --> 00:22:23,940 ZDR for short. They claim that they are not going to keep any of your stuff. So if we search 356 00:22:24,300 --> 00:22:28,540 chat GPT, oh let's just do this. 357 00:22:31,740 --> 00:22:36,700 Tell me about chat GPT ZDR. 358 00:22:38,360 --> 00:22:39,060 I'm gonna look up pricing. 359 00:22:46,500 --> 00:22:49,620 It's a shorthand for an internal project, let's see. 360 00:22:50,440 --> 00:22:52,680 I don't know, oh I didn't understand what I meant. 361 00:22:54,240 --> 00:22:54,620 Classic. 362 00:22:56,000 --> 00:22:58,760 Zero data retention policy. 363 00:23:03,380 --> 00:23:05,380 OpenAI's own open model. 364 00:23:05,940 --> 00:23:06,800 Didn't know what ZDR meant. 365 00:23:07,580 --> 00:23:09,240 Okay, what is it and why does it matter? 366 00:23:09,280 --> 00:23:10,900 Oh man, we really gotta fix these tables. 367 00:23:11,420 --> 00:23:14,500 Sometimes called a no store or data purge on exit policy 368 00:23:14,840 --> 00:23:16,400 is a set of rules and technical controls 369 00:23:16,500 --> 00:23:18,180 that ensure an organization does not keep 370 00:23:18,300 --> 00:23:20,140 any user generated or processed data 371 00:23:20,740 --> 00:23:23,440 after a defined point of completion. 372 00:23:23,920 --> 00:23:24,680 Okay? 373 00:23:25,580 --> 00:23:26,380 That's key right there. 374 00:23:26,890 --> 00:23:28,440 This data is still passing through the servers. 375 00:23:29,020 --> 00:23:36,700 If you are a company, an organization that deals with highly sensitive information, and 376 00:23:36,700 --> 00:23:47,240 you sign up with OpenAI for a zero data retention plan, which -- that's the API pricing. 377 00:23:49,160 --> 00:23:50,900 Just give me chat GPT pricing. 378 00:23:51,360 --> 00:23:55,820 Why is it so hard to get pricing sometimes? 379 00:23:58,180 --> 00:23:59,520 ChachiBT.com slash pricing. 380 00:24:01,740 --> 00:24:02,060 Whatever. 381 00:24:04,940 --> 00:24:05,580 My goodness. 382 00:24:06,940 --> 00:24:09,880 Okay, well, you have to pay for an enterprise plan. 383 00:24:10,580 --> 00:24:12,400 You have to pay for these higher level tiers. 384 00:24:12,720 --> 00:24:13,880 I'm pretty sure it's an enterprise plan. 385 00:24:14,020 --> 00:24:15,700 It's been a little bit, but you have to pay for one of those. 386 00:24:15,860 --> 00:24:17,940 Give them a lot of money, and then they will give you zero data retention. 387 00:24:18,480 --> 00:24:29,240 What that means is after your data has passed through those servers and, you know, potentially been logged all over the place, they simply will not hit save at the end on their servers. 388 00:24:32,060 --> 00:24:36,180 There are all sorts of opportunities for bugs along the way, right? 389 00:24:36,900 --> 00:24:44,840 some data could be logged in some console somewhere on servers, and then those logs are 390 00:24:45,530 --> 00:24:51,820 backed up and saved for data bugging purposes, right? If they have to triage and look at 391 00:24:51,960 --> 00:24:55,320 something that happened, they can go back and dig through those logs. So they might be saving those 392 00:24:55,520 --> 00:25:01,679 logs for very good reasons, but they're like, hey, these logs don't have any PII in it, personal 393 00:25:01,680 --> 00:25:07,480 identifiable information, or maybe they say these logs don't have any ZDR data in them, 394 00:25:07,860 --> 00:25:10,680 so we're going to save these forever if we want to. 395 00:25:13,120 --> 00:25:18,340 But maybe they push a bug and it accidentally saves some ZDR data for a while and they don't 396 00:25:18,420 --> 00:25:19,400 realize it, right? 397 00:25:19,540 --> 00:25:22,280 Or maybe they go back and clean up after the fact and they don't get it all. 398 00:25:23,020 --> 00:25:27,740 Your sensitive data is still passing through the servers and could be inspected or saved 399 00:25:27,860 --> 00:25:28,340 at any moment. 400 00:25:28,620 --> 00:25:29,680 You simply just have no idea. 401 00:25:30,440 --> 00:25:31,900 they're not even keeping their promise, right? 402 00:25:32,140 --> 00:25:33,700 I'm not saying that ChatGPT is doing this, 403 00:25:34,190 --> 00:25:36,100 but the possibility is there 404 00:25:36,200 --> 00:25:38,240 that they are saving your data, 405 00:25:38,560 --> 00:25:41,000 even the ZDR data, that they're saving it somewhere. 406 00:25:42,240 --> 00:25:44,100 And we have no way of verifying. 407 00:25:45,020 --> 00:25:45,460 Okay. 408 00:25:46,420 --> 00:25:48,840 So what we do at Maple is that 409 00:25:49,040 --> 00:25:51,320 we basically give you ZDR by default 410 00:25:51,800 --> 00:25:53,300 and we let you verify it. 411 00:25:53,560 --> 00:25:55,620 So actually I'm not gonna do that. 412 00:25:55,800 --> 00:25:57,160 I have a different window open here. 413 00:25:57,840 --> 00:25:57,940 Okay. 414 00:25:59,700 --> 00:26:02,020 So with Maple, we say that we are private AI chat 415 00:26:02,260 --> 00:26:02,920 that's truly secure. 416 00:26:03,580 --> 00:26:04,520 We're using secure enclaves, 417 00:26:04,740 --> 00:26:05,880 we're using confidential computing, 418 00:26:06,320 --> 00:26:08,700 and we have open source code that you can run to prove it. 419 00:26:09,140 --> 00:26:11,380 There are other providers out there. 420 00:26:11,670 --> 00:26:12,640 I don't wanna name names. 421 00:26:13,300 --> 00:26:17,480 I'm really trying hard to say all of us privacy AI people 422 00:26:17,550 --> 00:26:19,680 are gonna lift this, all boats are, you know, 423 00:26:19,820 --> 00:26:21,920 we're gonna lift this water level together 424 00:26:22,080 --> 00:26:23,180 so all the boats can rise together. 425 00:26:23,720 --> 00:26:25,720 We really need to be going after the big people 426 00:26:25,810 --> 00:26:26,980 who are not even doing this at all. 427 00:26:27,660 --> 00:26:32,120 But publishing your open source code 428 00:26:32,940 --> 00:26:35,420 doesn't fully mean that you are verifiable. 429 00:26:35,980 --> 00:26:37,960 Unless people can see what's running on the servers 430 00:26:38,460 --> 00:26:40,200 and use cryptographic proof 431 00:26:40,690 --> 00:26:41,700 of what you're running on the servers, 432 00:26:42,570 --> 00:26:45,660 then open sourcing your code will only get you so far. 433 00:26:47,820 --> 00:26:49,840 Anybody can publish code 434 00:26:50,040 --> 00:26:52,400 and then when they go to deploy it to the servers, 435 00:26:53,760 --> 00:26:55,920 add stuff back in and deploy that to the servers. 436 00:26:56,480 --> 00:26:58,200 In fact, that happens all the time, 437 00:26:58,270 --> 00:27:00,840 not for nefarious reasons, but they change build numbers 438 00:27:01,040 --> 00:27:03,320 or they change little things here and there 439 00:27:03,500 --> 00:27:04,780 as part of the deployment process. 440 00:27:05,410 --> 00:27:08,140 And that stuff doesn't make it into the open source code 441 00:27:09,120 --> 00:27:11,800 because one, it doesn't need to for some reason, 442 00:27:12,080 --> 00:27:15,660 or two, there is security stuff in there 443 00:27:15,720 --> 00:27:18,060 that they don't want to maybe publish open source. 444 00:27:18,480 --> 00:27:21,560 So there are reasons why code would get changed 445 00:27:21,800 --> 00:27:25,179 before it's deployed, but they could also be 446 00:27:25,180 --> 00:27:26,980 putting other stuff in there that is tracking your stuff. 447 00:27:27,400 --> 00:27:30,200 So we give people the ability to prove it. 448 00:27:30,240 --> 00:27:31,540 You just click on proof here 449 00:27:32,100 --> 00:27:33,900 and we show you the attestation. 450 00:27:34,460 --> 00:27:36,180 And this is what Apple was referring to 451 00:27:36,500 --> 00:27:37,820 in their blog posts if we go back. 452 00:27:39,299 --> 00:27:44,280 Some specialized mechanisms exist, AWS Nitro attestation. 453 00:27:44,700 --> 00:27:46,980 So this is like a fingerprint of the server 454 00:27:48,020 --> 00:27:51,500 where this is the code that was deployed on the server. 455 00:27:52,040 --> 00:27:55,060 And then you can go to github.com. 456 00:27:56,000 --> 00:27:57,660 Actually, let's just click on it in here. 457 00:27:58,080 --> 00:27:59,120 Why am I typing that? 458 00:28:00,100 --> 00:28:04,220 Just go to our GitHub, okay, and go to Maple. 459 00:28:05,170 --> 00:28:07,180 You also can look at our Open Secret server code. 460 00:28:09,240 --> 00:28:12,000 But you can run the code yourself. 461 00:28:12,750 --> 00:28:14,680 While you're there, click a star, star us. 462 00:28:15,360 --> 00:28:15,920 It helps us out. 463 00:28:16,840 --> 00:28:18,160 But yeah, you can go to Open Secret, 464 00:28:18,460 --> 00:28:19,240 you can build the code, 465 00:28:19,600 --> 00:28:22,860 you can get that same attestation fingerprint thing, 466 00:28:23,200 --> 00:28:23,720 right, checksum, 467 00:28:24,180 --> 00:28:26,100 and you can compare those two to each other. 468 00:28:26,720 --> 00:28:31,220 We also give you all the attestations for the full stuff 469 00:28:32,280 --> 00:28:35,220 for the AWS hardware as well. 470 00:28:35,840 --> 00:28:36,640 What this all means 471 00:28:36,820 --> 00:28:38,640 is you're getting hardware level encryption. 472 00:28:39,520 --> 00:28:41,600 So we're publishing our code open source, 473 00:28:41,800 --> 00:28:44,620 and then we say this code is running on a server 474 00:28:44,740 --> 00:28:47,920 with this secure enclave, this secure chip. 475 00:28:48,660 --> 00:28:51,040 And that chip is encrypted. 476 00:28:52,420 --> 00:28:54,340 And the memory that's running, 477 00:28:54,450 --> 00:28:56,360 the RAM that's running on that server is encrypted. 478 00:28:57,030 --> 00:28:58,600 So people are not able to access it. 479 00:28:59,220 --> 00:29:01,620 The only thing that can look at that memory 480 00:29:01,820 --> 00:29:02,820 is the code that is running. 481 00:29:03,550 --> 00:29:04,960 And how do you know if you can trust the code 482 00:29:04,990 --> 00:29:05,420 that is running? 483 00:29:05,550 --> 00:29:07,360 Well, it is this code right here on GitHub. 484 00:29:07,900 --> 00:29:08,820 You can go see it for yourself 485 00:29:09,070 --> 00:29:10,940 and you can see that there are no logs happening. 486 00:29:11,010 --> 00:29:12,720 You can see that there's no data being stored, 487 00:29:13,400 --> 00:29:14,400 all that good stuff, right? 488 00:29:15,060 --> 00:29:18,520 So this is, sure, you can call this a pitch 489 00:29:18,590 --> 00:29:19,500 for what we're doing, but really, 490 00:29:19,760 --> 00:29:24,740 we are taking these tools, these basic principles, 491 00:29:25,780 --> 00:29:29,900 and we are applying them to how we do security at Maple, 492 00:29:30,720 --> 00:29:33,480 because we don't want to keep track of our user data. 493 00:29:33,580 --> 00:29:34,680 We don't want our user data. 494 00:29:34,810 --> 00:29:36,640 So when you use Maple, it's your data. 495 00:29:36,740 --> 00:29:39,500 You have a private key that encrypts your data 496 00:29:39,940 --> 00:29:42,540 on your device before it is sent to our servers, 497 00:29:43,100 --> 00:29:48,880 And then on our servers, the only thing that interacts with your data in a way that it can be read is the enclave. 498 00:29:49,380 --> 00:29:53,400 And that's the enclave on the CPU side where it's handling the encryption back and forth. 499 00:29:53,420 --> 00:29:57,480 And then on the GPU side, we have GPU providers that also use secure enclaves. 500 00:29:58,980 --> 00:30:08,500 And your code, sorry, not your code, your chats and your data, your personal information is sent encrypted to the GPUs. 501 00:30:08,540 --> 00:30:10,740 And then in the enclaves, it's decrypted. 502 00:30:11,700 --> 00:30:18,540 The AI accesses it, comes up with a response, re-encrypts it, and then sends it back to your device where it is decrypted on your device. 503 00:30:19,440 --> 00:30:24,760 At no point in time do we have access to your data when it is unencrypted. 504 00:30:25,000 --> 00:30:25,780 It's always encrypted. 505 00:30:26,700 --> 00:30:28,520 So that's what we give you. 506 00:30:28,940 --> 00:30:31,060 And this is our don't trust, verify model. 507 00:30:31,440 --> 00:30:33,280 We don't ask you to just trust us, bro. 508 00:30:33,980 --> 00:30:42,120 Really, the only thing that you're trusting is this hardware encryption on the chip that is being run inside of AWS and at our GPU providers. 509 00:30:42,790 --> 00:30:47,740 Now, if that's too much for you, you don't want to trust that, you can run AI locally. 510 00:30:47,900 --> 00:30:49,520 There are so many great AI tools run locally. 511 00:30:49,840 --> 00:30:52,580 I've done an episode on this to show you how to do that. 512 00:30:53,700 --> 00:30:56,160 If you need that level of security, that is the best. 513 00:30:56,380 --> 00:30:57,120 Run it on your own. 514 00:30:57,340 --> 00:30:58,020 Turn off the internet. 515 00:30:58,630 --> 00:31:01,480 Run on a server that's not going to connect to anything and do that. 516 00:31:01,960 --> 00:31:07,780 But if you want to have AI that is available everywhere, if you're using ChatGPT right now, 517 00:31:08,080 --> 00:31:11,400 if you're using Grok and you have a free account on there or even a paid account, 518 00:31:11,900 --> 00:31:12,940 go to Maple and get a free account. 519 00:31:13,340 --> 00:31:14,980 It doesn't cost you anything. 520 00:31:15,760 --> 00:31:20,480 And you're going to get infinitely better security guarantees than you would with ChatGPT 521 00:31:20,740 --> 00:31:21,400 and Claude and Grok. 522 00:31:22,280 --> 00:31:26,940 We just went through some of the stories as to why you shouldn't potentially trust them 523 00:31:28,300 --> 00:31:30,640 or why you should verify before you trust them. 524 00:31:31,620 --> 00:31:33,220 So anyways, that's where I'm going to end it today. 525 00:31:33,920 --> 00:31:35,080 Don't trust, verify. 526 00:31:35,900 --> 00:31:38,620 Every service you look at, when you go to the security page, 527 00:31:38,820 --> 00:31:40,980 when you go to, you know, why you should trust us, 528 00:31:41,620 --> 00:31:44,260 start looking at it through this new lens of, 529 00:31:44,720 --> 00:31:47,540 is there a way for me to verify the code that is running on their servers? 530 00:31:49,340 --> 00:31:53,480 And start looking at, like, what other tools are they sharing my data with 531 00:31:53,680 --> 00:31:54,680 for their internal practices? 532 00:31:55,740 --> 00:31:58,880 Go back to that Torrent Freak article if you want to, 533 00:31:59,180 --> 00:32:01,280 and they have these 12 questions that they ask everybody. 534 00:32:02,600 --> 00:32:06,780 what political pressure is on that company, you know, based on the country that they operate in. 535 00:32:06,940 --> 00:32:10,740 There's all sorts of great things to just be thinking about. Be thinking about these as you 536 00:32:10,800 --> 00:32:19,180 access different services. And I'm going to bid you farewell from season one of Freedom Tech 537 00:32:19,540 --> 00:32:25,520 Weekend. If you are just tuning in right now, this is the end of season one. This is episode 21 of 538 00:32:25,560 --> 00:32:30,199 season one of Freedom Tech Weekend. It's been a blast being along here with everybody. Thanks for 539 00:32:30,200 --> 00:32:35,140 joining in. Thanks for tuning in week in and week out. The only week I missed was last week, 540 00:32:35,520 --> 00:32:40,620 but things are getting really busy right now. So we're approaching a thousand viewers here 541 00:32:41,140 --> 00:32:44,620 live. Thank you for joining us. Go back and catch the beginning of the episode. 542 00:32:45,680 --> 00:32:53,120 Don't trust bros. Just verify instead. All right. Stick around if you're on the TFTC channels 543 00:32:53,380 --> 00:32:58,680 for Rabbit Hole Recap. If you're on my channel, hop over to TFTC, go check out Rabbit Hole Recap. 544 00:32:59,300 --> 00:33:01,500 And I hope that you have a great weekend. 545 00:33:02,100 --> 00:33:06,720 And go over to trymaple.ai and get yourself a free Maple account. 546 00:33:07,320 --> 00:33:07,600 All right. 547 00:33:08,020 --> 00:33:08,160 Later. 548 00:33:08,260 --> 00:33:08,280 Thank you.