1 00:00:00,659 --> 00:00:06,719 podcasting 2.0 February 26 2021 Episode 26 were Manning battle 2 00:00:06,719 --> 00:00:07,289 stations 3 00:00:10,950 --> 00:00:14,310 going to war anything just man in the battle stations why the 4 00:00:14,310 --> 00:00:20,220 hell not? time once again for a Friday show I love the Fridays 5 00:00:20,220 --> 00:00:23,070 not because I get the podcast but because it's time for a 6 00:00:23,070 --> 00:00:27,630 board meeting of podcast index.org podcasting 2.0 I'm 7 00:00:27,630 --> 00:00:30,960 Adam curry in Austin, Texas and in Alabama the man who writes 8 00:00:30,960 --> 00:00:34,680 prose as well as he codes my friend on the other end Dave 9 00:00:34,680 --> 00:00:35,940 Jones 10 00:00:37,980 --> 00:00:41,010 gonna make it to cosmic weenie one of these days. I'm getting 11 00:00:41,010 --> 00:00:41,250 there. 12 00:00:41,279 --> 00:00:42,539 Don't get too excited about it. 13 00:00:42,900 --> 00:00:43,560 It's my goal. 14 00:00:44,490 --> 00:00:45,540 To go straight to the top. 15 00:00:46,349 --> 00:00:51,299 Yes, everybody time once again to get down to business. What it 16 00:00:51,300 --> 00:00:56,400 is Mark Cuban has a What was the name of his service this week? 17 00:00:56,760 --> 00:01:00,300 Well, I think if I'm reading the headlines you just invented 18 00:01:00,750 --> 00:01:09,360 reinvented me. Guy is such a typical venture capitalist kind 19 00:01:09,360 --> 00:01:10,170 of douche. 20 00:01:11,790 --> 00:01:15,030 Oh, fireside that somebody has already been using that for for 21 00:01:15,030 --> 00:01:17,490 a decade. Yeah, podcasting 2.0. 22 00:01:19,080 --> 00:01:22,080 Now, did he actually say that? Or was that just I have a 23 00:01:22,080 --> 00:01:25,590 feeling it might have been like a one line throw away. He had 24 00:01:25,590 --> 00:01:28,920 somewhere in in some zoom conference. 25 00:01:29,280 --> 00:01:33,600 I don't know. I just like I'm such a stickler about don't 26 00:01:33,600 --> 00:01:35,880 read. Don't just read a headline, read the entire 27 00:01:35,880 --> 00:01:39,210 article. And I forced myself to do that. But I saw that and I 28 00:01:39,210 --> 00:01:41,250 was like, I don't want to read I don't want to read. 29 00:01:42,870 --> 00:01:43,620 I don't want to read that. 30 00:01:44,250 --> 00:01:46,830 I would rather just make fun of it. You know? Well, it 31 00:01:46,830 --> 00:01:51,300 is it is fantastically interesting to me the clubhouse 32 00:01:51,510 --> 00:01:52,500 phenomenon. 33 00:01:53,220 --> 00:01:53,820 Yeah. 34 00:01:54,540 --> 00:01:59,670 But, you know, to me, it's like, who was I talking to? I was 35 00:01:59,670 --> 00:02:07,560 talking to, to gene and Gene Has it ever got pushed back up a 36 00:02:07,560 --> 00:02:11,880 little bit? So gene, a friend of mine, and he's been on he's been 37 00:02:11,880 --> 00:02:16,800 kind of looking at podcast index or doing he was on the on the 38 00:02:16,800 --> 00:02:20,460 mastodon and I forget what it was exactly, but we were 39 00:02:20,460 --> 00:02:24,300 celebrating some some when in a thread like, Hey, you know, this 40 00:02:24,330 --> 00:02:29,730 work? And then he popped in with? Well, you know, like, my 41 00:02:29,730 --> 00:02:32,790 mom couldn't figure it out. It's no good. And I just gave him 42 00:02:32,790 --> 00:02:36,390 shit right then and there. So ever since then, of course, he's 43 00:02:36,390 --> 00:02:39,990 completely entrenched in podcasting. 2.0 has a podcast 44 00:02:39,990 --> 00:02:44,430 has chapters, has images, is doing transcripts is excited 45 00:02:44,430 --> 00:02:45,780 about the satoshis. 46 00:02:45,810 --> 00:02:49,170 Yes, like a cat, neither they the more the more you abuse 47 00:02:49,170 --> 00:02:51,300 them, the more they love you. I mean, kick them down the stairs, 48 00:02:51,300 --> 00:02:54,060 get out of the way that they just want to know love and lay 49 00:02:54,060 --> 00:02:57,480 in your lap. Now, were you abused Jean. And now I know he's 50 00:02:57,480 --> 00:02:58,320 loved us all in 51 00:02:58,350 --> 00:03:00,540 now. Why was it bringing him up again? What were we talking 52 00:03:00,540 --> 00:03:00,990 about? 53 00:03:01,169 --> 00:03:02,369 That? Oh, no, come on. 54 00:03:03,539 --> 00:03:06,359 No, no. So then I was talking to him on the phone about about 55 00:03:06,359 --> 00:03:10,409 podcasting. 2.0 and clubhouse. And he said, you know, clubhouse 56 00:03:10,409 --> 00:03:14,969 is kind of like, what you go into a room, and there's all 57 00:03:14,969 --> 00:03:19,139 these podcasts. And you click on one and it drops you right in 58 00:03:19,139 --> 00:03:22,319 the middle of the conversation. And it's a great way, you know, 59 00:03:22,319 --> 00:03:25,319 to sample stuff. And if you want to, you can hang around now you 60 00:03:25,319 --> 00:03:28,499 can't rewind and go back to the beginning, but you can hang out. 61 00:03:28,649 --> 00:03:31,829 And I said, so it's kind of like a push button podcast 62 00:03:31,829 --> 00:03:34,319 experience. You said yes. That Yes. It's a lot like that. I 63 00:03:34,319 --> 00:03:37,259 said, Well, have you seen caste coverage? And I finally 64 00:03:37,259 --> 00:03:41,399 remembered the name. Cast coverage, calm. Anyone over 65 00:03:41,399 --> 00:03:44,879 there. So not just just hit it. And he said, Oh, it dropped me 66 00:03:44,879 --> 00:03:48,719 into a random podcast. With the bright in the middle. I said 67 00:03:48,719 --> 00:03:52,709 yes. Hit it again. Oh, and look at building up a playlist so you 68 00:03:52,709 --> 00:03:57,089 can remember what you listened to out. So I'm thinking of that 69 00:03:57,089 --> 00:03:59,579 and I just want to throw it out there that that's you know, cast 70 00:03:59,579 --> 00:04:02,549 coverage. Why just call it clubhouse coverage? Everyone 71 00:04:02,549 --> 00:04:06,119 seems to be my name is Khalid clubhouse coverage. And then 72 00:04:06,119 --> 00:04:11,879 just have you have it worked the same way. And even. Even pod 73 00:04:11,879 --> 00:04:14,669 friend has pod friender. Although it doesn't, I don't 74 00:04:14,669 --> 00:04:17,969 think it drops you into the middle of a podcast randomly. 75 00:04:17,969 --> 00:04:20,309 But you can swipe left, swipe right if you'd like what you 76 00:04:20,309 --> 00:04:20,699 hear 77 00:04:21,000 --> 00:04:23,100 that needs to be that that needs to be an option like a 78 00:04:23,100 --> 00:04:27,660 preference is like also, jaw drop me into a random podcast, 79 00:04:27,660 --> 00:04:29,760 but also drop me at a random needle drop. 80 00:04:30,060 --> 00:04:33,150 You know, exactly the Neato drugs actually. Exactly. And I 81 00:04:33,150 --> 00:04:36,990 think I think that's, it could be a standalone app. I swear to 82 00:04:36,990 --> 00:04:43,470 God just called clubhouse for podcast. And and it would it I 83 00:04:43,470 --> 00:04:48,090 love what is possible with the index. Yeah, we just need people 84 00:04:48,090 --> 00:04:51,270 to free themselves and see what's possible. Yeah, break out 85 00:04:51,270 --> 00:04:51,930 of the mold. 86 00:04:52,710 --> 00:04:55,410 Like I was reading about clubhouse a little bit this past 87 00:04:55,410 --> 00:04:59,490 week. I didn't realize that they were being so aggressive with 88 00:04:59,490 --> 00:05:01,260 stealing. your address book? 89 00:05:01,440 --> 00:05:03,930 Oh, yeah, you can't invite anyone unless you upload it as 90 00:05:03,930 --> 00:05:04,800 what I understand. 91 00:05:05,190 --> 00:05:07,470 Yeah. I mean, they just suck that entire thing off your 92 00:05:07,470 --> 00:05:13,050 phone, which still, which still kind of is still ticks me off a 93 00:05:13,050 --> 00:05:16,200 little bit or concerns me a little bit about signal because 94 00:05:16,200 --> 00:05:17,310 they do the same thing. 95 00:05:17,340 --> 00:05:20,820 Well, I've been told that that is not true. And you know, look 96 00:05:20,820 --> 00:05:25,560 at this. To me the only secure chat is going to be a lightning 97 00:05:25,560 --> 00:05:29,850 chat. That Yeah, when I do that, I feel like okay, no one else 98 00:05:29,850 --> 00:05:32,700 touched that message. It went from my node to the recipients 99 00:05:32,700 --> 00:05:37,980 node. I can confirm it. It costs me one Satoshi. No one 100 00:05:37,980 --> 00:05:42,210 intercepted that and it's encrypted. So now that that's 101 00:05:42,210 --> 00:05:43,530 the way I love that. 102 00:05:43,950 --> 00:05:47,820 Okay, speaking, have you installed the Sphinx node relay 103 00:05:47,820 --> 00:05:49,170 on your Raspberry Pi? 104 00:05:50,040 --> 00:05:51,690 Blitz, right. Yeah, raspy Blitz, thank 105 00:05:51,690 --> 00:05:52,530 thank you for bringing it up. 106 00:05:52,529 --> 00:05:56,219 Yes, this was one of the easiest things that I've ever done to a 107 00:05:56,219 --> 00:06:02,309 degree. Because my recipe Blitz is not directly accessible. I 108 00:06:02,309 --> 00:06:04,799 have you know, it's like my home bank. So I didn't want to put 109 00:06:04,799 --> 00:06:07,979 that just on my kit hanging off my cable modem. So you can 110 00:06:07,979 --> 00:06:14,369 access it via Tor. And to set up the Sphinx chat, all you do is 111 00:06:14,369 --> 00:06:17,069 just select the service in your recipe Blitz menu, and it 112 00:06:17,069 --> 00:06:21,509 installs it. And then it does the same, just like a zap or 113 00:06:21,509 --> 00:06:25,049 Zeus wallet, which kind of blew my mind because I understood. I 114 00:06:25,049 --> 00:06:29,519 mean, I knew how spinx chat worked. But it wasn't until I 115 00:06:29,519 --> 00:06:33,929 scan the QR code brought up. You know, it said okay, connected to 116 00:06:33,929 --> 00:06:37,859 node. And then I saw Oh, 35 million sets, oh, this is really 117 00:06:37,859 --> 00:06:40,169 a wallet. Because you know, that's what I have on this node, 118 00:06:40,619 --> 00:06:44,999 like, holy shit. So I can stream 35 million sets worth of 119 00:06:45,719 --> 00:06:50,309 satoshis to podcast now. This is cool. And so that in that 120 00:06:50,309 --> 00:06:54,209 moment, it hit me. Like, if you can put anything you want on top 121 00:06:54,209 --> 00:06:58,979 of lmd. You can do all kinds of cool stuff with it. 122 00:06:59,610 --> 00:07:05,580 Okay, so you, essentially, as I'm talking to you on on Sphinx 123 00:07:05,580 --> 00:07:10,560 chat app, yeah. And am I now talking to you on your railay? 124 00:07:11,040 --> 00:07:11,580 Yes. 125 00:07:12,390 --> 00:07:15,600 So how did you manage the x? Did you export your keys? So no, 126 00:07:15,600 --> 00:07:18,930 no, I'd see. Well, I did export my key, but I don't think you 127 00:07:18,930 --> 00:07:24,240 can you can't replace a node with a node. 128 00:07:24,959 --> 00:07:27,029 I don't, you can't, you can't like swap out. 129 00:07:27,089 --> 00:07:31,499 Right. So I have, I still have the iPhone seven. And that has 130 00:07:31,499 --> 00:07:35,699 my Sphinx account on it. And and I switched over now it only 131 00:07:35,699 --> 00:07:40,169 works on my local network, you know, 192 dot 168 cetera. But it 132 00:07:40,169 --> 00:07:43,439 works really well. What I've been trying now what I tried 133 00:07:43,439 --> 00:07:47,009 this morning, which wasn't that successful, because we also had 134 00:07:47,009 --> 00:07:48,899 internet outages. And when that's happening in the 135 00:07:48,899 --> 00:07:51,989 background, you don't know if something's failing, or you just 136 00:07:51,989 --> 00:07:56,969 had no connection was too. And this and I really thought this 137 00:07:56,969 --> 00:08:00,449 was slick. Although it doesn't work yet. You can go right into 138 00:08:00,449 --> 00:08:04,229 the raspy Blitz and say, okay, I'd like to have this on a 139 00:08:04,229 --> 00:08:07,619 dynamic DNS, then it has two providers there and I have my 140 00:08:07,619 --> 00:08:11,129 own, but I figured this use duck DNS org, and through a 141 00:08:11,129 --> 00:08:16,109 subscription menu that you do this. And so then it ties that 142 00:08:16,109 --> 00:08:23,339 domain name to your raspy Blitz. And then you can order a tour to 143 00:08:23,339 --> 00:08:29,729 IP bridge, which costs 24 sets to set up and 24 sets every day 144 00:08:29,759 --> 00:08:32,939 that you use it. And so it gives you a public IP address that you 145 00:08:32,939 --> 00:08:38,279 can map duck DNS to, and then that will tour into the node. 146 00:08:38,549 --> 00:08:43,139 And that you know that Rube Goldberg machine should work 147 00:08:43,139 --> 00:08:47,369 now. Yeah, it doesn't work. It doesn't work for me yet. But 148 00:08:47,369 --> 00:08:50,489 ultimately, yeah, that that is the idea is that you're saying 149 00:08:50,489 --> 00:08:53,999 I'm when you send me a Sphinx chat and message it goes 150 00:08:53,999 --> 00:08:57,659 straight from your node, which would be a Sphinx node goes out 151 00:08:57,659 --> 00:09:01,709 through the router, nothing but net into mine. And it has the 152 00:09:01,709 --> 00:09:04,289 encoded message I decrypt and good to go. 153 00:09:06,360 --> 00:09:11,640 Ah, that is that is. That is it is magical. 154 00:09:11,670 --> 00:09:14,190 Even better. You can also set up tribes. 155 00:09:15,330 --> 00:09:19,980 Yeah, well, the john, he did that. He moved to the move to 156 00:09:20,160 --> 00:09:23,160 Okay, so now the export thing makes sense, because when he did 157 00:09:23,160 --> 00:09:26,040 it, he had to get everybody to resubscribe. 158 00:09:27,540 --> 00:09:30,930 Exactly, yep. Yeah, that's the problem. That's the problem. Now 159 00:09:30,930 --> 00:09:33,630 it's not a problem. It's just the way the system is 160 00:09:33,630 --> 00:09:37,290 architected. So it's really not a problem. You need to you just 161 00:09:37,290 --> 00:09:40,110 need some foresight to know that. That's what you wanted to 162 00:09:40,110 --> 00:09:40,470 do. 163 00:09:40,740 --> 00:09:42,210 Yes. Well, you really set it up. 164 00:09:42,480 --> 00:09:45,330 Well, yeah, before you start making friends because I had to 165 00:09:45,330 --> 00:09:48,000 go through the whole thing and say, Hey, I'm over here now. If 166 00:09:48,000 --> 00:09:52,320 you want to reach me, but I enjoy I really liked the idea. 167 00:09:52,350 --> 00:09:57,060 Just the I wish I had. Well, not really, I guess the swings app 168 00:09:57,060 --> 00:10:02,400 is good, you know? Yeah, there's nothing I guess there's nothing 169 00:10:02,430 --> 00:10:06,090 I really wish for. I wish more people had it. Yeah, but I 170 00:10:06,090 --> 00:10:09,030 talked to Ryan Gentry he has he hasn't set up on he has a 171 00:10:09,030 --> 00:10:13,590 voltage node. And he has his because voltage nodes now also 172 00:10:13,590 --> 00:10:18,570 come with the Sphinx back end that isn't officially up 173 00:10:18,570 --> 00:10:19,440 enrolling yet. 174 00:10:19,920 --> 00:10:22,020 Yeah, I was about to say, I don't know. I don't see that. 175 00:10:22,020 --> 00:10:22,290 And no, 176 00:10:22,290 --> 00:10:25,350 it's it's, it's not a it's not an option yet. Unless you know, 177 00:10:25,350 --> 00:10:27,420 somebody who works there. You can get. 178 00:10:28,020 --> 00:10:29,610 I don't know. Anybody know, anybody 179 00:10:29,610 --> 00:10:30,210 over there. 180 00:10:31,650 --> 00:10:35,610 Yeah, so, you know, it's just, I don't, man, it's exciting. I dig 181 00:10:35,610 --> 00:10:39,150 it. And to me, it's also all new stuff, you know, so I'm, that's 182 00:10:39,150 --> 00:10:43,140 what drives me and this is Oh, yeah. Like this. This is new. 183 00:10:43,200 --> 00:10:44,550 What am I doing? SHINee 184 00:10:45,090 --> 00:10:51,780 do you think? Well, okay, so let me ping pong off of that into 185 00:10:52,320 --> 00:10:55,830 this as we're talking about Bitcoin stuff is enlightening is 186 00:10:55,830 --> 00:11:01,200 the podcast value? documentation? Yes. And that I 187 00:11:01,200 --> 00:11:05,820 put up yesterday. First, you think well, first of all about 188 00:11:05,820 --> 00:11:06,060 that. 189 00:11:06,090 --> 00:11:11,640 Well, okay. Congratulations. fantastic job. You, you can 190 00:11:11,640 --> 00:11:13,410 write you bastard. 191 00:11:13,680 --> 00:11:16,380 It sucks. I know every minute of it Really? 192 00:11:16,380 --> 00:11:19,590 Well, I don't I'm, well, once I'm into writing, then it goes 193 00:11:19,590 --> 00:11:22,380 pretty well. But I really like how you read it. You haven't 194 00:11:22,380 --> 00:11:23,940 posted the blog post yet? Have you? 195 00:11:24,269 --> 00:11:27,929 No, I haven't there's that's tweaking that a little bit. I 196 00:11:27,929 --> 00:11:29,759 think I may do that. Like Monday or Tuesday, 197 00:11:29,820 --> 00:11:32,370 when my wife looks at something because I said Tina, please 198 00:11:32,370 --> 00:11:36,600 review this. We call it the Tina wash. Just throw stuff through 199 00:11:36,600 --> 00:11:39,060 and it comes out the other end sparkling she said yes. 200 00:11:39,060 --> 00:11:42,060 Beautiful. I really have no changes. She had no question 201 00:11:42,060 --> 00:11:45,690 about something and said, No, consider rewriting this. But 202 00:11:46,410 --> 00:11:49,020 that means you're good, man. Trust me. That means 203 00:11:49,020 --> 00:11:52,320 you're good. It's a little there's a little lens flare on 204 00:11:52,320 --> 00:11:55,800 it. A little flash. Nice sparkle. Yes. 205 00:11:56,220 --> 00:12:00,210 Exactly. Well, I think it's good. I saw Brian of London made 206 00:12:00,210 --> 00:12:03,720 probably a valid point about something consistency of using 207 00:12:03,750 --> 00:12:05,160 share versus split. 208 00:12:05,700 --> 00:12:12,180 Yeah, yeah. Yeah. That, that balls like that falls into the 209 00:12:12,180 --> 00:12:17,940 category of, I'm not sure. That falls into the category of it 210 00:12:17,940 --> 00:12:21,840 doesn't matter what we name it. But I'm not saying it falls 211 00:12:21,840 --> 00:12:24,480 firmly into that category. I'm not sure I'm just not sure yet. 212 00:12:24,480 --> 00:12:26,310 Right. I'm just, I just gotta think about that. 213 00:12:26,460 --> 00:12:30,510 But once once I see all this stuff working, and Okay, now 214 00:12:30,510 --> 00:12:33,270 I've got it in my head. And you know, knowing how the ln paste 215 00:12:33,270 --> 00:12:36,420 stuff works. It's all API stuff. And it's really quite simple. I 216 00:12:36,420 --> 00:12:40,200 think the, the money part is just a challenge for most people 217 00:12:40,200 --> 00:12:43,230 who look at this with fresh eyes. Because you're not used to 218 00:12:43,230 --> 00:12:47,100 money working this way. Well, I can split this money up, I can 219 00:12:47,100 --> 00:12:50,730 split into little bits, I can, you know, just poop it out 220 00:12:50,730 --> 00:12:52,950 through the system and someone will catch it. I mean, these are 221 00:12:52,950 --> 00:12:56,610 all these are all kind of concepts that you know, goes 222 00:12:56,610 --> 00:13:00,330 against banking, just what we're used to as regular as banking. 223 00:13:00,330 --> 00:13:04,290 It. None of it really seems logical, 224 00:13:04,560 --> 00:13:09,300 but it's programmable money. And that's just like, that should 225 00:13:09,300 --> 00:13:12,510 make every developer sort of salivate a little bit. Yeah, it 226 00:13:12,510 --> 00:13:15,330 should make you scared to but because you can, you know, he 227 00:13:15,330 --> 00:13:18,540 clearly screwed things up. But it should, but it should make it 228 00:13:18,810 --> 00:13:22,830 like, I think the blog post will go into a little bit more of a 229 00:13:24,180 --> 00:13:28,140 some some of the stuff around that that revolves around it 230 00:13:28,140 --> 00:13:32,760 because like, okay, for instance, Chris Crillon in, in 231 00:13:32,760 --> 00:13:37,140 southeast Portland. I was listening to pod land last 232 00:13:37,140 --> 00:13:40,980 night. And by the way, did you shake the dust off yourself? 233 00:13:40,980 --> 00:13:41,850 When you woke up this morning? 234 00:13:43,200 --> 00:13:46,800 I shake the dust off myself. Did I miss something in pod land 235 00:13:46,800 --> 00:13:47,790 that I should know about? 236 00:13:49,170 --> 00:13:50,130 Yeah, listen to 237 00:13:50,190 --> 00:13:51,000 what he said. 238 00:13:52,470 --> 00:13:56,430 And said he said he said that you see you seeing there was a 239 00:13:56,430 --> 00:13:59,340 problem. You shook the dust off of yourself and crawled back 240 00:13:59,340 --> 00:14:00,180 into podcasting? 241 00:14:00,210 --> 00:14:04,800 No, that's nice. Yes. dusted myself off as I was under Yeah. 242 00:14:05,250 --> 00:14:06,210 saw dust. 243 00:14:06,450 --> 00:14:08,970 You got the bet you got the best signal. So yeah. 244 00:14:08,970 --> 00:14:10,440 All right. Time to suit up. 245 00:14:10,920 --> 00:14:16,050 Get out of the crypt. That's funny. Anyway, they they were 246 00:14:16,050 --> 00:14:18,420 talking about all these announcements that Spotify made. 247 00:14:18,450 --> 00:14:20,940 Yes, yes. Yeah. And all this stuff like, wow, you're 248 00:14:20,940 --> 00:14:22,560 reinventing the wheel? How cool. 249 00:14:22,889 --> 00:14:26,399 Yeah, like spot, the Spotify day or whatever this was. And, you 250 00:14:26,399 --> 00:14:29,999 know, so they're like, well, we can do polls and q&a. That's a 251 00:14:29,999 --> 00:14:32,519 feature, but it only works on Spotify. 252 00:14:32,550 --> 00:14:33,810 Yeah. Well, that makes 253 00:14:34,200 --> 00:14:38,280 sense. Yeah. With anchor and I'm like, Okay, well, you can do q&a 254 00:14:38,280 --> 00:14:41,760 and polls in chat in chapters. Yes, you can. I could put a poll 255 00:14:41,760 --> 00:14:45,240 or q&a in a chat in a chapter right now. And we show up on 256 00:14:45,240 --> 00:14:49,890 hyper catcher and pod friend. Yep. And you can do that. Oh, 257 00:14:50,160 --> 00:14:53,640 you can also charge for podcasts, but only in limited, 258 00:14:54,240 --> 00:14:57,690 limited availability in certain parts of the world and you can 259 00:14:57,750 --> 00:15:00,690 you can charge 299 499 99 260 00:15:00,720 --> 00:15:03,570 Well, they're acting like they have captured the industry. 261 00:15:04,050 --> 00:15:07,950 Yeah. And I just don't I'm not buying it. I'm just not seeing 262 00:15:07,980 --> 00:15:12,180 evidence of them having the industry. And I and this just 263 00:15:12,180 --> 00:15:14,850 and they haven't published any docs on these changes have they 264 00:15:14,850 --> 00:15:16,710 that anyone could implement that I know of? 265 00:15:17,880 --> 00:15:20,700 No, I mean, nobody can implement it. It's all siloed. It's all in 266 00:15:20,700 --> 00:15:22,950 the it's all in the, in the walled garden, 267 00:15:23,850 --> 00:15:25,860 probably just making straight API calls. 268 00:15:26,400 --> 00:15:29,610 Oh, yeah. It's within their stack. None of this stuff is 269 00:15:29,610 --> 00:15:33,780 usable without outside of their of their system. You know, and 270 00:15:33,780 --> 00:15:36,000 I'm sitting here listening, I'm listening and listening to this 271 00:15:36,000 --> 00:15:40,560 stuff. And I'm like, you know, there is there is literally 272 00:15:40,560 --> 00:15:46,860 nothing that they can do within a closed system that cannot also 273 00:15:46,860 --> 00:15:50,760 be done in RSS. Absolutely. Nothing. And I'm not I'm not, 274 00:15:50,790 --> 00:15:54,990 that is not hyperbole. There is nothing that they can do. It 275 00:15:54,990 --> 00:15:59,220 can't be done in an open in an open system. And in the old 276 00:15:59,220 --> 00:16:01,710 knock would be what we are. Yeah, but it may take longer. 277 00:16:01,860 --> 00:16:04,470 They're agile, they can move because they don't have to, but 278 00:16:04,470 --> 00:16:07,080 they don't have to worry about interop. Well, that's not true. 279 00:16:07,260 --> 00:16:10,530 Because they're slow as molasses. Yeah. They're slow. 280 00:16:10,560 --> 00:16:14,160 They're, they're I mean, they're saying that, oh, we're gonna 281 00:16:14,160 --> 00:16:20,400 have q&a or you know, paid beta, beta for right nim for 282 00:16:20,400 --> 00:16:23,460 subscribing monetary subscriptions in podcast. And it 283 00:16:23,460 --> 00:16:27,900 only works in an anchor. It only works in Spotify. And it will be 284 00:16:27,900 --> 00:16:32,160 in limited beta in the at the end of the spring. Yeah, got me. 285 00:16:32,160 --> 00:16:36,390 We got we got lightning up and running in five months. Four 286 00:16:36,390 --> 00:16:36,720 months. 287 00:16:36,870 --> 00:16:38,700 We did it was so fast. 288 00:16:39,960 --> 00:16:44,310 Me. Yeah. Yeah. Anyway, that's just they're not they're not 289 00:16:44,310 --> 00:16:48,210 fast. is not faster. It's not easier to use. 290 00:16:50,970 --> 00:16:53,340 I could do anything better than you. 291 00:16:57,000 --> 00:17:02,040 ourselves on for today. Yeah, you can do I can do better. 292 00:17:02,460 --> 00:17:05,160 Yeah, that's me. That is that's what it sounds like when I'm 293 00:17:05,160 --> 00:17:05,610 Petty. 294 00:17:05,819 --> 00:17:07,019 Yeah, exactly. 295 00:17:07,559 --> 00:17:12,719 I don't, I don't mind being a petulant child. It aggravated 296 00:17:12,719 --> 00:17:12,989 me. 297 00:17:13,049 --> 00:17:16,439 Here's something I was I was thinking about, because my mind 298 00:17:16,439 --> 00:17:18,959 is already going around. And what's there's some app or 299 00:17:18,959 --> 00:17:22,919 something that came out where you can opt in, and your 300 00:17:22,919 --> 00:17:27,179 behavior will be tracked. And I think you get some benefit for 301 00:17:27,179 --> 00:17:32,219 it. I was like one app, and they clearly wants statistics. And I 302 00:17:32,219 --> 00:17:34,979 was thinking we could reverse this process. Now. I'd haven't 303 00:17:34,979 --> 00:17:38,279 thought it all the way through. But we could reverse the 304 00:17:38,279 --> 00:17:44,849 streaming satoshis process easily to allow an Advertising 305 00:17:44,849 --> 00:17:48,059 Bureau to track listening minutes. 306 00:17:49,589 --> 00:17:51,029 stream it, stream it right back and 307 00:17:51,390 --> 00:17:53,910 stream it right on them and they can track they can track the 308 00:17:53,910 --> 00:17:57,330 minutes, you know, it will be a very so MUCH better this. I 309 00:17:57,330 --> 00:18:00,240 mean, it's this is a metric that no one has. You know, it would 310 00:18:00,270 --> 00:18:03,480 it would explode all the IB bullshit overnight. 311 00:18:03,750 --> 00:18:05,850 I've got it. I've got it. 312 00:18:05,880 --> 00:18:08,160 Okay, I'm gonna write it down. I'm gonna trademark it. What's 313 00:18:08,160 --> 00:18:09,450 the domain name? No, 314 00:18:10,170 --> 00:18:15,960 no, no. I've had it. I've got a brainstorm. Okay. So there was 315 00:18:15,960 --> 00:18:20,730 this? Where did I read this? I think I think I read it this 316 00:18:20,730 --> 00:18:26,040 morning. There was a article about paid guesting on 317 00:18:26,040 --> 00:18:29,610 podcasting. And I think it was in Business Insider. And I 318 00:18:29,610 --> 00:18:33,600 didn't print that article. But it was essentially saying that 319 00:18:33,600 --> 00:18:38,070 there's this whole world of people that want you to pay to 320 00:18:38,070 --> 00:18:41,490 be on their show. Okay. And it's it seemed to be a lot of like 321 00:18:41,490 --> 00:18:44,310 these, you know, like marketing guru work, 322 00:18:44,309 --> 00:18:47,969 you know, who people whose business it is to be on show? 323 00:18:47,969 --> 00:18:48,389 Sure, 324 00:18:48,420 --> 00:18:51,990 yeah, yeah, entrepreneur, you can make you know, $10,000 from 325 00:18:51,990 --> 00:18:55,170 home, you know, and have a better life, this kind of stuff. 326 00:18:55,619 --> 00:18:58,049 Like, just become a podcast, app developer. 327 00:18:58,260 --> 00:18:58,980 Yeah. 328 00:19:00,240 --> 00:19:04,080 That's the quick right way to get to the top. But anyway, 329 00:19:04,080 --> 00:19:08,370 there's just like, so there's this whole system going on, 330 00:19:08,370 --> 00:19:13,050 where you can say, well, I've got this, you know, I want to be 331 00:19:13,050 --> 00:19:15,960 on your show, because I want to promote my show, or I want to 332 00:19:15,960 --> 00:19:19,230 promote my book or whatever, will different podcasts will 333 00:19:19,230 --> 00:19:25,410 charge you 250 500 $1,000 to have a guest spot on their show. 334 00:19:25,410 --> 00:19:29,730 And they don't they don't label it as as if the paid as a paid 335 00:19:29,730 --> 00:19:33,360 spot, even though that's what it is. It just, it just shows up as 336 00:19:33,360 --> 00:19:37,410 if it was just a random interview. So right, what if you 337 00:19:37,410 --> 00:19:42,870 reverse the flow, you reverse that flow? Is it okay for you 338 00:19:42,870 --> 00:19:46,710 know, for if you want to gain audience, instead of paying some 339 00:19:46,710 --> 00:19:50,970 other podcast or $1,000 you just say I'll pay all my listeners 340 00:19:52,260 --> 00:19:57,270 per minute for as you as you listen to me for a limited 341 00:19:57,300 --> 00:20:00,450 amount of time until I get I like it. I know. Until I'll 342 00:20:00,450 --> 00:20:04,050 build my audience up to 300 I'll just reverse the faucet and you 343 00:20:04,050 --> 00:20:05,460 know reverse the valve. And for 344 00:20:05,460 --> 00:20:07,590 that good idea, I like it. 345 00:20:08,069 --> 00:20:10,859 Yeah. Pay pay for audio. I mean, that's what clubhouse is doing. 346 00:20:10,859 --> 00:20:13,199 They're paying for audience right now. Yep. Aren't they? 347 00:20:13,229 --> 00:20:16,199 Aren't they paying people to, to club cash or whatever? 348 00:20:16,199 --> 00:20:16,619 Definitely 349 00:20:16,620 --> 00:20:20,310 paying some people. Yes, I'm not sure who, but they're definitely 350 00:20:20,310 --> 00:20:21,180 paying some people. 351 00:20:21,569 --> 00:20:24,209 tankers paying their own people, their their house ads is like 352 00:20:24,209 --> 00:20:28,139 90% of the ads. So I mean, like, I think that's a good idea. 353 00:20:28,829 --> 00:20:34,709 I love it. Hey, a quick mention of buzzsprout. I was already 354 00:20:34,709 --> 00:20:37,559 kind of high on this company. And now I understand why no one 355 00:20:37,559 --> 00:20:41,609 reached out to me left our last show. Like, there were a little 356 00:20:41,609 --> 00:20:46,079 busy. They were a little busy. Yeah, with a DDoS attack, which 357 00:20:46,079 --> 00:20:50,789 I've witnessed in many different forms. It sucks. What I liked is 358 00:20:50,789 --> 00:20:56,159 how they communicated how they were also communicating 359 00:20:56,159 --> 00:21:00,359 publicly, to other podcast community communities, including 360 00:21:00,359 --> 00:21:03,749 ours. And then today, I listened to the to the buzz cast. And 361 00:21:03,749 --> 00:21:08,099 they did a nice job, a whole post production with music and 362 00:21:08,099 --> 00:21:11,969 the facts and everything of what went down. 30 minute podcast, it 363 00:21:11,969 --> 00:21:16,289 was very good. And you know, we obviously believe in the concept 364 00:21:16,319 --> 00:21:21,419 of open open communications with the company and then this is our 365 00:21:21,419 --> 00:21:24,689 board meeting that I've really felt that was not just smart, it 366 00:21:24,689 --> 00:21:29,039 shows you what what their DNA is. And big kudos all around 367 00:21:29,069 --> 00:21:30,659 kicking ass did a great job 368 00:21:30,810 --> 00:21:36,270 where they trying to pull in the true crown. Crap. Well, they got 369 00:21:36,270 --> 00:21:39,480 me starting last week, in the middle of the night. 370 00:21:41,460 --> 00:21:44,910 Wait, so I play a little bit of our new podcast? Oh, yeah, sure. 371 00:21:48,330 --> 00:21:49,290 You don't have a brush, you can 372 00:21:54,510 --> 00:21:56,460 just walk up your mask dividend. 373 00:22:01,829 --> 00:22:02,969 I'd like your three days. 374 00:22:07,200 --> 00:22:07,740 Before 375 00:22:10,200 --> 00:22:13,170 we can do this show, ma'am. That's a great show. It 376 00:22:14,670 --> 00:22:18,600 is capturing the whole headspace craze, you know? 377 00:22:20,490 --> 00:22:23,760 Okay, what do we have anything else we need to discuss before 378 00:22:23,760 --> 00:22:26,640 we get to our guest who has been waiting patiently, although he 379 00:22:26,640 --> 00:22:30,180 has been able to listen in so he kind of gets a free ride. I'm 380 00:22:30,180 --> 00:22:31,020 listening to the show. 381 00:22:31,530 --> 00:22:33,330 I'm not gonna punish him any longer. 382 00:22:33,629 --> 00:22:37,049 Ladies and gentlemen, we have one of our Primo podcast app 383 00:22:37,049 --> 00:22:42,479 developers with us right now. The man who is without a doubt a 384 00:22:42,479 --> 00:22:46,859 renaissance man he is from everywhere and nowhere. He's got 385 00:22:46,859 --> 00:22:52,079 a Brazilian Portuguese background. He's Italian. He's 386 00:22:52,079 --> 00:22:56,369 German. He's lives on Mars. Please welcome Gilly Anima delgo 387 00:22:56,369 --> 00:22:57,119 Steen. 388 00:23:00,180 --> 00:23:02,820 I'll have to hire you for doing my PRM and 389 00:23:04,170 --> 00:23:07,950 you misunderstood as part of podcasts? index.org. It's free? 390 00:23:08,490 --> 00:23:11,280 Yes. You get it for free. My 391 00:23:11,280 --> 00:23:16,050 brother is in the package. Yeah, you're a you're a man of the 392 00:23:16,050 --> 00:23:16,590 world. 393 00:23:19,260 --> 00:23:26,550 So DMA showed up on the mastodon podcast index dot social podcast 394 00:23:26,550 --> 00:23:29,460 in the CLI social Yes, podcast index dot social, gosh, darn it. 395 00:23:30,450 --> 00:23:34,800 So many of these to remember very early on, and is one of the 396 00:23:34,860 --> 00:23:39,720 premier developers, I would say always, they're always ahead of 397 00:23:39,720 --> 00:23:44,220 the curve. But first, we need to understand exactly what your 398 00:23:44,220 --> 00:23:47,130 background is. Guillermo, because we got you on the on the 399 00:23:47,130 --> 00:23:51,360 zoom call. And so you are are you Portuguese or Brazilian? 400 00:23:52,140 --> 00:23:57,420 So I am Brazilian. And a lot of people get this confused because 401 00:23:57,420 --> 00:24:00,510 like we speak Portuguese in Brazil, right? Yeah, but I am 402 00:24:00,510 --> 00:24:07,560 Brazilian and I lived there until 2013. So basically, I grew 403 00:24:07,560 --> 00:24:12,450 up and became an adult there. And it was like it was 2020 a 404 00:24:12,450 --> 00:24:17,940 lot. And then I moved to Germany. And while I have a 405 00:24:17,940 --> 00:24:20,610 background as a software developer, I still work on the 406 00:24:20,610 --> 00:24:25,200 industry. Now I'm not developing I am in a very confusing role 407 00:24:25,200 --> 00:24:29,790 that it's hard to explain like mainly helping to onboard new 408 00:24:29,820 --> 00:24:33,960 colleagues and new teams into a project that I am working. Yeah, 409 00:24:33,960 --> 00:24:39,600 but I was never a web developer before or at least I am not a 410 00:24:39,600 --> 00:24:45,270 web developer. by trade. I always worked either on the back 411 00:24:45,270 --> 00:24:49,410 end or like it was in the GRP software. And before that, I was 412 00:24:49,410 --> 00:24:52,740 doing extensions for design software, so like completely 413 00:24:52,740 --> 00:24:57,690 different. And while I got in contact with podcasts around 414 00:24:57,690 --> 00:25:03,240 2012 2011 And we've time I started listening a lot of 415 00:25:03,240 --> 00:25:09,240 podcasts. And I still do a lot of listening on my desktop at 416 00:25:09,240 --> 00:25:12,240 that time, and I wanted something, basically to 417 00:25:12,240 --> 00:25:18,990 synchronize between devices. And to be free. Because I'm cheap 418 00:25:18,990 --> 00:25:25,740 guy. And I was learning a bit of web development there, it was 419 00:25:25,740 --> 00:25:28,890 contributing to an internal tool in the company. So it was not my 420 00:25:28,890 --> 00:25:32,790 main job. But on the side, I was learning it. And I also got in 421 00:25:32,790 --> 00:25:36,810 contact with development of browser extensions also, because 422 00:25:36,810 --> 00:25:41,670 of an ad I had before developing pod station. And while I 423 00:25:41,670 --> 00:25:45,300 discovered that this in, if you do a browser extension, or at 424 00:25:45,300 --> 00:25:50,580 least for Chrome, there is a very, very tiny space of sync 425 00:25:50,580 --> 00:25:54,360 storage that you can use. It's 200 kilobytes like, wow, tiny 426 00:25:54,360 --> 00:26:01,350 Whoa. What's that? Exactly, it's back to stone age, I was okay. 427 00:26:02,070 --> 00:26:08,340 If I had a floppy disk, a good start. But it was enough at 428 00:26:08,340 --> 00:26:12,300 least to to store the list of podcasts that I subscribed to. 429 00:26:12,660 --> 00:26:15,840 And that's how it started. So in the beginning, like the first 430 00:26:15,840 --> 00:26:19,500 version that I published, was, it didn't even have a player, it 431 00:26:19,500 --> 00:26:24,900 was just like, you use the iTunes search, and just 432 00:26:24,900 --> 00:26:25,950 downloaded it, just click 433 00:26:25,950 --> 00:26:26,940 download or whatever. 434 00:26:26,970 --> 00:26:30,300 Yeah, you click download, you listen in either directly in the 435 00:26:30,300 --> 00:26:33,510 browser, but not before player like this standard player from 436 00:26:33,510 --> 00:26:36,900 the browser, or you don't load to listen, and then which time I 437 00:26:36,900 --> 00:26:40,710 started adding features and then adding a player playlist. And 438 00:26:40,740 --> 00:26:46,710 well, now today, it's a full fledged thing with some features 439 00:26:46,710 --> 00:26:50,580 that I decided not to implement, because like, for instance, a 440 00:26:50,580 --> 00:26:55,290 lot of people ask, well, Why cannot I mark something as 441 00:26:55,290 --> 00:26:59,160 Leeson that I are already listening? And because it takes 442 00:26:59,370 --> 00:26:59,700 a lot of 443 00:26:59,700 --> 00:27:00,540 storage? 444 00:27:01,200 --> 00:27:04,590 Exactly. So I could do it locally, I guess that a lot of 445 00:27:04,590 --> 00:27:06,780 people listening a single device, but then I have to 446 00:27:06,780 --> 00:27:10,980 distinguish what goes locally, what goes in sync storage. And 447 00:27:10,980 --> 00:27:14,070 it would be very confusing for people that using both devices, 448 00:27:14,070 --> 00:27:16,650 because then you have it marked in one device and it's not 449 00:27:16,650 --> 00:27:19,740 marked in the other device. Yeah. And then I decided, Okay, 450 00:27:20,040 --> 00:27:22,650 if I cannot implement it in a good way, then I will leave it 451 00:27:22,650 --> 00:27:27,390 out. But basically, that's it whatever I can, and I can fit in 452 00:27:27,390 --> 00:27:32,040 this 200 kilobytes goes in. So the playlist the progress of 453 00:27:32,040 --> 00:27:35,310 your podcasts as long as it's not too much, I didn't get this 454 00:27:35,310 --> 00:27:38,700 whole time, only one or two people came to me and say, hey, 455 00:27:38,730 --> 00:27:41,250 it's not working. And then we looked at it and it was full. 456 00:27:45,150 --> 00:27:50,160 Before before you continue going from Brazil to Germany, is that 457 00:27:50,160 --> 00:27:53,880 a typical jump for people? Or is that something you? I mean, how 458 00:27:53,880 --> 00:27:56,610 did that come about? What was your what was the process, if 459 00:27:56,610 --> 00:27:57,420 you don't mind me asking. 460 00:27:57,930 --> 00:28:02,460 But it was a bit particular. So I work for a company that's 461 00:28:02,490 --> 00:28:05,850 German company, and they had a subsidiary there where I live in 462 00:28:05,850 --> 00:28:12,270 Brazil, and also my wife, she's a physicist, and she was looking 463 00:28:12,270 --> 00:28:17,580 for a PhD on Europe. Oh, there it is. Yep, 464 00:28:17,639 --> 00:28:20,249 there it is. Yeah, it's always for a woman, whether you're 465 00:28:20,249 --> 00:28:21,479 looking for one or following 466 00:28:23,550 --> 00:28:29,310 through. And she, she basically brought me to Europe. And we 467 00:28:29,310 --> 00:28:32,850 came together and we managed the winning away that she did her 468 00:28:32,850 --> 00:28:37,140 PhD. And I got a transfer. So she was nice studying near to 469 00:28:37,140 --> 00:28:38,700 the place where I could work here. 470 00:28:38,940 --> 00:28:39,840 Worked out good. Yeah. 471 00:28:40,260 --> 00:28:43,110 Actually stayed. Basically that that was how it worked. 472 00:28:43,859 --> 00:28:50,429 Excellent. So now I use pod station. Almost every day in 473 00:28:50,489 --> 00:28:53,999 that I'm in the studio, because I know I have that's the only 474 00:28:54,929 --> 00:28:59,219 machine I have that I use that. That is a desktop I use my my 475 00:28:59,219 --> 00:29:02,099 graphene Oh, S for everything else. So first of all, thank 476 00:29:02,099 --> 00:29:07,709 you, because it is the easiest, quickest slam dunk player there 477 00:29:07,709 --> 00:29:11,069 is it's always there. You know, I don't I don't have to go to my 478 00:29:11,069 --> 00:29:15,239 start menu and just like oh, click this thing up here. And 479 00:29:15,239 --> 00:29:19,349 the fact that you were outside of savings will really from the 480 00:29:19,349 --> 00:29:22,169 Sphinx, proof of concept, the first one to implement. 481 00:29:23,219 --> 00:29:27,719 Streaming SATs value for value is just phenomenal. And I know 482 00:29:27,719 --> 00:29:30,359 that you're seeing me use it because you say hey, someone 483 00:29:30,359 --> 00:29:33,389 sent some stats, some sass this way. What's going on? Yeah, 484 00:29:33,389 --> 00:29:35,069 that's me. And 485 00:29:35,849 --> 00:29:39,989 it was the first time I got any sets. I think it was from you. I 486 00:29:39,989 --> 00:29:43,049 don't know if anyone else is using but I knew at least from 487 00:29:43,049 --> 00:29:44,309 you, I was gonna get something 488 00:29:44,819 --> 00:29:50,249 that how's How hard is it to write a decent browser 489 00:29:50,249 --> 00:29:53,339 extension? I mean, like, I've done a little bit of it and in 490 00:29:53,339 --> 00:29:56,969 the past of a road, one extension to do to do something 491 00:29:56,969 --> 00:30:00,179 within our company. And in Chrome. It was it was for 492 00:30:00,179 --> 00:30:04,709 Chrome, and I remember just sort of getting so frustrated and 493 00:30:04,709 --> 00:30:07,379 banging my head against the wall about all the limitations you 494 00:30:07,379 --> 00:30:10,769 had to jump through. It means that I couldn't imagine writing 495 00:30:10,769 --> 00:30:13,679 a podcast app. And that is it. I mean, did you just like want to 496 00:30:13,679 --> 00:30:14,969 scream and jump out a window? 497 00:30:15,750 --> 00:30:19,650 No, no, not at all. Actually, it's the opposite. Because it, 498 00:30:20,070 --> 00:30:24,750 it facilitated some stuff for me like, it's basically like a web 499 00:30:24,750 --> 00:30:28,770 app. But there's some stuff that I use the API's from the 500 00:30:28,770 --> 00:30:33,750 extension, one of one big advantage is you can get around 501 00:30:33,750 --> 00:30:37,860 this cross origin resource sharing thing, that dreaded 502 00:30:37,860 --> 00:30:41,490 corollary, the dreaded course, yeah, that's something that have 503 00:30:41,490 --> 00:30:46,380 been keeping me away of trying to do a web version of it for a 504 00:30:46,380 --> 00:30:51,570 long time, it's a big limitation, I even started to 505 00:30:51,570 --> 00:30:55,920 call the web app based on ionic like this framework for hybrid 506 00:30:56,310 --> 00:31:01,830 development. It worked, it works, but it didn't get so far, 507 00:31:01,830 --> 00:31:05,460 because a bae wanted to focus a bit more on the on the 508 00:31:05,460 --> 00:31:10,290 extension, I think that they are. Now with the index, it's 509 00:31:10,290 --> 00:31:14,340 much easier because you can get a lot of stuff from the index. 510 00:31:14,640 --> 00:31:19,170 And get around this. Because if you want only if you get to the 511 00:31:19,170 --> 00:31:23,190 point where it gets to the audio file, like to the URL, then you 512 00:31:23,190 --> 00:31:29,130 can play it because you you can if you don't do like HTTP 513 00:31:29,130 --> 00:31:32,160 requests from inside your code from the JavaScript, and you can 514 00:31:32,160 --> 00:31:37,860 get around this. But if you had, for instance, to fetch the feed 515 00:31:37,860 --> 00:31:40,830 and parse the feed, and then the feed is not corps enabled, then 516 00:31:40,830 --> 00:31:44,430 you cannot do it. And then the index, you can resort to that. 517 00:31:45,599 --> 00:31:48,209 What what's the point of this evil Corps in the first place? 518 00:31:48,209 --> 00:31:50,699 Is it for some kind of hack that people can do? That's, that's 519 00:31:50,699 --> 00:31:52,169 what it's trying to avoid? 520 00:31:53,579 --> 00:31:56,789 I think it's something like, like when you are in your 521 00:31:56,789 --> 00:32:02,519 domain, you cannot look at data from the other domains or post 522 00:32:02,519 --> 00:32:06,569 data to the other domains unless, unless the other domain 523 00:32:06,569 --> 00:32:10,709 allows you to do it. It's a big limitation. I think for 524 00:32:10,709 --> 00:32:13,589 progressive web apps, especially these kind of progressive web 525 00:32:13,589 --> 00:32:17,759 apps, and especially for having a decentralized web. I think 526 00:32:18,449 --> 00:32:21,419 when you have a Chrome extension, you have the 527 00:32:21,419 --> 00:32:25,589 permissions. And in my case, I am very permissive. And then if 528 00:32:25,589 --> 00:32:30,059 you install it, it's gonna say, hey, this extension can read 529 00:32:30,329 --> 00:32:33,359 from all the websites or visit and stuff like that. But that's 530 00:32:33,359 --> 00:32:39,479 because I didn't get the effort to do this more fluent 531 00:32:39,479 --> 00:32:42,869 permission requests, like when you are going to access that 532 00:32:42,869 --> 00:32:45,599 domain, then I ask him, Hey, can I access this domain? But then 533 00:32:45,929 --> 00:32:48,779 this could also be a bit annoying, you can kind of ruin 534 00:32:48,779 --> 00:32:53,909 the experience. Yeah, exactly. But at least something similar 535 00:32:53,909 --> 00:32:58,589 for, for progressive web apps should be there where I say, 536 00:32:58,589 --> 00:33:02,219 Hey, I don't need to post stuff. I only need to get stuff from 537 00:33:02,249 --> 00:33:06,059 this domains. And then I asked for the permission. And then if 538 00:33:06,059 --> 00:33:08,999 the user says, Yeah, you're okay, you can get it. And then 539 00:33:08,999 --> 00:33:12,779 you don't have to refresh that very often. That is, could be an 540 00:33:12,779 --> 00:33:17,249 OK, experience. But it's a very big limitation for for 541 00:33:17,249 --> 00:33:20,969 distributed web apps based on RSS and that kind of stuff. 542 00:33:21,509 --> 00:33:21,959 Yeah, 543 00:33:21,990 --> 00:33:23,190 it's a fairly is, 544 00:33:23,250 --> 00:33:25,470 I don't know, I don't know how you did it. But the, you know, 545 00:33:25,500 --> 00:33:29,310 with with no space to with 200 kilobytes to work with, and you 546 00:33:29,310 --> 00:33:33,660 still got lm pay working fine in there, because you you support 547 00:33:33,660 --> 00:33:37,890 both interfaces, the REST API, the LM pay, I mean, you are so 548 00:33:37,890 --> 00:33:39,390 ahead of the game was fantastic. 549 00:33:39,420 --> 00:33:41,940 I didn't know the I didn't know the macaroon stuff was still in 550 00:33:41,940 --> 00:33:44,130 there. So you can do both? I think so 551 00:33:44,130 --> 00:33:48,750 you can select Yeah, it's both. Oh, well, you go there because 552 00:33:48,750 --> 00:33:52,290 the options. Yep. And you can select it, select an l&d node, I 553 00:33:52,290 --> 00:33:54,720 wanted to implement other nodes as well. But I don't know how 554 00:33:54,720 --> 00:33:58,260 popular they are. I think I had to start with something. So it 555 00:33:58,260 --> 00:34:00,690 went like CSC lightwell. And I think 556 00:34:02,099 --> 00:34:02,879 with lnd 557 00:34:03,900 --> 00:34:05,550 Yeah, I think it's the most popular, 558 00:34:05,579 --> 00:34:08,009 what have you run up against? What were some of the problems 559 00:34:08,009 --> 00:34:10,079 you run up against? For the other developers who were 560 00:34:10,079 --> 00:34:12,809 implementing this now? was anything particularly difficult? 561 00:34:14,070 --> 00:34:18,510 No, not not much, actually. But one of the things it's like the 562 00:34:18,510 --> 00:34:22,350 the conversion of data that you have to do like from binary to 563 00:34:22,350 --> 00:34:25,440 wax to something else, and then figure out exactly what is the 564 00:34:25,440 --> 00:34:29,250 formatting that you have to do when you consume the API's. But 565 00:34:29,280 --> 00:34:33,030 once once it's up, it's quite simple. I mean, it's more like 566 00:34:33,270 --> 00:34:36,240 you spend a little bit of time fine tuning and finding exactly 567 00:34:36,240 --> 00:34:38,880 what you have to send through the API's. And once you get 568 00:34:38,880 --> 00:34:41,010 there, it's it's quite easy. And doing that 569 00:34:41,220 --> 00:34:44,250 without without a back end server. That's, that's, that's 570 00:34:44,250 --> 00:34:44,970 pretty awesome. 571 00:34:46,530 --> 00:34:51,060 Yeah, it's, it's one of the limitations is like you having 572 00:34:51,060 --> 00:34:54,600 to install the certificate because if you run an old test 573 00:34:54,840 --> 00:34:58,050 on your own, it's going to be HTTPS, and it's going to be its 574 00:34:58,050 --> 00:35:02,820 own certificate. So you have to do it. Probably, yeah. But aside 575 00:35:02,820 --> 00:35:06,420 from that, it's quite simple. It's just consuming an API on a 576 00:35:06,690 --> 00:35:12,930 on a remote system. And the LNP was quite easy to it. So I think 577 00:35:12,930 --> 00:35:16,920 that this technical part of actually consuming the API's and 578 00:35:16,920 --> 00:35:19,650 triggering the transmissions, it's the easy part, I think the 579 00:35:19,650 --> 00:35:24,000 part that's going to be a bit of a struggle is that you have to 580 00:35:24,000 --> 00:35:28,050 start building a small accounting system inside of your 581 00:35:28,410 --> 00:35:31,380 application, because you start having to calculate these 582 00:35:31,380 --> 00:35:34,200 values. If it's offline, you accumulate for a long time. So 583 00:35:34,200 --> 00:35:38,310 you have a persistency, for that you have stuff. And once you 584 00:35:38,310 --> 00:35:41,760 start doing that, you have to think, how do I show this to the 585 00:35:41,760 --> 00:35:44,160 user. So this is something I completely don't do, and I 586 00:35:44,160 --> 00:35:47,520 completely don't have persistency for that. So right, 587 00:35:47,520 --> 00:35:48,930 isolating, 588 00:35:49,290 --> 00:35:53,100 so I go offline. So if your app goes offline, you read now your 589 00:35:53,100 --> 00:35:55,620 best, you're just no payments. And so when it comes back 590 00:35:55,620 --> 00:35:58,650 online, then you you're not, you're not tracking it in a way 591 00:35:58,650 --> 00:36:00,330 where you can batch the stuff together later, 592 00:36:01,200 --> 00:36:05,340 it stays in memory. So as long as it doesn't unload, it would 593 00:36:05,340 --> 00:36:08,430 work. But on the other hand, you need to be online to listen to 594 00:36:08,430 --> 00:36:12,210 the podcast unless it's buffered, and to a certain 595 00:36:12,210 --> 00:36:15,840 point, but it is I don't have the option to download for 596 00:36:15,840 --> 00:36:21,450 offline listening yet. So yeah, if if you went offline, for a 597 00:36:21,450 --> 00:36:24,480 certain time, it's going to accumulate, if you go back, then 598 00:36:24,480 --> 00:36:27,480 it's going to send that cumulated values. But it's a 599 00:36:27,480 --> 00:36:31,440 very short time span. If you wanted to have something more 600 00:36:31,440 --> 00:36:35,580 like a traditional podcast app experience, and really download 601 00:36:35,580 --> 00:36:39,780 and listen offline. No, you need all this accounting and on the 602 00:36:39,780 --> 00:36:45,270 back end, on the background, to to collect all this data to 603 00:36:45,270 --> 00:36:48,510 maybe show Hey, this is spending or this is what you sent before. 604 00:36:48,510 --> 00:36:51,810 And now the challenge is a bit of a UX challenge. How do I show 605 00:36:51,810 --> 00:36:53,670 this to the users? Well show 606 00:36:53,730 --> 00:36:56,100 what you know what I really would I really love it's just 607 00:36:56,100 --> 00:36:59,460 me, so please don't build this. But I love popping up the log. 608 00:36:59,820 --> 00:37:03,270 And, and seeing everything. No scroll by I'm like, okay, and it 609 00:37:03,270 --> 00:37:06,540 says, Oh, yeah, collecting data for the shoe for payment. Oops, 610 00:37:06,540 --> 00:37:09,930 not enough yet waiting. And then it's like, okay, sending 611 00:37:09,930 --> 00:37:13,800 payments, sending completes, like, Oh, this is so nice. It 612 00:37:13,800 --> 00:37:14,910 made me feel good. 613 00:37:16,320 --> 00:37:19,290 When I implemented it, that was mainly for debugging, because I 614 00:37:19,290 --> 00:37:22,680 had no other way of seeing what was happening. Aside from 615 00:37:22,680 --> 00:37:27,750 looking at the log off the node and attach it to it. It's nice 616 00:37:27,750 --> 00:37:28,650 to see it building up. 617 00:37:28,680 --> 00:37:33,060 There's your UX man, I just love seeing that. I mean, it can be 618 00:37:33,060 --> 00:37:36,750 as simple as how much I've sent so far. But for some reason, I 619 00:37:36,750 --> 00:37:38,940 just love seeing that log, you know, it's like, hey, while 620 00:37:38,940 --> 00:37:40,980 you're listening, look at what's going on in the background. 621 00:37:40,980 --> 00:37:42,270 Boom. Another another 622 00:37:42,330 --> 00:37:45,150 another least at least, I'm not the only one that does print 623 00:37:45,150 --> 00:37:45,810 debugging. 624 00:37:48,840 --> 00:37:51,180 And not survive who bought it? Yeah, me too. 625 00:37:51,210 --> 00:37:54,420 I mean, I know. You know, I've used plenty of debuggers. But 626 00:37:54,420 --> 00:37:57,150 I'm like, I just keep falling back to it's so easy just to 627 00:37:57,150 --> 00:37:59,820 drop printf in there and just move on with my life, you know, 628 00:38:00,150 --> 00:38:00,870 for sure. 629 00:38:00,990 --> 00:38:05,670 Yeah. Yeah. So the Yeah, that that's gonna be a challenge, I 630 00:38:05,670 --> 00:38:09,540 guess, how do you present this to the users? Because now what I 631 00:38:09,540 --> 00:38:12,360 am doing is basically am cumulating based on the nodes. 632 00:38:12,360 --> 00:38:17,460 And and I already introduced this custom record, because I am 633 00:38:17,460 --> 00:38:21,090 using LMP to get the 1% Commission. Did you 634 00:38:21,090 --> 00:38:24,240 see that? A? Did you see that? In the documentation that I 635 00:38:24,240 --> 00:38:26,040 posted? Yesterday? I put the custom rec? 636 00:38:26,040 --> 00:38:28,770 No, I didn't see the documentation yet. But I'm very 637 00:38:28,770 --> 00:38:29,670 curious to see that. 638 00:38:30,180 --> 00:38:33,030 Yeah, I mean, it's nothing groundbreaking. I'm just trying 639 00:38:33,030 --> 00:38:36,510 to formalize what you what did what you had talked about 640 00:38:36,510 --> 00:38:40,710 earlier, it's just a custom key and a custom value. And it's 641 00:38:40,710 --> 00:38:43,650 just, they're just optional attributes now, and it turned 642 00:38:43,650 --> 00:38:46,410 out that Sphinx is gonna need that too, because they're doing 643 00:38:46,410 --> 00:38:50,580 some stuff that I'm not sure if they're ready to talk about it 644 00:38:50,580 --> 00:38:53,460 yet. But they're polish and they're doing some things. And 645 00:38:53,460 --> 00:38:55,470 he was like, Yeah, can we really need a way to pass some 646 00:38:55,470 --> 00:39:00,660 metadata? And I will, you know, he needs that same thing, too. 647 00:39:00,660 --> 00:39:03,030 So let's just go ahead and formalize this, how 648 00:39:03,030 --> 00:39:04,740 we do it. Yeah. 649 00:39:04,770 --> 00:39:08,820 And then the custom, because because we're that, you know, 650 00:39:08,820 --> 00:39:11,670 baton around this idea of putting, where do you put all in 651 00:39:11,670 --> 00:39:16,020 the string with a delimiter, or Nino? And I think they and you 652 00:39:16,020 --> 00:39:18,660 both were just like, No, it's just easier to do attributes. 653 00:39:19,320 --> 00:39:21,060 And so hopefully, that'll work for you. 654 00:39:22,260 --> 00:39:26,760 No, I think it'll work. As long as we have at least one custom 655 00:39:26,760 --> 00:39:30,630 record that we can put there with one key and one value. That 656 00:39:30,630 --> 00:39:33,240 should be sufficient that thing for most cases, and in the 657 00:39:33,240 --> 00:39:36,780 future, if we need more than one custom record, then we can 658 00:39:36,780 --> 00:39:38,430 expand the namespace somehow. 659 00:39:39,480 --> 00:39:43,800 You said that you were using something to get the 1% 660 00:39:43,800 --> 00:39:45,960 Commission. Can you just explain what what you're talking? I 661 00:39:45,990 --> 00:39:48,300 think I know what you're talking about, but how that works, what 662 00:39:48,300 --> 00:39:48,990 you're doing there? 663 00:39:50,070 --> 00:39:56,460 Yeah, so basically, we currently have the split that right before 664 00:39:56,460 --> 00:40:00,450 it didn't implement thinking that it had to be 100% Some of 665 00:40:00,450 --> 00:40:04,530 the splits, so it was already treating it as chairs. And what 666 00:40:04,530 --> 00:40:11,940 I do is, I basically normalize it in a way that I will that the 667 00:40:11,940 --> 00:40:15,630 shares will now sum up to 99, let's say and then they take 668 00:40:15,630 --> 00:40:22,680 this 1%. And I add this as one split that sends it to Ellen pay 669 00:40:23,130 --> 00:40:28,830 with this custom record that it identifies the wallet. Right? 670 00:40:29,850 --> 00:40:33,990 Yep. And and the idea, I guess, for the future is that this is 671 00:40:33,990 --> 00:40:37,740 what Dave was mentioning that in the namespace, we can also 672 00:40:37,740 --> 00:40:42,690 support these nodes that have like veered to a wallet on top 673 00:40:42,720 --> 00:40:47,070 based on customer records. And so this is partially implemented 674 00:40:47,070 --> 00:40:51,090 already in BOD station, because I am using to get my 1%. But 675 00:40:51,090 --> 00:40:55,170 once we have this in the index, and also in the namespace, then 676 00:40:55,170 --> 00:40:59,610 I can also parse this, and anyone could could use a wallet 677 00:40:59,610 --> 00:41:03,960 like Ellen pay to also get paid, which I think it's a big deal, 678 00:41:03,960 --> 00:41:08,010 because it will also make the onboarding for podcasters. 679 00:41:08,040 --> 00:41:10,950 matches your index. Yes. Much. Very important. 680 00:41:10,980 --> 00:41:11,970 Yeah. Much easier. 681 00:41:12,029 --> 00:41:16,829 So what do you what do you need? You mentioned the other day, I 682 00:41:16,829 --> 00:41:20,879 think, on the on the masculine that you're needing feed, that 683 00:41:20,879 --> 00:41:22,769 they would implement that so that you could test it? 684 00:41:23,700 --> 00:41:27,270 No, no, that is very easy. For me, I can produce a feed myself, 685 00:41:27,270 --> 00:41:31,440 I was just thinking about somebody that's actually like a 686 00:41:31,440 --> 00:41:34,860 podcaster. That will use it productively like, because it's 687 00:41:34,860 --> 00:41:38,070 so easy to do the onboarding, that if somebody is interested, 688 00:41:38,190 --> 00:41:42,930 then it will be a very good use case. Okay, well, 689 00:41:42,930 --> 00:41:44,640 I'm a podcaster. 690 00:41:45,930 --> 00:41:50,550 Both if you want to, but to switch now to LMP. It's for the 691 00:41:50,550 --> 00:41:51,210 receiving end. 692 00:41:51,540 --> 00:41:54,090 Yeah, I haven't I haven't lm pay wallet. 693 00:41:55,230 --> 00:41:59,490 yet. You could, well, maybe what you could do is but part of the 694 00:41:59,490 --> 00:42:04,920 split goes to your regular node, and the other part goes to LMP. 695 00:42:05,580 --> 00:42:08,160 That could also be a good way of doing it. 696 00:42:08,280 --> 00:42:12,060 Yeah. So you know, you know, because whatever, whenever we're 697 00:42:12,060 --> 00:42:14,670 doing this, I just say to Dave, Hey, can you switch my note, 698 00:42:14,670 --> 00:42:19,380 again? What I have noticed there's some say yes, yes, 699 00:42:19,380 --> 00:42:23,700 there's some client out there somewhere that is still sending 700 00:42:23,700 --> 00:42:26,880 me or maybe there's some feed out there something in the index 701 00:42:26,880 --> 00:42:33,690 is not, is not changed, because I'm seeing, like a three Satoshi 702 00:42:33,810 --> 00:42:38,100 payment from a Sphinx chat coming through on my on my curry 703 00:42:38,130 --> 00:42:42,270 node to my home node and that we haven't used that in ages. Oh, 704 00:42:42,270 --> 00:42:47,520 so I wonder if it's a caching thing? Or? Or if maybe we didn't 705 00:42:47,520 --> 00:42:50,190 change one of them? I don't know. I would presume you just 706 00:42:50,190 --> 00:42:51,570 do a search and replace. 707 00:42:52,350 --> 00:42:56,310 Yeah, and it was just, it's bit yet. There. I'll change. Oh, 708 00:42:56,310 --> 00:43:00,000 wait. Yeah. If you're searching Yeah, yeah. Know that. I know. 709 00:43:00,000 --> 00:43:03,480 It will do this is my my, my first node to go out to do a 710 00:43:03,480 --> 00:43:07,020 different search. Anyway, doesn't matter. Doesn't matter. 711 00:43:07,020 --> 00:43:10,560 But yeah, I'll we can switch at least one of the shows just just 712 00:43:10,560 --> 00:43:13,290 to see how it doesn't matter. I just change them all. See him 713 00:43:13,290 --> 00:43:15,210 come in. I can't wait to Yeah, we'll try that. We'll let you 714 00:43:15,210 --> 00:43:15,780 know. Gilliam? 715 00:43:15,990 --> 00:43:16,320 Oh, 716 00:43:16,440 --> 00:43:19,020 I'll do that. All right. Cool. 717 00:43:19,590 --> 00:43:23,550 No, I'm a very good guinea pig. Because when I break somebody I 718 00:43:23,550 --> 00:43:24,450 just called Dave. 719 00:43:26,340 --> 00:43:29,490 Yeah, thanks. That's not that's not what I call a good guinea 720 00:43:29,490 --> 00:43:29,760 pig. 721 00:43:31,950 --> 00:43:34,560 Once once that's in the index, just let me know when I will 722 00:43:34,560 --> 00:43:35,190 implement that. 723 00:43:35,940 --> 00:43:39,420 So what do you what are your plans with this? Because, you 724 00:43:39,420 --> 00:43:44,310 know, clearly, there is value flowing to you. That's good. I 725 00:43:44,310 --> 00:43:48,210 mean, we know it's not very much we don't have a lot of, you 726 00:43:48,210 --> 00:43:51,420 know, we're still building everything out. Do you Where do 727 00:43:51,420 --> 00:43:53,010 you see this going for you personally? 728 00:43:54,510 --> 00:43:58,380 Oh, man. That's a difficult question. I didn't, I didn't 729 00:43:58,380 --> 00:43:59,430 think that far. I had 730 00:44:03,719 --> 00:44:06,449 quite a few users that right? I mean, did you have like, over 731 00:44:06,449 --> 00:44:06,719 1000 732 00:44:08,010 --> 00:44:15,060 I have 50,000 installations around the browser. They are 733 00:44:15,870 --> 00:44:19,980 active in the sense that they are installed because they I 734 00:44:19,980 --> 00:44:23,790 think the way that the Chrome Web Store does it, if your 735 00:44:23,790 --> 00:44:26,850 browser tries to get new updates, it counts as an active 736 00:44:26,850 --> 00:44:33,540 installation. In my analytics, it's, I have more or less 1500 737 00:44:34,200 --> 00:44:39,690 active users per day, and 5000 per week and 14,000 per month, 738 00:44:39,690 --> 00:44:45,000 something like that. So I did the math and actually, even if 739 00:44:45,060 --> 00:44:50,400 all of them were were streaming value at 1%, I will be getting 740 00:44:50,400 --> 00:44:55,890 like, I don't know, six $6 a day or something like that. So 741 00:44:57,120 --> 00:45:01,740 unless I can expand my customer base I don't even call them 742 00:45:01,740 --> 00:45:07,440 customers because I mean, it's a hobby project. It's free. It's, 743 00:45:08,430 --> 00:45:11,670 it wouldn't be too much Actually, my, my interest is 744 00:45:11,730 --> 00:45:16,380 kind of a hobby interested in. And also, I always wanted to 745 00:45:16,380 --> 00:45:20,490 have this kind of value for validating for podcasts not for, 746 00:45:20,880 --> 00:45:24,060 like, for me as a consumer of podcast, and also for the 747 00:45:24,060 --> 00:45:30,030 podcasters. Because I, I hate to see the podcasters having to do 748 00:45:30,030 --> 00:45:33,630 advertising and stuff and usually send them it's like, it 749 00:45:33,630 --> 00:45:37,290 doesn't sound natural, and I like ham and it shouldn't be 750 00:45:37,290 --> 00:45:42,810 like that. And, and then yet, you can put your money there. 751 00:45:43,380 --> 00:45:43,950 It's nice. 752 00:45:44,130 --> 00:45:49,080 Let me give you a couple suggestions. free advice. First 753 00:45:49,080 --> 00:45:54,270 of all, if you could implement the boost functionality, I don't 754 00:45:54,270 --> 00:45:56,730 know if you're familiar with it, but on the unswervingly they 755 00:45:56,730 --> 00:46:01,260 have a button you can configure a one time payment just by 756 00:46:01,260 --> 00:46:02,190 hitting that button. 757 00:46:02,640 --> 00:46:05,610 So yeah, that's gonna be hard that it's, it's I'm already 758 00:46:05,610 --> 00:46:08,910 thinking about doing that and putting some big button on the 759 00:46:08,910 --> 00:46:11,010 player very can can boost 760 00:46:11,100 --> 00:46:15,510 Yes, because you will see the difference in your 1% as well. 761 00:46:15,510 --> 00:46:18,000 That's really where the money is being made. I'll be honest with 762 00:46:18,000 --> 00:46:21,150 you at these, because I'm tracking you know, the the index 763 00:46:21,150 --> 00:46:25,680 node, and the index node is doing between I think it's like, 764 00:46:27,120 --> 00:46:32,040 I mean, it's between one and $2, depending on what day of the day 765 00:46:32,040 --> 00:46:35,220 of the week, sometimes it's half. And we really don't have a 766 00:46:35,220 --> 00:46:38,640 lot of people using these things. So, but if I if I go in 767 00:46:38,640 --> 00:46:42,840 and analyze what's really nice, is it and of course this changes 768 00:46:42,840 --> 00:46:45,780 over time as we started this project Bitcoin was what Dave 769 00:46:45,780 --> 00:46:54,060 20,000 Yeah, so you know, the the values have gone up, while 770 00:46:54,060 --> 00:46:57,390 the value sliders have stayed relatively the same. So that 771 00:46:57,390 --> 00:47:01,170 default of five or 10 sets, you know, is looking better than it 772 00:47:01,170 --> 00:47:04,800 used to, but man, it is the boosts and and that'll get you 773 00:47:04,800 --> 00:47:09,030 excited. And and I think being Since you're so far ahead of 774 00:47:09,030 --> 00:47:11,400 everybody. And I know you have your restrictions, but it kind 775 00:47:11,400 --> 00:47:15,270 of makes it cool. The more you can surface of that kind of 776 00:47:15,270 --> 00:47:21,210 stuff, you know when boosts occur, but just the fact that 777 00:47:21,300 --> 00:47:24,870 you as a user are sending some value when you have a tally of 778 00:47:24,870 --> 00:47:27,990 that. And I think it'll make it very exciting. And then there's 779 00:47:27,990 --> 00:47:30,480 something else which may or may not be interesting to you, 780 00:47:30,480 --> 00:47:33,840 because I just came out to it. I saw it today. It's been out for 781 00:47:33,840 --> 00:47:38,400 a couple couple days. Apparently Chrome, and I presume chromium 782 00:47:39,360 --> 00:47:44,910 is looking at implementing some kind of RSS aggregation slash 783 00:47:44,910 --> 00:47:47,730 reader functionality. And they're going to be adding a 784 00:47:47,730 --> 00:47:51,450 follow button, so that you can fall into what's the smartest 785 00:47:51,450 --> 00:47:56,040 thing that that odio ever did before they became Twitter is to 786 00:47:57,330 --> 00:47:59,850 you know, so instead of subscribed to this website that 787 00:47:59,850 --> 00:48:03,660 saying follow, and the thinking is that this is some kind of 788 00:48:04,230 --> 00:48:07,710 under the hood, you know, reader that they're putting in there. 789 00:48:08,130 --> 00:48:12,780 And my feeling is, somehow it makes sense for you to also look 790 00:48:12,780 --> 00:48:15,450 at how you could do streaming value for value payments for 791 00:48:15,450 --> 00:48:17,100 people reading articles. 792 00:48:18,000 --> 00:48:20,130 Oh, yeah. Yeah, that 793 00:48:20,130 --> 00:48:25,080 that will be interesting. I mean, I have seen like, 794 00:48:25,080 --> 00:48:29,580 sometimes I see text there on the UI of pod station because 795 00:48:29,910 --> 00:48:34,980 people sometimes mix in the feed articles and podcasts. Mm hmm. 796 00:48:35,040 --> 00:48:40,890 And yeah, I think for data we'll have to have a bottom button 797 00:48:40,890 --> 00:48:46,890 there that says okay, donate or send this much to to this feed. 798 00:48:46,920 --> 00:48:50,070 I'm thinking I do it on the scroll and you scroll down 799 00:48:50,190 --> 00:48:52,440 halfway through boom payment goes out 800 00:48:53,400 --> 00:48:56,940 Yeah, they're just as just boost or just a bit just to boost 801 00:48:56,940 --> 00:48:57,870 maybe Yeah, 802 00:48:57,900 --> 00:49:01,740 I'm only saying it because somehow when these things start 803 00:49:01,740 --> 00:49:05,910 to happen I see RSS coming back into play you know, there's 804 00:49:06,030 --> 00:49:08,700 there may be a whole nother system that needs to be set up a 805 00:49:08,700 --> 00:49:12,480 whole nother index not maybe not that we're gonna do it but I'm 806 00:49:12,480 --> 00:49:15,390 just saying this shit is happening here and with all the 807 00:49:15,810 --> 00:49:19,170 all the deep platforming all the just call it what it is 808 00:49:19,170 --> 00:49:21,510 censorship if you got advertising you're being 809 00:49:21,510 --> 00:49:24,930 censored one way or the other. There's a movement man and and 810 00:49:24,930 --> 00:49:29,940 we are timing for once in my life is probably spot on. This 811 00:49:29,940 --> 00:49:31,800 everyone is looking for alternatives 812 00:49:31,860 --> 00:49:35,400 you've got have so you know if you're, if you're a developer 813 00:49:35,400 --> 00:49:40,440 who can swing getting something as complicated as this time 814 00:49:40,440 --> 00:49:45,660 interval Based Payment Kissin stuff working, then something 815 00:49:45,660 --> 00:49:49,920 like paying like boosting for an article that is like dead simple 816 00:49:49,920 --> 00:49:51,060 compared to this man. 817 00:49:51,300 --> 00:49:54,630 It's not complicated. Now that part is the easy part. 818 00:49:56,460 --> 00:49:58,680 Value block and all that stuff. You know that's still neat. 819 00:49:58,680 --> 00:49:59,280 Yeah. 820 00:50:00,000 --> 00:50:03,330 You know, the thing that the complicated part is like, 821 00:50:03,870 --> 00:50:07,770 building something attractive, that has that functionality, 822 00:50:07,770 --> 00:50:11,250 like building the reader that is nice and have nice features and 823 00:50:11,250 --> 00:50:15,060 that functionality, because I think that's, that's something 824 00:50:15,060 --> 00:50:19,710 very nice, but I think that if you don't have the rest, then 825 00:50:19,710 --> 00:50:23,610 that's not going to fly. It would be a completely different 826 00:50:23,610 --> 00:50:26,760 product. I mean, I wouldn't put it together with pod station, it 827 00:50:26,760 --> 00:50:28,980 would be like a separate extension or something. Oh, 828 00:50:28,980 --> 00:50:32,490 yeah. Yeah. Problem is there is already a lot of other 829 00:50:32,490 --> 00:50:36,810 extensions for that. We'll be competing with them. But yeah, 830 00:50:36,810 --> 00:50:38,820 maybe that will be the differentiator. 831 00:50:39,390 --> 00:50:46,380 substation, call it substantial. capitalize on some of that 832 00:50:46,380 --> 00:50:47,460 substack Mojo. 833 00:50:49,469 --> 00:50:53,519 But I think you guys will want me to focus on the podcasting 834 00:50:53,519 --> 00:50:55,439 part, at least is the 835 00:50:57,540 --> 00:51:00,330 core we want to we want you to focus on 15 different things all 836 00:51:00,330 --> 00:51:01,680 at once. The way we 837 00:51:04,739 --> 00:51:11,489 do I detect some animosity Dave Jones, know that it is the way 838 00:51:11,489 --> 00:51:17,729 we go. Yeah. Okay, let's see, what would did we still have on 839 00:51:17,729 --> 00:51:21,779 deck for Guillermo? He has, he has no plans for the future. He 840 00:51:21,779 --> 00:51:23,879 doesn't know what he's going to do. Okay. 841 00:51:26,489 --> 00:51:33,329 That's the best. If I made plans, and I, before I started 842 00:51:33,329 --> 00:51:40,109 put station, I wouldn't have made it. I prefer to just follow 843 00:51:40,109 --> 00:51:46,769 and it's better. If I start doing plans, I keep up. Well, I 844 00:51:46,769 --> 00:51:46,949 want 845 00:51:46,950 --> 00:51:49,740 to know what you're you're a coder, I want to know what 846 00:51:49,740 --> 00:51:53,700 you're like, what background did you have? But were you 847 00:51:53,700 --> 00:51:56,910 JavaScript from the beginning? Or did you come to Oh, no, 848 00:51:56,910 --> 00:52:02,550 I didn't know. I knew nothing about JavaScript. Actually, from 849 00:52:02,790 --> 00:52:06,330 the all the times I tried to do web development before I kind of 850 00:52:06,360 --> 00:52:08,010 failed. Okay, wait, I'm 851 00:52:08,010 --> 00:52:11,850 gonna guess I'm gonna guess what your what your language was 852 00:52:11,910 --> 00:52:15,090 before? Oh, I doubt you're gonna get it. But let's Oh, that's a 853 00:52:15,090 --> 00:52:15,660 challenge. 854 00:52:16,920 --> 00:52:21,240 So you said it was not web related? I'm going to say that 855 00:52:21,240 --> 00:52:27,000 it had something to do with embedded industrial control. 856 00:52:27,930 --> 00:52:32,580 No, no. So in the very beginning, so the first half of 857 00:52:32,580 --> 00:52:38,040 my career, let's say I was coding in c++. So you know, this 858 00:52:38,340 --> 00:52:42,360 very famous design software. I don't know exactly how it's 859 00:52:42,360 --> 00:52:44,970 pronounced in English. I think it's out to cat or something. 860 00:52:45,330 --> 00:52:51,210 Yes, cat. Yeah, we saw I work it for a company that did some 861 00:52:51,210 --> 00:52:55,620 extensions for AutoCAD. And we did that in c++. Is your 862 00:52:55,620 --> 00:52:56,310 extension 863 00:52:56,310 --> 00:52:58,380 background? Oh, yeah. I 864 00:52:58,380 --> 00:53:00,540 never thought about that. But yeah, that's my extension 865 00:53:00,540 --> 00:53:06,600 background. And then I moved into this. Big companies SAP, 866 00:53:06,600 --> 00:53:09,690 maybe you've heard about it is more in the enterprise world 867 00:53:09,690 --> 00:53:14,460 course. And, and they had a very proprietary still have 868 00:53:14,490 --> 00:53:18,900 proprietary platform and this language up, it's called, and 869 00:53:18,900 --> 00:53:22,530 it's only used in this context. So yeah, never heard of that. 870 00:53:22,530 --> 00:53:28,110 Yeah. Yeah, but But the thing is, the I mentioned before, they 871 00:53:28,110 --> 00:53:33,000 had this internal tool, and it was, this was a web tool. And it 872 00:53:33,000 --> 00:53:36,000 was coded, of course, in JavaScript, but we found guler j 873 00:53:36,000 --> 00:53:39,180 s. So the first one point something version of Angular, 874 00:53:39,510 --> 00:53:43,350 and I learned a little bit of it, to do an extension on that 875 00:53:43,350 --> 00:53:48,540 too, for something I needed. Again, an extension. And that 876 00:53:48,540 --> 00:53:53,550 was how I started and then I started, what station first we 877 00:53:53,550 --> 00:53:56,460 fought Angular. And then I said, Okay, I'm going to use this. And 878 00:53:56,460 --> 00:54:02,460 it's still using AngularJS. So, and I am thinking about moving 879 00:54:02,460 --> 00:54:06,180 little by little maybe to react things. It's so popular now. 880 00:54:06,510 --> 00:54:10,890 Yeah. But the thing is, there is I wouldn't even say there is a 881 00:54:10,890 --> 00:54:14,640 stack or something. What do you get in the browser is what I 882 00:54:14,640 --> 00:54:18,000 call there is no transpiling. There's no bundling. There's no 883 00:54:18,000 --> 00:54:22,560 nothing. It's like less than one less. And although I love that, 884 00:54:22,590 --> 00:54:25,740 it's starting to hit some limitations. So I'm thinking now 885 00:54:25,740 --> 00:54:30,120 about moving to a more modern stack and putting maybe some 886 00:54:30,150 --> 00:54:33,600 TypeScript to get me some type safety and all that kind of 887 00:54:33,600 --> 00:54:38,250 stuff, some bundling. So I have to investigate. There is a bit 888 00:54:38,250 --> 00:54:41,400 of technical depth. One of the reasons I want to look into that 889 00:54:41,760 --> 00:54:45,720 is because Chrome is moving the extension format now to this 890 00:54:45,720 --> 00:54:50,040 manifest v3, and there's a lot of incompatible things. And we 891 00:54:50,040 --> 00:54:52,260 will eventually have to move because they will deprecate the 892 00:54:52,260 --> 00:54:53,730 version two. did that. 893 00:54:54,210 --> 00:54:55,710 Did that break a bunch of stuff for you? 894 00:54:56,549 --> 00:54:59,999 bunch of stuff and one very important thing. I cannot wait 895 00:54:59,999 --> 00:55:03,119 The audio from the background anymore. So I don't know if 896 00:55:03,119 --> 00:55:07,769 that's how you use it use it, Adam. But a lot of users, they 897 00:55:07,769 --> 00:55:10,259 play it and they close the tab and it keeps playing in the 898 00:55:10,259 --> 00:55:14,429 background. And that's something I cannot do with the mp3 899 00:55:14,429 --> 00:55:17,639 anymore. There is already an open feature request, but God 900 00:55:17,639 --> 00:55:20,189 knows when to look at it. No, I 901 00:55:21,120 --> 00:55:24,960 don't close the tab. I like keeping it open. All right, 902 00:55:25,020 --> 00:55:28,920 that's just me. The only thing I I'd love for more people to try 903 00:55:28,920 --> 00:55:33,660 this out. Have you considered a little more documentation for 904 00:55:33,660 --> 00:55:36,630 people who want to try it your experimental section of the 905 00:55:36,630 --> 00:55:37,320 options? 906 00:55:37,920 --> 00:55:38,790 Yeah, I 907 00:55:38,790 --> 00:55:43,950 have to do that and put a link in the in the options. I I did 908 00:55:43,950 --> 00:55:47,430 everything I did in the very rushed away just to get it out 909 00:55:47,430 --> 00:55:51,330 there. But I definitely have to do some some more comprehensive 910 00:55:51,330 --> 00:55:52,050 documentation. 911 00:55:52,080 --> 00:55:55,350 Yeah. Because Because I love promoting stuff. So you know, 912 00:55:55,350 --> 00:55:57,900 whenever I can make it as simple as possible for the people who 913 00:55:57,900 --> 00:56:01,710 are going to pick it up, so they don't get too frustrated. So as 914 00:56:01,710 --> 00:56:04,530 we said at the beginning, you know, whenever you need a PR 915 00:56:04,530 --> 00:56:05,850 push, let me know. 916 00:56:07,410 --> 00:56:09,990 Right? How long When did you first release? busstation? How 917 00:56:09,990 --> 00:56:11,040 long has it been out? 918 00:56:11,879 --> 00:56:17,519 It's a long time. First time was 2015. So that's been the middle 919 00:56:17,519 --> 00:56:19,829 of 2015 mature is 920 00:56:19,830 --> 00:56:20,820 your codebase 921 00:56:21,600 --> 00:56:26,460 I have been maintaining it for quite some time. And it's it's 922 00:56:26,460 --> 00:56:32,820 mature. It's I want to say I am ashamed. What What is Terry? I 923 00:56:32,820 --> 00:56:35,520 couldn't have done it better. But it was my learning project. 924 00:56:36,030 --> 00:56:39,570 Yeah, but when you have a pet project and you have limited 925 00:56:39,570 --> 00:56:43,110 time, you have to accept that you are going to have some cut 926 00:56:43,110 --> 00:56:47,220 some corners. They're all in all it's I think it's a good code 927 00:56:47,220 --> 00:56:47,610 base. 928 00:56:48,359 --> 00:56:51,149 Okay, I'm gonna I'm gonna have to write a review. Because the 929 00:56:51,149 --> 00:56:57,389 Chrome Web stores like not enough with 2018 and now we got 930 00:56:57,389 --> 00:57:00,659 to do some either some 2020s there people like it. Look at 931 00:57:00,659 --> 00:57:01,109 this. 932 00:57:02,070 --> 00:57:06,090 Oh, yeah, that I mean, people do that. Yeah, that leaves reviews 933 00:57:06,120 --> 00:57:11,280 in the parties say the rating is up the roof. It means 4.0 you 934 00:57:11,280 --> 00:57:13,650 got four. Yeah, you got over 4.5 935 00:57:14,430 --> 00:57:16,590 Yeah, yeah, it's not bad. No, it's 936 00:57:16,590 --> 00:57:18,810 excellent. Outstanding. Very nice. It 937 00:57:18,870 --> 00:57:21,750 so do you get contacted with people wanting you to take their 938 00:57:21,750 --> 00:57:23,640 podcast off your pot station? 939 00:57:26,610 --> 00:57:31,950 never I never got that I was reading to threaten the monster 940 00:57:31,950 --> 00:57:37,020 done. Yeah, from Martin they're surprised nobody ever asked to 941 00:57:37,020 --> 00:57:40,410 get something removed from anybody draw you a picture and 942 00:57:40,410 --> 00:57:45,660 crayon of their of your logo. That's interesting. Actually, 943 00:57:46,500 --> 00:57:46,920 that 944 00:57:47,370 --> 00:57:50,250 happens that immediately made me think it was comic strip blogger 945 00:57:50,250 --> 00:57:56,040 in disguise. Okay, he's drawing 946 00:57:59,460 --> 00:58:03,090 what happens from time to time and I get random emails of 947 00:58:03,090 --> 00:58:06,150 people asking do you want to sell but station and they don't 948 00:58:06,150 --> 00:58:09,360 even have an email from a company It's like he may we may 949 00:58:09,360 --> 00:58:12,360 or they say are from a company and stuff like that? Oh, yeah. 950 00:58:12,900 --> 00:58:17,190 And a few people we got back to the ones that were a little bit 951 00:58:17,190 --> 00:58:21,810 more serious. Or look at more series at least. And one guy 952 00:58:21,810 --> 00:58:24,270 offered me like 400 bucks and 953 00:58:26,160 --> 00:58:27,300 I would buy it for 954 00:58:30,480 --> 00:58:32,250 five I'll pay five right now. 955 00:58:33,390 --> 00:58:34,590 I'll pick him up pitching 956 00:58:35,310 --> 00:58:36,090 him Bitcoin. 957 00:58:37,020 --> 00:58:39,990 Come on, you're good. You're gonna buy my hobby? What I'm 958 00:58:39,990 --> 00:58:41,310 gonna do with my free time. 959 00:58:44,430 --> 00:58:47,040 Dude, I'll pay you $400 not to email me anymore. 960 00:58:49,110 --> 00:58:54,120 Well, you know, since you are here, we do have something we 961 00:58:54,120 --> 00:58:58,830 need to do from time to time on the show. And I think it really 962 00:58:58,830 --> 00:59:02,490 pertains to you because I'm very interested. If you are feeling 963 00:59:04,860 --> 00:59:06,360 hot, named Oh, 964 00:59:06,360 --> 00:59:09,810 yeah. Are you feeling the name space? 965 00:59:10,230 --> 00:59:17,010 And I already mentioned namespace twice. where's where's 966 00:59:17,010 --> 00:59:19,470 the Jingo? dropping clues? 967 00:59:19,469 --> 00:59:23,549 You got it? Brother? You got it? So obviously, you support 968 00:59:23,609 --> 00:59:26,789 portions of the namespace. What are the other? It's kind of an 969 00:59:26,789 --> 00:59:30,329 interesting app in that regard. I think, you know, pod station 970 00:59:30,329 --> 00:59:33,299 is something that a lot of people want because it's out of 971 00:59:33,299 --> 00:59:36,569 the way and because it's kind of in the background. What are your 972 00:59:36,569 --> 00:59:37,199 thoughts? 973 00:59:38,580 --> 00:59:44,550 Yeah, so I think I only support funding and Bella. Bella was 974 00:59:44,580 --> 00:59:47,130 very experimental funding. I think I was the one that 975 00:59:47,130 --> 00:59:51,420 suggests that even because I always wanted to make it easy to 976 00:59:51,450 --> 00:59:53,940 hit one button and go to the place where you give money to 977 00:59:53,940 --> 00:59:59,190 the to the podcasters some some of the things I am really not 978 00:59:59,190 --> 01:00:03,510 much into Care location. And I think that there was something 979 01:00:03,510 --> 01:00:10,020 else that was like, I never use no person Personally, I actually 980 01:00:10,020 --> 01:00:14,130 I am into it. I didn't have the time to to engage with the 981 01:00:14,130 --> 01:00:17,940 thing. But there is a lot of nice stuff that uh, that you 982 01:00:17,940 --> 01:00:22,200 could have like search for episodes that somebody 983 01:00:22,200 --> 01:00:25,680 participated in and then it's getting for multiple feeds. I 984 01:00:25,680 --> 01:00:30,750 think that's a nice thing, or, or even is that you don't search 985 01:00:31,020 --> 01:00:34,290 directly for that person. But I am listening to a podcast and 986 01:00:34,290 --> 01:00:37,350 now Who is this guest and then they click there and then I it 987 01:00:37,350 --> 01:00:41,280 show me episodes from other podcasts. I think that's, that's 988 01:00:41,280 --> 01:00:45,990 a very interesting one. Actually, before this, this 989 01:00:45,990 --> 01:00:49,980 namespace, I have created one namespace that I never advertise 990 01:00:49,980 --> 01:00:52,890 it too much. And I never did anything with it. That was 991 01:00:52,890 --> 01:00:56,160 called social RSS. And remember, you're linking to 992 01:00:56,160 --> 01:00:57,150 that. Yeah. Saw that? 993 01:00:57,240 --> 01:01:01,350 Yeah, I think Yeah, exactly. And I think when I proposed the 994 01:01:01,350 --> 01:01:05,340 funding I linked to it because in that one, I already had the 995 01:01:05,340 --> 01:01:09,480 funding or monetization or something like that. And and 996 01:01:09,480 --> 01:01:15,000 also links to the social handles off the podcast and also from 997 01:01:15,000 --> 01:01:18,150 the participants and stuff like that. But it was a bit 998 01:01:18,150 --> 01:01:22,170 complicated. Like I define it i think i only defined it 999 01:01:22,170 --> 01:01:25,860 participant and then there was like permanent participant and 1000 01:01:26,130 --> 01:01:29,910 guest or something like that. And also something that was like 1001 01:01:29,910 --> 01:01:34,350 a reference to a participant because you could find it on the 1002 01:01:34,380 --> 01:01:38,670 channel and then in the items but you didn't want to duplicate 1003 01:01:38,670 --> 01:01:42,060 everything on the item so your reference to the to the one in 1004 01:01:42,060 --> 01:01:45,510 the channel it's a bit more complicated for parsing and 1005 01:01:45,510 --> 01:01:49,860 stuff but it saves you let's say if you are building the thing 1006 01:01:49,860 --> 01:01:54,450 manually and it saves you a bit space in the feed I think that 1007 01:01:54,450 --> 01:01:58,230 channel sorry that the chapters and the transcription they are 1008 01:01:58,230 --> 01:02:01,890 nice I want to implement at some point they just didn't have the 1009 01:02:01,890 --> 01:02:06,330 time and also these are a bit more demanding to me because I 1010 01:02:06,360 --> 01:02:09,810 think on the user experience and then that's the part where it 1011 01:02:09,840 --> 01:02:12,600 always take a little bit more time I didn't know how he does 1012 01:02:12,600 --> 01:02:16,380 because he comes up like you You think of a tag and he comes up 1013 01:02:16,380 --> 01:02:20,850 with in pod friend there is already a very nice user 1014 01:02:20,850 --> 01:02:21,690 experience where it 1015 01:02:21,900 --> 01:02:25,860 does UI guys like him drive me crazy because I'm late to my 1016 01:02:25,860 --> 01:02:28,350 head against the wall trying to make something look like a 1017 01:02:28,350 --> 01:02:30,840 button look pretty and you know they can do it in like five 1018 01:02:30,840 --> 01:02:31,140 minutes. 1019 01:02:32,489 --> 01:02:35,729 One station is not minimalistic just because of a design 1020 01:02:35,729 --> 01:02:39,749 decision. It was by my lack of skill. I couldn't do something 1021 01:02:39,749 --> 01:02:40,109 more 1022 01:02:41,670 --> 01:02:42,570 failing human 1023 01:02:42,750 --> 01:02:44,910 and it's actually a big advantage because a lot of 1024 01:02:44,910 --> 01:02:49,710 people that give reviews say wow that's very simple and 1025 01:02:49,710 --> 01:02:52,620 minimalistic and Stephanie yeah because that's what I can do. 1026 01:02:53,850 --> 01:02:57,000 And I like to keep it that way so I always think very carefully 1027 01:02:57,000 --> 01:03:00,240 before doing changes Adams still use it for his email 1028 01:03:00,270 --> 01:03:00,840 I do 1029 01:03:02,070 --> 01:03:03,600 I have no idea what that is. 1030 01:03:04,770 --> 01:03:07,560 Yeah, it's a great command line email I have a tricked out have 1031 01:03:07,560 --> 01:03:08,100 scripted 1032 01:03:08,550 --> 01:03:11,850 you know I may have used it one time long oh 1033 01:03:11,850 --> 01:03:20,010 I'm sure I'm sure we all use it at one point so I was just 1034 01:03:20,100 --> 01:03:22,770 messing around while you guys were talking I don't see the I 1035 01:03:22,770 --> 01:03:29,910 don't think the the funding tag works or at least not what I 1036 01:03:29,910 --> 01:03:35,340 wasn't I whenever I click on the donate it goes to you which I'm 1037 01:03:35,340 --> 01:03:38,370 happy to donate to you but stop now it's like a lot in the army. 1038 01:03:38,430 --> 01:03:38,790 Yeah. 1039 01:03:42,330 --> 01:03:46,140 I need to work in the UX there actually I want to if you go 1040 01:03:46,140 --> 01:03:50,850 into the list of podcasts you will see a bit of hidden not 1041 01:03:50,850 --> 01:03:55,920 hidden but it's it's there like if you look in the podcasting 1042 01:03:55,920 --> 01:03:59,850 2.0 you will see like fun this podcast or something, but it 1043 01:03:59,850 --> 01:04:02,670 doesn't call your attention. I really need to do something 1044 01:04:02,670 --> 01:04:06,210 about that. I think at least what I wanted to do. First I 1045 01:04:06,210 --> 01:04:09,750 want to make that maybe the same yellow that I have in the donate 1046 01:04:09,750 --> 01:04:14,160 button. The main Yeah, that was me. Yeah, that went home. And 1047 01:04:14,160 --> 01:04:18,780 when you play an episode of both cast that test funding I want to 1048 01:04:18,780 --> 01:04:21,270 show a button on the player too. So that guy 1049 01:04:22,290 --> 01:04:26,460 what's really sexy though, is if you're using pod station and the 1050 01:04:26,460 --> 01:04:30,000 flip over to your Ellen pay wallet. It's kind of cool 1051 01:04:30,000 --> 01:04:33,960 because now you have to refresh but it shows you the the the 1052 01:04:33,960 --> 01:04:37,410 share split payment shows you when it went what time. I mean, 1053 01:04:37,410 --> 01:04:40,920 it would take a small, small amount to translate that and say 1054 01:04:40,920 --> 01:04:44,490 oh, this is part of the podcasting 2.0 podcast you were 1055 01:04:44,490 --> 01:04:46,500 listening to. I just find it exciting. 1056 01:04:47,550 --> 01:04:48,930 You mean the log so 1057 01:04:49,920 --> 01:04:53,430 I'm in I'm in Ellen pay just looking at the LM pay, wallet 1058 01:04:53,430 --> 01:04:55,890 pay. Okay, yeah, kind of technical. 1059 01:04:57,180 --> 01:04:59,610 So you're seeing it going out and then on one side and coming 1060 01:04:59,610 --> 01:05:00,450 in on the other said 1061 01:05:02,520 --> 01:05:08,910 no, because I, my incoming is to my voltage node. That's my 1062 01:05:08,910 --> 01:05:12,810 personal and this is just I put 10,000 satoshis every time on 1063 01:05:12,810 --> 01:05:18,540 the LM pay wallet. And I guess, yeah, it's, it's, I just can't 1064 01:05:18,540 --> 01:05:20,880 tell you how much I appreciate that you're doing this to the 1065 01:05:20,880 --> 01:05:25,050 airmen it's it's, it's so nice to have a stable operating 1066 01:05:26,340 --> 01:05:29,340 implementation of this outside of what we already had with a 1067 01:05:29,340 --> 01:05:33,120 proof of concept with swings who are also doing their upgrades. I 1068 01:05:33,120 --> 01:05:36,000 just love it, man. And I hope we can get more people to use it. 1069 01:05:36,720 --> 01:05:37,800 Yeah, I hope so. Is 1070 01:05:37,800 --> 01:05:42,030 there nice to implement this? It's now just a I have to think 1071 01:05:42,030 --> 01:05:44,790 on how to make it more accessible. On the namespace 1072 01:05:44,790 --> 01:05:45,450 side, what? 1073 01:05:45,780 --> 01:05:49,530 Are there any tag tags that are not in there that you're that 1074 01:05:49,530 --> 01:05:53,040 you really think would be a good thing to focus on for like phase 1075 01:05:53,040 --> 01:05:53,430 three? 1076 01:05:54,960 --> 01:05:58,650 Oh, not from the top of my mind, though, I was so focused on this 1077 01:05:58,650 --> 01:06:01,590 valid thing that I kind of forgot a little bit about the 1078 01:06:01,740 --> 01:06:03,630 other ones. Because I'm 1079 01:06:03,630 --> 01:06:08,070 really thinking about the alternate enclosure tag, it 1080 01:06:08,070 --> 01:06:11,610 really seems to be Oh, that one is nice need to be able to do to 1081 01:06:11,610 --> 01:06:14,550 flip it, like be able to flip back and forth between audio and 1082 01:06:14,550 --> 01:06:17,340 video in the same feed and not have to produce two feeds for 1083 01:06:17,340 --> 01:06:19,380 it. That seems like a great yeah. 1084 01:06:20,550 --> 01:06:24,810 Yeah, I think one big use case for that is the quality of the 1085 01:06:24,810 --> 01:06:27,810 audio, or bitrate or however you want to call it, I think, 1086 01:06:29,010 --> 01:06:32,460 especially for people that are listening on the mobio or stuff 1087 01:06:32,460 --> 01:06:35,820 like that, that there are many countries where the bandwidth is 1088 01:06:35,820 --> 01:06:39,660 not great. So So having this all in one feed, and then you can 1089 01:06:39,660 --> 01:06:43,950 select like a default quality and then it falls back to that 1090 01:06:43,980 --> 01:06:44,700 to be great. 1091 01:06:46,140 --> 01:06:48,870 What is it is bandwidth, okay, in Brazil? 1092 01:06:49,949 --> 01:06:53,909 for desktop, sorry, for not desktop, but if you use it at 1093 01:06:53,909 --> 01:06:57,209 home with your Wi Fi and landline? It's it's quite okay. 1094 01:06:57,239 --> 01:07:01,679 And it's unlimited. You don't have to worry about that. And 1095 01:07:01,739 --> 01:07:06,419 you don't have mobile, it's it's a bit more expensive and a bit 1096 01:07:06,419 --> 01:07:10,259 more limited. So I think most people probably downloaded 1097 01:07:10,259 --> 01:07:12,929 before, or offline usage. 1098 01:07:13,620 --> 01:07:17,130 Okay. Yeah, I would think that that can be easily, you know, 1099 01:07:17,130 --> 01:07:21,240 like an auto selection, too. If you're, if the app detects that 1100 01:07:21,240 --> 01:07:24,480 the rate, you know, it's yellow, and it's running out of buffers, 1101 01:07:24,480 --> 01:07:26,670 that means he can just automatically downgrade to the 1102 01:07:26,670 --> 01:07:27,690 lower audio quality. 1103 01:07:28,230 --> 01:07:32,070 Yeah, it could do that. Yeah. So it's kind of this automatic 1104 01:07:32,070 --> 01:07:34,230 quality on YouTube and stuff like that, that 1105 01:07:34,500 --> 01:07:38,460 adjusts automatically. Are you does your disposition support 1106 01:07:38,460 --> 01:07:42,060 video? Or do you plan on supporting it? No, I 1107 01:07:42,090 --> 01:07:46,350 did a proof of concept once. I have to tweak it a little bit, 1108 01:07:46,350 --> 01:07:49,890 because by default, it plays on the background. So I don't 1109 01:07:49,920 --> 01:07:54,210 render anything on the app. And by the in the video, I of course 1110 01:07:54,210 --> 01:07:57,930 will have to play it, but it on the tab. But there was so little 1111 01:07:57,930 --> 01:08:01,080 demand for that so far, that they never put a lot of effort 1112 01:08:01,080 --> 01:08:01,380 there. 1113 01:08:01,680 --> 01:08:04,830 Especially being a background or kind of thing seems like, 1114 01:08:05,040 --> 01:08:07,500 exactly, yeah. You don't want to foreground Yeah, 1115 01:08:07,560 --> 01:08:11,130 yeah. But I have been thinking more and more about that. And to 1116 01:08:11,130 --> 01:08:15,180 be honest, I don't like YouTube very much. I mean, it's has a 1117 01:08:15,180 --> 01:08:18,660 lot of functionality is great. I even pay the premium thing. But 1118 01:08:18,660 --> 01:08:22,320 I hate the fact that people put all their content in a single 1119 01:08:22,320 --> 01:08:27,330 platform is maddening. And, yes, I cannot understand them. And 1120 01:08:27,360 --> 01:08:32,460 even the big channels that they they could simply say, hey, I 1121 01:08:32,460 --> 01:08:36,330 want to have some leverage. So you know, it's not that hard to 1122 01:08:36,330 --> 01:08:38,160 put in other platforms. And I've been 1123 01:08:38,160 --> 01:08:43,530 looking at this, and I finally understood the problem. And, you 1124 01:08:43,530 --> 01:08:46,650 know, when we started podcast index, and people said, Oh, this 1125 01:08:46,650 --> 01:08:48,870 would be you know, can't wait when you do it for video, and 1126 01:08:48,870 --> 01:08:52,650 I'm sitting there going, but it's, it's already there. But I 1127 01:08:52,650 --> 01:08:57,720 figured out what the problem is. And it's it is it is such a 1128 01:08:58,020 --> 01:09:03,420 monolithic problem from so many angles, that there's almost no 1129 01:09:03,420 --> 01:09:07,440 incentive to solve it. And I shall explain it. If you because 1130 01:09:07,440 --> 01:09:10,710 I have, I've now been playing around for several months with 1131 01:09:11,100 --> 01:09:17,010 buzzsprout with the libsyn with the blueberry. Any others? Those 1132 01:09:17,010 --> 01:09:17,580 are the main ones 1133 01:09:17,610 --> 01:09:18,690 rss.com. 1134 01:09:19,980 --> 01:09:23,970 I haven't haven't used the RSS calm. But I think they'll 1135 01:09:23,970 --> 01:09:28,560 probably have, they all have the same issue. Because of the 1136 01:09:28,560 --> 01:09:31,890 bandwidth and the storage necessary. If you open an 1137 01:09:31,890 --> 01:09:35,070 account with any I think as far as I know, with any of these, 1138 01:09:35,190 --> 01:09:39,570 you have an X number of megabytes or gigabytes, usually 1139 01:09:39,570 --> 01:09:44,310 megabytes to store and at the lowest plan. And they have to 1140 01:09:44,310 --> 01:09:46,740 because they're, you know, well the disk storage is one thing 1141 01:09:46,740 --> 01:09:49,860 that's gotten pretty inexpensive. But if you have an 1142 01:09:49,860 --> 01:09:53,310 episode and it's a gigabyte of video because it's an hour or 1143 01:09:53,370 --> 01:09:55,950 that way, you could compress it a lot more but let's say it's 1144 01:09:55,950 --> 01:10:03,210 half a gig. That's going to cost them A lot more in transfer 1145 01:10:03,210 --> 01:10:07,260 costs, particularly. And so they've they've artificially 1146 01:10:07,260 --> 01:10:12,000 made this inaccessible to people. And people have no idea 1147 01:10:12,000 --> 01:10:14,730 they don't understand why this can't be done. So I just got 1148 01:10:14,730 --> 01:10:16,950 this many megabytes whatever, I can't do video, I guess you 1149 01:10:16,950 --> 01:10:21,720 can't do a video. If we had an alternate storage solution. This 1150 01:10:21,720 --> 01:10:24,870 would be this would revolutionize everything 1151 01:10:24,870 --> 01:10:27,720 overnight. It's just because people have learned over at 1152 01:10:27,720 --> 01:10:30,420 least 10 years, I can upload video, I don't have enough 1153 01:10:30,420 --> 01:10:34,380 space. That's the only reason every player pretty much handles 1154 01:10:34,380 --> 01:10:34,710 it. 1155 01:10:35,760 --> 01:10:36,540 Yeah, yes. 1156 01:10:37,980 --> 01:10:42,450 It's on the hosting side, this is a big problem. And, of 1157 01:10:42,450 --> 01:10:46,260 course, many in YouTube, people were used to a get a video on 1158 01:10:46,260 --> 01:10:48,930 the best quality possible way upload, and they handle 1159 01:10:48,930 --> 01:10:55,350 everything to storage. Forget it, yeah. And then they would 1160 01:10:55,350 --> 01:10:58,380 expect something similar from the hosting like a I upload this 1161 01:10:58,380 --> 01:11:03,030 video, and then you will produce feed with many different 1162 01:11:03,030 --> 01:11:07,680 qualities or even have some way to have this adaptative quality 1163 01:11:07,680 --> 01:11:10,770 with a single URL, I don't know, there's a lot of expectation 1164 01:11:10,770 --> 01:11:13,230 there we fall do is way simpler. And 1165 01:11:13,260 --> 01:11:17,250 yes, but the beauty is the receiving end pretty much 1166 01:11:17,250 --> 01:11:21,810 everybody. Even cellular phones, now it's going to eat up more 1167 01:11:21,840 --> 01:11:24,030 more data, which could be a problem in some countries. But 1168 01:11:24,030 --> 01:11:27,240 in general, the receiving side is set up, you know, I have 1169 01:11:27,240 --> 01:11:31,620 enough bandwidth to to progressively download and start 1170 01:11:31,620 --> 01:11:35,970 playing a video. in almost any device can do that almost any 1171 01:11:35,970 --> 01:11:40,350 connection can do that. It is purely a hosting pricing issue. 1172 01:11:40,710 --> 01:11:44,520 And I and I understand that, I'm just saying I'm repeating this 1173 01:11:44,520 --> 01:11:47,280 because I know they're listening, I understand it's 1174 01:11:47,280 --> 01:11:51,060 scary to give up one of the things that that you're 1175 01:11:51,060 --> 01:11:55,410 providing. But think about how beautiful it will be when for 1176 01:11:55,410 --> 01:12:00,090 your customers, they will seamlessly not know that it's 1177 01:12:00,510 --> 01:12:06,120 distributed in half space, or in ipfs, or whatever it is. And you 1178 01:12:06,120 --> 01:12:11,910 can charge them progressively with small increments for their 1179 01:12:11,910 --> 01:12:14,910 file access instead of button file storage and transfer 1180 01:12:14,910 --> 01:12:18,660 instead of just making it a hard No. And having your user 1181 01:12:18,660 --> 01:12:23,220 interface your user experience be what people pay for. And, and 1182 01:12:23,220 --> 01:12:28,290 yes, YouTube is free. And free comes with a lot of expensive 1183 01:12:28,290 --> 01:12:30,630 downsides if you build a business on it. And all of a 1184 01:12:30,630 --> 01:12:34,020 sudden you get cancelled or any of this stuff. It is it is 1185 01:12:34,020 --> 01:12:37,050 something that we can solve together podcasts index is 1186 01:12:37,050 --> 01:12:44,460 ready, willing and able to be an ipfs node to be a pin node. And 1187 01:12:44,460 --> 01:12:46,800 we can I know and we know there's business models that 1188 01:12:46,800 --> 01:12:50,190 will work. We just have to all kind of do it. And so that's my 1189 01:12:50,190 --> 01:12:51,990 final call out to the hosting companies. 1190 01:12:53,790 --> 01:12:58,650 Yeah, I think it's, it's such a Yeah, I think you're right, I 1191 01:12:58,650 --> 01:13:01,530 think you nailed it. It's the scary part. It's the scary part 1192 01:13:01,530 --> 01:13:03,990 from just an unknown. I mean, you open the floodgates to that. 1193 01:13:03,990 --> 01:13:06,060 And it's like, Ah, man, what, 1194 01:13:06,360 --> 01:13:10,290 but also, if it works, the gamble, if it works, you can 1195 01:13:10,290 --> 01:13:14,460 double your profit, maybe triple. Yeah, think about that. 1196 01:13:15,060 --> 01:13:17,040 What's that, you know, that it's, there's got to be 1197 01:13:17,040 --> 01:13:22,710 somewhere that you've got to almost go to that next level up 1198 01:13:22,740 --> 01:13:26,940 in order to that's where Google, that's where Google and you 1199 01:13:26,940 --> 01:13:29,760 know, CloudFlare and these guys, they're, they're sort of they 1200 01:13:29,760 --> 01:13:34,590 have they have elevated their, their business up to the next 1201 01:13:34,590 --> 01:13:40,230 level of internet infrastructure to where the bandwidth is not so 1202 01:13:40,230 --> 01:13:42,480 much of a problem, because they're all their virtue there. 1203 01:13:42,630 --> 01:13:45,810 They're living in the carrier domain anyway. Yes, they are. 1204 01:13:46,110 --> 01:13:49,050 Yeah. And so they, they just really have a strong advantage. 1205 01:13:49,200 --> 01:13:53,220 And it does that if you're anywhere in any tier below that 1206 01:13:53,610 --> 01:13:57,060 you have to play in their playground. Well, how about 1207 01:13:57,060 --> 01:13:57,510 this? 1208 01:13:59,160 --> 01:14:01,560 So yeah, I'm very familiar with with what they do, you know, 1209 01:14:01,590 --> 01:14:04,650 just like Netflix, you know, Netflix is not streaming from 1210 01:14:04,650 --> 01:14:08,100 one server in California, obviously. But they get boxes, 1211 01:14:08,100 --> 01:14:12,750 they drop boxes into exchanges, and, and then into cable 1212 01:14:12,750 --> 01:14:16,260 companies themselves, and they will. And they'll pick it up 1213 01:14:16,260 --> 01:14:16,830 from there. 1214 01:14:17,700 --> 01:14:18,840 That's the way to do it. And 1215 01:14:18,840 --> 01:14:25,080 but we can use the same basic system ology as Microsoft uses 1216 01:14:25,080 --> 01:14:30,030 for their updates, where if you're on a segment of, of a 1217 01:14:30,030 --> 01:14:34,350 cable network, you should be able to be serving portions of 1218 01:14:34,380 --> 01:14:39,060 video files to other people on that network. Yeah, and the 1219 01:14:39,060 --> 01:14:42,270 technologies are there all of its there, we just have to do 1220 01:14:42,270 --> 01:14:47,340 it. And I'd hate to have to do it and then have to become a 1221 01:14:47,340 --> 01:14:50,280 hosting provider to do it. I don't want that. 1222 01:14:50,400 --> 01:14:55,800 I don't know what would be really cool would be if we go 1223 01:14:55,800 --> 01:15:01,230 into this ipfs game and people can have like In their houses, 1224 01:15:01,890 --> 01:15:05,160 piece of storage where the content that they consume, they 1225 01:15:05,160 --> 01:15:09,240 also store and serve there and plug this into the developer of 1226 01:15:09,240 --> 01:15:12,690 Hello thing with the lightning. Yep. Imagine you could get a 1227 01:15:12,690 --> 01:15:16,770 piece for the hosting. And that's because you don't know 1228 01:15:16,770 --> 01:15:20,310 where you are hosting from. And you cannot put this into the RSS 1229 01:15:20,310 --> 01:15:24,450 directly. But I mean, eventually we we can think about 1230 01:15:25,590 --> 01:15:31,170 ipfs. And Dave will correct me if I'm wrong. ipfs has a way to 1231 01:15:31,200 --> 01:15:34,860 interact. And we could do this with when we talked about it a 1232 01:15:34,860 --> 01:15:39,030 million times L SATs milset l SATs where there's a payment for 1233 01:15:39,030 --> 01:15:46,200 the for the API exchange, and it's in satoshis. Which is just 1234 01:15:46,230 --> 01:15:50,850 beautifully simple. I was met that was with with my my my 1235 01:15:50,850 --> 01:15:54,330 raspy blitz that we were talking about earlier. I just I just hit 1236 01:15:54,330 --> 01:15:58,440 the tour to IP bridge and said, Okay, this is gonna cost you 1237 01:15:58,440 --> 01:16:03,540 24 724 sets every every 24 hours. And I just said yes. I 1238 01:16:03,570 --> 01:16:08,010 never authenticated anything. I never I just said yes. And it 1239 01:16:08,010 --> 01:16:11,040 went because everything was already connected. So this can 1240 01:16:11,040 --> 01:16:14,100 be done the same way for hosting. I think ipfs has that 1241 01:16:14,100 --> 01:16:15,120 built in, doesn't it? Dave? 1242 01:16:15,810 --> 01:16:17,970 I don't think it I don't know that it has I think they're 1243 01:16:17,970 --> 01:16:21,510 using filecoin. What else that isn't? 1244 01:16:21,539 --> 01:16:25,259 No, no, no. But file coin is I don't think it's necessary to 1245 01:16:25,259 --> 01:16:29,579 use file coin as the value mechanism. You can layer on I 1246 01:16:29,579 --> 01:16:33,299 think you can layer anything on top of ipfs Yeah, I think so. If 1247 01:16:33,299 --> 01:16:34,679 not, we'll just make it so 1248 01:16:34,980 --> 01:16:37,530 well. We just need to have that PFS guys on the show and ask him 1249 01:16:37,530 --> 01:16:37,890 about it. 1250 01:16:38,340 --> 01:16:40,020 Who are the ipfs? Guys? 1251 01:16:40,410 --> 01:16:42,150 I don't know. ipfs 1252 01:16:43,380 --> 01:16:44,400 ipfs. Guys, 1253 01:16:44,400 --> 01:16:46,950 hit us up infoed podcast index.org. 1254 01:16:47,670 --> 01:16:50,670 There's always underscore guys, it's there somewhere. 1255 01:16:50,730 --> 01:16:53,190 Speaking of guys, why don't we take a moment Dave to thank 1256 01:16:53,190 --> 01:16:58,620 people who support the podcast index, project podcast in 2.0, 1257 01:16:58,620 --> 01:17:04,680 this podcast and have really been supportive. And we've been 1258 01:17:04,710 --> 01:17:07,860 able to run on donations since the almost since the very 1259 01:17:07,860 --> 01:17:11,850 beginning. If you'd like to support us it's value for value. 1260 01:17:11,850 --> 01:17:14,520 Whatever you get out of this. It may be just like, listen to this 1261 01:17:14,520 --> 01:17:17,100 podcast, you learn a little bit about what's happening. Maybe 1262 01:17:17,100 --> 01:17:20,880 you're a podcaster and you're excited about these features, 1263 01:17:20,910 --> 01:17:24,720 whatever it is. Just turn that into a number and send it back 1264 01:17:24,720 --> 01:17:29,940 to us. You can find our our Donate button. It's hidden in 1265 01:17:29,940 --> 01:17:34,860 pod station. But if you go to podcast index.org scroll down to 1266 01:17:34,860 --> 01:17:38,970 the bottom. Big Red Donate button to hit that up. And Dave 1267 01:17:38,970 --> 01:17:42,690 who can we thank as our supporters for for this week. 1268 01:17:43,530 --> 01:17:45,000 We're podcasting. index.org 1269 01:17:46,080 --> 01:17:51,150 Well, the first speaking of hosting companies rss.com Ah, 1270 01:17:51,180 --> 01:17:56,700 there you go. Bit basement and now and Alberto. They gave us 1271 01:17:57,180 --> 01:17:58,170 $500. 1272 01:17:59,280 --> 01:18:04,020 Wow, man and not only do they they they live up to their name, 1273 01:18:04,020 --> 01:18:09,810 don't say hey rss.com It's ours. It's important. Thank you. Thank 1274 01:18:09,810 --> 01:18:13,860 you guys. So they are very, very nice. 1275 01:18:15,630 --> 01:18:19,320 bins, they sent us a message he says, Adam and Dave here some 1276 01:18:19,320 --> 01:18:23,760 treasure for podcast index. Feel free to convert to SATs and test 1277 01:18:23,760 --> 01:18:28,230 sending to your faves. Might we might we suggest David Norman 1278 01:18:28,230 --> 01:18:32,430 and Martin as a start? Right? Yes, yes. We're working on 1279 01:18:32,430 --> 01:18:35,940 namespace updates. And hope to have some news soon. There's 1280 01:18:35,940 --> 01:18:42,150 your There's your teas from your friends@rss.com podcast hosting 1281 01:18:42,150 --> 01:18:42,780 Alberto and 1282 01:18:42,810 --> 01:18:45,570 wait a minute. What's the T's here? Are they are they teasing 1283 01:18:45,600 --> 01:18:47,130 all kinds of namespace 1284 01:18:47,310 --> 01:18:51,420 things? I don't know. Where work is just as we're working on 1285 01:18:51,420 --> 01:18:53,370 namespace. Okay, I 1286 01:18:53,370 --> 01:18:54,120 love it. 1287 01:18:55,080 --> 01:19:05,400 It says go podcasting. Ah, 1288 01:19:05,400 --> 01:19:09,840 there's the crumble. Everybody loves the crumble. Okay, 1289 01:19:09,870 --> 01:19:19,230 do you know this person? It is Rene. Nigar Nigar spell it KNI 1290 01:19:19,230 --> 01:19:19,950 gg 1291 01:19:21,090 --> 01:19:22,680 canessa. No, I don't think so. 1292 01:19:22,950 --> 01:19:24,990 Can you can you from the Netherlands? 1293 01:19:25,080 --> 01:19:29,040 Is that Dutch? Okay. It could be it looks like it says let me let 1294 01:19:29,040 --> 01:19:33,720 me let me read it. At em gents. I've been listening to na since 1295 01:19:33,720 --> 01:19:40,290 the start on and off. And mo FX on and off. And next these next 1296 01:19:40,290 --> 01:19:45,360 these high quality podcasts a bunch of other ones. The podcast 1297 01:19:45,360 --> 01:19:48,480 in this podcast need to point gnosis to start love how it's 1298 01:19:48,480 --> 01:19:52,080 evolved so far. The new index deserves all the support and 1299 01:19:52,080 --> 01:19:55,590 love it gets. Here's my small part in supporting this Gertz 1300 01:19:55,590 --> 01:19:59,970 from Dan hildur, the Netherlands. Very nice. 1301 01:20:00,000 --> 01:20:00,570 Thank you. 1302 01:20:01,170 --> 01:20:02,730 Greetings, I guess Yes. 1303 01:20:02,760 --> 01:20:07,320 Well in in Dutch, we say crutches. That would be like 1304 01:20:07,320 --> 01:20:13,050 Bruce in German. And, and and somehow that when you say that 1305 01:20:13,110 --> 01:20:17,400 it, it turned into greets gr etc. Is that what it says? Or 1306 01:20:17,400 --> 01:20:17,970 your yard? 1307 01:20:18,180 --> 01:20:19,920 Yes gr Tz. Yeah. 1308 01:20:20,910 --> 01:20:26,970 It's a very Dutch thing to do. Okay. Yeah. Okay. We appreciate 1309 01:20:26,970 --> 01:20:27,420 it. Thank you. 1310 01:20:27,480 --> 01:20:29,700 Yes, that was a he gave us $50. Nice. 1311 01:20:30,660 --> 01:20:31,170 Nice. 1312 01:20:31,320 --> 01:20:36,810 Thank you. I don't understand it says Rene. And then it says Dan 1313 01:20:36,810 --> 01:20:37,290 Helder. 1314 01:20:37,860 --> 01:20:41,940 10 Helder is the place he's from. That's northern Holland. 1315 01:20:42,570 --> 01:20:45,450 been there many times? Alright. So thank you, Renee. 1316 01:20:45,540 --> 01:20:49,200 They have a helicopter landing pad of their military. 1317 01:20:50,250 --> 01:20:56,640 Thomas umstead. He gave us $25. He said you should create a 1318 01:20:56,640 --> 01:21:01,590 podcast 2.0 certification badge that compliant apps and hosts 1319 01:21:01,590 --> 01:21:04,950 can use it. Don't we have those somewhere? We do. And I just put 1320 01:21:04,950 --> 01:21:09,180 it up on the namespace. Oh, nice. Yes. Although I'm not 1321 01:21:09,180 --> 01:21:15,150 happy with it, because it says it says podcast index namespace. 1322 01:21:16,140 --> 01:21:19,410 And I feel like it should just say like, podcasting 2.0 or 1323 01:21:19,410 --> 01:21:21,030 something like, Oh, yeah, let 1324 01:21:21,030 --> 01:21:21,840 me take a look. 1325 01:21:22,440 --> 01:21:25,470 If you go to the names, if you go to the namespace repository, 1326 01:21:25,800 --> 01:21:28,470 and it's on the readme and scroll all the way down to the 1327 01:21:28,470 --> 01:21:32,460 bottom. It's pretty it's very pretty. Benjamin Bellamy made it 1328 01:21:32,460 --> 01:21:35,190 for us. But I feel like it shouldn't say our name. No, 1329 01:21:35,190 --> 01:21:39,090 it what it should say is podcasting. 2.0 certified. 1330 01:21:39,390 --> 01:21:43,560 Yeah, yeah, that's what we need. Okay, so my, if somebody can can 1331 01:21:43,560 --> 01:21:45,390 grab that and morph it and change. 1332 01:21:45,480 --> 01:21:49,110 I love that so much. Like, Hey, I gotta change to the to your 1333 01:21:49,110 --> 01:21:54,060 website. Just pull request. Okay. I love that. That's the 1334 01:21:54,060 --> 01:21:55,650 way it's supposed to work, man. 1335 01:21:56,310 --> 01:21:59,160 This will allow those of us on other apps to put pressure on 1336 01:21:59,160 --> 01:22:03,180 our hosts to get podcasting. 2.0 certified. I saw this happen 1337 01:22:03,180 --> 01:22:06,570 with IB certification, that peer pressure was intense. IB 1338 01:22:06,570 --> 01:22:08,940 certified hosts cool. Hey, even that, 1339 01:22:09,060 --> 01:22:10,620 I got an idea. Right? 1340 01:22:11,880 --> 01:22:16,980 When you are podcasting, 2.0 certified, which means you have 1341 01:22:19,050 --> 01:22:25,410 you're implementing multiple tags, you get instead of paying 1342 01:22:25,410 --> 01:22:33,240 for that badge from us, we give you a free node for a year. Like 1343 01:22:33,240 --> 01:22:35,610 it with a badge. So you get a badge that says you're 1344 01:22:35,610 --> 01:22:40,590 compatible. And we give you a gift. I like it. Yeah, you don't 1345 01:22:40,590 --> 01:22:45,030 pay us we pay you exactly. We'll give you a node. And that will 1346 01:22:45,030 --> 01:22:49,110 incentivize you to put up to add the value tags because you can 1347 01:22:49,110 --> 01:22:53,100 and will add your node to the index and you're good to go free 1348 01:22:53,520 --> 01:22:59,460 from delicate value for value. Gatsby. Don't pay 40 grand for 1349 01:22:59,460 --> 01:23:02,280 an IAB certification have a free node. 1350 01:23:04,110 --> 01:23:10,620 don't pay anything at all. I be certified hosts were cool. Even 1351 01:23:10,620 --> 01:23:14,190 though most podcasters had no idea. No idea what AIB 1352 01:23:14,190 --> 01:23:15,030 certification Really? 1353 01:23:15,390 --> 01:23:16,740 Right. Yeah. 1354 01:23:18,150 --> 01:23:19,830 No one knows exactly what it is. 1355 01:23:21,630 --> 01:23:26,400 Thank you, Thomas. 25 bucks. Thank you. Yeah, he I think he 1356 01:23:26,400 --> 01:23:32,430 was on the mastodon yesterday. Oh, cool. Yeah. Let's see. Who's 1357 01:23:32,430 --> 01:23:38,730 this? Oh, okay. Dred Scott. Came gave us 26 bucks, 1358 01:23:38,760 --> 01:23:40,350 drab, Dred Scott. 1359 01:23:40,380 --> 01:23:42,870 Dude, you need to stop man. Yeah, it's 1360 01:23:42,870 --> 01:23:46,560 like time, talent, treasure. It doesn't have to be all three. 1361 01:23:46,680 --> 01:23:50,130 You're doing time. Now. I'll get time. Okay, because you'd listen 1362 01:23:50,130 --> 01:23:54,480 to the show anyway. But your talent you're very talented at 1363 01:23:54,570 --> 01:23:58,020 at making these chapters, adding images to it. Fuck it. That's 1364 01:23:58,020 --> 01:24:00,810 time to you don't need to keep it in the treasure, man. I 1365 01:24:00,810 --> 01:24:03,510 appreciate it. And we were just sending it right back to him. 1366 01:24:03,510 --> 01:24:05,340 Does he have a node now? Do we get him a node? Yeah, 1367 01:24:05,370 --> 01:24:08,250 no, yeah, he's getting set up. He's gonna stop or he's got a 5% 1368 01:24:08,250 --> 01:24:08,520 split. 1369 01:24:08,550 --> 01:24:10,590 Where's this node? Is he a Sphinx node? Or is it God? 1370 01:24:10,620 --> 01:24:12,210 Yes. Thanks. Yes. 1371 01:24:12,570 --> 01:24:14,010 That's how it should be man. 1372 01:24:14,640 --> 01:24:16,140 Stop giving it back to us. 1373 01:24:16,590 --> 01:24:22,320 We're sending it to you. Stop, stop. Stop the circular stuff. 1374 01:24:22,530 --> 01:24:22,920 Yeah. 1375 01:24:23,370 --> 01:24:28,980 It says Happy ponemos supporter. Give me a give me a you've been 1376 01:24:28,980 --> 01:24:31,740 defragmented jingle so I can hear My Sassy little four year 1377 01:24:31,740 --> 01:24:33,450 old while working on chapter markers. 1378 01:24:40,530 --> 01:24:43,710 Show number donation to go with my monthly aggregator donation 1379 01:24:43,710 --> 01:24:45,930 Keep up the great work nice. Oh, man. 1380 01:24:46,170 --> 01:24:49,440 Thank you so much, man. Yeah, a big part of this revolution. 1381 01:24:49,710 --> 01:24:50,400 Yes. Thank you, 1382 01:24:50,550 --> 01:24:53,640 you know, without without his chapter creation and the images 1383 01:24:53,940 --> 01:24:57,030 we wouldn't have wouldn't have pushed over the edge so quickly. 1384 01:24:57,510 --> 01:25:00,600 Yeah, he he got chapters off the wall. The runway. 1385 01:25:00,630 --> 01:25:03,210 Yeah, I mean people see it like, holy crap, look at all this 1386 01:25:03,210 --> 01:25:06,900 stuff. And then you see the fun stuff he's doing with it. And 1387 01:25:06,900 --> 01:25:10,530 even now he said, What did he say? He he he had an interesting 1388 01:25:10,530 --> 01:25:13,770 question about chapters that I just wanted to add this to our 1389 01:25:13,770 --> 01:25:19,890 hot namespace talk. On a second I think it was it was no agenda 1390 01:25:19,890 --> 01:25:27,750 social.com a second. It was something Hold on one moment. 1391 01:25:30,210 --> 01:25:30,600 Here's 1392 01:25:30,900 --> 01:25:33,150 something about chat about the way the chapters work. 1393 01:25:33,660 --> 01:25:41,040 It was it was snow about putting something a link into the into 1394 01:25:41,040 --> 01:25:45,930 the chapters when someone mentioned something. Ah. Oh, 1395 01:25:45,930 --> 01:25:47,700 gosh, darn it. I can't remember now. 1396 01:25:48,060 --> 01:25:51,090 But it had to do with the automated the GPT three chapter 1397 01:25:51,090 --> 01:25:52,080 stuff, maybe? 1398 01:25:52,560 --> 01:25:55,440 I don't know. Here's the problem. I don't know if it was 1399 01:25:55,470 --> 01:26:00,870 on. If he sent that message to me on the mastodon for 1400 01:26:00,870 --> 01:26:05,160 podcasting index. What Yeah, what why don't you get it? Why 1401 01:26:05,160 --> 01:26:06,180 don't you continue? 1402 01:26:07,200 --> 01:26:08,490 Why don't we get one last year? 1403 01:26:09,240 --> 01:26:10,980 I'll see if I can find this real quick. 1404 01:26:11,310 --> 01:26:17,340 This is $20 from see super cereal marketing LLC. It's Simon 1405 01:26:17,370 --> 01:26:23,790 Aaron aronowitz. And this is a long note. Let me see if I can 1406 01:26:23,790 --> 01:26:26,940 do it justice here. In the morning, Adam and Dave and thank 1407 01:26:26,940 --> 01:26:30,150 you for your courage. Since shortly after you launch podcast 1408 01:26:30,150 --> 01:26:32,940 index and podcasting 2.0 podcast I've been following your 1409 01:26:32,940 --> 01:26:36,930 progress intently. My business my business gets super cereal 1410 01:26:36,930 --> 01:26:40,260 fell into podcast and online TV show production last year after 1411 01:26:40,260 --> 01:26:43,800 the lockdown mitt nobody wanted to invest in marketing services. 1412 01:26:44,520 --> 01:26:47,730 Our modest $20 is a small financial contribution to your 1413 01:26:47,730 --> 01:26:50,370 worthy efforts to modernize, modernize podcasting, while 1414 01:26:50,370 --> 01:26:52,770 keeping it open. And to celebrate the launch of our 1415 01:26:52,770 --> 01:26:55,560 first show to show business show. Oh, yeah. Listen, I 1416 01:26:55,560 --> 01:26:59,100 started listening to it yesterday. Yeah. Yep. Our first 1417 01:26:59,100 --> 01:27:02,250 episode was released yesterday. And both video and podcast links 1418 01:27:02,250 --> 01:27:06,930 can be found at www dot show business show. Our focus is the 1419 01:27:06,930 --> 01:27:10,020 business of podcasting and online shows. On our premiere 1420 01:27:10,020 --> 01:27:13,920 episode, our guest was James Cridland editor of pod news. We 1421 01:27:13,920 --> 01:27:15,930 talked about the new announcement from Spotify, 1422 01:27:15,930 --> 01:27:19,920 including monetization for podcasters. And I wonder if he 1423 01:27:19,920 --> 01:27:25,140 if James was as cranky on that show. As he is on pod land, 1424 01:27:25,230 --> 01:27:29,010 because he is cranky about the value tag. He is not down with 1425 01:27:29,010 --> 01:27:30,240 it. He was cranky about 1426 01:27:30,240 --> 01:27:30,510 it. 1427 01:27:30,600 --> 01:27:32,460 Yeah. Isn't it? 1428 01:27:32,490 --> 01:27:33,330 What did he say? 1429 01:27:33,450 --> 01:27:37,950 He said he doesn't think that it's a good idea to have to 1430 01:27:37,950 --> 01:27:41,040 incentivize to basically reward people people for just having 1431 01:27:41,040 --> 01:27:46,800 long shows like The per minute. Whoa, buddy. Know About the 1432 01:27:46,800 --> 01:27:48,000 boost? Well, how 1433 01:27:48,000 --> 01:27:51,930 about how about just increasing your SATs per minute? You can do 1434 01:27:51,930 --> 01:27:53,400 it by show individually? 1435 01:27:54,210 --> 01:27:59,400 Yeah, just are boosted. Yes. Yeah, man. 1436 01:27:59,610 --> 01:28:04,710 Burn what a burn. And I'm always I'm always sending him SATs and 1437 01:28:04,710 --> 01:28:06,870 I'm always boosting in Hmm. 1438 01:28:07,260 --> 01:28:09,780 You gotta take some of that back. No, no, no, he's 1439 01:28:09,780 --> 01:28:13,260 an advertising guy. He's they're invested in all that 1440 01:28:13,410 --> 01:28:18,600 is he's he's he's he's in Australia's in a funky timezone. 1441 01:28:18,600 --> 01:28:21,780 He misses all the good stuff. And he just aggravated about it. 1442 01:28:23,280 --> 01:28:26,400 So I thought I found the note from Dred Scott. And it was it 1443 01:28:26,400 --> 01:28:29,760 was it wasn't all it was spectacular, I thought. But he 1444 01:28:29,760 --> 01:28:32,880 said when people plug a website in their donation notes, such as 1445 01:28:32,880 --> 01:28:37,980 we just did, yep. Are you okay with me creating a chapter that 1446 01:28:37,980 --> 01:28:38,610 links to that? 1447 01:28:38,640 --> 01:28:39,900 Yes, yes. 1448 01:28:40,890 --> 01:28:45,840 That's beautiful. So, on this donation, say it again? And then 1449 01:28:45,840 --> 01:28:47,970 we'll tell people they can click on the link in the chapter. 1450 01:28:48,420 --> 01:28:55,650 Yeah. See, www dot show business dot show. Let's see. Wait, where 1451 01:28:55,650 --> 01:28:59,490 was lost my place? Oh, yeah, here it is. We talked about the 1452 01:28:59,490 --> 01:29:02,490 new announcement Spotify bubble. We played several clips, 1453 01:29:02,490 --> 01:29:07,110 including one from podcasting 2.0 Episode 24. Adam, the 1454 01:29:07,110 --> 01:29:13,740 timecode is 5335. Though I hope you'll find time and time to 1455 01:29:13,740 --> 01:29:18,870 listen to the whole thing. And see, as well as some opinions 1456 01:29:18,870 --> 01:29:21,720 about Adams views on free speech and streaming value for value. 1457 01:29:21,870 --> 01:29:25,560 James also has some very spicy comments about Joe Rogan who now 1458 01:29:25,560 --> 01:29:26,790 wait a minute not to that point. 1459 01:29:26,820 --> 01:29:31,800 Wait a minute. So James was was grumpy about the value for value 1460 01:29:31,830 --> 01:29:33,060 on the show business show? 1461 01:29:33,330 --> 01:29:35,190 No in the pot, pot pot land. 1462 01:29:36,540 --> 01:29:39,540 All right. Yeah. I don't know what to listen to first. 1463 01:29:41,790 --> 01:29:43,980 We'd like James a lot, and this is anything but throwing him 1464 01:29:43,980 --> 01:29:46,140 under the bus. We know we get some great content from our 1465 01:29:46,140 --> 01:29:48,960 first episode, and we'll be clipping it accordingly. We're 1466 01:29:48,960 --> 01:29:52,050 video first so we're hoping for some verb virality from the 1467 01:29:52,050 --> 01:29:56,490 interwebs. We were always marketers first, but also also 1468 01:29:56,490 --> 01:30:00,690 always through creating high quality and persuasive content, 1469 01:30:01,230 --> 01:30:05,040 grab them with a strong headline. That's why in part, 1470 01:30:05,100 --> 01:30:08,190 we're big fans of podcasting to point, those objectives. My 1471 01:30:08,190 --> 01:30:12,090 business partner, Bailey and I are very much looking forward to 1472 01:30:12,090 --> 01:30:14,820 making the most out of the new feature set, including streaming 1473 01:30:14,820 --> 01:30:19,800 value for value. We're also both free speech advocates. And so 1474 01:30:19,800 --> 01:30:22,500 according, I'm not going to read this location, so accordingly 1475 01:30:22,500 --> 01:30:27,660 has a constitutional right to say what, what he wants. I, on 1476 01:30:27,660 --> 01:30:32,250 the other hand, living in the northwest of England to see live 1477 01:30:32,250 --> 01:30:34,950 under the crown is, this is a long note. I'm not sure if I can 1478 01:30:34,950 --> 01:30:35,850 read all this well. 1479 01:30:38,040 --> 01:30:40,170 Okay, can you finish the note? 1480 01:30:40,500 --> 01:30:43,410 Yeah, I'll just I'll just jump jump in. Say I'll wrap this up 1481 01:30:43,410 --> 01:30:45,510 now and apologize for the verbosity of this note. However, 1482 01:30:45,510 --> 01:30:48,180 this is a huge vote of support for what y'all are doing. In 1483 01:30:48,180 --> 01:30:50,550 closing, I'd like to invite those listening again to check 1484 01:30:50,550 --> 01:30:55,230 out the show business Show at www dot show business does show. 1485 01:30:55,620 --> 01:30:58,410 And if you didn't see that pop up and your podcast app, you've 1486 01:30:58,410 --> 01:31:02,850 got an old app, you need to get one of those newfangled apps, 1487 01:31:02,880 --> 01:31:07,230 then go to new podcast apps.com. And I was can't get over this. 1488 01:31:07,230 --> 01:31:10,050 And we need to bring Guillermo back in because Are you still 1489 01:31:10,050 --> 01:31:12,450 there? Gilliam? Are you asleep? Are you with us? 1490 01:31:13,200 --> 01:31:18,780 I'm here, I think they should read the full note. Because then 1491 01:31:18,780 --> 01:31:20,310 who have more sets training? 1492 01:31:23,400 --> 01:31:26,400 Let me think you know, this is this is a very interesting if 1493 01:31:26,400 --> 01:31:30,780 they had never considered this as an objection. But isn't it 1494 01:31:30,780 --> 01:31:36,000 the same? Isn't it ultimately your time? That time is money 1495 01:31:36,000 --> 01:31:40,050 your your time is valuable? If you have a short podcast, you 1496 01:31:40,050 --> 01:31:44,490 can't have a mid roll and a beginning roll and enroll, you 1497 01:31:44,490 --> 01:31:48,120 know, so you also will have less income? Technically, unless you 1498 01:31:48,120 --> 01:31:52,410 jam it full of ads. I I don't see how it's unfair. I think 1499 01:31:52,410 --> 01:31:54,750 it's one of the most fair things I've ever heard of, particularly 1500 01:31:54,750 --> 01:31:58,290 because you can set the money you send yourself. 1501 01:31:58,800 --> 01:32:01,590 Oh, okay. So the, the the example you use was pod news. 1502 01:32:01,740 --> 01:32:04,980 Bad news is a very short show. But he makes a valid point. He 1503 01:32:04,980 --> 01:32:09,060 says it's very short, but it's very valuable. And I agree. I 1504 01:32:09,060 --> 01:32:11,580 agree. But that's where the boost is. And that's where you 1505 01:32:11,580 --> 01:32:12,630 jack your slider up. 1506 01:32:13,020 --> 01:32:16,980 Yeah, exactly. Exactly. And I'm always hitting a boost on him. 1507 01:32:17,460 --> 01:32:23,160 Yeah, you set your boost to me know, to five 5000 SATs or 1508 01:32:23,160 --> 01:32:24,180 10,000 sets. And you 1509 01:32:24,870 --> 01:32:28,710 this is where we could really use the I think was part of your 1510 01:32:28,740 --> 01:32:33,000 your documentation, the recommended SATs per minute. 1511 01:32:33,330 --> 01:32:34,350 Mm hm. 1512 01:32:34,530 --> 01:32:37,470 You know, that should be for a shorter show that should be that 1513 01:32:37,470 --> 01:32:38,640 should be set higher. 1514 01:32:39,390 --> 01:32:42,450 Or if somebody just believes their show is very valuable. 1515 01:32:42,510 --> 01:32:46,140 Yeah. Well, okay. I have to listen to what exactly what he 1516 01:32:46,140 --> 01:32:48,660 said, No, I really appreciate this kind of I appreciate all 1517 01:32:48,660 --> 01:32:51,090 criticism and all kinds of feedback. I just want to make 1518 01:32:51,090 --> 01:32:54,930 sure if I'm understanding the problem, right, because I think 1519 01:32:54,930 --> 01:32:58,080 I think this is something that's easily addressed without even 1520 01:32:58,080 --> 01:33:01,410 changing anything. It's just it's just a philosophy. Yeah, I 1521 01:33:01,410 --> 01:33:04,410 think so too. And I think it's already I think the parts are 1522 01:33:04,410 --> 01:33:05,010 already there. 1523 01:33:05,249 --> 01:33:08,789 Well, well, what I'm going to do now is let me see so I'm 1524 01:33:08,789 --> 01:33:11,309 streaming it let me just see when I'm because I always listen 1525 01:33:11,309 --> 01:33:16,679 to it on pod station. Almost always. So let me just see. So 1526 01:33:16,679 --> 01:33:17,129 Outlander 1527 01:33:17,130 --> 01:33:17,670 pod news. 1528 01:33:18,690 --> 01:33:22,950 pod news. Got some just think so pod news is typically about 1529 01:33:22,950 --> 01:33:27,330 three minutes. So let's just say for now, three minutes is 1530 01:33:27,330 --> 01:33:32,280 probably fair or four minutes. And let me see I'm streaming at 1531 01:33:32,850 --> 01:33:39,930 3000 SATs per hour. So what is that? 50 SATs a minute? Am I 1532 01:33:39,930 --> 01:33:40,650 saying that? Right? 1533 01:33:42,000 --> 01:33:43,800 Don't ask me to do that. I think so. 1534 01:33:45,030 --> 01:33:47,280 Right? You've had your head into it. Right? 1535 01:33:47,610 --> 01:33:50,460 I have no idea. I'm terrible at 1536 01:33:51,480 --> 01:33:56,670 50. If I have 50 SATs times 60 minutes, that's 3000. 1537 01:33:56,700 --> 01:33:57,840 Yes. Okay. 1538 01:33:58,050 --> 01:34:02,550 All right. I'm gonna up that. I'm gonna boost him. $5 1539 01:34:03,630 --> 01:34:07,200 Oh, yeah. You're putting your money where your mouth is just 1540 01:34:07,200 --> 01:34:13,020 right at a baller baller. Boost, right? baller boost. All right, 1541 01:34:13,050 --> 01:34:15,450 I want it. I want him to be happy. I want everybody to be 1542 01:34:15,450 --> 01:34:18,330 happy. Guillermo, how can I make you happy? What can we do to 1543 01:34:18,330 --> 01:34:20,340 make your life better as a developer? 1544 01:34:21,329 --> 01:34:24,839 Just keep using both station and distributor sets to me and I'm 1545 01:34:24,839 --> 01:34:25,229 happy. 1546 01:34:27,960 --> 01:34:28,500 Baby. 1547 01:34:29,220 --> 01:34:33,390 Very nice. Very nice. All right, Dave, anything we can do for you 1548 01:34:33,390 --> 01:34:34,500 to make your life easier. 1549 01:34:35,370 --> 01:34:40,290 Oh, gosh. Maybe? I don't know what it is though. 1550 01:34:40,410 --> 01:34:44,070 Okay, well, you will send me a memo and I will I will put me on 1551 01:34:44,070 --> 01:34:49,020 the distribution list on mail. What do we have coming up in the 1552 01:34:49,020 --> 01:34:53,130 next week? Do you think the breeze guys are getting close to 1553 01:34:53,130 --> 01:34:55,500 releasing next week? Do you think anything like that? 1554 01:34:56,760 --> 01:34:59,610 Feels what I needed that. I spent the last few days heads 1555 01:34:59,610 --> 01:35:02,970 down to documentation, mostly for them because they needed. 1556 01:35:03,270 --> 01:35:06,450 They, they really wanted to have some stuff to link to when they 1557 01:35:06,480 --> 01:35:09,480 did their release, which is cool. Yeah. And I've got I've 1558 01:35:09,480 --> 01:35:12,600 got the documentation come in, excuse me documentation posted. 1559 01:35:12,600 --> 01:35:15,480 And then there's wrote a blog post just to give some context 1560 01:35:15,480 --> 01:35:18,660 to it. So I think, I think they're close. I don't know if 1561 01:35:18,660 --> 01:35:21,180 they're, I don't know how many how close but 1562 01:35:21,240 --> 01:35:25,410 they follow. Follow breeze mobile and GitHub. And you know, 1563 01:35:25,410 --> 01:35:28,350 there's there's pull requests, like, which I thought was really 1564 01:35:28,350 --> 01:35:32,490 cool. Get notify the user if funds are running low while 1565 01:35:32,490 --> 01:35:38,310 playing a podcast. This is good. This is good. Just a little hint 1566 01:35:38,310 --> 01:35:40,680 there. guiliana just saying, you know, there's us stuff that 1567 01:35:40,680 --> 01:35:42,840 people like get more money, get more snaps. 1568 01:35:43,710 --> 01:35:47,130 Yeah, all of pod stations, funding links, go back to gamma 1569 01:35:47,130 --> 01:35:47,700 anyways. Yeah, 1570 01:35:47,700 --> 01:35:48,120 that's right. 1571 01:35:49,860 --> 01:35:53,730 He just sent it to him directly. Yeah. All right, gentlemen. 1572 01:35:54,390 --> 01:35:56,970 We'll get there. But thank you so much for joining us. It was 1573 01:35:56,970 --> 01:35:59,610 great to get to know you a little bit better. And thank you 1574 01:35:59,640 --> 01:36:03,900 guys so much for the value you're bringing to the entire 1575 01:36:03,900 --> 01:36:05,790 project is really appreciated. 1576 01:36:06,570 --> 01:36:08,160 Thank you. It was great to be here. 1577 01:36:09,330 --> 01:36:11,220 Dave, last words for you. 1578 01:36:14,610 --> 01:36:17,670 I've got to return to work and actually do real day job stuff. 1579 01:36:17,670 --> 01:36:20,400 So we all my words and my words are over. 1580 01:36:21,270 --> 01:36:24,690 We all have a job. Alright. Thanks again, man. Have yourself 1581 01:36:24,690 --> 01:36:30,000 a great weekend. Have a good weekend, my friend. We'll do 1582 01:36:30,000 --> 01:36:34,140 another one next week podcasting 2.0 podcast index.org. See you 1583 01:36:34,140 --> 01:36:34,440 then. 1584 01:36:50,460 --> 01:36:52,080 listening to podcasts. 1585 01:36:53,370 --> 01:36:57,210 Visit podcasts. For more information.