WEBVTT 00:00.000 --> 00:05.440 should be live. A lot fewer shenanigans, I hope, than last week. 00:07.260 --> 00:15.320 YouTube says the stream has started. It says it's excellent. Hello, everybody. Hello. Welcome in. 00:15.420 --> 00:20.400 Welcome in. Happy Friday. Happy Crunchy Day, as Adam Bean would definitely say. 00:21.460 --> 00:26.660 I see some familiar faces already. Let me go ahead and bring that up. 00:28.980 --> 00:33.920 Whenby's Note, Adam Bean, Shadow Ben. Shadow Ben, yeah, I was going to say that's a new one. 00:34.100 --> 00:38.140 Hi, Henry. First time in live. Welcome in. Welcome in. JMS 547, welcome. 00:39.720 --> 00:43.860 Terracotta Pie. The title of the stream sounds interesting. Yeah, I think it's a common issue, 00:43.900 --> 00:48.660 right? It's a common thing, at least I get back here, so I have to assume it impacts 00:49.100 --> 00:56.140 a lot of people who listen. But the concept of burnout and just always trying to stay on top of 00:56.140 --> 01:05.280 things and just feeling like it's maybe more work than you're able to put in. And then kind of wondering, 01:05.580 --> 01:13.100 hey, so is this doable? Is it possible? Should I keep going? There's an actual direct question 01:13.100 --> 01:18.320 that I'll address shortly. But I feel like those are the questions I see a lot back here. 01:18.400 --> 01:22.160 I've received emails from you guys that see the comments, so I wanted to address it, 01:22.200 --> 01:24.580 share my thoughts on it. It's something I've shared my thoughts on before, 01:24.580 --> 01:29.580 but I think it's always a really good reminder to share. If you're in the live chat, say hi. Hello. 01:29.780 --> 01:32.600 I'm going to give everyone a few minutes to log in. If you're in a signal group, 01:33.060 --> 01:37.200 definitely say hi as well. I'll be kind of cycling there, too. So say hi if you're in a 01:37.200 --> 01:42.340 signal group and you're tuning in live. Say hi in the live chat there. And I also want to 01:42.340 --> 01:46.000 thank the five people who left questions. If you guys want to already get ahead of that, 01:46.160 --> 01:51.080 there is a link that's the same consistent link every week in a description so that you 01:51.080 --> 01:55.360 can leave a question, a formal question like the one here that I answer in the next week's stream. 01:57.020 --> 02:01.940 So that's how we kind of keep the show going. And if it can be about me, it can be about you, 02:02.100 --> 02:08.380 it can be about life, it can be about tech, it can be about anything. Hello, green cactus. 02:08.740 --> 02:15.500 Hello, 303. Poochievert. Hello, hello. Welcome, everybody. Let me see how the stream is looking 02:15.500 --> 02:20.120 here. All right. I'll give it a few more minutes. Wait a few more minutes for everyone 02:20.120 --> 02:24.840 to come in. Do you guys have any updates or anything you're looking forward to this weekend? 02:25.280 --> 02:29.180 On my end, it is a boring weekend, which I'm really happy about because on the topic of burnout, 02:30.220 --> 02:34.660 I don't feel like I'm burning out, but I'm just exhausted this week. So I'm excited for 02:34.660 --> 02:39.640 kind of a down weekend to relax over here. It's been a crazy week with recording. 02:40.160 --> 02:46.120 I think yesterday I recorded for like five. No, it was like three to four hours of just 02:46.120 --> 02:49.340 talking because I had a Techlor Talks interview to record yesterday and then I recorded the 02:49.340 --> 02:52.540 second part of the proton hardening video, which was an hour and then surveillance support was 02:52.540 --> 02:59.760 over an hour. So my voice yesterday was pretty wiped. All right. Let me check the stream. 03:00.500 --> 03:06.660 Okay. Let's go ahead and get started. So the main question this week, okay. And then 03:06.660 --> 03:10.700 Steve says hi from the signal group. Hi, Steve. Definitely feel free to leave questions and 03:10.700 --> 03:16.040 tag along as we go. And I'll go ahead and bounce between people. So go ahead and keep 03:16.040 --> 03:19.400 leaving questions in the live chat. Again, I bounced between them and I'll make sure to 03:19.400 --> 03:23.560 catch up. So please be a part of the stream. You guys are part of the stream if you're in 03:23.560 --> 03:28.080 the live chat. And yeah, let's get into it. So this is from an anonymous person. They asked, 03:28.180 --> 03:33.040 I'm getting tired of trying to maintain my privacy. At what point do you accept that 03:33.040 --> 03:38.160 all services collect data on you? Your voice and image will likely be fed to AI. 03:38.680 --> 03:41.920 And you just have to live with that in order to live in the world. It sucks, 03:41.920 --> 03:47.520 but especially in some industries, you just have to use the invasive tools. There isn't 03:47.520 --> 03:50.900 another option and trying to fight it puts you behind your colleagues who are using 03:50.900 --> 03:55.780 the big data tools and not worrying about being private. Yeah. So I think there's two, 03:56.400 --> 04:01.420 maybe three parts of this question. The first is that I always see this feeling, 04:01.600 --> 04:06.240 I'm just going to call this privacy burnout, right? I think that's maybe just a term that 04:06.240 --> 04:10.720 we can all coin and use. I think everybody can understand quite easily. It's probably 04:10.720 --> 04:15.340 relatable to many people as well. I see it as a signal, not really a verdict, right? 04:16.060 --> 04:21.440 In the running world, I'm a runner. And if I, you know, if I've been training for months 04:21.440 --> 04:26.380 and months and months, and then I have a week where I'm just mentally and physically exhausted, 04:27.260 --> 04:30.880 it means I'm over-training. It doesn't mean that I hate running, even though it might feel 04:30.880 --> 04:33.840 like I hate running that week. It doesn't mean that there's anything wrong with the running. 04:34.000 --> 04:38.080 It doesn't mean that it's something wrong. I'm doing too many hills. It's just that 04:38.080 --> 04:43.040 I'm doing too much relative to what I can handle and what I probably need in that time. And so 04:43.040 --> 04:49.280 actually the way to address this isn't to do more. It isn't to quit. It's to just step back 04:49.280 --> 04:54.300 for a second and re-reflect on the situation and see why you feel that way. Again, the burnout 04:54.300 --> 04:58.900 is a signal that something isn't working. It's usually just a mismatch. Technically, 04:59.040 --> 05:02.400 if you want to get technical, it's a mismatch between your threat model and what you're 05:02.400 --> 05:10.040 doing to try to address kind of the risks that you have established. So I think that's 05:10.040 --> 05:14.080 always where I like to start. It's always good for any of you if you feel this way to ask what 05:14.080 --> 05:19.900 specifically is giving me the most amount of overwhelm and is that aligned with what my 05:19.900 --> 05:26.080 concerns actually are? Because when you actually, you know, dig into this, it feels like every 05:26.080 --> 05:31.340 service collects data on you and your voice and image will be fed to AI. But really, 05:31.340 --> 05:36.280 that's not always true. A lot of the privacy respecting services actively try not to collect 05:36.280 --> 05:41.480 data about you. And I'm sure you already used many of them. So it's easy to only look at the 05:41.480 --> 05:45.420 negatives when you're in that kind of very negative state. So that's always what I like 05:45.420 --> 05:51.600 to say if you have burnout. Now, in terms of solutions, again, step back, re-reflect 05:51.600 --> 05:55.400 either what you're doing doesn't align with your threat model and your threat model is 05:55.400 --> 05:59.820 actually good. Like you've put together a good threat model, you understand what your risks are, 05:59.820 --> 06:03.500 you understand what you really care about. And then you might realize, oh, 06:03.760 --> 06:07.980 eight of these things I'm doing actually are too much. Like they actually go beyond 06:07.980 --> 06:14.020 what I need to do. And sometimes it's actually not that at all. Sometimes you are actually 06:14.780 --> 06:17.920 just, you don't have a good threat model. And sometimes you need to update the threat model. 06:17.940 --> 06:22.420 And it's like, okay, beforehand I had this concern and I realized maybe this isn't as much 06:22.420 --> 06:27.540 of my concern anymore. So I'm going to change that expectation. And then when I actually 06:27.540 --> 06:32.300 execute with the tools, they will better align with that. So I just think it signals something 06:32.300 --> 06:37.140 isn't matching up. In terms of your follow-up questions, I think that, you know, anything 06:37.140 --> 06:45.060 that has to do with work, I think that is less of a burnout thing and more of a compartmentalization 06:45.060 --> 06:50.620 thing. This is the kind of situation where it's like, hey, if something's for work, 06:50.760 --> 06:55.520 it's probably for a business, it's probably for school, it's probably something that doesn't 06:55.520 --> 07:00.820 even need to inherently be about you. And so it's very possible to actually have a situation 07:00.820 --> 07:06.180 where you're using tools that maybe you wouldn't use in your personal life that you feel comfortable 07:06.180 --> 07:10.720 using because they align with the risk and the kind of what you've designated into that 07:10.720 --> 07:14.880 section of your life. So if you work for a company and you're helping this company develop 07:14.880 --> 07:18.560 a piece of software and they're like, hey, you should use cloud code. You should use chat 07:18.560 --> 07:24.600 GBT to help build the tool. And then it's like, okay, I'll use these tools to build the site 07:24.600 --> 07:28.120 for the company. But that doesn't mean you have to upload your personal information to it. 07:28.120 --> 07:31.800 You don't have to upload your bank statements. You don't have to upload even your first and 07:31.800 --> 07:36.580 last name sometimes. So that's typically how I look at it. But you guys should also let me know 07:36.580 --> 07:40.460 if you're in the, in the live chat, like what's been your experience. I know it's very common. 07:40.660 --> 07:45.860 So I just want to make sure that no one feels like it's only them going through this. I go 07:45.860 --> 07:50.220 through this too. I actually just had this happen to me a few weeks ago where I just felt 07:50.220 --> 07:54.740 overall overwhelmed by my tech stack, not specifically the privacy and security, but 07:54.740 --> 08:00.180 just overall in tech, everything just felt like it just wasn't working. And so I had to kind of go 08:00.180 --> 08:06.360 through very particularly, like just the little things, the big things, it was, it was a whole 08:06.360 --> 08:10.220 thing. It took my whole weekend up. But when I came back from the weekend, it was like a whole 08:10.220 --> 08:14.920 weight came off my chest and it felt really nice. So that's what I have to say about that question. 08:16.480 --> 08:20.680 Let's see here. The title of the stream sounds interesting. Yeah, yeah, yeah. It's a common thing. 08:21.240 --> 08:26.080 My processor is also burning out apparently very frequent system fails today. I'm sorry about 08:26.080 --> 08:35.820 that. I hope that it can get over it by stepping back and reassessing where it's at. I also just 08:35.820 --> 08:41.160 wanted to shout out on this, the privacy dad, I really liked their blog. It's very practical. 08:41.160 --> 08:46.220 It's coming from the perspective of someone with a family. And so I just think it's really 08:46.220 --> 08:50.560 well done. But they actually just published this a few days ago. It's okay to take a break from 08:50.560 --> 08:56.280 thinking about digital privacy. It's not like inherently about burnout. Like that's not exactly 08:56.280 --> 09:00.600 what it's about. But I think there's a lot of overlaps with kind of what he discusses and why 09:00.600 --> 09:04.960 he kind of took a little break and how it allows him to come back stronger and still 09:04.960 --> 09:09.000 passionate about this. You guys have to take a break. Like I can tell you I've been doing 09:09.000 --> 09:13.460 this for over 10 years. And if I was like on it every single day all the time, 09:13.520 --> 09:16.940 I wouldn't still be doing this. Like I would have quit a long time ago and I would have 09:16.940 --> 09:21.980 maybe just given in fully. So I really think it's important to have those boundaries for yourself. 09:23.540 --> 09:28.140 Steve shared a recent win on signal here, installing smart tube on the fire stick for 09:28.140 --> 09:31.980 ad for YouTube. That's pretty cool. I haven't heard a smart tube before, but whatever you 09:31.980 --> 09:36.640 can do to get ad for YouTube is going to be a big win. So good work. I mean, not a win for 09:39.100 --> 09:44.560 maybe creators fully, but it's a win for you guys personally. I also wanted to share our quiz. 09:44.980 --> 09:48.900 Actually, I think is a really good tool for this too. So our quiz is going to ask you 09:48.900 --> 09:54.880 questions about your situation all across the board. This browser doesn't support emojis. 09:55.060 --> 09:59.200 That's why you see that thing. But on our tools, it's going to ask you like, hey, 09:59.320 --> 10:02.740 tell me a little bit about yourself. And then it's going to ask, what do you do? 10:02.940 --> 10:07.740 And when you skip to results, it's going to tell you, hey, you're doing enough for who 10:07.740 --> 10:11.660 you are. You're doing too much for who you are. It actually tells you, you're probably doing more 10:11.660 --> 10:15.340 than you need to do. And I think it's not a perfect tool by any stretch of the imagination. 10:15.340 --> 10:19.200 That's not the point. It's not meant to be exact. It's meant to give you an idea of where 10:19.200 --> 10:24.080 you're at and track patterns over time. So the quiz, it actually tracks your score over time. 10:24.200 --> 10:27.780 And again, it's it's your own link. So we don't keep that data. It's just a link that you 10:27.780 --> 10:31.940 keep for yourself. If you keep taking that quiz of every couple months, it'll actually 10:31.940 --> 10:36.240 start to spot patterns over time on how you're doing. And this question is a big reason for 10:36.240 --> 10:44.980 why I developed that quiz. So all right, let's see Gothic for life. Personal data is very much 10:44.980 --> 10:47.880 connected with your work, though. It's very difficult to avoid that SSO integrations. Most 10:47.880 --> 10:52.340 companies use. Yeah, but most companies, they set up an email account for you, right? Like a 10:52.340 --> 10:55.180 lot of companies, let's say they use Google, they're going to give you a Google account 10:55.180 --> 10:58.220 tied to your company, Google account. If they're not doing that, they're not 10:58.220 --> 11:02.700 doing things properly, I would say. A lot of organizations again, really should be giving 11:02.700 --> 11:08.720 you company based credentials that aren't personal whatsoever. And ideally, a company 11:08.720 --> 11:12.760 is giving you dedicated devices for work as well. That's how they should be doing 11:12.760 --> 11:16.560 things. If they're not, then you should still try to recreate that create a new 11:16.560 --> 11:20.700 account just for work that isn't tied to you that you can use for work. Try to 11:20.700 --> 11:23.640 set up a virtual machine if they don't want to give you a dedicated device, 11:23.780 --> 11:26.380 like try your best to recreate that if they're not going to do it. 11:30.780 --> 11:36.960 Let's see. The link is quiz.techlor.tech. It's on our site. It's easy to find. 11:37.880 --> 11:42.400 Just go to our site. Felix's next question, and I'll jump again between the chats, 11:42.540 --> 11:46.660 but Felix's next question, I am living in a heavily censored country where 99% 11:46.660 --> 11:50.860 of major VPN providers are inaccessible. So most of your recs on those are 11:50.860 --> 11:54.240 useless for me. What is your stance and advice on proxy protocols that are 11:54.240 --> 11:58.160 primarily used to bypass censorship in countries like mine where normal VPNs 11:58.160 --> 12:02.600 like WireGuard and OpenVPN and proxies are blocked? I'm mostly talking about 12:02.600 --> 12:07.360 Shadowsocks, V2ray, Trojan, Hysteria 2, et cetera that have appeared in China 12:07.360 --> 12:11.540 for circumventing the Great Firewall and are now widely used in countries like 12:11.540 --> 12:17.440 Russia and Iran to access the rest of the internet. So I always preface this 12:17.440 --> 12:22.620 question. Like I want to be as realistic with where I think my advice 12:22.620 --> 12:26.540 is, and this is a place where I just don't have much first-hand experience. 12:26.840 --> 12:32.140 Like I have lived in the US most of my life, and here I've never had to deal 12:32.140 --> 12:35.440 with censorship issues other than the occasional Wi-Fi network that doesn't 12:35.440 --> 12:39.220 want VPN usage on it, which is a very easy thing to get around, 12:39.500 --> 12:43.320 and it's nothing anywhere near as complex as what you might be dealing 12:43.320 --> 12:49.100 with in your region. So again, and I think this is why when we talk 12:49.100 --> 12:55.300 about having public teams for projects, it's really important because when a 12:55.300 --> 12:59.340 project is public about who runs it, then you get to know who runs the project, 12:59.880 --> 13:03.680 whether it's a service, an email client, et cetera, and whoever runs it, 13:04.600 --> 13:09.080 their personal experiences end up in the product. So 13:09.980 --> 13:13.860 Techlor probably right now isn't the best resource for censorship circumvention 13:13.860 --> 13:17.180 because look at me, like I've lived in the US my whole life, like how much am I 13:17.180 --> 13:20.300 going to know about it, and how much first-hand experience am I going to have? 13:20.840 --> 13:25.660 That doesn't mean I can't understand, it doesn't mean that I can't learn and give 13:25.660 --> 13:30.000 you guys better advice, but there's probably people who actively are in your exact situation 13:30.000 --> 13:34.980 who have that info. So I just always want to preface that, guys, and it's a good 13:34.980 --> 13:40.920 reminder to like when you're using a service, just know who runs it because it reflects on 13:40.920 --> 13:43.620 the service and what they're going to prioritize. Based on what I've seen, 13:43.620 --> 13:48.760 seems like it's the best right now, but guys, this is based on what I read online and what 13:48.760 --> 13:54.200 people report works today. And this stuff is a cat and mouse game, what works today might not 13:54.200 --> 13:59.880 work next week. And so all I can share is try to find communities online that discuss these 13:59.880 --> 14:04.120 things that have people like yourself that are going through this exact situation. 14:05.160 --> 14:09.260 And don't just rely on one method because this change is so frequently, so you need to have 14:09.260 --> 14:14.180 more than one method ready to go so that you can access content because this is, again, 14:14.320 --> 14:18.480 it's a cat and mouse game. So I don't think one method is ever going to be the only method that 14:18.480 --> 14:23.260 will permanently work for you. And that's pretty much the best I can kind of share right now, 14:23.420 --> 14:25.880 unfortunately. It's just not something I know very much about. 14:28.280 --> 14:34.080 Anonymous asks, could you explain lockdown mode, please? I hear it helps against UFED and 14:34.080 --> 14:38.700 other digital forensics tools designed to extract phone data and is very useful to journalists, 14:38.700 --> 14:43.520 but I don't understand the pros and cons and if I should use it. I suppose if I can use the service 14:43.520 --> 14:48.060 on a computer, then I shouldn't use my phone for it to limit the data on my phone, or is it more 14:48.060 --> 14:56.580 secure to use the phone since iOS sandbox is everything. Yeah, so the first thing, it's weird 14:56.580 --> 15:02.120 because this video actually got quite a lot of views, but it seems like it got organic search 15:02.120 --> 15:06.200 views and it feels like a lot of our like dedicated audience missed it for some reason. 15:06.720 --> 15:12.180 So we made a whole lockdown video and I've been using lockdown mode for years now and that video 15:12.180 --> 15:18.140 was made a while back, but it's overall still relevant and that video discusses exactly what 15:18.140 --> 15:24.460 you actually notice when you start using lockdown mode on the phone, on the laptop, and it literally 15:24.460 --> 15:29.020 shows you like side by side how the features impact your day to day workflow. So I'd highly 15:29.020 --> 15:32.960 recommend checking out that video if you want to learn more about what it looks like. Now, 15:33.700 --> 15:37.000 for me personally, I think that lockdown mode is a lot more restrictive on mobile, 15:37.440 --> 15:42.440 mainly because third-party browsers you can't add site exceptions for, so you're kind of incentivized 15:42.440 --> 15:48.220 to use Safari. iMessage features largely break to be honest, like I'm pretty sure search just 15:48.220 --> 15:53.160 isn't a thing in iMessage. Photo sharing is always a little bit iffy and I just stumble on random 15:53.160 --> 15:58.900 things that don't seem to work on mobile because of lockdown mode. On desktop, honestly, 15:58.900 --> 16:04.800 I can't even tell you it's on 90% of the time. Like on desktop, because third-party 16:04.800 --> 16:08.920 browsers can use their own browser engines, they're not really impacted when you enable lockdown mode, 16:09.420 --> 16:15.640 so I just don't notice much on desktop. In terms of, you know, you say should I enable it on one 16:15.640 --> 16:21.700 device or another device, I would say that if you are using lockdown mode for a good reason, 16:21.740 --> 16:25.240 which I don't think is necessarily everyone should use lockdown, but I think it's designed for 16:25.240 --> 16:32.740 specific people or just people who want more security. But if you have to enable it on one device, 16:32.840 --> 16:36.140 you probably have to enable it on all of your devices. I mean, this is what Apple specifically 16:36.140 --> 16:41.840 recommends. It's supposed to be enabled on all of your devices. In fact, if you remove a device 16:41.840 --> 16:46.380 and you're signed into the same Apple account, if you remove a device and you turn off lockdown 16:46.380 --> 16:50.920 mode on one of them, you get notified on your other devices, hey, lockdown mode was disabled on one 16:50.920 --> 16:55.540 of your devices. And also, if you have lockdown mode enabled on like an iPhone and you buy a brand 16:55.540 --> 17:00.700 new Mac, while you go through the setup menu on the Mac, it'll prompt you and ask you if you want to 17:00.700 --> 17:06.300 enable lockdown mode. So again, it's meant to be used on all devices. If you have an Apple Watch 17:06.300 --> 17:10.140 and you have an iPhone, the Apple Watch will automatically inherit lockdown mode from the 17:10.140 --> 17:14.860 iPhone. So again, I really don't think there's many situations where you should be enabling 17:14.860 --> 17:18.860 lockdown mode on one, but not the other. It's meant to be used across all Apple devices. 17:19.700 --> 17:24.460 The one exception maybe is if you have like very compartmentalized Apple devices that are 17:24.460 --> 17:28.700 like tied to different accounts or you don't use any Apple services on them, then maybe 17:28.700 --> 17:32.300 there's a use case where like maybe a home desktop doesn't need lockdown mode, but the 17:32.300 --> 17:38.080 phone you take with you does. But overall, that's what I would say to that question. 17:38.360 --> 17:42.420 Did I miss something here? In terms of the digital forensic tools, I think, you know, 17:42.940 --> 17:48.000 the main thing I associate lockdown mode with is actually like mercenary spyware. 17:48.000 --> 17:54.100 Like that's kind of what I'm associating lockdown mode with. Not so much. And actually, 17:54.220 --> 17:58.500 let me check. I want to make sure. Okay, I want to make sure I wasn't like the big view here. 17:59.740 --> 18:05.260 And the main thing of lockdown mode that I think might impact this, the digital forensic tools, 18:05.340 --> 18:10.360 is the fact that it actually has forces on the feature where you can't plug things in unless 18:10.360 --> 18:13.780 your device is unlocked. So that might have something to do with the digital forensics 18:13.780 --> 18:17.880 tools. But again, I associate personally lockdown mode as being more of a spyware thing. 18:18.420 --> 18:22.600 Um, yeah, I guess I didn't really answer your first question. Lockdown mode, it's it's, 18:22.600 --> 18:26.700 I would call it reductionist. It's not adding anything. It's not like you're installing 18:26.700 --> 18:31.260 an antivirus. You're not installing a VPN. You're not installing something to do 18:31.260 --> 18:35.840 something extra for you. Lockdown mode does the opposite. It actually removes things. 18:36.040 --> 18:40.860 It removes features. It removes or changes the way that features work to pretty much 18:40.860 --> 18:47.340 prevent almost all of the avenues that someone well equipped can try to exploit 18:47.340 --> 18:53.340 to attack your device. And to this day, Apple still recently said that they have not found 18:53.340 --> 18:57.720 any sign of lockdown mode being bypassed for any kind of mercenary spyware, which is really impressive. 18:58.640 --> 19:05.120 So yeah, let's see. All right, let me go ahead and bump over to the live chat. 19:09.660 --> 19:22.030 Let's see. On topic of staying on top, I actively stopped looking at privacy stuff for 19:22.030 --> 19:24.530 a few months when the whole chat control and age verification started to hit. 19:24.630 --> 19:26.270 It was starting to stress me out too much. Yeah. 19:28.470 --> 19:32.590 It's a really tough line to draw because, you know, we want to make sure we're staying up 19:32.590 --> 19:35.870 to date on these things so that we can stay active in them. 19:38.850 --> 19:42.710 But at the same time, I also think that the long-term sustainability 19:43.610 --> 19:46.410 of keeping up with things should be sustainable. 19:47.510 --> 19:51.630 That was worded horribly, but I hope you guys know what I'm saying. 19:52.390 --> 19:58.290 I just feel like there is some kind of balance that we have to find where 19:59.930 --> 20:04.210 if you have to take a few months off, then when you come back, how can I 20:04.770 --> 20:08.150 still keep up with these things but not have to take three months off again? 20:08.370 --> 20:12.530 It's kind of the question I would pose. So maybe it's, hey, I just checked the news 20:12.530 --> 20:16.510 each weekend. Once a week, that's actually pretty good, right? 20:16.710 --> 20:18.810 Like it means that you're going to catch almost all the stuff. 20:18.970 --> 20:22.270 It means that you don't have to like keep up with it during the week 20:22.270 --> 20:23.750 when you're probably the most overwhelmed. 20:24.430 --> 20:26.770 And it means that you can even set aside an hour. 20:27.090 --> 20:29.550 Like it doesn't have to be a weekend, just like an hour over the weekend 20:29.550 --> 20:31.630 where I go ahead and actively look at this stuff. 20:31.750 --> 20:34.770 That's actually like the whole inspiration behind surveillance support, right? 20:35.010 --> 20:38.390 The reason my surveillance support started is for this job, 20:38.410 --> 20:40.710 I literally have to keep up with news all the time. 20:40.710 --> 20:44.150 And I hate keeping up with news. And so for me, it just wasn't fun. 20:44.570 --> 20:50.710 And so I still do it because it's my job and it's something I love doing for you guys 20:50.710 --> 20:52.230 and people clearly like the podcast. 20:52.390 --> 20:55.130 And the podcast has just been extremely successful over the years. 20:56.070 --> 20:59.570 But the whole point of the podcast is so that people don't have to do that. 20:59.790 --> 21:03.250 Like that really is, I think the main selling point of surveillance support is like, 21:03.310 --> 21:08.110 hey, you don't have to follow news from like 100 different sources each week. 21:08.110 --> 21:13.090 Just watch this 45 minute podcast and you will get everything you need to know for the week. 21:13.350 --> 21:17.450 So I hope that like, you know, that's what it's doing. 21:19.110 --> 21:22.190 Other than that, I hope you can find some kind of balance for yourself 21:22.190 --> 21:23.210 because I think it's important. 21:24.390 --> 21:26.370 Gothic Life Your Personal Day is very much connected with your work. 21:26.450 --> 21:27.870 I think I addressed that one earlier. 21:29.830 --> 21:30.710 This is a good one. 21:30.890 --> 21:34.470 Ophelia says, for me, the privacy burnout is not from what I'm doing myself, 21:34.470 --> 21:38.970 but seeing the people around me absolutely not care about privacy at all. 21:39.410 --> 21:42.770 Yeah, I think it's always hard because privacy is a social thing. 21:43.450 --> 21:46.470 And I think there's almost maybe a loneliness to it, right? 21:46.590 --> 21:49.690 Like if there's something that you care about that you're putting a lot of time into, 21:49.790 --> 21:51.050 but the people around you aren't. 21:51.230 --> 21:53.950 I think that is inherently, you know, kind of isolating. 21:54.130 --> 21:55.630 So I can definitely see that. 21:55.750 --> 21:56.850 And I mean, I feel it too. 21:57.430 --> 22:00.550 For me, I like going to events like I go to, 22:00.710 --> 22:03.230 and I try to do coverage for the events when I go on the channel. 22:03.710 --> 22:07.050 But it's also really fun to be around other people who care about these things 22:07.050 --> 22:08.850 where you don't have to explain yourself. 22:09.070 --> 22:10.930 There is no, oh, here's why I do this. 22:10.970 --> 22:13.330 People just ask, oh, like what are you doing for this? 22:13.350 --> 22:15.050 Which is a different conversation, right? 22:15.510 --> 22:20.910 Like what a conversation about why you do something versus what you're doing is very different. 22:22.650 --> 22:24.430 So yeah, I think that's the first thing. 22:24.490 --> 22:29.130 The second thing is if you can just try to find some way to feel optimistic 22:29.130 --> 22:30.790 when you're engaging with it yourself, 22:30.790 --> 22:33.310 whether that's for some people, it's joining a community 22:33.810 --> 22:35.470 of other people going through the journey. 22:35.790 --> 22:39.830 For some people, it's disconnecting from that, right? 22:39.950 --> 22:41.650 Like for some people, they don't want to be a part of it. 22:41.690 --> 22:42.910 And for them, it's a lot more intrinsic, 22:43.130 --> 22:44.630 the reason why they're doing these things. 22:45.590 --> 22:47.750 So I hope something there resonated with you, 22:47.790 --> 22:49.650 but it's a tough place to be. 22:52.810 --> 22:56.270 Lizzie Taj says, I've been under the impression that DNS control 22:56.270 --> 22:59.370 blocking is hugely important when it comes to privacy. 22:59.370 --> 22:59.950 Would you agree? 22:59.950 --> 23:07.110 Actually, I think DNS is kind of the thing that I have evolved my views on 23:07.110 --> 23:09.430 maybe the most the last few years or one of the most. 23:09.590 --> 23:12.430 I can't measure that, but I feel like it's something that... 23:13.590 --> 23:16.510 I didn't completely ignore DNS back in the day, 23:16.550 --> 23:18.870 but I didn't realize just how powerful it really was, 23:18.930 --> 23:22.510 especially the blocking aspect of things until maybe a couple of years ago, 23:22.770 --> 23:24.050 especially on mobile devices, 23:24.210 --> 23:26.550 because mobile devices don't let you do anything, right? 23:26.550 --> 23:31.290 Like if an app bundles itself with a third-party SDK 23:31.290 --> 23:34.150 to the invasive company, you can't really block the SDK. 23:34.970 --> 23:36.050 There's not much you can do. 23:36.150 --> 23:39.190 It's not like a browser where a browser can actually block elements 23:39.670 --> 23:42.830 from the website, and it can give you fingerprinting resistance, 23:42.930 --> 23:44.750 and it can do really fun, cool things. 23:45.310 --> 23:47.430 So the closest thing we can do is DNS blocking. 23:47.730 --> 23:49.690 And that's why I think DNS blocking is really powerful, 23:49.750 --> 23:52.870 is it can actually deal with apps that otherwise there's nothing 23:52.870 --> 23:55.730 you can really do to make them a little bit more privacy-respecting. 23:55.730 --> 23:58.030 So, I'm a fan. 24:00.290 --> 24:03.630 I need a tablet for school as an iPad, the best privacy tablet, 24:03.750 --> 24:06.070 especially with Graphene StopPixel tablet support soon. 24:06.210 --> 24:08.370 Also, what are your thoughts on Open Slate by Brax, 24:08.470 --> 24:09.350 their upcoming tablet? 24:09.890 --> 24:11.790 I don't have many thoughts on their devices. 24:13.250 --> 24:16.330 Yeah, I always want to tread carefully 24:16.330 --> 24:18.390 because I know that building products is really challenging, 24:18.390 --> 24:20.950 and it's not to discount that they could be good devices, 24:20.950 --> 24:25.110 but I do think that I'm always going to trust... 24:25.110 --> 24:26.490 And this goes for us as well. 24:26.830 --> 24:29.810 Like, you know, we're content first, and then services second. 24:29.970 --> 24:31.710 That doesn't mean we can't build good services, 24:31.710 --> 24:34.550 but I also think building a website with some tools 24:34.550 --> 24:37.270 is a lot easier than building a full phone 24:37.270 --> 24:38.430 with hardware and software. 24:39.630 --> 24:42.910 So, yeah, I would just say, like, if you trust the tool, 24:43.030 --> 24:43.870 then definitely use it. 24:43.990 --> 24:45.870 I personally would probably be looking more at, 24:45.870 --> 24:48.630 like, Calyx or Graphene, and then just getting my own phone. 24:49.850 --> 24:52.030 That's personally how I would go about it. 24:52.710 --> 24:54.230 In terms of a tablet for school, though, 24:54.230 --> 24:56.390 I actually don't think it matters too much, right? 24:56.530 --> 24:57.890 Like, we talked about this earlier. 24:58.050 --> 24:59.590 I think it's more about compartmentalization, 24:59.810 --> 25:02.350 like work, school, all of these things. 25:02.710 --> 25:05.050 Like, yes, it might have your name in the settings, 25:05.050 --> 25:07.090 but overall, you can have that device 25:07.090 --> 25:08.970 be used for that one use case. 25:09.230 --> 25:12.710 You can literally power off the device physically, 25:12.990 --> 25:15.070 and only power it on at school 25:15.070 --> 25:17.950 or when you're, like, at a cafe or at the library to study. 25:18.350 --> 25:19.190 And that's it. 25:19.290 --> 25:21.690 That's where it exists, and it's logged into 25:21.690 --> 25:23.670 even, like, your school's EDU email. 25:23.910 --> 25:25.950 You set up a new Apple account with the EDU email. 25:26.110 --> 25:28.910 Like, you can really set up, like, different lives 25:28.910 --> 25:30.770 for yourself, and you can have these devices 25:30.770 --> 25:31.730 follow those lives. 25:31.930 --> 25:34.470 And that way, there isn't really that much personal exposure. 25:35.130 --> 25:38.430 And it's really, I think, the easiest way 25:38.970 --> 25:41.110 to make privacy easy, actually. 25:41.710 --> 25:43.630 If you're trying to go for absolute privacy 25:43.630 --> 25:44.930 in all areas of your life, 25:45.350 --> 25:47.590 it's gonna be extremely difficult, if not impossible, 25:47.730 --> 25:50.390 unless you wanna just, you know, live at home all day 25:50.390 --> 25:51.690 and never leave the house. 25:51.970 --> 25:54.150 And complete recluse-style lifestyle. 25:54.830 --> 25:56.370 So I really think compartmentalization 25:56.370 --> 25:57.550 is how you can pull this off. 26:02.890 --> 26:03.670 Let's see. 26:04.610 --> 26:06.930 Any personal information is enough to make dots between. 26:07.710 --> 26:10.130 Yeah, I got, like, right, I'm not saying 26:10.130 --> 26:13.590 that's not the case, but it's about risk reduction. 26:13.870 --> 26:15.690 Again, you're not gonna be perfect. 26:16.370 --> 26:18.410 Like, if that, if your point 26:18.410 --> 26:19.610 is any personal information is enough 26:19.610 --> 26:21.530 to make dots between your personal and your work life, 26:21.690 --> 26:23.890 well, what are you suggesting in that situation, right? 26:24.050 --> 26:25.830 Like, what is your real suggestion there? 26:26.090 --> 26:29.050 Is it to, like, I don't know. 26:29.130 --> 26:30.030 Like, how is that actionable? 26:30.630 --> 26:35.150 So I really do think that compartmentalization, 26:35.410 --> 26:38.310 as much as you can, can actually get you very far. 26:38.390 --> 26:40.450 And it's a very nice middle ground for a lot of people. 26:43.110 --> 26:45.730 What crypto prepaid Visa Mastercard disposable cards 26:45.730 --> 26:46.370 do you recommend? 26:47.050 --> 26:49.330 I use CakePay personally in CakeWallet. 26:49.330 --> 26:50.770 It's just, I already use CakeWallet. 26:50.910 --> 26:53.090 CakePay's already built in, and so it's really easy to use that. 26:53.610 --> 26:57.170 I also know there's CoinCards, and that's another really good tool. 26:58.170 --> 27:01.310 I don't, I have never done a prepaid Visa through CoinCards, 27:01.710 --> 27:04.770 but I've definitely done them with CakePay, 27:04.850 --> 27:05.550 and it works really nicely. 27:15.020 --> 27:18.200 I'm still deciding on my future non-Gmail email account. 27:18.360 --> 27:20.400 Does anyone have experience of Infomaniac 27:20.400 --> 27:21.800 and how private their email is? 27:24.000 --> 27:25.780 Yeah, Infomaniac looks interesting. 27:25.780 --> 27:28.180 A lot of people have asked for a review of it. 27:28.800 --> 27:32.660 I haven't personally used it yet, so I don't have any feedback there. 27:37.740 --> 27:40.920 It's their way to alias credit cards for free while keeping privacy. 27:41.140 --> 27:45.140 I don't think credit cards, unless your credit card company does that. 27:45.740 --> 27:48.560 Like, I believe Capital One has a feature like that 27:48.560 --> 27:50.840 that I think does work on credit cards, actually. 27:52.460 --> 27:55.700 So there are some tools, but no, even Privacy.com, 27:55.840 --> 27:59.600 which I'm a big fan of, they don't support credit. 27:59.600 --> 28:01.480 It's just debit cards, which is a bit sad. 28:04.460 --> 28:06.020 Yeah, yeah, you're welcome. 28:08.580 --> 28:10.900 All right, let's switch back to the questions. 28:11.180 --> 28:13.840 It's a light week this week, so it's nice because I'm exhausted. 28:15.780 --> 28:16.400 Let's see. 28:16.780 --> 28:17.060 Hi, Henry. 28:17.180 --> 28:18.920 I have a question about VPNs and proxies. 28:19.000 --> 28:20.100 I really like this question, 28:20.180 --> 28:21.700 because a lot of people don't know how this works, 28:21.840 --> 28:25.740 so it's a chance for me to showcase a feature 28:25.740 --> 28:26.980 that people don't know much about. 28:26.980 --> 28:30.280 In the MOLVAD browser, when using their extension, 28:30.520 --> 28:32.240 when you enable random mode on all sites, 28:32.380 --> 28:33.300 it routes through a proxy. 28:33.580 --> 28:34.660 Is this on top of a VPN? 28:35.060 --> 28:37.040 I'm using a system-wide VPN with lockdown mode enabled, 28:37.120 --> 28:39.720 plus all sites on random in the extension on the MacBook. 28:40.840 --> 28:42.740 So, yeah, or MOLVAD browser, I guess. 28:43.080 --> 28:44.940 MOLVAD browser and B could be either, 28:45.100 --> 28:46.420 but it sounds like both apply to you. 28:47.640 --> 28:51.480 So lockdown mode is irrelevant here, so ignore that. 28:51.780 --> 28:53.480 That doesn't, it shouldn't change anything 28:53.480 --> 28:54.860 as part of your question. 28:54.860 --> 28:56.700 Now, what people don't know 28:56.700 --> 28:59.220 is that the proxy inside of MOLVAD 29:00.460 --> 29:04.020 only works if you are connected to MOLVAD VPN. 29:04.680 --> 29:07.780 So it's actually not at all like other extensions. 29:07.960 --> 29:09.940 So when you see the Wendscribe extension, 29:10.180 --> 29:11.560 the ProtonVPN extension, 29:12.040 --> 29:13.860 really any VPN that has an extension, 29:14.040 --> 29:15.540 that's just like in the Chrome store 29:15.540 --> 29:16.920 or in the Firefox store, 29:17.980 --> 29:20.800 what those do is they are essentially 29:20.800 --> 29:24.140 just creating a SOX5 proxy in your browser, 29:24.140 --> 29:26.300 and it's still overall going to give you 29:26.300 --> 29:27.960 the IP protection of a VPN, 29:28.200 --> 29:29.680 but it's keeping it within your browser. 29:30.380 --> 29:31.540 MOLVAD is a bit different. 29:31.700 --> 29:33.140 It's still a SOX5 proxy, 29:33.480 --> 29:36.100 but again, it requires you to be connected 29:36.100 --> 29:37.240 to their VPN first. 29:37.460 --> 29:39.520 So it's actually a multi-hop kind of. 29:39.940 --> 29:42.340 It's, you're connecting to MOLVAD VPN servers, 29:42.540 --> 29:44.460 and then from the VPN server, 29:44.560 --> 29:48.000 it connects to the SOX5 proxy in the extension. 29:48.240 --> 29:50.200 So then the site sees the proxy, 29:50.400 --> 29:52.040 not even the MOLVAD exit node. 29:52.600 --> 29:55.220 So you see it's almost a multi-hop 29:55.220 --> 29:56.540 with a VPN and a proxy. 29:56.720 --> 29:59.140 It's a very interesting workflow, 29:59.140 --> 30:00.900 and why it's actually really powerful 30:00.900 --> 30:03.040 is that because you set it to random, 30:03.280 --> 30:05.200 it means every site per tab 30:05.680 --> 30:08.000 is going to get a different IP address. 30:08.360 --> 30:09.560 It's different than when you connect 30:09.560 --> 30:11.040 to just a system-wide VPN. 30:11.220 --> 30:12.900 When you're connecting to a system-wide VPN 30:12.900 --> 30:15.260 and you access 10 websites in a regular browser, 30:15.620 --> 30:17.320 those 10 websites will still get 30:17.320 --> 30:20.080 the same IP address of your VPN connection, 30:20.080 --> 30:22.300 which typically is fine, right? 30:22.360 --> 30:24.380 Like the, there's a huge, like, 30:24.440 --> 30:26.260 anonymity layer to this 30:26.260 --> 30:28.360 because if you have 10,000 people 30:28.360 --> 30:30.120 connected to the same VPN connection, 30:30.200 --> 30:32.000 they're all going to have the same IP address. 30:32.120 --> 30:33.020 And so you're normally blending 30:33.020 --> 30:34.620 in quite nicely with other people. 30:34.820 --> 30:36.380 But the nice thing about the proxy 30:36.380 --> 30:38.160 is that you still get that anonymity 30:38.160 --> 30:39.940 because there's other people connecting to the proxy. 30:39.960 --> 30:41.820 But now you get a different IP address 30:41.820 --> 30:42.660 on every website. 30:42.800 --> 30:44.360 And in fact, you're using MOLVAD browser, 30:44.420 --> 30:46.860 which is already designed to make users look the same 30:46.860 --> 30:49.500 because it's pretty much like a lightweight Tor browser, 30:49.500 --> 30:49.760 right? 30:51.120 --> 30:52.780 You're getting a lot of privacy from that. 30:52.980 --> 30:55.180 So it's kind of a hidden thing I would recommend 30:55.180 --> 30:56.840 if you want the maximum amount of privacy 30:56.840 --> 30:58.100 out of the MOLVAD browser 30:58.100 --> 31:00.020 to enable the extension and use the proxy, 31:00.200 --> 31:01.520 kind of like you're doing in random mode. 31:02.260 --> 31:04.200 The other nice usability benefit I've found 31:04.200 --> 31:05.120 using the proxy 31:05.120 --> 31:07.100 is that the proxies are typically 31:07.100 --> 31:08.620 a little bit less blocked 31:08.620 --> 31:10.260 than the VPN itself. 31:10.560 --> 31:12.360 Like Reddit is a really good example of this. 31:12.500 --> 31:16.360 Like MOLVAD VPN IPs are to meet, 31:16.480 --> 31:18.300 for me, at least universally blocked by Reddit. 31:18.300 --> 31:20.480 But the proxies, I'd say, are 50-50. 31:20.780 --> 31:21.900 So when I try to access Reddit, 31:22.260 --> 31:25.120 I have a specific proxy I'm connected to just for Reddit 31:25.120 --> 31:26.540 because I know that proxy works. 31:26.820 --> 31:28.960 And then maybe in two months, they block that one too. 31:29.120 --> 31:32.580 But I just have an easier time bypassing those site blocks. 31:33.080 --> 31:35.680 So yeah, that's a pro tip. 31:36.100 --> 31:38.400 I don't know how commonly known that is, 31:38.480 --> 31:40.720 but it was something I definitely wanted to talk about. 31:43.740 --> 31:46.000 It looks like we got some troubleshooting there 31:46.000 --> 31:46.780 in the Signal Group. 31:46.780 --> 31:49.140 Okay, last question. 31:49.260 --> 31:50.520 Again, it was a really light week here. 31:50.800 --> 31:52.660 And then we can just open it up for the live chat. 31:52.920 --> 31:54.780 But it's YodaLuca23. 31:55.180 --> 31:56.740 They said that seems that Google Messages 31:56.740 --> 31:59.520 is finally starting to roll out the full RCS 3.1 spec 31:59.520 --> 32:00.700 in the stable release branch. 32:01.040 --> 32:02.840 That includes RCS end-to-end encryption. 32:03.260 --> 32:05.140 This is a hugely forward for global society. 32:05.360 --> 32:06.580 And I don't think they say it here, 32:06.660 --> 32:09.420 but a couple iOS version updates ago. 32:10.020 --> 32:12.420 Apple also released this so that you can enable it. 32:12.620 --> 32:14.240 I believe it was in beta. 32:14.360 --> 32:15.300 It might still be in beta, 32:15.980 --> 32:18.380 where you can enable RCS with end-to-end encryption 32:18.860 --> 32:20.820 inside of the settings on your Apple device. 32:21.000 --> 32:23.040 So then theoretically, you would get that 32:23.040 --> 32:24.280 between Android and iOS. 32:25.400 --> 32:28.000 Now, the real question a lot of people I communicate with 32:28.000 --> 32:30.360 refuse to get Signal Session, SimpleX, 32:30.420 --> 32:31.900 or any other privacy-focused messenger, 32:31.940 --> 32:33.620 and only WhatsApp or RCS. 32:34.060 --> 32:35.300 So what is my better choice? 32:35.480 --> 32:37.600 And then they kind of go through their thought process 32:37.600 --> 32:42.360 as to like, is WhatsApp better or worse than RCS? 32:42.360 --> 32:47.820 So RCS is using MLS, which is at least like an open standard. 32:48.000 --> 32:48.640 It's something open. 32:48.780 --> 32:50.780 Now, technically, WhatsApp is using Signal's protocol, 32:50.860 --> 32:51.860 which is also open. 32:52.780 --> 32:54.720 But I really think this, I don't know, 32:54.840 --> 32:56.500 first off, it's a wash to me. 32:56.680 --> 32:57.760 Like if I'm comparing them, 32:58.120 --> 33:00.660 I'm not like this one is just across the board, 33:00.740 --> 33:01.400 the better option. 33:01.500 --> 33:03.060 So you should definitely always use this one. 33:03.100 --> 33:04.400 So I'm not gonna like take a, 33:05.580 --> 33:07.240 I'm on the fence as well here. 33:07.880 --> 33:10.920 I don't think you need to decide fully, right? 33:10.920 --> 33:13.520 Like I don't see any harm in having an RCS client 33:13.520 --> 33:14.620 and a WhatsApp client, 33:14.760 --> 33:16.380 and then seeing over time how that develops, 33:16.700 --> 33:18.240 especially because the RCS thing is new. 33:18.480 --> 33:21.800 So I would love to see maybe a little bit more coverage 33:21.800 --> 33:24.360 for the full kind of metadata leakage 33:24.360 --> 33:27.400 if there are any like more independent audits 33:27.400 --> 33:30.060 that are done to try to see how secure it really is. 33:30.480 --> 33:33.680 We might see over time like how good it really is. 33:33.700 --> 33:35.880 And I think over time we'll get the answer of like, 33:35.900 --> 33:38.180 hey, is RCS becoming more popular? 33:38.180 --> 33:42.600 And is it starting to take some of the traffic away from WhatsApp? 33:42.820 --> 33:45.020 If that's the case, then maybe RCS makes more sense. 33:45.780 --> 33:47.420 So the only other thing I'd say 33:47.420 --> 33:49.260 is that at the end of the day, RCS is a standard. 33:50.380 --> 33:52.260 And you're just using a standard, 33:52.340 --> 33:53.440 whereas if you're using WhatsApp, 33:53.620 --> 33:54.740 you're using a private company 33:54.740 --> 33:56.400 that's gonna be associating that traffic 33:56.400 --> 33:58.700 with everything else you do in the Facebook ecosystem. 33:59.620 --> 34:01.560 So again, it's kind of a wash. 34:01.700 --> 34:03.500 These are just kind of the things I'd be thinking about. 34:03.660 --> 34:05.020 And really the biggest hole 34:05.020 --> 34:06.360 is probably gonna be backups, 34:06.540 --> 34:07.980 regardless of what you choose to use. 34:07.980 --> 34:09.020 So if you're using WhatsApp, 34:09.260 --> 34:10.960 but your contacts and yourself 34:10.960 --> 34:12.720 aren't using the encrypted backups feature, 34:13.400 --> 34:16.540 then all of your chats are gonna end up unencrypted 34:16.540 --> 34:18.320 as a cloud backup that they can access. 34:18.740 --> 34:20.380 And same thing with RCS. 34:20.640 --> 34:22.100 I don't know what Google Messages does, 34:22.320 --> 34:24.180 but if Google Messages does do any backups 34:24.180 --> 34:25.460 that aren't fully encrypted, 34:26.000 --> 34:27.840 then your messages would end up there as well. 34:28.200 --> 34:29.260 So I'd be looking at that, 34:29.600 --> 34:31.020 try to meet people where they're at 34:31.020 --> 34:32.580 with the best tool you can give them. 34:33.040 --> 34:34.080 So, yeah. 34:34.160 --> 34:35.940 And actually, JMR just had a really good point. 34:35.940 --> 34:37.520 You have to watch for old text protocol 34:37.520 --> 34:38.560 fallback from RCS. 34:38.780 --> 34:39.480 It's a really good point. 34:39.620 --> 34:40.240 When you're using WhatsApp, 34:41.240 --> 34:44.840 fairly certain there is no way to somehow fall back 34:44.840 --> 34:46.780 to something that's not end-to-end encrypted. 34:47.380 --> 34:50.020 But when you are using something that is RCS 34:50.020 --> 34:50.820 with end-to-end encryption, 34:50.980 --> 34:53.120 you're in a client that probably can fall back 34:53.120 --> 34:54.500 to something a lot worse. 34:54.640 --> 34:55.280 It's a really good point. 34:55.500 --> 34:56.300 So thanks for saying that. 34:57.660 --> 34:59.420 But that's actually it for the week, guys. 35:00.520 --> 35:01.860 So let me go ahead 35:01.860 --> 35:03.700 and we can just stay here in the live chat 35:03.700 --> 35:04.600 and have some fun. 35:05.300 --> 35:06.480 If you're in a signal group, 35:06.700 --> 35:08.840 definitely say that you're in the signal group. 35:09.400 --> 35:12.540 Otherwise, let me switch these around. 35:14.540 --> 35:15.820 Swap tab positions. 35:16.980 --> 35:18.460 Do I even need this? 35:19.060 --> 35:20.280 Honestly, I kind of don't. 35:21.060 --> 35:22.500 Why don't we just leave it like that? 35:23.060 --> 35:25.500 And then I have the signal room open. 35:26.240 --> 35:27.680 If you guys want to join a signal group, 35:27.840 --> 35:29.960 it is open to all our techlorians, 35:30.060 --> 35:31.580 even the smallest techlorian tier. 35:32.260 --> 35:34.040 You get access to our signal group. 35:34.420 --> 35:35.900 It's something that's a lot of fun. 35:36.040 --> 35:36.820 I get active there. 35:36.940 --> 35:38.960 It's our only community left at this point. 35:39.100 --> 35:40.780 It's the only one that we're able to maintain. 35:41.300 --> 35:42.580 We're a two-person team. 35:42.680 --> 35:44.280 So the forum was just way too much for us. 35:44.640 --> 35:46.600 Even with moderators, it was just a lot of work. 35:46.920 --> 35:49.360 So I'm really happy to still have at least one community. 35:50.220 --> 35:52.080 And yeah, you also get to access my RSS feed. 35:52.220 --> 35:53.300 Like on the topic of burnout, 35:53.580 --> 35:55.860 like I maintain my own RSS feed 35:56.260 --> 35:58.300 to track all the surveillance report stories. 35:58.800 --> 36:01.340 And so if you want to be able to just track one feed 36:01.340 --> 36:03.100 and not have to track hundreds of things, 36:03.620 --> 36:05.640 that's something that's also part of the techlorians. 36:06.120 --> 36:07.460 And you can join that down in the description. 36:07.680 --> 36:08.460 It's a big help for us. 36:12.140 --> 36:12.820 Let's see. 36:14.780 --> 36:16.700 What was the name of the other card provider, 36:16.820 --> 36:17.800 the one you said after CakePay? 36:17.940 --> 36:19.380 It's called CoinCards. 36:21.840 --> 36:24.720 Again, I didn't have as good of an experience with it 36:24.720 --> 36:25.660 as I do with CakePay, 36:26.520 --> 36:28.240 but I still like CoinCards. 36:28.340 --> 36:29.340 It's still a really good service. 36:31.180 --> 36:34.200 Can anyone remember the name of the iOS app he showed us 36:34.200 --> 36:35.780 that shows all the secrets your iPhone leaks? 36:35.920 --> 36:37.140 Yeah, it's called Loop. 36:37.840 --> 36:39.920 L-O-U-P-E, I believe. 36:40.300 --> 36:41.040 I believe it's called Loop. 36:50.730 --> 36:51.710 Yeah, it's a good point. 36:52.650 --> 36:52.910 Hi. 36:53.390 --> 36:55.970 Hello, Amethyst... 36:57.330 --> 36:58.490 Uh, Emi. 37:01.970 --> 37:02.430 Amethystangel216. 37:02.610 --> 37:03.190 Hello, hello. 37:04.130 --> 37:06.790 I do not have any info on CHOMP SMS. 37:06.790 --> 37:08.450 I have never heard of a CHOMP. 37:10.650 --> 37:11.490 Thanks again, Henry. 37:11.710 --> 37:12.450 Yeah, of course, of course. 37:13.110 --> 37:13.430 Yeah. 37:13.690 --> 37:15.790 So guys, this is the open time. 37:16.010 --> 37:17.830 Maybe we'll go to just an hour this week. 37:17.870 --> 37:20.070 We don't need to push this further than it needs to go. 37:20.350 --> 37:22.330 So say hi if you have a question for me, 37:22.410 --> 37:23.650 if you have a question about privacy, 37:23.890 --> 37:27.630 security, digital rights, the world, whatever. 37:28.170 --> 37:28.450 I'm here. 37:30.450 --> 37:31.630 It's meant to be the office hours, 37:31.690 --> 37:33.350 so we can just kind of chill and have a good time here. 37:33.630 --> 37:34.430 If you're in a signal group, 37:34.630 --> 37:35.790 same thing goes to you guys. 37:37.990 --> 37:38.970 Steve, Henry's still here. 37:39.070 --> 37:41.290 One of the rare times I've been free for this slot. 37:41.590 --> 37:42.170 Yay, yeah. 37:42.510 --> 37:44.910 I feel like I haven't seen you on the live chat often, 37:45.170 --> 37:46.050 if ever. 37:46.190 --> 37:46.830 I don't want to say ever, 37:46.910 --> 37:48.410 because maybe there was a time where you were on 37:48.410 --> 37:49.010 and I'm forgetting. 37:49.710 --> 37:50.810 But it's good to have you on. 37:55.350 --> 37:56.010 Let's see. 37:56.350 --> 37:58.370 Grant Sherman, have you heard of File-In, 37:58.470 --> 37:59.710 the cloud storage provider? 37:59.950 --> 38:02.050 You should do a privacy cloud storage tier list. 38:02.670 --> 38:06.490 Actually, we did do some coverage for File-In. 38:06.490 --> 38:07.170 Way back. 38:07.310 --> 38:08.850 I think this was four or five years ago. 38:08.970 --> 38:12.930 We did a video on top five Google Drive alternatives 38:12.930 --> 38:14.950 or just end-end encrypted cloud providers. 38:15.530 --> 38:16.390 And File-In was on there. 38:17.030 --> 38:18.850 I forgot if File-In's on our website, 38:19.430 --> 38:20.890 actually, on our tools page. 38:21.350 --> 38:22.430 Let's find out here. 38:24.490 --> 38:24.970 Tools. 38:27.110 --> 38:28.370 Yeah, File-In's on there. 38:30.970 --> 38:33.310 We just can't do coverage for everything. 38:33.650 --> 38:35.470 We don't have a Firefox-focused video. 38:35.470 --> 38:37.930 We don't have a Duck-to-Go browser video. 38:38.110 --> 38:39.330 We don't have a Waterfox video. 38:39.510 --> 38:41.670 Like, there's just so many tools that we don't have videos on. 38:41.890 --> 38:45.410 So I do think that the nice thing about having the site tools 38:45.410 --> 38:47.330 is that we can still kind of keep up with things 38:47.330 --> 38:48.350 a bit better on a website. 38:48.810 --> 38:50.610 Because content is really hard. 38:50.670 --> 38:53.210 It's hard to put together a content version of sites. 38:53.630 --> 38:54.670 It just takes a lot more time. 38:57.490 --> 38:59.430 How's the compatibility with using crypto wallets 38:59.430 --> 39:00.610 for regular commercial use? 39:00.730 --> 39:02.410 Are these usable in place of credit cards? 39:03.350 --> 39:04.870 Yeah, I don't think so. 39:04.870 --> 39:07.210 Some businesses, you can look at maps online 39:07.210 --> 39:08.750 of businesses that support cryptocurrency. 39:09.210 --> 39:10.030 I think that's what you're asking. 39:12.090 --> 39:14.290 But ultimately, I think for a regular person, 39:14.430 --> 39:16.850 if you're trying to use cryptocurrency day-to-day, 39:17.090 --> 39:19.290 you're probably going to have to use one of these bridges, 39:19.490 --> 39:21.290 like using a prepaid Visa gift card. 39:21.870 --> 39:23.130 I've done the experiment before. 39:23.370 --> 39:24.990 It's actually really fun where it's like, 39:25.090 --> 39:28.270 okay, can I spend a week and only use cryptocurrency? 39:29.570 --> 39:31.790 And specifically, CakePay, back in the day, 39:32.030 --> 39:34.550 I did a showcase partnered video with CakePay. 39:34.550 --> 39:37.630 This was a long time ago, back when they first released the feature. 39:37.850 --> 39:40.670 And it was like, I did a road trip just using CakePay. 39:40.750 --> 39:42.030 So I bought the hotel with it. 39:42.170 --> 39:44.610 I got our food with it. 39:44.690 --> 39:46.330 And it was a really fun video to record. 39:46.890 --> 39:48.810 We drove into the Humboldt Mountains 39:48.810 --> 39:50.770 and the Redwoods and the Giants. 39:50.850 --> 39:52.130 So it was really cool. 39:53.950 --> 39:56.970 So I think that is really the main way to do it. 39:57.210 --> 39:58.810 Most people don't support cryptocurrency. 39:59.150 --> 40:00.930 And so if you want to actually use it more often, 40:01.650 --> 40:04.290 you need to probably find people who natively support it 40:04.290 --> 40:05.290 and use that when you can. 40:05.510 --> 40:07.970 But otherwise, you have to use something like a gift card 40:07.970 --> 40:08.850 that you purchase. 40:09.070 --> 40:10.250 And it's kind of like a workaround. 40:12.390 --> 40:13.790 Do you have a referral link for CakePay? 40:13.870 --> 40:14.950 No, I don't think there's referral links. 40:16.070 --> 40:17.430 So yeah, just use it. 40:18.130 --> 40:19.950 Create an app that uses Google Drive for storage, 40:20.030 --> 40:21.410 but it encrypts the file before uploading it. 40:21.490 --> 40:23.250 Nice. How does it compare to like CryptoMator? 40:23.730 --> 40:25.370 Like what's the difference between CryptoMator? 40:27.330 --> 40:28.730 Anyone here have info on CHOP? 40:30.590 --> 40:31.750 What is CHOP SMS? 40:32.370 --> 40:33.170 I have to know now. 40:33.170 --> 40:34.850 I'm going to pull it in my other browser. 40:35.090 --> 40:36.110 I don't trust you guys always. 40:36.630 --> 40:36.790 I know. 40:37.550 --> 40:39.850 There's like pranks and stuff that you guys could play. 40:40.210 --> 40:40.750 CHOP SMS. 40:41.010 --> 40:42.270 Okay, no, it's a real thing. 40:42.410 --> 40:42.830 It's a real thing. 40:43.570 --> 40:45.130 I'm seeing it on the Google Play Store. 40:45.430 --> 40:46.590 It looks like an SMS client. 40:47.850 --> 40:49.570 It looks like just an SMS client. 40:50.090 --> 40:52.690 I don't see what about it would be better or worse 40:53.370 --> 40:58.230 for your privacy unless they're uploading any of that data elsewhere. 40:59.770 --> 41:01.170 But I'm on their site. 41:01.170 --> 41:05.210 I would guess it's like more of a generic SMS client from what I can tell. 41:08.970 --> 41:12.330 How can I still use YouTube while keeping the recommended feed? 41:12.550 --> 41:14.110 The issue with the YouTube offshoots 41:14.110 --> 41:16.910 are that you lose the convenience of a curated feed. 41:17.410 --> 41:20.170 Personally, I think that's like the whole benefit 41:20.690 --> 41:23.290 to using something without a feed. 41:23.410 --> 41:24.310 Like I think that's a good thing. 41:25.130 --> 41:26.910 But if you really want that feed, 41:27.430 --> 41:30.430 I mean, I don't know how else you're going to recreate that. 41:31.210 --> 41:34.490 You're going to have to use YouTube probably to do that. 41:34.630 --> 41:37.510 In that case, then like use YouTube in a dedicated browser 41:38.050 --> 41:41.030 that's only used for YouTube, maybe use an ad blocker 41:41.030 --> 41:42.630 because you can still have an ad blocker 41:42.630 --> 41:43.890 and still get the recommendations. 41:45.130 --> 41:47.250 That's probably the direction I would go 41:47.250 --> 41:50.090 if those are the specific things that you want. 41:54.350 --> 41:55.790 Speaking of Firefox focus, 41:56.010 --> 41:57.730 I used to have it as my main browser. 41:58.130 --> 41:59.970 So links from other apps open in it 41:59.970 --> 42:02.530 instead of normal Firefox issue is it doesn't have extensions. 42:02.770 --> 42:03.930 Do you think focus is worth it? 42:03.990 --> 42:06.390 I think focus is nice for just a disposable browser. 42:07.070 --> 42:10.050 So if you want your default browser to just open things 42:10.050 --> 42:11.730 and then they don't permanently stay, 42:11.930 --> 42:13.630 I think focus is really nice for that use case. 42:14.030 --> 42:16.690 DuckDuckGo is going to offer something quite similar there too. 42:17.250 --> 42:18.210 So it's kind of your call, 42:18.350 --> 42:19.930 what you want your default browser to do. 42:22.010 --> 42:23.750 I've been in both phases myself. 42:24.030 --> 42:25.130 Like I've been in a phase where it's like, 42:25.230 --> 42:26.330 I actually want my default browser 42:26.330 --> 42:28.690 to be the browser I'm using to log into accounts, etc. 42:28.690 --> 42:30.910 And I've also been in a situation where it's like, 42:30.990 --> 42:32.810 I want my default browser to just wipe everything 42:32.810 --> 42:34.870 when I'm done on mobile specifically, right? 42:35.410 --> 42:36.790 On desktop, I'm always like, 42:36.930 --> 42:38.750 my default browser is always like my account browser, 42:38.770 --> 42:40.970 but on mobile, I've kind of gone back and forth there. 42:41.210 --> 42:42.090 So try them out. 42:42.270 --> 42:44.750 I mean, they're, see what you like better too. 42:45.070 --> 42:47.030 There's no, like none of these are bad options. 42:50.450 --> 42:51.790 Yeah, good luck over there. 42:52.210 --> 42:56.010 I hope that it's not too bad troubleshooting what's going on. 42:56.010 --> 42:57.670 I remember when I got my, 42:58.650 --> 43:01.910 like my first PC build was the Skylake build 43:01.910 --> 43:05.070 with like the 6700K, I believe. 43:06.750 --> 43:12.450 And pretty much like, it was a good computer. 43:12.590 --> 43:13.470 It just worked really nicely. 43:13.630 --> 43:16.710 And then I kind of like started getting into this mode. 43:16.850 --> 43:18.450 It's an issue that I think a lot of people go through 43:18.450 --> 43:21.090 where it's like, oh, I want to be more professional 43:21.090 --> 43:22.710 and I want to be more like a business, 43:23.570 --> 43:25.170 even though we're like a two person team, 43:25.170 --> 43:27.690 just kind of like figuring this stuff out as we go, right? 43:28.070 --> 43:29.550 But I went through this phase and so I was like, 43:29.670 --> 43:31.790 okay, I'm going to build like a really nice PC 43:31.790 --> 43:36.190 using more like business-esque style hardware. 43:36.570 --> 43:39.470 So I got the Skylake X processor, big mistake. 43:40.410 --> 43:41.850 That thing was a pain in the ass. 43:42.050 --> 43:43.470 I, you know, because it's like 43:43.470 --> 43:44.830 a little bit more of a niche processor, 43:44.990 --> 43:47.270 I had to get a much more expensive motherboard. 43:48.090 --> 43:51.430 And then the thing ran so flipping hot. 43:51.430 --> 43:54.550 Like I got the nicest Noctua Air fan 43:55.110 --> 44:00.290 and that thing ran idling at like 50, 60 Celsius sometimes. 44:00.470 --> 44:02.350 And when I actually hit it hard with a video edit, 44:02.490 --> 44:04.290 it would crack 100 Celsius. 44:05.370 --> 44:09.110 So I actually had to set up my first liquid cooled PC 44:09.110 --> 44:10.210 just for that thing. 44:10.390 --> 44:16.030 So literally, like this is why, I don't know, like in life, 44:16.170 --> 44:18.110 I've learned to try to always take the simplest path 44:18.110 --> 44:22.170 where I can because like the amount of downstream impacts 44:22.170 --> 44:24.230 from one choice is like crazy. 44:24.350 --> 44:25.110 It blows my mind. 44:25.250 --> 44:26.770 Like me choosing to go with that processor, 44:26.770 --> 44:29.030 it changed the CPU cooler I had to buy. 44:29.150 --> 44:30.290 It changed the motherboard I had to buy. 44:30.490 --> 44:32.430 It changed literally the GPU I had to buy. 44:32.670 --> 44:34.290 Like everything downstream had to change 44:34.290 --> 44:36.150 as a result of the CPU I picked. 44:36.770 --> 44:39.510 So never underestimate like a decision you're making 44:39.510 --> 44:41.790 that might seem a little complicated on day one 44:41.790 --> 44:44.030 and like what it really means long-term. 44:45.270 --> 44:46.810 And we see this everywhere. 44:46.810 --> 44:48.730 Like the operating system you choose to use 44:48.730 --> 44:50.410 literally impacts everything downstream. 44:50.610 --> 44:53.030 This is like one of the main selling points, I think, 44:53.030 --> 44:54.370 actually for the Apple ecosystem. 44:55.110 --> 44:57.450 It's like, and again, this is all personal preference, 44:57.450 --> 44:59.690 but when you choose to use the Apple ecosystem, 45:00.050 --> 45:02.750 you get 80% of everything over the cloud 45:02.750 --> 45:03.950 with end-to-end encryption. 45:04.210 --> 45:05.290 It's not the best end-to-end encryption. 45:05.430 --> 45:06.910 There's still metadata collection from Apple. 45:07.190 --> 45:08.050 I get that, right? 45:08.590 --> 45:10.230 But it takes care of everything for you. 45:10.570 --> 45:11.950 If you go with something like Graphene, 45:12.230 --> 45:14.130 still a great project, you can still recreate 45:14.130 --> 45:16.770 that experience, but it's gonna take a lot more work. 45:17.310 --> 45:19.310 So again, there's no right answer. 45:19.430 --> 45:20.310 You're gonna get a lot of benefits 45:20.310 --> 45:22.650 by doing that latter thing as well in other areas. 45:22.770 --> 45:24.710 But it's those kind of decisions 45:24.710 --> 45:26.750 that people don't put as much emphasis on. 45:26.850 --> 45:28.170 People are a lot more likely to go, 45:28.290 --> 45:31.490 how does iOS and their sandboxing 45:31.490 --> 45:33.590 compare to Android and their sandboxing? 45:33.770 --> 45:35.930 But realistically, the real secret 45:35.930 --> 45:37.630 is that that's probably not going 45:37.630 --> 45:39.290 to make or break anything for you. 45:39.610 --> 45:41.750 What's gonna make or break either option for you 45:41.750 --> 45:44.650 is downstream what it enables you to do 45:44.650 --> 45:46.310 on top of the operating system. 45:46.770 --> 45:49.890 From that perspective, it really comes down to the individual. 45:50.670 --> 45:52.350 I just caught myself rambling about, 45:52.710 --> 45:53.490 I don't even know what. 45:53.770 --> 45:54.850 Like, why did I start rambling? 45:55.590 --> 45:57.190 Oh, you're reseeding your CPU. 45:57.730 --> 45:59.050 I'm wishing you very much luck 45:59.050 --> 46:01.750 in that your system is not a Skylake X system. 46:05.770 --> 46:07.350 Mayonnaise, I'm thinking about making 46:07.350 --> 46:08.970 the full switch over to Proton today. 46:09.050 --> 46:10.230 I haven't watched your video yet, 46:10.230 --> 46:11.670 but do you have any suggestions 46:11.670 --> 46:13.310 of an order to work in when starting? 46:13.870 --> 46:14.450 You don't have to, 46:14.550 --> 46:16.990 so you say full switch over to Proton today. 46:17.790 --> 46:19.270 The first thing I would say 46:19.270 --> 46:21.550 is that these things can be a transition. 46:21.830 --> 46:23.730 I know, like, I'm this way too. 46:24.230 --> 46:25.610 I want, when I'm done with something, 46:25.750 --> 46:27.590 I want to just delete it and have it out of my life 46:27.590 --> 46:28.510 and it's out of my bandwidth 46:28.510 --> 46:30.110 and it's not taking up that mental space. 46:30.390 --> 46:31.750 And I just want to be done, right? 46:32.430 --> 46:34.350 But I think big transitions, right? 46:34.450 --> 46:35.490 Like Proton's a suite, 46:35.630 --> 46:37.670 which means you might be coming from another suite 46:37.670 --> 46:39.350 and suites aren't just one tool. 46:39.350 --> 46:40.310 It's email. 46:40.710 --> 46:41.470 It's drive storage. 46:41.710 --> 46:42.130 It's photos. 46:42.650 --> 46:43.550 It's calendars. 46:43.870 --> 46:45.650 There are so many things 46:45.650 --> 46:47.390 that could go wrong in the transition. 46:47.770 --> 46:49.570 So I don't know where you're at. 46:49.630 --> 46:50.710 You didn't tell me where you're at 46:50.710 --> 46:52.470 or what full switch means to you. 46:52.690 --> 46:54.510 But Proton just released a new feature 46:54.510 --> 46:56.590 even where you can link a Google account 46:56.590 --> 46:57.970 into Proton. 46:58.350 --> 46:59.950 So you can literally use Proton 46:59.950 --> 47:01.430 as your centralized email client. 47:01.590 --> 47:03.310 And you can have a Proton email there 47:03.310 --> 47:05.510 as well as a Gmail email there. 47:05.670 --> 47:06.810 And that's not going to cost you 47:06.810 --> 47:07.770 any more privacy, right? 47:08.310 --> 47:09.590 If you trust Proton, 47:09.630 --> 47:10.850 they're not going to do anything nefarious 47:10.850 --> 47:11.770 with your emails there. 47:12.410 --> 47:14.210 If anything, there might be some privacy benefits 47:14.210 --> 47:15.730 because you're not using the Gmail client, 47:15.930 --> 47:17.410 which might have some of its own tracking 47:17.410 --> 47:18.130 built into it. 47:18.450 --> 47:20.970 So do your best to do the transition 47:20.970 --> 47:22.810 and slowly phase things out. 47:23.330 --> 47:25.210 You know, move one service over, 47:25.910 --> 47:27.350 then start using that service. 47:27.490 --> 47:28.630 You might find a week later 47:28.630 --> 47:30.490 that this one thing didn't transfer properly. 47:30.730 --> 47:32.430 And then when you actually have full confidence, 47:32.710 --> 47:34.510 then delete the data from the old service 47:34.510 --> 47:35.890 and then you're done with that service. 47:35.890 --> 47:37.250 And then over time, 47:37.470 --> 47:38.870 you can finally click that delete button. 47:39.170 --> 47:40.230 Again, I don't know where you're at. 47:40.470 --> 47:42.310 So I'm just making a lot of assumptions here. 47:43.250 --> 47:45.150 But it's something that I know I fall into 47:45.150 --> 47:46.490 in terms of traps. 47:48.990 --> 47:49.770 Let's see. 47:53.950 --> 47:56.050 Steve, tip, have a separate profile 47:56.050 --> 47:57.690 on your phone for finance apps. 47:57.830 --> 47:58.690 Don't use it outdoors. 47:58.890 --> 48:00.350 If your phone is snatched from your hand 48:00.350 --> 48:01.310 because of your carelessness, 48:01.490 --> 48:02.890 at least the thief cannot see or access 48:02.890 --> 48:03.590 your finance apps. 48:03.650 --> 48:04.090 Yeah, it's true. 48:04.550 --> 48:05.730 Yeah, it's a very good tip. 48:05.730 --> 48:06.670 So thanks for sharing, Steve. 48:08.170 --> 48:08.770 Let's see. 48:12.070 --> 48:12.970 Cloud storage provider. 48:13.270 --> 48:16.050 Again, infomaniac suite claims to be 150 Euro for 50 gigabytes 48:16.050 --> 48:17.230 along with the rest of the suite. 48:17.350 --> 48:18.930 Like I said above, seems too good to be true. 48:19.750 --> 48:20.650 Yeah, it might be. 48:20.770 --> 48:21.930 Again, I don't have experience with it. 48:24.310 --> 48:25.150 Question for Henry. 48:25.330 --> 48:26.770 Going cognitive course is five years old. 48:26.830 --> 48:27.390 If you have the time, 48:27.490 --> 48:28.970 is there anything you would update? 48:29.410 --> 48:31.450 Yeah, well, it's already recorded, the update. 48:32.090 --> 48:32.990 It was like a nine hour, 48:33.530 --> 48:34.850 it's like nine hours total of footage. 48:35.730 --> 48:37.090 And we're in the middle of cutting it up. 48:37.170 --> 48:38.330 We already have beta testers 48:38.330 --> 48:40.550 and we have a completed lesson for the most part 48:41.130 --> 48:42.910 as kind of like our template lesson. 48:43.370 --> 48:44.870 So if you're one of those beta testers, 48:44.910 --> 48:45.510 you know who you are. 48:46.350 --> 48:48.270 And the site is done. 48:49.370 --> 48:50.290 We're going to do the transition 48:50.290 --> 48:52.650 from the old teachable users to the new site 48:52.650 --> 48:53.850 for the first version. 48:53.930 --> 48:55.590 So that way they're on the new site. 48:56.310 --> 48:57.910 So we're literally in the middle 48:57.910 --> 48:58.950 of just editing the new one. 48:59.050 --> 49:00.150 And there are a lot of updates. 49:00.370 --> 49:03.630 Like there's a lot of things that have changed 49:03.630 --> 49:04.350 in five years. 49:04.350 --> 49:06.390 I'd say the fundamentals are still there, right? 49:07.490 --> 49:09.150 But especially the tool recommendations 49:09.150 --> 49:10.090 have changed a lot. 49:10.250 --> 49:12.730 Like there wasn't even aliasing five years ago, right? 49:12.850 --> 49:13.710 Like simple login. 49:14.270 --> 49:15.590 I mean, all those tools weren't a thing. 49:15.990 --> 49:17.230 It's kind of crazy to think about that. 49:19.130 --> 49:21.730 So yeah, it's going to be really good guys. 49:21.870 --> 49:23.110 Like I'm really hyped for it. 49:23.830 --> 49:25.670 And it's going to be a lot more thorough 49:25.670 --> 49:26.590 than the first one too, 49:26.690 --> 49:28.670 while still being accessible and easy to take. 49:28.950 --> 49:30.330 And there's still going to be the free version. 49:30.790 --> 49:32.870 But we're probably going to open up pre-orders 49:32.870 --> 49:33.990 for it pretty soon here 49:33.990 --> 49:36.370 because we're already kind of coming up 49:36.370 --> 49:37.850 on maybe finishing our first section. 49:39.030 --> 49:40.990 So yeah, it's an exciting time. 49:41.150 --> 49:42.770 That's what we've been putting a lot of our time 49:42.770 --> 49:43.770 into the last few weeks. 49:44.050 --> 49:44.610 So it's pretty good. 49:46.530 --> 49:47.410 Let's see. 49:49.230 --> 49:49.670 Hello. 49:50.010 --> 49:50.750 Thanks for all the content. 49:50.950 --> 49:51.250 Of course. 49:51.350 --> 49:52.150 Thanks for tuning in. 49:52.530 --> 49:55.610 Massive Holes Plat, 8539. 49:56.230 --> 49:57.210 Have you ever used EOS? 49:57.490 --> 49:57.710 I have. 49:57.830 --> 49:59.790 I actually have a review of EOS. 50:00.030 --> 50:01.190 It's very outdated, right? 50:01.310 --> 50:02.010 It's changed a lot. 50:02.070 --> 50:02.890 And I think I'd be maybe 50:02.890 --> 50:05.050 a little bit less critical of it now in 2026. 50:07.150 --> 50:08.990 I'm still not a fan of it. 50:09.210 --> 50:10.970 Not like I'd say don't use it. 50:11.650 --> 50:14.010 It's just for me, when I'm using Android, 50:14.050 --> 50:15.190 I don't want it to be like EOS. 50:15.430 --> 50:18.730 And I just don't really like the EOS-esque-ness of EOS. 50:20.150 --> 50:22.870 So yeah, that's just my feelings towards it. 50:22.910 --> 50:23.930 Again, very personal preference. 50:24.090 --> 50:25.830 I know a lot of you guys use EOS 50:25.830 --> 50:26.790 and you guys really like it. 50:26.950 --> 50:28.970 So it seems like a great project. 50:36.260 --> 50:37.360 It's just as well. 50:37.680 --> 50:39.940 You didn't have self-oxidizing raptor. 50:40.100 --> 50:40.360 Funny. 50:44.880 --> 50:46.720 Fortunately, I can watch the stream on a tablet, 50:46.860 --> 50:48.400 not missing it for the CPU BS. 50:48.620 --> 50:49.140 Thanks for the luck. 50:49.260 --> 50:49.540 Of course. 50:49.760 --> 50:49.920 Of course. 50:51.240 --> 50:53.500 Why don't you recommend YouTube Revansit? 50:53.580 --> 50:55.020 It is the most convenient YouTube alternative. 50:55.300 --> 50:57.340 It blocks ads, OLED dark mode sponsor block, 50:57.420 --> 50:58.520 and it just feels like the original YouTube 50:58.520 --> 50:59.050 without the bloat. 51:00.060 --> 51:00.620 Use it. 51:01.740 --> 51:03.760 I don't like not recommend YouTube Revansit. 51:03.820 --> 51:04.800 I know a lot of you guys use it. 51:04.800 --> 51:06.440 So yeah, please do. 51:07.760 --> 51:11.580 I will say sponsor block does piss me off a little bit. 51:11.820 --> 51:13.580 Like I get why people use it, 51:13.620 --> 51:16.880 but I do feel like it pushes the boundaries, man. 51:17.220 --> 51:19.400 Because I'm already pro ad blocking. 51:19.860 --> 51:19.880 Right? 51:20.200 --> 51:23.000 I think there is no way that I can, 51:23.560 --> 51:26.120 in good faith, run a channel that talks 51:26.120 --> 51:28.020 about the topics we discuss and say, 51:28.080 --> 51:30.300 yeah, but guys, you should keep your ads on. 51:30.740 --> 51:32.720 The whole industry that's behind 51:32.720 --> 51:35.860 over half of the real privacy invasion happening 51:35.860 --> 51:37.660 and also security issues that are behind it. 51:37.720 --> 51:40.220 So I can't, in good faith, say you don't use an ad blocker, 51:40.440 --> 51:44.240 even though like 75% of our views are non monetized, 51:44.540 --> 51:46.580 which means that a huge majority of our audience 51:46.580 --> 51:49.000 is using an ad blocker and we're not getting money for it. 51:49.300 --> 51:51.200 But sponsor block really pisses me off actually, 51:51.380 --> 51:53.220 especially because we time stamp things like, 51:53.580 --> 51:56.060 you know, we time stamp like every sponsor segment. 51:56.180 --> 51:57.300 So it's really easy to skip. 51:59.300 --> 52:01.660 And I feel like at that point it's like, hey, 52:01.660 --> 52:03.040 like you just don't value the creator. 52:03.320 --> 52:04.560 It's how it feels to me. 52:04.940 --> 52:07.380 I'm not saying that's necessarily how you feel about it. 52:07.420 --> 52:09.140 But as a creator, it feels like, okay, 52:09.200 --> 52:10.200 if you're blocking my ads, 52:10.280 --> 52:11.680 if you're blocking the sponsor segment, 52:12.400 --> 52:16.060 then it just, it feels like it just sucks, man. 52:16.140 --> 52:17.260 Because like it takes a lot of time. 52:17.360 --> 52:20.120 These videos can take like 10, 20, 30 hours 52:20.120 --> 52:21.280 to put together. 52:21.480 --> 52:22.660 And obviously it's not free. 52:22.960 --> 52:24.660 And the only way we can do this for a living 52:24.660 --> 52:26.380 and not dedicate ourselves to other things 52:26.380 --> 52:27.720 is because of revenue models. 52:28.040 --> 52:31.460 So yeah, all I'll say, if you do use these tools, 52:31.460 --> 52:34.620 try to support the creators however they're doing it. 52:34.760 --> 52:39.080 So if you are using sponsor block on like all things secured 52:39.080 --> 52:40.740 or the hated one or whoever, 52:41.720 --> 52:45.280 find a way to support them individually separate from that. 52:46.360 --> 52:48.900 So that way you can still get the best of all worlds. 52:50.660 --> 52:50.880 Yeah. 52:51.340 --> 52:53.340 And I mean, don't disrespect again to the project. 52:53.460 --> 52:54.920 I know that the person who runs the project 52:54.920 --> 52:57.100 knows of our content because they tweeted at us once 52:57.100 --> 53:00.620 because I forgot to time stamp a sponsor segment once. 53:00.620 --> 53:02.500 Like literally it was like on a surveillance report. 53:02.640 --> 53:04.020 I think I forgot to time stamp a segment. 53:04.220 --> 53:07.580 And then the sponsor block Twitter account 53:07.580 --> 53:10.080 added the Techlor Twitter account and said, 53:10.140 --> 53:11.480 why did you not timestamp this? 53:11.540 --> 53:13.300 It's like, oh my God, I literally just forgot. 53:14.620 --> 53:16.700 So I think they might be familiar with our stuff. 53:17.580 --> 53:17.980 Yeah. 53:18.940 --> 53:19.540 Let's see. 53:19.700 --> 53:20.140 Why reasoning? 53:20.680 --> 53:21.740 Why receding a CPU? 53:24.820 --> 53:25.220 Yeah. 53:25.380 --> 53:26.860 Good call to keep paying for a domain. 53:27.240 --> 53:27.380 Yeah. 53:27.600 --> 53:28.440 It's a good point. 53:29.000 --> 53:31.280 Another place, just a tip when you're transitioning, 53:31.600 --> 53:32.760 I think they're referring to the transition 53:32.760 --> 53:34.180 to like a new email provider. 53:35.020 --> 53:37.380 When you change phone numbers, 53:37.640 --> 53:41.000 I do always like say, if you're not 100% ready, 53:41.460 --> 53:44.140 you can port your phone number to something like Google Voice. 53:44.280 --> 53:44.800 I know it's Google. 53:45.080 --> 53:46.340 You can port it to something else. 53:47.540 --> 53:50.000 But that way the number still exists somewhere 53:50.000 --> 53:52.580 and you still have it parked somewhere 53:52.580 --> 53:53.840 if you really need access to it 53:53.840 --> 53:55.400 and it'll still receive messages. 53:55.400 --> 53:58.700 So don't forget, you can like port things to other places 53:58.700 --> 54:00.740 to kind of just buy yourself some time 54:00.740 --> 54:02.920 to make sure that the transition was actually successful 54:02.920 --> 54:04.460 when you're moving between providers. 54:06.180 --> 54:07.520 If you need any more beta testers, 54:07.520 --> 54:08.140 I'd love to sign up. 54:08.200 --> 54:08.800 Yes, send me an email. 54:09.020 --> 54:10.900 If you guys want to be a beta tester for going Cognito, 54:11.080 --> 54:12.320 I'm trying to keep it very low key. 54:13.200 --> 54:15.040 You know, I'm giving free access to the course, 54:15.080 --> 54:16.560 which is like the least I could do 54:16.560 --> 54:17.920 for you guys taking a look at it. 54:18.060 --> 54:22.580 But like the first three people who email us meet, 54:22.580 --> 54:25.300 email me, Henry, Henry at techlar.tech. 54:25.820 --> 54:26.940 First three people, 54:27.180 --> 54:28.740 I'll get you added to that signal group, 54:29.000 --> 54:30.380 but that's it. 54:30.540 --> 54:31.440 I won't do more than three. 54:31.560 --> 54:32.580 I already only let, I think, 54:32.620 --> 54:34.880 like five or six people in from our techlorians. 54:35.000 --> 54:37.560 So I gave kind of like a techlorian beta access to those. 54:38.820 --> 54:39.600 Thanks for the answer. 54:39.760 --> 54:41.000 I appreciate it, of course, of course. 54:41.160 --> 54:42.100 Did you mention in the video 54:42.100 --> 54:44.600 that what Google's up to doing with app installations, 54:44.840 --> 54:46.320 Google's not allowing any apps to be installed 54:46.320 --> 54:47.480 without being signed by them 54:47.480 --> 54:49.060 or a hard way for a usual user to get around? 54:49.160 --> 54:50.640 Yeah, we've been doing a lot of coverage for that. 54:50.640 --> 54:52.660 Like we have been really promoting the hell 54:52.660 --> 54:53.640 out of keep Android open. 54:54.420 --> 54:56.180 And we even signed the open letter. 54:56.400 --> 54:57.440 Like we're listed on their site 54:57.440 --> 54:58.420 as like some of their sources. 54:58.760 --> 55:00.440 So I'm keeping track of it. 55:00.560 --> 55:02.460 In fact, the people who run keep Android open 55:02.460 --> 55:04.920 like literally send me emails when they get updates. 55:05.140 --> 55:06.600 So I'm very much kept in the loop 55:06.600 --> 55:07.500 on what's happening there. 55:07.920 --> 55:09.160 And if there's something that I miss 55:09.160 --> 55:09.800 and you're like, Henry, 55:09.880 --> 55:10.580 why didn't you talk about this? 55:10.620 --> 55:11.320 Then maybe I missed it. 55:11.440 --> 55:13.460 So let me know and then I can try to cover it. 55:20.110 --> 55:21.570 Multiple YouTube creators I follow here 55:21.570 --> 55:22.930 have been experiencing horrible decreases 55:22.930 --> 55:23.690 in user revenue. 55:23.990 --> 55:24.930 Is that affecting you? 55:25.650 --> 55:26.070 Yeah. 55:26.330 --> 55:27.970 I mean, revenue definitely has gone down 55:27.970 --> 55:29.090 on the YouTube end of things. 55:29.290 --> 55:31.410 Like our ad revenue has been a lot lower 55:31.410 --> 55:33.030 the last few months, I would say. 55:33.770 --> 55:35.950 And like the first few months of this year 55:35.950 --> 55:37.370 we saw a huge spike. 55:37.830 --> 55:39.630 So it feels especially aggressive 55:39.630 --> 55:40.750 because we went like, 55:40.950 --> 55:42.210 we had kind of our average 55:42.210 --> 55:44.010 and then our ad revenue went like this. 55:44.210 --> 55:45.630 And now it like came down 55:45.630 --> 55:47.570 like really hard the last few months. 55:48.970 --> 55:51.610 So again, that's why we have other revenue models. 55:51.690 --> 55:52.570 That's why we have techlorians. 55:52.690 --> 55:53.750 That's why we have affiliate links 55:53.750 --> 55:54.870 that are always opt-in. 55:55.530 --> 55:56.510 That's why we have sponsors. 55:56.930 --> 55:58.690 Like that's how we can still keep doing this. 55:58.970 --> 56:01.610 And I don't feel like I can say no to a sponsor. 56:01.790 --> 56:04.570 I can say no to like paywalling content, 56:04.770 --> 56:06.090 which I know is a common thing. 56:06.830 --> 56:08.110 So like it's cool. 56:08.350 --> 56:10.650 I like the diversification that we've accomplished. 56:10.870 --> 56:11.970 But yeah, it is always hard 56:11.970 --> 56:13.330 when the YouTube ad revenue drops 56:13.330 --> 56:15.830 because when it does well, 56:15.910 --> 56:16.990 it's actually a huge help for us 56:16.990 --> 56:17.790 when it doesn't do well. 56:17.830 --> 56:18.890 Then it's like, man, that would be, 56:19.030 --> 56:20.490 I think it's like the easiest thing 56:20.490 --> 56:22.730 to like influence if you get like a really 56:22.730 --> 56:23.910 good video out. 56:24.210 --> 56:26.030 But if you're just dependent on ad revenue, 56:26.210 --> 56:27.710 then you're only incentivized 56:27.710 --> 56:30.730 to make like crazy viral videos 56:30.730 --> 56:32.910 that like are going to get the most attention. 56:33.510 --> 56:36.970 I think that's like why it's hard to, 56:38.290 --> 56:40.390 it's hard to only have one revenue source 56:40.390 --> 56:41.510 because then you're incentivized 56:41.510 --> 56:42.330 by that revenue source. 56:42.450 --> 56:44.050 That's always what I try to come back to 56:44.550 --> 56:44.990 back here. 56:45.030 --> 56:46.390 And it's how I try to run the channel 56:46.390 --> 56:47.710 in a way that I think is fair 56:47.710 --> 56:49.590 to what I want it to look like. 56:53.390 --> 56:55.090 Does YouTube premium light actually result 56:55.090 --> 56:56.230 in creators getting a good cut? 56:56.550 --> 56:57.630 I've heard that it does, 56:58.030 --> 56:59.230 but I'm not YouTube. 56:59.550 --> 57:00.550 And I don't know much about YouTube 57:00.550 --> 57:01.230 premium light. 57:01.510 --> 57:02.130 That's a new thing. 57:02.230 --> 57:03.150 So I don't know. 57:09.340 --> 57:09.920 Oh, I see. 57:10.080 --> 57:11.040 I could go voice is not available 57:11.040 --> 57:11.340 in Germany. 57:11.340 --> 57:11.960 That's a bummer. 57:13.860 --> 57:15.180 Yeah, I feel like in the US too, 57:15.260 --> 57:16.860 most people take the number with them. 57:17.160 --> 57:18.700 That's a very normal thing to do. 57:18.800 --> 57:20.240 Like normally you port to the new provider. 57:20.880 --> 57:22.680 But because we have VoIP services 57:22.680 --> 57:24.160 that are a lot more common here, 57:24.200 --> 57:25.340 I think it's a little more common 57:25.340 --> 57:26.800 to use something like Google Voice as well. 57:28.260 --> 57:29.820 If I were to email you about beta testing, 57:30.000 --> 57:31.240 going cognitive, I mean, I was ready to 57:31.240 --> 57:32.540 choose a new email provider. 57:32.920 --> 57:33.180 That's funny. 57:33.580 --> 57:33.760 Yeah. 57:34.140 --> 57:35.200 Hey, you could set up. 57:35.380 --> 57:37.440 And this is another pro tip. 57:37.680 --> 57:39.160 If you don't have a custom domain or 57:39.160 --> 57:41.600 something set up simple login, 57:42.280 --> 57:43.320 use simple login, 57:43.560 --> 57:44.920 and then you can change behind the 57:44.920 --> 57:46.480 scenes, the email that it gets 57:46.480 --> 57:47.160 forwarded to. 57:47.400 --> 57:48.760 That's like another huge benefit 57:48.760 --> 57:49.900 when you're using simple login, 57:50.060 --> 57:51.160 when you're using ad EIO. 57:52.100 --> 57:53.820 Let's say you generate 10 emails on 57:53.820 --> 57:54.660 10 different accounts. 57:55.160 --> 57:56.720 It doesn't matter if you change 57:56.720 --> 57:57.860 your email provider behind the 57:57.860 --> 57:59.340 scenes, the 10 emails on those 57:59.340 --> 58:00.940 accounts always stay the same. 58:01.240 --> 58:02.260 If you get a new email provider, 58:02.440 --> 58:04.340 you just point simple login or 58:04.340 --> 58:05.720 ad EIO at the new email provider. 58:06.040 --> 58:07.760 So if you're not using aliasing 58:07.760 --> 58:08.860 services, just reach out with an 58:08.860 --> 58:09.480 alias to me. 58:09.640 --> 58:10.980 And then it doesn't matter if you 58:10.980 --> 58:12.280 do a transition in a week. 58:12.620 --> 58:13.280 Like I won't know. 58:13.400 --> 58:14.280 I'm still going to email the same 58:14.280 --> 58:14.540 email. 58:14.700 --> 58:15.320 It's just going to go to a 58:15.320 --> 58:15.900 different inbox. 58:19.220 --> 58:20.460 What's your favorite secondary 58:20.460 --> 58:21.640 phone number provider to sign 58:21.640 --> 58:22.160 up for sites? 58:22.280 --> 58:23.480 VoIP are sometimes blocked. 58:23.680 --> 58:24.400 Lately it's Cape. 58:24.800 --> 58:26.180 I migrated to Cape Cellular 58:26.180 --> 58:27.220 like a few weeks ago. 58:27.220 --> 58:28.840 And they have a secondary numbers 58:28.840 --> 58:29.200 feature. 58:29.780 --> 58:31.060 And I think 58:32.080 --> 58:34.260 someone I know tried signing up 58:34.260 --> 58:36.000 for a Facebook account with the 58:36.000 --> 58:37.160 secondary numbers feature and 58:37.160 --> 58:38.260 that wasn't approved. 58:38.540 --> 58:40.500 But I have been able to access 58:40.500 --> 58:42.500 like so many services that were 58:42.500 --> 58:43.660 blocked with my other VoIP 58:43.660 --> 58:45.300 provider with Cape's secondary 58:45.300 --> 58:45.740 numbers. 58:46.380 --> 58:47.960 And I did the full switch. 58:48.120 --> 58:49.740 So now I'm using only Cape. 58:49.920 --> 58:51.620 So I have like my regular Cape 58:51.620 --> 58:52.840 SIM number and I have the two 58:52.840 --> 58:53.600 secondary numbers. 58:53.960 --> 58:55.100 The first secondary number I'm 58:55.100 --> 58:56.980 using for accounts and like 58:57.500 --> 58:58.600 OTPs and stuff like that. 58:58.780 --> 59:00.140 And then the second Cape number 59:00.140 --> 59:01.380 I'm using is just my spam. 59:01.660 --> 59:02.520 Like I can give this out to 59:02.520 --> 59:04.480 anybody number and that way it's 59:04.480 --> 59:05.680 like part of the same cell plan 59:05.680 --> 59:06.840 and it's all I'm paying for. 59:07.060 --> 59:08.580 So I think I'm going to make a 59:08.580 --> 59:09.960 full Cape review soon because I've 59:09.960 --> 59:11.480 been pretty impressed with the 59:11.480 --> 59:12.520 user experience and it's 59:12.520 --> 59:13.620 really enabled a lot of cool 59:13.620 --> 59:16.040 workflows that are pretty 59:16.040 --> 59:16.300 nice. 59:18.700 --> 59:20.300 I do have an idea about a 59:20.300 --> 59:21.340 peer recommendation model using 59:21.340 --> 59:22.180 social recommendations. 59:22.480 --> 59:23.300 Still trying to figure that out. 59:23.420 --> 59:24.400 It's an interesting concept. 59:24.640 --> 59:24.720 Yeah. 59:24.720 --> 59:26.940 PeerTube I think kind of does this 59:26.940 --> 59:27.640 if I'm not mistaken. 59:28.100 --> 59:28.700 Like you should look at how 59:28.700 --> 59:29.880 PeerTube does recommendations 59:29.880 --> 59:31.840 because we're on PeerTube. 59:32.120 --> 59:33.780 You guys I should have 59:33.780 --> 59:34.280 mentioned that. 59:34.440 --> 59:35.920 Everyone who's like watching 59:35.920 --> 59:37.140 your content using YouTube 59:37.140 --> 59:38.500 revancid and whatnot. 59:39.180 --> 59:40.860 Don't do that for us. 59:41.820 --> 59:43.220 Not because there's 59:43.220 --> 59:44.180 nothing wrong with it, 59:44.220 --> 59:45.560 but because we literally host 59:45.560 --> 59:47.300 a PeerTube server which is 59:47.300 --> 59:49.660 just ad free out of the box. 59:49.740 --> 59:50.560 And it's a lot more privacy 59:50.560 --> 59:53.360 respecting than going 59:53.360 --> 59:54.640 through Google in any capacity. 59:55.300 --> 59:56.980 So check us out on PeerTube 59:56.980 --> 59:57.980 techlor.tv. 59:58.920 --> 01:00:00.000 That's always the better way 01:00:00.000 --> 01:00:00.280 to go. 01:00:00.360 --> 01:00:01.740 If you can push some of your 01:00:01.740 --> 01:00:03.200 creators simply onto better 01:00:03.200 --> 01:00:04.240 platforms then you don't have 01:00:04.240 --> 01:00:05.480 to use tools like YouTube 01:00:05.480 --> 01:00:06.520 revanced or 01:00:07.380 --> 01:00:08.600 Grey J and stuff like that. 01:00:09.420 --> 01:00:10.240 So again nothing wrong with 01:00:10.240 --> 01:00:11.940 the tools but I think the 01:00:11.940 --> 01:00:13.020 best case scenario is to just 01:00:13.020 --> 01:00:14.200 get people in better platforms. 01:00:15.460 --> 01:00:16.180 So yeah. 01:00:20.280 --> 01:00:20.940 Brilliant tip. 01:00:21.040 --> 01:00:21.440 Simple login. 01:00:21.580 --> 01:00:22.200 I'll do that this evening. 01:00:22.200 --> 01:00:23.500 Yeah. Yeah. It's it's a nice 01:00:23.500 --> 01:00:24.700 like side effect of using 01:00:24.700 --> 01:00:25.560 aliasing services. 01:00:27.900 --> 01:00:28.660 All right guys. 01:00:29.020 --> 01:00:31.620 I'm gonna give this a five 01:00:31.620 --> 01:00:33.540 minutes cutoff. 01:00:33.780 --> 01:00:34.420 Five more minutes. 01:00:34.780 --> 01:00:35.820 I just hit an hour. 01:00:36.220 --> 01:00:37.840 So let's do five more minutes. 01:00:38.220 --> 01:00:39.080 So why don't you guys 01:00:39.080 --> 01:00:40.100 leave your final questions. 01:00:40.420 --> 01:00:41.560 Any wins that you had in the 01:00:41.560 --> 01:00:42.640 last week you want to share 01:00:43.200 --> 01:00:44.260 or anything else. 01:00:44.440 --> 01:00:45.680 Signal group, same thing. 01:00:46.420 --> 01:00:48.140 Go for your last calls. 01:00:48.600 --> 01:00:49.740 Five minutes, last calls. 01:00:51.120 --> 01:00:52.680 And while you guys kind of get 01:00:52.680 --> 01:00:55.000 those in if you can support 01:00:55.000 --> 01:00:55.840 us definitely do. 01:00:56.020 --> 01:00:57.280 Otherwise just you being here 01:00:57.280 --> 01:00:58.920 is amazing and having people 01:00:58.920 --> 01:00:59.860 to do this live stream with 01:00:59.860 --> 01:01:00.500 is a lot of fun. 01:01:00.600 --> 01:01:01.700 And it's again just meant to 01:01:01.700 --> 01:01:03.240 be a place where I can just 01:01:03.240 --> 01:01:05.240 be more candid just be myself 01:01:05.800 --> 01:01:07.480 and just kind of share more 01:01:07.480 --> 01:01:09.620 like thoughts as I go along 01:01:09.620 --> 01:01:10.100 with you all. 01:01:12.040 --> 01:01:13.380 And this is normally done 01:01:13.380 --> 01:01:14.820 Fridays at 10 a.m. 01:01:14.980 --> 01:01:16.200 I think next week I might 01:01:16.200 --> 01:01:16.840 have to move it a little 01:01:16.840 --> 01:01:17.220 earlier. 01:01:17.320 --> 01:01:17.760 I think there's something 01:01:17.760 --> 01:01:19.480 on my calendar next week 01:01:19.480 --> 01:01:20.940 but I normally schedule them 01:01:20.940 --> 01:01:21.700 a day or two in advance. 01:01:21.960 --> 01:01:22.580 So you guys will get notified 01:01:22.580 --> 01:01:23.140 about that. 01:01:23.860 --> 01:01:25.080 And if you become a TechLorean 01:01:25.080 --> 01:01:26.260 in the description you can 01:01:26.260 --> 01:01:27.520 join our private signal group. 01:01:27.640 --> 01:01:28.180 We'll get you in there 01:01:28.180 --> 01:01:28.720 pretty quickly. 01:01:28.880 --> 01:01:30.000 You can also do it via Monero. 01:01:30.260 --> 01:01:31.300 You can literally become 01:01:31.300 --> 01:01:32.400 a TechLorean with Monero 01:01:32.400 --> 01:01:33.460 and we'll comp you for the 01:01:33.460 --> 01:01:33.680 year. 01:01:34.160 --> 01:01:34.920 And then you can just 01:01:34.920 --> 01:01:36.060 renew manually each year. 01:01:36.160 --> 01:01:36.920 Kind of like I think what 01:01:36.920 --> 01:01:37.880 Mulvad does with their 01:01:38.440 --> 01:01:38.840 subscription. 01:01:40.080 --> 01:01:42.240 And then let's see. 01:01:42.940 --> 01:01:43.460 Beyond that. 01:01:45.380 --> 01:01:46.420 Is there anything else I want 01:01:47.020 --> 01:01:47.780 to promote? 01:01:48.780 --> 01:01:49.220 No. 01:01:50.380 --> 01:01:51.480 It's nice to have you all in here. 01:01:52.400 --> 01:01:52.660 Let's see. 01:01:53.960 --> 01:01:55.040 What kinds of use cases 01:01:55.040 --> 01:01:55.900 should someone choose 01:01:55.900 --> 01:01:57.320 cubes versus tails versus 01:01:57.320 --> 01:01:57.680 who next? 01:01:57.840 --> 01:01:58.540 I understand how they're 01:01:58.540 --> 01:01:59.340 different but not super 01:01:59.340 --> 01:02:00.160 clear on when one is 01:02:00.160 --> 01:02:01.180 preferable to another. 01:02:02.140 --> 01:02:02.440 Yeah. 01:02:02.540 --> 01:02:03.020 It's a good question. 01:02:03.580 --> 01:02:05.240 So cubes for me is 01:02:05.240 --> 01:02:06.320 supposed to be. 01:02:06.400 --> 01:02:07.020 It doesn't have to be 01:02:07.020 --> 01:02:08.860 but it's to me aimed 01:02:08.860 --> 01:02:09.740 at being more of like 01:02:09.740 --> 01:02:11.080 a daily driver operating 01:02:11.080 --> 01:02:11.540 system. 01:02:12.400 --> 01:02:13.620 Cubes when you use it 01:02:13.620 --> 01:02:15.160 just makes compartmentalization 01:02:15.160 --> 01:02:17.160 stupid easy kind of 01:02:17.160 --> 01:02:17.940 because I think cubes 01:02:17.940 --> 01:02:18.760 is actually horrible 01:02:18.760 --> 01:02:19.940 from usability perspective. 01:02:20.120 --> 01:02:21.440 I can't stand using cubes 01:02:21.960 --> 01:02:23.840 but it makes compartmentalization 01:02:23.840 --> 01:02:25.360 itself as a concept 01:02:25.360 --> 01:02:26.240 easy to do. 01:02:26.400 --> 01:02:27.360 It lets you have 01:02:27.360 --> 01:02:29.200 as many Firefox browsers 01:02:29.200 --> 01:02:29.780 as you want 01:02:29.780 --> 01:02:30.840 and each of them can tunnel 01:02:30.840 --> 01:02:32.020 through a different VPN 01:02:32.020 --> 01:02:32.540 connection. 01:02:32.860 --> 01:02:33.640 Some of the things you can 01:02:33.640 --> 01:02:34.700 have go through who next 01:02:34.700 --> 01:02:36.080 like cubes is just 01:02:36.080 --> 01:02:37.060 extremely powerful 01:02:37.060 --> 01:02:38.900 and it's a wonderful tool 01:02:38.900 --> 01:02:40.000 at what it does. 01:02:40.620 --> 01:02:41.720 And again though 01:02:41.720 --> 01:02:42.420 it's meant to be 01:02:42.420 --> 01:02:43.340 a permanent home. 01:02:43.360 --> 01:02:44.400 It's where you do 01:02:44.400 --> 01:02:44.900 your stuff. 01:02:44.920 --> 01:02:46.100 It's where you save your data. 01:02:46.730 --> 01:02:47.980 So it's more of a traditional 01:02:48.740 --> 01:02:49.280 Linux. 01:02:49.740 --> 01:02:50.920 It's not technically it's 01:02:50.920 --> 01:02:51.720 like what a zen 01:02:53.920 --> 01:02:54.460 situation 01:02:56.180 --> 01:02:57.260 but yeah 01:02:57.260 --> 01:02:58.620 that's how I would define it. 01:02:58.740 --> 01:02:59.940 Tails is pretty much 01:02:59.940 --> 01:03:01.240 exclusively designed to be used 01:03:01.240 --> 01:03:02.340 on a USB flash drive. 01:03:02.540 --> 01:03:03.060 It's meant to be 01:03:03.060 --> 01:03:04.320 completely ephemeral 01:03:04.970 --> 01:03:06.180 and it's meant to 01:03:06.180 --> 01:03:07.420 just be spun up 01:03:07.420 --> 01:03:09.280 and then you unplug it 01:03:09.280 --> 01:03:09.980 and it's gone. 01:03:10.660 --> 01:03:11.480 Who next does have 01:03:11.480 --> 01:03:12.860 a live OS version as well 01:03:12.860 --> 01:03:13.940 but it's definitely 01:03:13.940 --> 01:03:15.200 more historically used 01:03:15.200 --> 01:03:16.540 like as a virtual machine 01:03:17.600 --> 01:03:18.840 on your device. 01:03:19.300 --> 01:03:20.280 And I think where it's 01:03:20.280 --> 01:03:21.140 actually most powerful 01:03:21.140 --> 01:03:21.820 is when you combine 01:03:21.820 --> 01:03:22.800 who next on cubes. 01:03:22.980 --> 01:03:24.020 So those can be combined 01:03:24.020 --> 01:03:24.660 as tools. 01:03:26.560 --> 01:03:27.440 So yeah 01:03:28.100 --> 01:03:29.240 they're just different tools 01:03:29.240 --> 01:03:30.300 for different people. 01:03:31.120 --> 01:03:31.420 I think 01:03:31.420 --> 01:03:32.740 Tails is just something 01:03:32.740 --> 01:03:33.280 you can always have 01:03:33.280 --> 01:03:33.720 in your backpack 01:03:33.720 --> 01:03:34.780 if you ever need it. 01:03:34.860 --> 01:03:35.460 It's a nice like 01:03:35.460 --> 01:03:36.040 safe place 01:03:36.040 --> 01:03:36.780 that you could boot up 01:03:36.780 --> 01:03:37.920 even on a public computer 01:03:37.920 --> 01:03:38.400 sometimes. 01:03:40.380 --> 01:03:41.620 And otherwise I think 01:03:41.620 --> 01:03:42.320 who next is good 01:03:42.320 --> 01:03:43.420 on any operating system 01:03:43.420 --> 01:03:44.080 if you just want 01:03:44.080 --> 01:03:45.260 like a more safe place. 01:03:45.860 --> 01:03:46.820 And if you want like 01:03:46.820 --> 01:03:47.640 the best scenario 01:03:47.640 --> 01:03:48.580 for who next you can use 01:03:48.580 --> 01:03:49.880 who next on top of cubes. 01:03:51.380 --> 01:03:52.320 Oh no you missed 01:03:52.320 --> 01:03:52.940 the whole stream 01:03:52.940 --> 01:03:54.460 Kredas Kredas. 01:03:54.800 --> 01:03:55.500 Sorry about that. 01:03:55.560 --> 01:03:56.240 You can always rewind. 01:03:56.380 --> 01:03:56.900 These are published 01:03:56.900 --> 01:03:57.560 after the fact. 01:03:57.640 --> 01:03:58.860 And oh my gosh 01:03:58.860 --> 01:03:59.680 that is an announcement 01:03:59.680 --> 01:04:00.880 I think one or two weeks 01:04:00.880 --> 01:04:01.220 ago. 01:04:03.740 --> 01:04:04.640 People were asking 01:04:04.640 --> 01:04:05.820 about getting these streams 01:04:05.820 --> 01:04:07.140 cross posted to peer tube. 01:04:07.480 --> 01:04:08.360 I'm going to have 01:04:08.360 --> 01:04:08.820 an announcement. 01:04:09.000 --> 01:04:09.840 This is more for me 01:04:09.840 --> 01:04:10.580 but it does impact 01:04:10.580 --> 01:04:11.640 you guys because 01:04:12.240 --> 01:04:13.800 we finally enabled 01:04:13.800 --> 01:04:15.080 channel auto sync 01:04:15.080 --> 01:04:15.920 on peer tube. 01:04:16.520 --> 01:04:17.500 Yes I know 01:04:17.500 --> 01:04:18.060 a lot of people 01:04:18.060 --> 01:04:18.880 are going to go Henry 01:04:18.880 --> 01:04:19.820 hasn't that been a feature 01:04:19.820 --> 01:04:20.920 for a long time 01:04:20.920 --> 01:04:21.580 where you can just 01:04:21.580 --> 01:04:22.760 automatically sync videos 01:04:22.760 --> 01:04:23.800 from YouTube to peer tube. 01:04:24.120 --> 01:04:25.540 Yes the feature exists 01:04:25.540 --> 01:04:26.940 but practically speaking 01:04:26.940 --> 01:04:28.480 it is a lot more annoying 01:04:28.480 --> 01:04:29.080 than that right 01:04:29.080 --> 01:04:30.580 because first off 01:04:30.580 --> 01:04:32.100 you can't for the most part 01:04:32.100 --> 01:04:33.320 I mean I guess 01:04:33.320 --> 01:04:34.040 some people are lucky 01:04:34.040 --> 01:04:34.580 and their servers 01:04:34.580 --> 01:04:35.500 haven't been blacklisted 01:04:35.500 --> 01:04:36.680 but day one 01:04:36.680 --> 01:04:37.760 of spinning up this server 01:04:37.760 --> 01:04:38.800 I was never able to do 01:04:38.800 --> 01:04:40.060 a YouTube import natively 01:04:40.060 --> 01:04:40.820 from peer tube 01:04:40.820 --> 01:04:42.160 because YouTube blocks 01:04:42.160 --> 01:04:43.120 you know imports 01:04:43.640 --> 01:04:44.860 and so our server IP 01:04:44.860 --> 01:04:46.180 was blacklisted from day one 01:04:46.180 --> 01:04:47.260 so I was never able to go 01:04:47.260 --> 01:04:47.680 that route. 01:04:47.960 --> 01:04:49.180 So then I set up 01:04:49.180 --> 01:04:50.120 a residential proxy 01:04:50.120 --> 01:04:51.680 but back in the day 01:04:51.680 --> 01:04:52.360 this was like 01:04:52.360 --> 01:04:53.820 even as early as a few months 01:04:53.820 --> 01:04:54.080 ago 01:04:55.300 --> 01:04:56.460 there was no way 01:04:56.460 --> 01:04:57.860 to only set a residential 01:04:57.860 --> 01:04:59.180 proxy for imports 01:04:59.180 --> 01:04:59.880 on YouTube 01:04:59.880 --> 01:05:01.120 so if you set a residential 01:05:01.120 --> 01:05:02.640 proxy in peer tube 01:05:02.640 --> 01:05:04.120 it applied to the whole 01:05:04.920 --> 01:05:06.680 damn peer tube site 01:05:06.680 --> 01:05:07.780 which means that 01:05:07.780 --> 01:05:08.900 all federated traffic 01:05:08.900 --> 01:05:09.880 goes through the residential 01:05:09.880 --> 01:05:10.360 proxy 01:05:10.360 --> 01:05:11.540 which is a huge problem 01:05:11.540 --> 01:05:12.480 because federation 01:05:12.480 --> 01:05:12.900 depends 01:05:12.900 --> 01:05:15.020 on a static IP address 01:05:15.020 --> 01:05:16.400 so I didn't know this 01:05:16.400 --> 01:05:16.800 beforehand 01:05:16.800 --> 01:05:17.960 so I just was like 01:05:17.960 --> 01:05:18.540 okay cool 01:05:18.540 --> 01:05:19.660 imports are working 01:05:19.660 --> 01:05:20.820 so I just set 01:05:20.820 --> 01:05:21.780 the residential proxy 01:05:21.780 --> 01:05:22.980 to the whole instance 01:05:24.340 --> 01:05:25.320 and of course 01:05:25.320 --> 01:05:26.480 you know it used a lot of bandwidth 01:05:26.480 --> 01:05:27.160 because then 01:05:27.160 --> 01:05:27.540 you know 01:05:27.540 --> 01:05:28.220 a lot of bandwidth 01:05:28.220 --> 01:05:29.280 goes through the proxy 01:05:29.280 --> 01:05:30.540 but especially 01:05:31.120 --> 01:05:32.280 the fact that 01:05:32.280 --> 01:05:33.320 federation just broke 01:05:33.320 --> 01:05:34.660 so we lost all our subscribers 01:05:34.660 --> 01:05:35.680 I think I've lost 01:05:35.680 --> 01:05:36.560 my peer tube subscribers 01:05:36.560 --> 01:05:38.060 like 10 different times now 01:05:38.060 --> 01:05:38.820 like I think we've actually 01:05:38.820 --> 01:05:39.360 lost like 01:05:39.360 --> 01:05:40.700 1,000 to 2,000 subscribers 01:05:40.700 --> 01:05:41.840 on our peer tube server 01:05:41.840 --> 01:05:43.020 as a result of me just 01:05:43.020 --> 01:05:44.100 screwing something up 01:05:44.100 --> 01:05:44.720 with federation 01:05:44.720 --> 01:05:45.380 it's like 01:05:45.380 --> 01:05:46.760 really easy to break federation 01:05:46.760 --> 01:05:47.160 apparently 01:05:48.580 --> 01:05:49.540 and then 01:05:50.140 --> 01:05:50.520 you know 01:05:50.520 --> 01:05:51.160 so what I had to do 01:05:51.160 --> 01:05:51.740 is I had to build 01:05:51.740 --> 01:05:53.060 like a proxy server 01:05:53.060 --> 01:05:54.120 so what was happening is 01:05:54.120 --> 01:05:54.820 I would send 01:05:54.820 --> 01:05:55.520 all the traffic 01:05:55.520 --> 01:05:56.260 from our peer tube 01:05:56.260 --> 01:05:57.260 to this proxy server 01:05:57.260 --> 01:05:58.220 and the entire 01:05:58.220 --> 01:05:59.560 point of the server 01:05:59.560 --> 01:06:00.160 is to just 01:06:00.160 --> 01:06:01.160 filter traffic 01:06:01.160 --> 01:06:02.600 so if something is 01:06:02.600 --> 01:06:03.220 YouTube traffic 01:06:03.220 --> 01:06:03.900 it goes through 01:06:03.900 --> 01:06:05.060 its residential proxy 01:06:05.060 --> 01:06:06.020 and if it's not 01:06:06.020 --> 01:06:07.280 YouTube traffic 01:06:07.280 --> 01:06:08.240 it pretty much just sends it 01:06:08.240 --> 01:06:09.200 back to the server 01:06:09.360 --> 01:06:10.320 the peer tube server 01:06:10.320 --> 01:06:11.200 and then sends it out 01:06:11.200 --> 01:06:12.160 through the static IP 01:06:12.160 --> 01:06:13.220 so that way 01:06:13.220 --> 01:06:14.680 it's like a dedicated IP 01:06:14.680 --> 01:06:15.820 that people can always use 01:06:15.820 --> 01:06:17.040 and it doesn't break federation 01:06:17.040 --> 01:06:18.460 but then the YouTube traffic 01:06:18.460 --> 01:06:19.340 does get tunnels 01:06:19.340 --> 01:06:20.480 so I had to recreate that 01:06:20.480 --> 01:06:21.620 thank goodness 01:06:21.620 --> 01:06:22.440 peer tube actually 01:06:22.440 --> 01:06:23.360 released this feature 01:06:23.360 --> 01:06:23.940 natively 01:06:23.940 --> 01:06:25.020 so now you can just 01:06:25.020 --> 01:06:25.540 proxy 01:06:25.540 --> 01:06:26.600 import traffic 01:06:26.600 --> 01:06:27.780 through the residential proxy 01:06:28.680 --> 01:06:30.320 and so I finally migrated 01:06:30.320 --> 01:06:31.640 to their native system 01:06:31.640 --> 01:06:32.260 which has been working 01:06:32.260 --> 01:06:33.620 fabulously for us 01:06:34.180 --> 01:06:35.140 and then you might be 01:06:35.140 --> 01:06:35.440 wondering 01:06:35.440 --> 01:06:36.320 oh Henry 01:06:36.320 --> 01:06:36.800 like 01:06:36.800 --> 01:06:38.100 why didn't you just enable 01:06:38.100 --> 01:06:38.980 channel sync then 01:06:38.980 --> 01:06:40.840 it's because the channel sync function 01:06:42.300 --> 01:06:43.880 actually uses a lot of bandwidth 01:06:44.760 --> 01:06:45.380 for us 01:06:45.380 --> 01:06:46.080 and our channel 01:06:46.080 --> 01:06:47.340 it runs every hour 01:06:47.340 --> 01:06:47.860 by default 01:06:47.860 --> 01:06:49.180 and each hour 01:06:49.180 --> 01:06:50.820 it uses 20 megabytes 01:06:50.820 --> 01:06:51.380 of bandwidth 01:06:51.380 --> 01:06:52.220 just to check 01:06:52.220 --> 01:06:53.160 if there's new videos 01:06:53.160 --> 01:06:54.060 if you do the math 01:06:54.060 --> 01:06:55.340 20 times 24 01:06:55.920 --> 01:06:57.420 like 20 times 24 01:06:57.420 --> 01:06:58.460 that's 480 01:06:58.460 --> 01:06:59.580 times 30 01:06:59.580 --> 01:07:01.900 that's 14.4 gigabytes 01:07:01.900 --> 01:07:03.100 of bandwidth a month 01:07:03.100 --> 01:07:05.220 and the residential proxy services 01:07:05.220 --> 01:07:05.840 aren't cheap 01:07:06.420 --> 01:07:06.820 so 01:07:06.820 --> 01:07:08.500 I finally learned 01:07:08.500 --> 01:07:09.920 recently that you can actually 01:07:09.920 --> 01:07:11.120 set it to auto sync 01:07:11.120 --> 01:07:11.840 every eight hours 01:07:12.440 --> 01:07:13.740 so now it auto sinks 01:07:13.740 --> 01:07:14.480 every eight hours 01:07:14.480 --> 01:07:15.960 so it will only use that 01:07:15.960 --> 01:07:16.920 20 megabytes of bandwidth 01:07:16.920 --> 01:07:17.800 every eight hours 01:07:17.800 --> 01:07:19.260 and it should only import 01:07:20.480 --> 01:07:21.360 the videos 01:07:21.360 --> 01:07:21.980 when needed 01:07:21.980 --> 01:07:22.760 and yes 01:07:22.760 --> 01:07:23.800 I did announce this last week 01:07:23.800 --> 01:07:24.720 but I wanted to just 01:07:24.720 --> 01:07:25.860 announce it again 01:07:25.860 --> 01:07:26.640 because I'm really excited 01:07:26.640 --> 01:07:27.040 about it 01:07:27.040 --> 01:07:27.800 and it's been working 01:07:27.800 --> 01:07:28.560 and you can see 01:07:28.560 --> 01:07:29.780 last week's stream 01:07:29.780 --> 01:07:31.880 did import correctly 01:07:31.880 --> 01:07:32.440 which 01:07:32.440 --> 01:07:33.360 when I announced it 01:07:33.360 --> 01:07:34.600 I didn't know if it would happen 01:07:34.600 --> 01:07:35.480 but now I'm a lot more 01:07:35.480 --> 01:07:36.240 confident enough 01:07:36.240 --> 01:07:37.060 to really expand 01:07:37.060 --> 01:07:38.340 on like the behind the scenes 01:07:38.940 --> 01:07:39.660 and yeah 01:07:39.660 --> 01:07:41.280 running peer trip is a pain in the butt 01:07:41.740 --> 01:07:42.880 and it costs us money 01:07:42.880 --> 01:07:43.800 it costs us time 01:07:45.000 --> 01:07:46.120 it's like one of the things 01:07:46.120 --> 01:07:48.120 that we continually go back here 01:07:48.120 --> 01:07:48.420 and say 01:07:48.420 --> 01:07:48.680 man 01:07:48.680 --> 01:07:50.200 we really want to cut this out 01:07:50.200 --> 01:07:51.700 like it's just a lot of overhead 01:07:52.340 --> 01:07:53.500 it's a lot of cost 01:07:53.500 --> 01:07:54.200 for what it is 01:07:54.200 --> 01:07:55.640 and like look at the views guys 01:07:56.120 --> 01:07:58.700 like we literally get 70 views 01:07:58.700 --> 01:07:59.760 on this interview 01:07:59.760 --> 01:08:01.680 I guess we got over 100 on this one 01:08:01.680 --> 01:08:03.680 the most views I see on a video on this 01:08:03.680 --> 01:08:04.780 is like 300-400 views 01:08:04.780 --> 01:08:06.540 so it's one of those like 01:08:06.540 --> 01:08:07.860 business decisions 01:08:08.400 --> 01:08:10.420 where it doesn't make any sense 01:08:11.700 --> 01:08:14.740 but it's the right thing to do 01:08:14.740 --> 01:08:18.080 like the reason I can tell you guys 01:08:18.080 --> 01:08:19.500 not to use an ad blocker 01:08:19.500 --> 01:08:20.420 and to like 01:08:20.420 --> 01:08:21.560 and the reason I feel comfortable 01:08:21.560 --> 01:08:22.500 posting to YouTube 01:08:22.500 --> 01:08:23.140 and all these things 01:08:23.140 --> 01:08:24.300 is because we have peer tube 01:08:24.300 --> 01:08:25.080 is that safe space 01:08:25.080 --> 01:08:26.140 if you don't have the safe space 01:08:26.700 --> 01:08:27.860 then it's a lot harder 01:08:28.800 --> 01:08:30.440 to like in good faith say 01:08:30.440 --> 01:08:32.320 oh I'm just posting to YouTube 01:08:32.320 --> 01:08:33.060 to reach people 01:08:33.060 --> 01:08:33.700 it's like yeah 01:08:33.700 --> 01:08:34.720 for reaching people 01:08:34.720 --> 01:08:35.900 who are already on YouTube 01:08:36.580 --> 01:08:38.460 but also we can get them on peer tube 01:08:38.460 --> 01:08:39.560 which is a much safer place 01:08:39.560 --> 01:08:41.160 anyway I just wanted to share 01:08:41.160 --> 01:08:41.940 a little bit about peer tube 01:08:41.940 --> 01:08:43.240 because it's a pain in the ass to host 01:08:43.840 --> 01:08:44.820 but it should be working 01:08:44.820 --> 01:08:45.900 and you guys should get these streams 01:08:45.900 --> 01:08:46.880 after the fact 01:08:48.440 --> 01:08:50.560 sorry I just went on a huge tangent there 01:08:50.560 --> 01:08:52.140 but I hope someone found that interesting 01:08:53.180 --> 01:08:53.900 let's see 01:08:56.920 --> 01:08:58.620 earlier stream would be nice for Europe 01:08:58.620 --> 01:09:00.640 next week will be about half an hour earlier 01:09:00.640 --> 01:09:02.380 but yeah it's not going to be that early 01:09:02.380 --> 01:09:03.220 at the time zone 01:09:03.220 --> 01:09:05.300 like pacific time to European 01:09:05.300 --> 01:09:07.820 time zones is just not fantastic 01:09:08.640 --> 01:09:10.040 I have to do a lot of meetings 01:09:10.040 --> 01:09:12.000 in central European time 01:09:12.000 --> 01:09:12.880 I think CET 01:09:13.480 --> 01:09:15.440 and it's always a little bit hard to coordinate 01:09:16.440 --> 01:09:17.680 you ever used Hoonix 01:09:17.680 --> 01:09:19.340 yeah I've used Hoonix in cubes 01:09:19.340 --> 01:09:20.220 and it was 01:09:20.860 --> 01:09:22.180 I don't have a use case for it 01:09:22.180 --> 01:09:22.580 day-to-day 01:09:22.580 --> 01:09:23.720 but it works well 01:09:23.720 --> 01:09:24.680 and I really enjoyed it 01:09:25.280 --> 01:09:26.120 why do you smell that 01:09:26.120 --> 01:09:26.820 instead of obscura 01:09:26.820 --> 01:09:27.980 it's still using more that 01:09:27.980 --> 01:09:28.540 but more anonymous 01:09:28.540 --> 01:09:30.500 I use Moldad instead of obscura 01:09:30.500 --> 01:09:31.740 because I actually use tail skill 01:09:32.180 --> 01:09:33.600 that's really why I use Moldad 01:09:34.100 --> 01:09:36.900 I actually wish that I could change the VPN provider 01:09:38.360 --> 01:09:39.380 as the exit node 01:09:39.380 --> 01:09:41.020 but there is no way to do that 01:09:41.020 --> 01:09:42.380 so for those who don't know 01:09:42.380 --> 01:09:44.240 tail scale is how you can connect to things 01:09:44.240 --> 01:09:46.380 it's more of like a traditional VPN use case 01:09:46.380 --> 01:09:47.400 so like I have my NAS 01:09:47.400 --> 01:09:49.280 I connect to my NAS using tail scale 01:09:49.860 --> 01:09:50.760 and I have some servers 01:09:50.760 --> 01:09:51.600 like the peer tube server 01:09:51.600 --> 01:09:52.440 that I can connect to 01:09:52.440 --> 01:09:53.480 through tail scale 01:09:54.260 --> 01:09:56.580 and tail scale pretty much is a VPN 01:09:56.580 --> 01:09:58.160 and normally it's 01:09:58.160 --> 01:09:59.040 you have to run tail scale 01:09:59.040 --> 01:10:00.300 and then Moldad separately 01:10:00.300 --> 01:10:02.220 so you have to have like two VPN connections running 01:10:02.220 --> 01:10:04.220 but tail scale partnered with Moldad 01:10:04.220 --> 01:10:05.540 so that you can just have Moldad 01:10:05.540 --> 01:10:07.040 built into the same VPN connection 01:10:07.040 --> 01:10:08.580 and use Moldad as an exit node 01:10:09.140 --> 01:10:09.980 so that's what I do 01:10:09.980 --> 01:10:10.820 it's very convenient 01:10:10.820 --> 01:10:12.500 it lets me have just one VPN connection 01:10:12.500 --> 01:10:13.340 across my devices 01:10:14.380 --> 01:10:16.100 and if I could use obscura 01:10:16.100 --> 01:10:16.880 within tail scale 01:10:16.880 --> 01:10:17.480 I would do it 01:10:17.480 --> 01:10:18.500 but it's just 01:10:18.500 --> 01:10:19.500 I don't want to have to run 01:10:19.500 --> 01:10:20.500 two VPN connections 01:10:21.720 --> 01:10:22.560 just to answer 01:10:22.560 --> 01:10:23.920 I got privacy burnout last week 01:10:23.920 --> 01:10:25.500 I was just too tired to be paranoid 01:10:25.500 --> 01:10:27.060 I just like to play my stuff 01:10:27.060 --> 01:10:28.180 without worrying about life too much 01:10:28.180 --> 01:10:29.260 like paying cash everywhere 01:10:29.260 --> 01:10:30.580 yeah again like 01:10:30.580 --> 01:10:32.220 I covered a lot more of my thoughts 01:10:32.220 --> 01:10:32.700 at the beginning 01:10:32.700 --> 01:10:33.520 so I would go there 01:10:33.960 --> 01:10:35.400 if you want to see it 01:10:38.180 --> 01:10:38.840 I'm in burnout 01:10:38.840 --> 01:10:40.640 trying to off-scape baseband signals 01:10:40.640 --> 01:10:42.000 watch a mobile didn't you announce 01:10:42.000 --> 01:10:42.680 yeah I did 01:10:43.080 --> 01:10:43.880 why burnout 01:10:43.880 --> 01:10:44.760 everyone's saying name 01:10:44.760 --> 01:10:45.180 privacy burnout 01:10:45.180 --> 01:10:46.320 why burnout lol 01:10:48.840 --> 01:10:49.240 yeah 01:10:49.240 --> 01:10:50.400 all right 01:10:50.880 --> 01:10:52.720 yeah I don't see much else 01:10:53.580 --> 01:10:54.380 let's see 01:10:54.380 --> 01:10:55.680 yeah nothing on signal 01:10:55.680 --> 01:10:56.260 all right guys 01:10:56.940 --> 01:10:57.640 I'm gonna go ahead 01:10:57.640 --> 01:10:58.600 and start rounding this out 01:10:59.120 --> 01:10:59.840 I want to thank you all 01:10:59.840 --> 01:11:01.060 for being here as always 01:11:01.060 --> 01:11:02.500 it's always a pleasure to be here 01:11:02.500 --> 01:11:03.880 and I 01:11:04.600 --> 01:11:06.040 you know these are just meant to be fun 01:11:06.040 --> 01:11:06.900 they're meant to be casual 01:11:06.900 --> 01:11:07.440 and so 01:11:07.440 --> 01:11:08.620 the fact that there's so many 01:11:08.620 --> 01:11:09.960 familiar faces that come each week 01:11:09.960 --> 01:11:11.580 just makes it a little bit more enjoyable 01:11:12.360 --> 01:11:13.360 it's already enjoyable 01:11:13.360 --> 01:11:14.200 but it's even more enjoyable 01:11:14.200 --> 01:11:14.740 with you guys 01:11:14.740 --> 01:11:15.900 and having familiar faces 01:11:16.480 --> 01:11:18.100 I hope that you are able to 01:11:18.100 --> 01:11:19.060 reset your cpu 01:11:19.060 --> 01:11:19.960 Adam Bean 01:11:22.340 --> 01:11:23.140 and yeah 01:11:23.140 --> 01:11:23.740 again 01:11:23.740 --> 01:11:25.060 Techlorians down in the description 01:11:25.480 --> 01:11:26.220 PeerTube server 01:11:26.220 --> 01:11:27.000 we have our tools 01:11:27.000 --> 01:11:28.360 tools.techlor.tech 01:11:28.360 --> 01:11:29.440 quiz.techlor.tech 01:11:29.440 --> 01:11:31.260 and also VPN.techlor.tech 01:11:31.260 --> 01:11:32.540 which did not come up this week 01:11:32.540 --> 01:11:34.280 anywhere near as much as last week 01:11:34.780 --> 01:11:36.040 but I will see you all 01:11:36.040 --> 01:11:37.160 next Friday 01:11:37.760 --> 01:11:39.760 check to see the exact time 01:11:39.760 --> 01:11:40.780 because I think next Friday 01:11:40.780 --> 01:11:42.040 might have to be a little bit earlier 01:11:42.040 --> 01:11:43.760 which you Europeans might enjoy 01:11:44.660 --> 01:11:45.640 other than that 01:11:46.200 --> 01:11:47.400 thank you all for being here 01:11:47.400 --> 01:11:48.480 and I'll see you guys 01:11:48.480 --> 01:11:50.260 next time on Techlor