Episode 74: Confetti Canon

1 00:00:00,599 --> 00:00:06,329 podcasting 2.0 for February 18 2020, to Episode 74 We got a 2 00:00:06,329 --> 00:00:07,289 confetti cannon 3 00:00:09,300 --> 00:00:10,920 spewing SATs everywhere 4 00:00:12,509 --> 00:00:15,749 Hello everybody. Welcome to the official board meeting of 5 00:00:15,749 --> 00:00:20,219 podcasting. 2.0 everything happening at podcast index.org 6 00:00:20,519 --> 00:00:25,199 podcasting 2.0 namespace and of course all the stuff happening 7 00:00:25,229 --> 00:00:30,659 at that wonderful root of creativity podcast index dot 8 00:00:30,659 --> 00:00:33,059 social I'm Adam curry here in the heart of the Texas Hill 9 00:00:33,059 --> 00:00:36,269 Country and in Alabama my midnight midnight upgrade from 10 00:00:36,269 --> 00:00:38,969 bed buddy, my friend on the other end ladies and gentlemen, 11 00:00:38,969 --> 00:00:40,589 Mr. Dave Jones. 12 00:00:42,060 --> 00:00:44,490 Okay, that was the weirdest. Yeah, and I 13 00:00:45,630 --> 00:00:48,510 was bad. It was best the Rhona man, it's like everything's off 14 00:00:48,510 --> 00:00:53,970 the rails. You're one tick one tick too slow and you got to 15 00:00:54,270 --> 00:00:58,050 give me your brain as I knew exactly how it feels. But I was 16 00:00:58,050 --> 00:01:01,500 in bed last night upgrading heli pad from my phone. I thought 17 00:01:01,500 --> 00:01:02,250 that was badass. 18 00:01:03,750 --> 00:01:05,160 From the phone SSH. 19 00:01:06,210 --> 00:01:09,690 You know what the hardest part is? is trying to copy and then 20 00:01:09,690 --> 00:01:12,480 paste in VI on your 21 00:01:13,680 --> 00:01:17,430 your phone terminal. Yeah, that's that's always that does 22 00:01:17,430 --> 00:01:20,220 not sound easy. No, it wasn't when it's like suddenly 23 00:01:20,220 --> 00:01:26,820 humongous long Sha 256 Well, it was the the Docker dot YAML 24 00:01:26,820 --> 00:01:32,790 thing that I had to change to typing Docker dot Yeah. Mo, like 25 00:01:32,820 --> 00:01:36,090 just typing that entire thing out on a phone. No, no, no, no. 26 00:01:36,090 --> 00:01:40,200 D tab. Not all works. I mean, all the all the shortcuts work. 27 00:01:40,200 --> 00:01:41,130 I love that part. 28 00:01:42,180 --> 00:01:46,080 Yeah, I guess the phone keyboard hashtag. Yeah, it's I'm using 29 00:01:46,590 --> 00:01:48,600 was it Terminex? I think 30 00:01:49,860 --> 00:01:52,320 Terminus Terminus. Yeah. Yeah. Terminal. 31 00:01:53,340 --> 00:01:56,850 Okay. Yeah, the standard keyboard. It's got its own built 32 00:01:56,850 --> 00:02:00,390 in. Yeah, yes. Okay. You can determine what special keys you 33 00:02:00,390 --> 00:02:03,330 want above the keyboard. So you can have your arrow keys and 34 00:02:03,330 --> 00:02:07,440 yeah, basically, I want to have escaped control tab, and then I 35 00:02:07,440 --> 00:02:09,480 can slide over to get all the arrow keys. 36 00:02:10,830 --> 00:02:15,180 Yeah, yeah. I know. I'm sick. Literally and figuratively. 37 00:02:15,210 --> 00:02:19,080 Yeah. Date run out of date. We're gonna update. You know, 38 00:02:19,080 --> 00:02:21,120 this morning. I woke up this is day 11. 39 00:02:22,410 --> 00:02:26,370 I went back and look day 11 At least him taking medication for 40 00:02:26,370 --> 00:02:26,850 it. So 41 00:02:28,200 --> 00:02:31,140 I woke up did not have night sweats. This is a huge 42 00:02:31,140 --> 00:02:36,300 improvement. Great. Yeah. So anyway, I'm just wearing now 43 00:02:36,300 --> 00:02:38,880 because of the well first of all you were telling me about? Well, 44 00:02:38,880 --> 00:02:42,540 you know, second wave was like everyone's got a story to vor X 45 00:02:42,540 --> 00:02:46,020 telling me about his kid. What was a month like? Okay, so I'm 46 00:02:46,020 --> 00:02:47,940 just waiting for the fatigue to hit me. Right. 47 00:02:48,990 --> 00:02:51,810 And then of course, yesterday we hear from the slate podcast, 48 00:02:51,810 --> 00:02:55,290 there's such a such thing as COVID Dick and their words not 49 00:02:55,290 --> 00:02:55,740 mine. 50 00:02:56,760 --> 00:02:59,670 What is that? It's erectile dysfunction baby. 51 00:03:02,160 --> 00:03:06,840 It's not funny because just the fact that women were talking but 52 00:03:06,840 --> 00:03:09,570 these women were talking about it. So you know, guys like that 53 00:03:09,570 --> 00:03:12,960 should gets in your head. It's like a win. Win. We're talking 54 00:03:12,960 --> 00:03:16,500 about like, like, I'm gonna have to get a divorce. Oh, no, man. 55 00:03:16,530 --> 00:03:20,580 Go listen, there's no agenda. It was bad enough there. I don't 56 00:03:20,580 --> 00:03:23,970 want to. I don't want to pollute anything here. People people 57 00:03:23,970 --> 00:03:27,960 emailing me like, Hey, man, are you okay? No, no, it's just a 58 00:03:27,960 --> 00:03:31,320 story. Okay, it's just a new story. Are you 59 00:03:33,630 --> 00:03:38,010 sending love Love and Light anyway? Anyway, Dave the new 60 00:03:38,010 --> 00:03:40,140 heli pad version 1.9. 61 00:03:41,310 --> 00:03:45,870 Yeah, kicks still doesn't do what your CSV export we will get 62 00:03:45,870 --> 00:03:48,840 there. We'll fix that fix. I don't understand that. Can we 63 00:03:48,840 --> 00:03:51,750 talk about that for a second? Because sure did. Okay, so let 64 00:03:51,750 --> 00:03:55,710 me pull up my pad. Here. We ladies and gentlemen, the gloves 65 00:03:55,710 --> 00:03:59,520 are off. We're pulling up our heli pads. This is how it all 66 00:03:59,520 --> 00:04:02,160 goes downhill but taking off 67 00:04:03,540 --> 00:04:07,020 well, I guess for a helipad up landing not taking off well that 68 00:04:07,020 --> 00:04:10,470 dependents that dependent goes both directions. Yes, of course. 69 00:04:11,280 --> 00:04:17,550 I'm so on my yellow pad. What happens is okay, here's here's 70 00:04:17,550 --> 00:04:21,270 the the algo or whatever, let me let me explain the problem. 71 00:04:21,720 --> 00:04:27,180 Okay, so I have there's a CSV export which has been built in 72 00:04:27,180 --> 00:04:30,900 which is very important as a podcaster so that you can output 73 00:04:30,960 --> 00:04:34,530 the booster grams and be able to thank people I have 74 00:04:36,660 --> 00:04:42,990 SATs coming in whether full on or just like 1% just to be able 75 00:04:42,990 --> 00:04:46,650 to get the booster grams from four different shows. And 76 00:04:47,790 --> 00:04:51,540 so when and some of them I do on a 14 day basis so when I'm going 77 00:04:51,540 --> 00:04:55,320 in to get the most facts booster grams, I have to go back a full 78 00:04:55,320 --> 00:04:59,850 two weeks and I wasn't because I have so many booster grams it 79 00:04:59,850 --> 00:05:00,000 just 80 00:05:00,000 --> 00:05:03,960 it, I wasn't able to go back far enough for whatever it was 81 00:05:05,279 --> 00:05:06,659 in the in the output. 82 00:05:08,069 --> 00:05:11,909 And so guys, I think, yeah, initially it was just 100. I 83 00:05:11,909 --> 00:05:14,909 think it was just like a hard coded, right, which is, which is 84 00:05:14,909 --> 00:05:15,839 like a week for me. 85 00:05:17,070 --> 00:05:18,690 Right? Yeah. So 86 00:05:19,800 --> 00:05:23,310 the way it's supposed to work, and I checked it this morning, 87 00:05:23,310 --> 00:05:26,160 and mine was working this way. So I still don't know what the 88 00:05:26,190 --> 00:05:31,470 discrepancy is. But the way it's supposed to work is every one of 89 00:05:31,470 --> 00:05:34,950 the items that you see on the screen has a message ID attached 90 00:05:34,950 --> 00:05:39,510 to it. And that message ID is the index number of the invoice 91 00:05:39,510 --> 00:05:40,440 within lnd. 92 00:05:41,640 --> 00:05:46,050 Okay, and what happens is, Hello, Pat is constantly keeping 93 00:05:46,050 --> 00:05:49,320 in sync with lnd every few seconds, it pulls lnd 94 00:05:49,740 --> 00:05:53,490 eventually, this will be a G RPC stream. That's bad now, because 95 00:05:53,490 --> 00:05:59,700 badass like that. Right? Yes. So it's polling and it says it just 96 00:05:59,700 --> 00:06:03,360 says any new invoices, you know, and then when it has some, it 97 00:06:03,360 --> 00:06:08,340 pulls them in. Now these are all the invoices. So your l&d 98 00:06:09,780 --> 00:06:15,810 Most current invoice index number should be the same in 99 00:06:15,810 --> 00:06:20,280 hell pad, they should both be matching all the time. So what 100 00:06:20,340 --> 00:06:24,420 happens in hell pad is if you ex, when you, when you load the 101 00:06:24,420 --> 00:06:27,330 screen initially, it just takes the most current invoice index 102 00:06:27,330 --> 00:06:31,380 number. It shows you all of them back like I don't think it's 103 00:06:31,380 --> 00:06:35,910 like initially Okay, 100. Then if you hit low, show more it, it 104 00:06:35,910 --> 00:06:37,800 just says, Okay, show me anything older and blah, blah, 105 00:06:37,800 --> 00:06:38,100 blah. 106 00:06:39,120 --> 00:06:39,600 Well, 107 00:06:40,680 --> 00:06:44,640 the display, there's a discrepancy with with between 108 00:06:44,640 --> 00:06:47,790 what the index numbers are on each boost in the list on Hello 109 00:06:47,790 --> 00:06:53,070 pad. And what how many invoices you might actually have, because 110 00:06:53,070 --> 00:06:57,690 help had only shows boosts not streaming payments, right. So 111 00:06:57,690 --> 00:06:58,920 there's gaps in there. 112 00:07:00,780 --> 00:07:04,500 So the way that it works currently is when you export the 113 00:07:04,500 --> 00:07:10,560 CSV, it, it takes its initial index number from the very top 114 00:07:10,560 --> 00:07:12,480 most boosts you see on the screen. 115 00:07:13,680 --> 00:07:17,280 And then it looks at whatever the last boost in the list is, 116 00:07:18,240 --> 00:07:23,010 and subtracts the last boost number from the boost number at 117 00:07:23,010 --> 00:07:29,160 the top to get a total number of booths to export. Okay, so if 118 00:07:29,160 --> 00:07:33,120 your top most number is 150, and the bottom most number is 75, 119 00:07:33,540 --> 00:07:38,430 the count will be 75. So it'll say Export starting at index 120 00:07:38,430 --> 00:07:42,780 150. And the count give me 75 boosts going backwards. 121 00:07:44,250 --> 00:07:48,750 That should give you it actually should give you more than what 122 00:07:48,750 --> 00:07:51,690 you see on the screen, because you're gonna have more than 75 123 00:07:51,690 --> 00:07:56,010 boosts in the output, because there's gonna be streams in 124 00:07:56,010 --> 00:07:59,970 there, too. So what you should see is you should see everything 125 00:07:59,970 --> 00:08:04,380 you see on the screen, probably plus some. But you're saying 126 00:08:04,380 --> 00:08:07,680 that you don't see that? No seeing less than what you see on 127 00:08:07,680 --> 00:08:11,250 the screens? Yeah, I just tried it. I just did an export. So you 128 00:08:11,250 --> 00:08:15,270 know, fresh on heavy pad. And just browsers never seen 1.9 129 00:08:15,270 --> 00:08:23,610 just minimize everything. And I hit more more boost twice. So 130 00:08:23,610 --> 00:08:26,280 the bot and it gave you boost eight, but each time did you hit 131 00:08:26,280 --> 00:08:30,060 it it gave you more? Yes, yes, that works. And so now I'm on 132 00:08:30,060 --> 00:08:35,010 the list, I'm down to 14 January, on the list at the 133 00:08:35,010 --> 00:08:37,350 bottom, and I'm just leaving my browser where it is I'm not 134 00:08:37,350 --> 00:08:39,180 going to the top, I'm just staying at the bottom, it 135 00:08:39,180 --> 00:08:42,660 shouldn't make any difference, I presume, no case, and I hit 136 00:08:42,660 --> 00:08:48,000 Export, and then the CSV and I opened it up. And the top number 137 00:08:48,510 --> 00:08:56,370 is from today 18th of February the index numbers 37,937. 138 00:08:57,450 --> 00:09:03,600 And the bottom of this list is February 1, and the index 139 00:09:03,600 --> 00:09:08,220 numbers 28,008 61. And this is what I get consistently no 140 00:09:08,220 --> 00:09:11,580 matter how many I expose in the in the web UI. 141 00:09:15,660 --> 00:09:22,650 I know well, this is clearly wrong. So what I'm going to need 142 00:09:22,650 --> 00:09:24,690 your database is what I'm going to need so I can figure this 143 00:09:24,690 --> 00:09:26,850 out. Hey, if you can have my database you can have my 144 00:09:26,850 --> 00:09:29,100 firstborn you can have whatever you want. 145 00:09:32,370 --> 00:09:36,870 Please take my firstborn. Let's start with the database and then 146 00:09:37,710 --> 00:09:39,990 work backwards from there. Yeah. 147 00:09:41,040 --> 00:09:46,410 Okay. Yeah, I'll give my you have significantly more invoices 148 00:09:46,410 --> 00:09:49,020 in there. Yeah, I'm a booster. You are. 149 00:09:50,130 --> 00:09:54,720 You have significantly more more invoices than anything in any 150 00:09:54,840 --> 00:09:57,900 that I've tested. But the math should be the same. I don't. I 151 00:09:57,900 --> 00:09:59,460 don't understand why it would be 152 00:10:00,000 --> 00:10:03,540 problem maybe? Well, the only thing as you were explaining 153 00:10:03,540 --> 00:10:06,240 that to me, I was hearing gaps. You know, of course, there's 154 00:10:06,240 --> 00:10:11,340 tons of gaps in in my data in the past three weeks. The Umbral 155 00:10:11,340 --> 00:10:14,490 definitely has crapped out a couple times. So I don't know if 156 00:10:14,490 --> 00:10:18,270 that makes a difference. But this was this was in essence, a 157 00:10:18,270 --> 00:10:22,020 fresh install. I mean, I edited my Docker dot Yamo. 158 00:10:23,310 --> 00:10:27,270 He did. And I saw it parse. I mean, and all the boosts are in 159 00:10:27,270 --> 00:10:28,680 there going back to November. 160 00:10:32,400 --> 00:10:32,790 Okay, 161 00:10:33,960 --> 00:10:37,110 so I don't understand that. Yeah, moss, I'll send you my 162 00:10:37,110 --> 00:10:39,960 database. It's okay. How many total entries are in that? May? 163 00:10:39,960 --> 00:10:44,520 It should be a bunch. I mean, it's when you x 209. Okay. 164 00:10:47,100 --> 00:10:50,790 It's so it's getting you what you need for now, but it's just 165 00:10:50,790 --> 00:10:53,910 not it's just not giving you it's not? Right. Correct. It's 166 00:10:53,910 --> 00:10:56,790 beautiful. By the way, it's beautiful. 167 00:10:57,810 --> 00:11:02,070 When you export is great. Really love it. Are you pulling it into 168 00:11:02,070 --> 00:11:06,150 Excel? Yeah, I've tried XL and libra office. 169 00:11:07,500 --> 00:11:12,360 Okay, so in Excel? Are you just right clicking and opening it? 170 00:11:12,360 --> 00:11:15,960 Or are you using the data CSV import? I'm right clicking and 171 00:11:15,960 --> 00:11:21,420 opening it. Okay, I do data CSV import. Yes. So instead of doing 172 00:11:21,420 --> 00:11:26,820 that, open up Excel by itself, then go to the Data tab. Ooh, 173 00:11:26,820 --> 00:11:29,640 hold on. This is sexy because let's let's do it live. I like 174 00:11:29,640 --> 00:11:34,350 this. Yes, zoo. Okay, I got new new workbook. Okay, what people 175 00:11:34,350 --> 00:11:36,570 love to listen to this other people talking about how to do 176 00:11:36,810 --> 00:11:41,940 this fun, sexy, okay, from text. CSV, right? I got that on the 177 00:11:41,940 --> 00:11:46,350 data tab and then and then pull in that file. Okay, hold on. I'm 178 00:11:46,350 --> 00:11:50,910 telling you. It looks awesome. Oh, this is interesting. Okay, 179 00:11:50,940 --> 00:11:56,580 here we go. Yeah. Was it damn with pivot tables? No, no. Stop, 180 00:11:56,580 --> 00:12:01,140 stop. You're kidding me? No, the emojis are the whole thing is 181 00:12:01,140 --> 00:12:04,830 beautiful. As Should I just hit Load or transform data? What 182 00:12:04,830 --> 00:12:08,580 does this load load? Yeah. I'm gonna give you that full load 183 00:12:08,700 --> 00:12:13,500 the whole load. Oh, wow. I've never seen Oh, whoa, whoa, that 184 00:12:13,500 --> 00:12:14,490 was really cool. 185 00:12:15,570 --> 00:12:18,120 It's all green. It has Yeah. 186 00:12:21,090 --> 00:12:24,450 Now let me see. Yeah, and look at the pivot tables. It's up you 187 00:12:24,450 --> 00:12:28,380 can sort and isolate just individual shows. This is 188 00:12:28,380 --> 00:12:33,240 exactly what I needed. Now. I'm still unfortunately, only 189 00:12:33,240 --> 00:12:36,420 getting to up until February 1 209 records. 190 00:12:38,250 --> 00:12:38,790 I know. 191 00:12:41,460 --> 00:12:44,760 Okay, and someone is sending the wrong shit. Who's sending this 192 00:12:44,790 --> 00:12:48,870 who's sending is what's wrong? Someone's sending something the 193 00:12:48,870 --> 00:12:52,710 wrong way. Fountain seems to be weird sometimes. 194 00:12:54,450 --> 00:12:57,150 No, that could just be spill over the field I guess. Okay, 195 00:12:57,180 --> 00:12:58,290 Oscar. 196 00:13:02,520 --> 00:13:06,420 Your Podcast Okay, so I can sort by this. That's my pivot table. 197 00:13:06,900 --> 00:13:09,960 Oh my goodness. If you get to the top of the podcast called 198 00:13:10,290 --> 00:13:13,230 dad like you can just say only show me more facts or only show 199 00:13:13,230 --> 00:13:19,710 me this. Oh, gosh. Ah, sexy. Yeah. In that awesome. It looks 200 00:13:19,710 --> 00:13:23,340 so much better than that stupid raw CSV import that though it 201 00:13:23,340 --> 00:13:26,100 does if you right click is it this is an Excel thing though. 202 00:13:26,100 --> 00:13:31,380 Excel does this for you, Microsoft. I hate you. Okay. 203 00:13:32,460 --> 00:13:35,550 All right. That's cool. Dave That is yeah, that that makes 204 00:13:35,550 --> 00:13:38,970 all the difference. We just need a well I of course what I've 205 00:13:38,970 --> 00:13:42,660 done is like a little translator table for the current bitcoin 206 00:13:42,660 --> 00:13:47,640 price to change the milli SATs into fee formulas. Yeah. Oh, 207 00:13:47,640 --> 00:13:48,120 yeah. 208 00:13:49,530 --> 00:13:52,320 Deep into formulas. Oh, yeah. I'm hacking this spreadsheet 209 00:13:52,320 --> 00:13:52,710 Dave. 210 00:13:55,080 --> 00:13:58,050 are going away. Okay, so it's so it's just a matter of that. 211 00:13:58,050 --> 00:14:01,980 Anyway, forget all that. Congratulations on the release 212 00:14:01,980 --> 00:14:05,130 because it's version 0.19 I should say. 213 00:14:06,840 --> 00:14:10,410 You really nailed what podcasters need. 214 00:14:11,670 --> 00:14:15,300 Someone tweeted. Someone tweeted earlier today. I don't know who 215 00:14:15,300 --> 00:14:19,110 it was Tina saw too. And, and the tweet was something like, 216 00:14:19,230 --> 00:14:25,620 Hey, I made you know 350,000 SATs last month compared to $27 217 00:14:25,650 --> 00:14:29,760 I usually make with advertising I'm never looking back. Oh yeah, 218 00:14:29,760 --> 00:14:32,760 that was Kevin rook from Kevin roach. dadoes Kevin rook right? 219 00:14:32,880 --> 00:14:38,760 Yeah and and so not only don't forget don't forget the the end 220 00:14:38,760 --> 00:14:42,420 of the post which he said and it takes forever to get your check 221 00:14:42,420 --> 00:14:45,510 from you. Yes. Instant settlement here. Exactly. 222 00:14:47,250 --> 00:14:51,660 What is so beautiful now with heli pad is exactly I had a 223 00:14:51,660 --> 00:14:53,940 problem. I was always worried that you know, my tour thing 224 00:14:53,940 --> 00:14:57,210 isn't working. So every morning I'm boosting myself which as we 225 00:14:57,210 --> 00:14:59,970 know is illegal and 1737 states 226 00:15:00,000 --> 00:15:02,430 The United States way to start a day though 227 00:15:05,069 --> 00:15:06,599 it is kind of an eye opener 228 00:15:10,170 --> 00:15:13,200 Hey, there we are, Dave it's gone downhill since the COVID. 229 00:15:13,200 --> 00:15:16,500 Dick sorry about that. Yeah. Never should have brought that 230 00:15:16,500 --> 00:15:16,710 in. 231 00:15:18,600 --> 00:15:23,010 So now you see this the your your balance up top. And and 232 00:15:23,010 --> 00:15:27,000 then when a stream a payment comes in, it pulsates. And 233 00:15:27,000 --> 00:15:31,350 confetti spews over the screen, it is on brand it is on message. 234 00:15:31,500 --> 00:15:36,930 And it makes me feel good. It makes it as a podcast or as a 235 00:15:36,930 --> 00:15:41,460 lifelong broadcaster since I was 13. The only thing you want to 236 00:15:41,460 --> 00:15:45,900 know is how far does my signal reach? He's someone listener. So 237 00:15:46,020 --> 00:15:49,230 when we had the ability to connect the phone line, yeah, I 238 00:15:49,230 --> 00:15:51,390 was like, Oh, someone's listening. They called me but 239 00:15:51,390 --> 00:15:55,590 now you see the listening. Podcasting 2.0 See the 240 00:15:55,590 --> 00:15:56,250 listening. 241 00:15:57,660 --> 00:16:02,790 Running with Scissors. See the listening is exciting is all 242 00:16:02,790 --> 00:16:07,050 hell. So I took the confetti out of the stream because I was 243 00:16:07,050 --> 00:16:10,440 afraid the background stream payments because I'm afraid that 244 00:16:10,440 --> 00:16:14,550 if if like four or five people are streaming all or more 245 00:16:14,550 --> 00:16:17,520 streaming all at once, it would just be this confetti, you know, 246 00:16:18,060 --> 00:16:22,140 just this constant so when what triggers it then isn't a new 247 00:16:22,140 --> 00:16:25,500 payment isn't to boost the boost. So only boost trigger 248 00:16:25,500 --> 00:16:28,530 confetti, the background streams now only just flashed the 249 00:16:28,530 --> 00:16:33,360 balance update. So did you know that somebody know is going but 250 00:16:33,360 --> 00:16:36,630 it's but I'm getting? I'm getting a confetti with the 251 00:16:36,630 --> 00:16:40,410 balance update. Boom, there go. Are you? Yep. And I like it. 252 00:16:41,130 --> 00:16:44,730 Okay, well don't take my confetti away. All right. No, it 253 00:16:44,730 --> 00:16:49,800 makes me makes me happy. It's done. Done. We fix that bug is 254 00:16:49,800 --> 00:16:50,490 stopped. 255 00:16:51,690 --> 00:16:54,990 So was it supposed to not not be doing that this is maybe there's 256 00:16:54,990 --> 00:16:59,070 something that didn't maybe some commit didn't take? I thought I 257 00:16:59,070 --> 00:17:03,360 thought that it did it was but you know, if you've ever looked 258 00:17:03,360 --> 00:17:04,230 at my development 259 00:17:05,820 --> 00:17:10,200 system, you would understand why I forget what I've done and what 260 00:17:10,200 --> 00:17:13,770 I haven't. Because it's basically everything that Alice 261 00:17:13,770 --> 00:17:18,510 gates wants you to do. I do the exact opposite. And so it's no 262 00:17:18,510 --> 00:17:19,200 wonder that 263 00:17:20,700 --> 00:17:25,830 that that I do not remember what I did two days ago, I suggest we 264 00:17:25,830 --> 00:17:30,210 get some confirmation on this right away. Okay. And we bring 265 00:17:30,210 --> 00:17:33,390 in our guest board members who are who've been sitting 266 00:17:33,390 --> 00:17:35,100 patiently in the corner, of course. 267 00:17:37,590 --> 00:17:41,280 We get brought in the hummus for one of our guests just to just 268 00:17:41,280 --> 00:17:42,030 to piss him off. 269 00:17:43,260 --> 00:17:47,340 Ladies and gentlemen, please welcome to Royal board members. 270 00:17:47,700 --> 00:17:51,120 We have Sir Alex gates and Sir Brian of London joining us 271 00:17:51,120 --> 00:17:51,540 today. 272 00:17:53,160 --> 00:17:53,820 Hey, in the morning. 273 00:17:55,980 --> 00:17:59,160 Morning, in the morning, and more. Hey guys, how are you? 274 00:17:59,160 --> 00:18:00,120 Hey, guys. 275 00:18:02,460 --> 00:18:06,480 There we go. Is it true Alex that basically my every bit of 276 00:18:06,480 --> 00:18:09,870 my development style is basically antithetical to 277 00:18:10,050 --> 00:18:13,620 everything that you stand for, as a human being, well standing 278 00:18:13,620 --> 00:18:15,960 for it, like I've done this stuff myself, but when you want 279 00:18:15,960 --> 00:18:17,610 to get professional about it, then 280 00:18:19,260 --> 00:18:23,100 being accountable for your for what you work on. So just let's 281 00:18:23,100 --> 00:18:26,190 let's just nail down some brass tacks here for the people who 282 00:18:26,190 --> 00:18:29,640 aren't necessarily developers. What exactly could they be doing 283 00:18:29,640 --> 00:18:32,490 better at or as you would say out, like, I don't want to have 284 00:18:32,490 --> 00:18:36,480 this more professional would make him more professional. 285 00:18:37,980 --> 00:18:40,980 I'm already working on that. I already got him to switch to a 286 00:18:40,980 --> 00:18:44,460 GitHub project this week. Oh, okay. Oh, good now. 287 00:18:49,080 --> 00:18:51,780 Hey, guys, welcome. Glad to have you here in the board meeting. 288 00:18:53,190 --> 00:18:56,190 You have both of you actually been quite active with so much 289 00:18:56,190 --> 00:18:59,340 development that I don't know where we can start. Dave, you 290 00:18:59,340 --> 00:19:01,830 should probably help us in 291 00:19:02,970 --> 00:19:08,340 guide us. Well, I want I want one of you, or both at the exact 292 00:19:08,340 --> 00:19:13,800 same time to talk about just the just the most recent update with 293 00:19:13,800 --> 00:19:17,190 POD paying. And I've got a bunch of questions and stuff in to 294 00:19:17,190 --> 00:19:20,010 talk about with it. But I want to just some somebody give a 295 00:19:20,010 --> 00:19:20,760 real quick 296 00:19:22,110 --> 00:19:23,460 overview on where 297 00:19:24,510 --> 00:19:27,210 what the changes are and what the updates are between 1.0 and 298 00:19:27,210 --> 00:19:27,900 1.1. 299 00:19:29,580 --> 00:19:32,640 That's going to be Alec. I want to hear this one here about it 300 00:19:32,640 --> 00:19:35,910 in in your words. So succinct, and then we can dig in. 301 00:19:37,260 --> 00:19:40,620 Yeah, I can give you the first shot on Branchville. And what 302 00:19:40,620 --> 00:19:43,020 are we talking about for people who have no clue? 303 00:19:44,940 --> 00:19:48,180 Yeah, so we're talking about specifically the popping hybrid 304 00:19:48,180 --> 00:19:51,030 project that we're working on, which makes it easy. I mean, 305 00:19:51,030 --> 00:19:54,690 it's what Dave uses to write the piping right. Piping the cloud. 306 00:19:56,040 --> 00:19:59,670 Yep, that's the back end. Yeah. The most significant change for 307 00:19:59,700 --> 00:19:59,970 for 308 00:20:00,000 --> 00:20:06,210 For this version of pod ping, is we added reason codes, which I 309 00:20:06,210 --> 00:20:10,500 mean, we only had one reason code, which is it, a podcast was 310 00:20:10,500 --> 00:20:15,210 able to say no, we're gonna start a live stream, which we 311 00:20:15,210 --> 00:20:18,450 we've tested and worked worked out, we could even do for the 312 00:20:18,450 --> 00:20:22,920 shelf we wanted to. And then we also added medium codes, which 313 00:20:22,920 --> 00:20:27,780 allows you to say, this is the medium type of this feed. So if 314 00:20:27,780 --> 00:20:30,540 it's a video and an app doesn't support a video, they can choose 315 00:20:30,540 --> 00:20:31,080 to ignore it. 316 00:20:33,270 --> 00:20:36,270 Excellent, me. So and we're using that already with three 317 00:20:36,270 --> 00:20:40,950 speaks. So all of three speaks pod ping announcements now say 318 00:20:40,950 --> 00:20:45,180 that it's video. And it's an update, as opposed to just 319 00:20:45,180 --> 00:20:49,710 podcast, which would be more normal for audio. Well, is there 320 00:20:49,710 --> 00:20:53,010 a live? Is there a live functionality within three 321 00:20:53,010 --> 00:20:54,750 speak? Is that being used at all there? 322 00:20:55,800 --> 00:20:59,670 There? There isn't. But there is another streaming service 323 00:20:59,760 --> 00:21:01,980 loosely based around hive called 324 00:21:03,720 --> 00:21:08,730 Vim. Vim, yeah. vim.tv. And I'm talking with them, and they're 325 00:21:08,730 --> 00:21:12,060 interested in doing and they're a live streaming service, you 326 00:21:12,060 --> 00:21:16,080 know, a twitch replacement. And they're interested in looking at 327 00:21:16,080 --> 00:21:21,240 live for people listening to Alex and Brian are the 328 00:21:21,390 --> 00:21:25,290 essentially that y'all you guys are the ones who are writing all 329 00:21:25,290 --> 00:21:29,370 of the pot PIN code. That is there's a difference between pot 330 00:21:29,370 --> 00:21:35,340 pink cloud and pod pink proper pink cloud is is podcast index 331 00:21:35,340 --> 00:21:41,670 is hosted. Front end for for pod paying itself. Pod on paying 332 00:21:41,670 --> 00:21:45,780 really is the hive writer, the hive writer is what you can give 333 00:21:45,780 --> 00:21:48,960 it some information about a podcast, and it writes it to the 334 00:21:48,960 --> 00:21:51,540 hive blockchain so that it becomes publicly available 335 00:21:51,540 --> 00:21:55,860 everywhere for everybody to see. The public cloud is just a front 336 00:21:55,860 --> 00:21:59,100 end to hive writer to make it easy for people to get on board. 337 00:21:59,100 --> 00:22:02,280 And that's what I ping right with my script. Yes, yes, that's 338 00:22:02,280 --> 00:22:07,020 right. So so what Alex and Brian do they write, they write the 339 00:22:07,020 --> 00:22:11,820 code for the the low, the lower level high writer itself. 340 00:22:13,020 --> 00:22:17,850 So the there's going to be, so I'll take this one out of the 341 00:22:17,850 --> 00:22:20,640 way too, there's going to be a change, or there already has 342 00:22:20,640 --> 00:22:24,390 been a change to the way that the listeners the hive watchers. 343 00:22:25,170 --> 00:22:29,550 Neat, neat need to need to behave. I do want to run over 344 00:22:29,550 --> 00:22:30,630 that real quick, Alex? 345 00:22:32,250 --> 00:22:36,810 Yeah, so I guess the backup a little bit. In addition to the 346 00:22:36,810 --> 00:22:41,040 hive writer, we're also we've also taken the task of defining 347 00:22:41,040 --> 00:22:47,160 the piping protocol. And what what that's evolved from from 348 00:22:47,190 --> 00:22:50,280 from one point now is, originally we were just saying, 349 00:22:50,310 --> 00:22:54,480 hey, this RSS feed has been updated. A listener can was able 350 00:22:54,480 --> 00:23:00,780 to, to receive those feeds, and assume that their RSS feeds and 351 00:23:00,900 --> 00:23:05,250 parse them do whatever they want with them. What we added was the 352 00:23:05,250 --> 00:23:09,450 ability to discover what you know more information about that 353 00:23:09,450 --> 00:23:13,770 feed without sticking the entire feed itself into hive, which is 354 00:23:14,220 --> 00:23:17,490 kind of some people I think some people misunderstand what that 355 00:23:17,490 --> 00:23:20,370 is, like, we're not putting, we're not replacing your RSS 356 00:23:20,370 --> 00:23:24,030 feed at all. We're just saying, Hey, you could just you could 357 00:23:24,030 --> 00:23:28,950 tell people when it's been updated that as well as the 358 00:23:28,950 --> 00:23:31,590 entire history of every feed that's ever been updated. But 359 00:23:31,590 --> 00:23:35,220 wait a minute, Alex, I heard for sure on a different podcast. 360 00:23:35,220 --> 00:23:37,380 This was an RSS replacement thingy. 361 00:23:39,360 --> 00:23:42,210 I think they're mixing it up with RS three. Oh, yeah. Cuz 362 00:23:42,210 --> 00:23:46,110 that's, that's, that's really simple syndication, RSS three. 363 00:23:47,160 --> 00:23:51,270 Yeah. The simple part starts with the algebraic equations 364 00:23:51,270 --> 00:23:53,760 that you need to understand in white paper. 365 00:23:54,810 --> 00:23:57,120 Right. Sorry, I didn't even didn't mean to interrupt, but 366 00:23:57,120 --> 00:24:01,350 it's this is a good as they call it explainer? Well, this is all 367 00:24:01,410 --> 00:24:05,130 also not web three. So I'll throw that well. Fuck, fuck the 368 00:24:05,130 --> 00:24:09,120 terms. i We are so web three, it hurts. Come on. I mean, if you 369 00:24:09,120 --> 00:24:10,500 really want to talk about it, 370 00:24:11,760 --> 00:24:18,300 I'll tell you what, what this is the what popping is doing is it 371 00:24:18,300 --> 00:24:21,150 gives us a way to make these announcements these and the 372 00:24:21,150 --> 00:24:24,960 announcement is purely this has changed. That's it. And we've 373 00:24:24,960 --> 00:24:28,560 just added with the new with the new sort of protocol change in 374 00:24:28,560 --> 00:24:31,200 the background that Alex talking about. We've added weights just 375 00:24:31,200 --> 00:24:34,980 to say just a little bit more information not too much. And it 376 00:24:34,980 --> 00:24:37,920 just, you know, it allows you to filter a little bit more 377 00:24:39,690 --> 00:24:43,200 with a with a little bit of ease. And but essentially it's 378 00:24:43,200 --> 00:24:45,990 just saying go pull this feed, it's made a change if you're 379 00:24:45,990 --> 00:24:50,040 interested in this feed. That's it. And that's the bit that's 380 00:24:50,460 --> 00:24:53,520 that's carrying on and it's been running you know nonstop now 381 00:24:53,520 --> 00:24:58,800 what for nine months, 10 months. It's it's quite I'm impressed 382 00:25:00,000 --> 00:25:02,250 I'm impressed with the back end of the, you know, the pod pink 383 00:25:02,280 --> 00:25:06,480 cloud front end that that you've got day running for it. But 384 00:25:06,510 --> 00:25:11,040 that, you know, the issue with that is that's the bit that's 385 00:25:11,040 --> 00:25:14,220 not decentralized, but the whole system itself is going to be 386 00:25:14,220 --> 00:25:17,970 decentralized. You know, one day we're going to have these these 387 00:25:18,000 --> 00:25:21,930 entities like the hosts writing directly to the hive blockchain, 388 00:25:21,930 --> 00:25:23,520 because it's really not that difficult. 389 00:25:24,960 --> 00:25:28,380 Yeah. And in fact, I already have a prototype of that working 390 00:25:28,380 --> 00:25:28,800 for 391 00:25:30,210 --> 00:25:33,210 Stephen belt for curio caster or Simon Fraser, I should say, 392 00:25:34,470 --> 00:25:37,860 we have a Docker image, and I have it to where I give him some 393 00:25:37,860 --> 00:25:40,920 JavaScript code to where he can run a serverless function and 394 00:25:40,920 --> 00:25:45,480 run a Docker container on Google Cloud, to publish a live stream 395 00:25:45,480 --> 00:25:49,110 notification. Can you can you flesh that out? And tell me how 396 00:25:49,110 --> 00:25:51,720 that works? Because I thought I was just sort of tangentially 397 00:25:51,720 --> 00:25:57,210 following what exactly is is the what exactly is going on there? 398 00:25:59,340 --> 00:26:02,220 In Google Cloud, I mean, yeah, it's really not different from 399 00:26:02,220 --> 00:26:05,370 what you would do on on your desktop or server, if you run 400 00:26:05,370 --> 00:26:10,530 Docker command line, except they offered as a service in an API. 401 00:26:11,280 --> 00:26:14,190 So it takes the Docker container, it doesn't run as a 402 00:26:14,190 --> 00:26:18,690 server just runs as a command line application. And you give 403 00:26:18,690 --> 00:26:23,400 it the feed you what you want it to update. And it runs the 404 00:26:23,400 --> 00:26:27,000 Docker container with those arguments, and then it exits. So 405 00:26:27,180 --> 00:26:31,740 knowing that from from JavaScript, how fast is there, 406 00:26:32,190 --> 00:26:34,770 never run a Docker container like that is sort of like an on 407 00:26:34,770 --> 00:26:39,060 demand function type situation, is it slow to spin up? Or is the 408 00:26:39,060 --> 00:26:41,640 container just so lean? That it's quick? 409 00:26:43,230 --> 00:26:46,380 The slowest part about is probably Google's API. Like if 410 00:26:46,380 --> 00:26:50,580 you do on your desktop, it's rapid. Yeah. So okay, I mean, 411 00:26:50,580 --> 00:26:51,570 it's under a minute still. 412 00:26:52,680 --> 00:26:55,620 Oh, wow. Okay, so you don't really get penalized by the by 413 00:26:55,620 --> 00:26:56,880 the serverless function stuff. 414 00:26:57,960 --> 00:26:59,400 Yeah. So Alex, 415 00:27:00,750 --> 00:27:04,830 we know that three speakers is integrating some of this you 416 00:27:04,830 --> 00:27:08,670 have yet another hat that you were at no agenda tube, what's 417 00:27:08,670 --> 00:27:11,730 the status of that because I have such high hopes for 418 00:27:12,840 --> 00:27:15,120 for the web torrent and for everything that you've been 419 00:27:15,120 --> 00:27:16,170 putting together there. 420 00:27:17,520 --> 00:27:19,140 The status that is it's working 421 00:27:20,220 --> 00:27:22,860 for super super, super basic functionality. 422 00:27:23,880 --> 00:27:26,010 I don't have any other new podcasts 2.0 features or 423 00:27:26,010 --> 00:27:30,060 anything except Alterna enclosure. But the the idea is 424 00:27:30,060 --> 00:27:35,070 once we get popping to a stable state, which is very, very soon, 425 00:27:36,000 --> 00:27:37,800 there's a couple more updates we are due for Dave, 426 00:27:38,970 --> 00:27:41,460 I want to be able to integrate that and integrate no agenda to 427 00:27:41,760 --> 00:27:45,450 live streaming per video as well. This is this, this is my 428 00:27:45,450 --> 00:27:50,190 ask. I have mo facts waiting in the wings. He's a he is a 429 00:27:50,190 --> 00:27:55,830 prototypical YouTuber. He does all of his last tapes and all 430 00:27:55,830 --> 00:27:59,340 this stuff live. And he uses the chat and the he doesn't use 431 00:27:59,340 --> 00:28:04,230 Super Chat doesn't monetize. But he is ready. As soon as you 432 00:28:04,230 --> 00:28:08,520 know, as soon as the light is given to hook in a live stream 433 00:28:09,840 --> 00:28:13,710 into no agenda tube. So we can do the notifications and he 434 00:28:13,710 --> 00:28:18,870 wants to do we'll do the kind of the Super Chat analogy with with 435 00:28:18,870 --> 00:28:22,110 the booster grams in the live in the live stream. So he's ready 436 00:28:22,110 --> 00:28:26,400 to go whenever we are, I'm going to do is doing better. I'm going 437 00:28:26,400 --> 00:28:29,460 to integrate live chat and the no agenda tube and we're gonna 438 00:28:29,460 --> 00:28:30,480 figure out how to do boost. And 439 00:28:32,820 --> 00:28:36,720 this is this is gonna be so big and we have ideas, man, we got 440 00:28:36,720 --> 00:28:40,140 ideas for this. They are you familiar with versus 441 00:28:42,090 --> 00:28:46,740 you were here versus but in what context that versus is a it's a 442 00:28:46,740 --> 00:28:52,560 hip hop battle. And it happens I think annually on an on streams 443 00:28:52,800 --> 00:28:56,580 on different platforms and YouTube as well. And, and it's 444 00:28:56,580 --> 00:28:59,940 so it's two different DJs or two hip hoppers. And it's like a 445 00:28:59,940 --> 00:29:01,950 battle and people vote. 446 00:29:03,240 --> 00:29:05,580 You know, with either thumbs up and I think they might be they 447 00:29:05,580 --> 00:29:08,910 might do some super chats with that as well. But we're thinking 448 00:29:09,600 --> 00:29:12,720 booster grams and streaming SATs, you got the scoreboard for 449 00:29:12,720 --> 00:29:15,990 each one. It's all live, the whole thing is completely 450 00:29:15,990 --> 00:29:17,490 replicable in our environment. 451 00:29:19,080 --> 00:29:22,140 Yeah, I've actually seen some live streaming platforms that 452 00:29:22,140 --> 00:29:26,340 have built in verses like that great analogy, but they do it 453 00:29:26,340 --> 00:29:28,740 with their own tokens and the great thing here is Yeah, which 454 00:29:28,740 --> 00:29:33,750 is Bitcoin? Yes. And this is the versus audiences a huge cash app 455 00:29:33,750 --> 00:29:34,410 audience. 456 00:29:36,210 --> 00:29:39,630 Which which which is Adams which is Adams code for black America, 457 00:29:39,660 --> 00:29:41,550 which is just what I know from mo 458 00:29:42,780 --> 00:29:47,040 Cash App Cash App rules, so you know, easy to fill up wallets. 459 00:29:47,070 --> 00:29:50,280 It's a it's a of course we're only talking to us only but I 460 00:29:50,280 --> 00:29:51,240 can't fix everything. 461 00:29:52,770 --> 00:29:56,370 Well, I thought a cash app was UK also it is yeah, but you 462 00:29:56,370 --> 00:29:59,370 know, it's not Australia then it gets no coverage in our news. I 463 00:29:59,370 --> 00:29:59,670 see. 464 00:30:03,480 --> 00:30:05,910 Our news doesn't cover say it's not Israel. 465 00:30:07,140 --> 00:30:09,990 Well, you guys got breeze man. What's your problem? This note 466 00:30:09,990 --> 00:30:10,350 we've got 467 00:30:11,460 --> 00:30:15,540 she got everything there. Your central bank shekels. 468 00:30:17,580 --> 00:30:20,490 So I want to I want to finish up the what is popping kind of 469 00:30:20,490 --> 00:30:25,470 thing? Sure. Dave, you use you posted a Twitter. What did they 470 00:30:25,470 --> 00:30:28,830 call it some audio live stream from Jack Dorsey and to Corey. 471 00:30:28,830 --> 00:30:32,160 So I think the other day Oh, I haven't today, Twitter Twitter 472 00:30:32,160 --> 00:30:35,310 spaces. I can't wait to listen to that. He he said something 473 00:30:35,310 --> 00:30:37,530 really beautiful. And that discussion? 474 00:30:38,790 --> 00:30:41,040 kind of halfway through and that was 475 00:30:42,690 --> 00:30:45,690 do you centralize information discovery has been the most 476 00:30:45,690 --> 00:30:49,830 difficult part ever since web 2.0 came out? And that really 477 00:30:49,830 --> 00:30:53,220 describes the issue of podcasting. One, podcasting. 1.0 478 00:30:53,220 --> 00:30:57,060 right. Pod ping is a way to discover 479 00:30:58,230 --> 00:31:03,870 got new RSS feeds, but with the addition of the medium tags. We 480 00:31:03,930 --> 00:31:06,900 I mean, no one's done it yet. But we can have blogs, we can 481 00:31:06,900 --> 00:31:10,860 have films which I'm going to pod teen is is the podcasting 482 00:31:10,860 --> 00:31:12,480 platform, dare I say that? 483 00:31:16,080 --> 00:31:19,230 Just sort of the argument of what podcasting is but uh, but 484 00:31:19,230 --> 00:31:23,340 it's it's, it's, you know, it's, there's, it's kind of a proto 485 00:31:23,340 --> 00:31:26,310 for proto form, you know, it's like a protocol and a platform 486 00:31:26,310 --> 00:31:29,910 at the same time. But you can build anything with podcasting 487 00:31:29,910 --> 00:31:33,090 off of pod ping, you could build an app could run on pod ping, I 488 00:31:33,090 --> 00:31:35,310 think I mean, you don't need anything? 489 00:31:36,540 --> 00:31:39,510 Well, you don't know it, because I haven't, I haven't got it to 490 00:31:39,510 --> 00:31:42,630 show you yet. But there's an API coming out of South Africa soon, 491 00:31:42,960 --> 00:31:47,850 which is going to be the public open API for exploring what's 492 00:31:47,850 --> 00:31:52,110 happened on Pompeii. And it's cool built as part of the hive 493 00:31:52,110 --> 00:31:55,950 work. Oh, excellent. It's called the hive application framework. 494 00:31:55,950 --> 00:31:59,940 It's a new part of Hive it. But it's specifically designed to 495 00:31:59,940 --> 00:32:03,990 make it easy to write apps that have a normal database, you 496 00:32:03,990 --> 00:32:06,030 don't have to think about blockchain, you don't, you don't 497 00:32:06,030 --> 00:32:08,100 have to be a blockchain developer, you just see a 498 00:32:08,100 --> 00:32:10,770 database and you'll see a database of all the pod pings. 499 00:32:11,010 --> 00:32:13,770 And then and then whatever you want to do with that you can do 500 00:32:13,770 --> 00:32:16,500 with that. And it's updated in real time, you know, three 501 00:32:16,500 --> 00:32:19,890 seconds after the latest pod ping, your tables are updated, 502 00:32:19,890 --> 00:32:23,550 and you just call a database. And that's, that's gonna be 503 00:32:23,550 --> 00:32:28,050 available as like, you can just download and install it with 504 00:32:28,050 --> 00:32:31,170 Docker, or you can access the public API. 505 00:32:32,550 --> 00:32:36,030 We're working on that. That's really interesting, because that 506 00:32:36,030 --> 00:32:40,140 is a way to decentralize the functions of the index. I mean, 507 00:32:40,140 --> 00:32:43,950 not not the API functions, but a lot of the storage function. 508 00:32:45,630 --> 00:32:48,660 This is because it's not going to go looking at the feeds. No, 509 00:32:49,110 --> 00:32:53,790 it is going to be the place to find new stuff, because because 510 00:32:53,820 --> 00:32:58,530 every new every active feed will be announced there. Once we get 511 00:32:58,530 --> 00:33:03,000 these sticky hosts to come on board, and it's really the 512 00:33:03,000 --> 00:33:06,300 ongoing back. That's a great catch, Alex and I haven't heard 513 00:33:06,300 --> 00:33:09,510 that that Dorsey thing yet. I can't it's on my list. 514 00:33:11,580 --> 00:33:16,200 Because the one thing that dislike the Holy Grail, where 515 00:33:16,230 --> 00:33:20,070 venture capitalists put hundreds of millions of dollars into 516 00:33:20,340 --> 00:33:25,560 discovery of podcasting, and this really invalidates all 517 00:33:25,560 --> 00:33:30,720 those investments, like that so much. What it does it in a way 518 00:33:30,720 --> 00:33:38,010 to that is is permanent, and you know, and discoverable by 519 00:33:38,010 --> 00:33:43,410 anyone. Oh, yeah. Well, you I'd like a couple, Dorsey said in 520 00:33:43,410 --> 00:33:47,970 that same conversation. And I regret I don't I haven't heard 521 00:33:47,970 --> 00:33:49,410 it or clipped it I would have been great. 522 00:33:50,550 --> 00:33:55,380 I sat down to clip it all last night, and then has sat down and 523 00:33:55,380 --> 00:33:58,770 a heavy pad and intervened. No, no, I just sat down to clip it 524 00:33:58,770 --> 00:34:02,790 all up and bring some clips to the show. And then like five 525 00:34:02,790 --> 00:34:08,580 minutes after I sat down my my 11 year old daughter gave me the 526 00:34:08,610 --> 00:34:12,660 she said the words that every parent dreads Oh with which is 527 00:34:12,690 --> 00:34:13,500 I'm pregnant 528 00:34:19,380 --> 00:34:22,140 I have daughters, I've stepped daughters and a daughter. Okay, 529 00:34:22,140 --> 00:34:26,130 this is this is what I'm thinking. No, no. She said, Hey, 530 00:34:26,130 --> 00:34:30,900 Dad, I want to play Minecraft with some buddies online and Oh, 531 00:34:30,960 --> 00:34:31,410 no. 532 00:34:33,210 --> 00:34:38,970 No, no. Hours crying more did server. No, no. Okay, so that's 533 00:34:39,000 --> 00:34:43,080 that was the original thing. Like five years ago I was for 534 00:34:43,080 --> 00:34:46,530 sure is Hey, Dad, can you install a mod for me? And you're 535 00:34:46,530 --> 00:34:47,130 like, No. 536 00:34:49,680 --> 00:34:53,190 I'm gonna really just JavaScript I grabbed from a random website. 537 00:34:54,120 --> 00:34:57,510 Yeah, exactly that nothing bad will happen. But now it's even 538 00:34:57,510 --> 00:34:59,970 though it's you know, like it's all on the Xbox. 539 00:35:00,299 --> 00:35:04,979 So I had to fight for two hours of you're not all your family 540 00:35:05,219 --> 00:35:09,389 security settings will not allow you to join online games and I 541 00:35:09,389 --> 00:35:13,289 was on Microsoft's website, like trying to change. Like doing 542 00:35:13,289 --> 00:35:17,549 family. Man, that's hilarious. Yeah. You missed this whole 543 00:35:17,549 --> 00:35:21,779 thing, Adam. Well, yeah, well, you know, right now it's like 544 00:35:21,779 --> 00:35:24,689 it's the opposite. I want my daughter to get pregnant. Come 545 00:35:24,689 --> 00:35:29,579 on. Grandpa already. I'm waiting for a girl hurry. Oh, well, 546 00:35:29,579 --> 00:35:32,279 Minecraft is not the route to pregnancy. So that's 547 00:35:34,050 --> 00:35:37,500 a great prophylactic. It's beautiful. Yes, it is. Yeah. But 548 00:35:38,070 --> 00:35:42,240 yeah, I was gonna say is that when what he talked about is 549 00:35:42,240 --> 00:35:48,900 that discovery is the the cause of centralization. Like that's 550 00:35:48,900 --> 00:35:52,890 why things centralized? Yes, yes, to make discovery possible. 551 00:35:53,190 --> 00:35:58,410 But this with POD ping, you end up there. Everything is 552 00:35:58,410 --> 00:36:02,130 decentralized. But it's still discoverable. And it's it's 553 00:36:02,130 --> 00:36:07,110 discoverable in a permanent way. Like, Alex out, I'm misquoted. I 554 00:36:07,110 --> 00:36:12,180 attributed this. The this to Chris Fisher, which is really, 555 00:36:12,210 --> 00:36:17,010 really Alex, who said this a few weeks ago was that pod paying is 556 00:36:17,010 --> 00:36:20,550 a distributed message bus for podcasting. And that's exactly 557 00:36:20,610 --> 00:36:23,970 that's exactly right. Yes, everybody can hook in and get 558 00:36:24,000 --> 00:36:29,220 all the same information. It is it is the opposite of anything 559 00:36:29,220 --> 00:36:34,140 you can do platform it is it is so big. I mean, I've seen I saw 560 00:36:34,140 --> 00:36:38,490 it from day one. It's like, once, once it dawned on me, 561 00:36:38,490 --> 00:36:41,310 which you understood much quicker than I did, Dave. But 562 00:36:41,310 --> 00:36:44,730 once I saw it, I'm like, holy crap, this is what everyone's 563 00:36:44,730 --> 00:36:48,420 been talking about. And all this money is, is Spotify, just 564 00:36:48,420 --> 00:36:52,530 bought companies that have some version of this, you know, of 565 00:36:52,530 --> 00:36:55,500 this discoverability factor, in this case, they tied into 566 00:36:55,500 --> 00:36:59,310 advertising. But this, this is beautiful. 567 00:37:00,360 --> 00:37:04,410 I want to just point out one one part of it that I think is, is 568 00:37:04,500 --> 00:37:07,980 misunderstood and overlooked, which is that the reason we can 569 00:37:07,980 --> 00:37:12,330 do all of this is because we were putting these messages into 570 00:37:12,330 --> 00:37:16,620 a system, which whilst we are not directly paying for, we are 571 00:37:16,620 --> 00:37:20,310 paying for by having an investment in it. Okay, that's 572 00:37:20,310 --> 00:37:24,630 the, you know, that's the amount of hive that I've raised and 573 00:37:24,660 --> 00:37:28,500 stake and you know, it's about 4000 or $5,000 Worth, it's 574 00:37:28,500 --> 00:37:31,770 really it's not a big amount. And it's not it's not spent 575 00:37:31,770 --> 00:37:36,690 money. But that's our stake in the ownership, partial ownership 576 00:37:36,720 --> 00:37:41,250 of Hive. And you can ask some questions about this. I know 577 00:37:41,250 --> 00:37:42,150 very little about it. 578 00:37:43,320 --> 00:37:47,430 So this is a high, high blockchain as a staking based 579 00:37:47,430 --> 00:37:50,670 systems, I understand it. Yeah. And we don't have a gated proof 580 00:37:50,670 --> 00:37:53,820 of stake. And we don't have to go too deep. But what is the 581 00:37:53,820 --> 00:37:58,050 ratio of usage versus stake EJ that you have to have? So you 582 00:37:58,050 --> 00:38:00,180 say, three $4,000? 583 00:38:01,260 --> 00:38:03,660 That's a lot of money to some people, a lot of money to a lot 584 00:38:03,660 --> 00:38:06,690 of people. So I just tried to understand how much do you need 585 00:38:07,140 --> 00:38:12,960 in order to utilize the system? Is there some kind of key that I 586 00:38:12,960 --> 00:38:15,990 can understand like, well, if I'm doing this with it, or if I, 587 00:38:16,200 --> 00:38:19,920 you know, what I'm saying? It's based on, it's based on a system 588 00:38:19,920 --> 00:38:23,970 called Resource credits, and you use up resource credits, which 589 00:38:23,970 --> 00:38:28,860 are a renewable resource, you, you know, you get them, they 590 00:38:28,860 --> 00:38:33,180 recharge all the time at a rate dependent on your investment in 591 00:38:33,180 --> 00:38:39,210 the system. And your resource usage is based on basically how 592 00:38:39,210 --> 00:38:42,720 much data and how quickly you're putting it into the chain, how 593 00:38:42,720 --> 00:38:45,630 much how much data you're writing, so we're writing these 594 00:38:45,630 --> 00:38:50,190 pod paying, got it, and we write what, four or 5000 a day, which 595 00:38:50,190 --> 00:38:54,060 is us, you know that on any other blockchain that would be a 596 00:38:54,060 --> 00:38:57,570 crazy amount of transactions. But that turns out to be point, 597 00:38:57,960 --> 00:39:01,680 one 6% of that type of transaction where we're 598 00:39:01,680 --> 00:39:07,020 miniscule where we're minnows, nobody even notices pod ping. So 599 00:39:07,260 --> 00:39:11,100 that investment and to be honest, is you know, I'm, I'm 600 00:39:11,130 --> 00:39:15,420 over invested because I'm investing in the whole system as 601 00:39:15,480 --> 00:39:19,470 as you know, just just to support it. But the point about 602 00:39:19,470 --> 00:39:23,970 hive that makes it different is the way it was born. There is no 603 00:39:23,970 --> 00:39:28,170 owner there is no venture capital there is no single owner 604 00:39:28,830 --> 00:39:35,130 there's nobody who has more than 3% we think and that means it is 605 00:39:35,130 --> 00:39:40,860 truly independent there's no CEO there's no office there's no 606 00:39:40,860 --> 00:39:44,280 address there's nowhere to serve legal papers you can't you which 607 00:39:44,280 --> 00:39:47,820 is 5g is unique, which is unique in the world of proof of stake 608 00:39:47,820 --> 00:39:52,080 if I'm wrong if I'm going Yes, Bitcoin is the only other thing 609 00:39:52,080 --> 00:39:55,590 I think that's like that. You know, there's just nobody you 610 00:39:55,590 --> 00:39:59,820 can go nail a sign on the door and say, say come to court with 611 00:39:59,820 --> 00:39:59,970 it. 612 00:40:00,000 --> 00:40:03,390 You can do that there are front ends to hive there are, you 613 00:40:03,390 --> 00:40:07,890 know, websites like Hive dot blog or peak d.com, you can find 614 00:40:07,890 --> 00:40:11,580 the owners of that. But the underlying system, the database, 615 00:40:11,610 --> 00:40:16,500 the bit that we're using, you can't find it. It's distributed 616 00:40:16,500 --> 00:40:21,210 properly. This is thank you for that explanation, I understand I 617 00:40:21,210 --> 00:40:25,530 have a better grasp on it. And so I'm right. This is this is 618 00:40:25,530 --> 00:40:30,090 true web 3.0 where the stakeholders run the system. And 619 00:40:30,090 --> 00:40:34,320 the stakeholders benefit however they need it. Yeah, yeah, I get 620 00:40:34,320 --> 00:40:40,410 it. I get it. And then, so take that VC. Yeah. And it's kind of 621 00:40:40,710 --> 00:40:43,890 web three in reverse. Because podcasting has been around for 622 00:40:43,890 --> 00:40:48,690 so long. We're just taking that way of standardizing information 623 00:40:48,690 --> 00:40:52,860 to applications and telling you where it is, then what and what 624 00:40:52,860 --> 00:40:56,940 happened? Well, let's talk about that, then. So you're 625 00:40:58,230 --> 00:41:06,360 so a, a pod, a pod paying, enabled host or platform. Let me 626 00:41:06,390 --> 00:41:07,920 let me figure out how to describe this. 627 00:41:09,330 --> 00:41:13,620 I think people don't understand what you can actually do with 628 00:41:13,620 --> 00:41:19,830 POD ping. What what they hear is, it's a way to see when feeds 629 00:41:19,830 --> 00:41:20,370 update. 630 00:41:21,690 --> 00:41:26,730 Okay, fine. Yes, that is true. It's now become a way to see 631 00:41:26,730 --> 00:41:31,410 when feeds update with appropriate data attached to 632 00:41:31,410 --> 00:41:34,890 that to know why it's updating and for and, and what that 633 00:41:34,890 --> 00:41:35,520 means. 634 00:41:36,780 --> 00:41:41,400 But think about it more broadly, if you're a hosting company, or 635 00:41:41,400 --> 00:41:45,900 an app, or some sort of third party platform like analytics, 636 00:41:47,400 --> 00:41:51,390 or a publisher, think about the types of data that you can 637 00:41:51,390 --> 00:41:57,540 glean, if you have a low noise ratio, constant stream of 638 00:41:57,600 --> 00:42:01,620 podcast activity that you can watch. So you could for 639 00:42:01,620 --> 00:42:04,050 instance, do something like, 640 00:42:05,190 --> 00:42:09,330 look at all these shows that you know, are highly successful, and 641 00:42:09,330 --> 00:42:12,810 look at their growth curves, and then correlate that with how 642 00:42:12,810 --> 00:42:16,080 many times a day they are, how many times a week they publish, 643 00:42:16,110 --> 00:42:18,930 or what days of the week they publish, or what time of day 644 00:42:18,930 --> 00:42:23,160 they publish, or how long the shows are. But once you have 645 00:42:23,160 --> 00:42:25,920 this sort of low signal to noise, high signal to noise 646 00:42:25,920 --> 00:42:26,670 ratio, 647 00:42:28,440 --> 00:42:33,210 message system, you can look at all those sorts of things and go 648 00:42:33,210 --> 00:42:35,130 back and remember, it's permanent. So you can go back in 649 00:42:35,130 --> 00:42:39,600 time, you can say, Okay, over the last year, these these shows 650 00:42:39,630 --> 00:42:43,620 on my platform have have peaked, and then the advertisements 651 00:42:43,980 --> 00:42:49,110 were, you know, successful here and had a good return. And they, 652 00:42:49,140 --> 00:42:51,810 you know, these other, you can do all these correlations 653 00:42:51,810 --> 00:42:56,250 between the activity you see, without having to have to deal 654 00:42:56,250 --> 00:43:00,450 with all of that noise. It's just things like that, where you 655 00:43:00,450 --> 00:43:04,860 can, if you think more a little bit beyond the immediate 656 00:43:04,860 --> 00:43:10,830 technology of it, you can see how powerful it becomes. Is that 657 00:43:10,830 --> 00:43:14,700 fair, and that's without running the podcast in because you can 658 00:43:14,760 --> 00:43:18,390 you Dave, who sits at the center of something called podcast 659 00:43:18,390 --> 00:43:22,560 index, which is quite a big expensive thing to run, you 660 00:43:22,560 --> 00:43:26,250 could work all of that out. But now, what we're going to have 661 00:43:26,250 --> 00:43:30,000 going forward is a way to just tap into that same information 662 00:43:30,180 --> 00:43:34,830 really cheaply. And, and, you know, there's a philosophical I, 663 00:43:35,040 --> 00:43:38,190 I got onto hive, like two years ago, after being chucked off 664 00:43:38,190 --> 00:43:42,120 Facebook, and it was a philosophical switch. Everybody 665 00:43:42,120 --> 00:43:45,240 was was all upset that Facebook and you know that they're paying 666 00:43:45,240 --> 00:43:49,110 huge fines. Now Facebook was, you know, selectively giving 667 00:43:49,110 --> 00:43:52,860 your information to this party or that party, Hive, everything 668 00:43:52,860 --> 00:43:55,860 I everything I click on is public. And you come to 669 00:43:55,860 --> 00:44:00,270 understand that, you know, if I'm going to be on social media, 670 00:44:00,270 --> 00:44:02,460 if I'm going to be acting in public, I might as well just 671 00:44:02,460 --> 00:44:05,310 assume that everything I do is public, because it's better that 672 00:44:05,310 --> 00:44:09,000 way. And when you're publishing a podcast, everything you do is 673 00:44:09,000 --> 00:44:13,050 public. You know, when you press publish, the whole world can see 674 00:44:13,050 --> 00:44:17,670 it, but it just up to now you'd have to look all over the web to 675 00:44:17,700 --> 00:44:20,490 you know, 4 million different places to find out when 676 00:44:20,490 --> 00:44:25,500 everybody published. So this centralize is where you look to 677 00:44:25,500 --> 00:44:29,190 see that information, but still in a decentralized way. It's 678 00:44:29,190 --> 00:44:33,810 really different. It's beautiful. I learned yesterday 679 00:44:36,390 --> 00:44:40,860 I made a mistake and I put the wrong image size in the RSS feed 680 00:44:40,860 --> 00:44:46,830 instead of minimum 2000 by 2000, which is the Apple requirement. 681 00:44:47,610 --> 00:44:55,440 I put the five whatever, five 520 Whatever it is 520 by 520. 682 00:44:55,890 --> 00:44:58,500 And Apple won't publish 683 00:45:00,599 --> 00:45:03,239 They won't, it will not surface on their app if you have the 684 00:45:03,239 --> 00:45:06,929 wrong image size. Oh, it just won't even show it. Oh, no, they 685 00:45:06,929 --> 00:45:09,899 will not publish it. And I know and I know, because we have a 686 00:45:09,899 --> 00:45:10,619 producer 687 00:45:11,790 --> 00:45:13,650 who approved it manually. 688 00:45:14,759 --> 00:45:19,199 After nine hours, like it's out of that. Yeah. Yeah. He said, 689 00:45:19,229 --> 00:45:22,349 Dude. And this happens a lot with me. Because it's not it's, 690 00:45:22,349 --> 00:45:24,269 you know, I change the album art all the time. And I make 691 00:45:24,299 --> 00:45:28,739 mistakes. I make stupid mistakes. It's my fault. But the 692 00:45:28,739 --> 00:45:30,599 fact that it doesn't even publish 693 00:45:31,770 --> 00:45:32,850 that's whacked. 694 00:45:34,110 --> 00:45:36,810 That's weird. You would think that it would publish and just 695 00:45:36,810 --> 00:45:40,800 have like, no, if your image it's a trap, if your image size 696 00:45:40,800 --> 00:45:43,920 is not correct on Apple, they do not publish it. Because you 697 00:45:43,920 --> 00:45:47,190 know, it might hurt the user. That's for the the overall image 698 00:45:47,190 --> 00:45:49,560 for the whole feed. It's it is it's a night I've been dealing 699 00:45:49,560 --> 00:45:51,660 with that with three spit, because we don't, we don't 700 00:45:51,660 --> 00:45:55,290 actually have a 2000 by 2000 image anywhere. And it's it's 701 00:45:55,290 --> 00:45:58,530 been a pain in the ass doing everything to comply with that. 702 00:45:58,530 --> 00:46:04,200 Just one and it sickens me. Yeah, yeah, you're right. I 703 00:46:04,200 --> 00:46:06,450 mean, I'd like to throw all my images out there, which of 704 00:46:06,450 --> 00:46:09,480 course I can do. I know. And we have that capability. And we 705 00:46:09,480 --> 00:46:12,150 have it, it's built into sovereign feeds, I still have to 706 00:46:12,150 --> 00:46:16,770 create them. But it's, anyway, just as an aside, all these all 707 00:46:16,770 --> 00:46:21,810 these hoops all fall away? Well, there's at least three is at 708 00:46:21,810 --> 00:46:24,210 least three more podcast hosts that I know of that are going to 709 00:46:24,240 --> 00:46:26,640 need are going to be coming on board with Todd ping. Excellent. 710 00:46:27,180 --> 00:46:30,810 And pretty soon. And I think that it's, 711 00:46:31,980 --> 00:46:35,610 it's clear, if you're not doing this, you're not your podcast 712 00:46:35,610 --> 00:46:36,240 host your 713 00:46:37,410 --> 00:46:41,550 words I was going to use, we'll go with, if you're not if you're 714 00:46:41,550 --> 00:46:43,500 a podcast host and you're not doing it. 715 00:46:45,240 --> 00:46:48,480 I just don't understand why it doesn't make it. So here's, 716 00:46:49,530 --> 00:46:53,460 here's another use case, just they just start hitting you as 717 00:46:53,460 --> 00:46:56,460 you think about this stuff. Another use case, a new podcast 718 00:46:56,460 --> 00:46:59,790 platform comes online. And we get requests for this all the 719 00:46:59,790 --> 00:47:02,730 time, I get three this week, three emails from different 720 00:47:02,730 --> 00:47:06,420 people saying, Hey, can I use the index database? What are the 721 00:47:06,420 --> 00:47:09,450 terms of service, blah, blah, blah, blah, blah. We're building 722 00:47:09,450 --> 00:47:11,550 a new app or a new platform or whatever. 723 00:47:12,660 --> 00:47:18,810 And so imagine, imagine a future where piping is the standard, 724 00:47:19,140 --> 00:47:22,140 with the way everybody distributes new new feed update 725 00:47:22,140 --> 00:47:27,990 notifications. A new platform coming on board can then take 726 00:47:28,020 --> 00:47:32,280 take a database like ours or some database, they can walk 727 00:47:32,310 --> 00:47:35,040 back or they don't even have to download the database, they 728 00:47:35,040 --> 00:47:40,140 could walk back in time on the blockchain, and see all of the 729 00:47:40,140 --> 00:47:42,960 feeds that have published updates over certain let's just 730 00:47:42,960 --> 00:47:47,400 say a year. And they can choose to only pull those in and only 731 00:47:47,400 --> 00:47:50,130 operate on those database and say, okay, the rest of them are 732 00:47:50,130 --> 00:47:53,400 not near a pod faded or whatever. These are the types of 733 00:47:53,400 --> 00:47:56,430 things that you can do. And when you're a participant in it as a 734 00:47:56,430 --> 00:48:01,050 hosting company, pushing that data out there. You are making 735 00:48:01,050 --> 00:48:06,570 your job in the future easier. And cheaper. Yes, you're using 736 00:48:06,570 --> 00:48:10,890 the whole Yeah, go ahead. Now. You don't have to work with this 737 00:48:10,890 --> 00:48:15,030 custom API's to submit feeds. Yeah, don't have to go to 738 00:48:15,030 --> 00:48:18,210 Spotify or Apple, say, hey, we need an API key to submit this 739 00:48:18,210 --> 00:48:20,280 new feed. Just put it on parking. 740 00:48:21,450 --> 00:48:24,300 Well, that's how I got all of the three speed feeds, you know, 741 00:48:24,300 --> 00:48:27,420 to you, you know, I was using the app. But from the start, as 742 00:48:27,420 --> 00:48:30,570 soon as as soon as the show updates, put it on pumping, you 743 00:48:30,570 --> 00:48:34,500 ingest it going forward. That's the way to add feeds to all 744 00:48:34,500 --> 00:48:39,360 indexes because it's so easy. It's public. It's it's, it's low 745 00:48:39,360 --> 00:48:41,730 abuse, you know, and we haven't seen any abuse yet. There are 746 00:48:41,730 --> 00:48:45,270 ways to deal with abuse, because, you know, we can, we 747 00:48:45,270 --> 00:48:48,540 can choose who to ignore. So if somebody is abusive, we'll just 748 00:48:48,540 --> 00:48:51,630 ignore that their pings, they'll put the pings on the blockchain, 749 00:48:51,870 --> 00:48:55,980 we'll just put them on our list that we just don't see them. But 750 00:48:56,220 --> 00:48:59,910 that asks censorship as a banker. 751 00:49:01,080 --> 00:49:04,770 Yeah, exactly. If you don't want to see that stuff, you won't 752 00:49:04,770 --> 00:49:08,610 have to see it. If they would be so kind as to use pod ping. 753 00:49:09,150 --> 00:49:09,600 Well, so 754 00:49:10,740 --> 00:49:12,900 sorry, go ahead. I was gonna say, 755 00:49:14,100 --> 00:49:19,860 can we talk about live plugin? And this is really for Alex, I 756 00:49:19,860 --> 00:49:23,010 guess. What? With live? 757 00:49:24,300 --> 00:49:27,540 What is that going to look like from the apps perspective? Can 758 00:49:27,540 --> 00:49:30,900 you describe sort of like a minimum viable product for 759 00:49:31,230 --> 00:49:36,750 allies for a live interface on the podcast app side? 760 00:49:38,790 --> 00:49:43,170 Yeah, so the minimum minimum viable product is they have a 761 00:49:43,170 --> 00:49:44,190 server somewhere 762 00:49:46,440 --> 00:49:48,930 and they're watching the hype blockchain and they get every 763 00:49:48,930 --> 00:49:51,510 block they get everything for every block. So I mean, it's not 764 00:49:51,510 --> 00:49:55,140 ideal right now. They get the fire hose of five. And then they 765 00:49:55,170 --> 00:49:57,450 know when they watch for the piping live events 766 00:49:59,100 --> 00:49:59,970 and if they 767 00:50:00,000 --> 00:50:01,680 A, you know, have any 768 00:50:03,060 --> 00:50:05,670 podcast listeners that are subscribed to that feed, they 769 00:50:05,670 --> 00:50:08,400 can send them a notification using whatever notification 770 00:50:08,400 --> 00:50:09,150 system they have. 771 00:50:10,260 --> 00:50:12,180 Now, is that too high level? Or? 772 00:50:13,349 --> 00:50:15,569 No, I'm playing I was thinking the only question I had was 773 00:50:15,569 --> 00:50:18,929 like, What about a? You're going to be did apps going to need 774 00:50:18,929 --> 00:50:22,919 some sort of like web hook or something to where they can get 775 00:50:22,919 --> 00:50:26,069 notified? Or do they need to just? 776 00:50:27,090 --> 00:50:32,640 How does this get to the point where they don't have to pull or 777 00:50:32,790 --> 00:50:37,320 look at the block chain? Constantly? So there's two 778 00:50:37,320 --> 00:50:39,840 solutions there, Brian mentioned the first one that he's working 779 00:50:39,840 --> 00:50:43,110 on. But that's for like super heavy apps that are, you know, 780 00:50:43,110 --> 00:50:47,370 really, really on hive, to have I love application framework. 781 00:50:47,370 --> 00:50:51,030 Right, right. But I will also be working on a, I'm going to 782 00:50:51,720 --> 00:50:54,000 probably some kind of lightweight hive notification 783 00:50:54,000 --> 00:50:54,630 framework. 784 00:50:56,430 --> 00:50:58,680 For applications that don't really care about 785 00:51:00,480 --> 00:51:03,120 how accurate some of the blocked updates are, which for 786 00:51:03,120 --> 00:51:05,790 livestream notifications, it doesn't matter that much. So 787 00:51:05,790 --> 00:51:06,840 what will happen is, 788 00:51:08,010 --> 00:51:11,460 it's not built yet it didn't start in the code. But what will 789 00:51:11,460 --> 00:51:14,100 happen is you could tell the server, which feeds you're 790 00:51:14,100 --> 00:51:17,730 interested in and how you want to receive updates for them. And 791 00:51:17,730 --> 00:51:20,250 then the server might give like, you could maybe give it a web 792 00:51:20,250 --> 00:51:24,690 hook or, you know, a WebSocket or something, and then it will 793 00:51:24,720 --> 00:51:27,540 give you give you the feed updates that you're interested 794 00:51:27,540 --> 00:51:30,690 in. And why that's important as that could work with a headless 795 00:51:30,690 --> 00:51:35,280 server as well. So like in a pod, or Kara cast or whatever. 796 00:51:37,170 --> 00:51:39,750 It'll be super lightweight and energy efficient for phones. 797 00:51:41,370 --> 00:51:44,220 And I haven't done it yet hive application, the hive 798 00:51:44,220 --> 00:51:47,700 application framework will or will ultimately be the 799 00:51:47,700 --> 00:51:50,640 lightweight back in that that's listening all the time to the 800 00:51:50,640 --> 00:51:54,330 hive blockchain and feeding the information in which can then be 801 00:51:54,330 --> 00:51:57,840 redistributed as WebSockets, or whatever, whatever sort of 802 00:51:57,900 --> 00:52:02,850 mobile friendly format, we need that just so it's so it becomes 803 00:52:02,850 --> 00:52:03,120 like, 804 00:52:04,140 --> 00:52:08,040 a tree, you know, an upside down tree. So, you know, it's got all 805 00:52:08,040 --> 00:52:11,460 the data in the center, but you just slowly send it off in this 806 00:52:11,460 --> 00:52:14,820 direction and that direction, depending on which client needs 807 00:52:14,820 --> 00:52:19,920 what, maybe not, not consulted me on whatever at the hive 808 00:52:19,920 --> 00:52:21,120 allocation framework, so 809 00:52:23,250 --> 00:52:27,180 I don't really do other things. Yeah, I don't really, I think 810 00:52:27,180 --> 00:52:29,070 it's too much for our use case, but maybe 811 00:52:30,270 --> 00:52:33,030 some historical context of why they made that is 812 00:52:34,800 --> 00:52:37,590 it can be pretty tricky for an application to know when a block 813 00:52:37,590 --> 00:52:38,430 is finalized. 814 00:52:39,540 --> 00:52:42,840 Which is more important for currency and token transactions. 815 00:52:43,350 --> 00:52:47,610 Yeah, it doesn't matter for us really, like you're talking 816 00:52:47,610 --> 00:52:50,280 about eventual consistency, sort of like as applied to a 817 00:52:50,280 --> 00:52:54,390 blockchain. But yeah, there's about a 40 sec 42nd to one 818 00:52:54,390 --> 00:52:59,370 minute, period in which, if you're being really for Nikiti 819 00:52:59,370 --> 00:53:01,230 on hive, you should wait 820 00:53:02,490 --> 00:53:05,670 for witnesses to attest to the transaction for all the 821 00:53:05,670 --> 00:53:08,610 witnesses to agree and then every now and then, PIF does 822 00:53:08,610 --> 00:53:12,270 micro fork all the time with little, little silly details, 823 00:53:12,270 --> 00:53:16,320 you know, sort of whether someone clicked like on a social 824 00:53:16,320 --> 00:53:21,030 post or not, that micro forks out from time to time that 825 00:53:21,810 --> 00:53:26,280 question that doesn't affect us question for Brian. So hive is a 826 00:53:26,280 --> 00:53:26,820 token 827 00:53:27,960 --> 00:53:34,290 what happens with the the usage of Hive does the value of the 828 00:53:34,290 --> 00:53:40,050 token go up? Versus fee like the US dollar? Is it something I 829 00:53:40,050 --> 00:53:43,680 should I should buy just to invest in the network? Is it 830 00:53:43,680 --> 00:53:46,590 something that I should buy as an investment is it you know, 831 00:53:47,340 --> 00:53:51,090 tell me about the financial side of the token. And and is there 832 00:53:51,090 --> 00:53:56,160 any risk of that just becoming a crazy, like, you know, Ico type 833 00:53:56,160 --> 00:54:00,360 shit coins situation where it kind of loses that functionality 834 00:54:00,360 --> 00:54:03,450 and is more about making, you know, money on investment. 835 00:54:04,560 --> 00:54:10,770 That's, that's such a big area now, not financial advice. For 836 00:54:10,770 --> 00:54:14,730 example, when we started doing pod ping, I think hive the price 837 00:54:14,730 --> 00:54:19,830 was around 20 or 30 cents. It's now just around $1 It just 838 00:54:19,860 --> 00:54:24,960 dipped below $1 Now, so actually most of the most of the hive 839 00:54:24,960 --> 00:54:29,160 power that I've locked in to do pod Ping has appreciated 840 00:54:29,160 --> 00:54:32,610 tremendously and I've you know, on paper we're ahead. 841 00:54:34,620 --> 00:54:37,950 I'm not going to say invest in hive but I'm going to say that 842 00:54:37,980 --> 00:54:42,570 it's what makes it stand out and different from all of that Ico 843 00:54:42,570 --> 00:54:46,590 noise and all of those other coins. The coins is the way hive 844 00:54:46,590 --> 00:54:51,120 was born. I was born in a war you know there was this I won't 845 00:54:51,120 --> 00:54:54,210 go into the it's too is too big a story but high was born 846 00:54:54,210 --> 00:54:58,320 because of an alien invasion. Someone came in tried to sell it 847 00:54:58,320 --> 00:54:59,400 man, this is great. Yeah. 848 00:55:00,000 --> 00:55:04,860 Warren in an alien invasion, it was, it was an alien invasion. 849 00:55:04,890 --> 00:55:08,850 And this is the thing about delegated proof of stake, and 850 00:55:08,850 --> 00:55:13,260 it's really important is that we don't, I don't want to run a 851 00:55:13,260 --> 00:55:18,060 server in order to have a social media site, nobody does. There 852 00:55:18,060 --> 00:55:22,710 are actually 20, top 20, there are 20 Top witnesses on hive. 853 00:55:22,950 --> 00:55:26,010 And then there's about another 80 witnesses that they they do 854 00:55:26,010 --> 00:55:28,980 the heavy lifting of keeping this thing running, and they get 855 00:55:28,980 --> 00:55:33,120 rewarded. And when the token price was down around six or 856 00:55:33,120 --> 00:55:38,700 seven cents, as it got to the bottom of the last drop, some of 857 00:55:38,700 --> 00:55:42,390 them were, it was hard to justify the cost of the 858 00:55:42,390 --> 00:55:45,510 equipment, but up at around $1. Everybody running the equipment 859 00:55:45,510 --> 00:55:48,990 that runs high, is making money and doing well, they're not 860 00:55:48,990 --> 00:55:51,690 super wealthy, they're not billionaires, there's no, 861 00:55:51,870 --> 00:55:56,490 there's no VC that's looking for an exit. But they're happy to 862 00:55:56,490 --> 00:55:59,700 run the equipment because they're rewarded. And everywhere 863 00:55:59,700 --> 00:56:03,180 I look, all of the projects, all of the front ends that I use, 864 00:56:03,930 --> 00:56:07,260 people are making enough money to cover their costs and then 865 00:56:07,260 --> 00:56:10,740 some, and that makes a difference. And I'm funded by 866 00:56:10,740 --> 00:56:18,780 the the the dow of Hive, so I get a steady increase. Yeah, I 867 00:56:18,780 --> 00:56:23,220 have to pay, I have to pay Alex more. I just must get around to 868 00:56:23,220 --> 00:56:25,590 that. And you know, fed some back to, 869 00:56:26,640 --> 00:56:29,730 to podcast, the index, and I should do some more. But the 870 00:56:29,730 --> 00:56:34,050 point is, this isn't it's not big cash. It's not the sort of 871 00:56:34,140 --> 00:56:37,890 $15 million funding that you get when you you know, sign up with 872 00:56:37,890 --> 00:56:42,870 a VC. But it's enough that the volunteers who love doing this 873 00:56:43,440 --> 00:56:47,760 are also not out of pocket doing it. And you know, that's value 874 00:56:47,760 --> 00:56:50,790 for value that that's the whole system operates and value of 875 00:56:50,820 --> 00:56:54,480 value. I'm not going to say by time, I think, you know, I've 876 00:56:54,480 --> 00:56:57,960 got a lot of Hive, and I've hardly bought any, I don't think 877 00:56:57,960 --> 00:57:02,310 I've really, I've earned it. I've written posts, I've been 878 00:57:02,310 --> 00:57:04,890 paid. And it was because I was thrown off Facebook, and I 879 00:57:04,890 --> 00:57:08,400 started putting my energy into hive. But because energy and 880 00:57:08,400 --> 00:57:12,030 time invested in high for me, where, you know, I was just 881 00:57:12,030 --> 00:57:15,660 writing stuff and posting videos. instead of it going to 882 00:57:15,660 --> 00:57:17,670 Zuckerberg it went to me. Thank you. 883 00:57:18,720 --> 00:57:23,850 That's what I and I'm now you know not? I've got a few. I've 884 00:57:23,850 --> 00:57:28,620 got a small ownership stake in hive. And it feels much better 885 00:57:28,620 --> 00:57:31,050 to be using a system that I'm a part owner of. 886 00:57:32,100 --> 00:57:35,640 Yeah. And you know what, make sure that you one more point 887 00:57:35,640 --> 00:57:38,070 about piping in general, is that 888 00:57:39,210 --> 00:57:43,170 it's not just podcasts. This is how we request YouTube. Yeah, 889 00:57:43,170 --> 00:57:45,690 weather. I mean, however you argue about the incentive 890 00:57:45,690 --> 00:57:49,650 structures of capitalism versus some inflation based token, 891 00:57:49,650 --> 00:57:54,060 which you know, Hive works. It allows you to distribute the 892 00:57:54,060 --> 00:57:55,020 storage 893 00:57:56,100 --> 00:58:00,960 of all those video streams. So you don't have to do 50 894 00:58:00,960 --> 00:58:03,420 terabytes a second video streaming or whatever. I mean, 895 00:58:03,420 --> 00:58:06,210 it's probably a lot more than that. But some, some some of 896 00:58:06,210 --> 00:58:09,120 those single live streams on YouTube when they get to 897 00:58:09,180 --> 00:58:14,130 100,000. Viewers, it's literally 10s of terabytes a second. Yeah, 898 00:58:14,190 --> 00:58:16,920 you can't. I mean, no one can compete with that. The only way 899 00:58:16,920 --> 00:58:19,050 to do it is to separate this a distributed. 900 00:58:20,340 --> 00:58:22,650 Yeah, I mean, that's what my friends at three speak are 901 00:58:22,650 --> 00:58:26,280 working on, which is a much bigger project. But it's about 902 00:58:26,490 --> 00:58:30,840 looking at this token omics, you know, how do we what made 903 00:58:30,840 --> 00:58:35,070 Bitcoin much more special than people realize is that it gave 904 00:58:35,070 --> 00:58:39,210 people an incentive to run a system. And to this day, it's 905 00:58:39,210 --> 00:58:42,300 worth running a miner because you get paid for it, you know, 906 00:58:42,330 --> 00:58:45,960 the amount the return on investment, after you've bought 907 00:58:45,960 --> 00:58:48,360 the machinery and after you've paid for the electricity, you 908 00:58:48,360 --> 00:58:53,130 make money. Same with most of the applications on hive, you 909 00:58:53,130 --> 00:58:57,360 put in the time and effort, you can make some money back. Not 910 00:58:57,360 --> 00:59:00,840 vast wealth, I don't think but, but and that's what they're 911 00:59:00,840 --> 00:59:03,360 trying to do with video storage. You know, there's three 912 00:59:03,360 --> 00:59:06,030 components that make video difficult on the internet, 913 00:59:06,090 --> 00:59:09,390 there's, there's the actual storage long term, there's the 914 00:59:09,390 --> 00:59:14,370 quick delivery, so CD ends, and the discovery in the front ends, 915 00:59:14,400 --> 00:59:19,440 but they're trying to put in place proper financial 916 00:59:19,440 --> 00:59:22,950 incentives to to have communities that can store the 917 00:59:22,950 --> 00:59:27,570 video for you and run up CDN. Now you don't need you don't 918 00:59:27,570 --> 00:59:32,190 need 1000s of CDN nodes, but you need some and you need some way 919 00:59:32,190 --> 00:59:36,660 to pay them. And it has to be an internal token system, which is 920 00:59:36,660 --> 00:59:40,770 trustless. And if people store and deliver video for you, you 921 00:59:40,770 --> 00:59:41,550 should pay them. 922 00:59:44,010 --> 00:59:46,200 Where should I Where can I buy a hive? 923 00:59:48,150 --> 00:59:50,940 Well, pretty soon you'll be able to buy it from me from 924 00:59:50,940 --> 00:59:55,620 lightning, but I'm doing the reverse high of lightning Rube 925 00:59:55,620 --> 00:59:58,680 Goldberg machine. Yeah. So you're you're a money 926 00:59:58,680 --> 00:59:59,970 transmitter. Now Brian 927 01:00:00,000 --> 01:00:05,340 You are let's not say that I'm raising I'm I'm creating open 928 01:00:05,340 --> 01:00:08,730 source software that will enable anyone to run the service. Yes. 929 01:00:09,570 --> 01:00:12,300 You need to follow that with your honor. You're 930 01:00:15,630 --> 01:00:16,890 building like a dmg. 931 01:00:21,030 --> 01:00:23,430 traffics in Yeah, crypto do 932 01:00:24,720 --> 01:00:29,220 this. And I'll tell you what, before I went through the was it 933 01:00:29,220 --> 01:00:31,710 close? It's actually as a good trace. That's what 934 01:00:32,880 --> 01:00:37,650 hive has been hive has actually been, I think shunned by the big 935 01:00:37,650 --> 01:00:41,580 boys because it doesn't have this VC thing. It's like, you 936 01:00:41,580 --> 01:00:44,010 know, what happens is behind the scenes, and I know this, because 937 01:00:44,010 --> 01:00:46,620 I know the volunteer people who are talking to the exchanges, 938 01:00:46,860 --> 01:00:49,260 the exchanges all want big listing fees, we're not going to 939 01:00:49,260 --> 01:00:52,890 pay those because we ain't got no big VC pot to pay, you know, 940 01:00:52,920 --> 01:00:57,990 to pay Coinbase whatever they're asking, Well, Jack Jack Dorsey 941 01:00:57,990 --> 01:01:01,680 made this, he made this point in that, in that Twitter spaces 942 01:01:01,680 --> 01:01:08,100 things he he spoke to his distaste of the VC backing of 943 01:01:08,100 --> 01:01:11,730 web three, and how he's like, you know, hey, you know, web 944 01:01:11,730 --> 01:01:15,270 three is singing the song of decentralization. And while that 945 01:01:15,270 --> 01:01:18,240 may or may not be accurate, depending on which blockchain 946 01:01:18,240 --> 01:01:22,500 you're talking about, one thing is absolutely certain is that 947 01:01:22,500 --> 01:01:25,770 the VC money that is going into it is not decentralized, that 948 01:01:27,060 --> 01:01:30,510 that is all in one basket. I mean, there's a couple of 949 01:01:30,510 --> 01:01:34,380 really, two or three really high powered VCs that are funding a 950 01:01:34,380 --> 01:01:38,520 lot of this stuff. And the when the VC money gets in there, your 951 01:01:38,520 --> 01:01:43,650 web three claims tend to meet to fall a little bit hollow in it. 952 01:01:43,680 --> 01:01:46,980 But this is happening everywhere. And I just had an 953 01:01:46,980 --> 01:01:51,900 interesting, I'll just call it web three, but maybe Gen D, D, 954 01:01:51,900 --> 01:01:54,630 sin generation decentralized. 955 01:01:56,040 --> 01:01:58,620 So someone on Twitter pinged me and said, Hey, man, if you're 956 01:01:58,620 --> 01:02:02,760 looking for for some fiber out there in the hill country, you 957 01:02:02,760 --> 01:02:06,330 should check out next stream. And so, you know, someone 958 01:02:06,330 --> 01:02:08,640 contacted me and like, okay, incident, can we come out 959 01:02:08,640 --> 01:02:12,450 Friday, so this morning, they came out the CEO, this is a 960 01:02:12,480 --> 01:02:16,560 small local company that have 400 miles of dark fiber. 961 01:02:17,640 --> 01:02:20,490 They, they have their own backhaul straight into all the 962 01:02:20,490 --> 01:02:22,920 exchanges. And then like now, fuck it, there's so many people 963 01:02:22,920 --> 01:02:25,830 out here who do not want to be connected to spectrum, which is 964 01:02:25,830 --> 01:02:26,760 our only choice. 965 01:02:28,080 --> 01:02:32,370 And he says, No, we're, we're almost almost level Co Op. 966 01:02:34,050 --> 01:02:37,110 And so they have no huge investors that they have to have 967 01:02:37,110 --> 01:02:40,680 an exit for. And they just, they just want to provide good 968 01:02:40,680 --> 01:02:44,670 service without tracking and all kinds of crap to, you know, over 969 01:02:44,670 --> 01:02:48,780 to not a small community hill country. And I see this more and 970 01:02:48,780 --> 01:02:50,850 more, we're kind of going back to what it was. 971 01:02:52,680 --> 01:02:53,010 Yeah. 972 01:02:54,390 --> 01:02:57,390 Yeah, I can see, I mean, cuz that's really where this stuff 973 01:02:57,960 --> 01:03:03,210 is. That's where the web 3.0 becomes, what it claims to be, 974 01:03:03,570 --> 01:03:07,110 is when it becomes decentralized on the money side of it, as well 975 01:03:07,110 --> 01:03:11,310 as the technology side. Because I mean, because otherwise, we we 976 01:03:11,310 --> 01:03:16,620 did the tendency is going to be to re centralize I mean that 977 01:03:16,620 --> 01:03:19,020 centralized data, so you can do so do you want to wet three, 978 01:03:19,020 --> 01:03:24,090 come a web three, whatever it might be Startup Platform, who 979 01:03:24,090 --> 01:03:27,180 is still selling everybody's data on the back end. I mean, 980 01:03:27,180 --> 01:03:30,600 like that is out. And and what Brian is doing, I think is is 981 01:03:30,600 --> 01:03:33,630 the future of these types of developments, as much as it 982 01:03:33,630 --> 01:03:36,900 pains me to say, because hive, but 983 01:03:38,310 --> 01:03:42,270 where when you decentralize the money, then you in essence, 984 01:03:42,270 --> 01:03:46,800 create an opportunity for a type of defy where people can invest. 985 01:03:46,800 --> 01:03:49,710 So that's where you have the the high fund and you know, the Dow 986 01:03:49,710 --> 01:03:52,230 that he's talking about for those that are no decentralized, 987 01:03:52,410 --> 01:03:57,420 autonomous organization. And it's all based upon open source 988 01:03:57,420 --> 01:04:01,530 money that is accountable, trackable and programmable, so 989 01:04:01,530 --> 01:04:04,470 that you can have certainly, because you have some kind of 990 01:04:04,470 --> 01:04:07,440 democratic system where people vote Okay, Brian of London, 991 01:04:07,590 --> 01:04:12,960 you're going to get X amount of funds to work to get hundreds of 992 01:04:12,960 --> 01:04:17,490 votes. Yeah, hundreds of people to vote for me. Now. It's stake 993 01:04:17,520 --> 01:04:20,670 weighted. So there are some big whales who vote and you know 994 01:04:20,670 --> 01:04:24,420 that, that that's how it should be in a democracy. Yes, how it 995 01:04:24,420 --> 01:04:27,390 should be the more money the more votes, screw it exactly. 996 01:04:28,440 --> 01:04:34,530 But, but, but the point, actually, is that some of the 997 01:04:34,530 --> 01:04:39,180 biggest guys who voted for me, they voted last, and they waited 998 01:04:39,180 --> 01:04:44,160 to see the level of interest. So I, you know, getting 100 votes 999 01:04:44,160 --> 01:04:48,000 from people whose vote was worth point 00 1% of what I needed. 1000 01:04:48,540 --> 01:04:54,750 That is what got me the votes of the guy who could vote 20% It 1001 01:04:54,750 --> 01:04:58,350 is. It's a very important check and balance. And what it also 1002 01:04:58,350 --> 01:05:00,000 means is that there's no one person 1003 01:05:00,000 --> 01:05:05,160 on high, who can deny me? There's no one big enough to to 1004 01:05:05,160 --> 01:05:09,570 veto me. You know? And that's, that's the point, you know, I'd 1005 01:05:09,570 --> 01:05:13,410 have to piss off a large number of important people. But it's 1006 01:05:13,410 --> 01:05:15,960 not like having a boss, but I feel accountable to this 1007 01:05:15,960 --> 01:05:18,570 community. I have to write posts and what I'm doing, I have to 1008 01:05:18,570 --> 01:05:22,350 show them progress. It's much better than having a real job, 1009 01:05:22,350 --> 01:05:28,200 but it's still it. I think it's the it is it is an alternate 1010 01:05:28,200 --> 01:05:31,680 future. It's not that the thing is, it's not going to produce 1011 01:05:31,680 --> 01:05:34,740 the you know, the speed of progress of a Facebook that can 1012 01:05:34,740 --> 01:05:38,880 just throw, you know, I disagree. I disagree. I 1013 01:05:38,880 --> 01:05:41,850 disagree, man, look, look at look at what we've achieved a 1014 01:05:41,850 --> 01:05:45,570 year and a half. And Facebook is still doing podcasting. Somehow, 1015 01:05:45,570 --> 01:05:49,710 someday. You kidding me? No, no, no, no, no. And of course, it 1016 01:05:49,710 --> 01:05:52,830 helps that Brian married in Arabian princess with her own 1017 01:05:52,830 --> 01:05:53,460 dowry. 1018 01:05:55,980 --> 01:05:57,090 I really didn't. 1019 01:05:59,100 --> 01:06:02,490 Know, please. All right. Let me bring it back to the technology, 1020 01:06:03,000 --> 01:06:09,480 the party pooper. The. So why am I getting beam API errors? What 1021 01:06:09,480 --> 01:06:09,870 is that? 1022 01:06:11,910 --> 01:06:15,390 Because I haven't turned off the warning level and the Python. 1023 01:06:15,390 --> 01:06:17,550 I'll do that. And then just hide. I thought you did that. 1024 01:06:17,610 --> 01:06:21,630 No, I downloaded Yeah, I had that. I did I need to check. I 1025 01:06:21,630 --> 01:06:24,570 need to switch into a different. There's there's different Python 1026 01:06:24,570 --> 01:06:27,810 libraries, and we'll get into but they're just they're 1027 01:06:27,810 --> 01:06:30,570 nonsense warning was really and then you know, the thing is, 1028 01:06:30,630 --> 01:06:33,540 you're dealing here with API's and the back end, just the ping 1029 01:06:33,540 --> 01:06:36,900 pong ball isn't hitting the spoon, right, Dave? Yes. 1030 01:06:38,880 --> 01:06:42,450 You know, even Facebook went down. Remember that? Oh, no, 1031 01:06:42,450 --> 01:06:47,400 please. Yeah, no, no, you get no pass for that? No, but but the 1032 01:06:47,400 --> 01:06:52,620 point here is that I think that there are probably 30 to 40 1033 01:06:53,070 --> 01:06:56,190 significant individuals involved in running the API 1034 01:06:56,190 --> 01:07:00,660 infrastructure of high. And it is not a simple thing. It is 1035 01:07:00,660 --> 01:07:04,980 really not a simple thing. And the fact that they and they're 1036 01:07:04,980 --> 01:07:07,560 all running different versions of the software that they're on 1037 01:07:07,560 --> 01:07:11,070 different. They're in different cloud servers all over the 1038 01:07:11,070 --> 01:07:13,530 place. Some of them are in that, you know, my friend runs a 1039 01:07:13,530 --> 01:07:17,490 witness node in his apartment in Tel Aviv, and a backup in his 1040 01:07:17,490 --> 01:07:23,130 office across the street. This is it is peace Robinson. But 1041 01:07:23,130 --> 01:07:25,890 because it's his Robertson, you can't go shut it down, because 1042 01:07:25,890 --> 01:07:28,260 you can't walk into a service center and pull the plug 1043 01:07:28,260 --> 01:07:32,280 somewhere. Well, and the reason I brought it up was because 1044 01:07:33,870 --> 01:07:36,390 what when I was trying to troubleshoot that this morning, 1045 01:07:38,280 --> 01:07:41,820 Alex made the point as I restarted the service, restarted 1046 01:07:41,820 --> 01:07:47,220 the hive watcher. And he noticed that what I can't, I said, I 1047 01:07:47,220 --> 01:07:50,490 don't think I was getting hive updates. And I'm still, I'm 1048 01:07:50,490 --> 01:07:53,970 actually not clear if I was or not, because the the logging 1049 01:07:54,000 --> 01:07:58,200 that that that logging was covering so much of the screen 1050 01:07:58,200 --> 01:08:02,700 that I couldn't tell if anything else was coming through. I think 1051 01:08:02,700 --> 01:08:05,520 I was actually getting still updates. But I was coming in and 1052 01:08:05,520 --> 01:08:08,790 obscure the standard error was obscuring standard out, I think, 1053 01:08:08,790 --> 01:08:11,700 is what was happening. But I'm not sure about that yet. I get 1054 01:08:11,700 --> 01:08:14,850 it. But then when I restarted the service, yeah, yeah. And 1055 01:08:14,850 --> 01:08:17,820 Alex made the point, he said, and you didn't miss any updates, 1056 01:08:18,570 --> 01:08:21,960 which is because it goes it goes back and picks it all right, 1057 01:08:22,470 --> 01:08:24,540 then that's what people need to understand when you're watching 1058 01:08:24,540 --> 01:08:28,470 pod paying member is permanent. So if you're, if your system 1059 01:08:28,470 --> 01:08:33,510 goes down, like or begins to air out, or something like that, and 1060 01:08:33,510 --> 01:08:35,790 you have to reboot, or you have to make a configuration change, 1061 01:08:35,790 --> 01:08:39,570 or you need to do something different. You just restart it, 1062 01:08:40,170 --> 01:08:43,740 and it searches back an hour, and picks up where it left off. 1063 01:08:43,740 --> 01:08:47,040 And you get all the stuff that you missed. I mean, it's that's 1064 01:08:48,180 --> 01:08:51,660 one of the most beautiful parts of the system. Can we switch 1065 01:08:51,660 --> 01:08:56,790 gears to activity pub cross app comments? Yes, I want to hear 1066 01:08:56,790 --> 01:09:03,210 what Alex has, he has to say about where you think this? What 1067 01:09:03,210 --> 01:09:07,590 do you think? What do you think is going on? That we need to be 1068 01:09:07,590 --> 01:09:10,830 careful of or switch gears or liming? Give me your thoughts, 1069 01:09:10,830 --> 01:09:11,250 Alex. 1070 01:09:14,370 --> 01:09:17,910 So back when we first started talking about this middle last 1071 01:09:17,910 --> 01:09:20,910 year, some time when, you know, it was kind of hot and heavy 1072 01:09:20,910 --> 01:09:21,780 that died off. 1073 01:09:22,890 --> 01:09:26,490 We had some proposals and some developer meetings. The Martin 1074 01:09:26,490 --> 01:09:31,590 and Paul friend was upset that by default, you couldn't comment 1075 01:09:31,590 --> 01:09:35,700 on every podcast, which was the understandably confusing user 1076 01:09:35,700 --> 01:09:39,690 experience for an end user. And I had come up with 1077 01:09:41,280 --> 01:09:42,960 possibilities to work around that 1078 01:09:44,580 --> 01:09:49,620 by basically providing a default comment for every podcast, you 1079 01:09:49,620 --> 01:09:53,100 know, at the time I was thinking it was be the podcast index or 1080 01:09:53,100 --> 01:09:55,350 we know whatever doesn't really matter who 1081 01:09:57,090 --> 01:09:59,010 and I had come up with a way to 1082 01:10:00,659 --> 01:10:03,839 Call back, like, you know, provide, you know, you know, the 1083 01:10:03,839 --> 01:10:06,419 way you do with podcaster wallet where you would provide a 1084 01:10:06,419 --> 01:10:10,829 default, you provide a default lightning address and that RSS 1085 01:10:10,829 --> 01:10:13,019 feed has their own, then you, you know, you choose theirs. 1086 01:10:14,009 --> 01:10:17,549 Right, we could have a way to provide a default comment, you 1087 01:10:17,549 --> 01:10:21,239 know, through some service through an API and then call 1088 01:10:21,239 --> 01:10:23,369 back to an original comment while retaining some of the 1089 01:10:23,369 --> 01:10:25,109 original posts 1090 01:10:27,300 --> 01:10:30,420 that was shut down at the time. I don't really know why. 1091 01:10:32,730 --> 01:10:34,470 You know, people's opinions change. 1092 01:10:37,620 --> 01:10:38,190 I, 1093 01:10:40,050 --> 01:10:43,920 it feels like, this is turning into a nice, you know, having 1094 01:10:43,920 --> 01:10:47,640 default comments on some, you know, intention is not 1095 01:10:47,700 --> 01:10:51,300 decentralized service, you know, podcast indexical so far with a 1096 01:10:51,300 --> 01:10:53,640 centralized service, but you know, you don't have to use it. 1097 01:10:54,660 --> 01:10:56,130 It's not the same as comments. 1098 01:10:58,020 --> 01:11:02,730 I could see inviting a lot of potential for people being 1099 01:11:02,730 --> 01:11:04,860 upset. And 1100 01:11:06,660 --> 01:11:10,380 not a bad thing. But I feel like I feel like the the alternative 1101 01:11:10,380 --> 01:11:13,620 way to do that would just speed up provided period count 1102 01:11:13,620 --> 01:11:18,420 service. Wait, could you break that down or abstracted a little 1103 01:11:18,420 --> 01:11:21,300 bit more from me, Alex on to understand what exactly might 1104 01:11:21,300 --> 01:11:24,300 happen that might get people upset? That's, that's the only 1105 01:11:24,300 --> 01:11:25,230 thing I can understand. 1106 01:11:26,430 --> 01:11:26,970 Um, 1107 01:11:28,020 --> 01:11:29,760 well, I mean, if we start inviting comments on every 1108 01:11:29,760 --> 01:11:32,580 single podcast, you know, people have no idea about podcasting. 1109 01:11:32,700 --> 01:11:37,050 No, there's some comment about them. That didn't sign up for 1110 01:11:37,050 --> 01:11:40,650 comments. I see mean, people putting a comment and then they 1111 01:11:40,650 --> 01:11:42,870 like shit, I don't want my comment there. And I want to 1112 01:11:42,870 --> 01:11:45,960 take it off. And it's there for good. No, I think I think about 1113 01:11:45,960 --> 01:11:46,710 the podcast or, 1114 01:11:48,120 --> 01:11:50,490 you know, some some random podcaster has no idea about 1115 01:11:50,490 --> 01:11:53,970 podcasting, or something. Somebody uses podcast to run our 1116 01:11:53,970 --> 01:11:55,260 app to comment about them. 1117 01:11:58,950 --> 01:12:01,740 They want to know how to get rid of it. How is it any different 1118 01:12:01,740 --> 01:12:05,490 from Apple comments or reviews or whatever? 1119 01:12:06,570 --> 01:12:10,830 It's not right. People. brown nose, Apple. 1120 01:12:12,660 --> 01:12:15,960 Thank you, I think. Well, I think, though, that that's a 1121 01:12:15,960 --> 01:12:19,650 good point, though. We say How's it different? I think there's 1122 01:12:19,650 --> 01:12:25,080 two sides to that. The the most obvious side is it's the most 1123 01:12:25,080 --> 01:12:29,670 obvious answers is not. But there's also another part, it 1124 01:12:29,670 --> 01:12:34,380 also should be different. Like, so I think both of those things 1125 01:12:34,380 --> 01:12:38,220 can be true at the same time. You know, it's not necessarily 1126 01:12:38,220 --> 01:12:41,220 different. But actually what we're building should be better. 1127 01:12:41,340 --> 01:12:44,640 And it should be different. But okay, but if we're concerned, 1128 01:12:44,880 --> 01:12:47,130 okay, just so I understand the actual issue. 1129 01:12:48,450 --> 01:12:53,760 So the issue is, I didn't want comments on my podcast. Thank 1130 01:12:53,760 --> 01:12:57,720 you very much. And now here's these 10 apps that have these 1131 01:12:57,750 --> 01:13:01,380 comments that I don't like that I can't get rid of, is that what 1132 01:13:01,380 --> 01:13:04,680 the problem is? perceived problem? I mean, people complain 1133 01:13:04,680 --> 01:13:07,350 about this today with, you know, centralized services. I don't 1134 01:13:07,350 --> 01:13:11,010 know why the arguments are different from those. I'm just 1135 01:13:11,010 --> 01:13:15,330 I'm just asking that. That's the, that's the warning is that 1136 01:13:15,330 --> 01:13:19,170 could piss people off. That's the danger. Okay. So which, 1137 01:13:19,710 --> 01:13:26,100 which means that there's, I mean, the only way to do to do 1138 01:13:26,100 --> 01:13:29,160 that, I guess, would be to have some kind of 1139 01:13:30,300 --> 01:13:32,400 extra tag that says No comment. 1140 01:13:34,440 --> 01:13:37,290 Let's see, what we're talking about backing up for a second is 1141 01:13:37,320 --> 01:13:44,760 so Spurlock John's burlock. Did did a version of what Alex 1142 01:13:44,760 --> 01:13:48,300 proposed last year, which was he just spun up. And I mean, 1143 01:13:48,300 --> 01:13:51,510 literally last night just spun up a new service, the mini pub, 1144 01:13:51,510 --> 01:13:55,500 is that what that is? No, this is podcast. social.org. Oh, is 1145 01:13:55,560 --> 01:13:59,040 this this is essentially a headless mastodon. And it's a 1146 01:13:59,040 --> 01:14:01,980 beautiful system. And the way he did it was B looks like he's he 1147 01:14:01,980 --> 01:14:05,760 did this the right way. It's a headless Mastodon type system, 1148 01:14:06,060 --> 01:14:10,230 where, you know, it's got an API in front of it, where I can call 1149 01:14:10,380 --> 01:14:15,750 the API, if I have, if I have keys, I can call the API in for 1150 01:14:15,750 --> 01:14:21,090 a podcast, spin up a route post comment that I can then get back 1151 01:14:21,090 --> 01:14:22,230 and put into 1152 01:14:23,940 --> 01:14:28,140 for the app. So for apps to know about so I can call out and say 1153 01:14:28,140 --> 01:14:32,190 here, I want to route post. And then I put that in the feed. And 1154 01:14:32,190 --> 01:14:35,490 then everybody picks up that social interact tag and sees the 1155 01:14:35,490 --> 01:14:37,800 route post and then other activity post servers can 1156 01:14:37,800 --> 01:14:45,090 comment on it. Now that that, in turn gets seen by all the apps, 1157 01:14:45,390 --> 01:14:49,950 and then they can display the comments. I think Alex is saying 1158 01:14:49,950 --> 01:14:52,380 that the danger there is that 1159 01:14:53,610 --> 01:14:57,210 all of a sudden now you have apps, you have comments showing 1160 01:14:57,210 --> 01:14:59,970 up in apps, that the podcaster may not 1161 01:15:00,000 --> 01:15:06,480 want that to be a function? Now, the, your, your comment about is 1162 01:15:06,480 --> 01:15:11,160 that different from Apple is is correct. It's not different from 1163 01:15:11,160 --> 01:15:13,950 Apple. And to make that point, it's not different from Apple or 1164 01:15:13,950 --> 01:15:17,700 good pods, or pod chaser or any of these other services, they 1165 01:15:17,700 --> 01:15:22,110 all do that and you as a podcaster cannot control what 1166 01:15:22,350 --> 01:15:26,160 you get as a podcaster cannot control with the fact that some 1167 01:15:26,160 --> 01:15:28,890 platform spins up and allows people comment on your podcast, 1168 01:15:28,890 --> 01:15:32,640 and you just gonna have to let that go. You can't do that. But 1169 01:15:33,450 --> 01:15:37,890 I think in time, I think before this is all said and done, 1170 01:15:37,890 --> 01:15:42,420 though, my feeling is a lie. I like the breaking the chicken in 1171 01:15:42,420 --> 01:15:45,450 the egg that this represents. And I think that's why Alex 1172 01:15:45,450 --> 01:15:48,060 initially had that doll last year is because you got to 1173 01:15:48,060 --> 01:15:51,210 figure out some way to break the chicken egg problem with with a 1174 01:15:51,210 --> 01:15:55,710 protocol like with an issue like this. But before it's all said 1175 01:15:55,710 --> 01:16:02,280 and done. And before, we have to figure out some sort of way to 1176 01:16:02,280 --> 01:16:06,870 make that problem better than what exists now. 1177 01:16:08,100 --> 01:16:11,850 Whether it's a no comment tag or whatever, we there does need to 1178 01:16:11,850 --> 01:16:15,360 be a way to make this thing fixable. This is a beautiful 1179 01:16:17,640 --> 01:16:21,300 graphic representation of what what's going on on podcast 1180 01:16:21,300 --> 01:16:23,370 social.org This is really nice. 1181 01:16:24,540 --> 01:16:28,500 Yeah, it's done a good job here. I mean, I guess index is social. 1182 01:16:28,980 --> 01:16:35,100 No podcast. social.org. Does this. Yeah. That's that's for 1183 01:16:35,100 --> 01:16:37,770 lots Hello, running with scissors. It's what we do. Of 1184 01:16:37,770 --> 01:16:39,210 course, it's confusing, but 1185 01:16:41,130 --> 01:16:46,860 Alright, so now in this case, the podcaster would publish the 1186 01:16:46,860 --> 01:16:50,130 root post using this system using this kind of headless 1187 01:16:50,190 --> 01:16:56,550 Mastodon shim. Right. That's, that's the intended use. Now, if 1188 01:16:57,510 --> 01:17:01,260 I have a, I have an API key and Spurlock sent me one last night. 1189 01:17:01,830 --> 01:17:05,490 I could technically spin up a root root post for any podcast, 1190 01:17:05,490 --> 01:17:06,450 I want it right. 1191 01:17:07,680 --> 01:17:10,710 So that's the therein lies the problem is got it. 1192 01:17:12,660 --> 01:17:13,740 Yeah, right. Yeah. 1193 01:17:16,800 --> 01:17:20,280 So to be clear, I'm perfectly fine with the delegate service 1194 01:17:20,280 --> 01:17:24,210 for a podcast with us. Right. In fact, I think he should make 1195 01:17:24,210 --> 01:17:28,170 them pay for it. Yeah. That'd be a great service. Doing it by 1196 01:17:28,170 --> 01:17:29,700 default. And maybe 1197 01:17:30,870 --> 01:17:35,910 you misunderstood some what some people said. I, I think the 1198 01:17:35,910 --> 01:17:40,380 sheer hypocrisy of complaining about comments or reviews on 1199 01:17:40,410 --> 01:17:44,130 closed stores, closed ecosystems, but wanting to hear 1200 01:17:44,130 --> 01:17:46,350 is just insane. 1201 01:17:48,090 --> 01:17:52,470 Well, that if the I think the idea of having it be a paid 1202 01:17:52,470 --> 01:17:56,340 service is absolutely 100%. Legit, I hope I hope that he 1203 01:17:56,340 --> 01:18:00,000 does make it a paid service. Because that even more reduces 1204 01:18:00,000 --> 01:18:05,010 the, the potential for shenanigans. Right? But but you 1205 01:18:05,010 --> 01:18:08,880 still have to put the the root post into the feed. Am I 1206 01:18:09,960 --> 01:18:13,800 not correct? Yeah. So so the way this is is like, okay, so what I 1207 01:18:13,800 --> 01:18:15,960 do is I take 1208 01:18:16,980 --> 01:18:20,850 you know, take a photo and put a make a comment, thread, post a 1209 01:18:20,850 --> 01:18:24,150 route post is what I've been doing to Yeah. And I take that 1210 01:18:24,150 --> 01:18:28,500 and I give it to you, or you see me, you take your URL, paste it 1211 01:18:28,500 --> 01:18:31,800 into the feed? Well, that's because I have a mastodon 1212 01:18:31,800 --> 01:18:35,010 account. I know I understand. So so you should definitely be 1213 01:18:35,010 --> 01:18:39,600 paying for, for using that or set up your own Macedon account, 1214 01:18:39,600 --> 01:18:40,140 whatever. 1215 01:18:42,120 --> 01:18:45,240 So this seems like a pretty because I guess the bottom line 1216 01:18:45,240 --> 01:18:51,630 is, there's no danger if you don't want these comments, it to 1217 01:18:51,630 --> 01:18:55,440 appear in the apps then don't put a root post in your feed is 1218 01:18:55,440 --> 01:18:57,330 that isn't doesn't that solve everything? 1219 01:18:58,530 --> 01:19:04,890 It does is as long as you don't have D 5000. Yes, default? Yes. 1220 01:19:04,950 --> 01:19:09,000 Yes. As long as it's not okay. So Alright, so now I remember 1221 01:19:09,000 --> 01:19:14,070 the the original conversation. And that was it. Right? I think 1222 01:19:14,070 --> 01:19:16,560 it was Martin who said well, I don't want to have an app that 1223 01:19:16,560 --> 01:19:23,430 only has the capability to comment if the podcaster has has 1224 01:19:23,460 --> 01:19:27,150 enabled that he says and he's looking at it from the pod 1225 01:19:27,150 --> 01:19:31,440 friend friendly app, where everything's obvious and so for 1226 01:19:31,440 --> 01:19:33,960 him it was not obvious for 1227 01:19:35,010 --> 01:19:38,250 for you be able to comment on on one show, but not on the other 1228 01:19:38,250 --> 01:19:41,520 because they're not 2.0 or whatever. So he's looking at it 1229 01:19:41,520 --> 01:19:43,950 from a customer standpoint, 1230 01:19:45,030 --> 01:19:48,420 from what he wants to deliver, which I personally think is the 1231 01:19:48,420 --> 01:19:49,560 wrong way to look at it. 1232 01:19:50,580 --> 01:19:54,240 I mean, that then you might as well put in a fake value block 1233 01:19:54,240 --> 01:19:54,960 for everybody. 1234 01:19:56,490 --> 01:19:59,970 Now or or chapters or whatever or did the then you know what 1235 01:20:00,000 --> 01:20:03,390 I have a transcript for no agenda, but I don't have it for 1236 01:20:03,420 --> 01:20:04,470 DHS unplugged. 1237 01:20:05,970 --> 01:20:09,270 Yeah, there's a, I feel like this is 1238 01:20:10,469 --> 01:20:14,729 this is sort of where thing, this is where we already, we 1239 01:20:14,729 --> 01:20:16,859 always knew this, we knew this from the very beginning that 1240 01:20:16,859 --> 01:20:18,629 comments was going to be the hardest thing. 1241 01:20:19,860 --> 01:20:22,980 And it's not is hard, not just for technical reasons, but also 1242 01:20:22,980 --> 01:20:26,940 for political reasons, and social reasons. And all those 1243 01:20:26,940 --> 01:20:29,520 things, because social networking and commenting is 1244 01:20:29,520 --> 01:20:36,840 hard by itself. So this, I think there's multiple problems that 1245 01:20:36,840 --> 01:20:41,070 are being that that have to be addressed. I think John, is 1246 01:20:41,070 --> 01:20:45,390 addressing one of those issues, but just, you know, rolling the 1247 01:20:45,390 --> 01:20:48,390 sleeves up and building a service that works like this. 1248 01:20:48,390 --> 01:20:51,180 And he's, he's solving the issue of, 1249 01:20:52,290 --> 01:20:55,410 there's a chicken and egg problem, we got to get some, we 1250 01:20:55,410 --> 01:20:59,190 got to get that broken somehow. And also, 1251 01:21:01,200 --> 01:21:03,240 people need to see things 1252 01:21:04,470 --> 01:21:09,030 they don't, most normal people don't think in terms of 1253 01:21:09,030 --> 01:21:12,360 protocols and white papers and specs, most people think in 1254 01:21:12,360 --> 01:21:17,760 terms of shiny things. And so having a website that, that 1255 01:21:17,760 --> 01:21:20,910 looks having a website, this looks good, explains everything, 1256 01:21:20,910 --> 01:21:23,190 and then also has an API attached like this sort of 1257 01:21:23,190 --> 01:21:28,200 canned, nice system that you can use as a stop gap. I think he 1258 01:21:28,200 --> 01:21:31,440 saw that as just, you know, let's just this this is a way to 1259 01:21:31,440 --> 01:21:35,340 move this thing forward and get some traction here. Then, in the 1260 01:21:35,340 --> 01:21:38,010 future, you know, this becomes a paid service, or however that 1261 01:21:38,010 --> 01:21:41,490 worked. And then everybody else sees that it works and can run 1262 01:21:41,490 --> 01:21:45,090 their own systems on the each on their hosting providers. And I 1263 01:21:45,090 --> 01:21:48,840 do, I'll say that, you know, channeling my inner talk Cochran 1264 01:21:48,840 --> 01:21:52,860 yet again, I will say I know of at least one host that is 1265 01:21:52,860 --> 01:21:57,150 seriously, you know, looking into cross app comments, because 1266 01:21:58,140 --> 01:21:59,670 cross comments 1267 01:22:01,530 --> 01:22:04,080 can be a way to really, 1268 01:22:06,120 --> 01:22:09,360 to really make make a visual impact on the podcasting 1269 01:22:09,360 --> 01:22:13,080 experience. Tell us I know, I know, people are looking at this 1270 01:22:13,080 --> 01:22:15,780 and to and taking note of the way thing of the way this stuff 1271 01:22:15,780 --> 01:22:19,200 works. And so having something visual out there, I think will 1272 01:22:19,200 --> 01:22:23,460 help to let everybody because some some, you know, some 1273 01:22:23,640 --> 01:22:26,370 hosting companies are very visionary. They look forward to 1274 01:22:26,370 --> 01:22:29,550 things, other hosting companies, they just need to be sort of, 1275 01:22:29,820 --> 01:22:32,370 you know, beaten over the head with it and say, Hey, so now 1276 01:22:32,370 --> 01:22:36,570 here's here's the reverse issue. I'm just thinking through. Now, 1277 01:22:36,570 --> 01:22:44,130 for a podcast app, in order to comment, you need to have the 1278 01:22:44,130 --> 01:22:48,690 user needs to have access to an activity pub account. 1279 01:22:50,490 --> 01:22:53,130 That's what so that's what John Spurlock is solving with any 1280 01:22:53,130 --> 01:22:56,520 pub, which is great. That's what a podcast app can use to they 1281 01:22:56,520 --> 01:22:58,830 can they can integrate that right into the code. You mean. 1282 01:22:59,610 --> 01:23:01,830 Right? There's still do their own account system and so forth. 1283 01:23:01,950 --> 01:23:03,390 Right. Yeah. Right. Right. 1284 01:23:04,920 --> 01:23:08,100 And so that's something that the podcast app developer runs 1285 01:23:08,400 --> 01:23:09,930 centrally on their server. 1286 01:23:11,730 --> 01:23:14,130 Or is it something that that goes right into the code for the 1287 01:23:14,130 --> 01:23:17,310 app itself? I think he's got they can run running Cloudflare 1288 01:23:17,310 --> 01:23:20,010 serverless. But yeah, it's still their service. 1289 01:23:21,120 --> 01:23:23,970 Okay, well, I think we've solved it, when do we start building 1290 01:23:25,740 --> 01:23:30,960 it? So my question my question to you as when thinking about 1291 01:23:30,960 --> 01:23:34,050 this last night, it I kind of had a hard time sleeping because 1292 01:23:34,050 --> 01:23:37,530 Birla released this right, you know, got it like nine o'clock. 1293 01:23:38,220 --> 01:23:41,880 And I was trying to figure out what my thoughts were on us 1294 01:23:41,880 --> 01:23:43,770 texting you and stuff. What? 1295 01:23:45,510 --> 01:23:47,130 How can 1296 01:23:48,240 --> 01:23:51,720 can comments when things are commented on? 1297 01:23:52,920 --> 01:23:57,690 Couldn't that be on a pod? On pod ping as well? Did there's 1298 01:23:57,690 --> 01:23:58,830 been a new comment 1299 01:24:00,750 --> 01:24:02,880 at some point in the future, like, like somebody has 1300 01:24:02,880 --> 01:24:09,450 commented, or so review live quiet here. Because you miss and 1301 01:24:09,600 --> 01:24:12,090 let me be clear, Brian, this is not I'm not talking about 1302 01:24:12,090 --> 01:24:14,790 putting my comments themselves on hive and talking about them. 1303 01:24:14,790 --> 01:24:19,080 Notice, I'm also I'm also not as well, because even with three 1304 01:24:19,080 --> 01:24:22,980 speakers stuff, when we're looking, you know, one of the 1305 01:24:22,980 --> 01:24:26,760 big guys bind freespeak, they call me down his name. He keeps 1306 01:24:26,760 --> 01:24:28,950 saying, you know, we're gonna look back in 10 years time, and 1307 01:24:28,950 --> 01:24:31,680 we're going to look at LOL, and we're going to be telling our 1308 01:24:31,680 --> 01:24:35,520 kids that was the days when we could still post lol on hive, 1309 01:24:35,520 --> 01:24:40,290 and it didn't cost a fortune. But it so I don't think carrying 1310 01:24:40,320 --> 01:24:44,040 vast quantities of ephemeral comment traffic is the future 1311 01:24:44,040 --> 01:24:45,480 for hive. But 1312 01:24:46,830 --> 01:24:49,200 I keep coming back, you know, it's like it's always I'm always 1313 01:24:49,200 --> 01:24:52,140 looking, who's running the service and who's incentivized 1314 01:24:52,140 --> 01:24:56,130 to run the service. So as long as there is a service that a 1315 01:24:56,130 --> 01:25:00,000 podcaster or someone has to pay for, to make sure that 1316 01:25:00,000 --> 01:25:04,530 It's gonna be there. You know, I'm okay with that. As to as to 1317 01:25:04,530 --> 01:25:08,280 announcing all the comments on pod ping. That's the same as 1318 01:25:08,280 --> 01:25:10,920 storing them to be brutally honest. I mean, most comments 1319 01:25:10,920 --> 01:25:14,280 are not much longer than the link to them. So, 1320 01:25:15,839 --> 01:25:18,179 you know, if we were going to announce them, we could just 1321 01:25:18,179 --> 01:25:21,539 post them on that? Well, there's two parts of this question. 1322 01:25:24,270 --> 01:25:28,680 So by default, activity streams, which is what activity pub uses, 1323 01:25:29,790 --> 01:25:32,430 is the mechanism that sort of is getting noticed get notified 1324 01:25:32,430 --> 01:25:33,270 into comments. 1325 01:25:34,830 --> 01:25:38,490 That's already built into the system when someone posts on no 1326 01:25:38,490 --> 01:25:42,720 agenda social, that the server sends an update to my guest. And 1327 01:25:42,720 --> 01:25:45,510 if that social, if you're following them already, 1328 01:25:46,950 --> 01:25:50,940 the mechanisms of how that works and everything gets cached and 1329 01:25:50,940 --> 01:25:53,670 so forth is a lot more complicated. But 1330 01:25:55,200 --> 01:25:59,340 theoretically, no, we don't need that. But that's redundant us. 1331 01:26:00,330 --> 01:26:02,400 Yeah. And it's not a perfect system, either, you know, 1332 01:26:02,400 --> 01:26:04,740 different servers work differently. So it could 1333 01:26:04,740 --> 01:26:09,480 probably be improved. However, that does bring up the the topic 1334 01:26:09,480 --> 01:26:16,770 of how do you notify an app or a server user, the external 1335 01:26:16,770 --> 01:26:18,900 content has been updated in the feed. 1336 01:26:20,790 --> 01:26:22,950 It applies to images and so forth. 1337 01:26:24,990 --> 01:26:26,250 Right, exactly. 1338 01:26:27,810 --> 01:26:30,990 And we want to avoid that that's, that's the hardest 1339 01:26:30,990 --> 01:26:34,020 problem we haven't popping right now. Because we only have so 1340 01:26:34,020 --> 01:26:34,380 much 1341 01:26:35,730 --> 01:26:41,790 available bandwidth, so to say, to send updates, and I'm trying 1342 01:26:41,790 --> 01:26:44,580 to think about how to do that efficiently without DDoS and 1343 01:26:44,580 --> 01:26:45,150 servers. 1344 01:26:47,100 --> 01:26:49,380 And that could be applied to comments, too. So. 1345 01:26:50,760 --> 01:26:54,690 Okay, now's a good discussion, because that yeah, I can see the 1346 01:26:54,690 --> 01:26:56,940 issues there. That has to be tread that that's ground that 1347 01:26:56,940 --> 01:26:59,160 has to be tread carefully. Yep. 1348 01:27:00,270 --> 01:27:04,890 Shall we? thank a few people, Dave? Oh, yes, sure. Yeah. And I 1349 01:27:04,890 --> 01:27:08,520 want to remind everybody, this is a value for value podcast, 1350 01:27:08,520 --> 01:27:12,150 the whole podcast index project is value for value. 1351 01:27:13,230 --> 01:27:16,830 Interesting thread this morning, although I, I typically despise 1352 01:27:16,860 --> 01:27:20,640 people saying, you know, what does it cost you to run this. 1353 01:27:23,370 --> 01:27:26,880 But there was an interesting post, I guess, Marco talked 1354 01:27:26,880 --> 01:27:30,990 about his server infrastructure in the context of Linode, being 1355 01:27:30,990 --> 01:27:36,420 purchased by Akamai, and that he spends about $5,000 a month. So 1356 01:27:36,420 --> 01:27:40,560 I just want everyone to realize that's, that that may be what 1357 01:27:40,560 --> 01:27:44,340 Marco pays, but I'm just looking at the pure value. You know, 1358 01:27:44,340 --> 01:27:49,470 there's, there's 15 apps running off podcast index.org. And 1359 01:27:49,500 --> 01:27:52,470 that's the type of value it would take for those apps 1360 01:27:52,470 --> 01:27:55,260 individually, to run a professional system, let's just 1361 01:27:55,260 --> 01:27:57,750 say that's, that's the mark in the sand, it's not true. 1362 01:27:58,920 --> 01:28:02,340 But the the value that this project brings, and that we need 1363 01:28:02,340 --> 01:28:03,240 to continue 1364 01:28:04,470 --> 01:28:08,460 to compensate, we'll just we'll only go up, we're keep working, 1365 01:28:08,460 --> 01:28:11,640 we're keeping it as lean as possible. And until we have a 1366 01:28:11,640 --> 01:28:15,300 lot more value for value flowing, certainly with the with 1367 01:28:15,300 --> 01:28:17,820 the streaming sets, we're going to need help, we're gonna need 1368 01:28:17,820 --> 01:28:20,970 help all the help we can get we, you know, we do need a little 1369 01:28:20,970 --> 01:28:25,140 bit of a war chest here. And it's an IT RIGHT NOW also 1370 01:28:25,140 --> 01:28:28,380 liquidity wise on the node, we only have a couple million SATs 1371 01:28:28,380 --> 01:28:29,610 left to open channels. 1372 01:28:30,630 --> 01:28:33,900 That's what I was actually talking to you about that Alex 1373 01:28:33,900 --> 01:28:36,150 the other night, or the other day, it was we're talking about 1374 01:28:36,300 --> 01:28:39,210 liquidity and lightly liquidity and stuff. And that, you know, I 1375 01:28:39,210 --> 01:28:41,550 had mentioned to you that we're like one of the things that 1376 01:28:41,850 --> 01:28:44,820 podcast index tries to do on our node, that's why we don't ever 1377 01:28:44,820 --> 01:28:47,850 take any money out of the out of podcast index out of the 1378 01:28:48,150 --> 01:28:52,800 company, is because the, the money has to stay in there in 1379 01:28:52,800 --> 01:28:56,430 order to weather the storm of let's just say we get six months 1380 01:28:56,430 --> 01:28:59,790 with terrible donations, and we gotta have a big war chest in 1381 01:28:59,790 --> 01:29:02,640 order to survive that, but also on the podcast and on the 1382 01:29:02,640 --> 01:29:06,390 lightning nodes. We gotta, we gotta leave all those stats on 1383 01:29:06,390 --> 01:29:09,990 the server. So that those that those channels can be opened 1384 01:29:09,990 --> 01:29:12,780 when people come in all the time, and we open channels to 1385 01:29:13,080 --> 01:29:17,550 have 140 channels now. Yeah, and each channel is because you 1386 01:29:17,550 --> 01:29:19,680 know, you have to be able to manage these channels. So for 1387 01:29:19,680 --> 01:29:22,890 us, there's there is kind of like a lower limit. So we have 1388 01:29:22,890 --> 01:29:28,080 to be at least 300,000 SATs. That's 150 bucks, we tie up for 1389 01:29:28,080 --> 01:29:31,050 someone who just bought a fucking Umbral node. So I'm just 1390 01:29:31,050 --> 01:29:35,760 saying okay, just saying this has been this has been my you 1391 01:29:35,760 --> 01:29:40,050 know, I I've come to love some aspects of lightning, especially 1392 01:29:40,050 --> 01:29:42,960 the wallets, the lightweight wallets on phones, for that is 1393 01:29:42,960 --> 01:29:48,870 fantastic. But on the backend side, the stupid habit expecting 1394 01:29:48,870 --> 01:29:51,150 that this is going to be super distributed and millions of 1395 01:29:51,150 --> 01:29:54,180 people are going to run nodes is ridiculous. I mean, I see what 1396 01:29:54,180 --> 01:29:58,110 it takes to run a node properly. That's changing. Brian, I'm 1397 01:29:58,110 --> 01:29:59,970 going to stop you before you it is you 1398 01:30:00,000 --> 01:30:02,730 embarrass yourself that's changing very rapidly. 1399 01:30:04,440 --> 01:30:08,220 There's fast to come very, very rapidly, six months, they mean, 1400 01:30:08,220 --> 01:30:11,160 it's happening very quickly, there's all kinds of 1401 01:30:11,250 --> 01:30:12,630 noncustodial 1402 01:30:13,950 --> 01:30:17,220 systems being built right now, that will, 1403 01:30:18,960 --> 01:30:24,000 that will make this problem go away, at least and you know, 1404 01:30:24,090 --> 01:30:27,870 people will have to pay. So you still have to pay for your 1405 01:30:27,870 --> 01:30:32,460 liquidity. And you just won't have to manage that. That's Yes. 1406 01:30:32,520 --> 01:30:37,440 If we if one could my complaint is and let me let me let me call 1407 01:30:37,440 --> 01:30:41,280 Manila doing the routing. Let me let me call me let me system let 1408 01:30:41,280 --> 01:30:41,910 me qualify 1409 01:30:43,140 --> 01:30:46,650 you won't have to put the liquidity in but you will still 1410 01:30:46,650 --> 01:30:49,980 have to pay for liquidity that you're you have to pay for 1411 01:30:49,980 --> 01:30:54,150 liquidity one way or the other. Now, it could be you know, one 1412 01:30:54,150 --> 01:30:58,950 penny a month or or a point on your transactions, you're gonna 1413 01:30:58,950 --> 01:31:02,400 have to pay for it somehow. And I understand that, you know, 1414 01:31:02,790 --> 01:31:03,240 it's 1415 01:31:05,100 --> 01:31:05,940 you don't like it? 1416 01:31:07,920 --> 01:31:11,670 Like it's not that I don't like it is that I want to look out 1417 01:31:11,670 --> 01:31:15,240 there and understand that the network is sustainable without 1418 01:31:15,270 --> 01:31:19,440 it being captured by a small number of venture capital things 1419 01:31:19,470 --> 01:31:22,470 but that's not it there's no evidence there's no evidence of 1420 01:31:22,470 --> 01:31:25,680 that happening and there's there's several I hate heavily 1421 01:31:25,680 --> 01:31:30,210 venture capital funded. Lightning labs itself is heavily 1422 01:31:30,510 --> 01:31:35,430 venture funded. I know I would say happy we route as many 1423 01:31:35,430 --> 01:31:39,060 payments as anybody else on the entire net worth more we don't 1424 01:31:39,060 --> 01:31:42,780 make mine we're not it. What do you mean? Yes, we do. Our 1425 01:31:42,780 --> 01:31:45,960 balance goes up all the time. You're talking about your your, 1426 01:31:46,350 --> 01:31:48,060 your investment? 1427 01:31:49,560 --> 01:31:53,760 Can Can someone make 6% a year on the on the on a balance of 1428 01:31:53,760 --> 01:31:54,750 Bitcoin? Oh, no. 1429 01:31:55,770 --> 01:32:01,290 No. 6% Were you getting out block fi in crypto.com? So the 1430 01:32:01,290 --> 01:32:04,800 point is, hold on, hold on, hold on, Dana bull is that for Tomba 1431 01:32:04,800 --> 01:32:07,950 sustained Hold on a second, don't get me started. That's all 1432 01:32:07,950 --> 01:32:11,490 shit coins. That's all tether type stuff that is in fact 1433 01:32:11,490 --> 01:32:14,670 inflationary to the entire economy and weigh against that 1434 01:32:14,670 --> 01:32:17,460 shit. You're not keeping your Bitcoin when you're doing that. 1435 01:32:17,520 --> 01:32:22,680 And worse, those very companies that are giving you six 810 12% 1436 01:32:22,920 --> 01:32:25,920 You have to have their shit coin, you have to have at least 1437 01:32:25,920 --> 01:32:29,280 one other stable coin. And you don't own your Bitcoin and there 1438 01:32:29,280 --> 01:32:33,990 you helping people short Bitcoin with it. I just say all of that. 1439 01:32:34,380 --> 01:32:38,940 I just, I'm just nervous about it comes back to what Moxie 1440 01:32:38,940 --> 01:32:41,790 Marlinspike wrote in his blog post a few weeks ago, and he was 1441 01:32:42,000 --> 01:32:45,420 hammering away at NF T's which I agree with the guy who sold out 1442 01:32:45,420 --> 01:32:50,940 his company to a shit coin. Yes, but the point is, the point is 1443 01:32:51,000 --> 01:32:54,360 not people just can't run servers, the vast majority of 1444 01:32:54,390 --> 01:32:57,660 commerce, they won't have to that that's yeah, that's that's 1445 01:32:57,660 --> 01:33:03,120 really nd now, just as an example, Brees is noncustodial. 1446 01:33:03,150 --> 01:33:08,070 The breeze app is your own node. Now. There's significant issues 1447 01:33:08,070 --> 01:33:12,660 with mobile, for PC, I know for key send, but that's about it. 1448 01:33:12,660 --> 01:33:15,960 And this is being solved is going to be solved as the you're 1449 01:33:15,960 --> 01:33:20,190 going to see. In the next six months, you're going to see a 1450 01:33:20,190 --> 01:33:24,810 huge shift in in the in the necessity for note. 1451 01:33:27,030 --> 01:33:30,990 The the the liquidity requirements. I like that 1452 01:33:30,990 --> 01:33:34,020 because not only custodial, but you still depend on them for for 1453 01:33:34,020 --> 01:33:37,380 the channels, right. But yeah, what's going down the other day 1454 01:33:37,380 --> 01:33:42,450 for for a few hours and people were screaming and breeze. Yeah, 1455 01:33:42,480 --> 01:33:46,320 you know, they had a complete Bobby but but that's and this is 1456 01:33:46,320 --> 01:33:48,960 saying my note goes down whenever I upgraded it takes 10 1457 01:33:48,960 --> 01:33:51,840 minutes, and I need to move it off this up this raspberry pi 1458 01:33:51,870 --> 01:33:54,300 because I realized now that that's way, way, way too 1459 01:33:54,300 --> 01:33:58,050 underpowered for what's happening on my node. But but 1460 01:33:58,050 --> 01:34:01,590 these are all these are all things that I I'm not, I'm not 1461 01:34:01,590 --> 01:34:06,330 an unfair of the system. I'm just looking and I'm hoping that 1462 01:34:06,330 --> 01:34:10,050 it's sustainable without it being captured by big 1463 01:34:10,050 --> 01:34:13,080 centralized venture capital. Right? I'm just just telling 1464 01:34:13,080 --> 01:34:17,130 you, there's the venture capitalists are there, the huge 1465 01:34:17,130 --> 01:34:21,300 wambo private channels, they're all there. We have built our own 1466 01:34:21,300 --> 01:34:24,000 little micro network right outside of all of that and it 1467 01:34:24,000 --> 01:34:25,170 works perfectly well. 1468 01:34:26,190 --> 01:34:30,330 Good. It really does. Now, we don't make a lot of money. 1469 01:34:30,720 --> 01:34:33,930 routing the payments, we make 1% off of 1470 01:34:34,950 --> 01:34:38,160 off of off of the transaction, which we're hoping will be 1471 01:34:38,160 --> 01:34:41,250 enough moving forward. But everybody like you know, Alex, 1472 01:34:41,250 --> 01:34:43,500 you're looking at your your system, you're going to charge 1473 01:34:43,500 --> 01:34:47,040 people 20% So this is how it will work. 1474 01:34:48,210 --> 01:34:52,110 And it will work. But no one can I mean it was built by venture 1475 01:34:52,110 --> 01:34:54,930 capital. Let's just be honest about it. Lightning Labs is a 1476 01:34:54,930 --> 01:34:59,730 100% venture funded company. Jack Dorsey is all his own but 1477 01:34:59,730 --> 01:35:00,000 you know all 1478 01:35:00,000 --> 01:35:02,700 other other people learned as well. And there's there's 1479 01:35:02,700 --> 01:35:08,400 others. So it's venture capital breeze takes venture capital. 1480 01:35:09,870 --> 01:35:14,190 So, capturing it, this is I had a conversation with my wife this 1481 01:35:14,190 --> 01:35:17,070 morning says, Well, you know, you know, just all of these 1482 01:35:17,070 --> 01:35:19,470 fuckers with, you know, all these big hedge funds and 1483 01:35:19,470 --> 01:35:21,900 BlackRock, they want to come in and they want to buy up all the 1484 01:35:21,900 --> 01:35:24,810 Bitcoin. And I said, so let's just talk about what that means 1485 01:35:24,810 --> 01:35:28,200 because it can't be done. And here's why. So it's part of the 1486 01:35:28,200 --> 01:35:32,550 same ecosystem agree with that. But But Bitcoin Yeah, it's 1487 01:35:32,550 --> 01:35:37,140 beyond that. I'm still skeptical. But using it. I'm 1488 01:35:37,140 --> 01:35:40,170 using it every day. I'm building right now I'm building on it. I 1489 01:35:40,170 --> 01:35:43,920 love it. And as I say, for the wallet, stuff on phones, there's 1490 01:35:43,920 --> 01:35:47,490 nothing like it. But the process of snapping little QR codes. It 1491 01:35:47,490 --> 01:35:50,640 just works. It's fantastic. I'm doing it 50 times a day 1492 01:35:50,640 --> 01:35:52,290 internally, while testing. 1493 01:35:54,210 --> 01:35:57,720 Right. But I'm looking forward to the day I can replace my day 1494 01:35:57,720 --> 01:36:02,880 job with it. But that's replaced what replaced what my day job 1495 01:36:02,940 --> 01:36:07,350 with the Oh, well. You and me both brother. I want to replace 1496 01:36:07,350 --> 01:36:10,470 Dave's day job. That's that's my mission in life is how do I get 1497 01:36:10,470 --> 01:36:14,670 Dave away from that damn office to soul deadening job? 1498 01:36:16,770 --> 01:36:17,250 Well, 1499 01:36:18,990 --> 01:36:20,280 let's let's think some people 1500 01:36:22,380 --> 01:36:25,890 think that was a long way around, wasn't it? Yes. Yes. 1501 01:36:25,920 --> 01:36:29,160 These are people that are trying to also get us all away from our 1502 01:36:29,160 --> 01:36:34,710 day jobs. Yes, they are. Shantell Angus is in his $350 1503 01:36:34,740 --> 01:36:37,590 Oh, is that a big baller? That's a big bus. 1504 01:36:40,290 --> 01:36:41,190 Blade. Oh, 1505 01:36:42,240 --> 01:36:48,150 nice. Thank you, Chantal. Any No, no, no, no, no, thank you. 1506 01:36:48,510 --> 01:36:49,950 That's what I'm talking about. 1507 01:36:52,830 --> 01:36:57,690 Rick, from glued to the screens, and it's $100. No note. And 1508 01:36:57,870 --> 01:37:01,260 another big. I mean, we had sad puppy last week. And now it's 1509 01:37:01,260 --> 01:37:05,430 like, well, that's how it goes. That's that's you got to ask if 1510 01:37:05,430 --> 01:37:06,780 you don't ask people don't help. 1511 01:37:08,310 --> 01:37:11,040 Yeah, that those are two big papers for the week. Thank you, 1512 01:37:11,040 --> 01:37:14,400 Chantal. And Rick, thank you very much. Yeah, that's great. 1513 01:37:15,030 --> 01:37:17,190 And if you have a note, please send it to me and I'll read it. 1514 01:37:17,400 --> 01:37:19,530 I read it next week. I asked them both if they hadn't noticed 1515 01:37:19,530 --> 01:37:22,650 and neither one of them responded. So outside of make 1516 01:37:22,650 --> 01:37:28,830 good booster Graham from last week from Arno for 25,000 to 33 1517 01:37:28,830 --> 01:37:35,490 cents. I think he sent it to your boost monitor Umbral 1518 01:37:35,730 --> 01:37:40,290 instead of to us Yeah. And he said thank you Dave for helping 1519 01:37:40,290 --> 01:37:43,440 to send booster grams boost 25 Oh 33 1520 01:37:45,120 --> 01:37:48,330 And so what what was the the number of sets you had? 1521 01:37:48,990 --> 01:37:54,420 25,033 33 I don't see it. 1522 01:37:56,430 --> 01:37:58,950 Well, I'm going to credit me anyway. Yeah, no matter no 1523 01:37:58,950 --> 01:38:00,210 matter what. Okay, sure. 1524 01:38:01,740 --> 01:38:06,750 So we got seemly flip over here. Having to read these off the 1525 01:38:06,750 --> 01:38:08,940 screen because my printer would not print. 1526 01:38:10,500 --> 01:38:16,470 Okay, we get it Scott. S dot c dot O dot t dot t. Fountain gave 1527 01:38:16,470 --> 01:38:21,600 us 10,420 SATs and he says go podcasting 2.0 puff puff pass. 1528 01:38:24,180 --> 01:38:28,500 What is that? puff puff pass? Oh, seems like a drug reference 1529 01:38:28,500 --> 01:38:32,700 to me. Dave. Sorry. A little slow on the uptake. Let me let 1530 01:38:32,700 --> 01:38:33,270 me try it. 1531 01:38:36,510 --> 01:38:42,120 Now pass it pass it. No, no, not yet. Yeah, pro Pro. There we go. 1532 01:38:43,440 --> 01:38:46,560 Over to you Alex. That will make you quit your day job. 1533 01:38:47,640 --> 01:38:48,690 Not for good reasons. 1534 01:38:50,760 --> 01:38:54,570 Cali bear of the intergalactic boom box and it's 25,000 SATs 1535 01:38:54,570 --> 01:38:58,080 through fountain and he says the intergalactic boombox podcast 1536 01:38:58,080 --> 01:39:01,650 that way so you still mess it up the intergalactic boombox 1537 01:39:01,650 --> 01:39:06,810 podcast, podcast. Jet sets. Do you cool cats? Please hit me 1538 01:39:06,810 --> 01:39:08,670 with a Paul Stanley boost. Oh 1539 01:39:15,570 --> 01:39:16,170 beautiful. 1540 01:39:17,340 --> 01:39:19,800 Thank you. Thanks for chatting the SATs brother. 1541 01:39:21,390 --> 01:39:27,000 Forged foe, sinister. Rove ducks and ethers tu tu tu tu through 1542 01:39:27,000 --> 01:39:28,440 fountain and he says quack quack 1543 01:39:34,050 --> 01:39:41,160 thank you for FFO blueberry. Says 8888 SATs boost. Oh, he 1544 01:39:41,160 --> 01:39:44,820 sent it through the command line. He's old school. I'd love 1545 01:39:44,820 --> 01:39:45,870 that. I love 1546 01:39:47,220 --> 01:39:50,940 it's a boost chain. Yeah. Who's the next in the bouschet? Yeah, 1547 01:39:50,940 --> 01:39:53,490 who's boosting in the chain? Yeah, I like this boost chain 1548 01:39:53,490 --> 01:39:56,220 idea. Oh, here we go. Here we go. 1549 01:39:57,240 --> 01:39:59,970 Through breeze 280 1550 01:40:00,000 --> 01:40:04,380 10,420 SAS holy crap just 1551 01:40:05,850 --> 01:40:09,270 says paywalls are broken information wants to be free and 1552 01:40:09,270 --> 01:40:14,400 value unbounded. There GG. Aha. Did he All right, hold on. Let 1553 01:40:14,400 --> 01:40:16,140 me give me my right the lightning boost. 1554 01:40:17,520 --> 01:40:21,270 Me go. Thanks there Gigi. Yeah, we're having him. He'll be on 1555 01:40:21,270 --> 01:40:24,270 the show in March already get it booked. Oh, cool. Now wasn't 1556 01:40:24,420 --> 01:40:29,250 Gigi who said he he he retired at block 700,000 was was that 1557 01:40:29,280 --> 01:40:33,840 dirt cheap? Or was it because I liked that because we determined 1558 01:40:34,320 --> 01:40:37,320 yesterday you and I block what block height? 1 million. David. 1559 01:40:37,710 --> 01:40:41,610 retiring. Yeah, we're out that 1 million blockout. 1 million. 1560 01:40:41,610 --> 01:40:44,910 We're out. Yeah, I wanna I want to start using a nem I'm gonna 1561 01:40:44,910 --> 01:40:50,400 become a nem nem Yeah. And you know, the anonymous, you know, 1562 01:40:50,400 --> 01:40:52,230 like, GG, that's not his real name. He's 1563 01:40:53,310 --> 01:40:55,950 an anonymous, so block 1 million. I'm just gonna become 1564 01:40:55,950 --> 01:41:01,020 like a, like a nim. So it's like the witness protection program. 1565 01:41:01,650 --> 01:41:06,630 Yeah, okay. Yeah. I'm just gonna come back as DJ or something 1566 01:41:06,630 --> 01:41:10,800 like that. And nobody know who I am Dave Jones. Yeah, yeah. 1567 01:41:12,270 --> 01:41:14,850 Thank you there GG. We appreciate it. I guess it's just 1568 01:41:14,850 --> 01:41:15,210 GG 1569 01:41:17,340 --> 01:41:26,490 G Jo. Jo. I don't know. J LT a TX Gil tax gave us 1024 SATs 1570 01:41:26,520 --> 01:41:31,110 call that a kilobyte boost. Oh 1024 cents I like that. Yeah do 1571 01:41:31,110 --> 01:41:32,970 fountain any just as boost yo 1572 01:41:36,150 --> 01:41:41,610 that's Tina right yeah, it is. Yes. Our buddy Karen for the 1573 01:41:41,610 --> 01:41:45,120 mere mortals podcasts in a rush boost 2112 una fountain 1574 01:41:46,830 --> 01:41:50,700 aces fantastic episode gents. I can give two endorsements for 1575 01:41:50,700 --> 01:41:54,060 two Satoshis dot stream and for Oscars new inbuilt wallet for 1576 01:41:54,060 --> 01:41:57,360 booster grams yay with with Satoshis dot stream I received 1577 01:41:57,360 --> 01:42:00,750 the messages and telegram and on Discord plus a daily update and 1578 01:42:00,750 --> 01:42:04,020 for my book review channel I use fountain which is really slick. 1579 01:42:04,350 --> 01:42:08,790 Just just need to get working on my V four v podcast on Hello Pat 1580 01:42:08,790 --> 01:42:13,140 and I'll have all bases covered. Oh nice. Very nice. Thank you 1581 01:42:13,140 --> 01:42:21,660 for this that's Karen. Best. Bessie UK. V si UK send us best. 1582 01:42:21,900 --> 01:42:27,690 Se UK I think Bessie UK maybe. Okay. Send us 117 says through 1583 01:42:27,690 --> 01:42:30,690 fountain and he says my podcast buddy and I just turned down 1584 01:42:30,690 --> 01:42:34,260 multiple legacy advertising offers and made our podcast 2.0 1585 01:42:34,260 --> 01:42:38,550 compatible. Yeah. As one of the first non crypto oriented castes 1586 01:42:38,550 --> 01:42:42,480 in Germany as far as I can tell, I wish you all the best Daniel 1587 01:42:42,480 --> 01:42:46,650 from the Hildon LD. If you need a Deutsche boost 1588 01:42:47,850 --> 01:42:51,780 go podcasting God podcasting Dodger boost podcast. 1589 01:42:53,130 --> 01:42:56,100 You sound so German when you do. Well. I have. 1590 01:42:57,390 --> 01:42:59,460 I have I have that Aryan thing about me. 1591 01:43:00,960 --> 01:43:06,120 Donation donations. Okay. 3300 SATs from Cass PyLint Ooh 1592 01:43:06,120 --> 01:43:09,810 through fountain and he says thanks for the show. Thank you 1593 01:43:09,810 --> 01:43:12,360 cast cast peatland from the Netherlands. 1594 01:43:13,470 --> 01:43:17,100 cheese cheese peel and right cast cheese that would be it. 1595 01:43:18,630 --> 01:43:21,720 Sir Doug's and his 4400 SAS through fountain and he just 1596 01:43:21,720 --> 01:43:23,280 says boost Yay. 1597 01:43:25,080 --> 01:43:29,280 Thank you, sir. Doug. Oh, sir Doug again. 4400 SATs again. 1598 01:43:29,400 --> 01:43:34,470 Nice says I'm podcasting without consequences. Don't just post 1599 01:43:37,230 --> 01:43:44,070 route. ruse Ruiz Elgato sent us 5000 SATs through fountain and 1600 01:43:44,070 --> 01:43:46,920 he says this is an oddly satisfying way of parting with 1601 01:43:46,920 --> 01:43:50,550 money. You may have stumbled onto something. Yeah. See this 1602 01:43:50,550 --> 01:43:54,960 is I saw that one come in. Like yeah, that's beautiful. Because 1603 01:43:54,960 --> 01:43:58,980 that's what it is. It feels good man. It really feels good to be 1604 01:43:58,980 --> 01:44:02,280 listening to something and just sending little bits of money. 1605 01:44:02,310 --> 01:44:06,660 Like I value this. I agree. Feels good on both ends. Let's 1606 01:44:06,660 --> 01:44:09,630 get this fan said last week on the show. If from bus Brad he's 1607 01:44:09,630 --> 01:44:12,540 like, you know, I never realized I get a dopamine hit by sending 1608 01:44:12,810 --> 01:44:17,220 money. Yeah, exactly. It's podcasting. 2.0 It's better than 1609 01:44:17,220 --> 01:44:22,140 a meditation app. Nomad Joseph and his 1002 SAS through pod 1610 01:44:22,140 --> 01:44:24,960 friend and he says happy puppy whooshed 1611 01:44:29,370 --> 01:44:30,090 cauldron 1612 01:44:31,350 --> 01:44:37,200 says it's cool name Cole Johnson is 18,001 Set oh I know we he 1613 01:44:37,200 --> 01:44:39,480 she has donated plenty of times before 1614 01:44:41,070 --> 01:44:43,380 I had to boost again after hearing you read my booster 1615 01:44:43,380 --> 01:44:47,790 grant from Korean the keeper for anyone vanilla kinky or LGBT. 1616 01:44:48,120 --> 01:44:50,820 Interested in relationship and intimacy coaching visit 1617 01:44:51,090 --> 01:44:53,850 cauldrons crypt.com/coaching. 1618 01:44:54,900 --> 01:44:59,670 This is this is the first Native advertiser on podcasting. 2.0 1619 01:44:59,670 --> 01:45:00,000 who has made 1620 01:45:00,000 --> 01:45:05,280 making the rounds and is is sending you know like nice size 1621 01:45:05,280 --> 01:45:08,850 boosts to have their booster Graham read. Yep that's how you 1622 01:45:08,850 --> 01:45:09,180 do it 1623 01:45:10,410 --> 01:45:15,930 let's see let's go to flightless birds send us 200 sets and he 1624 01:45:15,930 --> 01:45:17,100 says you 1625 01:45:20,310 --> 01:45:24,810 I left it on again yesterday during no agenda can hear it on 1626 01:45:24,810 --> 01:45:28,410 the across the room my headphone doesn't quite the cord doesn't 1627 01:45:28,410 --> 01:45:32,520 quite reach to get to it to the volume and so I heard ago pew 1628 01:45:32,850 --> 01:45:36,090 and and what happens is on the live stream these fuckers are 1629 01:45:36,090 --> 01:45:38,880 sitting there and in the troll room like oh, he's got the booty 1630 01:45:38,880 --> 01:45:41,040 Graham you got the helipad on let's let's boost 1631 01:45:42,330 --> 01:45:46,410 like 50 SATs pew pew pew pew pew pew pew pew like very funny. 1632 01:45:46,830 --> 01:45:47,700 Very, very funny. 1633 01:45:49,170 --> 01:45:49,680 Like 1634 01:45:51,180 --> 01:45:58,650 see anonymous through breeze, send us 12345 So 12,354 45 sets 1635 01:45:59,910 --> 01:46:03,420 and they say Brees warned me that they may shut down my node 1636 01:46:03,420 --> 01:46:05,580 due to lack of activity. This is a forced boost 1637 01:46:07,200 --> 01:46:08,310 force boost. 1638 01:46:09,750 --> 01:46:12,060 This is very Star Wars Force boost test 1639 01:46:13,170 --> 01:46:18,630 stim our steamer steamer 42. Send us 4242 sets through 1640 01:46:18,630 --> 01:46:22,410 fountain and he says hey guys, please. Hey guys, please tell us 1641 01:46:22,650 --> 01:46:25,890 please tell Jason that podcasting with legacy apps is 1642 01:46:25,890 --> 01:46:30,000 like making movies for VHS. VHS when Netflix is available. Is 1643 01:46:30,000 --> 01:46:33,480 Jason. Is he talking about Jason Calacanis. 1644 01:46:35,130 --> 01:46:38,430 That's the only that's the only he's on podcasting tours is at 1645 01:46:38,430 --> 01:46:41,160 his podcast. Yeah. 2.0 compatible. I never hear him 1646 01:46:41,160 --> 01:46:44,190 talk about it. Maybe he's talking about Jason from podcast 1647 01:46:44,190 --> 01:46:46,710 guru but I don't remember what he would have said no, I don't 1648 01:46:46,710 --> 01:46:49,800 either. I got I've got a fix for this since 1649 01:46:53,100 --> 01:46:56,670 Dave, you really picked up this value for value very quickly. 1650 01:46:57,180 --> 01:47:02,640 It's not rocket science. It's it was a quick way at 3333 says 1651 01:47:02,640 --> 01:47:06,690 from signs of new growth through the fountain app. He says 1652 01:47:07,080 --> 01:47:09,600 appreciate all your nonstop hard work to make this new system a 1653 01:47:09,600 --> 01:47:13,320 reality and I will also add I'm this is me editorializing, the 1654 01:47:13,320 --> 01:47:19,410 nonstop hard work of also guys like Alex and Brian cast of 1655 01:47:19,410 --> 01:47:24,360 1000s and Spurlock and Steven crater, Steven Bell and 1656 01:47:24,450 --> 01:47:27,270 everybody that does work on this project and the hosting 1657 01:47:27,300 --> 01:47:31,020 companies Yes, yes and the hosting companies and the app 1658 01:47:31,020 --> 01:47:35,700 and the podcasters everybody yes want to make that clear 1659 01:47:35,940 --> 01:47:38,790 appreciate all your hard work to make this new system a reality 1660 01:47:39,030 --> 01:47:41,760 been having lots of fun producing songs publishing them 1661 01:47:41,970 --> 01:47:44,460 receiving histograms and interacting with all supportive 1662 01:47:44,460 --> 01:47:47,310 people at podcast index dot social I'm trying to figure out 1663 01:47:47,310 --> 01:47:50,370 how to contribute to a more music focused podcasting 2.0 1664 01:47:50,370 --> 01:47:53,760 experience able Kirby answer Spencer seem to be leading the 1665 01:47:53,760 --> 01:47:58,560 way with their various projects. Great. And I'll I'll I'll do my 1666 01:47:58,650 --> 01:48:02,160 my rant as usual. All it takes is one developer to create a 1667 01:48:02,160 --> 01:48:05,250 different front end just for music. That's all it takes. 1668 01:48:06,360 --> 01:48:08,550 That's all it takes. Everything else works. 1669 01:48:12,210 --> 01:48:16,170 That's right. Just Hey, man, you want to be a musician you. 1670 01:48:19,350 --> 01:48:22,380 Alright, another t shirt. I sent us your took the words out of my 1671 01:48:22,380 --> 01:48:25,740 mouth. Now I talked to I want to mention this to talk to the 1672 01:48:27,360 --> 01:48:30,480 no agenda shop guy. Turns out it's one guy and his wife, which 1673 01:48:30,480 --> 01:48:34,680 is just she slays me at the amount of work he does. Wow. And 1674 01:48:34,860 --> 01:48:37,290 so he's going to take care of the rest of our T shirts, which 1675 01:48:37,290 --> 01:48:39,630 you've heard he's actually designing a new short new shirt 1676 01:48:39,630 --> 01:48:40,170 for us. 1677 01:48:41,520 --> 01:48:45,630 For our 10 donors who we still owe shirts, apologies for that. 1678 01:48:46,140 --> 01:48:52,530 But he also wants to do a whole podcasting 2.0 section with a 1679 01:48:52,560 --> 01:48:56,340 you know, something podcasting 2.0 podcasts index related, so 1680 01:48:56,730 --> 01:49:00,960 to do merch and then he'll he'll give a portion of the proceeds 1681 01:49:00,990 --> 01:49:05,850 to the podcasting 2.0 project the index that's really need to 1682 01:49:05,850 --> 01:49:09,570 hit him up. He has to he has to take lightning and have a BTC 1683 01:49:09,570 --> 01:49:13,050 pay server on the front of that. It really it's time. 1684 01:49:14,820 --> 01:49:17,910 I'll talk to him about I mean, I thought he had his own company. 1685 01:49:18,570 --> 01:49:22,020 He literally has no inventory. He's just figured out how to do 1686 01:49:22,020 --> 01:49:25,440 it cost effectively. His wife helps him pack stuff up. It's an 1687 01:49:25,470 --> 01:49:30,120 I for years thought this was a company. He has a full time job. 1688 01:49:30,120 --> 01:49:34,140 He does something completely unrelated. I have to have two 1689 01:49:34,350 --> 01:49:37,470 shirts that he's produced so far. They're good shirts, yes, 1690 01:49:37,500 --> 01:49:40,560 great shirts, good quality, and he T shirts. I think what his 1691 01:49:40,560 --> 01:49:44,100 ultimate. He wanted to learn how to do an apparel line moving 1692 01:49:44,100 --> 01:49:48,000 forward. And so this was kind of his, his training ground. It 1693 01:49:48,000 --> 01:49:50,460 just became a thing and he's just like, No, I mean, he 1694 01:49:50,460 --> 01:49:51,480 doesn't live off of it. 1695 01:49:52,560 --> 01:49:55,350 But he certainly certainly makes a lot of people happy 1696 01:49:56,790 --> 01:49:59,940 Satoshis dot stream, send us 10,000 sets 1697 01:50:00,359 --> 01:50:00,899 Nice. 1698 01:50:02,730 --> 01:50:06,330 Benjamin is a nice guy and podcast font is cool. Thanks 1699 01:50:06,330 --> 01:50:11,490 again for the logo. Oh yeah. Very nice. Thanks. So she's 1700 01:50:11,490 --> 01:50:11,970 downstream. 1701 01:50:13,290 --> 01:50:19,140 See 30,000 SATs from Peter through the fountain app. And he 1702 01:50:19,140 --> 01:50:23,100 says podcasting 2.0 uncensor ability is directly responsible 1703 01:50:23,100 --> 01:50:26,790 for changing the trajectory of humanity for all eternity. So 1704 01:50:26,790 --> 01:50:31,020 happy to be part of the part of history boost boost boost. Nice. 1705 01:50:31,230 --> 01:50:35,640 Thank you for those 30,000 says Peter, appreciate that. And the 1706 01:50:35,640 --> 01:50:38,430 delimiter here it is ladies and gentlemen comics through blogger 1707 01:50:38,430 --> 01:50:44,160 with his weekly donation 10,033 SAS through pod friend, he says 1708 01:50:44,280 --> 01:50:47,850 greetings to podcast index.org. Team. Thank you for your service 1709 01:50:47,850 --> 01:50:50,640 to podcasting and you're invited to listen to our podcast 1710 01:50:50,640 --> 01:50:54,660 entitled AI cooking. Read by Englishman Gregory William 1711 01:50:54,660 --> 01:50:58,500 Forsythe Forman can be found in web browsers by typing AI 1712 01:50:58,530 --> 01:51:02,160 cooking or via new podcast apps calm yo, yo. 1713 01:51:03,420 --> 01:51:07,860 He's popping us FOD one came in from Sir Spencer. Did you see 1714 01:51:07,860 --> 01:51:11,400 that about an hour ago? No, that was probably after I already 1715 01:51:11,400 --> 01:51:13,320 dumped the list. Yeah, I just read this one since 1716 01:51:14,580 --> 01:51:22,950 33,333 SATs from Sir Spencer. Yeah. Hold on a second was Yeah. 1717 01:51:24,300 --> 01:51:27,210 Hope this reaches you in time well, due to the real time 1718 01:51:27,210 --> 01:51:31,170 nature of Heli pad. Yes. Looking forward to your visit with us 1719 01:51:31,170 --> 01:51:34,260 Sunday on bowls with bugs live on the no agenda stream after no 1720 01:51:34,260 --> 01:51:38,310 agenda wraps up set for you, Dave. It is on Sunday. Yep, 1721 01:51:38,370 --> 01:51:43,020 we'll be demonstrating our new boost IRC bot featuring custom 1722 01:51:43,200 --> 01:51:50,130 lists featuring custom numerology emojis. Oh, man, I 1723 01:51:50,130 --> 01:51:56,280 love this. That's that's that's fucking cool, man. Yeah, I can't 1724 01:51:56,280 --> 01:51:59,070 wait. I'm happy what and be distracted by the troll run the 1725 01:51:59,070 --> 01:52:02,040 entire time. Fantastic. Love it. 1726 01:52:03,480 --> 01:52:06,480 We get monthly donors. Yes. We get some 1727 01:52:07,590 --> 01:52:11,550 monthly donors. Here we got Jeremy Kevin all $10 Chris 1728 01:52:11,550 --> 01:52:15,330 Callen. $5 There's a guy I don't know if y'all know him. His name 1729 01:52:15,330 --> 01:52:20,700 is Alice gates heard of him. He gave us $25 Thank you, Alex. 1730 01:52:22,530 --> 01:52:26,970 He's popping. Jeffrey Rutherford. $5 naman Kessel 1731 01:52:26,970 --> 01:52:32,850 Jack, give us $15 Paul Saltzman $22.22 Derek Fisker. $21 David 1732 01:52:32,850 --> 01:52:34,740 Norman $25. 1733 01:52:37,290 --> 01:52:42,690 Jeremy Gertz $5 Timothy Hudgins $25. My buddy David would find 1734 01:52:42,690 --> 01:52:45,960 $3 and this is Dutch I'm going to try to do it I'm going to try 1735 01:52:45,960 --> 01:52:46,920 to do Dutch accent 1736 01:52:49,140 --> 01:52:55,500 which will close post vessel vessel throat TR o St. proced 1737 01:52:55,500 --> 01:53:02,310 Yeah, O P vessel proced p r o st P as in Papa, no t to t trust. 1738 01:53:02,850 --> 01:53:07,530 Trust So trust which means to trust is to comfort 1739 01:53:08,610 --> 01:53:11,130 Oh, this beautiful comforting remember that the Dutch when 1740 01:53:11,130 --> 01:53:14,610 Napoleon invaded they all changed their names and they got 1741 01:53:14,610 --> 01:53:16,920 drunk the night before and said hey, I'll just call my head 1742 01:53:16,920 --> 01:53:21,120 myself. Shit mountain. Okay. To beat you day to day there are 1743 01:53:21,120 --> 01:53:23,460 people whose last name is shit mountain. 1744 01:53:25,230 --> 01:53:26,850 I'm telling you man is crazy. 1745 01:53:27,930 --> 01:53:31,620 Oh, he comforted us with $1 Well, thank you very much. 1746 01:53:31,680 --> 01:53:33,960 typical Dutch Dutch guy. There you go. 1747 01:53:36,420 --> 01:53:41,580 Survey of ash gave us $5 and Thomas Sullivan Jr. $5. My 1748 01:53:41,580 --> 01:53:47,010 favorite name. And I want to say also give a shout out to Dr. 1749 01:53:47,010 --> 01:53:49,740 Scott and David Norman for their continuous chapter work they 1750 01:53:49,740 --> 01:53:53,910 don't get enough recognition for that. Indeed everybody in you 1751 01:53:53,910 --> 01:53:58,050 can bring your your value to the project with the three T's time 1752 01:53:58,050 --> 01:54:00,780 talent, treasure, we need to treasure for sure. But just look 1753 01:54:00,780 --> 01:54:04,200 at all the time and talent that we have here. It's it's always 1754 01:54:04,230 --> 01:54:08,430 mind boggling. I would pay I would well, we kind of do but I 1755 01:54:08,430 --> 01:54:12,300 would pay to be to be a part of this group. I think we do. I 1756 01:54:12,300 --> 01:54:15,690 think I think we lose out Dave I think we boost more than than 1757 01:54:15,690 --> 01:54:19,740 we'll ever see. Yes, I've had to cut back I've had to make a 1758 01:54:19,740 --> 01:54:22,230 conscious effort to cut back I knew you were on a collision 1759 01:54:22,230 --> 01:54:25,350 course I knew you were boost you were over boosting and I and I 1760 01:54:25,350 --> 01:54:28,500 quit I thought it was almost time for an intervention Okay, 1761 01:54:28,530 --> 01:54:31,350 cuz I saw it I'm like Dave's boosting a little too much man. 1762 01:54:31,350 --> 01:54:34,080 He's gonna boost my wife knew if she she knew it was time for an 1763 01:54:34,080 --> 01:54:37,410 intervention if she actually intervened. Hey, slow down with 1764 01:54:37,410 --> 01:54:42,600 the boosting bra. Yeah, yeah, one, one pull request from Alice 1765 01:54:42,600 --> 01:54:45,990 gates represents 1000s of dollars worth of development, 1766 01:54:46,170 --> 01:54:49,830 professional development. Work is right. Oh, speaking of 1767 01:54:49,830 --> 01:54:53,790 selling. So you can obviously you can you can support the 1768 01:54:53,790 --> 01:54:58,320 whole project and liquidity and help everybody out by boosting 1769 01:54:58,320 --> 01:54:59,640 us that's highly appreciated. 1770 01:55:00,000 --> 01:55:04,050 The paper towels, the Fiat fun coupons still very necessary for 1771 01:55:04,050 --> 01:55:08,100 us to continue operations. We have a donate button at podcast 1772 01:55:08,100 --> 01:55:13,650 index.org at the bottom, I hooked up the tally coin 1773 01:55:15,000 --> 01:55:18,960 QR code for payments. And someone said, Oh yeah, no, I'll 1774 01:55:18,960 --> 01:55:21,600 put in a pull request and I don't think it's happened yet. 1775 01:55:21,750 --> 01:55:25,980 Just Steven crater he's he'll he'll he'll get to us. Yeah, now 1776 01:55:25,980 --> 01:55:30,180 he re that's another person that is she redid the whole a whole 1777 01:55:30,180 --> 01:55:35,940 lot of stuff. Right? It makes us so no. Well, Steven B redid the 1778 01:55:35,940 --> 01:55:40,530 ads page. But then Stephen crater came in and 1779 01:55:41,640 --> 01:55:45,570 took care of a lot of nagging issues on the site like infinity 1780 01:55:45,570 --> 01:55:49,980 scroll, he put that in on the feed low, nice. And did some 1781 01:55:49,980 --> 01:55:53,670 search work also took care of the URL encoding for the search 1782 01:55:53,670 --> 01:55:56,310 so you can find curry and the keeper and those kinds of 1783 01:55:56,310 --> 01:56:01,350 things. Although I changed the the RSS feed to be curry a n d 1784 01:56:01,350 --> 01:56:06,000 th e keeper. Yes, yeah, yeah. But he he did. He's done. He's 1785 01:56:06,000 --> 01:56:08,100 done a bunch of them. And he also is the maintainer of the 1786 01:56:08,100 --> 01:56:12,450 hive watcher, JavaScript, cetera, et pod ping dot watcher 1787 01:56:12,690 --> 01:56:16,710 watch. While he does that side, but he also maintains the 1788 01:56:16,710 --> 01:56:20,340 JavaScript version of the hive watcher. Gotcha. Gotcha. I use 1789 01:56:20,340 --> 01:56:21,990 pod ping Dot Watch all the time. 1790 01:56:23,760 --> 01:56:27,390 On that note, quick aside, he was actually the first support 1791 01:56:27,420 --> 01:56:31,320 live and popping the watch. So Oh, that's right. It comes in a 1792 01:56:31,320 --> 01:56:35,520 different color, right? Yes, it comes in red. Oh, cool. So you 1793 01:56:35,520 --> 01:56:38,910 can use that to test until we can get it into another app? So 1794 01:56:38,940 --> 01:56:44,340 here's a question just briefly for y'all pod pingers sometimes, 1795 01:56:44,460 --> 01:56:47,640 and I just look at pod Pink Dot Watch. And they'll say podcast 1796 01:56:47,640 --> 01:56:52,800 index. And it'll have a you know, slash podcast slash and 1797 01:56:52,830 --> 01:56:57,720 then a thing. But here's one podcast index and it gives a 1798 01:56:57,720 --> 01:57:01,500 search query to a Buzzsprout RSS feed. 1799 01:57:03,330 --> 01:57:04,470 Wind does not found 1800 01:57:05,640 --> 01:57:10,440 in podcasts and Oh, so it's not found Okay, right. That means 1801 01:57:10,440 --> 01:57:10,530 that 1802 01:57:11,790 --> 01:57:13,770 it will let me tell you the reason why puts the search query 1803 01:57:13,770 --> 01:57:16,500 in there because when you hit it with a search query for a URL, 1804 01:57:16,830 --> 01:57:19,920 and the URL is not found, it gives you the option on the page 1805 01:57:19,920 --> 01:57:22,200 to add the feed to the index. 1806 01:57:23,790 --> 01:57:27,300 So that surfaces the add the public add functionality where 1807 01:57:27,300 --> 01:57:29,070 you can click to add it if you wanted to 1808 01:57:30,360 --> 01:57:34,230 pass it that feed is not exist in the index, but if you click 1809 01:57:34,230 --> 01:57:38,910 through it, you can add Holy shit. Yeah, add this to the 1810 01:57:38,910 --> 01:57:42,780 index. Click here. Click here. Oh, that is also something that 1811 01:57:42,840 --> 01:57:47,640 this Steven did this a recruiter put Oh my goodness. So I could 1812 01:57:47,640 --> 01:57:51,990 actually I can help like, oh, wait, wait, wait, wait. 1813 01:57:53,010 --> 01:57:58,380 Train train isn't popping gonna rain 1814 01:57:59,550 --> 01:58:02,700 is already doing it train that train, train. 1815 01:58:04,350 --> 01:58:07,740 Training. I'm training the Google it's I have to prove on 1816 01:58:07,740 --> 01:58:08,430 cumin which 1817 01:58:09,780 --> 01:58:12,000 I thought you were a foamer I didn't know it was? Well, no, I 1818 01:58:12,000 --> 01:58:16,620 had to click trains. They they were buses and trains. So I was 1819 01:58:16,620 --> 01:58:23,670 clicking trains train train. I'm a good slays okay, I hate that. 1820 01:58:23,700 --> 01:58:25,920 I hit that and I get a blank page after that. 1821 01:58:27,480 --> 01:58:29,580 But it's being done automatically. Anyway, on the 1822 01:58:29,580 --> 01:58:32,820 back end. Bye. Bye. Okay, podcast index. I thought I could 1823 01:58:32,820 --> 01:58:35,850 find it'll be there. I thought it could help. It's a good 1824 01:58:35,850 --> 01:58:36,270 hobby. 1825 01:58:41,400 --> 01:58:43,410 Google self driving cars need all the help. 1826 01:58:45,600 --> 01:58:47,430 Look, we don't want people to die out there. So 1827 01:58:49,290 --> 01:58:53,220 that's interesting. That's very interesting. Thanks, everybody. 1828 01:58:53,820 --> 01:58:57,210 That's a better week. Thank you. That really makes a difference. 1829 01:58:57,210 --> 01:58:59,220 And when you're boosting just consider what you're boosting. 1830 01:58:59,820 --> 01:59:03,600 And we need as much as we can get the but I mean, even curry 1831 01:59:03,600 --> 01:59:07,350 and the keeper and Mo facts, man. Holy crap. People are 1832 01:59:07,350 --> 01:59:10,200 really starting to move money through the booster grams. It's 1833 01:59:10,200 --> 01:59:13,170 picking up. Yeah, it's picking up really? Is it really the 1834 01:59:13,170 --> 01:59:14,430 same? It's great. 1835 01:59:15,960 --> 01:59:19,230 All right. Anything else? What do we get? Oh, my goodness, this 1836 01:59:19,230 --> 01:59:22,560 board meeting is out of control. Anybody on PayPal right now? 1837 01:59:22,590 --> 01:59:26,400 Yes, we are anybody else? For the for the closing. Closing 1838 01:59:26,400 --> 01:59:30,750 questions, closing arguments. I've won. Thank you. Thank you 1839 01:59:30,750 --> 01:59:34,020 for everything. Oh, Brian, thank you. That's my contribution. 1840 01:59:34,020 --> 01:59:36,750 Really, really, honestly, from the bottom of my heart, 1841 01:59:37,020 --> 01:59:40,530 everything, everything that you've done, it just given me a 1842 01:59:40,530 --> 01:59:43,260 huge amount of joy and, and purpose. 1843 01:59:44,400 --> 01:59:47,310 Wow, that's very nice thing that's very nice of you to say, 1844 01:59:48,600 --> 01:59:50,580 Hey, Alex, this is my purpose. So 1845 01:59:51,630 --> 01:59:55,200 that's all I got. So one more thing I'm trying to work on was 1846 01:59:55,230 --> 01:59:59,700 popping in the medium tag is a and maybe a new knit namespace 1847 01:59:59,700 --> 01:59:59,970 feature. 1848 02:00:00,000 --> 02:00:06,000 is a way to do playlists for anything. So podcasts or music 1849 02:00:06,000 --> 02:00:06,600 or whatever. 1850 02:00:08,010 --> 02:00:08,820 Just something to 1851 02:00:10,290 --> 02:00:13,200 think about that for discussion soon. I think I think we could 1852 02:00:13,200 --> 02:00:15,120 do it without, you know, any copyright issues. 1853 02:00:16,350 --> 02:00:20,760 And that could be a whole new, whole new use case. So just how 1854 02:00:20,760 --> 02:00:22,380 do you do that? You do that with what? 1855 02:00:23,940 --> 02:00:28,380 Think about adding a new namespace proposal? Item. So you 1856 02:00:28,380 --> 02:00:30,960 can have a feed that's not that doesn't have any items that 1857 02:00:30,960 --> 02:00:36,990 would be that would be a playlist RSS. Yep. Yep. Nice. 1858 02:00:37,080 --> 02:00:42,600 Oh, ooh. And then can we do inclusion of other playlists? 1859 02:00:44,460 --> 02:00:46,530 Maybe think about right. 1860 02:00:48,540 --> 02:00:51,300 I was like, could be, that's a big part about Spotify, right? 1861 02:00:51,300 --> 02:00:56,850 Is curated playlists. So now, can we finally can we can we 1862 02:00:56,850 --> 02:00:58,800 find like, Why did you laugh at that, Brian? 1863 02:00:59,940 --> 02:01:03,510 Because I love the idea every time we come up with a feature, 1864 02:01:03,720 --> 02:01:07,560 but that is like a core product of web 2.00. 1865 02:01:08,910 --> 02:01:13,440 Distribute it for free. And they're multi billion dollar 1866 02:01:13,440 --> 02:01:17,280 history. You can't do anything to stop it. That's funny. Okay. 1867 02:01:17,730 --> 02:01:22,020 Is this a way Alex to finally bring OPML back into our lives? 1868 02:01:22,020 --> 02:01:25,890 Because I I really feel like it's slipping through my 1869 02:01:25,890 --> 02:01:28,590 fingers. I do love the format so much. 1870 02:01:29,730 --> 02:01:34,140 I don't think so. Maybe? I don't know much about it. But I feel 1871 02:01:34,140 --> 02:01:37,680 like it's just a regular trade. Right. I mean, I just I still 1872 02:01:37,740 --> 02:01:42,360 yearn for import export, have OPML subscription lists, and 1873 02:01:42,390 --> 02:01:48,090 very few support it. It's just too bad. I think. I think that I 1874 02:01:48,090 --> 02:01:52,680 may be the only human in the history of the world that has 1875 02:01:52,680 --> 02:01:54,720 written a namespace for OPML. 1876 02:01:57,540 --> 02:02:00,450 That may be true. We don't need to think about it. Dave is 1877 02:02:00,450 --> 02:02:01,080 definitely 1878 02:02:02,220 --> 02:02:05,040 about it. still proud of it. I'm still proud of it. All right, 1879 02:02:05,040 --> 02:02:10,110 everybody. Good meeting guys. Very good. And I can distill 1880 02:02:10,110 --> 02:02:10,830 some pizza. Let's 1881 02:02:11,970 --> 02:02:14,430 go ahead and have that on your way out. Take a little take a 1882 02:02:14,430 --> 02:02:18,030 little slice. Thank y'all for board meeting us pod Ting. We'll 1883 02:02:18,030 --> 02:02:19,650 see you next week everybody bye bye. 1884 02:02:35,790 --> 02:02:41,130 Listening to podcasting 2.0 Visit podcasts index.org. For 1885 02:02:41,130 --> 02:02:42,330 more information