Episode 121: Lawful but Awful

1 00:00:00,750 --> 00:00:07,230 podcasting 2.0 February 10 2023 Episode 121 lawful but awful 2 00:00:09,120 --> 00:00:12,420 Hello, everybody once again it's a Friday time for the board 3 00:00:12,420 --> 00:00:15,180 meeting the official one the only board meetings of 4 00:00:15,180 --> 00:00:19,470 podcasting. 2.0 everything happening in podcasting, we are 5 00:00:19,470 --> 00:00:24,000 the first line of defense against big tech capture. We 6 00:00:24,060 --> 00:00:27,840 are, we are slaying it. You can find everything at podcasts 7 00:00:27,840 --> 00:00:30,930 index.org Of course, we got the podcast namespace where all the 8 00:00:30,930 --> 00:00:34,470 innovation is documented and everything happening in podcast 9 00:00:34,470 --> 00:00:37,800 index dot social. I'm Adam curry here in the chilly heart of the 10 00:00:37,800 --> 00:00:42,330 Texas Hill Country and Alabama. He's the big A and API say hello 11 00:00:42,330 --> 00:00:44,790 to my friend on the other end, ladies and gentlemen, it's Mr. 12 00:00:44,790 --> 00:00:46,470 Dave Jones. 13 00:00:47,160 --> 00:00:48,840 Did you call me the big day 14 00:00:48,960 --> 00:00:54,450 in API? Okay. Yeah, not isn't. No, it's meant to be. Come on, 15 00:00:54,450 --> 00:00:58,560 man. I'm just doing this over my head. Yeah, I just, I just throw 16 00:00:58,560 --> 00:01:01,200 it out there. You know, whatever comes to mind, I got to do 17 00:01:01,200 --> 00:01:03,330 something every single week. So I'm drinking 18 00:01:03,330 --> 00:01:05,880 the beef milk. And halfway through the beef milkshakes. I 19 00:01:05,880 --> 00:01:07,050 mean, big A's. 20 00:01:08,760 --> 00:01:13,440 Big is coming. Brother, how are you feeling? By the way? Because 21 00:01:13,440 --> 00:01:15,090 I know you were still a little bit under the weather. 22 00:01:15,720 --> 00:01:18,840 Oh, yeah. This has been a roller coaster I went, I was, you know, 23 00:01:18,840 --> 00:01:22,050 went down, get get the antibiotics and those in the 24 00:01:22,050 --> 00:01:30,630 steroid shot. Came back up was like 100 was like 99%. Then got 25 00:01:30,810 --> 00:01:36,240 them when Rob back down again. Round two. I was so my thought 26 00:01:36,240 --> 00:01:41,850 was okay. I've didn't clear the first thing, whatever this was, 27 00:01:41,850 --> 00:01:45,870 and I've and it's come back. But now I'm thinking because my 28 00:01:46,110 --> 00:01:50,070 thinking that the sequence of events was that I got sick, 29 00:01:50,520 --> 00:01:55,890 Clear that out. And then just the universe hates me. So I just 30 00:01:55,890 --> 00:01:58,950 had a different I guess, I think I got two different things back 31 00:01:58,950 --> 00:01:59,280 to back. 32 00:01:59,310 --> 00:02:03,810 Oh, goodness. I mean, this is Tina had this thing that you 33 00:02:03,810 --> 00:02:07,020 have it was and she was, I'd say it took a good two weeks. And 34 00:02:07,020 --> 00:02:11,610 she and she still? Well, she basically either cracked or 35 00:02:11,640 --> 00:02:15,600 bruised her ribs severely. So she still has Yeah, from the 36 00:02:15,600 --> 00:02:19,470 coughing. And like, I missed her. And she's so healthy 37 00:02:20,130 --> 00:02:23,250 compared to me and works out, you know, twice a day and does 38 00:02:23,280 --> 00:02:26,670 all this stuff. And I just kind of like your podcast, I have 39 00:02:26,670 --> 00:02:33,180 some beef. That's veils regimen, and a Dr. Pepper. And I didn't 40 00:02:33,180 --> 00:02:37,080 get anything. And I know lots of people like this just it's been 41 00:02:37,080 --> 00:02:37,830 bad. 42 00:02:38,220 --> 00:02:44,070 Melissa has a forcefield I mean, she never gets sick. And, and I 43 00:02:44,070 --> 00:02:47,820 mean, like somebody, you know, float by me and I get in looks 44 00:02:47,820 --> 00:02:49,800 at me wrong and I get sick. It's so annoying 45 00:02:49,800 --> 00:02:53,340 socks profit. So you've been working from home? No, you've 46 00:02:53,340 --> 00:02:54,660 been going into the office? 47 00:02:54,810 --> 00:03:00,870 Yes, I did. During the pandemic. We never I didn't miss a day 48 00:03:00,870 --> 00:03:03,660 except for those 11 days. I was locked in the room in my room 49 00:03:03,690 --> 00:03:05,220 with COVID which was 50 00:03:05,220 --> 00:03:09,030 bad. I remember that you were on the ropes. Yeah, we did. When we 51 00:03:09,030 --> 00:03:13,380 still did I still did this show. I remember. That's right, 52 00:03:13,380 --> 00:03:16,770 brother. That's your vow of poverty for the for the further 53 00:03:16,770 --> 00:03:18,030 ment of podcasting. 54 00:03:18,360 --> 00:03:20,940 Yes, crawler across the floor of treasuries to Mike. 55 00:03:22,470 --> 00:03:28,200 Remember this? Oh goodness. So those of you that have it and 56 00:03:28,230 --> 00:03:31,920 know about it, we're lit. That means that we are live on the 57 00:03:31,920 --> 00:03:38,580 air. It's it's a fantastic new format for podcasting that I'm 58 00:03:38,580 --> 00:03:41,970 very familiar with because I've been doing it for maybe 1314 59 00:03:41,970 --> 00:03:44,430 years, but 15 years have no agenda but it never came 60 00:03:44,430 --> 00:03:48,840 together the way it is in these apps now with chat room with 61 00:03:49,140 --> 00:03:52,830 with live stream and of course the extra bonus of the live 62 00:03:52,830 --> 00:03:58,140 booster Graham's this thing is catching fire and I saw the new 63 00:03:58,140 --> 00:04:02,490 media show Todd and Rob they went live with video, which was 64 00:04:02,490 --> 00:04:07,950 made possible in the new version of pod verse with I think a lot 65 00:04:07,950 --> 00:04:12,900 of background assist from Alex gates, since it was this new 66 00:04:13,470 --> 00:04:18,330 chipped up, choppy LS thingamabob video format HLS 67 00:04:18,330 --> 00:04:23,760 Yes, what I mean HLS which sounds HLS sounds like something 68 00:04:23,820 --> 00:04:28,650 bad that you can get can catch, but like RSV, I got a case of 69 00:04:28,650 --> 00:04:31,410 HLS now stay away from me, bro. 70 00:04:33,360 --> 00:04:36,810 Yeah, that's that I didn't realize that Alex was in on 71 00:04:36,810 --> 00:04:39,180 that. I was kind of like tangential to what was going on? 72 00:04:39,240 --> 00:04:42,720 I think they jump in and whip them into shape. Well, I think 73 00:04:42,720 --> 00:04:50,340 because he's peer tube work has been with with HLS and no agenda 74 00:04:50,340 --> 00:04:54,510 tube, which is you know, the the peer tube instance that he runs, 75 00:04:54,930 --> 00:05:00,210 has this, this HLS capability. So I mean, what can you do? Tell 76 00:05:00,210 --> 00:05:03,960 us, besides the fact that pod verses now come into its own, 77 00:05:04,500 --> 00:05:09,750 into into a mature state of application, I would say, how 78 00:05:09,750 --> 00:05:12,180 does how does this what is this HLS stuff? And why is it 79 00:05:12,180 --> 00:05:14,910 important? And do I need a special special server for it? 80 00:05:15,930 --> 00:05:16,860 How does this work? 81 00:05:17,759 --> 00:05:23,639 I think if I'm not mistaken, I'm not mistaken. Apple had a strong 82 00:05:23,639 --> 00:05:31,229 hand in in HLS. I think, if I'm not mistaken, so think I'm 83 00:05:31,229 --> 00:05:35,159 totally not the expert with with the video streaming formats, but 84 00:05:35,159 --> 00:05:40,529 I think if I understand it correctly, sort of HLS is like 85 00:05:40,829 --> 00:05:44,249 it's an acronym like or something. Yes, right. Yes. HTTP 86 00:05:44,249 --> 00:05:47,369 Live Streaming is that oh, okay. That helps HTTP Live Stream. 87 00:05:47,399 --> 00:05:52,829 Yeah, you like segment you segment the, the stream into 88 00:05:52,979 --> 00:05:56,309 chunks, I guess chunks are something in the new rather than 89 00:05:56,309 --> 00:05:59,789 like trying to stream on an unbroken 90 00:06:01,020 --> 00:06:01,770 rights 91 00:06:02,460 --> 00:06:05,370 as opposed to mp3 streaming, Riah, that kind of thing. So 92 00:06:05,370 --> 00:06:05,640 this is 93 00:06:05,640 --> 00:06:09,060 why it works on on curio caster as well, because that's 94 00:06:09,060 --> 00:06:11,370 basically a web browser and he's wet. The web browsers already 95 00:06:11,370 --> 00:06:13,950 understand this is HLS format. 96 00:06:14,400 --> 00:06:17,550 Well, I think they're using a library. I don't know, I don't 97 00:06:17,550 --> 00:06:19,710 know if the browsers don't understand it natively. But I 98 00:06:19,710 --> 00:06:23,070 think they're, I think they're using a sort of a common library 99 00:06:23,070 --> 00:06:26,940 to do this that understands it. Will. It may Safari, I think may 100 00:06:26,940 --> 00:06:32,130 do it HLS natively. I don't know about Chrome based browsers. 101 00:06:32,220 --> 00:06:34,980 Okay. There's a lot yeah, there's a lot I don't know about 102 00:06:34,980 --> 00:06:40,170 it. But I do know it's way more efficient. You It tolerates it 103 00:06:40,170 --> 00:06:44,130 tolerates poor connections well, and it's just it's the right way 104 00:06:44,130 --> 00:06:45,930 to go. But it's the modern approach. It's 105 00:06:45,930 --> 00:06:52,770 not just video it does mp3 and AC three and all other AAC. So 106 00:06:52,890 --> 00:06:56,820 is this something we should be using in general also for for 107 00:06:56,820 --> 00:06:57,990 audio lit streaming? 108 00:06:59,340 --> 00:07:04,560 I think I think the difference here is, again, with the caveats 109 00:07:04,560 --> 00:07:07,920 of non knowledge of video, I think the difference here is 110 00:07:07,920 --> 00:07:12,690 that something like mp3 streaming is so small already, 111 00:07:12,900 --> 00:07:16,770 like audio only streaming is very, is as already just 112 00:07:16,770 --> 00:07:20,970 efficient by by nature. Whereas something like video streaming 113 00:07:21,000 --> 00:07:24,810 is so heavy, right? You have you really like you can survive with 114 00:07:24,810 --> 00:07:28,530 some made with audio streams that are a little bit fatter 115 00:07:28,530 --> 00:07:31,890 than you can with an with a video stream. That's fat, you 116 00:07:31,890 --> 00:07:37,020 really have to pare that down and make it nice for you know, 117 00:07:37,020 --> 00:07:42,000 latency and things like that. But Nathan G says HLS lets you 118 00:07:42,000 --> 00:07:44,670 skip back to the to catch the start of the Live episode and 119 00:07:44,670 --> 00:07:46,200 even increase the playback speed to catch. 120 00:07:46,560 --> 00:07:48,210 Oh, okay, that's cool. 121 00:07:48,690 --> 00:07:53,370 Yeah, is it? Is it packet based? I'm not real sure. I don't know 122 00:07:53,370 --> 00:07:57,930 how deep in the, in the, in the OSI stack it goes. I don't know 123 00:07:57,930 --> 00:08:01,290 if it goes all the way down to the you know, like so now 124 00:08:01,290 --> 00:08:04,890 when the lower levels now I need to do is also baking web 125 00:08:04,890 --> 00:08:07,590 torrent. And then we don't even need streaming servers. We don't 126 00:08:07,590 --> 00:08:09,420 even need infrastructure just works. 127 00:08:10,200 --> 00:08:12,780 Yeah, it'll it'll only take. It'll be here in two years. 128 00:08:12,780 --> 00:08:12,990 Yeah. 129 00:08:15,330 --> 00:08:18,540 Now that's like, 10 years for anything. Climate change 130 00:08:18,540 --> 00:08:21,150 related? Yep. We'll have how green hydrogen and 10 years. 131 00:08:21,150 --> 00:08:21,690 Okay, great. 132 00:08:21,960 --> 00:08:24,870 Always 10 years? Course five years. And always? 133 00:08:25,050 --> 00:08:27,660 Well, I remember we might have talked about this in a recent 134 00:08:27,660 --> 00:08:32,250 episode, was it BitTorrent live or something? And with a bit bit 135 00:08:32,250 --> 00:08:36,420 torrent before, they, I don't know, somehow they they became a 136 00:08:36,420 --> 00:08:40,080 company and took money, and then it all sucked. But they were 137 00:08:40,080 --> 00:08:43,290 going to do something? Maybe that's what web torrent is, I 138 00:08:43,290 --> 00:08:47,250 don't know. But I've always been very enamored of the idea that 139 00:08:47,250 --> 00:08:50,370 you didn't need a central server for streaming stuff for a number 140 00:08:50,370 --> 00:08:52,740 of reasons. But I always thought that would be cool. If that 141 00:08:52,740 --> 00:08:55,980 actually worked, then I think web torrent does it to some 142 00:08:55,980 --> 00:08:56,610 degree. 143 00:08:57,390 --> 00:09:00,270 It does, except the you know, the, the problem was you always 144 00:09:00,270 --> 00:09:05,370 just, it's hard to get everybody to, to seed and to participate. 145 00:09:05,400 --> 00:09:08,700 Right? It's like it's like you have this I wouldn't I don't 146 00:09:08,700 --> 00:09:11,610 know if I call it a chicken and egg problem but you you have to 147 00:09:11,610 --> 00:09:17,850 have enough is the same it's the same as the DHT DHT bootstrap 148 00:09:17,850 --> 00:09:22,740 problem that you have with DHT based networks once you get to a 149 00:09:22,740 --> 00:09:26,940 critical mass something like IPFS you print it you can you 150 00:09:26,940 --> 00:09:32,370 can ride you're good to go. But then there's that initial thing 151 00:09:32,370 --> 00:09:37,440 of trying to get enough peers online and and bootstrapped 152 00:09:37,470 --> 00:09:41,970 Yeah. To so that you have other people participating. Like and 153 00:09:41,970 --> 00:09:44,280 it seems like every time you would boot up a live stream you 154 00:09:44,280 --> 00:09:47,880 would have to go through that entire process again. You know, 155 00:09:47,880 --> 00:09:50,670 it's like it will it's the way it is with bits with Bit Torrent 156 00:09:50,670 --> 00:09:54,180 to every time you you find something and you start to 157 00:09:54,180 --> 00:09:56,340 download it. It's like okay, went offline. 158 00:09:56,730 --> 00:09:57,810 He went, one guy, 159 00:09:58,080 --> 00:09:59,970 one guy, stay online man, don't 160 00:10:00,000 --> 00:10:07,050 Oh, he went offline. Yeah, yeah, remember that I'm, in a way it's 161 00:10:07,050 --> 00:10:10,020 like nostre, which I've been, I've been, I'm still 162 00:10:10,020 --> 00:10:16,170 experimenting with. And it's, you're so right, that Alex is 163 00:10:16,170 --> 00:10:24,090 right to about the relays. It's all about the relays 100% of any 164 00:10:24,090 --> 00:10:32,160 issue is relay related. And I can just I think probably 90% of 165 00:10:32,160 --> 00:10:36,240 people who try out noster say, Oh, it's a Twitter that's 166 00:10:36,240 --> 00:10:38,850 decentralized which of course isn't it? I mean, the protocol 167 00:10:38,850 --> 00:10:42,930 is built for anything was it notes over things and relays or 168 00:10:42,930 --> 00:10:45,540 whatever it stands for some light? Yes, yeah. But the minute 169 00:10:45,540 --> 00:10:51,150 you boot up and a relay is not isn't there or is overloaded and 170 00:10:51,180 --> 00:10:55,710 you know, stuff doesn't load and I mean, the user experiences is 171 00:10:55,710 --> 00:10:59,100 very hit or miss and please don't email me tell me that I'm 172 00:10:59,100 --> 00:11:02,400 doing it wrong. You're holding it wrong. You're holding it 173 00:11:02,400 --> 00:11:06,690 wrong. And then so I was really jacked when when Umbro I think 174 00:11:06,690 --> 00:11:09,780 was a Dorsey said oh, you know he posted a screen picture 175 00:11:09,780 --> 00:11:12,540 because you know why? Why post on you? He doesn't post words. 176 00:11:12,990 --> 00:11:14,820 The like nobody does anymore. They 177 00:11:15,960 --> 00:11:20,910 can emoji PV which I guess is noster for a beautiful life or 178 00:11:20,910 --> 00:11:28,770 you know, have a great day or whatever it is like oh, you can 179 00:11:28,800 --> 00:11:32,580 now load or rely on your Umbro. I'm like, oh, okay, now now 180 00:11:32,580 --> 00:11:37,500 you're Now you're talking. So I install it? Yeah. All right. So 181 00:11:37,530 --> 00:11:41,550 it's like several other apps that are all exciting on Umbro. 182 00:11:41,820 --> 00:11:48,030 But unless you have a public IP with with with a cert with it, 183 00:11:48,030 --> 00:11:51,420 so you can do HTTPS or in this case w s s 184 00:11:52,140 --> 00:11:54,840 is not going to work for you. What is W SS? 185 00:11:55,080 --> 00:11:58,560 This is the w s i don't know if some this is like 186 00:11:58,590 --> 00:12:01,560 a I rarely hear acronym that I've never heard before. I had 187 00:12:01,560 --> 00:12:03,030 no idea what this is. Well, I 188 00:12:03,030 --> 00:12:10,350 learned about it because w s s is is the here w s on HTML now 189 00:12:10,350 --> 00:12:17,880 see, here it is. Stack Overflow. Web web web sockets WebSocket 190 00:12:17,880 --> 00:12:18,330 protocol. 191 00:12:18,360 --> 00:12:19,650 Oh, okay. 192 00:12:20,400 --> 00:12:22,950 Now I'm just Yes, you didn't know this. 193 00:12:23,310 --> 00:12:25,020 Now. Gotcha. Okay, so 194 00:12:25,110 --> 00:12:30,210 so all the apps expect a W s s connection. But of course, your 195 00:12:30,210 --> 00:12:35,460 Umbral is not going to be w s s out of the box is W S. So even 196 00:12:35,460 --> 00:12:41,880 though I use to scale, which is pretty secure, I think I would 197 00:12:41,880 --> 00:12:46,380 now have to go through the effort of setting up a cert for 198 00:12:46,380 --> 00:12:51,870 the for the encrypted session. And otherwise, the apps won't 199 00:12:51,870 --> 00:12:55,710 talk to my relay, and the relay only will archive what I'm doing 200 00:12:55,710 --> 00:12:59,040 anyway. It's not a relay that you can use publicly, as far as 201 00:12:59,040 --> 00:12:59,820 I understand. 202 00:13:01,530 --> 00:13:08,070 So there's no, there's no like, tours a no go. Is which I don't 203 00:13:08,070 --> 00:13:11,640 run over tour. Yeah, but I mean, like if somebody had wanted to 204 00:13:12,450 --> 00:13:14,790 do their nostril failover tour, that's, that's not going 205 00:13:14,910 --> 00:13:19,290 well, you still have to have a secure. Yeah, it's looking for a 206 00:13:19,290 --> 00:13:20,580 secure sockets layer. 207 00:13:21,030 --> 00:13:23,340 Because I mean, 90% of the people that have umbrellas like 208 00:13:23,340 --> 00:13:25,950 at home, they're not they don't have public IPs mapped to that. 209 00:13:25,980 --> 00:13:27,750 No, it did. It's all Tor. 210 00:13:28,320 --> 00:13:32,220 I mean, I haven't used what Tor for me blows. I mean, it's just 211 00:13:32,250 --> 00:13:35,010 oh, it's slow. It sucks. You know, half the stuff you want to 212 00:13:35,010 --> 00:13:39,930 do you have to switch to a Tor browser. So tail scale is is you 213 00:13:39,930 --> 00:13:41,280 know, Godsend 214 00:13:42,960 --> 00:13:45,450 but your public put your public connections like to your 215 00:13:45,450 --> 00:13:48,300 channels and stuff. That's that's Tor. Is that that Tor 216 00:13:48,990 --> 00:13:51,240 course yeah, yeah. Which is because if you're coming back 217 00:13:51,240 --> 00:13:53,430 through if you're coming back through your firewall, your home 218 00:13:53,430 --> 00:13:56,310 network, you know, then you're gonna have to if it doesn't do 219 00:13:56,310 --> 00:13:59,880 tour, then you kind of out of the water. Yeah, you're 220 00:14:00,120 --> 00:14:07,740 and even so there's so I have to reopen a channel to my to my my 221 00:14:07,740 --> 00:14:12,120 Umbral node with podcasts index at least once every two three 222 00:14:12,120 --> 00:14:13,950 weeks. Because whatever. 223 00:14:14,010 --> 00:14:14,880 I've noticed this 224 00:14:15,449 --> 00:14:17,219 with your own with your own note as well. 225 00:14:17,579 --> 00:14:20,099 No, no, I noticed it with your node because I had to dump all 226 00:14:20,099 --> 00:14:22,739 the transactions out for the tax. 227 00:14:23,250 --> 00:14:26,880 Curry's opening and closing 2 million sets every day every 228 00:14:26,880 --> 00:14:27,180 time 229 00:14:27,180 --> 00:14:30,030 it was 2 million it was like when the world is going on and 230 00:14:30,030 --> 00:14:33,420 it was like force close force close force close force close 231 00:14:33,420 --> 00:14:36,540 from podcast index and that's a pretty yeah pretty good node you 232 00:14:36,540 --> 00:14:40,560 know I'm I don't know how to configure it differently so I'm 233 00:14:40,560 --> 00:14:43,950 so sad blows Yeah, and it's it's really the I think it's the 234 00:14:43,950 --> 00:14:46,380 laptop that I'm running that arborlon That's why I ordered a 235 00:14:46,410 --> 00:14:49,830 Bitcoin machines another one of those because I have no problem 236 00:14:49,830 --> 00:14:52,410 with that machine, even though it's also running over Tor same 237 00:14:52,410 --> 00:14:56,760 network. So it's got to be something with the with the 238 00:14:56,760 --> 00:15:00,540 machine. It's all it's amazing. Any of it works at all. If it's 239 00:15:00,540 --> 00:15:06,690 amazing any of this works, but congratulations to Mitch on on a 240 00:15:06,690 --> 00:15:09,360 great new version of pod verse. Love it. I love that. Thanks, 241 00:15:10,170 --> 00:15:18,900 Todd, for running with a huge pair of shears loppers has no, 242 00:15:19,080 --> 00:15:21,720 he does not afraid of anything. Oh yeah, we'll just do the 243 00:15:21,720 --> 00:15:26,040 switching protocols on the fly or whatever it was, it didn't 244 00:15:26,040 --> 00:15:30,930 work and then T switch to I guess he was streaming an audio 245 00:15:30,930 --> 00:15:36,690 slash, whatever. MBA versus video so and he just switched it 246 00:15:36,690 --> 00:15:39,330 on the fly and it all worked. It was amazing, was really amazing. 247 00:15:40,020 --> 00:15:43,110 And he's whatever whatever they've got go in there with his 248 00:15:43,110 --> 00:15:47,520 setup. He's able to he's able to get it. Me in a pot, the pot 249 00:15:47,520 --> 00:15:50,130 things go out for the video and the audio stream BOTH Yeah, I 250 00:15:50,130 --> 00:15:53,490 mean, he's there. You can see the sort of like the narrowing 251 00:15:53,490 --> 00:15:56,520 down of these of these troubles each week as they go in this. 252 00:15:56,550 --> 00:16:00,600 Like they're settling on an actual, stable platform that 253 00:16:00,600 --> 00:16:05,220 works. Very cool. And Mitch is Hi, Mitch is homepod Verse I'm 254 00:16:05,220 --> 00:16:09,480 in and I am to me like he was he's pretty excited about. He's 255 00:16:09,480 --> 00:16:13,170 pretty excited about this version. And in mean, any should 256 00:16:13,170 --> 00:16:18,600 be. Feels good. Yeah, it feels like it's really becoming. It 257 00:16:18,600 --> 00:16:22,860 feels like it's taken a step into like, the upper level of 258 00:16:22,860 --> 00:16:26,130 podcast apps. Now the stabilities there, the polishes, 259 00:16:26,130 --> 00:16:29,130 they're just getting shot versus a great app. Yeah. 260 00:16:29,850 --> 00:16:34,140 And did you tell me that podcast guru was going to implement 261 00:16:34,590 --> 00:16:36,300 value for valued payments? 262 00:16:37,530 --> 00:16:39,840 Maybe I hope so. In the future. 263 00:16:40,620 --> 00:16:42,780 I thought I heard that somewhere. I don't know. I'm 264 00:16:42,780 --> 00:16:45,240 trying to keep up. No one tells me anything anymore. 265 00:16:45,720 --> 00:16:46,650 There. Yeah. 266 00:16:46,709 --> 00:16:47,429 I don't know why. 267 00:16:49,320 --> 00:16:50,220 Yeah, hope so. 268 00:16:51,210 --> 00:16:55,650 I, we did get a great gift from Marcus couch. If you don't think 269 00:16:55,650 --> 00:16:59,310 you know, Marcus couch, but he I know him. Oh, goodness, back to 270 00:16:59,310 --> 00:17:06,510 the pod show days. And so Marcus Heyman, his lovely wife always 271 00:17:06,510 --> 00:17:10,650 stayed in touch. And he's a big fan of podcasting. 2.0. And he 272 00:17:10,950 --> 00:17:14,730 was always, always promoting and boosting. And he said that he 273 00:17:14,730 --> 00:17:21,150 won in an auction podcast apps.com. Whoa, anyway, and he 274 00:17:21,150 --> 00:17:24,210 said, Hey, you wanna You want me to transfer that to you? So now 275 00:17:24,210 --> 00:17:26,640 you hold on to that boot case, he's just going to point it to 276 00:17:26,760 --> 00:17:30,510 to our Apps page. So instead of new Cast apps, we'll also have 277 00:17:30,540 --> 00:17:31,920 podcast apps.com. 278 00:17:32,850 --> 00:17:34,440 Well, that's a strong win. 279 00:17:35,400 --> 00:17:38,430 Yeah, I think he gets it in 11 days or something. I don't know 280 00:17:38,430 --> 00:17:41,460 what he paid for it. I hope he didn't go crazy on that. Oh, 281 00:17:41,460 --> 00:17:41,700 yeah. 282 00:17:41,700 --> 00:17:43,530 Hope it Yeah. Strong winds. 283 00:17:43,890 --> 00:17:45,660 Strong wind is the right word. 284 00:17:46,230 --> 00:17:47,820 I like cast app stock. Yeah, 285 00:17:47,820 --> 00:17:51,210 that's pretty good. Great domain. Great to me. I tried to 286 00:17:51,210 --> 00:17:57,120 register lawful but awful today was a phrase that you all did 287 00:17:57,120 --> 00:18:01,740 you not read the latest? How top political podcasts are spread 288 00:18:01,740 --> 00:18:04,350 unsubstantiated and false claims? 289 00:18:04,710 --> 00:18:08,880 Oh, I remember lawful but awful. That's. That's Vicki, Vicki, 290 00:18:08,940 --> 00:18:12,480 Vicki. So she came out with another article, our our pal 291 00:18:12,480 --> 00:18:14,430 Vicki over there at Brookings. 292 00:18:14,820 --> 00:18:18,360 We have printed it last night. And I'm about what I'm gonna 293 00:18:18,360 --> 00:18:21,990 send Brookings, a bill for the amount of toner that I had to 294 00:18:21,990 --> 00:18:26,010 use to print this 25,000 word monstrosity of an article with a 295 00:18:26,010 --> 00:18:29,640 lot of graphs, a lot of graphs less of an article and more like 296 00:18:29,640 --> 00:18:36,690 a pamphlet, or a or a or an imprint is very, very long. And 297 00:18:36,690 --> 00:18:38,220 I have not even I have not read it yet. 298 00:18:38,310 --> 00:18:42,210 Well, the funny thing is, you know, the article is audible 299 00:18:42,210 --> 00:18:44,970 reckoning, which I'm not quite sure. I'm not quite sure why she 300 00:18:44,970 --> 00:18:49,800 chose that as a title. Valerie vert Shafter how top political 301 00:18:49,800 --> 00:18:54,330 podcasters which I'm not in that list, by the way, spread 302 00:18:54,750 --> 00:18:58,620 unsubstantiated and false claims. And our whole article as 303 00:18:58,620 --> 00:19:03,120 it comes to the evolution of the podcasting medium is filled with 304 00:19:03,150 --> 00:19:09,090 unsubstantial and false claims, such as Ben Hammersley, of 305 00:19:09,090 --> 00:19:13,590 course invented podcasting. And he is a podcast pioneer. 306 00:19:16,800 --> 00:19:23,820 This so I don't have on hand the article that we the last time 307 00:19:23,820 --> 00:19:24,720 this came up, 308 00:19:25,379 --> 00:19:29,369 you know, and we actually got we just we discussed it on the show 309 00:19:29,370 --> 00:19:33,630 for sure. Yeah. It's been a couple of months ago. But this 310 00:19:33,630 --> 00:19:39,390 was the one where, like, on the first page, she referenced a New 311 00:19:39,390 --> 00:19:44,250 York Times article, and she said, and she summarized and she 312 00:19:44,250 --> 00:19:47,280 she gave a link to the article and summarized what the articles 313 00:19:47,280 --> 00:19:50,940 conclusions were. So of course, I clicked the link and went and 314 00:19:50,940 --> 00:19:54,480 read the article. The articles conclusions were the 180% 315 00:19:54,510 --> 00:19:57,270 opposite of the thing that she said they were it was like, she 316 00:19:57,270 --> 00:20:00,570 said, The New York Times discovered this sentence so that 317 00:20:00,570 --> 00:20:03,390 when actually they said literally in the article, it was 318 00:20:03,390 --> 00:20:07,680 the exact opposite of the thing. And I was like, okay. Okay, like 319 00:20:09,240 --> 00:20:11,370 she had she said some things that were very interesting, 320 00:20:11,370 --> 00:20:13,830 although not the way I remember it, but it doesn't matter, 321 00:20:14,070 --> 00:20:17,100 because what happened, according to Ben Hammersley and Ben 322 00:20:17,100 --> 00:20:19,470 Hammersley, who basically invented the whole, a whole 323 00:20:19,470 --> 00:20:23,880 category. He just because he said, audio blogging, 324 00:20:23,880 --> 00:20:27,030 podcasting, Guerilla Media. This is before anything was really 325 00:20:27,900 --> 00:20:32,100 before Dave and I put it all together with the iPod. But at 326 00:20:32,100 --> 00:20:35,160 the time, this term was describing serial audio content 327 00:20:35,160 --> 00:20:38,550 that could be played on demand through any mp3 device such as 328 00:20:38,550 --> 00:20:42,000 the then increasingly popular iPod, listeners could take their 329 00:20:42,000 --> 00:20:45,060 audio with them, pause it as needed, or the pause start 330 00:20:45,060 --> 00:20:48,630 button and start again at their convenience. Early adopters of 331 00:20:48,630 --> 00:20:51,330 the medium shared episodes through really simple 332 00:20:51,330 --> 00:20:54,870 syndication feeds, which users could consume, by subscribing 333 00:20:54,870 --> 00:20:58,560 directly or indirectly. The RSS architecture here comes 334 00:20:58,710 --> 00:21:02,040 facilitated the growth of a decentralized medium detached 335 00:21:02,040 --> 00:21:07,020 from regulatory oversight. Which I like that's the that's the 336 00:21:07,020 --> 00:21:10,110 only part of the article I think, is really good. Because 337 00:21:10,110 --> 00:21:13,410 then she goes on with it was a medium where quote, anyone can 338 00:21:13,410 --> 00:21:16,980 be a publisher, anyone can be a broadcaster, according to one of 339 00:21:16,980 --> 00:21:21,030 podcasting pioneers, footnote 14, and that's literally been 340 00:21:21,030 --> 00:21:25,830 hammered. Hammersley. So he, I guess, did it all? And then 341 00:21:29,130 --> 00:21:31,950 yeah, where was it? There was something funny in here, like 342 00:21:31,950 --> 00:21:35,280 once written off as a dead medium. See, where was that it 343 00:21:35,280 --> 00:21:38,760 was? Now, it doesn't really matter. But what, what what I 344 00:21:38,760 --> 00:21:41,220 think is unfortunate, because the again, the whole point of 345 00:21:41,220 --> 00:21:47,280 this article is podcasting has no moderation. There's unlike 346 00:21:47,280 --> 00:21:51,930 social media, there's no way for the crowd to push back. Where I 347 00:21:51,930 --> 00:21:54,720 would say immediately Well, if you actually did some research, 348 00:21:54,720 --> 00:21:58,470 you see that currently booster grams are a way to push forward 349 00:21:58,470 --> 00:22:02,700 or push back and there is sufficient work on cross app 350 00:22:02,700 --> 00:22:07,170 comments. So since there, since it's all just people talking to 351 00:22:07,170 --> 00:22:11,610 themselves, with no feedback loop, complete bull crap, 352 00:22:11,940 --> 00:22:16,560 because we do have things such as email and, and, and people do 353 00:22:16,740 --> 00:22:21,030 have places to comment or even services to comment. You know, 354 00:22:21,030 --> 00:22:25,350 we don't have any. We don't have any, any moderation. It's always 355 00:22:25,350 --> 00:22:28,980 about moderation with her. And how do we get the overlords to 356 00:22:28,980 --> 00:22:32,730 moderate and make sure that people don't get miss or 357 00:22:32,730 --> 00:22:37,350 disinformation out there? And again, if she did any work, and 358 00:22:37,350 --> 00:22:42,360 maybe did even a Google search, you might find that what she 359 00:22:42,360 --> 00:22:45,570 says, Well, there's no incentive for the companies that make 360 00:22:45,570 --> 00:22:50,550 podcast apps to do any of this. That companies. Yeah, I mean, 361 00:22:50,550 --> 00:22:55,110 the beauty is, if she, she seems that you know, Brookings seems 362 00:22:55,110 --> 00:22:58,740 to have a lot of money. So I say Brookings, why don't you come 363 00:22:58,740 --> 00:23:03,990 in, read the API docs and create your own app, you can use our 364 00:23:03,990 --> 00:23:09,120 index, then you can put all kinds of reporting bits and an 365 00:23:09,480 --> 00:23:13,140 alarm bells that you can push that go somewhere until somebody 366 00:23:13,560 --> 00:23:17,040 can do all kinds of stuff like this dashboard. We have a 367 00:23:17,040 --> 00:23:19,860 dashboard. Yes, you can have a complete dashboard. You could 368 00:23:19,860 --> 00:23:23,100 have a an app that centers all the stuff that is bad, you could 369 00:23:23,100 --> 00:23:27,090 actually you as Brookings Institute could do this. You 370 00:23:27,090 --> 00:23:30,480 could filter out all the stuff that is awful, lawful, but 371 00:23:30,480 --> 00:23:31,080 awful. 372 00:23:32,100 --> 00:23:34,170 That should be the name of the app. LBA Yes, 373 00:23:34,230 --> 00:23:37,170 I tried. I'm sure someone somebody's already registered it 374 00:23:37,770 --> 00:23:41,220 but that's literally what this what the content is called. 375 00:23:41,340 --> 00:23:42,720 lawful but awful. 376 00:23:44,040 --> 00:23:47,820 Yeah, this is always this always strikes me similarly to the way 377 00:23:47,820 --> 00:23:53,970 that the Bitcoin narrative of you know, it's just used by bad 378 00:23:53,970 --> 00:23:59,580 guys. The bad guys use it for all kinds of terrible things. So 379 00:24:00,060 --> 00:24:03,180 clearly, it's bad. Well, you know, like, have you checked out 380 00:24:03,180 --> 00:24:06,870 the US dollar lately past use for leg it used for a lot of bad 381 00:24:06,870 --> 00:24:10,470 things for the history of all of, you know, for all of the 382 00:24:10,470 --> 00:24:15,210 entire history of its of its use in there. It's like, well, yeah, 383 00:24:15,240 --> 00:24:17,790 podcasts. Sure there's misinformation and 384 00:24:17,790 --> 00:24:21,060 disinformation and all kinds of information on podcasts. We know 385 00:24:21,060 --> 00:24:23,490 step outside every now and then you're gonna see that there's a 386 00:24:23,490 --> 00:24:28,350 diff in DM on every corner of the street in every newspaper. 387 00:24:28,350 --> 00:24:32,490 It's all over the place. MDM is Yeah, Mal DIS and missing from 388 00:24:32,490 --> 00:24:36,060 it. Of course. I found that when I found the article, the US 389 00:24:36,060 --> 00:24:41,580 podcast, this is from October 3. Last year, yeah, right. 22. 390 00:24:41,580 --> 00:24:45,180 Yeah. us in the title of the article is us podcasters spread 391 00:24:45,180 --> 00:24:47,880 Kremlin narratives on Nord Stream sabotage. 392 00:24:48,720 --> 00:24:51,960 It turns out to all be true. Yes, yes. So 393 00:24:52,290 --> 00:24:56,940 here it says the US did it. They just give me the quote US did it 394 00:24:56,940 --> 00:25:00,690 conspiracy on popular American podcast and there A chart 395 00:25:01,979 --> 00:25:05,909 that is now confirmed on a few saw now confirmed by Pulitzer 396 00:25:05,909 --> 00:25:10,679 Prize winning Seymour Hersh, Seymour Hersh, who? Who has 397 00:25:10,769 --> 00:25:15,389 stopped like the Vietnam War he was. He is credited with being 398 00:25:15,389 --> 00:25:18,419 the impetus for stopping the Vietnam War because of his 399 00:25:18,419 --> 00:25:25,409 reporting on the atrocities committed there. But okay. Turns 400 00:25:25,409 --> 00:25:29,189 out to be true. So I can't see anything here where she retracts 401 00:25:29,189 --> 00:25:31,919 that, of course, nobody's listening to the retraction in 402 00:25:31,919 --> 00:25:36,329 this in this new article, the role of podcasting apps and tech 403 00:25:36,329 --> 00:25:40,469 companies. Okay, that we talked to some of those people since 404 00:25:40,469 --> 00:25:44,039 the early years. What does to you if you since the early years 405 00:25:44,039 --> 00:25:47,309 of podcasting apps have taken a hands off approach to moderating 406 00:25:47,339 --> 00:25:52,049 moderating content? And for button No, no Apple deep 407 00:25:52,049 --> 00:25:55,979 platform, Spotify, the platform so no, since the early years of 408 00:25:55,979 --> 00:26:00,209 pod, I think overcast, take stuff off. Since the early years 409 00:26:00,209 --> 00:26:03,359 of podcasting apps have taken a hands off approach to moderating 410 00:26:03,359 --> 00:26:06,419 content have provided a sparse architecture to facilitate 411 00:26:06,419 --> 00:26:10,319 distribution, as the medium continues to evolve and expand 412 00:26:11,159 --> 00:26:15,629 for 18 years, the tech companies that develop the tech companies 413 00:26:15,659 --> 00:26:19,139 Hey, Mitch, this is you. The tech companies that can go a 414 00:26:19,139 --> 00:26:22,679 Franco Franco Oscar your tech companies that develop 415 00:26:22,679 --> 00:26:26,489 podcasting apps, you can help shape the information ecosystem 416 00:26:26,669 --> 00:26:30,659 in important ways by crafting more robust content moderation 417 00:26:30,659 --> 00:26:34,169 guidelines and practices, promoting greater transparency 418 00:26:34,349 --> 00:26:38,279 and improving the in app experience for users. Which 419 00:26:38,279 --> 00:26:40,349 starts with content moderation. 420 00:26:41,190 --> 00:26:42,930 I've noticed started with sleep timers. 421 00:26:44,190 --> 00:26:48,390 The number one requested feature is not content moderation. Oh, 422 00:26:48,390 --> 00:26:57,480 Vicki. Oh, is it asleep timer? Dark Mode, okay. As the medium 423 00:26:57,480 --> 00:27:00,300 grows in popularity, oh, this is interesting. And based on the 424 00:27:00,300 --> 00:27:03,990 European Union's recently enacted Digital Services Act, 425 00:27:04,290 --> 00:27:08,790 which the DSA which sets forth the contours of digital content 426 00:27:08,790 --> 00:27:12,390 moderation across the EU, podcasting apps may soon be 427 00:27:12,390 --> 00:27:16,230 forced to reckon with how they handle content that falls into 428 00:27:16,230 --> 00:27:20,820 the so called here it is lawful but awful domain, such as hate 429 00:27:20,820 --> 00:27:25,530 speech, misinformation, and targeted harassment. Well, I 430 00:27:25,530 --> 00:27:29,670 harass people on the podcast all the time. You do and I'm very 431 00:27:29,670 --> 00:27:33,180 proud of that. These policies will have to balance a desire to 432 00:27:33,180 --> 00:27:37,230 limit the real world harm harm that can stem from the mass 433 00:27:37,230 --> 00:27:40,770 dissemination of objectionable content with a vital necessity 434 00:27:40,770 --> 00:27:44,370 not to curtail speech too aggressively, or inconsistency 435 00:27:44,400 --> 00:27:48,720 or its balance. Okay, to address these challenges, tech companies 436 00:27:48,720 --> 00:27:53,850 should colon colon, colon provide more detailed 437 00:27:53,850 --> 00:27:56,730 transparent guidelines for the content that podcasters can 438 00:27:56,730 --> 00:27:58,170 share on their apps. Why think 439 00:27:58,170 --> 00:28:00,750 waiter and the waiter there these options? Do I get to pick 440 00:28:00,750 --> 00:28:02,130 between these options? No, no? No. 441 00:28:02,730 --> 00:28:04,020 It's a sure Okay, sure. 442 00:28:04,050 --> 00:28:07,020 You should? Because I would like to choose between these. 443 00:28:07,080 --> 00:28:10,890 Yeah, no, no, it's a should do. We want to share this with the 444 00:28:10,890 --> 00:28:14,310 app developers so they know what they should be doing. Develop 445 00:28:14,310 --> 00:28:17,340 detailed, transparent guidelines for the content that apps will 446 00:28:17,340 --> 00:28:22,440 promote or recommend. Hmm. She also has some she's misinformed. 447 00:28:22,440 --> 00:28:25,440 She believes that these apps have algorithms that recommend 448 00:28:25,440 --> 00:28:30,600 stuff. Here, in addition to the guidelines detailing what 449 00:28:30,600 --> 00:28:32,940 content tech companies will host some platforms have developed 450 00:28:32,940 --> 00:28:35,580 separate guidelines for detailing the types of content 451 00:28:35,580 --> 00:28:38,070 their recommendation algorithms will promote 452 00:28:38,670 --> 00:28:42,330 the algorithm get in most podcast apps, it goes like this 453 00:28:44,310 --> 00:28:49,890 GREP the request logs and find out which which at which podcast 454 00:28:49,890 --> 00:28:53,160 is being recommended, like requested the most? Or how many 455 00:28:53,160 --> 00:28:57,870 subscribers are in that are the most for each podcast and then 456 00:28:57,870 --> 00:29:01,290 recommend the ones that are at the top? That is the algo that's 457 00:29:01,290 --> 00:29:03,990 the extent of the algorithm. There's there's no there's no 458 00:29:03,990 --> 00:29:04,770 complicated, 459 00:29:04,830 --> 00:29:08,460 incorrect, incorrect, incorrect. Vicki Brookings Institute 460 00:29:08,520 --> 00:29:11,610 institution says apart from Word and route of mouth 461 00:29:11,610 --> 00:29:16,770 recommendations, which will also soon stop adding that but you 462 00:29:16,770 --> 00:29:21,720 know that will editorialize editorial. Users often discover 463 00:29:21,720 --> 00:29:25,260 new podcasts through in app recommendation systems like 464 00:29:25,350 --> 00:29:29,880 featured most popular lists, or personalized recommendations. 465 00:29:30,360 --> 00:29:33,420 podcast app, like Spotify and Apple podcast should should 466 00:29:33,450 --> 00:29:36,810 develop similarly detailed policies on the types of content 467 00:29:36,810 --> 00:29:39,840 they may choose not to amplify to their users via 468 00:29:39,840 --> 00:29:43,470 recommendation systems. Even if the app still decide to host it, 469 00:29:43,740 --> 00:29:47,190 which it emits. You need to you just need to stop Yeah, just 470 00:29:47,190 --> 00:29:50,640 bothering about HLS and stuff that makes your app work and 471 00:29:50,640 --> 00:29:54,990 just really focus on this page double down on the paperwork of 472 00:29:55,350 --> 00:29:58,260 regulations and policies for at least six months. But 473 00:29:58,260 --> 00:30:02,610 wait, there's more. Improve reporting processes for 474 00:30:02,610 --> 00:30:08,460 individual podcast episodes. Ah, bad episode, podcast apps have 475 00:30:08,460 --> 00:30:12,480 not yet developed sophisticated real time systems to identify 476 00:30:12,480 --> 00:30:17,910 harmful content at scale. And can you can you only guess what 477 00:30:17,910 --> 00:30:21,390 their what they're what her solution is for this broken 478 00:30:21,390 --> 00:30:23,550 shit? Broken feature? 479 00:30:24,810 --> 00:30:27,810 Reg ID laws, regulations. 480 00:30:28,230 --> 00:30:31,770 No, but we are literally doing what she is asking for 481 00:30:32,490 --> 00:30:38,490 transcripts and machine learning to so your app needs to scan 482 00:30:38,490 --> 00:30:41,430 through all the transcripts to find stuff that's wrong. 483 00:30:42,090 --> 00:30:46,710 Yeah, so so the way this works is you you transcribe everything 484 00:30:46,920 --> 00:30:54,780 in then somebody at when a when a particular strain of MDM is 485 00:30:54,780 --> 00:30:59,130 identified a strain I like that, yes, as an Android, a new MDM 486 00:30:59,130 --> 00:31:04,770 variant, when a new variant of MDM is identified. Such as the, 487 00:31:04,980 --> 00:31:10,980 the, the US, the US blew up the pipeline, various variants of 488 00:31:11,370 --> 00:31:14,670 MDM of MDM, once that is identified, somebody plugs it 489 00:31:14,670 --> 00:31:20,040 into the system. They stick it in there, it goes out to all the 490 00:31:20,070 --> 00:31:25,800 to all the apps and cleanses them of claims. All of the 491 00:31:25,800 --> 00:31:29,490 episodes, that it's a vaccine, this is an Indian vaccine is 492 00:31:29,490 --> 00:31:33,930 cleanses them of all the episodes that have this phrase 493 00:31:33,960 --> 00:31:37,680 or this terminology that have been identified by GPT or 494 00:31:37,680 --> 00:31:38,460 something within. 495 00:31:38,760 --> 00:31:41,610 I want to I want to I want to turn, I want to turn 496 00:31:41,610 --> 00:31:45,120 it in six months later, when Seymour Hersh writes an article 497 00:31:45,120 --> 00:31:46,830 that says that it was actually true 498 00:31:46,860 --> 00:31:51,900 that all then they hit undo the Undo Ctrl Z Ctrl Z, Z. All 499 00:31:51,900 --> 00:31:54,810 right, so but I want to turn this around. And I want to offer 500 00:31:54,810 --> 00:31:57,300 to the Brookings Institute or institution. 501 00:31:58,980 --> 00:32:00,900 Yes, thanks. 502 00:32:01,560 --> 00:32:06,330 I want to offer our services, anything we can do to help 503 00:32:06,330 --> 00:32:09,990 because everything you'd say, No, this is the last I'll read 504 00:32:09,990 --> 00:32:13,230 of this. Because then it goes into role of government design, 505 00:32:13,230 --> 00:32:17,310 an app architecture that allows for richer community engagement 506 00:32:17,310 --> 00:32:22,500 and more dynamic information environment. Vicki, Google, 507 00:32:22,530 --> 00:32:26,940 okay, podcasting 2.0 The namespace you have not done the 508 00:32:26,940 --> 00:32:30,780 work people who who support Brookings with your donations, 509 00:32:30,840 --> 00:32:34,380 stop them and take them back until she does the work because 510 00:32:34,380 --> 00:32:38,280 she literally is discussing what we're doing. pause on this 511 00:32:38,310 --> 00:32:43,260 podcast apps could experiment, which we call running with 512 00:32:43,260 --> 00:32:46,440 scissors, with a variety of inept features for these 513 00:32:46,440 --> 00:32:50,190 purposes, including voting and commenting systems with 514 00:32:50,190 --> 00:32:53,730 additional features at the episode level. Hello, Vicki. 515 00:32:54,150 --> 00:32:57,420 With the development of open source transcription models like 516 00:32:57,450 --> 00:33:01,170 open AIS whisper, adding transcripts to episodes has 517 00:33:01,170 --> 00:33:06,210 never been easier. Oh, everyone's so creative. Building 518 00:33:06,300 --> 00:33:11,100 on ad hoc, decentralized contribution from fans, users 519 00:33:11,100 --> 00:33:14,790 and hosts could be a way to add Show Notes and references to 520 00:33:14,790 --> 00:33:18,360 podcast episodes like I don't know, chapters, anybody. 521 00:33:18,840 --> 00:33:23,250 Moreover, podcasting apps could experiment with up voting and 522 00:33:23,250 --> 00:33:26,370 down voting features for these contributions, drawing 523 00:33:26,400 --> 00:33:30,750 inspiration from community driven websites such as Reddit, 524 00:33:30,840 --> 00:33:37,620 and Stack Overflow, or Twitter's a community. All of all of this 525 00:33:37,620 --> 00:33:41,910 has been invented, much of it has been implemented, and you're 526 00:33:41,910 --> 00:33:47,310 still in the Stone Age Vicki, and we will be happy we welcome 527 00:33:47,310 --> 00:33:51,240 you. I think it's a great idea. As long as you promote the 528 00:33:51,240 --> 00:33:56,040 namespace and apps that do 2.0 I want lots I want people to build 529 00:33:56,970 --> 00:33:58,230 safe apps. 530 00:33:58,830 --> 00:33:59,880 I would love that. 531 00:34:01,050 --> 00:34:06,510 That'd be great. You can use an app that for for adults, like 532 00:34:06,660 --> 00:34:14,010 pod verse cast, thematic curio caster podcast guru fountain or 533 00:34:14,010 --> 00:34:17,940 you could have your childish pussy app we want you to build 534 00:34:17,940 --> 00:34:22,290 that I really I'm serious. I will help I will consult for 535 00:34:22,290 --> 00:34:26,400 free I will tell you how to do it we have all this so stop 536 00:34:26,400 --> 00:34:28,590 wasting your donors money Vicki 537 00:34:29,250 --> 00:34:31,710 you can have real scissors are you can have safety scissors of 538 00:34:31,710 --> 00:34:32,160 course 539 00:34:32,190 --> 00:34:34,560 with the rounded with the rounded tip. Yeah, 540 00:34:34,590 --> 00:34:37,440 they just fallen they we fall on a stick in your jugular? 541 00:34:37,470 --> 00:34:41,010 No. Now here's one more thing. I do think that she she thinks 542 00:34:41,010 --> 00:34:44,580 this is very important podcast or funding. Despite the 543 00:34:44,580 --> 00:34:47,250 importance of advertisement and sponsorship revenue to the 544 00:34:47,250 --> 00:34:50,760 podcasting ecosystem, there are no obvious requirements for 545 00:34:50,760 --> 00:34:54,780 financial disclosures beyond those agreed upon between a 546 00:34:54,780 --> 00:34:57,150 given series and its sponsors. 547 00:34:58,020 --> 00:35:00,510 Although which losers Could you play? Sibley 548 00:35:01,380 --> 00:35:05,160 well, and but we've already been done in our world, we literally 549 00:35:05,190 --> 00:35:08,910 read out the money that people send us, we could not be more 550 00:35:08,910 --> 00:35:09,990 transparent. 551 00:35:10,650 --> 00:35:15,840 If the I mean, like, no business has to tell anybody who gives 552 00:35:15,840 --> 00:35:20,220 them money unless it's like a terrorist. You're not required 553 00:35:20,220 --> 00:35:23,220 to like to like report when somebody gives you, hey, 554 00:35:23,220 --> 00:35:26,070 somebody just paid me. Okay. Like? 555 00:35:26,700 --> 00:35:32,190 Well, I think I think the point she's making is that the radio 556 00:35:32,190 --> 00:35:35,580 industry and social media influencers have to disclose if 557 00:35:35,580 --> 00:35:38,340 they're being paid off their I don't know, an advisor to 558 00:35:38,340 --> 00:35:42,030 something. I think that I think that's what what she's saying. 559 00:35:42,390 --> 00:35:46,170 And that, that these financial relationships are not clear. It 560 00:35:46,170 --> 00:35:48,420 would just be another lever or another wedge, which is why I 561 00:35:48,420 --> 00:35:52,620 think we like the lightning Bitcoin network, except to fight 562 00:35:52,620 --> 00:35:56,310 exactly what she wants to useless for. But again, all of 563 00:35:56,310 --> 00:35:59,820 it is completely available. I think it'd be podcasting. 2.0 564 00:35:59,970 --> 00:36:04,290 There's plenty of room for these kinds of crippled apps, also 565 00:36:04,290 --> 00:36:12,900 known as crap. On the fly on the fly, fly on the fly, I should 566 00:36:12,900 --> 00:36:16,080 have said we should make plural craps. I should have man craps, 567 00:36:16,110 --> 00:36:16,620 double. I've 568 00:36:16,620 --> 00:36:20,760 got it. Yeah, I've got a cheat sheet. By the way, it is my 100% 569 00:36:20,760 --> 00:36:25,740 Cheat Sheet. It is basically a printout of the thesaurus for 570 00:36:25,740 --> 00:36:29,850 everything I can reuse to every term I can use to replace 100%. 571 00:36:30,990 --> 00:36:32,730 So yes, yes, please. 572 00:36:32,879 --> 00:36:36,089 I agree with you, Adam entirely entirely. 573 00:36:42,210 --> 00:36:46,200 I would have more respect for I just would have more respect for 574 00:36:46,200 --> 00:36:52,050 the, for the, for the arguments being made here. If she would 575 00:36:52,050 --> 00:36:55,260 stop spreading misinformation while she's doing it. I mean, 576 00:36:55,320 --> 00:36:59,010 this is the same problem that I had with Leo's comments on pod 577 00:36:59,040 --> 00:37:06,090 on pod news weekly review is, it's like, okay, you know, 578 00:37:06,090 --> 00:37:11,310 you're, you just said that the that Alex Jones was the whole 579 00:37:11,310 --> 00:37:13,860 point of the podcast index, which is completely not true, 580 00:37:14,010 --> 00:37:16,950 and go on to save like three or four things that are complete 581 00:37:16,950 --> 00:37:21,600 lies that are absolutely, demonstrably. Everybody knows 582 00:37:21,600 --> 00:37:25,680 they're not true. So it's like, boy, if you want to have any 583 00:37:25,680 --> 00:37:28,950 credibility, when you criticize other people from met for 584 00:37:28,950 --> 00:37:33,990 misinformation, stop spreading it during your criticism, that 585 00:37:33,990 --> 00:37:36,660 just has to be sort of like the well that's kind of table 586 00:37:36,660 --> 00:37:37,350 stakes. 587 00:37:37,920 --> 00:37:41,340 But that's kind of the point is that misinformation, 588 00:37:41,340 --> 00:37:46,890 disinformation, Mal information. It is it's all subjective. And 589 00:37:46,920 --> 00:37:50,190 everyone gets stuff, right. And she's literally making the case 590 00:37:50,430 --> 00:37:56,370 that regulated businesses that have lots of, of these aspects 591 00:37:56,370 --> 00:38:02,190 like television. They're just that is just as bad. Except I 592 00:38:02,190 --> 00:38:05,520 guess you can get fired easier or something like that. The 593 00:38:05,520 --> 00:38:09,240 point is, it's such a waste of their money, whereas they if 594 00:38:09,240 --> 00:38:13,230 they believe that is the world they want to live in. My point 595 00:38:13,230 --> 00:38:16,950 is we have the toolkit we even have, what's the what's the 596 00:38:16,950 --> 00:38:21,600 framework that the breeze started off with? The podcast 597 00:38:21,600 --> 00:38:23,670 work? Yeah, the open source framework. 598 00:38:24,180 --> 00:38:27,450 Oh, you? Air, air, air 599 00:38:27,450 --> 00:38:30,000 something air play airsoft air? 600 00:38:30,450 --> 00:38:35,460 Air soft. Now, you're talking about Ben, Ben hills. Yeah, 601 00:38:35,490 --> 00:38:38,580 I mean, we haven't you have it? Well shoot, even you could take 602 00:38:38,580 --> 00:38:43,740 pod friend open source version, you can spin up an app quite 603 00:38:43,740 --> 00:38:47,610 quickly, and implement all these features, instead of wasting 604 00:38:47,610 --> 00:38:54,000 Dave's paper and toner with your 25,000 words of marginally 605 00:38:54,000 --> 00:38:58,050 entertaining content, which is just regurgitated from the last 606 00:38:58,050 --> 00:38:58,530 time. 607 00:38:59,460 --> 00:39:02,880 Anytime, anytime podcast player. And that's what you're thinking. 608 00:39:03,090 --> 00:39:04,890 Anytime you had written in flutter. Yeah, 609 00:39:04,920 --> 00:39:08,190 and I would love it because it would promote the namespace, it 610 00:39:08,190 --> 00:39:12,090 would promote so much, it will be a very, very good idea. 611 00:39:14,130 --> 00:39:18,720 This to get to dig and none dig into this a little bit, but kind 612 00:39:18,720 --> 00:39:24,450 of pull this thread a bit. So I think there's we have to 613 00:39:24,450 --> 00:39:30,930 understand. I believe that that there's trade offs with a lot of 614 00:39:30,930 --> 00:39:34,800 this technology and maybe I'm, I'm still deep in the weeds on 615 00:39:35,460 --> 00:39:40,020 technological society, the Juggalo book, mind is just 616 00:39:40,110 --> 00:39:44,220 aiming in this direction sort of all the time. But for Ferny for 617 00:39:44,220 --> 00:39:51,030 example, Mastodon we know is there any doubt I was talking to 618 00:39:51,030 --> 00:39:54,030 Alex this week about this? Is there any doubt in anybody's 619 00:39:54,030 --> 00:39:58,260 mind that what is going to happen with mastodon? We can all 620 00:39:58,260 --> 00:40:00,630 agree it's better than better than Twitter. I I think we can 621 00:40:00,630 --> 00:40:04,230 all agree Oh, yes, it isn't, as Sure. But just because it's 622 00:40:04,230 --> 00:40:09,390 better does not mean that it is not that he doesn't have his own 623 00:40:09,390 --> 00:40:14,730 problems and B could potentially be even worse in the right 624 00:40:14,730 --> 00:40:17,820 circle under the right circumstances. And what I mean 625 00:40:17,820 --> 00:40:23,400 by that is, so actually, it's actually much easier to do 626 00:40:23,400 --> 00:40:27,060 something nefarious with Mastodon sure, like, get like 627 00:40:27,060 --> 00:40:32,820 create a reputation system. Like some sort of open reputation 628 00:40:32,820 --> 00:40:38,040 system that tags each individual Mastodon user account with a 629 00:40:38,190 --> 00:40:43,680 with a social score. Yeah, sure. And then all these new instances 630 00:40:43,680 --> 00:40:47,490 begin to begin to sign on to this reputation system. So they 631 00:40:47,580 --> 00:40:51,270 will instantly block replies from people who don't, who don't 632 00:40:51,270 --> 00:40:55,050 satisfy the reputation score. I mean, like, that's even easier 633 00:40:55,050 --> 00:40:58,830 to do. That's way easier to do on Mastodon than it is on 634 00:40:58,830 --> 00:41:01,560 Twitter, you really couldn't do that on as an outside user on 635 00:41:01,560 --> 00:41:07,140 Twitter, that this just because we go decentralized, and we 636 00:41:07,200 --> 00:41:10,320 just doesn't doesn't mean all that horrible stuff can happen. 637 00:41:10,530 --> 00:41:11,250 Right? 638 00:41:11,310 --> 00:41:14,010 Right. And it could happen. It can happen in podcasting, too. 639 00:41:14,370 --> 00:41:18,000 Like if, if the right people get involved and start doing what 640 00:41:18,000 --> 00:41:20,820 you know, the things that she's describing, and start 641 00:41:20,820 --> 00:41:26,790 transcribing everything. And then using using AI to tag 642 00:41:26,790 --> 00:41:30,450 certain things that interested parties think are 643 00:41:30,450 --> 00:41:34,320 misinformation, with no regard for down the line, whether they 644 00:41:34,320 --> 00:41:39,390 turn out to be true. That the things decentralization doesn't 645 00:41:39,390 --> 00:41:42,180 always protect you from the bad stuff because 646 00:41:42,180 --> 00:41:47,910 No, but open open source is, of course, always the answer. Which 647 00:41:47,940 --> 00:41:52,890 is, is simultaneously the problem because there's no easy 648 00:41:52,890 --> 00:41:58,020 money in open source, Enter value for value. You know, but 649 00:41:58,020 --> 00:42:00,750 that's, I don't want to get off in that and that course of the 650 00:42:00,750 --> 00:42:05,310 conversation, but there is not going to be one network where 651 00:42:05,310 --> 00:42:09,210 everybody communicates that will not be one. Even the idea of a 652 00:42:09,210 --> 00:42:13,200 global Town Square. Do you hear what you're saying? No, you have 653 00:42:13,200 --> 00:42:17,520 town squares. We have a small we have communities. No agenda is a 654 00:42:17,520 --> 00:42:20,430 perfect example. 10,000 people on the mastodon instance 655 00:42:20,460 --> 00:42:25,890 instance 2000 blocks from other instances, fine, but that's 656 00:42:25,890 --> 00:42:30,150 fine. It's okay. That's okay. That's how it should be. Which 657 00:42:30,150 --> 00:42:36,240 is again why I really hope I really I would love for twit who 658 00:42:36,240 --> 00:42:39,510 understand this very well. They've blocked no agenda twit 659 00:42:39,510 --> 00:42:43,620 dot social, they've blocked no agenda. That's fine. You know, 660 00:42:43,890 --> 00:42:48,000 grab these 2.0 features and build an app that is for your 661 00:42:48,000 --> 00:42:50,970 own little protected environment that is that you feel 662 00:42:50,970 --> 00:42:55,560 comfortable with that's that's the whole point. You can let in 663 00:42:55,560 --> 00:42:58,410 what you what your community your local community wants to 664 00:42:58,410 --> 00:43:01,560 let it's it's a federation it's like the federated you know, the 665 00:43:01,560 --> 00:43:06,270 United States is a is a republic of Federation, Texas will say no 666 00:43:06,270 --> 00:43:10,470 to some things. And you know, it can be convinced otherwise. And 667 00:43:10,470 --> 00:43:13,620 we often have to convince things from the inside out like this 668 00:43:13,620 --> 00:43:17,100 things that Texans don't agree with. And we have our own little 669 00:43:17,190 --> 00:43:20,550 our issues and battles, which can even be on the on the city 670 00:43:20,550 --> 00:43:24,810 level. That's a beautiful way this is the AI they're trying to 671 00:43:24,810 --> 00:43:28,890 shoehorn technology into the new world order global everything. 672 00:43:29,400 --> 00:43:33,330 That's the problem that thinking is just incorrect. It is 673 00:43:33,360 --> 00:43:36,810 unnatural. It is not how humans work. That's not how the world 674 00:43:36,810 --> 00:43:41,460 has ever worked. And thanks to the internet, they have a lot of 675 00:43:41,460 --> 00:43:45,480 ways to, to do they, I'll say have a lot of ways to do what 676 00:43:45,480 --> 00:43:50,220 they want, but you also just don't you just don't and I think 677 00:43:50,220 --> 00:43:52,980 that's fine. I don't know. Do you want to is that making any 678 00:43:52,980 --> 00:43:57,900 sense? Yeah, I think so. It'd be a bitching and moaning and build 679 00:43:57,900 --> 00:43:58,620 something 680 00:44:00,030 --> 00:44:05,100 that's a good point. That's a good point is the the well but 681 00:44:05,100 --> 00:44:08,820 you know that that really speaks to what the goal is the goal may 682 00:44:08,820 --> 00:44:11,430 not be the building the goal may be the bitching and moaning 683 00:44:11,580 --> 00:44:14,400 thank you and rang and because good point because the the 684 00:44:14,400 --> 00:44:18,780 bitching and moaning a lot of times is a is a 685 00:44:19,290 --> 00:44:22,020 those who can't build bitch that's what it is. 686 00:44:22,980 --> 00:44:27,810 The What was the reason data or whatever the reason for 687 00:44:27,810 --> 00:44:32,520 existence raison d'etre? Yeah that that's a lot of times they 688 00:44:32,910 --> 00:44:36,780 the griping or the pointing out of problems is the whole point 689 00:44:36,780 --> 00:44:40,530 and there is nothing that new that gets built or created that 690 00:44:40,620 --> 00:44:44,670 in I think all the pieces are in place to do everything to do 691 00:44:44,670 --> 00:44:49,260 everything that she has various that is proposed right 692 00:44:49,260 --> 00:44:51,780 but are these terrible but I don't even think it's nefarious. 693 00:44:51,810 --> 00:44:55,230 I think it'd be fantastic if people would make all to make 694 00:44:55,230 --> 00:44:59,610 your your payment stuff. Value for value is literally that if 695 00:44:59,610 --> 00:45:03,690 done in The false scope of value for value dot info where part of 696 00:45:03,690 --> 00:45:07,290 the feedback loop is recognizing and is showing what the value 697 00:45:07,290 --> 00:45:11,340 was that you sent back. There's your transparency transcript 698 00:45:11,370 --> 00:45:11,970 100. 699 00:45:13,380 --> 00:45:20,100 You can I get to offer you a fully about fully 700 00:45:20,520 --> 00:45:31,920 na just fully correct. utterly, utterly correct on the mark but 701 00:45:31,920 --> 00:45:35,880 yes, please more transcripts many, many more transcripts and 702 00:45:35,970 --> 00:45:41,250 even fit with chat GPT throw all Hey, if you go to mp3 dot no 703 00:45:41,250 --> 00:45:47,370 agenda notes.com. It's an open directory of every single mp3 I 704 00:45:47,370 --> 00:45:50,160 have created since that systems exists, which is quite a few, 705 00:45:50,310 --> 00:45:54,900 but also all the s dot SRT files, throw it in your AI, 706 00:45:55,410 --> 00:45:59,400 throw it in there, find stuff, block it, whatever. The fact is, 707 00:45:59,430 --> 00:46:01,500 you can throw it in, you can also say I want to find 708 00:46:01,500 --> 00:46:03,990 something and someone else could build something I want to find 709 00:46:03,990 --> 00:46:09,000 something specifically. Um, this is what I'm for. So I don't care 710 00:46:09,000 --> 00:46:13,710 that that she wants to that she wants to use all these things we 711 00:46:13,710 --> 00:46:18,540 have developed for what I think are awful things. But I wish you 712 00:46:18,540 --> 00:46:21,780 would get someone to do it already. Brookings must have 713 00:46:21,810 --> 00:46:26,550 $100 million build something it helps everybody 714 00:46:26,819 --> 00:46:29,879 gotta be more than that. They got bet you they get it they get 715 00:46:29,879 --> 00:46:34,649 tons of money. That I think there's a there's a naivety 716 00:46:35,610 --> 00:46:39,450 another French word, named Benjamin will be so proud of you 717 00:46:40,050 --> 00:46:42,390 read on Datron every day what else? 718 00:46:43,110 --> 00:46:44,550 I'm reading the Shaka Zulu. 719 00:46:45,600 --> 00:46:47,520 Now I know I'm reading Jacques Cousteau. 720 00:46:50,520 --> 00:46:55,080 So I think there's a sort of naivete of amongst I don't know 721 00:46:55,080 --> 00:47:00,270 how old you know, Victoria is but she's, she seems young. You 722 00:47:00,270 --> 00:47:02,940 seem very young from the picture. Yeah. Yeah. And so I'm 723 00:47:02,940 --> 00:47:08,910 thinking that there is just a naivety of whatever. There's 724 00:47:08,910 --> 00:47:12,300 naivety of trust in the establishment. And, and I'm 725 00:47:12,300 --> 00:47:15,630 going to say that, you know, people who are old enough to 726 00:47:15,630 --> 00:47:17,430 remember, you don't even have 727 00:47:17,790 --> 00:47:21,360 I'm sorry, I'm sorry. I just looked at Brookings Institution, 728 00:47:21,360 --> 00:47:27,750 their form 990 $195 million. In the last year they brought in, 729 00:47:28,020 --> 00:47:33,660 they have $568 million in assets. Build something. 730 00:47:34,020 --> 00:47:37,500 Give them a boost. Booster grant, like, 731 00:47:39,570 --> 00:47:42,750 come on big. Boost us. Exactly. 732 00:47:43,710 --> 00:47:46,380 But I'm thinking that you don't I mean, you don't have to be old 733 00:47:46,380 --> 00:47:50,130 enough to go back to like Gulf of Tonkin level this new 734 00:47:50,130 --> 00:47:53,100 government field misinformation. Another good one, you can just 735 00:47:53,100 --> 00:47:58,110 go back, you can just go back to something as recent as Syrian 736 00:47:58,110 --> 00:47:59,430 gas attacks or 737 00:47:59,430 --> 00:48:02,670 Yeah, the white The White Helmets anything? Yeah. Or or 738 00:48:03,840 --> 00:48:07,680 Biden laptop? Russian disinformation? 739 00:48:08,100 --> 00:48:11,280 Or if you want to go back to something just that's that's 740 00:48:11,310 --> 00:48:16,740 super uncontroversial about the lack of WMDs in Iraq? I mean, 741 00:48:16,740 --> 00:48:17,070 yeah, 742 00:48:17,100 --> 00:48:18,240 yeah, exactly. 743 00:48:18,240 --> 00:48:25,110 There's so aluminum tubes. Do you think for one second, that 744 00:48:25,110 --> 00:48:30,720 if that if the State Department under George Bush had access to 745 00:48:30,720 --> 00:48:34,950 some sort of system, that would, they could instantly send out a 746 00:48:34,950 --> 00:48:41,490 bat signal to flag all the podcasts that were created? They 747 00:48:41,490 --> 00:48:45,180 were critical of the idea that there were WMDs in Iraq? Do you 748 00:48:45,180 --> 00:48:48,000 think that they would have hesitated for one second to do 749 00:48:48,000 --> 00:48:51,750 that? Of course, they would have done it. And it was completely 750 00:48:51,750 --> 00:48:57,420 bogus and untrue. But that's, that's if you build this, this 751 00:48:57,420 --> 00:49:02,100 is what I've tried to say over and over and over it the the 752 00:49:02,100 --> 00:49:06,030 Terrible idea in this The unfortunate thing in this 753 00:49:06,030 --> 00:49:08,850 country in the United States, what I'm talking about is every 754 00:49:09,240 --> 00:49:15,210 every every year, but the left, right, bull crap, it let it it 755 00:49:15,210 --> 00:49:20,610 is so it ends up pushing things forward, that is in nobody's 756 00:49:20,610 --> 00:49:24,360 interest. And so it's like well, my guys are in charge right now. 757 00:49:24,360 --> 00:49:28,830 So I'm gonna get try to silence all the other guys. And you end 758 00:49:28,830 --> 00:49:32,970 up building a system to where when the power flip you get 759 00:49:32,970 --> 00:49:34,500 screwed by the thing you build, 760 00:49:34,530 --> 00:49:37,620 but that's, that's only with centralized systems. So I really 761 00:49:37,620 --> 00:49:41,940 am advocating and I will contact her if possible, I say Would you 762 00:49:41,940 --> 00:49:45,000 please let me give you a little tour of what is possible 763 00:49:45,000 --> 00:49:48,030 everything permanent everything she says on the list is 764 00:49:48,030 --> 00:49:50,340 possible. And I welcome it. 765 00:49:50,640 --> 00:49:51,870 I really meeting you're gonna, 766 00:49:52,140 --> 00:49:56,220 I'm gonna, I'm gonna. Yes, we're gonna pump the brakes and have a 767 00:49:56,220 --> 00:50:01,320 Zoom meeting. I am all I really am Ford. put some money into 768 00:50:01,320 --> 00:50:05,580 this thing and use it how you find appropriate. That's totally 769 00:50:05,580 --> 00:50:06,330 cool. 770 00:50:07,589 --> 00:50:11,309 You can build that I would use that dashboard. Um, yeah, I 771 00:50:11,309 --> 00:50:12,629 mean, I was searched up for 772 00:50:12,660 --> 00:50:16,260 Yeah, but I mean predetermine whatever you want to do, that 773 00:50:16,260 --> 00:50:20,250 it's all good. And then when it flips around, then you can flip 774 00:50:20,250 --> 00:50:24,510 your system around. There's what is not possible, it's not 775 00:50:24,510 --> 00:50:27,420 possible to build this for everybody. And that is because 776 00:50:27,420 --> 00:50:31,800 of the unfortunate nature of RSS. And the unfortunate nature 777 00:50:31,830 --> 00:50:35,640 nature of a richly diversified hosting environment, which 778 00:50:35,640 --> 00:50:40,350 includes IPFS. So that genies out of the bottle, but if you 779 00:50:40,350 --> 00:50:43,560 feel that you need to protect the vulnerable people, then 780 00:50:43,560 --> 00:50:49,410 please stop writing and wasting your $195 million a year and 781 00:50:49,410 --> 00:50:52,110 come over here and put some money into the ecosystem and 782 00:50:52,110 --> 00:50:57,150 build something. I mean, I'm extending my hand here. 783 00:50:58,680 --> 00:51:00,510 You open palm open palm. 784 00:51:02,880 --> 00:51:06,060 Anyway, quite enough of that, I believe. Let's talk about 785 00:51:06,060 --> 00:51:11,250 subscriptions. Because I know I've been keeping my eye on what 786 00:51:11,250 --> 00:51:15,750 Buzzsprout did. Because as you know, I have a vested interest 787 00:51:15,750 --> 00:51:20,910 in moving away from PayPal on no agenda. Just because it's a very 788 00:51:20,910 --> 00:51:25,770 weak link in the chain. We are we do have a lightning node. And 789 00:51:25,770 --> 00:51:29,070 as soon as the lightning and this was from Ibex that it 790 00:51:29,070 --> 00:51:32,550 already works. The way we want it to be it's a great solution 791 00:51:32,550 --> 00:51:36,150 for people if you want to accept open donations, or you can even 792 00:51:36,150 --> 00:51:37,500 set a preset amount. 793 00:51:37,800 --> 00:51:41,010 Wait, wait, wait, wait, wait, pause, stop. Are you saying that 794 00:51:41,010 --> 00:51:43,590 you're back stuff is up and running now as functional? 795 00:51:44,430 --> 00:51:45,090 rolled it out? 796 00:51:45,210 --> 00:51:50,100 We have not, we have not promoted it yet. And the reason 797 00:51:50,130 --> 00:51:56,040 why is because I would prefer it to also accept key send and it 798 00:51:56,040 --> 00:51:59,760 doesn't accept key send yet, I want people to also be able to 799 00:51:59,760 --> 00:52:04,170 use the 2.0 app. So this is the shoehorn I'm using against Ibex 800 00:52:04,920 --> 00:52:07,680 is like you know, because we'll bring him on this show, we'll 801 00:52:07,680 --> 00:52:09,930 promote him anything you want. We'll talk about it, I know 802 00:52:09,930 --> 00:52:12,570 agenda, we'll get other podcasters to use it. But you 803 00:52:12,570 --> 00:52:15,120 got to have key send enabled so that I can receive booster 804 00:52:15,120 --> 00:52:19,770 grams, then they're having, I don't know, development is slow. 805 00:52:19,770 --> 00:52:25,440 And I respect that it's okay. But my point is, we need other 806 00:52:25,440 --> 00:52:32,520 systems for value for value. Now. PayPal is of course, you 807 00:52:32,520 --> 00:52:36,270 can do an open PayPal like we have here as well open PayPal 808 00:52:36,300 --> 00:52:39,420 donation, you can put your note in there, which is also become a 809 00:52:39,420 --> 00:52:42,420 problem because PayPal shortened the field that you can put a 810 00:52:42,420 --> 00:52:45,150 note in, which is very annoying, and we have no control over 811 00:52:45,150 --> 00:52:46,890 that. How long is it Dino? 812 00:52:46,950 --> 00:52:51,210 Si? It's like 150 characters is not even a tweet length. It's 813 00:52:51,240 --> 00:52:51,510 it's 814 00:52:51,900 --> 00:52:54,330 George Graham is longer than that. Exactly. 815 00:52:56,400 --> 00:53:00,330 But it's very rare. That is not really many. And please don't 816 00:53:00,330 --> 00:53:05,760 email me. There are not many easy systems comparable to pay 817 00:53:05,760 --> 00:53:09,570 pal subscription that you can set up your subscription. Some 818 00:53:09,570 --> 00:53:15,540 people do build it yourself. Right. And so and I'm very 819 00:53:15,540 --> 00:53:19,530 intrigued by what Buzzsprout has done because it links right into 820 00:53:20,280 --> 00:53:27,360 I think Apple Pay and and Google and Google's pay system. Now 821 00:53:28,290 --> 00:53:32,850 what I'm still not exactly, I can't I don't think I can 822 00:53:32,880 --> 00:53:38,700 explain or push a 15% fee through to my podcast partner, 823 00:53:38,760 --> 00:53:41,490 even though I'm told that it's comparable to everything else, 824 00:53:41,520 --> 00:53:45,420 it may be comparable to we're better than Patreon but I don't 825 00:53:45,420 --> 00:53:50,040 see how it can be lower than than PayPal. But regardless, I 826 00:53:50,040 --> 00:53:53,970 would love to have an open system that we can put into 827 00:53:53,970 --> 00:53:58,890 podcasting 2.0 apps, it can use any back end system and I have 828 00:53:58,890 --> 00:54:03,420 two requirements for it to be value for value. One is it can 829 00:54:03,420 --> 00:54:08,670 be it can the amount has to be open you know some people want 830 00:54:08,670 --> 00:54:11,700 to send it now. When people send the dollar we actually lose 831 00:54:11,700 --> 00:54:14,370 money on it. I mean that's that's that's almost run it as 832 00:54:14,370 --> 00:54:17,340 almost rude. But it's okay. If that's what you want to do. 833 00:54:17,340 --> 00:54:21,180 That's what you want to do. I want to be Bitcoin I want to be 834 00:54:21,180 --> 00:54:26,190 anything that that we choose it to be, it has to be open. And in 835 00:54:26,220 --> 00:54:31,410 in the case of my vision, my vision for podcasting value for 836 00:54:31,410 --> 00:54:38,340 value. I would like to split to be honored in this because that 837 00:54:38,340 --> 00:54:42,750 is that is truly something that is unique to our version in 838 00:54:42,750 --> 00:54:45,960 podcasting. 2.0 of value for value is the splits can flow 839 00:54:45,960 --> 00:54:51,060 through because I feel if we if we go a subscription amount 840 00:54:51,060 --> 00:54:54,750 route and leave the app developers out of the system, 841 00:54:54,780 --> 00:54:58,230 then we've then we've made a mistake. And currently you know 842 00:54:58,230 --> 00:55:02,820 there's no subscription system that, that can value a split 843 00:55:02,850 --> 00:55:06,510 architecture, where the podcast can determine what can go to 844 00:55:06,510 --> 00:55:10,230 other people now, that may not work with, with Fiat fun coupons 845 00:55:10,230 --> 00:55:14,100 and dollars. But if we implement a subscription system into 846 00:55:14,340 --> 00:55:18,870 podcasting 2.0, you will be really, really, really beautiful 847 00:55:18,870 --> 00:55:22,440 to take into account a version of the splits, which we already 848 00:55:22,440 --> 00:55:25,950 have, that can be incorporated. And I know that you've been 849 00:55:25,950 --> 00:55:29,250 talking to people about doing exactly this. 850 00:55:30,420 --> 00:55:33,240 Yeah, and we're in we're gonna have, we're gonna have Tom on 851 00:55:33,240 --> 00:55:37,860 the show soon. As soon as we've got Tom from Buzzsprout. Yeah, 852 00:55:37,860 --> 00:55:41,610 yes, for Buzzsprout. Because, you know, their, their vision is 853 00:55:41,610 --> 00:55:45,810 to have that be, you know, something that is standard, 854 00:55:45,900 --> 00:55:51,210 standard Eisele that could become open. So that they, I 855 00:55:51,240 --> 00:55:55,170 think, yes, I think and we, me and him, talked about it this 856 00:55:55,170 --> 00:55:59,940 week, and hashed out a bunch of ideas. And it was a great, great 857 00:55:59,940 --> 00:56:02,280 discussion. So he's gonna come on, and we're gonna, like, just 858 00:56:02,280 --> 00:56:05,850 brainstorm about it on the board meeting, sit here soon, and try 859 00:56:05,850 --> 00:56:09,270 to see if we can, you know, sort of come up with a with a 860 00:56:09,270 --> 00:56:14,100 framework or an open an open way to do this, where that where 861 00:56:14,100 --> 00:56:17,370 basically what they built can just become sort of a standard 862 00:56:17,370 --> 00:56:20,910 that everybody can can adopt. And I think after talking to 863 00:56:20,910 --> 00:56:23,370 him, the other, I think it's very doable. And I think it 864 00:56:23,370 --> 00:56:28,230 would be very, I think it's, I think there's a way to do it, 865 00:56:29,130 --> 00:56:37,350 where the apps where the apps don't have to, again, re 866 00:56:37,350 --> 00:56:42,780 architect some new thing, look, so the way that they're, you 867 00:56:42,780 --> 00:56:48,810 know, the way their system works, and I did this on the Pod 868 00:56:48,810 --> 00:56:53,070 news weekly review show. So I opened up my cast thematic, I 869 00:56:53,070 --> 00:56:57,510 hit the the funding button, which on cast Matic is down 870 00:56:57,510 --> 00:57:00,390 there toward the bottom on the right. So if you have a funding 871 00:57:00,390 --> 00:57:03,330 tag in your feed, and you hit the button, it'll pop up a web 872 00:57:03,330 --> 00:57:08,460 view that goes to whatever the funding page is. And so since 873 00:57:09,000 --> 00:57:13,800 James and Sam had their their subscriptions, set up the other 874 00:57:13,800 --> 00:57:18,720 Buzzsprout subscription page, in the funding tag, it opened. So 875 00:57:18,720 --> 00:57:23,190 it opened in a WebView in the app. And right there said, Oh, 876 00:57:23,190 --> 00:57:26,970 do you want to know do you want to subscribe? And what level 877 00:57:26,970 --> 00:57:30,090 like 357 10 bucks whatever, Daddy's some options, that's 878 00:57:30,090 --> 00:57:31,140 a problem there? Yeah, 879 00:57:31,230 --> 00:57:34,740 it is. It is. It is. So but I'm just I'm just talking through 880 00:57:34,740 --> 00:57:41,040 the experience. Sure. I go down, I choose the $10. And I hit a 881 00:57:41,040 --> 00:57:44,370 hit subscribe, and it comes up. So you want to do Apple Pay, or 882 00:57:44,370 --> 00:57:46,260 do you want to do a credit card or whatever I hit Apple Pay, 883 00:57:46,260 --> 00:57:50,550 because I've already got this set up. Hit it. Face ID me done. 884 00:57:51,210 --> 00:57:56,880 Back Back to in and then I hit I hit OK. I'm back in the in the 885 00:57:57,930 --> 00:58:01,470 in cast thematic. I never actually left cast semantics. 886 00:58:01,500 --> 00:58:03,060 Right. Right. Which is the whole point. 887 00:58:03,210 --> 00:58:07,620 That's the whole point. Yeah. So yeah. So in honest and so the 888 00:58:07,620 --> 00:58:14,370 web nature of this thing is the only way that I see that this 889 00:58:14,370 --> 00:58:15,360 could work. 890 00:58:16,259 --> 00:58:18,989 I'm if I can just interrupt. I'm just looking at that. We said 891 00:58:18,989 --> 00:58:26,159 just now I see a choose a fan emoji. Where's my notes go? I 892 00:58:26,159 --> 00:58:31,019 don't just mean I don't see a note in this Buzzsprout thing. I 893 00:58:31,019 --> 00:58:35,159 did what you just described on pod news weekly review. It opens 894 00:58:35,159 --> 00:58:39,839 up to support to become a supporter 358 $10 Choose a fan 895 00:58:39,839 --> 00:58:44,219 emoji name, email, then my credit card. We're missing an 896 00:58:44,219 --> 00:58:49,259 important part here, which is no, not incredibly important. So 897 00:58:49,259 --> 00:58:51,629 I just want to and the only reason I'm saying this is 898 00:58:51,629 --> 00:58:55,529 because the more I can develop this over 15 years we know what 899 00:58:55,529 --> 00:58:57,719 works we know what doesn't work, we know what's needed. 900 00:58:58,650 --> 00:59:03,300 So the end again, like so we're gonna have Tom also will talk 901 00:59:03,300 --> 00:59:07,020 about this more more with him. But I think I think that this is 902 00:59:07,020 --> 00:59:10,230 my feeling he Tom did not tell me this, but this is my feeling. 903 00:59:11,100 --> 00:59:19,380 Is they? Is that what you see right now? Was that not an MVP? 904 00:59:19,380 --> 00:59:23,250 Not not not a minimum product. But that was the thing that they 905 00:59:23,250 --> 00:59:27,630 could? Did. They felt confident in, in order to make it where 906 00:59:27,630 --> 00:59:32,220 things did not go south. Because if you if you come out of the 907 00:59:32,220 --> 00:59:35,580 gate and you enter and you put in something like an empty box 908 00:59:35,580 --> 00:59:37,920 where somebody can type their own amount, right? You 909 00:59:37,920 --> 00:59:40,380 immediately have support problems because you have people 910 00:59:40,380 --> 00:59:44,790 that accidentally typed $2,000 And they're like, Oh crap, I 911 00:59:44,790 --> 00:59:48,000 need to I need to roll that back. What do I do? Like, I 912 00:59:48,000 --> 00:59:52,320 think the incarnation that it is right now it was probably the 913 00:59:52,320 --> 00:59:55,530 safe launch technique. 914 00:59:55,590 --> 00:59:59,970 Oh, yeah. No, go for a lot of things incredibly hard. This guy 915 01:00:00,000 --> 01:00:04,710 This stuff. Absolutely. We saw Pay Pal struggle enormously. And 916 01:00:06,180 --> 01:00:08,400 I could just tell you where this leads, which is why I like 917 01:00:08,400 --> 01:00:11,640 lightning, which is why I want this implemented in lightning as 918 01:00:11,640 --> 01:00:18,450 well. On PayPal all the time, we get people say, hey, you know, 919 01:00:18,450 --> 01:00:22,170 all of a sudden, my payment is under review. I mean, you have 920 01:00:22,170 --> 01:00:26,070 to do know your customer, you have to do all kinds of stuff to 921 01:00:26,070 --> 01:00:29,700 terrorism financing. When someone does it from overseas, 922 01:00:29,700 --> 01:00:34,110 you get all kinds of issues all this it's a very, it's a hard 923 01:00:34,110 --> 01:00:39,120 business to be in, in the Fiat subscription business is very, 924 01:00:39,120 --> 01:00:42,990 very hard. And kudos to them for doing it at all. 925 01:00:44,040 --> 01:00:48,750 But I think so when we can, we can nail so we can sort of so 926 01:00:48,750 --> 01:00:51,990 nail down a framework when it comes on. But I think my take 927 01:00:51,990 --> 01:00:58,740 away from from our discussion was that it's very, it's it's 928 01:00:58,740 --> 01:01:03,180 not only doable, but I think it's doable in a great way that 929 01:01:03,180 --> 01:01:05,880 keeps the apps from getting in trouble with any app store 930 01:01:05,880 --> 01:01:09,480 policies or anything like that. Like I think I think this could 931 01:01:09,480 --> 01:01:13,740 be a really good thing. So anyway, I think I think it's 932 01:01:13,740 --> 01:01:14,700 great. Yeah. 933 01:01:15,150 --> 01:01:19,020 Well, unfortunately, I see a bleak future for any payment 934 01:01:19,020 --> 01:01:22,500 systems in any app store. Just in general. Yeah. 935 01:01:22,920 --> 01:01:27,150 Well, um, so what I mean by that is, when you when you open up a 936 01:01:27,150 --> 01:01:33,120 web view, the way the bad the app stores, force the apps is 937 01:01:33,120 --> 01:01:37,440 they can't take payments in the app through they can't sell 938 01:01:37,440 --> 01:01:40,320 things in the ad, I understand. It has to it has to open a web 939 01:01:40,320 --> 01:01:43,050 browser, it has to open a web browser in this does, you know, 940 01:01:43,050 --> 01:01:44,880 like this is a web based transaction. 941 01:01:44,940 --> 01:01:47,910 But you know, that's a very simple policy change to make. 942 01:01:48,450 --> 01:01:51,570 It is yeah, so what we'll see what happens that I don't know 943 01:01:51,570 --> 01:01:54,660 that they're willing, I don't know that the app stores are 944 01:01:54,660 --> 01:01:58,050 willing to go to the mat or something like that. Now with 945 01:01:58,050 --> 01:01:59,730 the current political climate as it is. 946 01:02:01,200 --> 01:02:04,260 It's a foregone conclusion in my mind. I mean, the app stores 947 01:02:04,290 --> 01:02:08,640 aren't are evil. They're evil. And the story artists are under 948 01:02:08,640 --> 01:02:12,510 a lot of scrutiny. Yeah, well, then they should allow 949 01:02:12,990 --> 01:02:15,330 Progressive Web Apps Apple should allow it to be done 950 01:02:15,330 --> 01:02:18,240 properly, but they won't because they're evil. Ultimately, 951 01:02:18,240 --> 01:02:20,850 they're greedy and evil. And they the that's the master they 952 01:02:20,850 --> 01:02:23,250 serve and that's okay. But let's not 953 01:02:23,819 --> 01:02:29,699 Mammon. Yes. What? Mammon? Yes, mammon, money. This, like the 954 01:02:29,699 --> 01:02:33,809 old biblical term for money is mammon, Ma. What are their 955 01:02:33,809 --> 01:02:37,289 master? Yeah, they serve their master mammon, wealth regarded 956 01:02:37,289 --> 01:02:40,019 as an evil influence or false object of worship and devotion. 957 01:02:40,110 --> 01:02:47,490 Well, it is. And but then that's okay. It's just let I always get 958 01:02:47,490 --> 01:02:50,220 so sad when I see people trying to get around exactly this 959 01:02:50,220 --> 01:02:53,610 problem, says all all Apple has to do is if they don't feel like 960 01:02:53,610 --> 01:02:57,030 it today, or Google, and you're seeing as Google is, by the way, 961 01:02:57,450 --> 01:03:01,380 did I not say that this is a quagmire? It's a piece of crap. 962 01:03:01,380 --> 01:03:03,870 And it's a big mistake this whole chat GPT just see what 963 01:03:03,870 --> 01:03:04,800 happened to Google. 964 01:03:05,609 --> 01:03:08,999 And I heard something about there was a fail on launch or 965 01:03:08,999 --> 01:03:11,279 something that I'd never saw. So first of all details, 966 01:03:11,400 --> 01:03:17,130 they named it that they named their chat bot, barf. bar, bar, 967 01:03:17,490 --> 01:03:23,040 bar bar, okay, bar, but we just call it Google barf. And, and 968 01:03:23,040 --> 01:03:26,310 the first the first question that was asked, gave an 969 01:03:26,310 --> 01:03:33,240 incorrect answer, the stock price drops 9% 9%. And it's in 970 01:03:33,240 --> 01:03:36,420 his boat there. Now the now they're fighting over book, 971 01:03:36,450 --> 01:03:41,190 every engineer knows that what is happening here is not really 972 01:03:41,190 --> 01:03:46,260 spectacular. It's a it's a parlor trick. I mean, it 973 01:03:46,260 --> 01:03:48,510 especially if it can't even get the answers, right, which is 974 01:03:48,510 --> 01:03:51,870 always going to be subjective. That's why you win a search, you 975 01:03:51,870 --> 01:03:55,860 get a list of links. Well, here's what most people clicked 976 01:03:55,860 --> 01:03:59,280 on. Okay. But now you have something coming back and 977 01:03:59,280 --> 01:04:01,530 saying, Well, I think this is what's happening. This is the 978 01:04:01,530 --> 01:04:05,340 answer to your question. Well, that's gonna be wrong. Lots of 979 01:04:05,340 --> 01:04:08,280 times. You know what I mean? 980 01:04:08,670 --> 01:04:14,280 Yeah, if you if you take, that could be a way too. That can be 981 01:04:14,280 --> 01:04:19,680 the ultimate cya. If you think about it, like, if you just if 982 01:04:19,680 --> 01:04:23,790 you change your algorithm to just to just generate an answer 983 01:04:23,790 --> 01:04:28,410 based on on a quote model was like, Oh, I'm sorry. We just 984 01:04:28,410 --> 01:04:31,290 need to tweak the model. Yeah. And I know it's giving you wrong 985 01:04:31,290 --> 01:04:33,900 information, but we just need to tweak the models. It's going to 986 01:04:33,930 --> 01:04:37,020 destroy these getting killed. Oh, we just need to tweak the 987 01:04:37,020 --> 01:04:37,470 model. 988 01:04:37,530 --> 01:04:41,340 I mean, it's going it's the demise of Google because they 989 01:04:41,340 --> 01:04:45,030 now are running after something that they know they know. And 990 01:04:45,060 --> 01:04:48,480 Sundar Pichai. He's not a marketing guy. He's a nerd. He's 991 01:04:48,480 --> 01:04:52,020 a technology guy. He knows what real AI looks like real machine 992 01:04:52,020 --> 01:04:55,740 learning, and it's not really anything even appropriate for 993 01:04:55,740 --> 01:05:00,660 consumers. So this parlor trick of taking the Some economists 994 01:05:00,690 --> 01:05:05,040 asked Jeeves only you know, they they improved it great. Well, 995 01:05:05,100 --> 01:05:08,100 you get, you're getting a real world answer by something that 996 01:05:08,100 --> 01:05:10,590 pretends to be a human being, and everyone is just going to 997 01:05:10,590 --> 01:05:13,860 fall for this, but it's not going to deliver the profits to 998 01:05:13,860 --> 01:05:17,820 them. And Microsoft is going to be interesting, because they 999 01:05:17,820 --> 01:05:20,430 want to put this into all of their products. So you know, you 1000 01:05:20,430 --> 01:05:23,760 open up Word, and you just say, type and apology letter, you 1001 01:05:23,760 --> 01:05:26,310 know, type of resume, and it'll just start to get it all going 1002 01:05:26,310 --> 01:05:30,240 for you. And everyone will be kind of the same NPC non playing 1003 01:05:30,240 --> 01:05:33,600 character drone, and you'll have all the same answers and all the 1004 01:05:33,600 --> 01:05:36,450 same information will be no, and the people that will stand out, 1005 01:05:36,450 --> 01:05:38,670 we'll be the ones that that are odd. 1006 01:05:39,360 --> 01:05:42,930 So I don't know about you. I don't know if you've had any 1007 01:05:43,020 --> 01:05:47,820 experience with this. But it's become popular now within 1008 01:05:47,820 --> 01:05:51,150 Outlook and Gmail and all these different email clients to it, 1009 01:05:51,150 --> 01:05:54,600 when you begin to type a reply. It'll want to like, auto 1010 01:05:54,600 --> 01:05:55,950 complete your reply for you. 1011 01:05:56,010 --> 01:05:59,070 I don't usually say I don't have any of it. Okay, well, 1012 01:05:59,070 --> 01:06:02,310 it's very common now. So you'll, you'll start to say, somebody 1013 01:06:02,310 --> 01:06:06,000 else send you a thing and say, Hey, can you go can you get this 1014 01:06:06,000 --> 01:06:09,060 information from me? And you say, and you start to reply. 1015 01:06:10,710 --> 01:06:13,710 Yeah, I'm in the middle of something right now. And maybe 1016 01:06:13,740 --> 01:06:18,990 it'll suggest to you that you autocomplete it with, but I'll 1017 01:06:18,990 --> 01:06:20,250 get to that here in a few minutes. 1018 01:06:20,280 --> 01:06:23,010 Okay. Yeah, that makes sense. Of course, of course, of course. 1019 01:06:23,070 --> 01:06:26,850 So that's, so that's this, like, if you take that to the next 1020 01:06:26,850 --> 01:06:30,240 level, and have it auto generate an entire email to you, that 1021 01:06:30,240 --> 01:06:33,810 would be sort of like this, this sort of model. But the way that 1022 01:06:33,810 --> 01:06:38,670 I, what I've begun doing is in this sort of, like subconscious 1023 01:06:38,670 --> 01:06:44,700 at the beginning, I would get these suggestions, of replies. 1024 01:06:45,210 --> 01:06:47,970 And I would immediately see, I would see this gesture of green, 1025 01:06:47,970 --> 01:06:50,250 you see that it's filled with this gentleman, I would say 1026 01:06:50,280 --> 01:06:53,640 Yeah, and I would, I would reject it. Because even though 1027 01:06:53,640 --> 01:06:57,630 it's what I was about to say, I don't want the other person to 1028 01:06:57,630 --> 01:07:00,810 think that I just hit a button and didn't actually think about 1029 01:07:00,810 --> 01:07:03,750 what I was saying. Like, I don't want to give them a canned 1030 01:07:03,750 --> 01:07:07,920 response. Because I don't want it to appear rude or is right 1031 01:07:07,920 --> 01:07:08,190 here. 1032 01:07:08,220 --> 01:07:12,360 This started with. I'm driving right now. I'll call you later. 1033 01:07:12,720 --> 01:07:15,690 Yeah, that means like, why don't why don't you just turn your 1034 01:07:15,690 --> 01:07:20,250 phone off them? You know, right? Or ever hear of hands free? 1035 01:07:20,790 --> 01:07:26,400 Bluetooth? And yeah, perfect example. Anyway, a long, long, 1036 01:07:26,430 --> 01:07:30,030 long arc around all that. Let's go to social interact API 1037 01:07:30,030 --> 01:07:31,800 endpoint. Very excited about this. 1038 01:07:32,220 --> 01:07:33,030 Yes, it is. 1039 01:07:34,980 --> 01:07:37,560 Now, why did you build this? And what's the idea? And what is it 1040 01:07:37,560 --> 01:07:39,390 because it seems like something dynamite 1041 01:07:40,170 --> 01:07:44,730 Well, a built it. Well built is a little bit, not the right 1042 01:07:44,730 --> 01:07:45,420 term. You built 1043 01:07:45,420 --> 01:07:48,870 it. I invented podcasts, you built the API, trust me, it's 1044 01:07:48,870 --> 01:07:50,340 the same thing. Okay. 1045 01:07:51,840 --> 01:07:57,480 So social interact wasn't in the API response. It just wasn't 1046 01:07:57,480 --> 01:08:00,060 there. So it needed to be there to begin with. They just 1047 01:08:00,510 --> 01:08:02,700 interested missing is just a fee. It's just a tag that had 1048 01:08:02,700 --> 01:08:09,780 not gotten around to yet. And it needed to be there. So and there 1049 01:08:09,780 --> 01:08:12,720 was nothing in the whole chain there was no it was not being 1050 01:08:12,720 --> 01:08:14,100 aggregated. It was not being 1051 01:08:16,350 --> 01:08:18,840 someone's feed if it's in there, and it's not he wasn't even in 1052 01:08:18,840 --> 01:08:19,590 the database. 1053 01:08:20,220 --> 01:08:23,340 Yet. Nothing. No, no, I didn't know that. None of that. Oh, 1054 01:08:23,340 --> 01:08:25,620 wow. So so I had no words 1055 01:08:25,620 --> 01:08:30,090 here. No one No wonder this wasn't off the ground yet. Now, 1056 01:08:30,090 --> 01:08:32,850 I understand the problem. I seriously, I didn't know that. I 1057 01:08:32,850 --> 01:08:36,660 didn't know that the root post was not no not your fault. No, I 1058 01:08:36,660 --> 01:08:39,240 didn't know that. I would have gone easier on everybody. I 1059 01:08:39,240 --> 01:08:42,000 didn't know what the root post wasn't available in the API. 1060 01:08:43,920 --> 01:08:45,000 Pardon me Ah, 1061 01:08:46,080 --> 01:08:51,090 well, I did I so I had to go and put it into party time. So that 1062 01:08:51,090 --> 01:08:56,880 would go get aggregated in then build the tables. And this just 1063 01:08:56,880 --> 01:08:59,340 kind of goes into something else we can talk about to the brain 1064 01:08:59,340 --> 01:09:06,870 which is no no no, which is deleting old episodes, when they 1065 01:09:06,870 --> 01:09:08,490 appeared. When they do 1066 01:09:08,489 --> 01:09:11,249 yes, I have this on my list too. So you can explain that to 1067 01:09:11,249 --> 01:09:13,859 everybody how easy it is, 1068 01:09:14,070 --> 01:09:22,080 we can do a mash up here. Alright. So the way that the 1069 01:09:22,080 --> 01:09:26,040 table the table structure in the database is for the API is for 1070 01:09:26,040 --> 01:09:31,920 the index is we have we have a news feeds table. And this 1071 01:09:31,920 --> 01:09:35,820 terminology this terminology came from the initial scheme it 1072 01:09:35,820 --> 01:09:39,450 came from Freedom controller so some of these terminologies I 1073 01:09:39,450 --> 01:09:39,780 loved 1074 01:09:39,780 --> 01:09:41,730 I loved that there's legacy and there is beauty. 1075 01:09:44,730 --> 01:09:51,990 So the podcasts table is called newsfeeds. The episodes table is 1076 01:09:51,990 --> 01:09:58,170 called items, for obvious reasons. So excuse me, NF items 1077 01:09:58,200 --> 01:10:05,130 is called NF items. So The newsfeeds table has a foreign 1078 01:10:05,130 --> 01:10:10,620 key relationship with the NF Items table. So the NF Items 1079 01:10:10,620 --> 01:10:18,180 table references the news, the N ID in the news feeds table. And 1080 01:10:18,180 --> 01:10:21,210 then, so that there's linkage between the two, there's a 1081 01:10:21,210 --> 01:10:22,470 relationship episode 1082 01:10:22,470 --> 01:10:25,740 and the and the fetus and the podcast itself, right. 1083 01:10:25,800 --> 01:10:31,020 And then a whole lot of tables hang off of each one of those. 1084 01:10:31,290 --> 01:10:37,350 So there's a thing called NF NF underscore value. Well, those 1085 01:10:37,440 --> 01:10:41,160 are, those are the value blocks. And they have a foreign key 1086 01:10:41,160 --> 01:10:43,980 relationship, that table, the NF underscore value has a foreign 1087 01:10:43,980 --> 01:10:47,850 key relationship with the news feed stable, so that we can so 1088 01:10:47,850 --> 01:10:52,260 that we can pull a news feed, and then also do a join in the 1089 01:10:52,260 --> 01:10:55,650 SQL in order to get the value blocks, but the value blocks 1090 01:10:55,650 --> 01:11:00,180 themselves are stored in a different table. These sorts of 1091 01:11:00,180 --> 01:11:05,550 table relationships are important, because you can you 1092 01:11:05,550 --> 01:11:09,060 can separate you can have a same schema and separate concerns. 1093 01:11:09,630 --> 01:11:13,080 And you can also update various bits of data in different tables 1094 01:11:13,410 --> 01:11:16,620 without necessarily locking, locking tables in the other. 1095 01:11:16,620 --> 01:11:16,890 Could 1096 01:11:16,890 --> 01:11:22,710 you explain just so I I've heard this term, first of all, having 1097 01:11:22,830 --> 01:11:28,710 run some companies and worked with DBAs, database, design 1098 01:11:28,710 --> 01:11:38,460 management, coaxing massaging it is as much voodoo and magic and 1099 01:11:38,490 --> 01:11:42,330 experience and maybe even religion as it is technology is 1100 01:11:42,330 --> 01:11:47,670 my experience. Yes, and yes, yes. But you can do things 1101 01:11:47,670 --> 01:11:51,060 exactly the same in one database will behave differently from the 1102 01:11:51,060 --> 01:11:55,830 other one. What is this locking business? Why does it occur? And 1103 01:11:55,860 --> 01:12:00,480 is it good? Is it bad? And good? Can you just give us a short 1104 01:12:00,510 --> 01:12:03,120 primer on the locking of tables? 1105 01:12:03,840 --> 01:12:08,700 Well, so the so if you think about it, when you these are 1106 01:12:08,700 --> 01:12:12,480 calls, these are called atomic operations. So you have to you 1107 01:12:12,480 --> 01:12:15,930 have to be sure that when you put when you when you do a 1108 01:12:15,930 --> 01:12:20,880 transaction to a database, you have to be sure that the data is 1109 01:12:20,880 --> 01:12:24,060 not going to change in the middle of, of the change you're 1110 01:12:24,060 --> 01:12:27,360 trying to make. So if you have parallel operations going on, if 1111 01:12:27,360 --> 01:12:30,960 you have, if you have one process that's trying to update 1112 01:12:30,960 --> 01:12:33,720 a table and another process that trying to delete records out of 1113 01:12:33,720 --> 01:12:38,610 a table, who who wins? Do they both happen at the same time? 1114 01:12:38,610 --> 01:12:41,910 Because then you have been you have corruption you have? Yeah. 1115 01:12:42,270 --> 01:12:46,890 So you have to, you have to lock in at least some portion of the 1116 01:12:46,890 --> 01:12:50,130 table, maybe not the entire table, but you have to lock the 1117 01:12:50,130 --> 01:12:53,430 records that could potentially be changed. So you use something 1118 01:12:53,430 --> 01:13:03,480 called a query. It's, I'm losing it, I'm losing the terminology. 1119 01:13:03,480 --> 01:13:07,590 But it's like a query plan, I'm sorry, query plan. So the query 1120 01:13:07,590 --> 01:13:15,180 plan, look, you know, SM ends up estimating what table rows are 1121 01:13:15,180 --> 01:13:19,050 going to be affected by certain action. And in certain 1122 01:13:19,050 --> 01:13:23,040 circumstances, if if it looks if it sees that there's a potential 1123 01:13:23,280 --> 01:13:27,450 for conflict, it will lock those particular rows so that you 1124 01:13:27,450 --> 01:13:32,070 don't get database corruption. Wow. Okay. Locking is, is 1125 01:13:32,070 --> 01:13:37,800 critical to safety. It's a it's a, it's a safety mechanism. And 1126 01:13:37,800 --> 01:13:42,540 so you can get around Yeah, and Table Table locking is is 1127 01:13:42,630 --> 01:13:47,190 something you have to avoid at all costs. And so most of the 1128 01:13:47,190 --> 01:13:52,470 design of a database, other than performance, your performance is 1129 01:13:52,470 --> 01:13:55,740 trying to get around some of these things, like locking so 1130 01:13:55,740 --> 01:14:00,390 that you don't, so that you don't hamstring yourself. So we 1131 01:14:00,390 --> 01:14:05,670 have the NF items, you know, NF Items table, but just like NF 1132 01:14:05,670 --> 01:14:10,200 underscore value, there's also an NF underscore value, excuse 1133 01:14:10,200 --> 01:14:13,800 me an NF items underscore value that has relationship back to 1134 01:14:13,800 --> 01:14:17,730 the NF Items table. So those are episode level split blocks, now 1135 01:14:17,730 --> 01:14:21,480 that you blocked and so in, so what I did was create a new 1136 01:14:21,480 --> 01:14:24,060 table. I'm just going through this because I think it's maybe 1137 01:14:24,150 --> 01:14:26,340 it's beneficial for people to understand how beneficial 1138 01:14:26,340 --> 01:14:29,100 I'm enjoying it very, I'm enjoying it a lot more than the 1139 01:14:29,100 --> 01:14:31,680 discussion about fees and splits in the last show. 1140 01:14:32,250 --> 01:14:39,150 Okay, okay. Good, this is good. Okay, so then, what I did was 1141 01:14:39,150 --> 01:14:41,760 went and created an NF underscore social interact 1142 01:14:41,760 --> 01:14:46,620 table. And then that has a foreign key relationship to the 1143 01:14:46,680 --> 01:14:50,070 NF Items table. So you have an NF NF items and then you have 1144 01:14:50,280 --> 01:14:54,390 relationship to NF items underscore social interact. So 1145 01:14:54,840 --> 01:14:58,020 as party time sees arrays of feed, parses it sees there's a 1146 01:14:58,020 --> 01:15:02,790 social interact tag in it it up, it inserts a record or updates 1147 01:15:02,790 --> 01:15:07,650 or record in the NF items underscore social interact table 1148 01:15:08,040 --> 01:15:15,450 to insert that entry in there. That that is the initial, that's 1149 01:15:15,450 --> 01:15:19,200 the, that's you're setting up the schema, okay? Then you go in 1150 01:15:19,200 --> 01:15:22,140 there and change Chain, make the modifications to party times, 1151 01:15:22,140 --> 01:15:24,780 like you've got your scheme. And now, then you go and change in 1152 01:15:24,780 --> 01:15:31,380 the parser to add in the discovery, parsing and database 1153 01:15:31,380 --> 01:15:35,280 insertion of the social interact tax. So now you're, now you've 1154 01:15:35,280 --> 01:15:39,840 got things populating in that table in the database, then the 1155 01:15:39,840 --> 01:15:43,770 final step is to go in there and look and actually change the 1156 01:15:43,770 --> 01:15:48,180 endpoint. Well, intermediary step, you go and you find the 1157 01:15:48,180 --> 01:15:53,160 lower level database call. In the API's sort of low level 1158 01:15:53,160 --> 01:15:56,250 functions itself, there's a thing called a function called 1159 01:15:56,250 --> 01:16:00,840 Get get items by feed ID three, that's the name of the function. 1160 01:16:01,470 --> 01:16:06,870 And that is responsible for pulling for you give it a 1161 01:16:06,900 --> 01:16:10,980 podcast, index ID feed ID, and it gives you back all of the 1162 01:16:10,980 --> 01:16:15,270 items that go to all the episodes that belong to it as a 1163 01:16:15,270 --> 01:16:20,700 structure, then, and that function is referenced by the 1164 01:16:20,700 --> 01:16:26,970 API endpoint, which is slash episodes by feed ID. So 1165 01:16:26,970 --> 01:16:32,010 episodes, episodes by feed ID calls get get items by feed ID 1166 01:16:32,010 --> 01:16:35,970 three. And that's where it gets us data. So you go in there and 1167 01:16:36,420 --> 01:16:42,600 change get episodes by feed ID three, to also do a left join on 1168 01:16:42,600 --> 01:16:46,350 the table on this new table, and F items underscore social 1169 01:16:46,350 --> 01:16:50,940 interact. Now it's getting the social interact tags back with 1170 01:16:50,940 --> 01:16:55,980 it along in the same query that it gets the episodes with. So 1171 01:16:55,980 --> 01:16:59,730 you're still only doing one database call. Now you've got 1172 01:16:59,730 --> 01:17:01,650 this extra this extra data that you're 1173 01:17:01,860 --> 01:17:06,390 going on in the background there. Yeah. Okay, so how does 1174 01:17:06,390 --> 01:17:08,790 deleting an episode screw it all up? 1175 01:17:09,780 --> 01:17:10,740 Well, okay, so 1176 01:17:11,670 --> 01:17:15,750 let me set the use case that people understand. Because I am 1177 01:17:15,750 --> 01:17:19,470 now in charge of incoming customer support, which is info 1178 01:17:19,470 --> 01:17:22,770 podcast index.org. And basically, people go delete my 1179 01:17:22,770 --> 01:17:27,030 show, and that's kind of it or I deleted this episode, you're 1180 01:17:27,030 --> 01:17:28,140 still hosting it? 1181 01:17:29,070 --> 01:17:32,640 Can you notice the the increase in the level of people asking 1182 01:17:32,640 --> 01:17:35,880 for stuff to be removed? It's I have a lot more than it used to 1183 01:17:35,880 --> 01:17:36,240 be. 1184 01:17:36,870 --> 01:17:42,540 I have I don't know why I'm not quite sure. What's going on. I 1185 01:17:42,540 --> 01:17:48,210 do get a lot of Buzzsprout said to call you. Yes, I get a lot of 1186 01:17:48,210 --> 01:17:51,480 that. Buzzsprout? What are you telling them like Buzzsprout use 1187 01:17:51,480 --> 01:17:55,290 it because people will delete it. I think what's happening is, 1188 01:17:55,410 --> 01:17:58,770 for whatever reason, people are not liking some of their 1189 01:17:58,770 --> 01:18:03,600 episodes. The thing some people are moving to different models, 1190 01:18:03,600 --> 01:18:06,300 maybe subscription model, and they want to delete certain 1191 01:18:06,330 --> 01:18:10,950 older episodes, and they delete it. And then they and then they 1192 01:18:11,040 --> 01:18:13,830 you know, for whatever reason, they find out that it still 1193 01:18:14,040 --> 01:18:18,720 doesn't work. But it's listed in podcast index. And you know, 1194 01:18:18,720 --> 01:18:22,530 they assume a that we stolen it, you can feel the undertone a lot 1195 01:18:22,530 --> 01:18:25,620 of this is why are you hosting this? Why is it still there? 1196 01:18:25,620 --> 01:18:27,630 Why? You know, it's like, they don't know what and I 1197 01:18:27,630 --> 01:18:32,010 understand. So we're very cool. But it's it literally is because 1198 01:18:32,010 --> 01:18:35,250 we have not root because a lot most of these, we won't refresh 1199 01:18:35,250 --> 01:18:38,130 for you know what, I don't know what the frequency is refreshing 1200 01:18:38,130 --> 01:18:41,160 most of these feeds, when it's refreshed them. I think it all 1201 01:18:41,160 --> 01:18:46,770 changes, then it those episodes are removed or maybe not. But 1202 01:18:46,770 --> 01:18:51,660 that is what seems to have to take place. But that operation 1203 01:18:51,660 --> 01:18:53,130 seems to be complicated. 1204 01:18:53,940 --> 01:18:57,900 Isn't it is it is complicated in and I will tell you that it's 1205 01:18:57,900 --> 01:19:05,280 complicated mostly by financial constraints. Do we know? We 1206 01:19:05,280 --> 01:19:12,240 cannot? If if we had the budget to throw lots of money at a huge 1207 01:19:12,240 --> 01:19:15,420 database instance, I would fix this with power. Okay, of 1208 01:19:15,420 --> 01:19:17,280 course, with just more power I 1209 01:19:17,280 --> 01:19:19,440 stop. Okay, what do we need? 1210 01:19:21,060 --> 01:19:23,790 Oh, no. I mean, like, in order to do this in close to real 1211 01:19:23,790 --> 01:19:29,580 time, yeah, we would need a very, very big database that we 1212 01:19:29,580 --> 01:19:30,330 can't afford. 1213 01:19:31,050 --> 01:19:34,290 I need I know we can't afford it. But I'd like to know, he put 1214 01:19:34,290 --> 01:19:38,130 a number on it is $1,000 a month? Is it $10,000 a month? I 1215 01:19:38,130 --> 01:19:41,610 mean, just whatever you think it might be more or less. 1216 01:19:42,150 --> 01:19:44,640 I can't put a number on it without doing some research and 1217 01:19:44,640 --> 01:19:46,710 we do some research on that because that would be a great 1218 01:19:46,710 --> 01:19:48,900 thing to ask for. Yeah, sure. 1219 01:19:48,960 --> 01:19:53,850 So you've hurt us. You scale vertical first. And then before 1220 01:19:53,850 --> 01:19:56,970 you scale horizontal, I mean, you just you just go you make 1221 01:19:56,970 --> 01:20:01,650 your database bigger. That's the way you Solve problems as 1222 01:20:01,650 --> 01:20:04,050 problems of this type. And let me describe to you what I mean 1223 01:20:04,050 --> 01:20:12,120 by this type. So the the reason that we can't do this in real 1224 01:20:12,120 --> 01:20:14,670 time, Alexa, what Daniel J. Lewis said, he's like, we just 1225 01:20:14,670 --> 01:20:17,400 download the feed, and just replace what's already there. 1226 01:20:18,270 --> 01:20:21,480 That's not the way that's not the way it works. Because you so 1227 01:20:21,480 --> 01:20:25,620 we have, as I described, we have the NFA Items table that has 1228 01:20:25,620 --> 01:20:33,150 about 110 million episodes in it. The, in order to there's 1229 01:20:33,150 --> 01:20:39,240 about 25 to 35,000 database transactions a minute, currently 1230 01:20:39,270 --> 01:20:44,610 on average in the in the index, if you and we have 10 1231 01:20:44,610 --> 01:20:47,550 aggregators. So we have aggregators, zero through nine, 1232 01:20:48,030 --> 01:20:52,020 they're all aggregating and inserting data at 1233 01:20:52,050 --> 01:20:55,530 simultaneously, simultaneously. Yes, so we have, you know, 10 1234 01:20:55,530 --> 01:20:57,870 different streams of database connections that are happening. 1235 01:20:58,320 --> 01:21:01,890 So peaks, it peaks out maybe 40,000 transactions a minute, 1236 01:21:02,490 --> 01:21:10,650 typically, at that volume, it doesn't take, but just a few 1237 01:21:10,860 --> 01:21:15,690 attempts at deleting records out of that size of a table, to 1238 01:21:15,690 --> 01:21:18,360 where it could potentially lock large portions of the table 1239 01:21:18,360 --> 01:21:23,490 where and that and when that happens. All the all the if one 1240 01:21:23,490 --> 01:21:28,170 aggregator does tries to do a large delete, let's just say 1241 01:21:28,170 --> 01:21:32,520 that it hits a podcast that has 20,000 episodes when it would 1242 01:21:32,520 --> 01:21:36,720 there are some in there. This podcast has 20,000 episodes. And 1243 01:21:36,720 --> 01:21:39,390 let's just say that 1000 of them disappear, because this is some 1244 01:21:39,390 --> 01:21:43,860 crazy, weird podcast. So you also you're going to delete 1000 1245 01:21:43,860 --> 01:21:47,700 records out of this out of the table. If it locks a large 1246 01:21:47,700 --> 01:21:52,170 portion of the table. All all nine other aggregators then have 1247 01:21:52,170 --> 01:21:56,100 to halt and wait for it to finish. If if it doesn't finish 1248 01:21:56,100 --> 01:22:00,630 fast enough, they could time out and just have to restart. 1249 01:22:00,870 --> 01:22:03,450 I'm super excited by this Congress. I thought I thought it 1250 01:22:03,450 --> 01:22:06,030 was going to fall asleep. But I'm really I really this has 1251 01:22:06,030 --> 01:22:08,760 become very exciting actually to listen to, for a number of 1252 01:22:08,760 --> 01:22:16,680 reasons. One, doesn't blockchain solve this? Blockchain solves it 1253 01:22:17,430 --> 01:22:18,900 to noster we're gonna, 1254 01:22:20,460 --> 01:22:23,940 Nasir can solve all this it goes away overnight. Give us some 1255 01:22:23,940 --> 01:22:30,690 bitcoin Jack. But Jack Dorsey. The so is this. If you could if 1256 01:22:30,690 --> 01:22:33,630 you had to start over again and do a different database design? 1257 01:22:33,630 --> 01:22:36,120 Would that make a difference? Or is this just a fact of life and 1258 01:22:36,120 --> 01:22:36,840 database? 1259 01:22:39,210 --> 01:22:42,060 That's a good question. And I don't know how to really answer 1260 01:22:42,060 --> 01:22:45,360 it. It's possible that if I had to go back and do this over I 1261 01:22:45,360 --> 01:22:50,880 may have a may have every a May May as I just don't know, put 1262 01:22:50,880 --> 01:22:56,190 everything as it is now and put all the episode data in an own 1263 01:22:56,190 --> 01:22:59,490 and only the episode data in a NoSQL database that that's 1264 01:22:59,490 --> 01:23:04,890 possible. I still don't know if that's ideal. I would a lot of 1265 01:23:04,890 --> 01:23:08,490 this stuff takes trial and error to figure out whether or not as 1266 01:23:08,550 --> 01:23:12,990 it's it's to figure out whether it's stable. Again, I've had 1267 01:23:13,890 --> 01:23:17,310 probably no sequel is it's eventually consistent. And 1268 01:23:17,310 --> 01:23:22,230 that's right. Eventually eventual consistency with 1269 01:23:22,230 --> 01:23:25,530 something like this is really a problem. You have to have some 1270 01:23:25,530 --> 01:23:26,580 some guarantees. 1271 01:23:26,610 --> 01:23:31,140 Is this what those plus guys figured out? What does the what 1272 01:23:31,140 --> 01:23:33,480 was it plus? What's the name of that company that has a datum? 1273 01:23:33,840 --> 01:23:38,010 Forget about it. This is really interesting. I'm glad that you 1274 01:23:38,040 --> 01:23:40,410 that you're laying this out because people have no I mean, 1275 01:23:40,410 --> 01:23:44,130 even people who are in the business clearly don't really. I 1276 01:23:44,130 --> 01:23:47,910 know, Daniel J. Lewis didn't have all the pieces together. 1277 01:23:48,780 --> 01:23:50,550 This was interesting problem. 1278 01:23:51,240 --> 01:23:54,420 Yeah. And I think, I think Daniel J. Lewis uses Mongo. So 1279 01:23:54,420 --> 01:23:58,350 he uses a no SQL database. And this, he's not constrained by 1280 01:23:58,350 --> 01:24:03,540 schema. But the doubt, like I said, the downside of no sequel 1281 01:24:03,570 --> 01:24:08,310 is you have a promise of eventual consistency. That's not 1282 01:24:08,310 --> 01:24:12,270 good enough for for what we're doing. Right? We have to have, 1283 01:24:12,360 --> 01:24:15,690 we have to have a guarantee of consistency. And so like he's, 1284 01:24:15,720 --> 01:24:20,040 he's, he's using he's doing stats. Right? Very different. 1285 01:24:20,040 --> 01:24:20,340 Very 1286 01:24:20,340 --> 01:24:26,640 different, very different use case. Okay. I, I would love to 1287 01:24:26,640 --> 01:24:29,700 know what, I think you should do that. Let's find out what it 1288 01:24:29,700 --> 01:24:33,570 cost. And let's figure out a way to make that happen. We'll see 1289 01:24:33,570 --> 01:24:36,180 what it looks me we know kind of our budget, we're not paying 1290 01:24:36,180 --> 01:24:42,630 ourselves. So this all all goes into the into the systems, but 1291 01:24:42,630 --> 01:24:44,130 everybody would benefit. 1292 01:24:44,670 --> 01:24:47,340 Well, that goes back to sort of the financial question because 1293 01:24:47,340 --> 01:24:52,290 you have, like, if you think I mean, if you look at what if you 1294 01:24:52,290 --> 01:24:55,680 look at what we have coming in as income. So here's how, you 1295 01:24:55,680 --> 01:24:59,640 know, we started this thing saying okay, we want to make 1296 01:24:59,640 --> 01:25:02,760 sure or that. So what was promised people, we made a 1297 01:25:02,760 --> 01:25:06,570 promise to people that we're going to have an API that was 1298 01:25:06,570 --> 01:25:12,240 free forever. And that was the promise. In order 1299 01:25:12,240 --> 01:25:16,020 to that's all we promised. We promised controversy, we 1300 01:25:16,020 --> 01:25:19,650 promised all kinds of stuff. Okay. unwritten with 1301 01:25:19,650 --> 01:25:25,710 regards to an API web API. And that it was, yes, you're right. 1302 01:25:25,710 --> 01:25:29,850 We did promise controversial. And so we promised an API that 1303 01:25:29,850 --> 01:25:32,340 would be free for for anybody's use forever. I think that's the 1304 01:25:32,340 --> 01:25:36,240 language we use now. And in order to fulfill that promise. 1305 01:25:37,980 --> 01:25:42,120 What we did was we said, Okay, we're not we're going to, as 1306 01:25:42,120 --> 01:25:45,390 soon as we make, as soon as we have more money in income than 1307 01:25:45,390 --> 01:25:49,020 we're spending in in expenses each month, we're going to keep 1308 01:25:49,020 --> 01:25:51,990 that we're going to stash that money in the bank for as long as 1309 01:25:51,990 --> 01:25:57,390 it takes to build up some number x number of years of hosting 1310 01:25:57,390 --> 01:26:01,170 fees, where if something happened, and one of us got 1311 01:26:01,170 --> 01:26:04,500 sick, or something happened, and the project got derailed, we 1312 01:26:04,500 --> 01:26:07,830 would have an X amount of years of runway where even if we had 1313 01:26:07,830 --> 01:26:11,310 no income whatsoever, the the API would continue to function. 1314 01:26:12,090 --> 01:26:15,030 And so in order to make that happen, we have to keep our 1315 01:26:15,030 --> 01:26:20,790 expenses low enough to where we're still building money. So 1316 01:26:20,790 --> 01:26:26,040 we're, you know, for if we're putting a few $100 in the bank, 1317 01:26:26,160 --> 01:26:31,500 after expenses every month, it's going to take, you know, 345 1318 01:26:31,500 --> 01:26:34,950 years to build up a decent runway. Well, we don't we don't 1319 01:26:34,950 --> 01:26:36,060 really we're keeping our 1320 01:26:36,090 --> 01:26:38,610 right. But we really don't we really don't know yet what it 1321 01:26:38,610 --> 01:26:40,950 would take to supercharge our database. 1322 01:26:41,879 --> 01:26:44,819 We don't we don't but that was the financial thinking that we 1323 01:26:44,849 --> 01:26:46,049 that we engaged in? Yes. 1324 01:26:47,670 --> 01:26:50,310 We support a lot of different things, you know, we're still, 1325 01:26:50,370 --> 01:26:54,420 you know, ln pay, we're still paying a fee amount for that, 1326 01:26:54,420 --> 01:26:57,150 that keeps a couple of apps running with wallets, which, you 1327 01:26:57,150 --> 01:26:59,880 know, that may go away over time. I mean, there's all kinds 1328 01:26:59,880 --> 01:27:03,810 of stuff that, that we put into this to make the whole ecosystem 1329 01:27:03,810 --> 01:27:04,200 work. 1330 01:27:04,680 --> 01:27:08,040 Right. And I just want to make that I just think that's 1331 01:27:08,070 --> 01:27:12,660 important that people understand that we, we have we're, we're 1332 01:27:12,660 --> 01:27:16,740 running the database, and we're running the API now. But that's 1333 01:27:16,740 --> 01:27:20,490 not the only concern. We want it we have to do we have to 1334 01:27:20,490 --> 01:27:24,630 concerns run the database, run the API now. And make sure that 1335 01:27:24,630 --> 01:27:28,890 the the API can run for years in the future. And so for that 1336 01:27:28,890 --> 01:27:33,570 reason, we cannot spend all the money that we would take in we 1337 01:27:33,570 --> 01:27:38,490 have to save some. And that and that means that we have to, even 1338 01:27:38,490 --> 01:27:40,740 though we like last month, I think you'd be added up. It was 1339 01:27:40,740 --> 01:27:45,210 like $2,000. We had $2,000 in income last month. And we had 1340 01:27:45,240 --> 01:27:50,160 $1,200 of expenses, that we can't spend 2000 Because we get 1341 01:27:50,160 --> 01:27:53,940 2000. Because then it one month goes by and we don't have enough 1342 01:27:53,940 --> 01:27:56,400 income. We're debt we're out. Well, we're out of the game 1343 01:27:56,820 --> 01:27:59,310 is just a moment, we can thank a few people who have been 1344 01:27:59,340 --> 01:28:03,330 supporting the index. Yeah. And then we'll come back. And we'll 1345 01:28:03,330 --> 01:28:05,760 talk about green light for a moment before we wrap it up for 1346 01:28:05,760 --> 01:28:11,820 today. Yep. And I wanted to, I wanted to start off with a big 1347 01:28:11,820 --> 01:28:19,140 thank you to he did this last year as well. Sir anonymous of 1348 01:28:19,140 --> 01:28:23,940 Dogpatch and Lois LeBeau via who is nice, I don't know who this 1349 01:28:23,940 --> 01:28:29,160 is, other than he donates every month to no agenda. And it's 1350 01:28:29,190 --> 01:28:33,030 always through the mail. It's, it's always cash. It's always 1351 01:28:33,030 --> 01:28:38,940 from literally from a mailbox on the street. And he sent to our 1352 01:28:38,940 --> 01:28:42,450 Pio box. And and when I saw this, I mean, I know you had the 1353 01:28:42,450 --> 01:28:48,780 same I sent you a picture. I was like, Oh, man $3,006 all in 1354 01:28:48,780 --> 01:28:53,190 cash, with a note for podcasting. 2.0 Thank you to all 1355 01:28:53,190 --> 01:28:56,070 that are working to keep free speech available to the masses. 1356 01:28:56,670 --> 01:29:03,000 And so it's not our database money. But wow. humbled by this. 1357 01:29:03,030 --> 01:29:05,550 I think he did something similar last when we started right. And 1358 01:29:05,550 --> 01:29:05,610 he 1359 01:29:05,610 --> 01:29:09,090 did some decent he didn't he sent us a $4,000 in cash last 1360 01:29:09,090 --> 01:29:09,660 year. Yeah. 1361 01:29:09,720 --> 01:29:13,620 Yeah. It's always an odd number. He literally sent $2 bills, 1362 01:29:14,430 --> 01:29:18,930 three $3 bills. So I don't know, I never figured out the numbers. 1363 01:29:19,500 --> 01:29:21,750 But thank you very much. So animus with Dogpatch and Lois 1364 01:29:21,750 --> 01:29:25,470 Bovie. That means so meaningful to us. And that goes right into 1365 01:29:25,470 --> 01:29:30,210 our into our savings into our bank for the years that we want 1366 01:29:30,210 --> 01:29:30,930 to keep it running. 1367 01:29:31,650 --> 01:29:33,870 Yeah, we're doing taxes right now. And we literally had this 1368 01:29:33,870 --> 01:29:36,570 discussion this morning. It's like, we're you know, we'll just 1369 01:29:36,570 --> 01:29:39,780 take out what we need to pay the taxes and the stays in the bank. 1370 01:29:39,810 --> 01:29:40,380 Yes, everyone 1371 01:29:40,380 --> 01:29:45,330 understands, like, it's a pass through LLC. So money that comes 1372 01:29:45,330 --> 01:29:49,350 in literally Dave and I are taxed on it ourselves. So we we 1373 01:29:49,350 --> 01:29:53,010 only take out that, that we have to pay on our personal income 1374 01:29:53,010 --> 01:29:53,610 taxes. 1375 01:29:54,270 --> 01:29:58,080 Right. The IRS treats it as if we made money even though it's 1376 01:29:58,080 --> 01:30:00,480 still in a bank account that we haven't done yet. If you don't 1377 01:30:00,480 --> 01:30:01,350 have it and 1378 01:30:01,350 --> 01:30:02,880 on the note and on the note Yeah, 1379 01:30:03,330 --> 01:30:07,110 right. Alright. That's huge. Yeah. Thank you. Thank 1380 01:30:07,110 --> 01:30:12,360 you so much pressure on me. All right, couple of couple of lit 1381 01:30:12,360 --> 01:30:16,950 boosts booster grams that came in. We have oh, just help, 1382 01:30:17,010 --> 01:30:22,170 although he will be coming in later. We have 5015 sets, from 1383 01:30:22,170 --> 01:30:26,430 comics through blogger. And he says, Yeah, I mean, we know 1384 01:30:26,430 --> 01:30:30,360 he'll come in later as he is the delimiter solution to your large 1385 01:30:30,360 --> 01:30:34,860 database problem is cockroach labs.com/product. Affordable 1386 01:30:34,860 --> 01:30:40,200 cloud native elastic scale distributed database. Yeah, how 1387 01:30:40,200 --> 01:30:43,590 much does this cost? I don't know if we're gonna find out, 1388 01:30:43,800 --> 01:30:47,280 but we need to know. Well, thank you comment your blog and we'll 1389 01:30:47,280 --> 01:30:52,410 find out well, all of this stuff will we'll find out. We have 1390 01:30:52,440 --> 01:30:57,570 33,369 from blueberry this is all within the lips timeframe of 1391 01:30:57,570 --> 01:31:02,730 the show. And he has a disparaging comment about twit, 1392 01:31:02,730 --> 01:31:06,780 which I'm just not going to read. Now that does no need for 1393 01:31:06,780 --> 01:31:14,550 that. 33,333 from Eric p p Thank you very much. cimp 100% x D D D 1394 01:31:14,550 --> 01:31:27,240 got him. 100% 36 912 we have Chad F 33 333,003 333 3333. Can 1395 01:31:27,240 --> 01:31:30,990 I get the JCD you will obey jhingo will obey or you will 1396 01:31:30,990 --> 01:31:36,300 obey you will obey we have lavished with 6666 incentive 1397 01:31:36,300 --> 01:31:39,750 boosts. Thank you, Mike Dell with 25,000. Now we're talking 1398 01:31:39,990 --> 01:31:44,970 round two blueberries PCPA PC 2.0 tags in progress. CO 1399 01:31:44,970 --> 01:31:56,640 podcasting he says we have 33,333 from SU pipe pipe CD. I'm 1400 01:31:56,640 --> 01:31:58,950 not going to type that in my command line loving the pod 1401 01:31:58,950 --> 01:32:00,900 verse love. Oh, of course. Well, we 1402 01:32:00,960 --> 01:32:04,620 would love CD. Yeah. From the from the socials. Yeah. We love 1403 01:32:04,620 --> 01:32:05,340 all the apps. 1404 01:32:05,400 --> 01:32:09,930 We love all of our apps. Chat F 3333. Again, remember Adam that 1405 01:32:09,930 --> 01:32:12,840 Na is a comedy show, so it doesn't count as a political 1406 01:32:12,840 --> 01:32:19,080 podcast. It's true. It's true. We have more IDs from contracts 1407 01:32:19,200 --> 01:32:23,730 with 13,579. Our evolution from a stats package to the home of 1408 01:32:23,730 --> 01:32:27,480 value for value creators starts next week with the integration 1409 01:32:27,480 --> 01:32:30,360 of podcaster wallet beyond excited Oh, we got that 1410 01:32:30,360 --> 01:32:34,650 together. You have an API keys. Oh, that's so cool. That was a 1411 01:32:34,650 --> 01:32:37,980 great on ramp for value for value. And by the way today as 1412 01:32:37,980 --> 01:32:44,820 of right now, I have the stats on the standby. 11,871 feeds 1413 01:32:44,820 --> 01:32:48,330 with value blocks up about 30 from yesterday. It used to be 1414 01:32:48,330 --> 01:32:51,540 one or two a day now we're at you know 20 or 30 a day new 1415 01:32:51,570 --> 01:32:55,860 value for value podcasts are very excited about that. Steve 1416 01:32:55,860 --> 01:33:00,840 Webb he is the OG God caster sir OG God caster with Whoa, a super 1417 01:33:00,840 --> 01:33:07,290 striper boost 77,777 Whoa, just saying hey, oh, and inviting the 1418 01:33:07,290 --> 01:33:10,590 PC 2.0 community to join the Lifespring family and reading 1419 01:33:10,590 --> 01:33:14,520 through the Bible in a year at audio Bible dot link. We'd love 1420 01:33:14,520 --> 01:33:18,660 to have you join us in our 13th Season go podcasting go God 1421 01:33:18,660 --> 01:33:19,050 cast. 1422 01:33:21,000 --> 01:33:23,400 Does that mean that they've read things read through the Bible? 1423 01:33:23,400 --> 01:33:25,320 13 times? Yes, it means yes, 1424 01:33:25,350 --> 01:33:30,000 yes. 13 Yeah, it does a whole year. And he's done it. Well, he 1425 01:33:30,000 --> 01:33:34,110 was one of the god casters were very early to understand what 1426 01:33:34,110 --> 01:33:35,520 was going on with podcasting. 1427 01:33:36,360 --> 01:33:39,000 So I think Buzzsprout got their start as a God cast or 1428 01:33:39,000 --> 01:33:40,080 repository. I think 1429 01:33:42,180 --> 01:33:44,460 they did like I believe it. No, I believe it. I believe it 1430 01:33:44,670 --> 01:33:50,400 wasn't gonna say Oh, do you remember Lilly and X? who 1431 01:33:50,400 --> 01:33:54,540 remember the band Lillian x? Well, well, it's interesting 1432 01:33:54,540 --> 01:33:58,650 because they haven't. They released 10 albums in their 1433 01:33:58,650 --> 01:34:02,460 career and they're in the Louisiana Hall of Fame and 1434 01:34:02,490 --> 01:34:07,530 Songwriters Hall of Fame. And when they first came out their 1435 01:34:07,530 --> 01:34:11,910 very first video I debuted on headbangers ball, and so they 1436 01:34:11,910 --> 01:34:14,550 have a new video coming out. And 1437 01:34:15,630 --> 01:34:17,070 and I'm old now. 1438 01:34:17,790 --> 01:34:21,810 They're my age, ancient. And they have a new video a new out 1439 01:34:21,810 --> 01:34:24,480 new video coming out. And they sent me a note and said, Hey, 1440 01:34:24,480 --> 01:34:27,900 ma'am, we love what you're doing. And we'd love for you to 1441 01:34:27,930 --> 01:34:32,220 intro our new video to put in the video reminding people that 1442 01:34:32,220 --> 01:34:37,050 35 years ago, you premiered us on headbangers ball. And you 1443 01:34:37,050 --> 01:34:39,510 know, we'd love to do that with a new video. And are you going 1444 01:34:39,510 --> 01:34:42,420 to do it? Well, so here's what's interesting. I'm looking at this 1445 01:34:42,420 --> 01:34:46,770 video. I'm like, I kind of look at is this a Satan band? Or what 1446 01:34:46,770 --> 01:34:50,640 is it? Until I got all the way through the video? I'm like, Oh, 1447 01:34:50,700 --> 01:34:52,920 I look them up. Yeah, you know, Christian man, I didn't know 1448 01:34:52,920 --> 01:34:54,720 that. And so of course I'm gonna 1449 01:34:54,720 --> 01:34:57,960 do that too. Yeah, name of the album. Yes. Yeah. 1450 01:34:58,380 --> 01:35:00,210 So of course we're gonna do that it was just interest thinking 1451 01:35:00,210 --> 01:35:03,750 that I had no idea that they were a Christian rock band. And 1452 01:35:03,750 --> 01:35:06,720 you wouldn't know necessarily until you see the video, which 1453 01:35:06,720 --> 01:35:09,990 is pretty funny. They still they still have humor. They're still 1454 01:35:09,990 --> 01:35:10,380 gonna say 1455 01:35:10,380 --> 01:35:12,690 you're gonna you're gonna do this. Yeah, of course. 1456 01:35:13,410 --> 01:35:15,480 Hey everybody remember me? I'm old. 1457 01:35:18,090 --> 01:35:18,900 Less hair. 1458 01:35:19,290 --> 01:35:23,640 That's right 2121 From tone record pod verse.fm is snappy 1459 01:35:23,640 --> 01:35:28,590 with this latest update props to Mitch and team. Sir Spencer 6969 1460 01:35:28,620 --> 01:35:33,060 Love at the work the board. I love all the work the board and 1461 01:35:33,060 --> 01:35:36,120 its members have put into the live experience. Live items 1462 01:35:36,120 --> 01:35:38,610 first birthday is coming up. We are excited to celebrate with 1463 01:35:38,610 --> 01:35:41,400 Dave on a bowls with buds at the end of the month. More details 1464 01:35:41,400 --> 01:35:43,350 to come green heart emoji 1465 01:35:43,410 --> 01:35:46,140 desert. Oh, that's right. We guesting on the guest 1466 01:35:46,170 --> 01:35:51,810 Nice Nice nice. Let me see tone record sent a short row of ducks 1467 01:35:51,810 --> 01:35:58,860 with a testing thank you all for the tests. And I think we're I 1468 01:35:58,860 --> 01:36:02,850 think that you have everything from there on out. So let's 1469 01:36:03,060 --> 01:36:05,550 let's thank the people with the booster grams that came in. 1470 01:36:05,910 --> 01:36:10,590 Well, we got to pay pal. One one singular Pay Pal. Yeah, the one 1471 01:36:10,590 --> 01:36:10,950 from 1472 01:36:11,400 --> 01:36:17,100 from our buddy Todd. He says, Hey guys, Todd. See. I want to 1473 01:36:17,100 --> 01:36:19,980 thank you for all the hard work you're doing here. Let's keep 1474 01:36:19,980 --> 01:36:22,500 the features coming. Mike and I are planning what our next round 1475 01:36:22,500 --> 01:36:25,320 of implementations will be for podcasters missing out on fun 1476 01:36:25,320 --> 01:36:27,180 migrate to blueberry today. Go podcasting. 1477 01:36:29,130 --> 01:36:34,950 Oh, nice. Oh, that qualifies. Sakala 20 is blades on the 1478 01:36:34,950 --> 01:36:36,000 Impala 1479 01:36:36,030 --> 01:36:39,300 my dog hates that jingle. She thinks that singing shock collar 1480 01:36:39,330 --> 01:36:44,280 so she always runs away when I play. big baller shot caller. 1481 01:36:44,520 --> 01:36:45,720 Oh, Daddy, no. 1482 01:36:47,010 --> 01:36:52,560 We got to 54321 from our buddy Roy. Oh, talking about tennis. 1483 01:36:52,560 --> 01:36:52,650 We're 1484 01:36:52,650 --> 01:36:55,770 gonna talk about Roy in his endeavors in a moment for sure. 1485 01:36:56,190 --> 01:37:00,180 Yeah, we we will. One of my endeavors is to get right back 1486 01:37:00,180 --> 01:37:01,590 on the show. So you can talk to us about it. 1487 01:37:01,620 --> 01:37:03,720 Well, he's not ready. He's got something to talk about. 1488 01:37:03,720 --> 01:37:05,910 Finally, Jean been 1489 01:37:06,150 --> 01:37:09,510 1337 lead booster cast Matic. He says, I don't think removing 1490 01:37:09,510 --> 01:37:12,960 emails were blowing it Buzzsprout, among other can put 1491 01:37:12,960 --> 01:37:15,780 the email back in for 24 hours or another small amount of time 1492 01:37:15,780 --> 01:37:17,010 to facilitate the validation. 1493 01:37:17,340 --> 01:37:20,400 Yes, right. Yes, we've learned that didn't know it. And 1494 01:37:20,400 --> 01:37:24,630 interestingly, we had a support email come in. It's still it's 1495 01:37:25,080 --> 01:37:29,880 it's still causing support. Increased support actions. Can 1496 01:37:29,880 --> 01:37:34,200 you remove this? Yeah, do you mind just sending this from from 1497 01:37:34,200 --> 01:37:36,990 the email address that is in your feed, and I see that you're 1498 01:37:36,990 --> 01:37:41,490 Buzzsprout you can have that put back into your feed reply comes 1499 01:37:41,490 --> 01:37:44,700 in, you can click on our E on our webpage and see that it's 1500 01:37:44,700 --> 01:37:49,920 the email so people don't want to do it. Yeah. People also 1501 01:37:49,920 --> 01:37:53,820 think that we're, you know, like, like Amazon or something 1502 01:37:53,820 --> 01:37:58,530 like, and I can't blame them for for, for thinking that we're as 1503 01:37:58,530 --> 01:38:04,980 Silicon Valley company, but even so, wow, privileged much. I 1504 01:38:04,980 --> 01:38:06,720 mean, if people are very rude 1505 01:38:08,880 --> 01:38:12,630 Todd from Northern Virginia 3333 through breweries, and he says, 1506 01:38:12,720 --> 01:38:16,470 What did I miss? Milkshake? I pray this is some sort of inside 1507 01:38:16,470 --> 01:38:21,480 joke. No, it's it is literally a milkshake made of made from beef 1508 01:38:21,480 --> 01:38:21,990 protein. 1509 01:38:23,310 --> 01:38:25,740 It's delicious. And it tastes like hamburger. 1510 01:38:26,730 --> 01:38:31,710 No, it tastes like chocolate. They it is it is the what does 1511 01:38:31,710 --> 01:38:32,160 this stuff 1512 01:38:32,640 --> 01:38:34,770 Alex gage turned you on this didn't he was telling me 1513 01:38:34,830 --> 01:38:39,930 no, no, no, Dan Benjamin did oh prime is that what this is going 1514 01:38:39,930 --> 01:38:44,370 to equip? Yes, Prime protein grass fed beef isolate protein 1515 01:38:44,370 --> 01:38:45,840 powder from equipped foods 1516 01:38:45,870 --> 01:38:49,050 and you throw it in water. Water mill I 1517 01:38:49,050 --> 01:38:52,380 put in milk and milk and ice cubes and like some 1518 01:38:52,410 --> 01:38:54,750 ice cubes, milk and ice cubes. Yeah, 1519 01:38:54,780 --> 01:38:57,930 it makes like a slushy. It's good. Like it's like a it tastes 1520 01:38:57,930 --> 01:38:58,500 like ice cream. 1521 01:38:58,530 --> 01:39:02,610 Are you still eating like actual beef like the KFC stuff? Okay, 1522 01:39:02,610 --> 01:39:02,970 good. 1523 01:39:03,090 --> 01:39:05,970 Yeah, this is my supercharge. This is my super beef charge. 1524 01:39:06,330 --> 01:39:11,520 Yeah. Yes, the quip. quip is the name of the thing. Coupon Code 1525 01:39:11,520 --> 01:39:16,590 podcasting. 2.0 G Jean bien again 2222 through cast thematic 1526 01:39:16,950 --> 01:39:19,320 just talking about where to put Mastodon comments. I'm wondering 1527 01:39:19,320 --> 01:39:22,380 if Todd could partner with Vivaldi are similar. They're 1528 01:39:22,380 --> 01:39:27,720 offering Mastodon accounts to all their users. Possible. Jean 1529 01:39:27,720 --> 01:39:30,840 began 22 to 22 through bigass demanding he says really enjoyed 1530 01:39:30,840 --> 01:39:33,810 hearing what Todd and crew were doing. also agree that it would 1531 01:39:33,810 --> 01:39:36,630 be awesome if some 2.0 features came to overcast. I love that 1532 01:39:36,630 --> 01:39:39,720 app. I do too. And I'm hoping that the firt I've sort of 1533 01:39:39,720 --> 01:39:42,600 separately hoping the first thing he implements other than 1534 01:39:42,600 --> 01:39:45,210 that I think transcripts is always good for accessibility is 1535 01:39:45,210 --> 01:39:47,790 live because I know that he he does a lot with users 1536 01:39:47,790 --> 01:39:49,350 himself. Yeah, exactly. Yeah, right. 1537 01:39:50,760 --> 01:39:53,760 Hard Hat one a one a one a binary boost through Kira 1538 01:39:53,760 --> 01:39:58,590 Castro. No note thank you hard hat, chaos. 99 5000 SATs and he 1539 01:39:58,590 --> 01:40:01,830 says another great episode. Thank you. Thank you. Mere 1540 01:40:01,830 --> 01:40:06,690 Mortals our buddy Kyron 11111 through fountain he says, I'm so 1541 01:40:06,690 --> 01:40:10,380 damn pumped. It feels like we've ditched the skis and hijacked a 1542 01:40:10,380 --> 01:40:11,040 snowmobile. 1543 01:40:14,670 --> 01:40:16,350 Satchel or Richards for the win 1544 01:40:16,410 --> 01:40:20,940 ice 100% I think what you meant was absolutely absolutely 1545 01:40:20,940 --> 01:40:23,610 yes. completely full on. 1546 01:40:24,330 --> 01:40:27,990 Build up Prague 1000 SATs through potrayed. He says 1547 01:40:27,990 --> 01:40:31,320 testing testing had no idea pod friend is abandoned. Looks like 1548 01:40:31,320 --> 01:40:34,290 it's still working. I don't think he's rewriting. 1549 01:40:34,590 --> 01:40:36,450 It still works very well actually. 1550 01:40:37,830 --> 01:40:40,530 Bill Prague again 1000 says stupid friend. He says there is 1551 01:40:40,530 --> 01:40:43,860 a protocol that you use for some time now that has private public 1552 01:40:43,860 --> 01:40:47,250 keys you can use to log into 100 plus apps and all your followers 1553 01:40:47,250 --> 01:40:50,610 are there. All your comments are also there. Cross app comments. 1554 01:40:50,910 --> 01:40:53,610 This news was boost was made possible. Thanks to Brian and 1555 01:40:53,610 --> 01:40:59,280 Hi. Bye. Not letting me boost over 1000 need to spin those 1556 01:40:59,280 --> 01:40:59,730 sets. 1557 01:40:59,760 --> 01:41:03,360 It must be so I know how this feels when you when you have a 1558 01:41:03,390 --> 01:41:07,080 technology that's been around for a long time and it works and 1559 01:41:07,080 --> 01:41:10,140 then people come along with something called noster and just 1560 01:41:10,140 --> 01:41:14,610 pisses you off. I feel you Brian I feel Yeah. 1561 01:41:16,200 --> 01:41:19,920 Bill Prague again. 1003 potrayed he says looks like I have to 1562 01:41:19,920 --> 01:41:23,340 boost 10 times 1000 SATs Pedialyte pod friends on the 1563 01:41:23,340 --> 01:41:26,430 browser. It was playing video, but he's given the ode to pod 1564 01:41:26,430 --> 01:41:29,100 friend but pod friends still lives man. Yeah, it's not that 1565 01:41:29,100 --> 01:41:35,310 okay. Rob Suzuki through fountain 2421. He says thanks 1566 01:41:35,310 --> 01:41:37,770 for your value to the Podcast Movement. Greetings from 1567 01:41:37,770 --> 01:41:38,670 Dominican Republic. 1568 01:41:38,700 --> 01:41:40,500 No Hello, Dominican Republic. 1569 01:41:41,910 --> 01:41:48,720 3000 from forest K Farscape. Ian through fountain no note CASP 1570 01:41:48,720 --> 01:41:52,050 eland 3690. Through fountain he says I have a question about the 1571 01:41:52,050 --> 01:41:54,990 splits. I was happy atmosphere. 1572 01:41:55,020 --> 01:41:55,890 How do you calculate? 1573 01:41:57,720 --> 01:42:01,230 I was happily streaming 17 sets a minute. I think calculate the 1574 01:42:01,230 --> 01:42:04,440 first split percentage goes to the highest percent. Oh god. 1575 01:42:04,980 --> 01:42:09,390 No, no, no. Don't take me there. Don't take. Don't take me down 1576 01:42:09,390 --> 01:42:10,290 that road. No. 1577 01:42:12,540 --> 01:42:13,740 Are you bending this question? 1578 01:42:14,010 --> 01:42:15,540 No, I'm not banning, of course. 1579 01:42:16,200 --> 01:42:20,250 I think I think calculate the first split percentage goes to 1580 01:42:20,250 --> 01:42:24,750 the highest percentage. And then calculating down. Streaming less 1581 01:42:24,750 --> 01:42:28,230 than one set a minute is not a thing. So let's see. I'm gonna 1582 01:42:28,230 --> 01:42:32,760 show 22 sets a minute pop up. Don't mind the small difference. 1583 01:42:34,080 --> 01:42:40,110 Oh, I'm so lost. CASS Cass sent me an email. I can't do it. It's 1584 01:42:40,110 --> 01:42:40,590 too much. 1585 01:42:41,970 --> 01:42:49,110 I have a small complaint. Before I forget. Yeah. You know, I add 1586 01:42:49,110 --> 01:42:51,930 a lot of podcasts manually for people who don't see the Add 1587 01:42:51,960 --> 01:42:52,470 button. 1588 01:42:54,570 --> 01:42:56,670 Yeah, the one that's at the top of the way, the one that 1589 01:42:56,670 --> 01:43:03,180 says Add? Yes. Can we change the sunflowers? Why I keep getting 1590 01:43:03,180 --> 01:43:08,340 sunflowers in the caption? It's always the sunflowers. I don't 1591 01:43:08,340 --> 01:43:12,780 trust it. I need something else. What do I get sunflowers all the 1592 01:43:12,780 --> 01:43:13,320 time. 1593 01:43:13,890 --> 01:43:17,700 I get trumpets. I do every time 1594 01:43:17,730 --> 01:43:20,520 I'll trade trumpets for sunflowers for a day. Just for a 1595 01:43:20,520 --> 01:43:21,090 day. 1596 01:43:21,330 --> 01:43:25,020 clear your cookies. Over your cookies. Okay. All right. Thank 1597 01:43:25,020 --> 01:43:27,810 you. You're becoming a help desk guy. I'm gonna I'm gonna. I'm 1598 01:43:27,810 --> 01:43:29,400 putting so JD when someone 1599 01:43:29,400 --> 01:43:33,330 says my episodes have been updated. I'm gonna say clear 1600 01:43:33,330 --> 01:43:34,140 your cookies. 1601 01:43:37,980 --> 01:43:41,700 Reboot rebooting. This is where we're turning you into a 1602 01:43:41,700 --> 01:43:45,840 helpdesk. Feeling good about it. Yes. Every time when you get off 1603 01:43:45,840 --> 01:43:48,180 a helpdesk call. You have to turn around a bitch to your co 1604 01:43:48,180 --> 01:43:51,330 workers about how stupid the person was. Like you're like, 1605 01:43:51,480 --> 01:43:56,940 Oh, you mean the Add button at the top? It was hard to spot. 1606 01:43:57,570 --> 01:44:01,170 Okay, Satoshi stream 5552. Through fountain This is 1607 01:44:01,440 --> 01:44:04,800 Benjamin at FOSDEM was good. Yes. Benjamin Bellamy. 1608 01:44:04,830 --> 01:44:07,980 Yeah. Oh, yeah, we forgot to talk about that. Good job, 1609 01:44:07,980 --> 01:44:08,610 Benjamin. 1610 01:44:09,090 --> 01:44:13,110 Yeah, great slideshow. Oh, awesome. Like, chop and dropped 1611 01:44:13,110 --> 01:44:14,910 and killed his numbers right after the show. 1612 01:44:16,950 --> 01:44:20,580 Love or hate the way he goes. This is not a podcast. This is a 1613 01:44:20,580 --> 01:44:27,090 podcast like a big RSS feed code. Yeah, Victoria needs to 1614 01:44:27,090 --> 01:44:29,160 see that so she understands what's happening. 1615 01:44:29,460 --> 01:44:35,700 Yeah. Who is the fountain? He says due to precision issues. We 1616 01:44:35,700 --> 01:44:38,760 should oh wait, this is a four. Okay, this is a multi Porter. 1617 01:44:38,880 --> 01:44:42,210 Okay, here we go. I think I got it here. Date all these are 1618 01:44:42,210 --> 01:44:44,850 10 1000s ask Dave seem to suggest that we don't require 1619 01:44:44,850 --> 01:44:47,640 splits to add up to a 100 because it's easy to make 1620 01:44:47,640 --> 01:44:51,600 mistakes and produce a different total amount. Although I agree 1621 01:44:51,600 --> 01:44:54,210 with this requirement shouldn't exist. I don't find this 1622 01:44:54,210 --> 01:44:57,780 rationale convincing. Validation can be performed on the host 1623 01:44:57,780 --> 01:45:01,620 side is that a mentioned and the player side have a much better 1624 01:45:01,620 --> 01:45:05,370 reason in my mind is the same as why companies don't limit the 1625 01:45:05,370 --> 01:45:10,110 number of shares to a 100. It would limit the maximum number 1626 01:45:10,110 --> 01:45:14,730 of shareholders and the fractions they can own. Okay for 1627 01:45:14,730 --> 01:45:17,970 us, and due to precision issues, we should always prefer integers 1628 01:45:17,970 --> 01:45:20,760 to decimal numbers in financial software. That's why stripe API 1629 01:45:20,760 --> 01:45:25,470 uses cents instead of dollars. For example, finally, as a math 1630 01:45:25,470 --> 01:45:28,950 teacher, oh, W Dawson math teacher. I feel Yeah, and this 1631 01:45:28,950 --> 01:45:31,500 makes me terrified for him to listen to the show. Finally, as 1632 01:45:31,500 --> 01:45:34,320 math teacher I feel the most intuitive way of explaining 1633 01:45:34,320 --> 01:45:38,100 splits to newcomers is by thinking of them as ratios, the 1634 01:45:38,100 --> 01:45:43,230 concept familiar to most as it is found in many recipes. A eg 1635 01:45:43,260 --> 01:45:46,680 if Alice's Bob's and Charlie splits are four, two and three 1636 01:45:46,680 --> 01:45:50,190 respectively. They will share the incoming SATs in the ratios 1637 01:45:50,190 --> 01:45:57,780 of four to four to two to three. That is the way that a math 1638 01:45:57,780 --> 01:46:03,420 teacher would explain it. You're right. And just that's more 1639 01:46:03,420 --> 01:46:05,190 confusing to me than percentages. 1640 01:46:06,390 --> 01:46:07,140 man 1641 01:46:10,590 --> 01:46:12,690 All right. Let me let me save you I'm gonna save you okay. 1642 01:46:12,720 --> 01:46:17,640 Yeah. Todd Cochran boosts 50,000 in my wallet on found with a 1643 01:46:17,640 --> 01:46:19,500 debit card. So simple. Good podcasting. 1644 01:46:19,530 --> 01:46:20,580 Oh. 1645 01:46:22,230 --> 01:46:25,740 A bit. You almost fell off the cliff. Okay, I had to save you. 1646 01:46:26,370 --> 01:46:28,980 Well, it's almost like if a split was traveling on a train 1647 01:46:28,980 --> 01:46:30,960 at 17 cents per minute. 1648 01:46:32,880 --> 01:46:35,610 And the ratios to distress. Thank you, Nathan. Yeah, good 1649 01:46:35,610 --> 01:46:39,840 line. And thank you, Debbie. Does I appreciate that. Yeah, I 1650 01:46:39,840 --> 01:46:43,980 don't know. It's just confused. Tone wrecker. 22 to 22 through 1651 01:46:43,980 --> 01:46:46,890 BOD verse he says, while it reloaded slinging Sass with 1652 01:46:46,890 --> 01:46:48,330 abandoned a boosting 1653 01:46:48,360 --> 01:46:50,850 haiku. I love swinging SATs. Thank you. 1654 01:46:51,900 --> 01:46:53,550 That was a haiku did you get Yes, of 1655 01:46:53,550 --> 01:46:55,440 course. I got the Haiku. Haiku. 1656 01:46:56,070 --> 01:46:57,090 That's, that's our first 1657 01:46:59,280 --> 01:47:00,090 booster coup. 1658 01:47:00,660 --> 01:47:06,000 This dequeue Bucha cool. I like it. Borlaug. 25,000 SATs through 1659 01:47:06,270 --> 01:47:08,460 the pod verse he says I can't thank you enough for all the 1660 01:47:08,460 --> 01:47:10,380 work that you've you're doing for this project. This is the 1661 01:47:10,380 --> 01:47:12,930 only board meeting I look forward to each week me but 1662 01:47:13,620 --> 01:47:17,880 ditto Yeah, yeah, that's where I ended on the on the boost and 1663 01:47:18,510 --> 01:47:19,740 where's comic strip blogger? 1664 01:47:21,330 --> 01:47:24,240 Bloggers right here. Oh, you already did him. Okay. No, no, 1665 01:47:24,270 --> 01:47:28,620 no, I didn't do I did the I did his his new one but not the not 1666 01:47:28,620 --> 01:47:30,360 the regular the regular Okay. 1667 01:47:30,540 --> 01:47:35,760 Comic Strip blogger 30 3015. Dear David, Adam, the AI dot 1668 01:47:35,760 --> 01:47:40,020 cooking podcast present obedience is in acknowledgment 1669 01:47:40,230 --> 01:47:44,760 to your safeguarding of free speech. At don't even know what 1670 01:47:44,760 --> 01:47:47,910 this word is. And now you're using words that now you know 1671 01:47:47,910 --> 01:47:54,330 more English than I do. The AI cooking podcast, President OBC 1672 01:47:54,330 --> 01:47:56,670 insists in acknowledgment to your safeguarding your free 1673 01:47:56,670 --> 01:48:00,990 speech, offering our fealty in the form of the part on the back 1674 01:48:00,990 --> 01:48:05,190 sets we implore you to keep abreast of the singularity by 1675 01:48:05,190 --> 01:48:09,810 downloading our fortnightly show the constant colloquy upon the 1676 01:48:09,810 --> 01:48:13,530 state of human hood. Podcasting is the medium of the people 1677 01:48:13,890 --> 01:48:17,700 congenially Yours, Gregory Forman yo CSV 1678 01:48:18,630 --> 01:48:21,690 Thank you. Thank you comics for blogger I tried to 1679 01:48:21,690 --> 01:48:26,700 do like a The Twilight Zone got was that was that was that 1680 01:48:26,700 --> 01:48:27,780 coming through a little bit? 1681 01:48:28,560 --> 01:48:34,350 It would need a little more. Comic Strip blogger just a comic 1682 01:48:34,350 --> 01:48:44,460 stripper or a blogger now in AI welcome li D to the just came in 1683 01:48:44,460 --> 01:48:47,970 5000 from anonymous and Bitcoin boost your favorite podcasters 1684 01:48:47,970 --> 01:48:53,280 and pod verse plus Alby hashtag Foss and Dred Scott who just 1685 01:48:53,280 --> 01:48:57,000 left the chat room live boosting for boost boost Can I get a 100% 1686 01:48:57,000 --> 01:49:01,920 horn please with 222,222 SAS 1687 01:49:07,950 --> 01:49:08,670 we got it all 1688 01:49:09,270 --> 01:49:12,780 20 is Blaze only Impala no one 1689 01:49:12,780 --> 01:49:16,020 understands exactly how Dred Scott does it but he does it 1690 01:49:16,260 --> 01:49:22,860 and will poor guy he said they may posted with his like Cisco 1691 01:49:22,860 --> 01:49:25,770 switch meltdown of epic proportions like it's 1692 01:49:26,280 --> 01:49:28,620 his job. Yeah. Oh boy. 1693 01:49:28,650 --> 01:49:31,260 Yeah, we know it was a bad one. It was a bad one. Yeah. 1694 01:49:31,290 --> 01:49:33,750 Thank you very much boosters we got some monthlies. 1695 01:49:34,860 --> 01:49:40,350 We do we have Joseph maraca $5 Jeremy new $5 Cameron Rose $25 1696 01:49:40,350 --> 01:49:47,700 Lauren ball $24.20 Basil Phillips $25 pod verse LLC. $50 1697 01:49:48,000 --> 01:49:51,720 Christopher Hora Baraka $10 In Mitch downy Tinder. 1698 01:49:52,349 --> 01:49:54,929 Thank you all very much the value for value if you'd like to 1699 01:49:54,929 --> 01:49:58,379 learn more about that concept value for number four value dot 1700 01:49:58,379 --> 01:50:02,339 info. This is The whole project is value for value just heard 1701 01:50:02,339 --> 01:50:04,649 where our money goes, what we do with it, what we do with your 1702 01:50:04,649 --> 01:50:08,999 money to make the project run, and how it benefits everybody. 1703 01:50:09,209 --> 01:50:12,719 If you'd like to learn more, if you'd like to actually support 1704 01:50:12,719 --> 01:50:15,929 us go to podcast index.org down at the bottom is a big red 1705 01:50:15,929 --> 01:50:21,239 donate button you can use that to send us Fiat fun coupons. 1706 01:50:21,239 --> 01:50:28,349 Also, we have a on chain, Bitcoin spot there and note we 1707 01:50:28,349 --> 01:50:32,009 have nothing came in although people wanted it so badly. Hey, 1708 01:50:32,009 --> 01:50:34,859 man, you should ever on chain Bitcoin, we need to scan a QR 1709 01:50:34,859 --> 01:50:37,499 code to send you Bitcoin man pretty much knew. 1710 01:50:37,530 --> 01:50:41,040 So the only time people ever use it is to make sure that it gives 1711 01:50:41,040 --> 01:50:42,030 you that it works. 1712 01:50:42,720 --> 01:50:45,540 Scott Trump's got basically we'll test it to make sure it's 1713 01:50:45,540 --> 01:50:49,020 being used. But of course, you can get any of the modern apps 1714 01:50:49,020 --> 01:50:53,340 at new podcast apps.com and use that to boost us. And of course, 1715 01:50:53,340 --> 01:50:56,940 you want to see that it has value for value. But use any of 1716 01:50:56,940 --> 01:51:00,270 them really, there's so many different. It's also personal, 1717 01:51:00,270 --> 01:51:03,060 so many different apps. But that is the preferred way. Of course, 1718 01:51:03,060 --> 01:51:05,010 you can always do it through PayPal, thank you very much for 1719 01:51:05,010 --> 01:51:08,430 supporting podcasting 2.0, the podcast, which is really the 1720 01:51:08,430 --> 01:51:12,270 gateway into the whole project. And now let's talk about ROI. 1721 01:51:13,560 --> 01:51:18,270 And, yeah, so, I mean, I can't, 1722 01:51:19,080 --> 01:51:23,430 he lived he literally came in almost on time. He said six 1723 01:51:23,430 --> 01:51:27,240 months. And it's just been seven or seven and a half months, but 1724 01:51:27,240 --> 01:51:31,680 almost two that he said it and here he is with the what is it 1725 01:51:31,680 --> 01:51:33,630 the breeze SDK. 1726 01:51:34,140 --> 01:51:41,640 SDK. And I'm hoping to have more He's He's helping me and Alex to 1727 01:51:41,640 --> 01:51:45,420 get up and running with it so that we can mess around with it. 1728 01:51:45,960 --> 01:51:50,010 Hoping to get it to get my hands dirty with it. The one things I 1729 01:51:50,010 --> 01:51:56,370 say initially I don't I've read it. I've looked at the at the 1730 01:51:56,940 --> 01:52:01,380 sort of structure the way everything's laid out. If I 1731 01:52:01,380 --> 01:52:06,750 understand it correctly, it's extremely easy. Rust is a first 1732 01:52:06,750 --> 01:52:08,250 class citizen which alike? 1733 01:52:08,550 --> 01:52:09,870 Can you explain what it is? 1734 01:52:11,400 --> 01:52:15,390 It looks like exactly what we thought it would be, which is a 1735 01:52:15,390 --> 01:52:20,010 green light, the green light service on the back end, and 1736 01:52:20,040 --> 01:52:26,100 breeze providing the liquidity and everything on the front end. 1737 01:52:26,730 --> 01:52:32,190 And the SDK looks like a way a set of libraries to interface 1738 01:52:32,190 --> 01:52:37,680 your app with that service. And so you basically just, you 1739 01:52:37,680 --> 01:52:44,640 initialize it with a with a key and call and basically start 1740 01:52:45,000 --> 01:52:48,510 start it start the what is what is I guess? I don't know if 1741 01:52:48,510 --> 01:52:52,050 there's a real node or virtual node? I'm not sure. Essentially, 1742 01:52:52,050 --> 01:52:56,160 then you just you get back what looks like a handle that you can 1743 01:52:56,160 --> 01:52:57,630 then just do things with. 1744 01:52:57,930 --> 01:52:59,640 And you still haven't told us what it is. 1745 01:53:00,780 --> 01:53:04,020 I mean, it's an SDK. I know but what software development kit 1746 01:53:04,050 --> 01:53:09,090 No, I understand but I know I just want to hear is it like a 1747 01:53:09,090 --> 01:53:09,750 wallet? 1748 01:53:11,580 --> 01:53:17,430 No, yeah, well, he says that it's not a wallet, but it looks 1749 01:53:17,430 --> 01:53:22,440 like you I mean, you you own the key the for it looks like the 1750 01:53:22,440 --> 01:53:25,380 first thing you do. When I was looking at it earlier, the first 1751 01:53:25,380 --> 01:53:31,350 thing you do is initialize your your kind of using these terms 1752 01:53:32,100 --> 01:53:36,330 backup. Okay, there's a lightning node let's just call 1753 01:53:36,330 --> 01:53:40,620 I'm gonna call it a virtual lightning node that you can use 1754 01:53:40,620 --> 01:53:43,920 to send and receive lightning payments. 1755 01:53:45,300 --> 01:53:51,060 I think that's fair as fair. As fair to me. Roy has probably 1756 01:53:51,060 --> 01:53:52,560 been like no y'all are idiots. 1757 01:53:53,250 --> 01:53:57,120 Well, I mean, what what does it replace? It replaces centralized 1758 01:54:00,480 --> 01:54:01,680 custody wallets? 1759 01:54:02,220 --> 01:54:08,430 Yes, it would have replaced something like ln PE L B. It 1760 01:54:08,430 --> 01:54:13,560 will replace the the the necessity to keep your wallet to 1761 01:54:13,560 --> 01:54:17,670 call and you're not calling you're not custodian you're not 1762 01:54:17,700 --> 01:54:21,780 you're in your wallet is not custodial. You own it the the 1763 01:54:21,810 --> 01:54:25,110 infrastructure that your wallet resides on and that the 1764 01:54:25,110 --> 01:54:28,980 liquidity travels through that is that that is owned by 1765 01:54:28,980 --> 01:54:29,550 somebody 1766 01:54:29,610 --> 01:54:32,940 that service right the liquidity that so it basically is taken 1767 01:54:32,940 --> 01:54:36,360 away. Okay, for me, it would be great because I know that 1768 01:54:36,360 --> 01:54:41,340 anything that comes in if I had that as my I could replace my 1769 01:54:41,370 --> 01:54:46,230 Umbro wallet that I used to receive booster grams with this. 1770 01:54:46,830 --> 01:54:53,490 And the benefit is it would always work theoretically. And 1771 01:54:53,880 --> 01:54:57,690 but no one can can just say oh curry that's it. We're done 1772 01:54:57,690 --> 01:55:01,680 because I own the keys to it and I can I also move it somewhere 1773 01:55:01,680 --> 01:55:03,540 else if I want, because I have the keys, 1774 01:55:04,110 --> 01:55:07,440 right you have the keys, and yeah, it's your it's your keys, 1775 01:55:07,440 --> 01:55:13,590 your coin. So you can, you can use their infrastructure without 1776 01:55:13,590 --> 01:55:18,270 risking having anything ever taken away from you other than 1777 01:55:18,270 --> 01:55:20,910 the service itself. And then if that happens, you just move 1778 01:55:20,910 --> 01:55:23,070 into, so you move it to your umbrella, right. 1779 01:55:23,070 --> 01:55:29,460 And because it's an SDK, you can put it into your mobile app, as 1780 01:55:29,460 --> 01:55:35,490 a developer, and you can even send but also receive Bitcoin on 1781 01:55:35,490 --> 01:55:41,010 your mobile app. Because without necessarily having your mobile 1782 01:55:41,010 --> 01:55:43,890 app open in the foreground, all that stuff, 1783 01:55:44,970 --> 01:55:49,950 I think of, I kind of think of it like running, running your 1784 01:55:49,950 --> 01:55:55,110 stuff on AWS, and all of your stuff is encrypted, and only you 1785 01:55:55,110 --> 01:55:59,640 have the keys. And if some, if one day, AWS decides to kick you 1786 01:55:59,640 --> 01:56:02,430 off their service, well, then that's fine. You just go over 1787 01:56:02,430 --> 01:56:04,770 here and write all your stuff with and take all your stuff. 1788 01:56:04,770 --> 01:56:08,460 And it's, they didn't take your stuff away. They just said, you 1789 01:56:08,460 --> 01:56:09,720 know, we're not going to run it. But you can 1790 01:56:09,720 --> 01:56:14,280 also if I wanted to have a vape service, I could have that that 1791 01:56:14,280 --> 01:56:17,280 SDK built into the software of my vape. And every single time I 1792 01:56:17,280 --> 01:56:18,930 hit the vape, he could send a payment. 1793 01:56:20,400 --> 01:56:21,480 Do this yes, 1794 01:56:21,509 --> 01:56:25,619 this is the stuff I think of that. That's how I think at 1795 01:56:25,619 --> 01:56:28,679 night. Wow. Wouldn't it be cool if we could vape as a service? 1796 01:56:28,679 --> 01:56:29,669 Mm hmm. 1797 01:56:29,700 --> 01:56:33,210 Well, we've already got the feed your sheep thinks. This makes a 1798 01:56:33,210 --> 01:56:37,620 lot of a lot. I didn't see feed your sheep on loan Roy's 1799 01:56:37,620 --> 01:56:41,700 article. And in his idea starter section, like and a little bit, 1800 01:56:41,760 --> 01:56:45,870 I have the article in the show notes. It's, it's really cool. 1801 01:56:46,020 --> 01:56:48,480 We clearly need we 1802 01:56:48,480 --> 01:56:55,200 need ROI. We need ROI to talk to us ROI come talk to us as soon 1803 01:56:55,200 --> 01:56:58,290 as possible, because this is a game changer now is all because 1804 01:56:58,290 --> 01:57:02,880 I saw you were looking at it as all work as implicit functioning 1805 01:57:02,880 --> 01:57:03,990 now, is it 1806 01:57:04,650 --> 01:57:08,280 a startup, a test project, a demo project. And I was going to 1807 01:57:08,280 --> 01:57:12,330 get around and play with it. And I went in I couldn't find the 1808 01:57:13,170 --> 01:57:17,730 packages were not in the repos like public repos for the for, 1809 01:57:18,540 --> 01:57:21,540 for anything. And he said for now that you have to build it 1810 01:57:21,540 --> 01:57:24,570 off the off the GitHub source, so that's fine. But then he's 1811 01:57:26,850 --> 01:57:31,230 he's going to do what he needs to do to give me and Alex access 1812 01:57:31,530 --> 01:57:35,400 to the green light. That is a two parter, it looks like if I 1813 01:57:35,400 --> 01:57:37,320 understand it correctly, as a two parter, you have the breeze 1814 01:57:37,320 --> 01:57:42,000 SDK code itself. But then you need a green light library to 1815 01:57:42,000 --> 01:57:45,900 put with it. But the green light code is not open source yet it's 1816 01:57:45,900 --> 01:57:49,290 going to be, but they haven't released it yet. So they're the 1817 01:57:49,800 --> 01:57:54,360 so he needs to give us access to the green light code. So that we 1818 01:57:54,360 --> 01:57:59,400 can actually build the SDK. So he's gonna, he's, he's gonna 1819 01:57:59,400 --> 01:58:02,700 give us access to that code, then I'll build it. I'll make 1820 01:58:02,700 --> 01:58:05,670 some test projects with it. And I'll be able to speak more 1821 01:58:05,670 --> 01:58:09,030 intelligently about it. Once that happens. It looks cool, 1822 01:58:09,030 --> 01:58:10,050 though. Very cool. 1823 01:58:10,350 --> 01:58:13,350 I'm excited about it. I'm very excited. I mean, something we've 1824 01:58:13,350 --> 01:58:18,330 been needing for a long time in this space, in lots of space, 1825 01:58:18,330 --> 01:58:20,640 and we can be in anything. I mean, that's what I like about 1826 01:58:20,640 --> 01:58:23,250 the SDK, put into a vending machine, put it into whatever 1827 01:58:23,280 --> 01:58:25,800 wherever you want it. That's that's a cool system. 1828 01:58:26,070 --> 01:58:28,860 One thing I like about the lightning ecosystem is the in 1829 01:58:28,890 --> 01:58:32,640 the way that is evolving, is that in I think, maybe the 1830 01:58:32,640 --> 01:58:37,080 lightning, the LDK thing was the first person, the first group to 1831 01:58:37,080 --> 01:58:40,710 kind of embrace this idea. Is that is you're, you're you're 1832 01:58:40,710 --> 01:58:44,430 taking, you're taking a node, and then you're splitting it 1833 01:58:44,430 --> 01:58:46,620 into its component parts. And you're saying, okay, these are 1834 01:58:46,620 --> 01:58:48,900 all the different things that when brought together 1835 01:58:48,900 --> 01:58:52,590 constituent constitute what a node is, but you blow them 1836 01:58:52,590 --> 01:58:55,710 apart, and you can say, Okay, I'll do this part over here, 1837 01:58:55,710 --> 01:58:57,810 this part over here, I'm going to replace this with a with a 1838 01:58:57,810 --> 01:59:02,160 different database, I'm going to use this as an LSP. It's like 1839 01:59:02,160 --> 01:59:04,920 you, you can mix and match these component parts. And what you 1840 01:59:04,920 --> 01:59:08,100 end up with is still a functional node, right? But it's 1841 01:59:08,100 --> 01:59:11,340 just kind of like, it's like deconstructed, and you're 1842 01:59:11,340 --> 01:59:13,380 running it in different ways. And I think they're taking I 1843 01:59:13,620 --> 01:59:16,050 think what breezes done is they're taking advantage of this 1844 01:59:16,530 --> 01:59:21,210 concept of deconstructed node. And they're putting in there, 1845 01:59:21,300 --> 01:59:26,070 they're using that as a service provider model, right? So you 1846 01:59:26,070 --> 01:59:29,490 still get all the benefits of running your own node? Well, 1847 01:59:30,000 --> 01:59:33,180 technically, not all because you, you know, you could be, you 1848 01:59:33,180 --> 01:59:36,060 know, you could be kicked off or whatever. I mean, if they don't 1849 01:59:36,060 --> 01:59:40,110 want to host you, but you're getting most of the benefits of 1850 01:59:40,110 --> 01:59:42,930 running your own node, the privacy the, excuse me, the key 1851 01:59:42,960 --> 01:59:47,430 key management. Yeah. The security of funds, you know, the 1852 01:59:47,460 --> 01:59:50,100 benefit of having an always on up 1853 01:59:50,130 --> 01:59:53,910 like, like an email service provider versus hosting your own 1854 01:59:53,910 --> 01:59:54,330 email. 1855 01:59:54,960 --> 01:59:57,480 Yeah, for sure. For sure. Yeah. You mean 1856 01:59:57,480 --> 01:59:58,290 100%? 1857 01:59:59,250 --> 02:00:01,860 No, I mean, And then unconditional 1858 02:00:01,920 --> 02:00:07,530 unconditionally. All the way. Right on. Exhausted. Oh my 1859 02:00:07,530 --> 02:00:10,350 brother is that I gotta get you out of here with two hours on 1860 02:00:10,350 --> 02:00:15,300 the nose two hours on the nose. No. Well, hoping you feel even 1861 02:00:15,300 --> 02:00:20,520 better hoping the beef milk makes the beef milkshakes do 1862 02:00:20,520 --> 02:00:21,330 their business. 1863 02:00:21,809 --> 02:00:24,329 I get I get I always feel better after the show. I get an 1864 02:00:24,329 --> 02:00:25,889 adrenaline pump during the show. 1865 02:00:26,429 --> 02:00:28,739 All right, thank you very much chat room. Thanks, everyone who 1866 02:00:28,739 --> 02:00:30,899 was hanging out with us. Let Dave Brother Love you. We'll 1867 02:00:30,899 --> 02:00:33,719 talk to her next week. All right, man. See, okay. 1868 02:00:34,949 --> 02:00:37,439 Podcasting. 2.0 the board meeting on the books. We'll be 1869 02:00:37,439 --> 02:00:40,649 back in seven days from now to tell you all that's going on 1870 02:00:40,649 --> 02:00:43,229 come back for podcasting 2.0 1871 02:00:57,900 --> 02:01:02,460 You have been listening to podcasting 2.0 Visit podcast 1872 02:01:02,460 --> 02:01:05,010 index.org For more information