Episode 116: Cryptotarians

1 00:00:00,630 --> 00:00:06,450 podcasting to one over January 6 2023, episode 116 We're Krypto 2 00:00:06,450 --> 00:00:12,480 terian Hello, everybody first board meeting of the new year 3 00:00:12,480 --> 00:00:16,980 2023 Are we already in the three years this thing almost Welcome 4 00:00:16,980 --> 00:00:19,830 to podcasting 2.0 It is your weekly board meeting where we 5 00:00:19,830 --> 00:00:23,700 discuss all things around the new podcast standards, the 6 00:00:23,700 --> 00:00:26,820 namespace, everything happening at podcast index dot social, and 7 00:00:26,820 --> 00:00:30,330 we've got some great guests here with us in the board room. I'm 8 00:00:30,330 --> 00:00:32,580 Adam curry here in the heart of the Texas Hill Country on 9 00:00:32,580 --> 00:00:36,330 Alabama. The man always prepared to pull your request. Say hello 10 00:00:36,330 --> 00:00:39,030 to my friend on the other end. Ladies and gentlemen, Mr. Dave 11 00:00:39,030 --> 00:00:39,960 Jones. 12 00:00:42,750 --> 00:00:46,080 Did you know that I got a deep cut for you here? 13 00:00:46,589 --> 00:00:51,419 A deep Wait, you have a deep cut for me? Yeah, like a lady like a 14 00:00:51,419 --> 00:00:53,399 deep cut is in a deep cut on a record. 15 00:00:54,270 --> 00:00:57,000 Yeah, but this is a fact. This is like a deep cut fact. 16 00:00:57,030 --> 00:00:59,100 Okay. All right. I'm excited already. 17 00:00:59,549 --> 00:01:02,459 Well, I was trying to figure out Oscar ping me this morning and 18 00:01:02,459 --> 00:01:05,999 said that we're getting four threes on the API. And so 19 00:01:06,809 --> 00:01:12,779 for those of you just tuning in, Oscar, Oscar Mary runs the 20 00:01:12,779 --> 00:01:16,019 fountain app. And what did he get on 21 00:01:16,020 --> 00:01:19,020 the API? Some four Oh, threes? 22 00:01:19,499 --> 00:01:24,389 What is a 403? It is an error of some sort. Obviously. 23 00:01:24,720 --> 00:01:28,830 Era. Yeah. So it's it's like, I think is a service unavailable. 24 00:01:29,970 --> 00:01:33,660 It's a 403. I was getting mixed up with a four Oh, yeah. 25 00:01:33,660 --> 00:01:36,990 Forbidden. My bad. So 403 forbidden, which is weird. I'm 26 00:01:36,990 --> 00:01:40,500 like, okay, that's, that's authentication related. I don't 27 00:01:40,500 --> 00:01:42,150 really get and when it gets through Cloudflare you're not 28 00:01:42,150 --> 00:01:48,120 exactly sure. Sometimes either, because it can get wonky. But so 29 00:01:48,120 --> 00:01:52,770 I'm trying to figure that out. And of course, because I'm 30 00:01:52,770 --> 00:01:59,040 listening to my playlist, my Spotify playlist for whenever 31 00:01:59,040 --> 00:02:02,580 I'm doing API stuff, because it's important. It gets me in 32 00:02:02,580 --> 00:02:03,060 the mood. 33 00:02:03,540 --> 00:02:06,330 Oh, wait a minute. I actually have a little peek inside your 34 00:02:06,330 --> 00:02:09,060 Spotify post. This is something you posted just today. 35 00:02:09,810 --> 00:02:15,720 Yeah, a little bit of numbers Jones for everybody. Yeah. In 36 00:02:15,720 --> 00:02:19,830 honor of the Indian Tom Jones Samsung logo. can 37 00:02:22,950 --> 00:02:26,340 help yourself is the title. We know why you posted that. But 38 00:02:26,340 --> 00:02:28,440 okay, let's, let's keep on going. 39 00:02:28,890 --> 00:02:33,330 Well, so unlike this, I'm trying to figure this out. And then 40 00:02:33,540 --> 00:02:38,730 what hits what hits the playlist is sailing, but Christopher 41 00:02:38,730 --> 00:02:39,300 cross. 42 00:02:39,360 --> 00:02:40,830 Oh, yeah. Take me away. 43 00:02:40,890 --> 00:02:46,080 Yes. See me? Yeah. And I'm like, Okay. I don't actually know who 44 00:02:46,080 --> 00:02:50,340 Christopher cross is. I thought he was a one hit wonder. I'm 45 00:02:50,340 --> 00:02:50,820 like, Oh, we 46 00:02:50,820 --> 00:02:52,620 got a couple songs. I think 47 00:02:52,950 --> 00:02:56,100 didn't Yeah, turn. Turns out he had a he had a couple of big 48 00:02:56,100 --> 00:02:58,860 ones. That's about it. I mean, like, evidently the guy he's 49 00:02:58,860 --> 00:03:00,330 from San Antonio. San Antonio. 50 00:03:00,360 --> 00:03:02,880 I didn't know it was from San Antonio. How about yesterday, 51 00:03:02,880 --> 00:03:06,210 Senator. Let me see he had say Arthur's theme that was the big 52 00:03:06,210 --> 00:03:09,720 one from from the movie Arthur and then oh, ride like the wind. 53 00:03:09,750 --> 00:03:13,560 Wait, that's did he do it? Yes. He did. Do what right. Yeah. 54 00:03:13,560 --> 00:03:15,300 Okay, so yeah, it's like three hits. 55 00:03:15,690 --> 00:03:19,350 Yeah, three hits and then going so but then but I believe you 56 00:03:19,350 --> 00:03:19,800 gotta move 57 00:03:19,800 --> 00:03:24,600 you hit. You're gone in comfort. For the rest of your life be 58 00:03:24,600 --> 00:03:25,560 okay. Yeah. 59 00:03:26,370 --> 00:03:29,640 But then I kept I kept reading on the on the book of knowledge 60 00:03:29,640 --> 00:03:33,960 and I'm like, okay. It says that he is such a good guitar player 61 00:03:34,290 --> 00:03:37,470 that he filled in for Ritchie Blackmore in a night in a deep 62 00:03:37,470 --> 00:03:42,270 purple concert in 1970 when Blackmore was sick. Now that's a 63 00:03:42,270 --> 00:03:42,990 deep cut 64 00:03:43,920 --> 00:03:49,710 is a deep, I always liked him. I thought he also did some other 65 00:03:49,710 --> 00:03:53,310 projects he was involved in. But I remember it was the album with 66 00:03:53,310 --> 00:03:56,280 the I'm looking at it right now. This is the Yeah, the album of 67 00:03:56,280 --> 00:04:00,750 the familiar Flamingo on it. Oh, yeah, that was the one we all 68 00:04:00,750 --> 00:04:02,850 had that. 119 79 69 00:04:03,510 --> 00:04:08,040 Yeah, this and I'm like, I mean, he looks like a normal guy. He 70 00:04:08,040 --> 00:04:10,410 just looks like yeah, you know, average Joe. Like you would see 71 00:04:10,410 --> 00:04:12,480 him at, you know, at the Walgreens. 72 00:04:12,480 --> 00:04:16,680 Yeah. He looks kind of like a homely average guy. A little bit 73 00:04:16,680 --> 00:04:23,310 sad. Just a dad. Well, three and a half million monthly 74 00:04:23,310 --> 00:04:24,810 listeners. According to Spotify. 75 00:04:25,290 --> 00:04:28,350 No. Well, um, yeah. Well, he's getting about 20 bucks. That's 76 00:04:28,350 --> 00:04:28,530 good. 77 00:04:28,560 --> 00:04:34,050 Yeah. If that if that. Well, thank you. Yes, yes. 78 00:04:34,080 --> 00:04:38,100 Yeah, we're right. We're back. We're back in business. I just 79 00:04:38,190 --> 00:04:43,470 have no idea. I think what happened was the I'm battling 80 00:04:43,470 --> 00:04:46,230 this in this is probably this is probably something that we 81 00:04:46,230 --> 00:04:48,900 should talk about. At some point. I'm, I'm battling this 82 00:04:49,410 --> 00:04:55,020 batch of signups to the API and it's just like, it's accelerated 83 00:04:55,020 --> 00:04:56,880 and I know a lot of them are just 84 00:04:57,150 --> 00:05:00,180 garbage scammers and Trump people just find this Got a 85 00:05:00,180 --> 00:05:01,410 scrape stuff from us. 86 00:05:02,220 --> 00:05:05,010 I don't exactly know what they're doing. Because most of 87 00:05:05,010 --> 00:05:08,100 the there's just tons and tons of signups. And nobody. And most 88 00:05:08,100 --> 00:05:13,140 of these don't actually do any anything in the API. So I'm just 89 00:05:13,140 --> 00:05:16,530 gonna have to like, and then there's also people that are 90 00:05:17,100 --> 00:05:22,020 hitting us with sample code, channel, the CSS, all you know, 91 00:05:22,020 --> 00:05:27,480 we have the example. Org, in GitHub that's got all the 92 00:05:27,480 --> 00:05:31,290 example code for every language known to man know, on how to hit 93 00:05:31,290 --> 00:05:34,680 the API, it will a lot of people are doing is just taking that 94 00:05:34,680 --> 00:05:38,760 code and just hit and just like, dropping, running, running 95 00:05:38,760 --> 00:05:43,290 going. Well, so we end up with tons of hits with with a user 96 00:05:43,290 --> 00:05:45,750 agent string. That's just right out of the sample code. 97 00:05:45,810 --> 00:05:49,140 Well, I think something else is going on here. This is clearly 98 00:05:49,170 --> 00:05:53,610 open AI chat GPT, which is, is searching through all of the kid 99 00:05:53,610 --> 00:05:57,330 hubs, sucking in the code running the code, probably even 100 00:05:57,330 --> 00:06:01,050 signing up. And I think it's probably even asking for you to 101 00:06:01,050 --> 00:06:03,780 take down some some podcast it doesn't like I'm telling you, 102 00:06:03,780 --> 00:06:06,330 Ma'am, this thing is out of control. The AI is taken over. 103 00:06:07,200 --> 00:06:07,680 Did you 104 00:06:07,680 --> 00:06:11,850 read that? What do you think that's real? What that email? Is 105 00:06:11,850 --> 00:06:13,290 that real up real person 106 00:06:13,320 --> 00:06:18,060 folders that are the email that we got? Yeah. I'm, I haven't hit 107 00:06:18,060 --> 00:06:24,180 Send yet. On the reply. I am 99% certain that it will bounce. 108 00:06:25,110 --> 00:06:25,470 Okay. 109 00:06:25,560 --> 00:06:29,670 I mean, there's no way there's no website associated with this. 110 00:06:29,880 --> 00:06:35,820 No, no, there's no website. It's a GoDaddy protected domain. So 111 00:06:35,820 --> 00:06:39,870 you can't find out who's registered it. Yeah. Sketchy, 112 00:06:39,870 --> 00:06:43,380 sketchy. I have I have my email already. I'm just going to 113 00:06:43,380 --> 00:06:47,400 double check it. Someone wanted to Fox News taken down from it's 114 00:06:47,400 --> 00:06:52,170 interesting to send it to us because it was sent to the URL 115 00:06:52,200 --> 00:06:53,730 refers to his pod friend. 116 00:06:54,660 --> 00:06:58,350 Yeah. And, um, and I'm sure as, as he appropriately should, I'm 117 00:06:58,350 --> 00:07:00,810 sure Martin got first email and he was like, nope. 118 00:07:02,430 --> 00:07:04,620 Guaranteed he didn't get an email. I'm telling you. He 119 00:07:04,620 --> 00:07:07,800 didn't. Okay. It'll be fun. It'll be fun to watch. I don't 120 00:07:07,800 --> 00:07:11,970 mind doing that. But the AI stuff is out of control. I have 121 00:07:11,970 --> 00:07:14,010 to say, it's out of control. 122 00:07:15,570 --> 00:07:18,960 I got tired of hearing people read a Chad GPT stories, 123 00:07:20,160 --> 00:07:24,690 telling me you tell. But here's the AI story from this morning. 124 00:07:25,260 --> 00:07:29,340 that I thought was interesting that Apple has quietly released 125 00:07:29,370 --> 00:07:36,120 AI narrated audio books. So and which is interesting to me, 126 00:07:36,120 --> 00:07:40,470 because you know, I make I make a living speaking so if this is 127 00:07:40,470 --> 00:07:46,620 what my competitor is going to be. And I Chad was Chad F was 128 00:07:46,620 --> 00:07:50,430 kind enough to send me a little sample, which I will share in 129 00:07:50,430 --> 00:07:53,160 the same way I did with my wife this morning. I didn't say 130 00:07:53,160 --> 00:07:56,940 anything. I just played it and waited for her to respond. I 131 00:07:56,940 --> 00:07:59,640 would didn't say listen to this. I just played I just played it. 132 00:08:00,270 --> 00:08:02,550 And here we go. And listen, listen and listen to this, I 133 00:08:02,550 --> 00:08:03,030 should say here 134 00:08:03,030 --> 00:08:05,850 we are trying to relay information that is not always 135 00:08:05,850 --> 00:08:08,820 identifiable by current analytical processes is 136 00:08:08,820 --> 00:08:12,930 sometimes haphazard. But through real life stories and examples 137 00:08:12,960 --> 00:08:15,720 that illustrate how others can achieve the same results 138 00:08:15,750 --> 00:08:20,010 at this point. She said, Why are you listening to a robot? She 139 00:08:20,010 --> 00:08:23,430 heard it right away? Oh, yeah, without me setting her up, which 140 00:08:23,430 --> 00:08:24,480 I thought was interesting. 141 00:08:25,770 --> 00:08:30,300 It's, it's in the this is on the upswing of the uncanny valley. 142 00:08:30,660 --> 00:08:36,750 It's just, it's just, which is almost the worst place to be 143 00:08:36,870 --> 00:08:40,020 like, you want to be you want to be on the ball, you want to be 144 00:08:40,020 --> 00:08:43,350 like on the on the beginning of the upside of the uncanny 145 00:08:43,350 --> 00:08:47,340 valley, not at the not halfway, because then it's like, then is 146 00:08:47,340 --> 00:08:51,990 really irritating and triggering you. Because you can hear it 147 00:08:51,990 --> 00:08:54,210 every now and then. And you're not you're constantly 148 00:08:54,210 --> 00:08:58,200 questioning whether or not what you're hearing is actually is 149 00:08:58,200 --> 00:09:00,990 actually right or wrong. It's like it's like you're 150 00:09:00,990 --> 00:09:02,190 gaslighting yourself. 151 00:09:03,210 --> 00:09:07,680 To me. I immediately just sound soulless. That's what I do every 152 00:09:07,680 --> 00:09:11,250 single time I see an AI generated anything, including 153 00:09:11,250 --> 00:09:16,650 chat GPT if soulless chat GPT is word salad soulless tank, let me 154 00:09:16,650 --> 00:09:22,380 write 50 words to say I can't help you is a bit much that 155 00:09:22,380 --> 00:09:28,590 much. But I did run some code. I write a best I say yeah, I said 156 00:09:28,590 --> 00:09:32,250 write a bash script that lets me check the bitcoin price. And it 157 00:09:32,250 --> 00:09:38,040 wrote a script. And I copy pasted it. Made executable and 158 00:09:38,040 --> 00:09:40,230 it worked. Quite impressive. 159 00:09:41,130 --> 00:09:44,130 It worked well for a while. I mean, what did it actually do 160 00:09:44,130 --> 00:09:44,490 though? 161 00:09:45,030 --> 00:09:48,990 Oh, no. It's like if I type in BTC price and run it then it 162 00:09:48,990 --> 00:09:51,690 comes back and it says you know do it right now. So 163 00:09:51,870 --> 00:09:54,870 what is it like what does the code do? What what what service? 164 00:09:54,870 --> 00:09:56,460 Is it query? Oh, 165 00:09:56,790 --> 00:10:04,680 allow me to tell you. Oh, second. Here we go BTC okay, 166 00:10:05,700 --> 00:10:11,460 what it does it? Okay Does it curl on the coin desk API? 167 00:10:11,760 --> 00:10:17,040 Releases Go routines retrieves the JSON then it uses JQ. 168 00:10:18,240 --> 00:10:18,600 Yeah, 169 00:10:19,650 --> 00:10:23,460 install what is JQ is a JSON Query, I guess JSON, JSON, 170 00:10:23,670 --> 00:10:27,930 JSON decoder for the composer parser. Okay. And then 171 00:10:27,930 --> 00:10:32,430 it, you know, it literally parses for dot BPI dot USD rate. 172 00:10:32,430 --> 00:10:35,280 And then it says echo the current price of Bitcoin is it 173 00:10:35,280 --> 00:10:39,150 even even told me how to install JQ? If it wasn't installed on my 174 00:10:39,150 --> 00:10:42,180 system? That was kind of cool. 175 00:10:42,900 --> 00:10:46,440 So the logical next question is, whose code did it steal? 176 00:10:46,470 --> 00:10:50,940 Oh, of course, it stole someone's code. Of course, what 177 00:10:50,940 --> 00:10:54,480 I discovered yesterday during no agenda, you know, I've been 178 00:10:54,480 --> 00:11:00,120 using Niva and e va as a search engine for oh, goodness, ever 179 00:11:00,120 --> 00:11:04,740 since they came out maybe two years? Using that? Oh, yeah. And 180 00:11:04,740 --> 00:11:09,060 I pay for it. And that's fine. And so I'm searching something. 181 00:11:09,660 --> 00:11:13,200 And all of a sudden, I see on the search results, Neva AI, and 182 00:11:13,200 --> 00:11:17,910 it's literally just like, chat GPT is, is rolling out. You 183 00:11:17,910 --> 00:11:20,580 know, it's typing in real time. But it's also showing you the 184 00:11:20,580 --> 00:11:23,940 sources where it got this information from. And these are 185 00:11:23,940 --> 00:11:27,150 ex Google guys. So what happened is you got this big 186 00:11:27,150 --> 00:11:29,790 organization, Google, who, of course, freaking out over this 187 00:11:29,790 --> 00:11:33,510 stuff, because it's much better as a user friendly way to get an 188 00:11:33,510 --> 00:11:37,230 answer. I'm not saying the answer is correct. But it you 189 00:11:37,230 --> 00:11:40,560 know, to get an answer, and a company like that, it's very 190 00:11:40,560 --> 00:11:43,710 difficult to move in any especially search. I mean, 191 00:11:43,710 --> 00:11:46,500 that's you don't fuck with search a Google man. You don't 192 00:11:46,500 --> 00:11:50,190 touch anything without the board knowing about it, I guess. And 193 00:11:50,190 --> 00:11:52,290 these next Google guys, they went, Oh, yeah, hold my beer. 194 00:11:52,290 --> 00:11:55,950 We'll implement that. No one knows about it. They'll get no 195 00:11:55,950 --> 00:11:58,980 ink. But I was impressed. They did it. I thought that was 196 00:11:58,980 --> 00:11:59,760 pretty interesting. 197 00:12:00,240 --> 00:12:02,760 Well, I think I think he made a good point. At some point in the 198 00:12:02,760 --> 00:12:07,020 past. I can't remember. I can't remember when you said this. I 199 00:12:07,020 --> 00:12:11,220 think it was basically the it's the it's the the sort of 200 00:12:11,220 --> 00:12:16,470 definitiveness of what Chad GPT says. That is that is sort of 201 00:12:16,470 --> 00:12:19,140 like the secret sauce that scares everybody in the search, 202 00:12:19,170 --> 00:12:23,610 right? They don't give you a list of links, list of search 203 00:12:23,610 --> 00:12:26,550 results. Exactly what you say. What's the best barbecue 204 00:12:26,550 --> 00:12:29,670 restaurant in Austin, Texas, and it says it's this one, right? 205 00:12:30,210 --> 00:12:33,930 Like, Oh, yeah. Oh, okay. But if you don't like that, when you 206 00:12:33,930 --> 00:12:36,720 could try these other ones, it's just the way that it's worded. 207 00:12:36,750 --> 00:12:40,800 You're like, Oh, let that's actually kinda and that's Yeah, 208 00:12:40,830 --> 00:12:43,830 exactly. You know it because if from a search engine standpoint, 209 00:12:43,830 --> 00:12:47,400 like that, is that is intoxicating to, to, to most 210 00:12:47,400 --> 00:12:49,890 people is that they just get an answer. They don't have to 211 00:12:49,890 --> 00:12:51,060 actually parse anything. 212 00:12:51,060 --> 00:12:54,240 Exactly. No, people like that. This is exactly what lazy people 213 00:12:54,240 --> 00:12:58,050 love. This is going to be great for people. It's fantastic. It 214 00:12:58,050 --> 00:13:03,210 will ruin society. It will, it will remove all soul from all 215 00:13:03,210 --> 00:13:09,240 art, but man will be happy doing it. For sure. Big day. Today is 216 00:13:09,240 --> 00:13:13,710 the first board meeting of the new year. We have not one but we 217 00:13:13,710 --> 00:13:17,430 have two esteemed and honorable board members who have been, 218 00:13:17,640 --> 00:13:19,920 even though I've had their microphones open. They're very, 219 00:13:19,920 --> 00:13:22,560 very quiet. That's there. We have trained them so well. 220 00:13:22,860 --> 00:13:27,060 Please welcome right away to the board meeting at the honorable 221 00:13:27,090 --> 00:13:30,300 Alex gates official podcasting 2.0 consultant and the honorable 222 00:13:30,300 --> 00:13:33,300 Mitch Downey, founder and developer. Converse. Hello, 223 00:13:33,300 --> 00:13:33,840 gentlemen. 224 00:13:34,740 --> 00:13:36,780 Hey, John. Hey, everybody. 225 00:13:36,870 --> 00:13:39,720 Yeah, everybody. There you go. See, Mitch has got a DJ voice on 226 00:13:39,720 --> 00:13:43,290 paper, buddy. Happy New Year, gents. 227 00:13:44,220 --> 00:13:47,430 Happy New Year. It's been a long journey for us. 228 00:13:49,290 --> 00:13:51,870 Just for today's Board Meeting been a long journey, or just in 229 00:13:51,870 --> 00:13:54,810 general, just a whole long journey, just as is 230 00:13:55,140 --> 00:13:56,100 a bit of both Ah, 231 00:13:57,450 --> 00:14:01,950 yeah. 2022 was a whirlwind of development and lots of exciting 232 00:14:01,950 --> 00:14:02,370 things. 233 00:14:03,060 --> 00:14:03,840 No kidding. 234 00:14:03,960 --> 00:14:08,850 Now that go ahead, Alex, I was gonna ask you. So the reason I 235 00:14:08,880 --> 00:14:11,640 kind of put y'all together on this show together is because 236 00:14:11,640 --> 00:14:14,070 we've been talking so much about, you know, cross out 237 00:14:14,070 --> 00:14:18,480 comments and that kind of thing. So we put this together the last 238 00:14:18,480 --> 00:14:21,180 couple weeks, because I kind of wanted to see, we've talked a 239 00:14:21,180 --> 00:14:25,560 lot about cross app comments, but then we haven't really, you 240 00:14:25,560 --> 00:14:31,710 know, pod VS is one of the only apps that has it in the app. And 241 00:14:31,710 --> 00:14:37,410 then, Alex, you've got a bunch of knowledge and development, 242 00:14:38,790 --> 00:14:44,490 sort of IP involved in thinking this thing through and getting 243 00:14:44,490 --> 00:14:47,400 it implemented. So I thought it just might be good to have sort 244 00:14:47,400 --> 00:14:50,340 of like the cross that come in executive committee. 245 00:14:50,430 --> 00:14:53,820 Oh, oh, yeah. Is it the same as the comp the compensation 246 00:14:53,820 --> 00:14:54,270 committee? 247 00:14:56,760 --> 00:15:00,420 There's actually no compensation committee at all. So even isn't 248 00:15:00,420 --> 00:15:02,190 it? Yeah, 249 00:15:02,639 --> 00:15:05,849 before we start, want to welcome everybody in the chat room. want 250 00:15:05,849 --> 00:15:10,289 to welcome everybody listening live, we are lit. And you're 251 00:15:10,289 --> 00:15:14,099 probably listening to it on curio caster or pod verse. And 252 00:15:14,489 --> 00:15:20,039 you can find more about that by checking out each of those apps. 253 00:15:21,029 --> 00:15:23,489 And just wanna make sure everyone knows that we love them 254 00:15:23,489 --> 00:15:26,429 in the in the chat room. And of course, there they are already 255 00:15:26,429 --> 00:15:29,099 pre boosting us. So good to have everybody here. 256 00:15:30,300 --> 00:15:33,810 But just in general, like Alex, I guess I want to start with 257 00:15:33,810 --> 00:15:38,430 you. Because what do you think there's been? We've been just 258 00:15:38,430 --> 00:15:42,330 been talking around cross app comments for weeks now. Like, 259 00:15:42,330 --> 00:15:47,100 what were what is your sense of where of where it's at? And then 260 00:15:47,250 --> 00:15:52,110 what what you envision as as what it will look like? Let's 261 00:15:52,110 --> 00:15:54,780 just, I don't want to guide you too much in question. We'll 262 00:15:54,780 --> 00:15:58,110 leave it open. But I mean, what do you think? What do you think 263 00:15:58,110 --> 00:16:01,950 is a reasonable sort of road roadmap? And then where do you 264 00:16:01,950 --> 00:16:05,190 think we could be like, within a couple of years? 265 00:16:08,670 --> 00:16:10,920 Well, short term, I think we're actually in a really good 266 00:16:10,920 --> 00:16:14,190 position. Kind of backup a little bit about the big 267 00:16:14,190 --> 00:16:17,490 picture. I think. Maybe in the beginning, we got a little bit 268 00:16:17,490 --> 00:16:23,490 too caught up on the perfect solution, which is, we didn't 269 00:16:23,490 --> 00:16:30,240 want to depend on on the Macedon API for either hosting or 270 00:16:30,240 --> 00:16:35,010 replying. But I think, especially within the last few 271 00:16:35,010 --> 00:16:40,470 months, we've noticed that was the influx of Macedon that I 272 00:16:40,470 --> 00:16:45,390 think it's a prime time to allow a dependency on the message API 273 00:16:45,390 --> 00:16:50,940 for inap replying. So the way James Crillon explained last 274 00:16:50,940 --> 00:16:55,950 week with the candidate or flow where you'd have popovers acting 275 00:16:55,950 --> 00:17:00,390 as a Macedon client. I think that we can do that today. 276 00:17:00,840 --> 00:17:03,900 There's plenty of examples where I've gone back and forth with 277 00:17:03,900 --> 00:17:11,070 Mitch on some of the available JavaScript libraries to do it. I 278 00:17:11,310 --> 00:17:17,430 think that is easily doable. Right now, obviously, talking 279 00:17:17,430 --> 00:17:20,730 about UX that it's not really my dog, my dog house, but uh, 280 00:17:22,410 --> 00:17:29,130 that's I'll leave Mr. Comment on that. But I think working on, on 281 00:17:29,160 --> 00:17:34,470 understanding how we've had these traditional podcast client 282 00:17:34,590 --> 00:17:37,500 UX for so long, and kind of breaking out of that will be 283 00:17:37,500 --> 00:17:38,010 important. 284 00:17:40,019 --> 00:17:43,499 You're doing me you're doing it already. With peer to write. I 285 00:17:43,499 --> 00:17:46,889 mean, this is just so people understand. I mean, when when 286 00:17:46,889 --> 00:17:50,639 you're you, people, people are interacting with peer tubes 287 00:17:50,639 --> 00:17:54,659 activity pub, went through through Mastodon, I mean, so 288 00:17:54,659 --> 00:17:57,659 this, this is this is doable. It's not theoretical. And this 289 00:17:57,659 --> 00:17:59,909 is actually code that exists. 290 00:18:00,450 --> 00:18:03,450 Yes, that's correct. And I'm actually actively working on 291 00:18:03,480 --> 00:18:07,980 upstreaming, that code into the main Putri project. So 292 00:18:07,980 --> 00:18:11,520 hopefully, within six months, that will be available to 293 00:18:11,520 --> 00:18:13,860 everyone who can run peer to peer to. 294 00:18:14,460 --> 00:18:19,830 And that's the you also posted something to me, I think it was 295 00:18:19,860 --> 00:18:24,720 maybe today or yesterday, and I was looking through it about 296 00:18:25,470 --> 00:18:28,770 giving out chat, having a live chat and then giving out the 297 00:18:28,770 --> 00:18:34,530 live chat details within activity pub messages. And 298 00:18:34,530 --> 00:18:37,080 that's somebody something somebody's proposed, but I mean, 299 00:18:37,110 --> 00:18:40,170 I think I think what you said was it made a lot of made a lot 300 00:18:40,170 --> 00:18:43,560 of sense, which we you know, we can it makes sense to adopt that 301 00:18:43,560 --> 00:18:46,770 not Reapered not just basically piggyback off that work, but 302 00:18:46,770 --> 00:18:47,640 within peer tube. 303 00:18:49,380 --> 00:18:52,050 Yes, although I want to be very clear, I think we should 304 00:18:53,730 --> 00:18:57,990 distinctly avoid confusing live chat and comments. It's a 305 00:18:57,990 --> 00:19:00,570 totally different experience for totally different purposes. 306 00:19:01,649 --> 00:19:05,369 Yeah. And because you corrected me on that couple of weeks ago, 307 00:19:05,369 --> 00:19:07,979 because you were saying that, you know, there's, you have a 308 00:19:07,979 --> 00:19:10,709 live chat if and when you're in I think the perfect example, 309 00:19:10,799 --> 00:19:14,489 sort of mentally that people can, can can envision is 310 00:19:14,999 --> 00:19:18,449 YouTube, and then you have a live chat on the same screen. 311 00:19:18,449 --> 00:19:21,719 You have a live chat and you have comments, you have both and 312 00:19:21,779 --> 00:19:22,529 and I have 313 00:19:22,529 --> 00:19:25,259 three including the Super Chat, you have three really which 314 00:19:25,259 --> 00:19:26,519 would be our Instagrams. 315 00:19:27,239 --> 00:19:31,739 Right? Yes, you really have has it conceptually, two, 316 00:19:32,339 --> 00:19:35,849 technically three things happening at the same time. And 317 00:19:35,939 --> 00:19:39,389 I tend to forget that because when you think of live chat, 318 00:19:39,389 --> 00:19:41,729 you've I forget that the comments are also there. 319 00:19:44,579 --> 00:19:48,359 Yeah, so live chat is definitely for me to just take no agenda as 320 00:19:48,359 --> 00:19:53,339 an example. It's for on the fly. trolling for lack of a better 321 00:19:53,339 --> 00:19:53,789 term. 322 00:19:54,120 --> 00:19:58,200 No, that's exactly what it is when we call it specifically 323 00:19:58,200 --> 00:20:01,170 call it the troll room, not the chat. Room on no agenda. 324 00:20:01,349 --> 00:20:04,019 And for some experiences, I mean, you can go to Twitch for 325 00:20:04,019 --> 00:20:06,239 some of the smaller channels that are, you know, there's 326 00:20:06,239 --> 00:20:09,449 legitimate real time discussion happening. But it's not 327 00:20:09,449 --> 00:20:13,169 mentioned process by any means. It's, it's, you know, it's near 328 00:20:13,169 --> 00:20:17,939 real time as possible. And comments are for more long, long 329 00:20:17,939 --> 00:20:20,549 term formal discussion, I think, well as formal as you can 330 00:20:20,549 --> 00:20:21,029 imagine. 331 00:20:22,049 --> 00:20:27,299 What what I've noticed, and this came up on the last episode, I 332 00:20:27,299 --> 00:20:30,809 think so first of all, the idea that it's all on the same page 333 00:20:30,809 --> 00:20:33,509 is important. And for those who are a little lost right now, 334 00:20:33,809 --> 00:20:37,199 we're talking about the concept of being able to comment on the 335 00:20:37,199 --> 00:20:41,099 podcast episode. And that showing up on that episode in 336 00:20:41,099 --> 00:20:44,129 every app that integrates the cross app comments, or the 337 00:20:44,129 --> 00:20:48,119 social interact tag as it's officially known. When you play 338 00:20:48,119 --> 00:20:52,559 a YouTube video, the comments are static down below, and you 339 00:20:52,559 --> 00:20:56,009 can sort them as well, from newest or most popular, that's 340 00:20:56,009 --> 00:20:58,499 not to be underestimated. I have no idea what people typically 341 00:20:58,499 --> 00:21:02,549 deal with the default is that you can set that. But you also 342 00:21:02,549 --> 00:21:06,509 have the option of playing back the live chat, which honestly, I 343 00:21:06,509 --> 00:21:08,969 kind of like if I'm if I'm watching some, even though I 344 00:21:08,969 --> 00:21:12,269 can't interact with it, and it says this is a this is a pre 345 00:21:12,269 --> 00:21:15,839 recorded, when that's kind of scrolling by on the side. I've 346 00:21:15,839 --> 00:21:17,609 always found that to be interesting. 347 00:21:20,009 --> 00:21:22,319 It depends on the on the stream. 348 00:21:23,040 --> 00:21:27,540 Well, it's a UX decision that they've made that clearly is 349 00:21:27,540 --> 00:21:30,000 working otherwise, I presume they did not do that. 350 00:21:30,299 --> 00:21:32,489 Well, yeah. It's honestly a feeling when you're watching a 351 00:21:32,489 --> 00:21:35,309 lot. That's part of lifetime experience. Right? Just seeing 352 00:21:35,309 --> 00:21:39,179 that the chaos, especially some of the bigger streams going on 353 00:21:39,179 --> 00:21:42,389 in the live chat as as they discuss things and people react 354 00:21:42,389 --> 00:21:44,249 to them, even if it's meaningless. 355 00:21:45,150 --> 00:21:46,650 Yeah, right. Yeah. 356 00:21:46,650 --> 00:21:50,340 I'm saying as it as a playback mechanism, it's, it's, it has 357 00:21:50,340 --> 00:21:54,030 value when you can play if you're coming in. And as it was 358 00:21:54,030 --> 00:21:56,970 live, and it was two different things, I realize it, but to 359 00:21:56,970 --> 00:22:00,690 say, chat shouldn't be a part of this. I don't know if that's 360 00:22:00,690 --> 00:22:03,630 correct, because we're looking at the template at the model 361 00:22:03,630 --> 00:22:09,180 that people like, and having a having that role, that scrolling 362 00:22:09,180 --> 00:22:12,960 thing while you're listening to it, even if it's a week later, 363 00:22:13,290 --> 00:22:16,020 is not without value for obviously for someone. 364 00:22:18,450 --> 00:22:21,720 Yeah, yeah, no, yeah, we're saying, Yeah, I think we're 365 00:22:21,720 --> 00:22:24,570 Yeah, we're saying that we're just saying that, like, we're 366 00:22:24,570 --> 00:22:28,380 talking about, about the giving out of the live chat information 367 00:22:28,380 --> 00:22:31,920 in activity pub. So that activity pub, been making the 368 00:22:31,920 --> 00:22:34,830 distinction between activity Pub is the comments activity. Pub is 369 00:22:34,830 --> 00:22:39,510 not the live chat. Agreed, complete. Yeah, yeah. Yeah, cuz, 370 00:22:39,570 --> 00:22:45,750 I mean, you gotta have some way to. I mean, I think it's fair to 371 00:22:45,750 --> 00:22:50,400 say that activity pub can be, and can be a carrier of a lot of 372 00:22:50,400 --> 00:22:56,850 stuff. Probably Probably a good carrier of a lot of a lot of 373 00:22:56,850 --> 00:23:01,050 information, rather than, rather than these, these sort of, 374 00:23:01,080 --> 00:23:05,850 rather than the thing itself, it can be a transporter of various 375 00:23:05,850 --> 00:23:07,380 things. Is that am I getting that? Right? 376 00:23:08,730 --> 00:23:12,300 Yeah, let me explain, I guess the history of why that came up. 377 00:23:12,690 --> 00:23:16,080 Okay. Basically, it with work I don't appear to have I'm 378 00:23:16,110 --> 00:23:22,410 allowing a way for pure to plugins to extend the RSS feeds. 379 00:23:22,890 --> 00:23:25,830 So if you host peer tube, and you want to add something to 380 00:23:25,830 --> 00:23:29,010 your RSS feed without having to modify the software, you'll be 381 00:23:29,010 --> 00:23:34,230 able to do that with the plugin. The the live chat thing you're 382 00:23:34,230 --> 00:23:37,530 mentioning is me working with with a live chat plugin 383 00:23:37,530 --> 00:23:41,700 developer for peer tube to work on a specification in parallel 384 00:23:41,700 --> 00:23:45,300 with an activity buff specification. So we can get 385 00:23:45,660 --> 00:23:50,790 live chat, you know, realistically into an RSS feed. 386 00:23:51,360 --> 00:23:56,400 And the parallel there is activity published just as 387 00:23:56,610 --> 00:24:00,390 extensible with as RSS with the namespace work and we're doing 388 00:24:00,840 --> 00:24:04,620 it just, it's just JSON and linked to structures. And 389 00:24:04,620 --> 00:24:09,420 that's, um, that's one of the big reasons activity Pub is so 390 00:24:09,450 --> 00:24:13,380 useful for us, is because we actually have that protocol. 391 00:24:13,380 --> 00:24:17,880 Whereas if we were to try to use an alternative, like Nostrovia, 392 00:24:17,880 --> 00:24:19,140 would have to invent all that. 393 00:24:20,490 --> 00:24:24,180 Yeah. All right. So where are we in the conversation? I'm a 394 00:24:24,180 --> 00:24:28,440 little lost. I mean, I'm here to find out how I can get the 395 00:24:28,440 --> 00:24:31,320 comments that I've been posting in the way I've been told to do 396 00:24:31,320 --> 00:24:34,650 it to surface in apps and for people to be able to comment in 397 00:24:34,650 --> 00:24:35,220 the app. 398 00:24:37,140 --> 00:24:40,860 short answers, make your map make your package client a 399 00:24:40,860 --> 00:24:43,380 message on client and allow the user to sign in. 400 00:24:46,200 --> 00:24:50,430 Well, I would I don't have a podcast client. I'm dependent 401 00:24:50,430 --> 00:24:55,440 upon podcast apps that are being created. So I'm just trying to 402 00:24:55,440 --> 00:24:58,500 follow the spec and see if we can get something to surface 403 00:25:00,269 --> 00:25:03,659 Well, there'll be a lot of talk from a front end perspective. 404 00:25:04,409 --> 00:25:09,689 These. So, cross app comments and live chat are two totally 405 00:25:09,929 --> 00:25:14,189 distinct features. You see this on youtube today, there's 406 00:25:14,189 --> 00:25:19,319 comments that are left asynchronously just reply to 407 00:25:19,319 --> 00:25:22,349 people's posts. And then there's also a separate live chat 408 00:25:22,349 --> 00:25:30,929 experience. So with regard to Macedon implementation, I'd like 409 00:25:30,929 --> 00:25:35,159 to say that the reason that we haven't seen faster adoption 410 00:25:35,459 --> 00:25:39,119 from the app side so you can actually get in and start 411 00:25:39,119 --> 00:25:42,839 replying within the app is just a knowledge, issue. 412 00:25:43,439 --> 00:25:47,279 implementation details about activity pub, all of this is 413 00:25:47,279 --> 00:25:52,049 possible today, with the social interact tag. And it has been 414 00:25:52,049 --> 00:25:56,729 possible for over a year, it's just a matter of, for us to 415 00:25:56,789 --> 00:25:59,639 learn the implementation details, which Alex has been 416 00:25:59,639 --> 00:26:03,209 helping us with, and there seems to be at least one good library 417 00:26:03,209 --> 00:26:08,309 we can use for this purpose. Ah, so. So right now today, in pod 418 00:26:08,309 --> 00:26:15,239 verse, we have a read only cross app comments experience. So if 419 00:26:15,239 --> 00:26:18,599 the podcaster provides a link to their Macedon post, it doesn't 420 00:26:18,629 --> 00:26:21,329 doesn't have to be Macedon, it could be other activity pub 421 00:26:22,229 --> 00:26:26,789 services, then, what our app will do is we'll use John 422 00:26:26,789 --> 00:26:32,939 Spurlock's Threadless, or Fred cap library, and that will pull 423 00:26:32,939 --> 00:26:38,309 in all of the replies that are associated with that activity 424 00:26:38,309 --> 00:26:42,509 pub posts. And so we have this read only you can't reply 425 00:26:42,509 --> 00:26:45,749 directly in the app. But that's only because we haven't done the 426 00:26:45,749 --> 00:26:51,179 work to learn how to do the OAuth process to let you log 427 00:26:51,179 --> 00:26:55,769 into your Macedon account, basically, within pod verse and 428 00:26:55,769 --> 00:27:01,709 then begin replying. So there's no technical limitation to why 429 00:27:01,919 --> 00:27:05,039 we haven't done yet. It's simply we haven't had the time to do 430 00:27:05,039 --> 00:27:10,769 it. But with the surge in popularity of Macedon, which was 431 00:27:10,919 --> 00:27:15,359 quite unexpected to me in 2022, it's becoming a high priority 432 00:27:15,359 --> 00:27:15,779 quickly. 433 00:27:16,740 --> 00:27:20,880 Yeah, so you can just take instead of about think that's 434 00:27:20,880 --> 00:27:24,150 probably what what Alex was saying earlier as we get to 435 00:27:24,150 --> 00:27:29,010 hooked on vanilla activity pub as being sort of, okay, every 436 00:27:29,070 --> 00:27:31,920 every implement every client implementation is going to have 437 00:27:31,920 --> 00:27:36,840 to roll and roll and activity pub solution. Whereas probably 438 00:27:36,840 --> 00:27:41,130 the best way forward net right now with the popularity of 439 00:27:41,130 --> 00:27:45,570 Mastodon in the in the flood of Mastodon people is just to say, 440 00:27:45,570 --> 00:27:49,890 okay, oh, auth out to your Mastodon account, and just do 441 00:27:49,890 --> 00:27:51,480 and just go that way. Now 442 00:27:51,509 --> 00:27:57,149 a question Will that will that them work? If you so you, you 443 00:27:57,149 --> 00:28:02,369 authenticate yourself once? And and then you won't have to go in 444 00:28:02,369 --> 00:28:07,319 and do all the dance of oh, I have to copy this find it go to 445 00:28:07,349 --> 00:28:12,839 go to my instance. And then only then can I reply to it? Um, you 446 00:28:12,839 --> 00:28:15,329 know what I'm talking about this, this kind of loop around 447 00:28:15,329 --> 00:28:16,769 that has to be done at this moment. 448 00:28:18,359 --> 00:28:22,679 Yeah, that doesn't work. And the reason I know it'll work is 449 00:28:22,679 --> 00:28:26,459 because you already use a client use pin for even for his doing 450 00:28:26,459 --> 00:28:27,119 this already. 451 00:28:28,109 --> 00:28:30,809 Ah, yeah. Okay. That's how they do that guy. 452 00:28:30,839 --> 00:28:35,669 Yeah. So what will have to happen is the partners, for 453 00:28:35,669 --> 00:28:40,409 example, will have to do that search step for you. For some 454 00:28:40,529 --> 00:28:44,009 stupid mess on reasons. But yeah, it'll be it'll be a 455 00:28:44,009 --> 00:28:45,179 seamless experience. 456 00:28:46,319 --> 00:28:50,249 Well, then we're all done. It works. 457 00:28:52,319 --> 00:28:53,069 short episode. 458 00:28:56,099 --> 00:29:01,259 Yeah, I'm actually gonna put pin of war in the, into the, into 459 00:29:01,259 --> 00:29:05,069 the show notes so people can see how that works. So is it? So 460 00:29:05,099 --> 00:29:08,219 okay, so this is really well, there's a couple of other things 461 00:29:08,219 --> 00:29:10,979 that I think are non technical that have been an issue. One is, 462 00:29:13,109 --> 00:29:17,099 how does this show up in the UI? Is it is it something that will 463 00:29:17,099 --> 00:29:19,889 move to the front? Now that seems like people are using it? 464 00:29:20,129 --> 00:29:25,079 Is it something that app developers want to see it on all 465 00:29:25,079 --> 00:29:28,139 the shows and don't want to have an empty spot? And because 466 00:29:28,139 --> 00:29:31,649 that's, that's clearly UI UX decisions that have to be made. 467 00:29:31,649 --> 00:29:36,269 So if there's no comment, or no rude post, or just just a random 468 00:29:36,269 --> 00:29:39,059 podcast, do you still we still want to have comments there? I 469 00:29:39,059 --> 00:29:41,579 mean, there's a lot of things that I remember from almost two 470 00:29:41,579 --> 00:29:44,879 years ago, I think, when we started talking about this, that 471 00:29:45,269 --> 00:29:50,969 that were raised as issues and I'm just not sure how, you know 472 00:29:50,999 --> 00:29:57,029 how we can motivate people to to start thinking about it and 473 00:29:57,029 --> 00:30:00,179 start implementing or not implementing or coming to some 474 00:30:00,179 --> 00:30:02,579 kind of consensus because right now we basically I think doesn't 475 00:30:02,579 --> 00:30:07,409 curio caster also do comments. Read Only comments? I don't 476 00:30:07,409 --> 00:30:09,149 think so. No. So it's only pod. 477 00:30:10,170 --> 00:30:12,780 Think it's only pod verson pod friend? 478 00:30:13,889 --> 00:30:17,579 Well, I've been kicking around ideas with Alex and Korean, our 479 00:30:17,579 --> 00:30:20,969 co founder. And so right now today the experience is if you 480 00:30:20,969 --> 00:30:23,849 go, if you open the player in pod verse and you swipe to the 481 00:30:23,849 --> 00:30:27,959 left or right, it'll show additional features. One of 482 00:30:27,959 --> 00:30:31,319 those features is comments. However, there's no indicator 483 00:30:31,349 --> 00:30:34,889 when the player appears, if a show has comments or not. So 484 00:30:34,889 --> 00:30:38,849 that is a UX problem that we need to solve. But it is 485 00:30:38,849 --> 00:30:43,079 solvable. And now that you know, comments are gaining a bit more 486 00:30:43,079 --> 00:30:46,829 traction. So we're thinking of how we can add it. So at a 487 00:30:46,829 --> 00:30:51,149 glance, you'll know if comments are available. I have two ideas 488 00:30:51,149 --> 00:30:54,929 we've been talking about one that people seem to like the 489 00:30:54,929 --> 00:31:00,569 most. So we could have one comment show. Like if comments 490 00:31:00,689 --> 00:31:04,229 are available, just one truncated comment appears on the 491 00:31:04,229 --> 00:31:09,389 screen. And then you tap it, and then the full list of comments 492 00:31:09,629 --> 00:31:14,399 could appear. So that would be in prime real estate on the 493 00:31:14,759 --> 00:31:20,429 right when you load the player. The other alternative I was 494 00:31:20,429 --> 00:31:24,779 thinking about this would take up less vertical real estate, 495 00:31:24,779 --> 00:31:28,049 which is the advantage but I'm not sure if this is a way go up. 496 00:31:28,079 --> 00:31:33,749 So Spotify has a feature where if a if a song has lyrics, 497 00:31:34,079 --> 00:31:37,379 there's a little card that peeks up from the bottom of the 498 00:31:37,379 --> 00:31:43,409 screen. And if you scroll down, it will reveal the lyrics. This 499 00:31:43,409 --> 00:31:45,899 design pattern could work for other things. Maybe it could 500 00:31:45,899 --> 00:31:50,849 work for comments. So if a podcast doesn't have comments, 501 00:31:50,849 --> 00:31:53,159 there just would not be an indicator on the screen. 502 00:31:53,640 --> 00:31:56,730 Realize a common idea like that is similar to 503 00:31:56,760 --> 00:32:00,990 streaming, streaming payments and booster grams if if the 504 00:32:00,990 --> 00:32:04,290 podcast doesn't have it, the UI doesn't show the buttons. 505 00:32:04,680 --> 00:32:07,830 But I actually think we should say comments are disabled for 506 00:32:07,830 --> 00:32:12,540 this podcast. I think that will actually help drive adoption and 507 00:32:12,540 --> 00:32:13,440 reduce confusion. 508 00:32:14,069 --> 00:32:17,789 That's a cool idea too. Because then then just din the negative 509 00:32:17,789 --> 00:32:21,389 of saying there are no comments for this podcast indicates that 510 00:32:21,389 --> 00:32:23,339 some podcasts actually do have comments. 511 00:32:24,180 --> 00:32:27,360 Yeah, I would suggest saying instead of have been disabled 512 00:32:27,360 --> 00:32:32,250 say not enabled. Not a little little friendlier. No, not 513 00:32:32,910 --> 00:32:35,850 enabled, I think is the right word. Because it's the podcast 514 00:32:35,850 --> 00:32:37,380 who should be enabling Correct. 515 00:32:38,819 --> 00:32:40,799 I was going out to YouTube verbiage. But 516 00:32:42,900 --> 00:32:46,560 please don't make me speak Silicon Valley language. Let's 517 00:32:46,560 --> 00:32:48,420 just do an upside down version. 518 00:32:49,799 --> 00:32:54,989 That's, that's sort of like an end what's what's the opposite 519 00:32:54,989 --> 00:32:57,899 of a dark pattern? It's it's a light pattern. That's this an 520 00:32:57,899 --> 00:33:01,919 anti dark pattern is your tip. It's like you're saying this, 521 00:33:01,949 --> 00:33:05,819 this thing doesn't have this thing. But wink wink, this thing 522 00:33:05,819 --> 00:33:07,349 is available to all yes, 523 00:33:07,380 --> 00:33:11,340 yeah. Not enabled. And that's up to any any podcast app how they 524 00:33:11,340 --> 00:33:14,670 want to do it. I mean, yeah, I'm so happy that we've gotten to 525 00:33:14,670 --> 00:33:17,520 this point. Because if I can summarize, because there's a lot 526 00:33:17,520 --> 00:33:23,700 of technical stuff. Summarizing, we got slowed down a bit, 527 00:33:23,700 --> 00:33:27,180 because we were looking purely at activity pub, it's a big 528 00:33:27,180 --> 00:33:30,600 learning curve. There's a lot to it. And you know, every single 529 00:33:30,600 --> 00:33:33,330 developer here obviously has millions of dollars and a whole 530 00:33:33,330 --> 00:33:35,940 staff to do whatever they want all day long. They just chose 531 00:33:35,940 --> 00:33:40,620 not to do it. So but now is the consensus, at least amongst the 532 00:33:40,620 --> 00:33:46,680 board here today, as as we count them, that going the Macedon API 533 00:33:46,680 --> 00:33:51,360 route may be the way to go as long as it's open for anyone to 534 00:33:51,390 --> 00:33:54,810 you know, obviously, you can use any activity pub client. Is that 535 00:33:54,840 --> 00:33:56,310 what we're what we're looking at now. 536 00:34:00,000 --> 00:34:02,610 That's my understanding, but I'll defer to Alex. 537 00:34:03,329 --> 00:34:08,759 Yeah, I think that's the way I like to see it. From a 538 00:34:08,969 --> 00:34:13,199 developer's perspective, is the mess on API for better or for 539 00:34:13,199 --> 00:34:18,269 worse is sort of becoming like the s3 of a social network, at 540 00:34:18,269 --> 00:34:23,159 least for activity, but then s3 s3 being the storage. 541 00:34:24,180 --> 00:34:27,810 Yeah, that's a good analogy. And because it's like, we can all 542 00:34:27,810 --> 00:34:32,850 wish that things were more generic and more sort of higher, 543 00:34:33,540 --> 00:34:38,550 higher level but then it's sort of like it's wishing versus sort 544 00:34:38,550 --> 00:34:44,280 of accepting reality as it is and that the the one extra the 545 00:34:44,280 --> 00:34:48,600 one benefit that I can think of on top of that is the fact that 546 00:34:48,600 --> 00:34:54,150 if you if you are just Oh thing out to to a mastodon instance, 547 00:34:54,360 --> 00:34:59,310 to an account on a mast on it says it didn't didn't matter. 548 00:34:59,340 --> 00:35:01,410 THE MODERATOR Shouldn't have those comments becomes the 549 00:35:01,410 --> 00:35:05,760 instances problem, not the ads problem. So so it really solves 550 00:35:07,859 --> 00:35:12,749 that big time. And it's easy to point podcasters to a $5 a month 551 00:35:12,749 --> 00:35:17,069 solution, you know, to host their own Mastodon client to set 552 00:35:17,069 --> 00:35:20,429 it up. I mean, that becomes almost a non issue. That's 553 00:35:20,429 --> 00:35:21,209 really cool. 554 00:35:22,380 --> 00:35:25,710 Yeah, I mean, if if Mitch has to build his own activity pub 555 00:35:25,710 --> 00:35:28,980 stack, then I mean, it's, then he's just, there's no way to get 556 00:35:28,980 --> 00:35:31,620 around that having to be responsible for the moderation. 557 00:35:33,000 --> 00:35:35,850 But yeah, and early on, that was part of the thing. That was one 558 00:35:35,850 --> 00:35:38,310 of the things that kept us from really moving forward with it, 559 00:35:38,310 --> 00:35:41,730 which is people were suggesting that we would create our own 560 00:35:41,760 --> 00:35:45,600 Macedon instance, and help people sign up for it. And that 561 00:35:45,600 --> 00:35:49,890 would be great. But we have to operate on a very lean budget as 562 00:35:49,890 --> 00:35:53,220 an open source project. And we're we're not interested in 563 00:35:53,220 --> 00:35:56,610 the amount of work that we'd be involved in, in moderating 564 00:35:56,610 --> 00:35:59,730 people's comments, because, like it or not, people can post very 565 00:35:59,730 --> 00:36:04,260 awful things, or illegal things. And that's, that's not something 566 00:36:04,320 --> 00:36:06,630 we want to be responsible for maintaining. 567 00:36:06,990 --> 00:36:13,530 So the experience would be, I opened up a podcast, I'm just 568 00:36:13,560 --> 00:36:16,440 just going through this from a listener perspective. And 569 00:36:16,710 --> 00:36:19,440 there's an indication Oh, that you can comment on this or there 570 00:36:19,440 --> 00:36:22,680 may be comments, maybe you can comment. And there's already 10 571 00:36:22,680 --> 00:36:27,480 comments, a counter. And then if I want to interact with that, I 572 00:36:27,480 --> 00:36:30,930 will, I will log in with my own app Mastodon account, if I don't 573 00:36:30,930 --> 00:36:36,930 know what that is, then a pointer, go over here. Get a 574 00:36:36,930 --> 00:36:39,810 mastodon account anywhere you want to get a mastodon account, 575 00:36:39,810 --> 00:36:44,490 because they're pretty easy to get now with all the press about 576 00:36:44,490 --> 00:36:47,040 it. Is that is that? Is that the flow? 577 00:36:47,280 --> 00:36:50,160 Yeah, that's basically it. And it is getting easier for people 578 00:36:50,190 --> 00:36:53,850 with adoption. So you would get a read only experience by 579 00:36:53,850 --> 00:36:57,390 default, you can just scan and you'll see whatever the comments 580 00:36:57,390 --> 00:37:00,810 are. And somewhere in the UI, there'll be a login button. Or 581 00:37:00,810 --> 00:37:04,320 maybe you press the Reply button. And first it prompts you 582 00:37:04,320 --> 00:37:09,690 to log in, then it redirects you to the to our own inap. Macedon 583 00:37:09,690 --> 00:37:10,500 login flow. 584 00:37:11,370 --> 00:37:12,150 Beautiful. 585 00:37:14,370 --> 00:37:17,400 Alex, what are you using for your A gates at activity pub dot 586 00:37:17,400 --> 00:37:20,700 a gates.io? What? What is the backing of that? Is that 587 00:37:20,700 --> 00:37:23,070 something you wrote? Or is that a Corona or what? 588 00:37:23,460 --> 00:37:28,830 I wish I had time for that. It was Paul Romer. And then I moved 589 00:37:28,830 --> 00:37:34,020 to a fork of it called rebased. Which is, it's very based in 590 00:37:34,020 --> 00:37:39,090 soap boxes is, honestly, the UI is better than mastodon. So 591 00:37:40,350 --> 00:37:41,190 definitely check it out. 592 00:37:41,759 --> 00:37:44,249 Is it a multi user type thing? Or is that just sort of like a 593 00:37:44,249 --> 00:37:46,349 single user instance type, do 594 00:37:46,560 --> 00:37:50,010 my mind is single instance. But by default, it's multi user. And 595 00:37:50,010 --> 00:37:52,650 I'm posting on a $5 month window. 596 00:37:53,820 --> 00:37:58,740 Because the the started, we talked last week about you know, 597 00:37:58,770 --> 00:38:03,240 get sort of bridging some of these things over to just get 598 00:38:03,600 --> 00:38:08,310 more, did just get more content to start to start the just start 599 00:38:08,310 --> 00:38:12,990 the activity post comment stream and kind of started outlining 600 00:38:12,990 --> 00:38:16,140 that writing it out on paper this week and looking at the 601 00:38:16,140 --> 00:38:21,810 activity protocol. And I mean, really is coming, looking at 602 00:38:21,810 --> 00:38:27,330 Mastodon it looks at the, the weaknesses and master the 603 00:38:27,330 --> 00:38:31,770 Achilles heel. And if somebody I'm sure there's more than one, 604 00:38:32,220 --> 00:38:36,810 but to me, the big Achilles heel of Mastodon is this dependence 605 00:38:36,810 --> 00:38:41,430 on sidekick for all the notifications that happen that 606 00:38:41,970 --> 00:38:46,500 that thing seems to be the really the thing that kills that 607 00:38:46,500 --> 00:38:49,500 kills it and makes it hard because you'll end up with, you 608 00:38:49,500 --> 00:38:54,480 know, 10s of 1000s of queued sidekick messages for all of 609 00:38:54,480 --> 00:38:57,270 this activity that's going in, you know, when things start to 610 00:38:57,270 --> 00:39:01,500 federate. And I feel like if you could take that thing out and 611 00:39:01,500 --> 00:39:07,170 make it where it was put it into a more efficient language or a 612 00:39:07,170 --> 00:39:10,770 more efficient structure. Things would be you could do it on a 613 00:39:10,770 --> 00:39:14,730 much smaller scale without all the huge overhead of Mastodon 614 00:39:17,430 --> 00:39:21,180 Yeah, not to get too nerdy, but Macedon. The main difference 615 00:39:21,180 --> 00:39:26,070 between messily on imploring for support Rama is Macedon doesn't 616 00:39:26,250 --> 00:39:30,210 like us, it's its own internal data structure, which 617 00:39:30,210 --> 00:39:33,720 complicates things significantly. Whereas the 618 00:39:33,720 --> 00:39:36,300 simplest activitypub implementations just store the 619 00:39:37,140 --> 00:39:39,630 the JSON in the database and use it that way. 620 00:39:40,200 --> 00:39:44,100 Yeah, cuz I was thinking you could even do that with me. You 621 00:39:44,100 --> 00:39:50,040 could even do it with just object storage. I mean, to you 622 00:39:50,040 --> 00:39:52,380 could go for I guess, one transit, you could go far with 623 00:39:52,380 --> 00:39:57,150 just object storage until you needed to do the note the 624 00:39:57,150 --> 00:40:00,360 federated notification, like you can really put something 625 00:40:00,360 --> 00:40:04,500 together. That's very, very lightweight. Which is what I'm 626 00:40:04,500 --> 00:40:09,480 what I'm hoping to do. But the anyone just went went off the 627 00:40:09,480 --> 00:40:09,720 rails. 628 00:40:10,500 --> 00:40:12,810 I like it. You're fixing mastodon? That's a good idea. 629 00:40:13,500 --> 00:40:15,780 Right? That's not? 630 00:40:16,949 --> 00:40:20,699 Well, I mean, I'll just say that we federate heavily on podcasts 631 00:40:20,699 --> 00:40:25,499 index dot social. All I do is I pay Masto dot host a fee every 632 00:40:25,499 --> 00:40:29,549 month, I pay them a little extra for the amount of users and for 633 00:40:29,549 --> 00:40:34,739 full site search. But you know, I've never seen has that thing 634 00:40:34,739 --> 00:40:37,889 ever gone down really, I don't think I've ever seen an outage. 635 00:40:38,159 --> 00:40:42,929 And it's Federation, everything seems to work pretty well. So I 636 00:40:42,929 --> 00:40:46,079 mean, if you're talking millions and millions and millions of 637 00:40:46,079 --> 00:40:49,829 people like Mastodon dot social, yeah, that's a whole different 638 00:40:49,859 --> 00:40:53,969 whole different ball of wax. But it seems like that wouldn't be 639 00:40:53,969 --> 00:40:57,449 too much of an issue for for what we're doing here, would 640 00:40:57,449 --> 00:41:02,429 it? But no, I think if you get the, the way I understand it is 641 00:41:02,429 --> 00:41:07,799 if you get somebody on your own your instance, who has, you 642 00:41:07,799 --> 00:41:10,079 know, potentially a million followers 643 00:41:10,110 --> 00:41:13,800 waiting on your instance, who certainly I'm going to post on 644 00:41:13,800 --> 00:41:16,410 my own instance, isn't that the idea that the podcasters 645 00:41:16,410 --> 00:41:19,740 responsible for either, you know, getting their account 646 00:41:19,740 --> 00:41:22,500 somewhere or, or setting up their own server? 647 00:41:22,980 --> 00:41:25,830 Yes. Okay. What and yeah, and that's what it's what I'm 648 00:41:25,830 --> 00:41:29,100 talking about, sort of like inter internal to, to Mastodon 649 00:41:29,100 --> 00:41:34,500 itself. So, you can just imagine if you had an, let's say, if you 650 00:41:34,500 --> 00:41:39,270 had a podcast that had that was extremely popular, you know, and 651 00:41:39,270 --> 00:41:45,480 had 10s of 1000s of followers, then it would be the same sort 652 00:41:45,510 --> 00:41:52,500 of potential problem, as if you had somebody like, I don't know, 653 00:41:52,920 --> 00:41:59,550 Stephen Fry, who has 100,000 followers on Mastodon, Mastodon 654 00:41:59,550 --> 00:42:04,890 on the fediverse. Will. Now every time he posts, you're 655 00:42:04,890 --> 00:42:11,370 gonna have notifications going out in in the 1000s. As feta as 656 00:42:11,370 --> 00:42:15,270 that federates. So that's, that's where you hit a snag with 657 00:42:15,270 --> 00:42:20,220 Mastodon is that process takes a huge amount of load that's 658 00:42:20,220 --> 00:42:24,360 directly that's directly the ability for the instance to 659 00:42:24,360 --> 00:42:28,080 handle that is, is basically proportional to how much compute 660 00:42:28,080 --> 00:42:31,620 it has. Because I don't think that's a efficiently parallel 661 00:42:31,620 --> 00:42:32,310 operation. 662 00:42:34,950 --> 00:42:39,000 That said, it's a problem that would affect what like point 663 00:42:39,000 --> 00:42:43,170 00 1% of podcasts who would be interested in this sort of 664 00:42:43,170 --> 00:42:47,490 feature. And assuming that you have a big enough show, you can 665 00:42:47,550 --> 00:42:51,510 solve scaling problems with more money and resources, I would 666 00:42:51,510 --> 00:42:51,930 think 667 00:42:53,670 --> 00:42:59,820 it's a good problem to have, honestly. And there are there 668 00:42:59,820 --> 00:43:03,450 are actually ways to optimize it. The people that critique it 669 00:43:03,480 --> 00:43:05,280 generally don't know about the optimizations. 670 00:43:07,889 --> 00:43:09,899 Did that right, Alex? 671 00:43:10,320 --> 00:43:14,160 So um, that's only really the case. If, if each one of your 1 672 00:43:14,160 --> 00:43:19,770 million followers each has their own instance. Because if you 673 00:43:19,770 --> 00:43:23,700 have, you know, 500,000 followers on one instance, you 674 00:43:23,700 --> 00:43:26,130 know, that the activity pop servers can generally optimize 675 00:43:26,130 --> 00:43:28,020 that because they know that they're all at the same place. 676 00:43:28,860 --> 00:43:31,680 Gotcha. Because you always you have sort of a single inbox or 677 00:43:31,680 --> 00:43:32,100 whatever. 678 00:43:32,700 --> 00:43:36,030 Yeah, I mean, it's very, very, very similar to email in that 679 00:43:36,030 --> 00:43:40,140 regard. Okay. But you're talking about like the Reply All 680 00:43:40,140 --> 00:43:41,670 scenario, honestly. Which, 681 00:43:42,750 --> 00:43:46,170 yeah, premature optimization. Sorry. 682 00:43:49,020 --> 00:43:51,630 Okay, and I was gonna, I was going to interject something 683 00:43:51,630 --> 00:43:55,440 else, just to just to make it more complicated. May I? Go 684 00:43:55,440 --> 00:44:00,930 ahead. So the next question is, we have an app out there that is 685 00:44:00,930 --> 00:44:06,180 doing lightning comments. I don't know how these are 686 00:44:06,180 --> 00:44:09,660 integrated. I find them interesting. I don't know if 687 00:44:09,660 --> 00:44:13,710 it's the same thing. All and there's, you know, there's 688 00:44:13,740 --> 00:44:18,450 questions and maybe we can't solve this here. But if I look 689 00:44:18,450 --> 00:44:23,190 at my own booster grams, they are pretty much comments 690 00:44:23,220 --> 00:44:25,410 account, and certainly in this show, they're calm. It's always 691 00:44:25,410 --> 00:44:29,250 a comment, actually, it's pretty much always common, or nine out 692 00:44:29,250 --> 00:44:32,820 of 10. Our comment, is that something that we integrate into 693 00:44:32,820 --> 00:44:37,020 this, is that something that that should and is separate, if 694 00:44:37,020 --> 00:44:40,350 it is separate, how the heck do we make it work on all apps 695 00:44:40,350 --> 00:44:44,070 instead of just one? Is it something that we can consider 696 00:44:44,070 --> 00:44:45,930 at all? I throw that out there? 697 00:44:47,489 --> 00:44:51,899 Yeah, I mean, it's def, to me, it's definitely separate. And 698 00:44:51,899 --> 00:44:54,899 that's, that's why I'm starting starting to write the thing that 699 00:44:54,899 --> 00:45:00,299 I'm running is to pull, pull that over so that it can be so 700 00:45:00,299 --> 00:45:04,439 that it can exist as an activity pub comment without having to 701 00:45:05,039 --> 00:45:08,759 mix the two together so that they can keep their distinct to 702 00:45:08,789 --> 00:45:13,109 their distinctiveness without, but but also use the fact that 703 00:45:13,109 --> 00:45:16,169 people meet some people and people who will do do lightning 704 00:45:16,169 --> 00:45:21,659 comments. I mean, it's part of founds a popular app. And so 705 00:45:21,869 --> 00:45:27,029 people who do that are they do it a lot. So that's a lot of 706 00:45:27,029 --> 00:45:30,479 content. So if we could use that kind of, if we could use those 707 00:45:30,479 --> 00:45:36,749 comments, to pollinate, you know, the activity pub route 708 00:45:36,749 --> 00:45:41,369 post, I mean, that's, that's what I'm trying to do, I want to 709 00:45:41,369 --> 00:45:44,279 mix the two, I just don't want to mix the two together, like on 710 00:45:44,279 --> 00:45:45,869 it on the technical side, 711 00:45:47,280 --> 00:45:49,830 if I could try to explain my understanding of this problem. 712 00:45:49,830 --> 00:45:54,300 So lightening comments exist within the metadata that is 713 00:45:54,330 --> 00:45:57,930 transmitted in the lightning, the Bitcoin Lightning Network. 714 00:45:58,290 --> 00:46:02,160 And it works. For most use cases, if you want to send a 715 00:46:02,160 --> 00:46:07,500 short message to a podcaster, it can generally fit within the 716 00:46:07,860 --> 00:46:11,040 metadata that's sent. However, Lightning Network also has 717 00:46:11,070 --> 00:46:13,200 something beyond my understanding that involves 718 00:46:13,230 --> 00:46:17,850 onion routing, which leads to an unpredictable amount of 719 00:46:17,850 --> 00:46:22,440 characters that you're allowed to send with a message. And for 720 00:46:22,440 --> 00:46:25,620 a messaging platform, that's a very, that's a very big 721 00:46:25,620 --> 00:46:30,900 limitation. So in pod verse, For example, we say a limit of 400 722 00:46:30,900 --> 00:46:35,340 characters in your booster gram. But that's just a guess I can't 723 00:46:35,340 --> 00:46:39,570 predict how many characters you actually have before it'll get 724 00:46:39,570 --> 00:46:43,140 cut cut off, because apparently, as the transaction is sent 725 00:46:43,140 --> 00:46:47,820 between different nodes, if I'm saying that right, each address 726 00:46:47,820 --> 00:46:51,900 will get concatenated in the message, so we can't predict how 727 00:46:51,900 --> 00:46:57,630 much room we have to send. So that is one major limitation of 728 00:46:57,630 --> 00:47:04,800 a purely Lightning Network based chat, or commenting system. 729 00:47:06,330 --> 00:47:09,750 Whereas something like activity Pub is designed for this 730 00:47:09,750 --> 00:47:13,500 purpose. And we can reliably use it. 731 00:47:13,949 --> 00:47:17,249 Right? So this is where if I understand Alex, you had ideas 732 00:47:17,249 --> 00:47:21,179 about separating that out and having the message being maybe 733 00:47:21,179 --> 00:47:25,049 still carried in the TLB or not, but I know you've got something 734 00:47:25,289 --> 00:47:25,919 in mind. 735 00:47:28,050 --> 00:47:31,440 Yeah, basically, there's ways built into both activity pub and 736 00:47:31,440 --> 00:47:37,170 lightning to one activity pub extend the specification, which 737 00:47:37,200 --> 00:47:40,710 is non trivial, just want to make that clear, upfront. But 738 00:47:40,980 --> 00:47:44,010 long term, we can add things to these, you know, activity by 739 00:47:44,010 --> 00:47:47,910 messengers. If we're you know, if the work of Macedon or 740 00:47:47,910 --> 00:47:52,860 whatever to do, so we can, we can attempt that. What we, what 741 00:47:52,860 --> 00:47:56,820 we do is, we would essentially attach what I'm calling a 742 00:47:56,820 --> 00:48:00,360 payment proof proof of payment, which would work with any 743 00:48:00,360 --> 00:48:03,720 system, not just lightning. But Lightning has a way to sign 744 00:48:03,720 --> 00:48:05,970 messages. I mean, you can go into your lightning node and do 745 00:48:05,970 --> 00:48:12,690 it right now. And what we can do is define a specification to a 746 00:48:12,690 --> 00:48:17,670 predefined message format, that says, hey, I paid this amount to 747 00:48:17,670 --> 00:48:22,260 this person does address and here's my mind, you can write 748 00:48:22,260 --> 00:48:25,410 and you can attach that to your activity blog post, they could 749 00:48:25,410 --> 00:48:30,060 all cryptographically sign so you can prove who it is. And we 750 00:48:30,060 --> 00:48:33,630 have to work on ways of verifying that's accurate. But 751 00:48:33,900 --> 00:48:37,620 that's I think it's the best way forward, even if it wasn't 752 00:48:37,620 --> 00:48:42,090 actually I think the proof of payment or concept is important 753 00:48:42,090 --> 00:48:45,420 to just get get speech out of 754 00:48:46,110 --> 00:48:50,580 payments. So maybe baby steps versus what I'm hearing. Yeah, 755 00:48:50,580 --> 00:48:50,730 we 756 00:48:50,730 --> 00:48:53,880 can I mean, at first, we'll probably just say, hey, this 757 00:48:53,880 --> 00:48:58,200 person boosted this amount and you know, it can be faked. But 758 00:48:58,530 --> 00:49:01,200 you know, that's a long way away. 759 00:49:02,040 --> 00:49:05,490 Yeah, I'm Hope I mean, hopefully this hopefully this bridge work 760 00:49:05,490 --> 00:49:09,930 will become something will become that you know, so that we 761 00:49:09,930 --> 00:49:13,140 can Hey as Okay, these things, these things are coming over 762 00:49:13,650 --> 00:49:16,320 these comments that originated as lightning comments are coming 763 00:49:16,320 --> 00:49:21,180 over here. Okay, now they're coming over as activity pub. Now 764 00:49:21,210 --> 00:49:26,460 logical next step. Let's have them as let's split the 765 00:49:26,460 --> 00:49:30,240 activity, pub comment and the payment and then add proof, add 766 00:49:30,240 --> 00:49:35,580 the proof of payment. And then, you know, and then actually make 767 00:49:35,610 --> 00:49:39,360 the split over time. I mean, that to me that makes makes 768 00:49:39,360 --> 00:49:41,730 logical sense as a as a sort of a roadmap. 769 00:49:41,820 --> 00:49:47,040 So we got a 10,000 stat boost from Sam Sethi, who doesn't know 770 00:49:47,040 --> 00:49:50,400 him, and Sam says pod fans, which is his super secret 771 00:49:50,400 --> 00:49:54,720 project, which is now just boosting about openly is working 772 00:49:54,720 --> 00:49:58,080 to make itself a mastodon client. We already support the 773 00:49:58,080 --> 00:50:06,300 activity stream standard ie X verb object, we can see, the ad 774 00:50:06,300 --> 00:50:09,390 says, We can post on behalf of the user, when they comment on 775 00:50:09,390 --> 00:50:12,120 pod fans, the difference between a comment and a booster gram is 776 00:50:12,150 --> 00:50:16,140 only the payment part. So that he's already thinking along the 777 00:50:16,140 --> 00:50:19,860 same the same line. So it will be great if we can get pod verse 778 00:50:20,100 --> 00:50:24,060 and, and maybe pod fans and maybe one other to support the 779 00:50:24,060 --> 00:50:27,240 cross app comments to surface those? I tell you, I will 780 00:50:27,240 --> 00:50:28,470 promote the crap out of it. 781 00:50:30,239 --> 00:50:32,759 Sure, well, we're interested in it. And Alex and I have talked 782 00:50:32,759 --> 00:50:38,549 about it quite a bit with is a JSON payment token spec. And I 783 00:50:38,549 --> 00:50:41,639 think it can happen in parallel with lightning comments as they 784 00:50:41,639 --> 00:50:44,759 exist today. Lightning comments, just they have their 785 00:50:44,759 --> 00:50:47,459 limitations, because it's not intended, intended to be a 786 00:50:47,459 --> 00:50:52,919 messaging system. But there's no reason we couldn't send the 787 00:50:52,919 --> 00:50:55,649 message to two places simultaneously, we can include 788 00:50:55,649 --> 00:50:59,969 the message in the booster gram lightning data. And we could 789 00:50:59,969 --> 00:51:04,229 also post the message to activity pub at the same time. 790 00:51:04,619 --> 00:51:10,109 And I think the feature advantages of activity pub over 791 00:51:10,109 --> 00:51:15,269 enough time would allow it to replace strict dependency on, 792 00:51:15,599 --> 00:51:18,209 you know, the Lightning Network, which isn't intended for this 793 00:51:18,209 --> 00:51:21,479 purpose. Alright, for this purpose, 794 00:51:22,110 --> 00:51:22,950 I like 795 00:51:22,950 --> 00:51:27,450 it. The simplest solution for for fountain would be to just 796 00:51:28,110 --> 00:51:31,650 post a message on server and post the lightning comments as 797 00:51:31,680 --> 00:51:33,090 messages for those users. 798 00:51:34,290 --> 00:51:41,730 That is, yeah, that is a good idea. As I wonder, I wonder if 799 00:51:42,000 --> 00:51:44,550 Oscars thought about doing that, because that's, that's a good 800 00:51:44,550 --> 00:51:53,640 solution. The Mitch, I guess you had brought something up a while 801 00:51:53,640 --> 00:51:56,340 back, and I hadn't written down here to talk to ask you about it 802 00:51:56,340 --> 00:52:03,660 was the you said you were having trouble with the shim aspect of 803 00:52:03,840 --> 00:52:08,280 of the podcaster wallet stuff. And I think it was specifically 804 00:52:08,280 --> 00:52:12,480 related to Episode level splits. Can you run through that real 805 00:52:12,480 --> 00:52:14,550 quick, because I want to make sure that I'm not leaving you 806 00:52:14,550 --> 00:52:15,450 hanging on something? 807 00:52:16,230 --> 00:52:21,900 Sure. So as a podcast app, we get all of our data from RSS. 808 00:52:22,350 --> 00:52:26,430 It's the adopted standard provides all of the show 809 00:52:26,430 --> 00:52:30,690 information that every podcast app needs to give the full 810 00:52:30,690 --> 00:52:36,660 experience all the features that that podcast has. Now with the 811 00:52:36,690 --> 00:52:44,520 value tag, you guys have created the monster that the shim is the 812 00:52:44,820 --> 00:52:46,080 gentler word 813 00:52:47,220 --> 00:52:49,500 that you get, you can replace a letter in there if you wants to. 814 00:52:51,989 --> 00:52:56,669 Which is a temporary stand in, which allows people to get the 815 00:52:56,669 --> 00:53:00,809 same experience as if they added their podcast value tagged to 816 00:53:00,809 --> 00:53:03,629 their RSS feed, but it's actually hosted is it podcast 817 00:53:03,629 --> 00:53:04,499 index is that 818 00:53:04,500 --> 00:53:07,500 it's in the AP is in this comes out of the AICPA API, right. 819 00:53:07,950 --> 00:53:08,580 Yeah, that's right. 820 00:53:09,150 --> 00:53:14,430 Right. So what we have to do, we have to add an extra step in our 821 00:53:14,460 --> 00:53:19,230 database in our API and parsing system, so that we request from 822 00:53:19,500 --> 00:53:24,330 podcasts index, the value tag information for every podcast, 823 00:53:25,050 --> 00:53:30,660 that's fine for now, like, and it I think there's like 10,000, 824 00:53:30,750 --> 00:53:33,840 podcasts or something, which is pretty cool. There's that many 825 00:53:34,590 --> 00:53:39,540 that support it. Now, if we want to apply that to episodes, we 826 00:53:39,540 --> 00:53:43,740 have to also scrape that data from podcast index for every 827 00:53:43,740 --> 00:53:47,550 episode. So now that you know if there's like 100 episodes per 828 00:53:47,550 --> 00:53:51,930 podcast, now we're at a million points of information, we have 829 00:53:51,930 --> 00:53:57,270 to scrape from an API. If that was in the RSS feed itself, we 830 00:53:57,270 --> 00:54:01,050 wouldn't have to even go to podcast index for this purpose. 831 00:54:01,260 --> 00:54:04,680 So I think it makes a lot of sense that the shim has been 832 00:54:04,680 --> 00:54:08,880 used to get lift off with this feature. But it is something we 833 00:54:08,880 --> 00:54:12,780 would want to move away from rather than consolidating this 834 00:54:12,780 --> 00:54:16,320 dependency on the API for this information. And it seems like 835 00:54:16,320 --> 00:54:18,930 RSS hosts are increasingly adopting. 836 00:54:19,380 --> 00:54:25,170 So the, the whole concept of a shim is is exactly what the word 837 00:54:25,170 --> 00:54:30,030 means. It's just a temporary fix to because we were very 838 00:54:30,030 --> 00:54:33,180 skeptical about doing this at all, but we wanted to launch and 839 00:54:33,180 --> 00:54:37,140 get the get the value for value system running, which is very 840 00:54:37,140 --> 00:54:44,700 successful. It's 10,780 podcasts on reading here. So question 841 00:54:44,700 --> 00:54:52,920 number one is so I know you maintain your own database you 842 00:54:52,920 --> 00:54:55,980 read from your own database. What is exactly the reason 843 00:54:55,980 --> 00:54:58,470 behind because you're one of the few I think, who does that? 844 00:54:58,470 --> 00:55:03,060 Maybe I'm wrong, but it seems like You know, you're, like 845 00:55:03,060 --> 00:55:05,700 you're unique in in having your own database 846 00:55:06,509 --> 00:55:10,889 that does well, for a lot of the 2.0 apps. I think that's true. 847 00:55:11,069 --> 00:55:15,359 Well, I mean, we existed before 2.0 was even a thing. So we 848 00:55:15,359 --> 00:55:18,779 needed to have our own infrastructure for a podcast 849 00:55:18,779 --> 00:55:23,279 database. And we decided to keep it because just in case, there 850 00:55:23,279 --> 00:55:26,819 are other features that we want to support that potentially, the 851 00:55:26,819 --> 00:55:30,809 index doesn't support, and also just for resilience, I guess, 852 00:55:31,439 --> 00:55:34,559 and to be able to support ourselves, you know, in a self 853 00:55:34,559 --> 00:55:37,679 hosted way, if for whatever reason, the index wouldn't be 854 00:55:37,679 --> 00:55:42,899 available. So currently, we have our own standalone parsing RSS 855 00:55:42,899 --> 00:55:46,679 parsing system and database. But we also sync with the podcast 856 00:55:46,679 --> 00:55:53,009 index regularly to get feed update notifications, or if a 857 00:55:53,009 --> 00:55:57,389 new feed was added or deleted. So we sync continuously, 858 00:55:57,420 --> 00:56:02,370 but But you don't you don't you can't sync the the value block 859 00:56:02,370 --> 00:56:03,060 information. 860 00:56:03,659 --> 00:56:07,529 We could, it's definitely possible. It's just there's, for 861 00:56:07,529 --> 00:56:11,819 the episode, specifically, we do support podcast level. So to be 862 00:56:11,819 --> 00:56:17,369 clear, if it's in the if it uses podcasts or wallet, we provide 863 00:56:17,549 --> 00:56:20,669 the value tag information for the podcast level, we don't 864 00:56:20,669 --> 00:56:26,009 provide the episode. So show specific splits, we can do that 865 00:56:26,039 --> 00:56:27,929 it will be more work for us to do that. 866 00:56:28,949 --> 00:56:32,429 So hold on a second. So if if I put you guys in the value block, 867 00:56:32,429 --> 00:56:36,029 which I'm which of course we do with all of our guests, you will 868 00:56:36,029 --> 00:56:38,159 actually not get that if someone uses pod verse. 869 00:56:38,820 --> 00:56:43,380 If you have it in the RSS feed, which I think you do, of course, 870 00:56:43,380 --> 00:56:48,240 yes, then we do support it. We we have just prioritized native 871 00:56:48,330 --> 00:56:52,980 RSS support over the episode level API integration, it's 872 00:56:52,980 --> 00:56:57,060 entirely possible, it just either will require a much 873 00:56:57,060 --> 00:57:04,530 larger syncing operation, maybe on a daily basis, with the index 874 00:57:05,220 --> 00:57:10,680 for on the fly in an app, we make a request to podcasts index 875 00:57:10,680 --> 00:57:15,000 and say, you know, this person just tried to play this episode, 876 00:57:15,270 --> 00:57:19,710 before playing it grab the value information, which which is 877 00:57:19,710 --> 00:57:23,310 fine, but it's you know, it's it's more interaction that has 878 00:57:23,310 --> 00:57:26,580 to happen, potentially more waiting time for a network 879 00:57:26,580 --> 00:57:29,790 request. So it's not our preferred approach 880 00:57:30,000 --> 00:57:35,280 would it would have helped Mitch, if I published, if I just 881 00:57:35,280 --> 00:57:42,030 dumped all of that episode level data out into just a big, just a 882 00:57:42,030 --> 00:57:45,360 big file. And you know, just did it every, I don't know, five 883 00:57:45,360 --> 00:57:49,260 minutes or so. That was something, grab something once 884 00:57:49,260 --> 00:57:51,060 and not have to be, you know, polling 885 00:57:51,989 --> 00:57:55,349 yet that something like that could definitely help. Okay, 886 00:57:55,469 --> 00:57:59,009 it's a solvable problem on our end with the existing resources. 887 00:57:59,579 --> 00:58:03,239 I just like to nudge people towards being aware that these 888 00:58:03,239 --> 00:58:06,959 limitations exist. And this is part of the reason why you would 889 00:58:06,989 --> 00:58:10,139 want to prefer to have it in RSS. 890 00:58:12,179 --> 00:58:15,899 Ultimately, ultimately, we all want it to be an RSS, but that's 891 00:58:15,899 --> 00:58:18,749 just going to take another five years, I can tell you right now, 892 00:58:18,749 --> 00:58:21,839 it's just gonna take a while before everybody before 893 00:58:21,839 --> 00:58:25,259 everybody has that. That's just the nature of the beast. I think 894 00:58:25,290 --> 00:58:28,740 it's been so hard just to even get people to transfer. Yeah. 895 00:58:28,740 --> 00:58:29,160 Oh, yeah. 896 00:58:29,159 --> 00:58:32,549 It's been great now, Mitch, by the way, congratulations. With 897 00:58:32,549 --> 00:58:36,239 all of the releases, you've been doing all the bug fixes. OPO, 898 00:58:36,239 --> 00:58:39,659 OPML import works. Again, it's been fantastic. I'm on graphene 899 00:58:39,659 --> 00:58:43,439 OS which is an oddball thing. I'm still don't worry about it, 900 00:58:43,439 --> 00:58:46,739 I'm still having issues. From time to time it forgets that 901 00:58:46,769 --> 00:58:50,099 it's connected to the Albea wallet. I'm not sure what the 902 00:58:50,099 --> 00:58:54,839 problem is. But I wouldn't worry about it too much a live issue 903 00:58:54,839 --> 00:58:59,039 that is cropping up on lit. And it's weird, because you're the 904 00:58:59,039 --> 00:59:02,969 guy that that has all of these features that are so exciting. 905 00:59:02,969 --> 00:59:05,639 You've got notifications for when a show goes live on, you 906 00:59:05,639 --> 00:59:08,789 know, unplugging the heck out of pod verse. So of course I have a 907 00:59:08,789 --> 00:59:12,809 vested interest on asking about a couple things that are our 908 00:59:12,809 --> 00:59:18,689 little troublesome or that are bugs. And the big one is images. 909 00:59:19,049 --> 00:59:24,179 For lit. There seems to be some caching going on. And like when 910 00:59:24,179 --> 00:59:30,239 I if I do no agenda, and I do the lit hits the pod paying 911 00:59:30,239 --> 00:59:36,269 everything flows, it'll pop up. And I'll see on the live bot on 912 00:59:36,299 --> 00:59:39,029 Mastodon it will have the correct image but the 913 00:59:39,029 --> 00:59:45,719 notification and sometimes even the actual image on the on the 914 00:59:45,749 --> 00:59:49,559 live on the Live episode will be the older image. Is there a way 915 00:59:49,559 --> 00:59:51,989 I can bust that cache and there's something that I can do. 916 00:59:53,429 --> 00:59:58,949 It's difficult I'll have to look into that more the it there 917 00:59:58,949 --> 01:00:00,929 could be caching things that They're out of our control at 918 01:00:00,929 --> 01:00:06,299 the time that a feed is parsed and also when the user plays the 919 01:00:06,299 --> 01:00:08,189 show. So if they get a notification, they immediately 920 01:00:08,189 --> 01:00:11,819 press play, whatever image we have at that moment is going to 921 01:00:11,819 --> 01:00:16,379 hang around in the player and not correct itself. Magically, 922 01:00:16,589 --> 01:00:20,789 if unless, you know, but maybe 15 minutes later, we reparse and 923 01:00:20,789 --> 01:00:25,079 we get the correct image that can work, I will have to look 924 01:00:25,079 --> 01:00:30,779 into it more. And if this is like a finer, finer tuning, 925 01:00:31,319 --> 01:00:35,369 something we lack is maybe a good environment to run our own 926 01:00:35,369 --> 01:00:40,349 tests like this with to be able to reproduce the steps that the 927 01:00:40,349 --> 01:00:46,109 podcasters are using. So these sorts of bugs can can crop in 928 01:00:46,109 --> 01:00:48,659 there, because in my tests, it's working fine. But I'm doing a 929 01:00:48,659 --> 01:00:53,699 much more limited test, then. You know, in the case of no 930 01:00:53,699 --> 01:00:54,239 agenda. 931 01:00:57,660 --> 01:01:02,790 Alex, what what do you are you supporting live pod pings in 932 01:01:02,790 --> 01:01:03,570 peer tube yet? 933 01:01:05,520 --> 01:01:11,100 No, which is I know very ironic, supporting live, live episodes, 934 01:01:11,130 --> 01:01:14,430 live streams. But I've done all the work in general with 935 01:01:14,430 --> 01:01:16,200 ParaType is to allow that to happen. 936 01:01:17,279 --> 01:01:18,809 That's part of your RSS work. 937 01:01:20,190 --> 01:01:21,660 And part of the plugin work. 938 01:01:22,680 --> 01:01:25,650 Okay, I just wondered how you were planning on? Like, do you 939 01:01:25,650 --> 01:01:28,740 have a strategy for that for because caching is just always 940 01:01:28,800 --> 01:01:31,890 it is, you know, one of the fundamental issues? Do you kind 941 01:01:31,890 --> 01:01:34,020 of have a theoretical idea of how you're going to handle that 942 01:01:34,050 --> 01:01:35,070 with images and such. 943 01:01:35,100 --> 01:01:37,140 And I've already got, I've already got the handle. 944 01:01:37,950 --> 01:01:41,220 Basically, whenever the live state changes on a video live 945 01:01:41,220 --> 01:01:48,270 stream, I'm clearing the cache. It lives in the server side. So 946 01:01:48,300 --> 01:01:51,300 where are you what what kind of caching do you use? Is it behind 947 01:01:51,330 --> 01:01:52,020 a CDN 948 01:01:52,440 --> 01:01:56,520 now appear to be using a built in cache in memory cache? So 949 01:01:56,520 --> 01:01:58,650 basically, it doesn't have to recreate the RSS feed every 950 01:01:58,650 --> 01:02:03,810 request. So to me, Misha, it sounds like a race condition 951 01:02:03,990 --> 01:02:06,330 where you might be sending the notification before you finish 952 01:02:06,330 --> 01:02:06,900 parsing. 953 01:02:10,080 --> 01:02:14,190 Possibly, I think in the sequence of things, it's 954 01:02:14,190 --> 01:02:17,340 supposed to wait to send the notification until after that, 955 01:02:17,340 --> 01:02:20,400 but you know, there's lines of code for me to the way that 956 01:02:20,400 --> 01:02:21,000 we're all through 957 01:02:21,030 --> 01:02:26,310 the place, you can see it perfectly is in 100%, retro the 958 01:02:26,310 --> 01:02:30,360 live stream, which by the way, is phenomenal how it works. And 959 01:02:30,390 --> 01:02:34,710 Dave, thank you so much for coding up their their electronic 960 01:02:34,710 --> 01:02:38,610 programming guide. So I get about 10 lit notifications a 961 01:02:38,610 --> 01:02:42,030 day. And it's for the show, and it's always the wrong image. 962 01:02:42,030 --> 01:02:45,990 Sometimes it's the same image for several hours. So it's 963 01:02:46,020 --> 01:02:49,380 whatever in general, I know, this is a problem with podcast 964 01:02:49,380 --> 01:02:58,710 apps. I think podcast addicts. I mean, I see people who are who 965 01:02:58,710 --> 01:03:02,970 will tweet out an episode and it's an image from three months 966 01:03:02,970 --> 01:03:08,730 ago. I mean, there's even though it was in the spec to be able to 967 01:03:08,730 --> 01:03:13,980 have different channel level images, item level images, it 968 01:03:13,980 --> 01:03:16,470 really never got the attention that it should have. Because 969 01:03:16,470 --> 01:03:19,230 most people don't do that. But I think more people would do it, 970 01:03:19,410 --> 01:03:22,890 if they can see if they actually see the result of it changing on 971 01:03:22,890 --> 01:03:27,000 a regular basis. It's just it's a general issue. And any way we 972 01:03:27,000 --> 01:03:29,730 can resolve that would be great. It's just it's too bad because 973 01:03:29,730 --> 01:03:31,470 everything else works beautifully. 974 01:03:32,400 --> 01:03:35,340 Sure, I wasn't even aware that 100% Retro didn't always have 975 01:03:35,340 --> 01:03:39,570 the right image artwork. So that's a great test case that I 976 01:03:39,570 --> 01:03:39,930 can. 977 01:03:40,860 --> 01:03:42,960 Yeah, that's actually really good. Because it rolls like 978 01:03:42,960 --> 01:03:46,770 every two hours, but anything, any man, I'd be happy to do any 979 01:03:46,770 --> 01:03:49,380 any type of test anything that I can help with anytime. 980 01:03:50,070 --> 01:03:52,950 Tell me what you want. Mitch, I can always make adjustments to 981 01:03:52,950 --> 01:03:55,590 that feed generator, because it's real simplistic. So if you 982 01:03:55,590 --> 01:03:58,110 want me to test different, like cache busting, or whatever I 983 01:03:58,110 --> 01:03:59,970 can, maybe that will help you pinpoint where the issue 984 01:03:59,970 --> 01:04:05,850 is. Okay, if the image always has a different URL, I would 985 01:04:05,850 --> 01:04:11,520 expect us to always get the right image. So I doubt that 986 01:04:11,520 --> 01:04:15,960 100% Retro was using the same image URL and alternating the 987 01:04:16,050 --> 01:04:16,710 image. 988 01:04:16,980 --> 01:04:18,900 Well, they would know because they 989 01:04:19,139 --> 01:04:23,699 know it's not it's a different it's a different URL. Yeah, it's 990 01:04:23,699 --> 01:04:27,269 a different URL. But yeah, we'll work together on it. See if we 991 01:04:27,269 --> 01:04:27,869 can figure it out. 992 01:04:29,400 --> 01:04:34,290 Cool. Oh, 100% retro, by the way, it's great. Because it's 993 01:04:34,290 --> 01:04:37,200 like my sanity check. Because I'm subscribed to notifications 994 01:04:37,200 --> 01:04:40,470 for it. And late in the night, if I'm like, worried, how is our 995 01:04:40,500 --> 01:04:43,770 live stream still working? So can I see all these 996 01:04:43,770 --> 01:04:44,490 notifications? 997 01:04:44,520 --> 01:04:48,840 A little anecdote? No. So this is just a guy I know, from 100 998 01:04:48,840 --> 01:04:52,080 years ago, he's in Belgium, he's put all his own money into this. 999 01:04:52,080 --> 01:04:55,800 He has, you know, some investors and so now he's now he always 1000 01:04:55,800 --> 01:04:59,190 planned to go down the advertising route. So he's he's 1001 01:04:59,190 --> 01:05:03,000 finally a opened up advertising. And of course, a new stream 1002 01:05:03,000 --> 01:05:05,910 without any marketing, you know, these he's gonna have to do some 1003 01:05:05,910 --> 01:05:09,540 marketing to get people to listen. But just as an anecdote, 1004 01:05:09,930 --> 01:05:15,420 in the first month of him running with ads, he actually 1005 01:05:15,420 --> 01:05:19,320 made more money with value for value streaming. Even though 1006 01:05:19,320 --> 01:05:23,100 it's from me you I think Cleveland may boost it from time 1007 01:05:23,100 --> 01:05:27,090 to time Dave probably he actually made more money and it 1008 01:05:27,090 --> 01:05:30,210 was more exciting to everybody to see the money coming in. In 1009 01:05:30,210 --> 01:05:34,980 real time, he just got a an lb lb wallet hooked up to it, it 1010 01:05:34,980 --> 01:05:36,960 was really is really quite interesting to see that we're 1011 01:05:36,960 --> 01:05:40,860 shaking asked there. It's really nice. Speaking of which, of 1012 01:05:40,860 --> 01:05:43,800 kicking ass, Dave, if I may, just to interrupt the 1013 01:05:43,800 --> 01:05:50,250 conversation for a moment. Is it possible to hand off some of the 1014 01:05:50,250 --> 01:05:54,630 incoming stuff that you deal with? Because I saw your you 1015 01:05:54,630 --> 01:05:59,220 said, Hey, I actually spend more time with email with podcast 1016 01:05:59,250 --> 01:06:03,180 index than anything else. Is it possible to hand off something 1017 01:06:03,180 --> 01:06:07,590 so that I can help reparse a feed when someone hits I get the 1018 01:06:07,590 --> 01:06:09,990 same emails, but I really don't know what to do or how to help. 1019 01:06:09,990 --> 01:06:15,870 One is, I need you to remove this one. Because I'm now here. 1020 01:06:16,200 --> 01:06:20,490 The other one is, not all my episodes are showing up. Are 1021 01:06:20,490 --> 01:06:23,970 there things that you can hand off to me or and I'm really 1022 01:06:23,970 --> 01:06:27,600 available for that, or any other person so we can alleviate some 1023 01:06:27,600 --> 01:06:30,150 of that, because it's an incredible waste of your time. 1024 01:06:30,450 --> 01:06:34,290 And I I really, I'm happy to do anything. I mean, I can I can 1025 01:06:34,290 --> 01:06:37,950 perform commands, you know, just tell me what to do. And I can I 1026 01:06:37,950 --> 01:06:40,950 can make stuff happen. I seriously, I mean this, I hate 1027 01:06:40,950 --> 01:06:43,890 that you're bogged down by that. I mean, I was able to wrangle 1028 01:06:43,890 --> 01:06:46,440 the takedown notice out of your hands, like except that you 1029 01:06:46,440 --> 01:06:48,750 shouldn't be dealing with that crap. But he's more on let me do 1030 01:06:48,750 --> 01:06:49,080 that. 1031 01:06:49,620 --> 01:06:54,030 Man I appreciate it's just it's one of those things, like, you 1032 01:06:54,030 --> 01:06:58,080 know, like, with all projects like this, you have, you have, 1033 01:06:58,680 --> 01:07:03,450 you can solve the issue by writing the software that allows 1034 01:07:03,450 --> 01:07:07,440 people to help. But that requires hours and hours of work 1035 01:07:07,440 --> 01:07:10,770 to write the software to allow people to help. So it's just, 1036 01:07:10,860 --> 01:07:13,530 you know, you get in this catch 22, where you're like, Okay, do 1037 01:07:13,530 --> 01:07:16,560 you? Do you spend all this time writing the tool that's gonna 1038 01:07:16,560 --> 01:07:20,370 save you time later? Or do you just do the thing now and get on 1039 01:07:20,370 --> 01:07:23,880 with it? And so, I mean, at some point, I'll just have to buckle 1040 01:07:23,880 --> 01:07:26,130 down and solve this problem, which is kind of what I'm having 1041 01:07:26,130 --> 01:07:30,870 to do with the API at the moment. Because, you know, after 1042 01:07:30,870 --> 01:07:34,230 looking at what happened this morning, you know, it's it's 1043 01:07:34,230 --> 01:07:38,070 just, there's things, there's technical debt that goes back, 1044 01:07:38,100 --> 01:07:43,980 literally all the way to freedom controller, August of 2020. We 1045 01:07:43,980 --> 01:07:48,720 win, wait, you know, when I rolled the API in six weeks, 1046 01:07:48,750 --> 01:07:52,020 right, and so like, there's things that that I still have to 1047 01:07:52,020 --> 01:07:57,060 crawl out from under for that. And that's just, it's just kind 1048 01:07:57,060 --> 01:08:01,530 of it's time for that stuff to happen. So yeah, I mean, I'll, 1049 01:08:01,650 --> 01:08:07,140 yeah, it's solve that issue at some point. But I mean, 1050 01:08:07,889 --> 01:08:11,399 or how about this? How about this? How about when those 1051 01:08:11,399 --> 01:08:15,929 requests come in, we set up a process, where I make sure that 1052 01:08:15,929 --> 01:08:19,619 these people get a reply and tell them that it's in the queue 1053 01:08:19,649 --> 01:08:23,369 and will be on the way, and then you can just, you know, there's 1054 01:08:23,369 --> 01:08:26,159 a stack that comes in, and you can deal with it whenever you 1055 01:08:26,159 --> 01:08:30,629 want. I mean, anything to get you out of the out of the 1056 01:08:30,659 --> 01:08:33,989 squirrel moment of oh, yes. If someone wants this, Oh, someone 1057 01:08:33,989 --> 01:08:37,469 wants that, you know, just even if it's just to say, you know, 1058 01:08:37,499 --> 01:08:41,519 expect, expect your answer in 48 hours or whatever, you know, 1059 01:08:41,519 --> 01:08:42,809 something that we can do. It's just, 1060 01:08:43,230 --> 01:08:46,860 it's now I was grumpy because I just dug out of like, you know, 1061 01:08:46,860 --> 01:08:50,520 over 100 emails of having to go through there. So, but no, I 1062 01:08:50,520 --> 01:08:53,460 need I need Mitch his brother. That's who I need. I just need 1063 01:08:53,460 --> 01:08:55,440 to forward all my emails to Michel's brother. 1064 01:08:56,130 --> 01:08:58,020 Wait a minute, am I missing something here, 1065 01:08:58,170 --> 01:09:03,540 but my calendar helps, Kyle helps. With a lot of day to day 1066 01:09:03,540 --> 01:09:06,840 I throw basically all kinds of different tasks at him. We try 1067 01:09:06,840 --> 01:09:10,800 to respond to people within one to two business days. And most 1068 01:09:10,800 --> 01:09:14,160 of the requests we get through are for related to podcasts 1069 01:09:14,160 --> 01:09:18,870 request, either a feed is missing, or the feed hasn't been 1070 01:09:18,870 --> 01:09:22,680 parsed for recently for one reason or another. And those are 1071 01:09:22,680 --> 01:09:25,590 things we want to be able to respond to immediately. And 1072 01:09:25,590 --> 01:09:28,650 they're pretty easy to do. But you know, when I'm constantly 1073 01:09:28,650 --> 01:09:32,190 doing programming problems, it gets to be quite a burden to be 1074 01:09:32,400 --> 01:09:34,440 replying to all these. So I'm just 1075 01:09:34,439 --> 01:09:36,479 gonna have a T shirt that says talk to Kyle. 1076 01:09:38,220 --> 01:09:42,570 You correspond with him quite a bit. I don't know I could ask if 1077 01:09:42,570 --> 01:09:45,810 he's if his services are available to get a price. 1078 01:09:47,460 --> 01:09:49,710 I literally offered the same thing for free. 1079 01:09:52,020 --> 01:09:55,320 I think Dave needs a ticketing system and you have to find SLAs 1080 01:09:55,860 --> 01:10:02,190 SLAs we know the ticketing system. Alex's is you get an 1081 01:10:02,190 --> 01:10:05,370 auto reply that says, Here's your ticket number and then just 1082 01:10:05,370 --> 01:10:07,050 nothing ever happens. Please 1083 01:10:09,150 --> 01:10:11,730 get a ticket number I read the riot act to someone the other 1084 01:10:11,730 --> 01:10:12,210 day. 1085 01:10:12,840 --> 01:10:16,110 You did. Yeah, I'm in an email box like, hey, stop being rude. 1086 01:10:16,170 --> 01:10:19,650 Yeah, Dick, cuz you were like, Oh, looks like your feed is part 1087 01:10:19,680 --> 01:10:23,490 really Dave, who really are all the episodes in really? Have you 1088 01:10:23,490 --> 01:10:27,750 checked it out? Now I'm adding the emphasis of the voice that I 1089 01:10:27,750 --> 01:10:28,710 heard at the time, 1090 01:10:29,010 --> 01:10:32,250 he taursus slave level agreement SLA, 1091 01:10:32,310 --> 01:10:35,610 he did come back and said, Oh, man, I didn't know you guys were 1092 01:10:35,610 --> 01:10:39,240 just volunteers and I positioned at something like that. Oh, I'm 1093 01:10:39,240 --> 01:10:43,020 sorry about that. But in general, the attitude that 1094 01:10:43,020 --> 01:10:48,360 people have about how technology works sometimes gets me very, 1095 01:10:48,360 --> 01:10:52,560 very angry. And I had a very shitty experience and it was all 1096 01:10:52,560 --> 01:10:57,600 my fault. Where you know, the show that Tina and I do curry in 1097 01:10:57,600 --> 01:11:01,140 the keeper going to keep her.com Everybody, which is which we 1098 01:11:01,140 --> 01:11:04,740 only accept value for value through podcasting. 2.0. And of 1099 01:11:04,740 --> 01:11:07,170 course, people send us bottles of wine. So okay, well, Oh, 1100 01:11:07,170 --> 01:11:11,910 crap, we'll have to take that. But, you know, I've always said 1101 01:11:12,900 --> 01:11:16,110 they have to read the instructions that the app gives 1102 01:11:16,110 --> 01:11:21,660 them. And I could always tell by, you know, and so people will 1103 01:11:22,050 --> 01:11:25,320 message Tina on Instagram, there's a very unsophisticated 1104 01:11:25,320 --> 01:11:28,380 users. And they're like, Okay, we really want to do it, and 1105 01:11:28,380 --> 01:11:31,860 we're really motivated, but we can't figure it out. And I was 1106 01:11:31,860 --> 01:11:34,740 like, they have to read I can tell they're not reading and 1107 01:11:34,740 --> 01:11:38,850 people don't read. You'll never get them to read. But then I 1108 01:11:38,850 --> 01:11:42,090 said, Tina, why don't we sit down and we'll go through you 1109 01:11:42,090 --> 01:11:44,340 have not been through the process yourself. You have not 1110 01:11:44,340 --> 01:11:48,510 set up a podcast app bought Bitcoin, put it in figured out 1111 01:11:48,510 --> 01:11:53,190 how to get it onto lightning and and then actually boost to show 1112 01:11:53,250 --> 01:11:55,440 that she's okay. This is a good idea because it was it was 1113 01:11:55,650 --> 01:11:58,950 causing tension between us because I get all huffy, like, 1114 01:11:58,980 --> 01:12:01,710 oh, people don't read. They don't care. And they don't they 1115 01:12:01,710 --> 01:12:04,920 don't we just have to admit that. And so she's like, well, 1116 01:12:04,920 --> 01:12:08,130 you know, they don't understand they're just trying to help. So 1117 01:12:08,130 --> 01:12:14,130 we went through it. I was it was a ghastly experience, we have 1118 01:12:14,160 --> 01:12:19,050 zero, good me even get Alby if you say, Oh, just use get LB and 1119 01:12:19,050 --> 01:12:25,290 hook it up to pod verse, PA, there's no information flow is 1120 01:12:25,290 --> 01:12:30,150 just an IP sucks. And we need to create some kind of project 1121 01:12:30,180 --> 01:12:34,830 again, something I'll be happy to spearhead whether the apps do 1122 01:12:34,830 --> 01:12:38,700 it themselves, you know, I had a Oscar Mary came back and said, 1123 01:12:38,700 --> 01:12:41,070 Oh, you know, it's gonna be much easier in version six, I presume 1124 01:12:41,070 --> 01:12:44,190 they're going to integrate the Bitcoin purchase right in there. 1125 01:12:44,460 --> 01:12:48,030 But even you know, the idea of I was saying to people, oh, just 1126 01:12:48,030 --> 01:12:50,610 go to cash app, and then you cash app, you can transfer it 1127 01:12:50,610 --> 01:12:54,390 Well, dude, it took a little while to figure out how you can 1128 01:12:54,390 --> 01:12:57,780 actually do with cash app, there's no no explanation of 1129 01:12:57,780 --> 01:13:02,520 that. So we need overall, we need to make sure that we're at 1130 01:13:02,550 --> 01:13:07,500 it. I am just as guilty of thinking, hey, you know, you 1131 01:13:07,500 --> 01:13:09,810 just have to follow the instructions. There's no 1132 01:13:09,810 --> 01:13:13,170 instructions anywhere really, that are of any use to anybody. 1133 01:13:14,070 --> 01:13:16,110 How do we do this? Is this something that should be a 1134 01:13:16,110 --> 01:13:19,500 central point should be something on podcasts index that 1135 01:13:19,500 --> 01:13:22,710 we explain different ways to purchase Bitcoin different ways 1136 01:13:22,710 --> 01:13:25,350 to get it into the Lightning Network? Is that something the 1137 01:13:25,350 --> 01:13:29,550 apps will do can do, since I only have you here, Mitch? I 1138 01:13:29,550 --> 01:13:32,730 mean, do you feel that you have an adequate explanation of how 1139 01:13:32,730 --> 01:13:35,910 this works? Or do you kind of dump people off and get Alby and 1140 01:13:35,910 --> 01:13:40,260 rely on get lb to help people understand because get LB is, is 1141 01:13:40,290 --> 01:13:43,500 unless you're a podcaster. If you're just someone who wants to 1142 01:13:43,500 --> 01:13:47,490 hook it up to pod verse, there's some gaps in the steps. 1143 01:13:48,450 --> 01:13:54,330 I think with the process of just connecting your lb wallet, it's 1144 01:13:54,450 --> 01:13:58,710 pretty straightforward, but the big knowledge gap is creating an 1145 01:13:58,710 --> 01:14:04,230 LV account and loading it with Bitcoin. And big strides were 1146 01:14:04,230 --> 01:14:09,600 made this year around a few months ago. So Alby previously 1147 01:14:09,600 --> 01:14:15,210 only allowed you to send send using the Lightning Network to 1148 01:14:15,210 --> 01:14:20,640 send sets into it. And that I wrote a tutorial myself and it 1149 01:14:20,730 --> 01:14:24,540 turned into like, like five pages of like needing to use a 1150 01:14:24,540 --> 01:14:27,690 third party app intermediary like you go from your exchange, 1151 01:14:27,690 --> 01:14:30,150 you go to this third party app, you send your SATs here then you 1152 01:14:30,150 --> 01:14:33,270 send it to LB and it was a big, it was just way too complicated. 1153 01:14:33,750 --> 01:14:37,980 But they have added unchained deposits. So now you can go 1154 01:14:37,980 --> 01:14:44,130 directly from wherever you buy bitcoin, and just send just 1155 01:14:44,130 --> 01:14:48,600 withdraw directly to your lb account so there's no Lightning 1156 01:14:48,600 --> 01:14:51,960 Network intermediary needed to get the the exchange doesn't 1157 01:14:51,960 --> 01:14:54,240 even have to support the Lightning Network for you to 1158 01:14:54,240 --> 01:14:55,590 load your wallet with SATs. 1159 01:14:55,680 --> 01:14:58,710 Wait a minute, wait a minute, don't you have to hook up an app 1160 01:14:58,800 --> 01:15:01,920 to your Alby wallet first. 1161 01:15:03,120 --> 01:15:06,210 What I believe it'll give you one by default, I didn't have to 1162 01:15:06,240 --> 01:15:09,510 connect a node I just signed up for lb. And they gave me a 1163 01:15:09,660 --> 01:15:10,170 wallet. 1164 01:15:11,070 --> 01:15:17,190 That you can that you can. Oh, that's ending right now. That is 1165 01:15:17,190 --> 01:15:21,960 new. Okay. That's cool. All right. All right. Oh, okay. So 1166 01:15:21,960 --> 01:15:22,170 might 1167 01:15:22,170 --> 01:15:24,900 have been one of the earliest adopters and this that 1168 01:15:26,340 --> 01:15:29,850 I hadn't actually seen this, this screen because when I went 1169 01:15:29,910 --> 01:15:35,610 maybe three days ago, I went to Aldi and I said, Okay, I want to 1170 01:15:35,640 --> 01:15:38,940 I want to receive into the lb wallet, it said, Oh, you have to 1171 01:15:38,940 --> 01:15:43,680 get a get Zeus and connect it this way. That that that was 1172 01:15:43,680 --> 01:15:46,740 like, What I haven't seen this top up either. Okay, this is 1173 01:15:46,740 --> 01:15:49,590 good. I think I'm just gonna write some stuff. And it may be 1174 01:15:49,590 --> 01:15:52,320 people can use it as a template, because I understand that 1175 01:15:52,320 --> 01:15:54,240 everyone's kind of like, well, you know, you do it there. You 1176 01:15:54,240 --> 01:15:56,670 do it there. But then everyone has all these pieces, and they 1177 01:15:56,670 --> 01:16:00,000 don't quite connect. And it's, it's just, it's just a shame, 1178 01:16:00,000 --> 01:16:01,680 because we're so close to everything. 1179 01:16:02,190 --> 01:16:04,860 Let me say anything, anything crypto that has to go through 1180 01:16:04,860 --> 01:16:08,250 KYC. I mean, it's just across the board. I mean, it's always 1181 01:16:08,250 --> 01:16:08,910 going to be 1182 01:16:09,090 --> 01:16:12,270 I'm always I'm not even, I'm not even talking about it. Just we 1183 01:16:12,270 --> 01:16:16,260 need to tell people what's going to happen. And Cash App is the 1184 01:16:16,260 --> 01:16:19,980 worst. I mean, and this is a big corporation, this is a public 1185 01:16:19,980 --> 01:16:24,030 company. Let me just tell you how Cash App went. Okay, Tina 1186 01:16:24,030 --> 01:16:26,700 installed Cash App. Great. Congratulations, you have cash 1187 01:16:26,700 --> 01:16:30,720 app, now figure out how to buy bitcoin, Oh, hold on a second, 1188 01:16:30,720 --> 01:16:35,190 we need to approve you to go through a process. Good. You'll 1189 01:16:35,190 --> 01:16:39,210 be verified very soon. So she got verified within 30 minutes 1190 01:16:39,270 --> 01:16:42,480 and just kept saying, verified. Now, this is when she was 1191 01:16:42,480 --> 01:16:46,560 sending a payment. And so the first thing she thought was, oh, 1192 01:16:46,560 --> 01:16:49,920 I'm verified. So the payment was sent, right? No, of course not. 1193 01:16:49,920 --> 01:16:52,800 Of course, they don't send that just because they verify you, 1194 01:16:53,070 --> 01:16:56,850 then you want to send bitcoin, then they all hold on a second. 1195 01:16:56,850 --> 01:16:59,460 Now we need your driver's license, we need a picture of 1196 01:16:59,460 --> 01:17:03,570 you. So it's very scary to people when they don't know. And 1197 01:17:03,570 --> 01:17:06,330 Moon pay does the same thing. I think when they don't know 1198 01:17:06,330 --> 01:17:08,820 what's happening, it's like, you know, you see something called 1199 01:17:08,820 --> 01:17:11,940 Moon pay the fact I have to get my driver's license to moon pay, 1200 01:17:11,970 --> 01:17:16,350 you know, it's scary to people. So we need to have some legit, 1201 01:17:16,830 --> 01:17:20,460 right? Sounds like crap like Moon pay? No, what is this 1202 01:17:20,460 --> 01:17:25,200 Russian. So I'm going to start a I'll do it on the GitHub so 1203 01:17:25,200 --> 01:17:28,770 people can can contribute to it. So we can just write something 1204 01:17:28,770 --> 01:17:33,270 up. That that is general for everybody. And then we can pick 1205 01:17:33,270 --> 01:17:37,110 and choose integrate that into your own FAQs or whatever. And 1206 01:17:37,110 --> 01:17:41,340 again, a handle on my own heart here i I really thought it was 1207 01:17:41,340 --> 01:17:42,510 much better explained. 1208 01:17:43,440 --> 01:17:47,370 Well put part of the problem is been that what is required is 1209 01:17:47,370 --> 01:17:50,820 changed on an almost monthly basis. And things are evolving. 1210 01:17:50,820 --> 01:17:53,340 So if I write a tutorial from three months ago, yeah, there's 1211 01:17:53,340 --> 01:17:56,820 now a much easier process today than there was three months ago. 1212 01:17:57,150 --> 01:17:58,680 So we've been boring. 1213 01:17:59,610 --> 01:18:03,900 Or Mitch, honestly or harder, because I mean, the Cash App 1214 01:18:03,930 --> 01:18:06,840 didn't used to be that hard. And it's harder now than it was six 1215 01:18:06,840 --> 01:18:07,290 months ago. 1216 01:18:07,290 --> 01:18:10,350 Let me tell you the thing about cash app. So we've got all this 1217 01:18:10,350 --> 01:18:15,240 set. And then we're now we're going to copy the invoice to 1218 01:18:15,270 --> 01:18:18,930 fund the wallet. And I say oh, yeah, just you don't have to 1219 01:18:18,930 --> 01:18:22,470 scan it, just copy it there. You go to Cash App. And cash app 1220 01:18:22,470 --> 01:18:27,810 doesn't have a paste this code. It has only the scan. And I'm 1221 01:18:27,810 --> 01:18:31,170 like, I can't undo it. And then and then I we saw a video from 1222 01:18:31,170 --> 01:18:35,760 three months ago. Ah, you can paste the code, if you go into 1223 01:18:35,760 --> 01:18:39,630 it to back to the homepage of the app and click on Bitcoin, 1224 01:18:39,900 --> 01:18:43,200 but not, not if you go, and I think it's a bug on there and 1225 01:18:43,320 --> 01:18:47,100 not if you go to the pay screen, it doesn't have that option. So 1226 01:18:47,100 --> 01:18:51,390 there's so much going on. And ultimately, I mean, I'm even 1227 01:18:51,390 --> 01:18:54,630 looking at this Alby. And this is actually quite good. I mean, 1228 01:18:54,660 --> 01:18:57,960 anybody could use this, because you can buy it right there and 1229 01:18:57,960 --> 01:19:00,420 you have an enlightening and then you can fund a wallet with 1230 01:19:00,420 --> 01:19:03,300 it. And I'm actually thinking I'll be is, is a very good 1231 01:19:03,300 --> 01:19:04,620 onramp at this point. 1232 01:19:05,130 --> 01:19:08,010 Yeah, I kind of buried the lead when I said the on chain 1233 01:19:08,010 --> 01:19:11,160 deposits, because that was a step forward. But this new moon 1234 01:19:11,160 --> 01:19:15,360 pay integration. Yeah, you can use a credit card. I haven't 1235 01:19:15,360 --> 01:19:17,910 gone through the process. I guess there's some KYC Of 1236 01:19:17,910 --> 01:19:21,990 course, of course, of course. However, you just go to LB and 1237 01:19:21,990 --> 01:19:26,490 then your the whole process is there. Once you create a wallet, 1238 01:19:26,490 --> 01:19:29,370 you put you buy some SATs, you put it in it, then you open up 1239 01:19:29,520 --> 01:19:31,980 pod verse go to the value for values scream 1240 01:19:31,980 --> 01:19:35,700 the authentic. Yep. And I do that twice. I do that twice, 1241 01:19:35,730 --> 01:19:37,230 three times. That is 1242 01:19:37,230 --> 01:19:40,860 unfortunate. I think there might be a graphene OS related 1243 01:19:40,889 --> 01:19:45,989 100% 100% 100% Don't worry about it. I don't mind because all I 1244 01:19:45,989 --> 01:19:49,199 have to do is just hit the V for V again and then just connect 1245 01:19:49,199 --> 01:19:51,839 and then it works. And it remembers the amounts I put in 1246 01:19:51,839 --> 01:19:54,959 there just forgets the connection for some reason. I 1247 01:19:54,959 --> 01:19:55,589 don't know why. 1248 01:19:56,040 --> 01:19:59,190 Yeah, I have to look into that. That's some the token. 1249 01:19:59,489 --> 01:20:03,839 Could it be IE, perhaps my MAC address changes every single 1250 01:20:03,839 --> 01:20:06,029 time I connect to a different network. Is it one of those 1251 01:20:06,029 --> 01:20:08,849 security things that's screwing it up? That might be an Al B 1252 01:20:08,849 --> 01:20:09,419 question. 1253 01:20:10,500 --> 01:20:14,160 It would depend on what type of so right now the wallet will 1254 01:20:14,160 --> 01:20:19,170 auto disconnect in pod verse if it gets a unauthorized response. 1255 01:20:20,160 --> 01:20:24,360 Which makes me wonder if there is extra security happening. I 1256 01:20:24,360 --> 01:20:27,150 don't know what changing that. Honestly, if somehow I find 1257 01:20:27,150 --> 01:20:31,440 myself reconnecting to Alby in contracts in a browser, I have 1258 01:20:31,440 --> 01:20:38,010 to reconnect regularly with the Saturn stats. So it's probably 1259 01:20:38,010 --> 01:20:41,790 the I have too much security in my life. I'm running more 1260 01:20:41,790 --> 01:20:42,510 dangerously. 1261 01:20:42,900 --> 01:20:46,260 I'm running any graphing OS to Adam and I don't think I have 1262 01:20:46,260 --> 01:20:49,290 the issue. So it's for strange. 1263 01:20:50,370 --> 01:20:52,860 Your pod verse and graphene. Right, Alex? 1264 01:20:53,849 --> 01:20:57,089 Yeah, that's not my primary efficient just using 10 up. 1265 01:20:59,999 --> 01:21:01,619 Okay, but I'll give a shout out. 1266 01:21:01,950 --> 01:21:04,560 Yeah, yeah. I mean, it's it. I just don't want to bother Mitch, 1267 01:21:04,560 --> 01:21:06,720 if it's something that's completely on my side, you know, 1268 01:21:06,720 --> 01:21:08,490 so don't have to deal with that crap. 1269 01:21:09,120 --> 01:21:10,740 Now, you're an expert at breaking things. 1270 01:21:10,950 --> 01:21:16,770 I am so good, valuable service. Steel, a speaking of such, I 1271 01:21:16,770 --> 01:21:21,420 want to promote the value for value dot info. website, which 1272 01:21:21,660 --> 01:21:24,060 I've been trying to get it out there, but not a lot of 1273 01:21:24,060 --> 01:21:31,560 traction. It's, it explains what value for value is and how it 1274 01:21:31,560 --> 01:21:35,730 works in context of podcasting. 2.0. So I'm putting that in the 1275 01:21:35,730 --> 01:21:41,250 show notes. Pass it on, let people know. And we finally were 1276 01:21:41,250 --> 01:21:46,170 able to make HTTPS work with new podcast apps.com. 1277 01:21:46,769 --> 01:21:49,049 So is it is it we're new? Yeah. Yeah, of course. Now, 1278 01:21:49,380 --> 01:21:52,350 after I paid pay for, for certificate. 1279 01:21:54,450 --> 01:21:56,490 Oh, he had to pay for certificate? 1280 01:21:56,550 --> 01:22:00,360 Well, if you do it through DNS, simple. I mean, ultimately, you 1281 01:22:00,360 --> 01:22:03,900 wind up paying for something somewhere. I mean, yeah. Don't 1282 01:22:03,900 --> 01:22:06,450 worry about it. It's I'm happy. It worked. I didn't know that 1283 01:22:06,450 --> 01:22:09,300 was possible. And so that that was a big, that was a big win, 1284 01:22:09,330 --> 01:22:11,040 because I think that was breaking everywhere. 1285 01:22:11,970 --> 01:22:15,660 Hey, Alex, can you give me an update on what you're like and 1286 01:22:15,660 --> 01:22:21,720 where you're at with your managing have no agenda tubes, 1287 01:22:21,750 --> 01:22:26,070 like, I guess I want I want to say moderation. But that's not 1288 01:22:26,610 --> 01:22:29,250 really what I'm talking about. You did a bunch of cleanup and 1289 01:22:29,250 --> 01:22:31,410 got rid of a bunch of crap accounts and that kind of thing. 1290 01:22:31,410 --> 01:22:35,190 But then also, like, what, how do you manage in general, the 1291 01:22:35,190 --> 01:22:38,460 comments section and all that stuff? I mean, like, what, what 1292 01:22:38,460 --> 01:22:39,330 do you do there? 1293 01:22:41,070 --> 01:22:46,470 Yeah, so basically closed open registration. Because the most 1294 01:22:46,470 --> 01:22:50,820 of the signups after the initial kind of announcement, but his 1295 01:22:50,820 --> 01:22:54,360 bot accounts like linking to looking outside of the site. So 1296 01:22:54,870 --> 01:23:01,650 I ended up cleaning up like maybe 30% of the accounts. So 1297 01:23:01,860 --> 01:23:06,480 that was fine. And then as far as comments, I don't there's 1298 01:23:06,480 --> 01:23:10,620 not, there's not a ton of comments. But it goes in line 1299 01:23:10,620 --> 01:23:15,450 with the traditional, I believe the traditional activity pub 1300 01:23:15,450 --> 01:23:20,580 reporting mechanism. So if someone reports a common ocular 1301 01:23:20,580 --> 01:23:26,250 notification, and I cannot act upon it there, I can either 1302 01:23:26,730 --> 01:23:30,720 ignore it, or I can, you know, delete the comment from no 1303 01:23:30,720 --> 01:23:34,620 agenda to I can't delete the comment because I don't have 1304 01:23:34,620 --> 01:23:37,470 access to other people's servers. I can also block 1305 01:23:37,470 --> 01:23:40,560 domains. So I mean, it's just like you'd see a mess. I think. 1306 01:23:41,820 --> 01:23:45,330 Oh, speaking of we got we got Fetty blocked hashtag Fetty 1307 01:23:45,330 --> 01:23:49,620 blocked on pasture podcasting index dot social, for the for 1308 01:23:49,620 --> 01:23:52,710 being, quote, libertarian and crypto. 1309 01:23:52,740 --> 01:23:56,130 Who who did that? I don't know. How do you know how do you know 1310 01:23:56,130 --> 01:23:58,140 we got blocked gooery posted 1311 01:23:58,140 --> 01:24:00,960 a screenshot from some other incidents that blocked us. 1312 01:24:01,830 --> 01:24:06,480 Hashtag city block. And the reason libertarian slash crypto. 1313 01:24:10,260 --> 01:24:15,330 That really sums everything up. Well, that's whatever you 1314 01:24:15,360 --> 01:24:18,180 whatever you're doing, Alex, I want to do that, too. I mean, I 1315 01:24:18,180 --> 01:24:20,820 think I think I just want to close. I think I just want to 1316 01:24:20,820 --> 01:24:23,880 close registration. I mean, do people have to email you to do 1317 01:24:23,880 --> 01:24:26,190 it? Or do you have some sort of trickery that they have to run 1318 01:24:26,190 --> 01:24:30,630 through? What are you doing? To register? Yeah, to get an 1319 01:24:30,630 --> 01:24:31,020 account? 1320 01:24:31,230 --> 01:24:34,020 Yeah, right. Now they would have to contact me with an email 1321 01:24:34,020 --> 01:24:35,700 address and create their own account. 1322 01:24:36,540 --> 01:24:40,290 Okay, because I think that's the way I'm going because the open 1323 01:24:40,290 --> 01:24:45,000 signup is just I feel like it's a losing battle. I feel like 1324 01:24:45,000 --> 01:24:48,660 didn't No matter what I do, there's going to be some bot 1325 01:24:48,660 --> 01:24:50,490 tree out there. They can defeat it. 1326 01:24:51,210 --> 01:24:55,830 I also have sign in with no agenda social, which just uses 1327 01:24:55,830 --> 01:24:56,370 OAuth. 1328 01:24:57,630 --> 01:25:00,420 Oh, no, you can that's basically how comments are work, 1329 01:25:01,080 --> 01:25:04,980 right? It's not the same thing with peer to peer. But yeah, 1330 01:25:04,980 --> 01:25:07,920 that's, that's a good flow if, if you want someone to sign and 1331 01:25:07,920 --> 01:25:11,100 it was like, you could you could assign on GitHub for if you 1332 01:25:11,100 --> 01:25:11,880 want. So, 1333 01:25:12,120 --> 01:25:15,240 so if, okay, so now since you're here, we're talking about no 1334 01:25:15,240 --> 01:25:22,590 agenda to, if I wanted to ask Mo, for mo facts, to start using 1335 01:25:22,590 --> 01:25:27,840 no agenda tube, what are the pieces he needs? And what is 1336 01:25:27,840 --> 01:25:33,510 missing? Or what do what do we need to do? Because the 1337 01:25:33,510 --> 01:25:38,670 disconnect I'm seeing is, well, one he would need, he can send 1338 01:25:38,670 --> 01:25:44,010 an RTP s stream, which I know that works, I've done that, then 1339 01:25:44,010 --> 01:25:48,450 what comes out, you have your own RSS feed. So that will be 1340 01:25:48,450 --> 01:25:51,300 separate from the RSS feed we already use. 1341 01:25:53,610 --> 01:25:57,900 Yeah, although you could take that item and put it in yours if 1342 01:25:57,900 --> 01:25:58,290 you want. 1343 01:25:59,880 --> 01:26:03,300 Right, but that would be that would require manual 1344 01:26:03,300 --> 01:26:04,140 intervention. 1345 01:26:05,220 --> 01:26:06,570 Or a script? Yep. 1346 01:26:06,660 --> 01:26:09,120 Is there something that you're that you're thinking about in 1347 01:26:09,120 --> 01:26:11,250 that way? I mean, obviously, want to keep your, your your 1348 01:26:11,250 --> 01:26:15,120 split in there. And all that working? is just how do we, you 1349 01:26:15,120 --> 01:26:20,130 know, we have our RSS feed, we want to have a user lit tag, we 1350 01:26:20,130 --> 01:26:23,700 want to go lit when people to pop up there, what is the best 1351 01:26:23,700 --> 01:26:24,690 way to do that. 1352 01:26:27,390 --> 01:26:31,020 So what I'm working on is targeting people who want to 1353 01:26:31,020 --> 01:26:34,080 stand up their own peer tube instances and use it as their as 1354 01:26:34,080 --> 01:26:40,170 their feed. Okay, yeah, kind of like, I want people to be able 1355 01:26:40,170 --> 01:26:44,910 to replace YouTube or Twitch, and not have to know how to host 1356 01:26:44,910 --> 01:26:52,680 an RSS feed. I mean, you saw, there's two ways you could do 1357 01:26:52,680 --> 01:26:57,150 it, you could have a permanent live stream. And just put that 1358 01:26:57,150 --> 01:26:59,910 in your feed and keep it there forever, just like you do with 1359 01:26:59,910 --> 01:27:04,350 icecast or more, or whatever you do for your mp3 stream, but no 1360 01:27:04,350 --> 01:27:07,680 dentistry. That would work. 1361 01:27:08,970 --> 01:27:13,740 Otherwise, so that would just be our own our own video server 1362 01:27:13,770 --> 01:27:14,460 basically. 1363 01:27:16,440 --> 01:27:19,950 Well, if you want to just know, genitive, it would be a put your 1364 01:27:19,950 --> 01:27:24,690 your live stream no agenda to your own there. 1365 01:27:25,080 --> 01:27:27,570 Okay, but then you don't necessarily get your split, 1366 01:27:27,750 --> 01:27:29,400 unless we put it in specifically. 1367 01:27:29,790 --> 01:27:33,150 Right, you'd have to add that. Okay. Which I mean, that's the 1368 01:27:33,150 --> 01:27:36,660 case with any external links and RSS feeds. I don't think that 1369 01:27:36,660 --> 01:27:42,720 gets all that problem. Okay, so we are working, there's a 1370 01:27:42,720 --> 01:27:45,300 camera, his name, there's someone working on a lightning 1371 01:27:45,810 --> 01:27:50,310 plugin for peer tube. And what I want to do is, hook in with 1372 01:27:50,310 --> 01:27:54,870 that, so I can put the value block into the feed too. But 1373 01:27:54,870 --> 01:27:58,050 then, I still you'd still have to have some kind of script to 1374 01:27:58,050 --> 01:27:58,680 pull it in. 1375 01:27:59,040 --> 01:28:03,030 And Mitch to you. Does pod verse do video? We'll do that kind of 1376 01:28:03,030 --> 01:28:04,050 video. I should say. 1377 01:28:04,649 --> 01:28:09,569 We do support video. I don't I'm not aware of any live streaming 1378 01:28:09,629 --> 01:28:15,269 video podcasts unless maybe Todd Cochran is has done one. We have 1379 01:28:15,269 --> 01:28:19,829 a limitation currently, which is we don't support HLS video 1380 01:28:19,829 --> 01:28:23,369 streams. Alex is well aware of this. He's the one who told me 1381 01:28:23,369 --> 01:28:23,759 about it. 1382 01:28:24,780 --> 01:28:27,630 Everything you dropped everything but HLS. Right, Alex? 1383 01:28:28,649 --> 01:28:32,939 Yeah, basically, the way peer tube works, I cut my storage in 1384 01:28:32,939 --> 01:28:37,739 half. Most supporting HLS right now it caught my paying 1385 01:28:37,859 --> 01:28:38,969 significantly less. 1386 01:28:40,439 --> 01:28:44,489 Yeah. And the good news on our end is that over the holiday 1387 01:28:44,489 --> 01:28:48,209 break, I created a branch for the mobile app where I'm 1388 01:28:48,239 --> 01:28:52,169 upgrading our video and audio library. It was a big, big 1389 01:28:52,169 --> 01:28:54,749 undertaking, and we need to do a lot of testing this is gonna be 1390 01:28:54,749 --> 01:28:58,799 a longer because yeah, if if the audio player or video player 1391 01:28:58,799 --> 01:29:02,609 have issues, that's the whole app. So we're going to I've been 1392 01:29:02,609 --> 01:29:06,869 delaying the release into beta until we have like a feel good 1393 01:29:06,869 --> 01:29:10,109 about our stable, you know, our version that we have live that 1394 01:29:10,109 --> 01:29:14,579 will beta test deeply for a couple of weeks. all goes well, 1395 01:29:14,579 --> 01:29:17,729 then we should be able to support HLS video pretty soon. 1396 01:29:18,420 --> 01:29:26,220 Killer. That's awesome. In your how health? how responsive has 1397 01:29:26,250 --> 01:29:30,330 appeared to been to your upstreaming in on all that. Do 1398 01:29:30,330 --> 01:29:32,460 you think that's gonna go pretty well, Alex? 1399 01:29:33,690 --> 01:29:36,750 Yeah, I can work on that this weekend. Obviously, they wanted 1400 01:29:36,750 --> 01:29:41,010 some changes. It's always it's always more difficult to work 1401 01:29:41,010 --> 01:29:44,700 with someone else's software than your own because you it's 1402 01:29:44,700 --> 01:29:49,260 as much politics as is developed. Yes, it is. I think 1403 01:29:49,260 --> 01:29:52,410 they're open to it. And I think some of the people understand 1404 01:29:52,410 --> 01:29:58,170 that. Having an RSS feed is very beneficial. So um, there are 1405 01:29:58,170 --> 01:30:03,240 many users asking for it. So, yeah, I think it's going well. 1406 01:30:05,339 --> 01:30:08,879 May I suggest we thank a few people. Now that were a buck 30 1407 01:30:08,879 --> 01:30:14,039 into this yet, let's go. We've had some. We've had quite a 1408 01:30:14,039 --> 01:30:18,959 number actually. Quite a number of live booths coming in. We'll 1409 01:30:18,959 --> 01:30:23,789 start with Mike Newman. The most recent 123,456 1410 01:30:25,080 --> 01:30:28,920 shot caller 20 blades on him Paula. 1411 01:30:29,610 --> 01:30:33,660 I think anything over 100,000 Is that Is that a big baller every 1412 01:30:33,660 --> 01:30:36,840 100,000 Plus we're gonna have to up the ante here on what's 1413 01:30:39,360 --> 01:30:43,170 down the ante with with the Martin. Way prices are 1414 01:30:44,550 --> 01:30:46,920 great hearing a full board boardroom to start the new year 1415 01:30:46,920 --> 01:30:50,130 today I'm creating I'm streaming with curio caster and boosting 1416 01:30:50,130 --> 01:30:54,360 from pod verse small right. Cheers. Wow, cheers to a 1417 01:30:54,360 --> 01:30:58,680 productive and collaborative 2023 for the PC to o community. 1418 01:30:58,710 --> 01:31:02,370 All right, Mike. Thank you very much. 10,000 SATs from Sam Sethi 1419 01:31:02,370 --> 01:31:06,480 again. Who says my lightning address Sam had Get out b.com is 1420 01:31:06,480 --> 01:31:09,270 also my noster account. Oh yeah, we haven't even talked about 1421 01:31:09,270 --> 01:31:13,140 that thank God as lb hold my public and private keys could 1422 01:31:13,140 --> 01:31:15,690 well be also integrate to Mastodon the same way. So I 1423 01:31:15,690 --> 01:31:18,480 could use my lightning address to post to Mastodon the same way 1424 01:31:18,480 --> 01:31:23,460 I can today with noster to any relay that I'm logged into. Who 1425 01:31:23,490 --> 01:31:25,290 I don't know Alex yes or no. 1426 01:31:27,300 --> 01:31:28,560 Sorry. Can you repeat the question? 1427 01:31:28,980 --> 01:31:32,370 I don't understand the question. So it's lightning and he's he 1428 01:31:32,370 --> 01:31:35,580 has a lightning address. It's Sam and get alby.com. It's also 1429 01:31:35,580 --> 01:31:38,490 his Nasr. Public Key. I guess that's what he says when he says 1430 01:31:38,520 --> 01:31:42,360 my noster account. Yeah, so if you use his public and private 1431 01:31:42,360 --> 01:31:46,740 keys for that could Alby also integrate into Mastodon in the 1432 01:31:46,740 --> 01:31:49,500 same way, so I could use my lightning address to post a 1433 01:31:49,500 --> 01:31:53,100 Macedon? I don't know if that's possible. I think so. 1434 01:31:53,460 --> 01:31:59,370 That's a difference between identity and service. So no, I 1435 01:31:59,370 --> 01:32:02,490 mean, you could log in with it. Maybe if they supported that. 1436 01:32:03,180 --> 01:32:05,970 Okay, I don't think it does. They would have to, they would 1437 01:32:05,970 --> 01:32:07,590 have to run a message on service. 1438 01:32:08,490 --> 01:32:14,190 Okay. Martin, Linda's cog row of short row of ducks. He says, 1439 01:32:14,190 --> 01:32:16,830 Hey, thanks for going for the flow for the user of a pod 1440 01:32:16,920 --> 01:32:20,010 catcher and listener to a podcast I think he means for the 1441 01:32:20,010 --> 01:32:24,090 comments. There Sam Sethi again, which we talked about with his 1442 01:32:24,090 --> 01:32:30,870 super project. Pod fans. That's the 10,000 SATs 33,333 from 1443 01:32:30,870 --> 01:32:38,820 cotton gin. Happy New Year go podcast podcast. 20,023 from 1444 01:32:38,820 --> 01:32:42,660 last stock Calavera first boost for the New Year from my own 1445 01:32:42,660 --> 01:32:46,950 node. Congratulations you full node owner you here's my two 1446 01:32:46,950 --> 01:32:50,760 saps on cross app comments fine for live stuff. But boost should 1447 01:32:50,760 --> 01:32:53,670 be the main mechanism for regular releases. I like 1448 01:32:53,670 --> 01:32:57,030 chapters I like boosts I'm not wanting I'm not wanting for 1449 01:32:57,030 --> 01:33:00,420 comments. I am curious to see how the value tag evolves this 1450 01:33:00,420 --> 01:33:04,050 year. Could a big player like Venmo get involved? They could 1451 01:33:04,050 --> 01:33:07,440 do Fiat but they also buy and sell Bitcoin and shit coins to 1452 01:33:07,440 --> 01:33:09,870 their users. Maybe it will be possible for someone to use a 1453 01:33:09,870 --> 01:33:14,700 service like that and bring it mainstream there's a lot there. 1454 01:33:15,960 --> 01:33:20,460 So I mean, that's your that's a personal preference. About boost 1455 01:33:20,460 --> 01:33:22,950 versus comments. I think we we kind of went through that I 1456 01:33:22,950 --> 01:33:25,260 think we have some consensus on that and how that could be 1457 01:33:25,800 --> 01:33:30,120 integrated but clearly separate. And yeah, any player can get 1458 01:33:30,120 --> 01:33:35,370 into this the spec is open so I don't see why not the problem is 1459 01:33:35,400 --> 01:33:40,440 typically with Fiat systems that they don't do very well at small 1460 01:33:40,440 --> 01:33:45,540 amounts for transactions. Then he comments 1461 01:33:46,470 --> 01:33:52,020 for the idea that booster grams and comments are separate. I 1462 01:33:52,020 --> 01:33:54,450 don't think it from a user experience they have to be all 1463 01:33:54,450 --> 01:33:58,380 that separate. If you look at YouTube live streams today they 1464 01:33:58,380 --> 01:34:03,390 have a chat and the super chats which are paid comments appear 1465 01:34:03,390 --> 01:34:07,710 within the chat they just have you know a value next to them. I 1466 01:34:07,710 --> 01:34:12,360 think a comparable experience is possible with booster grams and 1467 01:34:12,360 --> 01:34:12,810 process. 1468 01:34:12,960 --> 01:34:16,170 I look forward to it Mitch, you know me I'll be the one 1469 01:34:16,200 --> 01:34:19,260 promoting it and breaking it at the same time. I'm very happy to 1470 01:34:19,260 --> 01:34:22,560 try that. Big players Yeah, big players are already getting into 1471 01:34:22,560 --> 01:34:26,280 the to the to the value space, which in general is good as long 1472 01:34:26,280 --> 01:34:31,380 as you know they can adhere to the way it works, I guess. I 1473 01:34:31,380 --> 01:34:33,750 mean, that seems to be an open I don't know if we have time to go 1474 01:34:33,750 --> 01:34:35,730 into that. Dave, if you want to comment on that. 1475 01:34:37,110 --> 01:34:39,960 The moment on which specific though it's like Venmo 1476 01:34:41,010 --> 01:34:42,690 or anybody coming in, I guess. 1477 01:34:43,649 --> 01:34:47,129 I don't know. I don't I don't know. That's just that's not 1478 01:34:47,129 --> 01:34:51,779 really I hate to say that I don't care. I guess because I 1479 01:34:51,779 --> 01:34:54,449 mean anytime some big player does something it has the 1480 01:34:54,539 --> 01:34:58,469 potential to you know, make waves and do all this stuff for 1481 01:34:58,469 --> 01:35:01,529 good and bad I guess but I just I don't know that I'm just not 1482 01:35:01,529 --> 01:35:05,909 focused on that. I mean, like that, to me, the, the, to me, 1483 01:35:05,909 --> 01:35:10,469 what matters is that you're able to do things direct, directly, 1484 01:35:10,769 --> 01:35:15,479 peer to peer. I mean, and, and I don't think we I think so much 1485 01:35:15,479 --> 01:35:19,499 of so much of everything that we do today is built in these on 1486 01:35:19,499 --> 01:35:22,919 these big platforms that I just want to minimize that. I mean, 1487 01:35:22,919 --> 01:35:27,089 you can't get to be realistic and say, Well, you can't ever 1488 01:35:27,089 --> 01:35:30,659 completely get away from it. Maybe but I don't know. I just, 1489 01:35:30,899 --> 01:35:33,929 um, through caring about what about what the big players are 1490 01:35:33,929 --> 01:35:34,349 doing? 1491 01:35:34,380 --> 01:35:41,970 No. There you go. I'm not implementing I'm excited. 33 333 1492 01:35:41,970 --> 01:35:45,300 from Eric P. P. Pew pew. He says thank you very much, Eric. 1493 01:35:45,300 --> 01:35:48,900 Appreciate it. The 6969 from a citizen fountain is great and 1494 01:35:48,900 --> 01:35:52,170 all but it's absolutely proprietary software sent to you 1495 01:35:52,170 --> 01:35:59,250 from pod verse powered by get Alby. Okay. Wow, that's an odd 1496 01:35:59,250 --> 01:35:59,640 one. 1497 01:36:00,810 --> 01:36:05,730 Well, thank you. Yeah, we are free and open source software. 1498 01:36:05,820 --> 01:36:09,360 And, you know, we love that some people appreciate that. 1499 01:36:09,750 --> 01:36:15,240 10,000 from Borlaug. Thank you. 17,776 from blueberry a big 1500 01:36:15,240 --> 01:36:17,820 freedom boost excited for this one. Mitch has come to chew 1501 01:36:17,820 --> 01:36:21,600 bubblegum and kick ass and he's all out of bubblegum. Go 1502 01:36:21,600 --> 01:36:27,780 podcast. Martin Linda cog. Linda's cog. Also very happy to 1503 01:36:27,780 --> 01:36:35,010 hear Mitch his voice 1776 And we have 1999 from the tone record, 1504 01:36:35,010 --> 01:36:38,490 please explain the Pugh sound trigger setup or share link 1505 01:36:38,490 --> 01:36:42,390 slash INFO. Looking to implement one here with music specific 1506 01:36:42,390 --> 01:36:47,490 boosts a sounds for boosts 808 SATs for triggers. Oh, he's got 1507 01:36:47,490 --> 01:36:50,490 a whole bunch of different tech. Well talk to blueberry about 1508 01:36:50,490 --> 01:36:54,000 that. And Sir Spencer and those guys because they've set all 1509 01:36:54,000 --> 01:36:57,750 that up. I'm not even sure how it works. We do have the pew pew 1510 01:36:57,750 --> 01:37:04,110 sound this one is in heli pad. Which I have been going through 1511 01:37:04,110 --> 01:37:09,120 my old domains or my hundreds of domains and trying to reduce 1512 01:37:09,150 --> 01:37:12,000 some. Some of these are pretty expensive. It turns out if it's 1513 01:37:12,000 --> 01:37:19,560 not a.com And we have heli pad dot cloud still do. Does anyone 1514 01:37:19,770 --> 01:37:23,130 know that? Yeah, it actually it points. It points to the GitHub 1515 01:37:23,130 --> 01:37:26,910 for helipad. The helipad is still a great program. I mean, I 1516 01:37:26,910 --> 01:37:31,680 use it every single time I'm doing stuff with the show. I 1517 01:37:31,680 --> 01:37:34,260 know it's like it might have dropped off everyone's radar for 1518 01:37:34,260 --> 01:37:36,960 a bit. But man, it's a great great little program 1519 01:37:36,960 --> 01:37:41,130 particularly for live stuff. And, and I see Todd Cochran is 1520 01:37:41,130 --> 01:37:45,960 next with 125,000 SATs, Todd Bala 1521 01:37:45,990 --> 01:37:49,830 Sakala. 20 is blades only Impala. 1522 01:37:49,890 --> 01:37:57,600 And Todd is using the lb related Saturn live view of the package. 1523 01:37:57,930 --> 01:38:02,250 Todd, I would say if you can get heli pad running, it only goes 1524 01:38:02,250 --> 01:38:06,000 off with boosts. Because I was listening to the live stream 1525 01:38:06,000 --> 01:38:08,250 from NAB. I think that's where they're at this week. And he's 1526 01:38:08,250 --> 01:38:13,140 doing a nine hour live stream. And so I'm listening and I'm 1527 01:38:13,140 --> 01:38:15,480 sending 200 SATs a minute. That's my standard. 1528 01:38:16,649 --> 01:38:18,509 And I'm a data controller. Okay, 1529 01:38:18,540 --> 01:38:22,710 I keep hearing every minute what it was like blooming, whatever 1530 01:38:22,710 --> 01:38:26,610 that sound is from, from Alby. We're, like oh, man, I should 1531 01:38:26,610 --> 01:38:30,270 stop sending the money, because it's annoying now. It's 1532 01:38:30,270 --> 01:38:32,310 like a 70s game show. Yes, 1533 01:38:32,310 --> 01:38:37,020 it does. So helipad is still a fantastic piece of software. If 1534 01:38:37,020 --> 01:38:40,980 you have Umbral, then it's right there in the in the store. I 1535 01:38:40,980 --> 01:38:44,520 love it. I think it works great. I use it to export my booster 1536 01:38:44,520 --> 01:38:47,460 grams from so I just wanted to make sure that everyone knows 1537 01:38:47,580 --> 01:38:51,030 heli pad dot cloud $50 a year but I'm happy to keep using it. 1538 01:38:51,630 --> 01:38:54,720 And Todd says hey guys, blueberry is really close and 1539 01:38:54,720 --> 01:38:59,040 releasing a bunch of podcasting 2.0 features. We'll be doing 1540 01:38:59,040 --> 01:39:02,160 final testing on our dashboard next week. Then we work on power 1541 01:39:02,160 --> 01:39:07,800 press. Go podcasting. Yeah, Podcast. I'm very excited about 1542 01:39:07,800 --> 01:39:12,720 that, Todd. So happy to see you jump in. And we had to pull you 1543 01:39:12,720 --> 01:39:16,140 in. We had to take your clothes off. We had to put your bathing 1544 01:39:16,140 --> 01:39:19,830 cap on but you're in in the deep end. We love that 1545 01:39:20,130 --> 01:39:21,300 and know where you're going with that. 1546 01:39:22,259 --> 01:39:26,789 It's true. Let me see. I think those are what No, I have a 1547 01:39:26,789 --> 01:39:32,879 couple more and other breweries. 1776. Thank you very much. Do I 1548 01:39:32,879 --> 01:39:36,149 have anything else here? Well, then I have the delimiter which 1549 01:39:36,179 --> 01:39:39,509 means it's time to hit it over to you Dave. So what do you 1550 01:39:39,509 --> 01:39:40,049 have? 1551 01:39:41,460 --> 01:39:46,350 We got a we have a pate. We have a Pay Pal. One Pay Pal this week 1552 01:39:46,380 --> 01:39:51,150 from blueberry $150 Whoa, whoa, 1553 01:39:51,150 --> 01:39:53,400 hold on a second. It's a baller. 1554 01:39:54,960 --> 01:39:56,940 Play on the Impala. 1555 01:39:56,970 --> 01:39:59,070 Does he already have a coveted t shirt? 1556 01:40:00,000 --> 01:40:04,380 No he does not but I will be I will be glad to send Todd and 1557 01:40:05,400 --> 01:40:05,940 Mike 1558 01:40:06,270 --> 01:40:08,760 cinnabar T shirts if they will make sure you let us know guys. 1559 01:40:09,360 --> 01:40:12,840 Yeah, thank you very there was no note. So I guess I guess the 1560 01:40:12,840 --> 01:40:16,590 boost was the note. Okay, the we got some histograms though. 1561 01:40:16,800 --> 01:40:23,430 We'll see. Blueberry row 611 111 through pod Verse eight says 1562 01:40:23,430 --> 01:40:24,300 keep it skanky. 1563 01:40:24,929 --> 01:40:27,179 That's also known as a satchel of Richard. 1564 01:40:27,899 --> 01:40:31,589 Oh, okay. All right. What does this term mean satchel of 1565 01:40:31,589 --> 01:40:32,279 Richard Well, 1566 01:40:32,309 --> 01:40:39,659 that's the British for bag of dicks. 1111 is a statue of 1567 01:40:39,659 --> 01:40:41,969 Richard it's the polite way to say it. 1568 01:40:42,570 --> 01:40:44,790 Okay, this in company in polite company 1569 01:40:45,030 --> 01:40:49,080 came up the other day. Like, oh, okay, I got you. Okay 1570 01:40:49,110 --> 01:40:53,640 in for VX 3333 through curio castering He says PC 2.0 To the 1571 01:40:53,640 --> 01:40:55,350 moon 2023 and beyond. 1572 01:40:55,860 --> 01:40:59,400 Thank you. Is that a boost? Or as a boost? Yes. 808 I'm 1573 01:40:59,400 --> 01:41:03,660 guessing no. 33330 That's different usually does. 808 All 1574 01:41:03,660 --> 01:41:04,380 right. Thank you. 1575 01:41:05,189 --> 01:41:09,059 Martin lenscoat He says it's a roadex tu tu tu tu and he says 1576 01:41:09,059 --> 01:41:12,179 cheers. What do you drink? James? You should drink tea. 1577 01:41:12,239 --> 01:41:13,589 Martin, Linda Scott. All right. 1578 01:41:14,100 --> 01:41:16,770 That's from our our year end episode. 1579 01:41:17,700 --> 01:41:21,150 Martin sent us a Russia 2112 boost and he says the Asian 1580 01:41:21,150 --> 01:41:25,530 market is the way to go. Is contro is a good ingredient for 1581 01:41:25,530 --> 01:41:26,280 Margarita. 1582 01:41:26,939 --> 01:41:30,749 This is all boosting basis. All boosting from that show. Yes. 1583 01:41:32,399 --> 01:41:37,409 Let's see. We got Mike Dell said 5555 through pod verse. He says 1584 01:41:37,409 --> 01:41:38,999 last boost to 2022 1585 01:41:39,240 --> 01:41:41,880 Nice one Mike Thank you. Blueberry. 1586 01:41:42,510 --> 01:41:47,280 Again at with boost CLI 33 333. And he says next week makes 100 1587 01:41:47,280 --> 01:41:50,910 Live episodes of behind the schemes in the can going live 1588 01:41:50,910 --> 01:41:54,000 with IRC and a voicemail line is such a killer combo 10 out of 10 1589 01:41:54,000 --> 01:41:55,560 would recommend Yes. 1590 01:41:56,130 --> 01:41:59,610 I'd love to understand how you're triggering all those all 1591 01:41:59,610 --> 01:42:01,530 those sounds with different amounts. 1592 01:42:01,920 --> 01:42:03,570 The goat slaughter Yes. Yeah, 1593 01:42:03,570 --> 01:42:06,450 I mean it's I'm sure it's documented somewhere but I just 1594 01:42:06,450 --> 01:42:09,120 love to see if I can do it myself. I love it. I love the 1595 01:42:09,120 --> 01:42:09,540 idea. 1596 01:42:10,320 --> 01:42:14,010 Net Ned sent us 10,000 SATs through fountain and he says not 1597 01:42:14,010 --> 01:42:21,510 DJ not VJ PB and J pod boosted Jackie. Boost tone records and 1598 01:42:21,510 --> 01:42:25,410 is 1999 1999 through curio Catherine says appreciate the 1599 01:42:25,410 --> 01:42:28,380 later live session today. A chance to sit in and chat 1600 01:42:28,380 --> 01:42:33,480 finally while logged out of work now. Oh, James Cridland oh this 1601 01:42:33,510 --> 01:42:39,840 this is your boost. This is your 100,000 Boost. Am I am I am I 1602 01:42:40,470 --> 01:42:41,850 overlapping do we do already do 1603 01:42:41,880 --> 01:42:45,150 Yeah, I don't think no the 100,000 book. Yes you overlapped 1604 01:42:45,150 --> 01:42:48,720 these were we read these while live? You got the 100,000 1605 01:42:48,720 --> 01:42:53,160 though. Yeah, that was for the bet. Now interestingly, it 1606 01:42:53,160 --> 01:42:57,150 should have gone to me alone but okay. And he actually he 1607 01:42:57,150 --> 01:43:00,720 actually sent like I think 10% back to Himself because we put 1608 01:43:00,720 --> 01:43:02,550 them in the split but okay. All right. 1609 01:43:04,290 --> 01:43:06,420 That wasn't that was a little sneaky. Yeah. 1610 01:43:07,260 --> 01:43:10,740 He did it last year too. And I'm sure for the next 10 years as I 1611 01:43:10,740 --> 01:43:14,400 remained correct on my with my bet that Apple will never 1612 01:43:14,400 --> 01:43:18,330 release Apple podcasting to Android. Just we'll just keep it 1613 01:43:18,360 --> 01:43:19,740 going to the indexes fine. 1614 01:43:21,240 --> 01:43:25,770 Let's see so I gotta I gotta make sure that I am in the right 1615 01:43:25,770 --> 01:43:27,120 thing. So we did 1616 01:43:27,240 --> 01:43:31,290 so Burberry says that all those sounds are triggered by IRC 1617 01:43:31,320 --> 01:43:35,670 okay? So it's a combine yes of the boost bot and IRC Well it's 1618 01:43:35,670 --> 01:43:38,940 good to know I mean, I'd love to understand I can get into IRC 1619 01:43:38,940 --> 01:43:39,360 stuff 1620 01:43:40,740 --> 01:43:46,980 um let's see okay. Oh, we got Peter sent us I don't I don't 1621 01:43:46,980 --> 01:43:51,600 think we did this way. I don't think so. Peter gave us 333 333 1622 01:43:51,690 --> 01:43:53,940 What? Through fountain 1623 01:43:54,479 --> 01:43:57,569 33 333,333. 1624 01:44:00,600 --> 01:44:03,720 Blades on am Paula no joke HR 1625 01:44:03,720 --> 01:44:04,350 Thank you. 1626 01:44:05,130 --> 01:44:08,100 He says thank you pod father postage and the mini mini pod 1627 01:44:08,100 --> 01:44:10,800 fluence errs out there making podcasts and 2.0 reality 1628 01:44:10,800 --> 01:44:14,250 including Alex and Mitch onward and upward boost boost boost 1629 01:44:14,250 --> 01:44:21,810 yay. 2023 sets through from Matt candle through fountain needs to 1630 01:44:21,810 --> 01:44:25,710 Happy New Year. Great meeting you at Podcast Movement. Great 1631 01:44:25,710 --> 01:44:30,930 meeting you to elite 1337 through gene from gene B. And 1632 01:44:30,930 --> 01:44:33,120 through fountain he says so glad to hear Dave say he's going to 1633 01:44:33,120 --> 01:44:35,070 build the bridge between Mr. Graham's like this one and 1634 01:44:35,070 --> 01:44:37,470 activity pub. Well, that's the plan. 1635 01:44:37,560 --> 01:44:40,950 Hey, are you are you going to pod fest? Me? 1636 01:44:40,979 --> 01:44:41,759 Yeah, no, 1637 01:44:41,790 --> 01:44:45,270 no, I just want to show you. I don't think I can handle it 1638 01:44:45,270 --> 01:44:45,780 anymore. 1639 01:44:46,770 --> 01:44:50,970 I can't it's too close to tax season. Is this whole? Yes, of 1640 01:44:50,970 --> 01:44:51,360 course. 1641 01:44:51,360 --> 01:44:51,810 Of course. 1642 01:44:52,410 --> 01:44:56,580 It's already started to season. Another one from Jean being the 1643 01:44:56,580 --> 01:44:59,460 problem with podcast apps running a mastodon server that 1644 01:44:59,460 --> 01:45:01,740 provides users With accounts is that the app owners now 1645 01:45:01,740 --> 01:45:04,290 responsible for moderation and all the other overhead of 1646 01:45:04,290 --> 01:45:07,080 operating a mastodon instance, just talked about. 1647 01:45:07,380 --> 01:45:09,120 I think we're good. I think we fixed that. 1648 01:45:10,050 --> 01:45:13,500 Social proof is also from Jean Bailey boost. He says social 1649 01:45:13,500 --> 01:45:17,490 proof social proof is just such a great way of describing 1650 01:45:17,490 --> 01:45:21,540 comments. Okay, is it something that we said? 1651 01:45:21,600 --> 01:45:25,170 I'm trying to think what that was? I don't remember saying I 1652 01:45:25,170 --> 01:45:29,010 don't feel. I like it. I'm not sure what it is. But I like it. 1653 01:45:30,390 --> 01:45:33,270 That's it. There you go. That's the show title. Social proof. We 1654 01:45:33,270 --> 01:45:35,490 got social proof. Nice. Thank 1655 01:45:35,490 --> 01:45:37,980 you probably relates to your nostril key. 1656 01:45:39,000 --> 01:45:42,510 Oh, that's right. That's right. Because I was saying that the 1657 01:45:42,510 --> 01:45:47,340 Jack was messaging me on noster he was like, that's not Jack. Ma 1658 01:45:47,340 --> 01:45:47,910 It was 1659 01:45:49,830 --> 01:45:52,980 it's it's a Jack It's not Jack and listen to this. It was the 1660 01:45:53,430 --> 01:45:57,810 it was the jack. Sir Michael 2020 says through fountain No, 1661 01:45:57,810 --> 01:46:02,520 no, thank you, sir. Thank you. Jean bein back with to 22 to 22 1662 01:46:02,520 --> 01:46:05,100 through fountaining says putting out a shameless plug for the 1663 01:46:05,100 --> 01:46:08,670 volunteer technologist podcast, where we dive into the many ways 1664 01:46:08,670 --> 01:46:11,550 people who are technically inclined voluntarily put their 1665 01:46:11,550 --> 01:46:15,750 skills to use outside of their primary job. That's interesting. 1666 01:46:15,780 --> 01:46:21,390 Yeah, I'm gonna give that a listen. Mister Mister. Not the 1667 01:46:21,390 --> 01:46:26,700 band from the 80s as soon as seven 674 sets through fountain 1668 01:46:26,730 --> 01:46:29,850 no note that what was their big hit? What was Mr. Misters big 1669 01:46:29,850 --> 01:46:30,240 two big 1670 01:46:30,240 --> 01:46:33,240 hits. I think the guys live out here actually carry a liaison 1671 01:46:33,450 --> 01:46:36,840 and broken wings of really nice guy. So can we 1672 01:46:37,860 --> 01:46:41,280 show these brains when we 1673 01:46:44,880 --> 01:46:46,890 stop? We're killing each other. 1674 01:46:47,760 --> 01:46:53,610 Five hat 10101 binary booster curio caster no note Sachtler 1675 01:46:53,610 --> 01:47:00,270 Richards from Joel Debbie. You go. No note 1555 from nomadic 1676 01:47:00,270 --> 01:47:05,670 coder, no note 2023 from Borlaug through pod verse says wanted to 1677 01:47:05,670 --> 01:47:08,010 start the new year right. You too are a gift and an 1678 01:47:08,010 --> 01:47:09,600 inspiration. Oh, 1679 01:47:10,020 --> 01:47:11,640 all Thank you. Thank you so much. 1680 01:47:13,710 --> 01:47:21,390 From me 26,000 sets use through the app use social don't see 1681 01:47:21,390 --> 01:47:23,370 that very much. I forgot about use social. Is 1682 01:47:23,370 --> 01:47:28,530 that the one that's on umbrella? Yeah. Oh, very cool. That's one 1683 01:47:28,530 --> 01:47:30,630 of the first ones overseen from eusocial. 1684 01:47:31,080 --> 01:47:34,890 Me too. And I don't know who me is. But whoever you are, you 1685 01:47:34,890 --> 01:47:35,190 know who? 1686 01:47:35,459 --> 01:47:36,479 Thank you. You 1687 01:47:37,200 --> 01:47:41,280 build up Prag 2500 SATs through pod friend. I think he's a hive 1688 01:47:41,280 --> 01:47:45,240 guy. Right? I think you could be says there's a simple solution 1689 01:47:45,240 --> 01:47:49,080 for comments. But it would be decentralized and forever. It 1690 01:47:49,080 --> 01:47:52,260 already works on 20 Plus social friends that I know this year. 1691 01:47:54,510 --> 01:47:57,510 Okay, this is the way that I've got started is there is a 1692 01:47:57,510 --> 01:48:00,690 solution for this. And then they go on to describe it and then 1693 01:48:00,690 --> 01:48:03,450 they end up with the punch line. It's Hi everyone can send a rate 1694 01:48:03,450 --> 01:48:07,980 a pod thing everyone can send or see a comment. Yes. Thank you, 1695 01:48:07,980 --> 01:48:12,390 Bill. Appreciate that. 6969 through pod verse from a citizen 1696 01:48:12,840 --> 01:48:17,370 sending GNU Linux and Software Freedom karma your way for 2023 1697 01:48:17,460 --> 01:48:18,840 The year of Linux desktop. 1698 01:48:19,140 --> 01:48:22,230 I'm going to save you and I'm going to say I heard you say 1699 01:48:22,230 --> 01:48:25,320 good new Linux I'm pretty sure you didn't say GNU I heard you 1700 01:48:25,320 --> 01:48:28,230 say good new canoe? Yes. Let's because if you don't say good 1701 01:48:28,230 --> 01:48:31,530 new Richard Stallman will come over and fart in your room or 1702 01:48:31,530 --> 01:48:36,810 something. It's like very, very paranoid about pronouncing that 1703 01:48:36,810 --> 01:48:37,320 correctly. 1704 01:48:37,800 --> 01:48:39,090 Get yes said that. Yes. 1705 01:48:39,600 --> 01:48:40,740 I heard you know. Yeah. 1706 01:48:41,939 --> 01:48:46,109 Another 6969 from a citizen. The pod verse he says boosting 1707 01:48:46,109 --> 01:48:51,239 because I love it when Dave says hey, citizen. We'll keep it up. 1708 01:48:53,459 --> 01:49:00,539 Let's see you got a couple lowball SC 54321 from Roy. Phil. 1709 01:49:00,539 --> 01:49:05,069 Hello Roy. And he says this He says this is bug bounty for 1710 01:49:05,069 --> 01:49:05,549 Adam. 1711 01:49:07,649 --> 01:49:08,849 Made some bug bounty. 1712 01:49:10,380 --> 01:49:11,520 Thank you Roger one. 1713 01:49:12,360 --> 01:49:15,870 Please stop calling me just stop is too much. I can't handle all 1714 01:49:15,870 --> 01:49:16,500 the calls. 1715 01:49:17,070 --> 01:49:19,950 All the all the nonexisting call he keeps avoiding 1716 01:49:19,950 --> 01:49:21,780 me. I don't know he only wants to talk to you and I don't want 1717 01:49:21,780 --> 01:49:24,030 to happen. It's gonna make fun of his slippers. 1718 01:49:24,960 --> 01:49:29,970 Mint lion through. This is one of breezes random Rando names. 1719 01:49:30,090 --> 01:49:35,100 6666. And he says are the beautiful Aussie drawl of James 1720 01:49:35,250 --> 01:49:38,550 filled me with national pride. Great guest to kick off the new 1721 01:49:38,550 --> 01:49:41,550 year Karen. Guessing this for Mere Mortals. 1722 01:49:41,580 --> 01:49:42,660 Thank you Kira, buddy. 1723 01:49:43,320 --> 01:49:47,550 I also have a make good from Karen. Last week and he called 1724 01:49:47,550 --> 01:49:51,600 me out on it. I got the timing wrong when I dumped the boosts 1725 01:49:51,600 --> 01:49:57,570 and it says he sent 148,000 SATs last week that I missed Hold 1726 01:49:57,570 --> 01:49:58,350 on a second 1727 01:49:58,380 --> 01:50:03,330 follow up shot How long 20 is blades? Only him. Paula 1728 01:50:03,330 --> 01:50:03,810 goodness. 1729 01:50:03,810 --> 01:50:04,410 Thank you. 1730 01:50:04,830 --> 01:50:08,280 Yeah, and I'm really I'm sorry about that, Karen. He says 1731 01:50:08,280 --> 01:50:12,090 regarding ethics, I'm certainly more generous care more about 1732 01:50:12,090 --> 01:50:14,550 making a great product for my audience. And most importantly, 1733 01:50:14,820 --> 01:50:17,670 didn't have to sell my soul through advertising or paywalls 1734 01:50:17,970 --> 01:50:21,120 or x before finding out about the V four V model. And that's 1735 01:50:21,120 --> 01:50:24,270 all due to YouTube and podcasting tip window. Happy New 1736 01:50:24,270 --> 01:50:28,350 Year to you both and I'm super excited for podcasting in 2023 1737 01:50:28,620 --> 01:50:29,400 value for 1738 01:50:29,400 --> 01:50:30,570 value dot info. 1739 01:50:31,020 --> 01:50:35,010 I'm sorry about missing that current. Let's see Brian of 1740 01:50:35,010 --> 01:50:38,280 London in the hive Dao 118,801 sets. 1741 01:50:40,229 --> 01:50:44,039 Shot call our 20th blades on am Paul out 1742 01:50:44,040 --> 01:50:45,210 some good boost today. 1743 01:50:45,810 --> 01:50:49,560 He says bit of a catch up donation though my main hive Dao 1744 01:50:49,560 --> 01:50:53,250 funding has reduced quite a bit. But as Freddy saying The show 1745 01:50:53,250 --> 01:50:55,110 must go on. I'd 1746 01:50:55,110 --> 01:50:57,360 love to understand how that works. I mean, what why did the 1747 01:50:57,360 --> 01:51:00,390 funding reduce? Do you have any idea how that works? Or what the 1748 01:51:00,390 --> 01:51:05,910 deal is? I don't like he's doing more work than ever. I don't 1749 01:51:05,910 --> 01:51:06,420 understand. 1750 01:51:06,630 --> 01:51:14,400 I can explain. Okay. Basically, the funny he got was voted on by 1751 01:51:14,400 --> 01:51:19,740 the have community. And I think his his renewal of that project 1752 01:51:21,330 --> 01:51:25,260 is either up for grabs or it didn't happen. 1753 01:51:27,300 --> 01:51:30,480 Does that mean he loses all the funding? Or does it just reduce 1754 01:51:31,590 --> 01:51:38,760 it? He loses the thickets daily or monthly income? Hmm. 1755 01:51:39,600 --> 01:51:45,030 What but I don't want Brian of London funding pod ping hive HBD 1756 01:51:45,030 --> 01:51:46,440 stuff out of his own pocket? 1757 01:51:46,770 --> 01:51:50,580 No, no, he doesn't. Just when you send a pod paying, you don't 1758 01:51:50,580 --> 01:51:55,770 actually spend any currency. So he's already got all that. The 1759 01:51:55,770 --> 01:52:00,030 only we're the only word we would have there as if piping 1760 01:52:00,030 --> 01:52:04,020 usage increased in. We had to help contribute to that. 1761 01:52:04,950 --> 01:52:06,060 Brian, let us know. 1762 01:52:06,810 --> 01:52:10,290 Which I'm happy to do I mean, you know, we Yeah, I'm happy. 1763 01:52:10,320 --> 01:52:16,500 We're happy to do that. Let's see. Oh, here we go. Blueberry. 1764 01:52:16,530 --> 01:52:21,870 17 776 through boost CLI and he says he gets a link here. He 1765 01:52:21,870 --> 01:52:24,780 says I don't know what to do with or where to use these 1766 01:52:24,780 --> 01:52:28,140 audiograms but they are fun to make. He gives a plug verse 1767 01:52:28,140 --> 01:52:32,580 link. I don't know how to. Maybe we can post this in the show 1768 01:52:32,580 --> 01:52:33,150 notes or something. 1769 01:52:33,180 --> 01:52:34,410 I'm seeing if I can find it. 1770 01:52:35,309 --> 01:52:40,679 Okay, and the delimiter comic strip blogger 33,015 SAS through 1771 01:52:40,679 --> 01:52:44,909 fountain he says dearest Dave, and artful Adam cumin kind is 1772 01:52:44,909 --> 01:52:47,939 indebted to your rejuvenation of podcasting, which will have a 1773 01:52:47,939 --> 01:52:51,569 lasting effect upon the fate of our children's children. Well, 1774 01:52:51,959 --> 01:52:55,709 your ingenuity will even cross over into emerging technological 1775 01:52:55,709 --> 01:52:59,369 sentience. So do keep tabs on the blossoming spirit of 1776 01:52:59,369 --> 01:53:03,269 artificial intelligence with AI duck cooking the podcast recited 1777 01:53:03,269 --> 01:53:05,399 by your boy Guth, yo. 1778 01:53:06,840 --> 01:53:12,750 Well, that link leads to a clip on pod verse and that clip is 1779 01:53:12,780 --> 01:53:16,260 why use pod verse. I will put that in the show notes. How nice 1780 01:53:16,260 --> 01:53:18,240 is that? Oh, that is nice. 1781 01:53:18,689 --> 01:53:23,159 You might want to listen to it for I think I heard this clip. 1782 01:53:23,189 --> 01:53:24,179 I agree I 1783 01:53:26,220 --> 01:53:28,110 would really is that what the screenshots 1784 01:53:33,600 --> 01:53:36,330 so would you like me to not post this clip? Mitch? 1785 01:53:36,540 --> 01:53:41,190 Oh, it's up to you. I'm just blueberries a prankster. 1786 01:53:41,220 --> 01:53:46,350 So okay, well, it's it appears to be from our show. Yeah, 1787 01:53:46,950 --> 01:53:48,150 Alex said I concur. 1788 01:53:49,979 --> 01:53:53,009 Cookies, blueberries always doing innovative things with the 1789 01:53:53,009 --> 01:53:56,339 show art. Their show behind the scenes, like just has these 1790 01:53:56,339 --> 01:53:59,489 really cool animated gifts that they they make themselves and 1791 01:53:59,489 --> 01:54:03,089 they you know, he puts them in as the chapter artwork and 1792 01:54:03,089 --> 01:54:04,649 stuff. It's really something to see if you 1793 01:54:04,650 --> 01:54:07,890 I mean, I just I just saw it. I saw the V for V logo dancing 1794 01:54:07,890 --> 01:54:08,370 around. 1795 01:54:09,450 --> 01:54:13,530 He did yeah. Yeah, he did that. And you should play an episode 1796 01:54:13,620 --> 01:54:17,490 of Behind the scheme some time and on the website and or the 1797 01:54:17,490 --> 01:54:21,060 mobile app and check the chapters because he has a lot of 1798 01:54:21,060 --> 01:54:23,220 animated gifts that I think he makes himself. 1799 01:54:24,000 --> 01:54:27,060 Yeah, very cool. It's it's a feast for the eyes for sure. 1800 01:54:27,090 --> 01:54:30,630 I love those guys. Man. That's insane. The stuff they're doing 1801 01:54:30,780 --> 01:54:34,260 really is they've grabbed the lip stuff by the horns. 1802 01:54:35,490 --> 01:54:40,110 And we've got let's see, we've got some monthlies. We get Chad 1803 01:54:40,110 --> 01:54:44,970 Pharaoh $22 Excuse me $20.20 Caught Jalbert $12 Martin Linda 1804 01:54:44,970 --> 01:54:51,150 scope would $1 Mark Graham $1 Joseph maraca $5 Jeremy knew $5 1805 01:54:51,150 --> 01:54:53,190 And Cameron Rose $25 And that's our group. 1806 01:54:53,639 --> 01:54:57,449 Thank you all so very, very much and today's booster grams and 1807 01:54:57,449 --> 01:55:01,319 streaming payments will be split between The usual suspects who 1808 01:55:01,319 --> 01:55:05,369 have helped us out with this program, including Dred Scott 1809 01:55:05,369 --> 01:55:09,059 for the chapters, and obviously, our two guests here in the 1810 01:55:09,059 --> 01:55:12,539 boardroom, Alex and Mitch. And so you guys have to make sure 1811 01:55:12,539 --> 01:55:15,599 that you send me your lightning addresses, so that I can 1812 01:55:15,659 --> 01:55:20,819 implement that upon publishing. Sure, value for value. That's 1813 01:55:20,849 --> 01:55:24,209 how this whole project works. If it's something of value to you 1814 01:55:24,239 --> 01:55:27,479 determine what it is, according to your own pocketbook, send it 1815 01:55:27,479 --> 01:55:29,939 back to us, you can do it in a number of ways you could the 1816 01:55:29,939 --> 01:55:32,969 number one way is to go to that now functioning new podcast 1817 01:55:32,969 --> 01:55:38,159 apps.com. The website and then you can find many different 1818 01:55:38,159 --> 01:55:42,209 podcasts, apps, you heard one here today, pod verse that 1819 01:55:42,209 --> 01:55:45,989 actually will send this value back to the to all the people 1820 01:55:45,989 --> 01:55:49,139 involved in the project. You can also go to podcast index.org at 1821 01:55:49,139 --> 01:55:52,499 the bottom, the requisite red donation button, which leads you 1822 01:55:52,499 --> 01:55:56,219 to our Fiat fun coupon, PayPal link and also tally coin, 1823 01:55:56,519 --> 01:55:59,519 believe it or not that Tina and I got a tally coin donation the 1824 01:55:59,519 --> 01:56:02,099 other day as someone actually was able to do it. And it 1825 01:56:02,099 --> 01:56:02,609 worked. 1826 01:56:03,060 --> 01:56:04,470 I'm just glad the site works. 1827 01:56:06,210 --> 01:56:08,790 Glad anything works. Really. It's amazing. any of this stuff 1828 01:56:08,790 --> 01:56:12,150 works. All right. Should we wrap this up gems anything for the 1829 01:56:12,150 --> 01:56:12,870 round table? 1830 01:56:13,500 --> 01:56:17,820 Yes, I just want to say how much I appreciate, I think. And I 1831 01:56:17,820 --> 01:56:22,170 hope both of you Alex and Mitch, hope both of you know how much I 1832 01:56:22,170 --> 01:56:25,770 appreciate you all and what you'll do. Just glad. Just glad 1833 01:56:25,770 --> 01:56:27,030 to be a part of it. It's just fun. 1834 01:56:28,710 --> 01:56:32,100 Yeah, yes. Small, small request. 1835 01:56:32,670 --> 01:56:34,710 roundtable question for the gentleman. Yes. 1836 01:56:34,710 --> 01:56:37,980 So the one thing now that the popping news is kind of you 1837 01:56:37,980 --> 01:56:41,220 know, in the past, one thing that we didn't talk about was a 1838 01:56:41,220 --> 01:56:44,940 new version of pod Ping was playlists. I know I'm, I'm 1839 01:56:44,940 --> 01:56:47,910 always like a year ahead on this stuff. But if you're a 1840 01:56:47,910 --> 01:56:52,950 developer, you're interested, reach out to us so we can test 1841 01:56:52,950 --> 01:56:55,260 it out. Now before we finalize the spec for the newspaper. 1842 01:56:55,740 --> 01:57:02,280 And playlists would be most usable for the medium tag music, 1843 01:57:03,270 --> 01:57:06,090 music and maybe video, I'm going to do it for peer tube as well. 1844 01:57:06,120 --> 01:57:09,810 So do playlists that gonna is that going to be in your code 1845 01:57:09,840 --> 01:57:13,590 for the for the new stuff that you're you're pushing into peer 1846 01:57:13,590 --> 01:57:16,740 to do not know yet. Okay. 1847 01:57:17,730 --> 01:57:20,430 What what specifically, are you do you have a concern that 1848 01:57:20,430 --> 01:57:22,350 you're trying to tease out? 1849 01:57:22,380 --> 01:57:25,770 No, I just I it's a brand new idea. And I would like feedback. 1850 01:57:25,770 --> 01:57:27,540 I know it's President space. 1851 01:57:28,740 --> 01:57:30,330 And where do they go? 1852 01:57:32,370 --> 01:57:36,120 To they go to the remote island proposal, I think, in the 1853 01:57:36,120 --> 01:57:41,250 GitHub. Yeah, and the list, mediums and remote item and get 1854 01:57:41,250 --> 01:57:42,960 up yet. All right. 1855 01:57:43,140 --> 01:57:45,720 And of course, you can always post something on podcasts index 1856 01:57:45,720 --> 01:57:48,540 dot social or if your client is not banned because of our 1857 01:57:48,540 --> 01:57:53,370 libertarian crypto ways. We should be able to federate just 1858 01:57:53,370 --> 01:57:54,180 fine with you. 1859 01:57:54,300 --> 01:57:55,650 sipto Tyrians. 1860 01:57:56,399 --> 01:58:01,349 Oh, wait a minute. Hold on a second. crypto. Terrans. Dang, 1861 01:58:01,380 --> 01:58:03,120 that'll get you blocked everywhere. 1862 01:58:03,180 --> 01:58:08,370 I need to have that domain name. That's what I need. One last 1863 01:58:08,370 --> 01:58:14,040 thing here. Martin, Linda's Koch asked if we got his late 2022 1864 01:58:14,040 --> 01:58:17,190 boosts ram of 123456 Satoshis. 1865 01:58:18,840 --> 01:58:25,560 Did you get my late 2022? histogram of 123456? I don't. I 1866 01:58:25,560 --> 01:58:25,950 don't 1867 01:58:25,950 --> 01:58:29,010 know. Know if we got that one I'm looking for well, we weren't 1868 01:58:29,010 --> 01:58:30,210 for sure. I'll give you a 1869 01:58:33,120 --> 01:58:35,220 blade on am Paula. 1870 01:58:35,310 --> 01:58:36,270 There you go. No, 1871 01:58:36,420 --> 01:58:37,980 I just wrote it down. I'll go find it. 1872 01:58:37,980 --> 01:58:40,590 We'll go find it. Gentlemen, thank you very much appreciate 1873 01:58:40,590 --> 01:58:45,000 all of you. And it's going to be another stellar year as 1874 01:58:45,000 --> 01:58:48,360 certainly as advertising falls apart. There's a number of links 1875 01:58:48,360 --> 01:58:52,140 in the show notes that we didn't discuss today, but interesting 1876 01:58:52,140 --> 01:58:56,400 to watch regardless. And I'll be on Rogen this month. I'm really 1877 01:58:56,400 --> 01:58:58,290 going to see if I can get him interested in talking about 1878 01:58:58,290 --> 01:59:02,280 podcasting. 2.0 This time, I'm not sure. But I'm gonna try. I'm 1879 01:59:02,280 --> 01:59:03,600 gonna try. We just 1880 01:59:03,599 --> 01:59:07,649 need to get him moved over there notes in the tube and in Watch, 1881 01:59:08,189 --> 01:59:09,719 watch the Linode meltdown. 1882 01:59:11,370 --> 01:59:12,570 Zone peer to that's what I'm doing. 1883 01:59:13,170 --> 01:59:17,910 Let me let me tell you, it's unwatchable on Spotify. They I 1884 01:59:17,910 --> 01:59:21,750 pay for Spotify. They interrupt the video every 10 minutes with 1885 01:59:21,750 --> 01:59:25,020 an ad that has audio those people are stupid over there. I 1886 01:59:25,020 --> 01:59:27,300 don't know what they're doing. But they don't understand user 1887 01:59:27,300 --> 01:59:30,540 experience is really really debilitating. If you notice that 1888 01:59:30,540 --> 01:59:33,960 have you ever watched this video with those interruptions? 1889 01:59:34,320 --> 01:59:39,750 No, I haven't defined it and Rogen show yeah. And I don't I 1890 01:59:39,750 --> 01:59:41,880 don't really listen to it unless you're on it. So I don't I don't 1891 01:59:41,880 --> 01:59:42,570 have any experience 1892 01:59:42,570 --> 01:59:45,240 with it. Well, don't worry, you'll be experiencing that 1893 01:59:45,270 --> 01:59:50,850 within a few weeks. You'll see every 10 minutes Hey, I use you 1894 01:59:50,850 --> 01:59:52,230 know some great vitamins. 1895 01:59:54,390 --> 01:59:58,800 If he shows up on in a tube now let's just sudo shutdown dash H 1896 01:59:58,800 --> 02:00:01,410 now. Walk away. 1897 02:00:01,560 --> 02:00:03,690 Alright everybody. Thanks again guys really appreciate it. Have 1898 02:00:03,690 --> 02:00:04,950 yourselves a great weekend. 1899 02:00:06,330 --> 02:00:07,380 Thanks so much. You too. 1900 02:00:08,820 --> 02:00:12,060 All right, Dave. Take it easy brother. See you man. Give me 1901 02:00:12,060 --> 02:00:15,990 some tools I want to help out. Make it as you're on. Yeah. 1902 02:00:17,010 --> 02:00:19,020 That's it for the board meeting everybody. We'll see you next 1903 02:00:19,020 --> 02:00:21,600 week right here for podcasting 2.0 1904 02:00:37,170 --> 02:00:41,700 You have been listening to podcasting 2.0 Visit podcast 1905 02:00:41,700 --> 02:00:44,370 index.com For more information 1906 02:00:46,680 --> 02:00:48,210 what is Blaze own