1 00:00:00,000 --> 00:00:06,270 Oh, podcasting 2.0 for February 3 2023, episode 120 We got the 2 00:00:06,270 --> 00:00:11,250 chop and drop. Friday once again, are you ready for the 3 00:00:11,250 --> 00:00:14,070 board meeting? That's right. It's the meeting you actually 4 00:00:14,070 --> 00:00:17,580 want to attend on a Friday board meeting of podcasting. 2.0 5 00:00:17,580 --> 00:00:22,590 everything going on with the incredible namespace with the 6 00:00:22,590 --> 00:00:25,740 index podcast. index.org. But really, everything that's 7 00:00:25,740 --> 00:00:28,740 discussed during the week in podcast index dot social. I'm 8 00:00:28,740 --> 00:00:31,020 Adam curry here in the heart of the Texas Hill Country and in 9 00:00:31,020 --> 00:00:34,710 Alabama, the Sultan of scissors to run with say hello to my 10 00:00:34,710 --> 00:00:38,820 friend on the other end, ladies and gentlemen, Mr. De Jones. 11 00:00:40,110 --> 00:00:44,130 You jinxed me 100%. I mean, what do you mean? You were talking 12 00:00:44,130 --> 00:00:49,020 about biting the inside of your mouth? It's like during the 13 00:00:49,020 --> 00:00:52,890 intro, I've got some granola and I just rocked to the roof. I 14 00:00:52,890 --> 00:00:56,460 don't know what Oh, my God, it hurts. I mean, like, is there 15 00:00:56,460 --> 00:01:00,240 blood? Yeah, holy crap. I don't know what I just did. 16 00:01:00,930 --> 00:01:05,520 I have these temporary chompers in the front, top and bottom. 17 00:01:05,550 --> 00:01:08,400 And, you know, if you don't pay attention, like if you're 18 00:01:08,400 --> 00:01:11,010 talking while something's in your mouth, or I'm leaning a 19 00:01:11,010 --> 00:01:14,100 little bit to the left hand side, then I can just kind of 20 00:01:14,100 --> 00:01:17,490 like nip the inside of my lip. And of course, the minute you do 21 00:01:17,490 --> 00:01:20,370 that, it gets thick. And then it's just primed. It's just a 22 00:01:20,370 --> 00:01:23,730 target. Now it's a target. Even talking, even talking. I can 23 00:01:23,730 --> 00:01:27,060 feel it going. Come on, come on. You want to bring it a little 24 00:01:27,060 --> 00:01:33,120 tighter. But the Pope, exactly are they doing brother? I'm 25 00:01:33,120 --> 00:01:36,630 good? Yeah, yeah, it's been. It's been kind of a crazy week. 26 00:01:36,630 --> 00:01:39,930 But yeah, I'd say in general, pretty good. A lot of stuff 27 00:01:39,930 --> 00:01:43,800 going on a lot of information, that information coming out 28 00:01:43,800 --> 00:01:49,230 everywhere and new information. And I had a couple of questions 29 00:01:49,230 --> 00:01:52,560 for you, actually, before we because we have we have guests 30 00:01:52,560 --> 00:01:55,320 in the boardroom today. I'm very excited about that. We do 31 00:01:55,350 --> 00:01:59,070 we do? We do have guests? Yes, yes. They're there in the lobby. 32 00:01:59,370 --> 00:01:59,700 A couple 33 00:01:59,700 --> 00:02:02,940 things from from the GitHub that I've been reading along with 34 00:02:02,970 --> 00:02:05,610 that, I think it's important to update everybody on they need to 35 00:02:05,610 --> 00:02:08,730 go and see it if they don't understand it. The first one is 36 00:02:08,730 --> 00:02:13,980 I believe we now have a clarification for what a fee is 37 00:02:14,010 --> 00:02:15,480 in the value for value model. 38 00:02:17,370 --> 00:02:20,460 Is this is this a clarification from me? 39 00:02:20,520 --> 00:02:24,000 Yes. You're going to say that's correct, sir. That is correct. 40 00:02:24,270 --> 00:02:29,310 As we do and what was anything changed to clarify this? Or? Or 41 00:02:29,310 --> 00:02:33,360 is it? I mean, can you give me a synopsis of how what a fee is 42 00:02:33,360 --> 00:02:35,910 versus a split? And how that is calculated? 43 00:02:37,950 --> 00:02:41,370 This is one of those things that have been perpetually difficult 44 00:02:41,370 --> 00:02:42,510 to explain. Yeah, 45 00:02:42,540 --> 00:02:44,970 that's why I have to I figured I put you on the spot for it. 46 00:02:46,110 --> 00:02:50,820 So that somebody posted an issue and said, you know, like, what 47 00:02:50,820 --> 00:02:54,180 am I've got? I've got to split concept thing. I've got it down. 48 00:02:54,480 --> 00:02:58,230 But what is the fee? How do I calculate that it's not clear 49 00:02:58,230 --> 00:03:07,320 from the dogs? I mean, I'm not sure that there is a way to make 50 00:03:07,320 --> 00:03:10,920 it super clear. This is one of those things where it's like, no 51 00:03:10,920 --> 00:03:15,060 matter how you explain it, the language just won't. It just 52 00:03:15,060 --> 00:03:17,640 kind of always gets in your way. Well, why don't why don't we 53 00:03:17,640 --> 00:03:21,930 start with who would use a fee versus a split. 54 00:03:23,640 --> 00:03:28,800 Any service that wants to just have a straight percentage, 55 00:03:29,850 --> 00:03:34,410 regardless of what else is in the split. So if I if I run a 56 00:03:34,410 --> 00:03:39,450 service, and I and let's just let's just make up a 57 00:03:39,840 --> 00:03:43,440 hypothetical service here, where you're gonna put me in your 58 00:03:43,440 --> 00:03:49,290 split. And for that I give you back. Let's just say stats. I 59 00:03:49,290 --> 00:03:49,980 give you back, right? 60 00:03:50,010 --> 00:03:54,300 Yep. Perfect. Perfect example for contracts as an example 61 00:03:54,300 --> 00:03:54,930 contract. 62 00:03:54,930 --> 00:04:01,350 Yeah. So So contracts may say, if you want to use our service, 63 00:04:01,680 --> 00:04:10,650 we charge a 1%. Split. Yeah. Okay. The splits are, the way 64 00:04:10,650 --> 00:04:15,840 the splits work is they're based on a share model. So you, if you 65 00:04:15,840 --> 00:04:21,090 have three splits, they don't have the, the split attribute 66 00:04:21,120 --> 00:04:26,790 that is defined in each split destination. That number does 67 00:04:26,790 --> 00:04:31,230 not have to add add up total up to 100. So you can have a split 68 00:04:31,230 --> 00:04:38,160 with 150, a split with 25. And in another split with 20 with 69 00:04:38,160 --> 00:04:40,410 us, give me an N and another split with 75. 70 00:04:41,010 --> 00:04:43,710 You've already lost me I don't understand. Yeah. So 71 00:04:43,710 --> 00:04:47,100 like if you the the when you're defining your receipt, your 72 00:04:47,100 --> 00:04:50,970 value recipients and the value blog, you have to put a there's 73 00:04:50,970 --> 00:04:56,340 a required attribute called split and that's just a number 74 00:04:56,760 --> 00:04:59,760 and it does the number those the number doesn't have to you have 75 00:04:59,760 --> 00:05:03,690 to eat 100 the number of all of that together doesn't have to 76 00:05:03,690 --> 00:05:08,280 equal 100. So if you had three splits, and one of them was 171 77 00:05:08,280 --> 00:05:10,470 of them was 20. And one of them was 90 78 00:05:10,500 --> 00:05:11,370 percentages. 79 00:05:13,139 --> 00:05:16,229 Now these that's the thing, they're not percentages, that 80 00:05:16,229 --> 00:05:21,089 those three splits equal add up to 280. Yeah, so you're you're 81 00:05:21,089 --> 00:05:25,979 not, you're not working, the splits are not vase 100, the 82 00:05:25,979 --> 00:05:29,909 splits are just rent a rent or just whatever numbers that you 83 00:05:29,909 --> 00:05:35,249 put in there, that when taken together, represent the shares 84 00:05:35,279 --> 00:05:39,929 amongst each. So if you take that those three addenda, in 85 00:05:40,079 --> 00:05:46,469 that example, added up to 280. You now you take that 280. And 86 00:05:46,469 --> 00:05:51,179 you've figured out what the percentage of each split number 87 00:05:51,179 --> 00:05:55,409 is of the 280. So you're just you're taking too you're taking 88 00:05:55,409 --> 00:05:57,599 whatever the total is, of all the splits? This is 89 00:05:57,600 --> 00:06:03,330 Common Core, right? Or is it modern monetary theory? I'm not 90 00:06:03,330 --> 00:06:04,170 sure which one it is. 91 00:06:04,170 --> 00:06:06,870 It's both it's post modern monetary theory, the obvious 92 00:06:06,870 --> 00:06:09,330 question will be in a moment, like, why not just I mean, what 93 00:06:09,330 --> 00:06:14,370 I'm doing in sovereign feeds is it all adds up to 100? To 100%? 94 00:06:14,730 --> 00:06:18,870 Because that's easy for you as a human to do that math on the 95 00:06:18,870 --> 00:06:24,960 fly. Correct. So but there's a few reasons why. There's, 96 00:06:24,990 --> 00:06:28,770 there's a couple of reasons why this is better. Not the least of 97 00:06:28,770 --> 00:06:35,850 which is that if you, if you get those numbers wrong, if 98 00:06:35,850 --> 00:06:39,960 everybody expects just a base 100 calculation, and if you get 99 00:06:39,960 --> 00:06:44,580 that number wrong, and it adds up to 103. What do you do? Like, 100 00:06:44,610 --> 00:06:47,520 it's now you're now you've completely you're out of spec, 101 00:06:48,060 --> 00:06:52,020 and there's no way to sort of recover from that and figure out 102 00:06:52,020 --> 00:06:56,700 what they're supposed to be. So this gives you doing it this way 103 00:06:56,700 --> 00:07:02,220 gives you flexibility to, to add up to whatever value and the the 104 00:07:02,220 --> 00:07:06,600 app can still make a calculation and enrich and come out with 105 00:07:06,690 --> 00:07:12,510 same results. Because you, you take your you take whatever 106 00:07:12,510 --> 00:07:15,810 number it adds up to. And you consider that as your as your 107 00:07:15,810 --> 00:07:19,050 100. And then you figure out the percentages based on it makes 108 00:07:19,050 --> 00:07:23,220 like, it's like having shares in a company, you know, a company 109 00:07:23,220 --> 00:07:26,460 can have, you know, a million million outstanding shares. 110 00:07:26,790 --> 00:07:29,520 Well, who who owns 50% of the company, you just figure out 111 00:07:29,520 --> 00:07:32,880 who's got 50% of that total of the total outstanding shares, 112 00:07:33,330 --> 00:07:36,210 this is the same way who somebody gets 50, you know, 113 00:07:36,210 --> 00:07:41,820 somebody's getting 50% of have to add, then they have to have, 114 00:07:41,910 --> 00:07:47,370 you know, they have to have the 50% of whatever to to add 140. 115 00:07:48,090 --> 00:07:52,230 So, like that's, that's the way that you do it. So since it's a 116 00:07:52,230 --> 00:07:58,350 share model, there's no clean way to just define a percentage. 117 00:08:00,870 --> 00:08:04,530 With regards to just a service that wants a percent a flat, A 118 00:08:04,530 --> 00:08:09,090 flat fee. So if those are in the in our example, let's just say 119 00:08:09,090 --> 00:08:14,100 contracts wants to charge 1% for their service. If the shares are 120 00:08:14,100 --> 00:08:18,270 always fluctuating, and it can be any number, you can just put 121 00:08:18,270 --> 00:08:22,140 a one in there because that one as a once as a split with one, 122 00:08:22,680 --> 00:08:25,740 because one doesn't mean what you say, doesn't mean anything. 123 00:08:25,770 --> 00:08:25,950 Well, 124 00:08:25,950 --> 00:08:30,060 hold on, hold on. Maybe this is not a good example, contracts, 125 00:08:30,480 --> 00:08:34,050 doesn't have power to do anything. In my feed, or in my 126 00:08:34,050 --> 00:08:37,650 split, I as the producer and the creator of the feed have that 127 00:08:37,650 --> 00:08:44,910 power. Right, right. So I still, I'm complete, I understand. No, 128 00:08:44,910 --> 00:08:48,870 I really don't understand I don't I seriously, I don't if so 129 00:08:48,870 --> 00:08:52,680 just from my perspective, and maybe we're talking on two 130 00:08:52,680 --> 00:08:55,170 different planes here. Maybe we're talking under the hood, 131 00:08:55,440 --> 00:08:59,370 and what the podcaster sees. So on the podcaster and for this 132 00:08:59,400 --> 00:09:04,500 episode, there's as 5% for one guest 5% For the next guest 5% 133 00:09:04,500 --> 00:09:09,090 For Dred Scott. There's, I think, some percentages for 134 00:09:09,720 --> 00:09:12,420 sovereign feeds, which I put in there, which is not taken 135 00:09:12,420 --> 00:09:21,240 automatically. And, and I've put in 1%, for my user on fountain, 136 00:09:21,240 --> 00:09:24,090 so we show up in the activity there. And then whatever's left 137 00:09:24,090 --> 00:09:27,900 over, goes to podcast index, which is at this point, like 138 00:09:27,900 --> 00:09:33,990 58%, in my mind, and it adds up to 100. And that's how I do it. 139 00:09:34,350 --> 00:09:37,470 Wow, who's doing this one ad that you speak of? 140 00:09:39,540 --> 00:09:43,260 It? I don't know who's doing it. But that's the way the way that 141 00:09:43,260 --> 00:09:47,940 you do it is valid, because it it it's still just share based. 142 00:09:48,330 --> 00:09:51,750 It's like so you're you're just taking 100 as what you want 143 00:09:51,750 --> 00:09:52,530 everything to total 144 00:09:52,530 --> 00:09:54,600 up to what shouldn't that be the requirement? 145 00:09:55,890 --> 00:10:00,270 No, no, why not? Because, because if if if you recall Word 146 00:10:00,270 --> 00:10:05,340 that always adds to 100. Yeah. And and one of the number and it 147 00:10:05,340 --> 00:10:09,930 doesn't, then it's, then it's broken. Correct you do it, if 148 00:10:09,930 --> 00:10:14,520 you do it based on a share model, then even even if it 149 00:10:14,520 --> 00:10:17,190 doesn't, if you've fat fingered something, and it goes in there 150 00:10:17,190 --> 00:10:22,020 wrong, it's still people still get it still functions. Like, 151 00:10:22,050 --> 00:10:28,800 imagine if you've broken if everything is a percentage. And 152 00:10:28,800 --> 00:10:33,450 then you expect every split be a percentage of 100. And something 153 00:10:33,450 --> 00:10:38,280 goes in there wrong. And it actually adds up to 103. What is 154 00:10:38,280 --> 00:10:39,390 the app supposed to do 155 00:10:39,420 --> 00:10:42,420 what my app does? It says you cannot go further. You've done 156 00:10:42,420 --> 00:10:43,020 it wrong. 157 00:10:43,650 --> 00:10:46,080 Right. And see, that's what you're trying to avoid. You try 158 00:10:46,080 --> 00:10:50,760 you don't We don't. We don't want that. We don't want this 159 00:10:50,790 --> 00:10:54,180 the strictness of having to do that no interest because it 160 00:10:54,180 --> 00:10:58,710 breaks things. Okay. All right. So like if you if something as 161 00:10:58,710 --> 00:10:59,790 of 203 Was 162 00:10:59,790 --> 00:11:03,960 it? Well, then let's let's but just for simplicity of for 163 00:11:03,960 --> 00:11:08,280 simplicity of explaining this, I would recommend not starting off 164 00:11:08,280 --> 00:11:11,220 with Well, you got 180 You gotta write what you know that all 165 00:11:11,220 --> 00:11:15,990 that already got me out. already fell on the floor. So, right, 166 00:11:16,020 --> 00:11:22,170 okay, so let's just say it all adds adds up to 100. Now, now 167 00:11:22,170 --> 00:11:23,850 take it from there to the fees. 168 00:11:26,220 --> 00:11:30,030 Okay, so the well, the see if you That's That's it, that's 169 00:11:30,030 --> 00:11:33,510 important, though, is important that it doesn't have to add to 170 00:11:33,510 --> 00:11:36,660 100. Because otherwise the fee, the reason the fee is there 171 00:11:36,660 --> 00:11:37,470 doesn't make any sense. 172 00:11:37,710 --> 00:11:40,890 I understand. Yeah, let's just let's just take that case to 173 00:11:40,890 --> 00:11:41,820 make it easy for me. 174 00:11:42,600 --> 00:11:48,690 Okay. So then the fee, if you the fee attribute vehicles, 175 00:11:48,690 --> 00:11:54,720 vehicles true means that whatever this split is, you want 176 00:11:54,750 --> 00:11:59,280 a total what you want 1% to be taken off the top after the 177 00:11:59,280 --> 00:12:05,190 calculation is made. So what you want is you want to say okay, I 178 00:12:05,190 --> 00:12:09,030 want 1% to go to Daniel J. Lewis, 179 00:12:10,320 --> 00:12:14,160 by AP would immediately reject that, because of Daniel J. 180 00:12:14,160 --> 00:12:19,260 Lewis, who was at no does not compute. Yes. canvasback just 181 00:12:19,590 --> 00:12:25,080 spread. Okay. I see. All right. Now. So this makes sense. I 182 00:12:25,080 --> 00:12:28,080 recommend we never talk about it in this way ever again. 183 00:12:28,410 --> 00:12:31,140 Because this is that this is what I'm saying? Like, yeah, is 184 00:12:31,140 --> 00:12:32,670 it possible to discuss it? No, 185 00:12:32,670 --> 00:12:38,970 no, no, here's No. Oh, it's not boring me brother at all. It's 186 00:12:38,970 --> 00:12:41,790 money. And it's important here, here's how I understand. Let me 187 00:12:41,790 --> 00:12:46,830 just see, maybe we can cut corners. So we're going to say 188 00:12:46,830 --> 00:12:52,470 that I have everything adding up to 100. And now we have the app 189 00:12:52,470 --> 00:12:59,190 that is that is that that person is using takes a 3% fee. So now 190 00:12:59,190 --> 00:13:03,510 it's 103. But what the app is going to do now under the hood 191 00:13:03,510 --> 00:13:07,590 is going to make a share model and recalculate that. So it's 192 00:13:07,590 --> 00:13:11,820 all it comes down to the that's your how many outstanding shares 193 00:13:12,000 --> 00:13:16,560 nothing that nothing at all that the user has to even know about. 194 00:13:17,400 --> 00:13:18,780 That's just under the hood. 195 00:13:19,530 --> 00:13:24,810 Right? Right. Yeah. Well, yeah. So you know, the, it's all on 196 00:13:24,810 --> 00:13:25,830 our system anyway. 197 00:13:26,310 --> 00:13:29,640 Yeah, sure. But I thought there was a difference between a fee 198 00:13:29,640 --> 00:13:35,670 being a part of the entire pie. Or in something being put on 199 00:13:35,670 --> 00:13:36,300 top. 200 00:13:37,350 --> 00:13:41,820 Yes, so the so the way the way that the spec is written, you 201 00:13:41,820 --> 00:13:47,610 take you take all the shares, add them up, and then okay, so 202 00:13:47,610 --> 00:13:50,220 whatever the payments gonna be, somebody sends a booster gram, 203 00:13:51,030 --> 00:13:56,520 and this is boost gram is 1000 SATs may got 100 and make it 204 00:13:56,520 --> 00:14:02,610 100. Okay, okay. 100. So, this grams, 100 sets and you got, you 205 00:14:02,610 --> 00:14:06,180 know, you got three splits you at you take that wonder sets, 206 00:14:06,180 --> 00:14:08,490 you figure out what the share amounts are. So you fit you 207 00:14:08,490 --> 00:14:12,570 calculate the percentages to figure out how, how much eat 208 00:14:12,570 --> 00:14:17,640 split gets done, you you have those numbers ready. Yeah. But 209 00:14:17,640 --> 00:14:23,550 then the before you do, before you do any of that. You take 210 00:14:23,910 --> 00:14:27,780 whatever, if there's any fees listed. You take them in order 211 00:14:27,780 --> 00:14:32,520 and you say okay, 1% If there's a 1% of the split in here, you 212 00:14:32,520 --> 00:14:40,530 take one set it off the top, send that split and then the now 213 00:14:40,530 --> 00:14:44,430 you're down to 99 sets and so then you recalculate everybody's 214 00:14:44,430 --> 00:14:50,040 split shares based on that. Okay. So the fee is a request to 215 00:14:50,040 --> 00:14:52,350 say hey, we want we want 216 00:14:52,350 --> 00:14:55,590 recalculation of the whole recalculation right. Yeah, 217 00:14:55,590 --> 00:15:00,510 we want to fee off the quote, quote, unquote, off the top In, 218 00:15:00,960 --> 00:15:04,740 that seems important, because there's really no other way to 219 00:15:04,830 --> 00:15:09,870 if you don't say, where the fee comes from, then you don't know. 220 00:15:10,170 --> 00:15:12,840 Like, there's no, it's just up to the app developer. Basically, 221 00:15:12,840 --> 00:15:17,310 there's the spec is written with the, with the goal, to at all 222 00:15:17,310 --> 00:15:22,080 costs. Don't, don't leave the spec ambiguous so that the app 223 00:15:22,080 --> 00:15:26,790 can make a mistake. Got it. And because it goes, you what you 224 00:15:26,790 --> 00:15:30,660 don't want is people bitching at the app developer that they that 225 00:15:30,660 --> 00:15:33,480 they screwed him out of out of some kind of payment, like, Oh, 226 00:15:33,480 --> 00:15:36,420 you didn't do it, right. And bla bla bla bla is like, okay, even 227 00:15:36,420 --> 00:15:39,990 if even if there's some quibbles about how it's done, you want it 228 00:15:39,990 --> 00:15:44,430 to be just as rock solid, clear as possible when it comes to 229 00:15:44,430 --> 00:15:45,900 doing the math in the app. 230 00:15:45,990 --> 00:15:49,680 Right? Totally agree. So we just need to never explain it the way 231 00:15:49,680 --> 00:15:53,460 you started off to people who are because people who complain 232 00:15:53,460 --> 00:15:57,180 will look at that and go, Hmm, that just No one No, I didn't I 233 00:15:57,240 --> 00:16:01,200 get it. It's, it's a weighting. Which is important. Because 234 00:16:01,200 --> 00:16:04,140 you're adding you're you have an external factor that is unknown, 235 00:16:04,140 --> 00:16:08,670 that is a fee. And you want to add that in, to then go back and 236 00:16:08,670 --> 00:16:11,940 recalculate everything based upon the new amount. And that's 237 00:16:11,940 --> 00:16:15,750 how you can count up to 103. Or, God forbid, 110 or whatever, 238 00:16:15,930 --> 00:16:18,030 then everything is recalculated, got it 239 00:16:19,020 --> 00:16:22,020 to V COMM The to V comes through in the in the boost 240 00:16:22,050 --> 00:16:24,540 with the sphere with the full thing, the full number with it 241 00:16:24,540 --> 00:16:26,100 with the original number. Yeah, yeah, I 242 00:16:26,100 --> 00:16:28,590 mean, it's honor system, but then the service could say, you 243 00:16:28,590 --> 00:16:31,950 know, hey, you know, you're, you're not really you're not 244 00:16:32,010 --> 00:16:36,090 doing what we asked. And, you know, they they could say, you 245 00:16:36,090 --> 00:16:39,180 know, they can make an issue out of it if they wanted to. I mean, 246 00:16:39,180 --> 00:16:42,090 I doubt anybody would, but I mean, at least it's there, they 247 00:16:42,090 --> 00:16:44,730 could check the math if they wanted to, to make sure people 248 00:16:44,730 --> 00:16:46,620 weren't right. Not ruin him or whatever 249 00:16:46,680 --> 00:16:50,520 is there. I've heard talk of people saying, well, there 250 00:16:50,520 --> 00:16:55,620 should also be a split that is just based on a number of 251 00:16:55,620 --> 00:16:59,880 Satoshis is that in there somewhere? 252 00:17:01,140 --> 00:17:03,180 I don't know what you mean. Can you explain that? 253 00:17:03,510 --> 00:17:09,450 So instead of fountain saying you activate this service for 1% 254 00:17:09,750 --> 00:17:12,210 you activate this service for five sets? 255 00:17:12,780 --> 00:17:16,440 Oh, I see just a straight straight upset static amount 256 00:17:16,440 --> 00:17:22,500 Yeah. There's no no there's no function in there for that. That 257 00:17:22,500 --> 00:17:26,760 just doesn't seem to be I don't even see how that's doable it 258 00:17:26,760 --> 00:17:30,930 wasn't it was a conversation on podcast index dot social. And 259 00:17:31,110 --> 00:17:33,870 and I initially thought Oh, that's interesting. And then I 260 00:17:33,870 --> 00:17:37,020 thought no, it's a very bad idea. And you would be crazy to 261 00:17:37,020 --> 00:17:37,500 do that. 262 00:17:38,520 --> 00:17:41,040 Yeah, the flat fee just seems like it would break 263 00:17:41,460 --> 00:17:45,060 well not not just break it's like why take a flat fee when 264 00:17:45,060 --> 00:17:47,700 you can get a percentage I mean, you're always gonna get one set 265 00:17:48,480 --> 00:17:51,300 can only be more now just because it was just a 266 00:17:51,300 --> 00:17:54,480 conversation. Just want to make sure that that didn't show up 267 00:17:54,480 --> 00:18:00,000 and that died on the vine just just like we did just like coil 268 00:18:00,810 --> 00:18:03,750 Oh yeah, no, I don't like dancing on graves. But man that 269 00:18:03,750 --> 00:18:04,590 went fast. 270 00:18:06,060 --> 00:18:09,750 We were I don't know is two and a half years is that fast? 271 00:18:09,810 --> 00:18:13,500 Well, no, we were talking about the web monetization and it had 272 00:18:13,500 --> 00:18:16,740 to be jammed into the value block we had to do it I gotta do 273 00:18:16,740 --> 00:18:19,980 it. Everybody's gotta be in that we want to take Visa MasterCard 274 00:18:21,180 --> 00:18:27,540 and two weeks later, coil bids farewell. She's dead. Well, no, 275 00:18:27,540 --> 00:18:30,780 actually they've updated the page coil bids farewell but not 276 00:18:30,780 --> 00:18:32,490 goodbye not goodbye. 277 00:18:33,690 --> 00:18:37,620 Huh? Well, I don't understand this because if you look at 278 00:18:37,620 --> 00:18:41,370 their page, if you read the statement, it says what is going 279 00:18:41,370 --> 00:18:45,930 to happen to my wallet and it says something like your inner 280 00:18:45,930 --> 00:18:50,010 Ledger Wallet will continue to function you know because your 281 00:18:50,010 --> 00:18:54,360 inner inter Ledger Wallet provider is not going away or 282 00:18:54,360 --> 00:18:58,140 something like that will coil was the only wallet provider so 283 00:18:59,280 --> 00:19:01,380 it seems like a distinction without a difference. 284 00:19:01,590 --> 00:19:03,120 Well I'm glad everybody took the money 285 00:19:04,140 --> 00:19:05,010 Yeah, good job. I 286 00:19:05,010 --> 00:19:07,890 mean getting the job every but now I feel kind of stupid. Now 287 00:19:07,890 --> 00:19:10,140 we could we should have taken 85 grand that would have been good. 288 00:19:10,140 --> 00:19:12,990 We could have put that in our pocket. Yeah, and implemented 289 00:19:12,990 --> 00:19:15,090 something and take it right out two weeks later. I'm not 290 00:19:15,120 --> 00:19:19,470 accusing anyone getting PPP PPP 291 00:19:20,430 --> 00:19:24,360 grant. Yeah. I mean, congratulations to to Peter 292 00:19:24,360 --> 00:19:26,580 rights for coming into the wire getting I hope to check. 293 00:19:29,130 --> 00:19:34,410 Yes, one other thing from the GitHub, because it's just been 294 00:19:34,410 --> 00:19:36,840 fascinating. And I read along with everything, not that I 295 00:19:36,870 --> 00:19:40,050 understand everything, but I saw ROI even show up in this one. 296 00:19:40,410 --> 00:19:46,050 And now this is the ln URL addresses or I guess we're 297 00:19:46,050 --> 00:19:48,930 calling them lightning addresses, which I think are two 298 00:19:48,930 --> 00:19:53,550 different things. I think it's worth yet again asking you for a 299 00:19:53,550 --> 00:19:59,580 little explanation if you can of what is happening there. Wow. 300 00:20:00,000 --> 00:20:04,110 Sorry. Should I not do this so close to the weekend? 301 00:20:04,470 --> 00:20:09,270 No, no, I'm fine. I'm good. I'm being amusing myself. Yes. Go 302 00:20:09,270 --> 00:20:10,470 ahead. Ask away. 303 00:20:11,940 --> 00:20:14,910 Well, what is it? What are we using? And what the hell was it 304 00:20:14,910 --> 00:20:15,390 for? 305 00:20:18,000 --> 00:20:23,160 The so there's there's asking for an attribute. I'm assuming 306 00:20:23,160 --> 00:20:25,560 this is switched on that Brandon Belinda first stab at changes to 307 00:20:25,560 --> 00:20:32,970 add L L and address. I think this is a this is an request for 308 00:20:32,970 --> 00:20:39,780 an attribute to be put in. So that you can put in an L an 309 00:20:39,900 --> 00:20:45,750 aligning address, instead of just a node ID right now, so 310 00:20:45,750 --> 00:20:46,590 that you can Yeah, 311 00:20:46,590 --> 00:20:50,730 so what I understood was, this is like the get Alby address 312 00:20:50,730 --> 00:20:56,580 where it's known URL. And, and if you test so for instance, 313 00:20:56,610 --> 00:20:59,670 although it's not set up, if you use the lightning address 314 00:20:59,670 --> 00:21:02,940 adam@curry.com, it would actually resolve to, you know, 315 00:21:02,940 --> 00:21:06,930 slash known URL, dot whatever. And then it would have a file in 316 00:21:06,930 --> 00:21:11,820 there, I think, a JSON file, and it has my, my node, my Node 317 00:21:11,820 --> 00:21:17,040 Details. Right, so that you don't have to look up. If I had 318 00:21:17,040 --> 00:21:20,310 the custom key custom value, all that stuff is in there. And it's 319 00:21:20,310 --> 00:21:25,110 just using that, too, as a shortcut to all of the details 320 00:21:25,110 --> 00:21:28,680 that you would need for your lightning wallet to either yet 321 00:21:28,680 --> 00:21:30,360 to be added. add someone to a split. 322 00:21:31,410 --> 00:21:39,600 So that it looks like it looks like and make sure. 323 00:21:40,560 --> 00:21:43,590 So I thought I thought you were a little more in the loop on 324 00:21:43,590 --> 00:21:45,360 this. If you don't know what it is we can just skip it. 325 00:21:45,570 --> 00:21:49,350 And it will I know that the I know that. There were there was 326 00:21:49,350 --> 00:21:53,160 a suggestion to add an extra attribute that was that would 327 00:21:53,160 --> 00:21:57,480 handle an address. A lightning resolved address through the dot 328 00:21:57,480 --> 00:22:02,100 well known. But it looks like what Brian has done here. I 329 00:22:02,100 --> 00:22:05,520 didn't see this before it looks like he's proposing. Did it just 330 00:22:05,550 --> 00:22:10,680 did it just be in the spec to resolve it. If they see it. So 331 00:22:10,680 --> 00:22:18,120 like it would still it would still go into? No, that's I'll 332 00:22:18,120 --> 00:22:19,530 have to read over this. And there was no 333 00:22:19,740 --> 00:22:22,140 way. I'm sorry, I didn't. That's why I asked him like what 334 00:22:22,140 --> 00:22:26,160 exactly are we doing? And I saw Roy chiming in about how that 335 00:22:26,310 --> 00:22:28,980 relates to ln URL, which is really worth it. I 336 00:22:28,980 --> 00:22:32,490 got it. I got I got this. I guess this is this is the extra 337 00:22:32,490 --> 00:22:34,620 attribute. This is what I thought it was. I misread the 338 00:22:34,620 --> 00:22:37,110 pull request. Yeah, this is the extra attribute. So he's, 339 00:22:37,560 --> 00:22:42,090 they're proposing that there be either an address attribute or 340 00:22:42,090 --> 00:22:47,490 an ln address attribute. An ln address attribute would would be 341 00:22:47,490 --> 00:22:52,290 the the resolver. Yeah, and I mean, I don't I don't really 342 00:22:52,290 --> 00:22:54,570 have. I don't really have a problem with that. I guess the 343 00:22:54,570 --> 00:22:59,820 only thing that feels awkward to me is that I'm generally 344 00:22:59,820 --> 00:23:06,930 uncomfortable with attributes that only exist based on a 345 00:23:06,930 --> 00:23:10,350 different attribute being set to a specific value. 346 00:23:10,560 --> 00:23:13,290 I hate it when that happens. I'm so against that stuff. 347 00:23:14,160 --> 00:23:17,610 I knew you would. I knew I knew if I threw that out there. You'd 348 00:23:17,610 --> 00:23:23,340 be on my side. Always. Yeah, so like, if you have type equals 349 00:23:23,340 --> 00:23:29,010 lightning, method, keys associated type equals 350 00:23:29,010 --> 00:23:34,380 lightning, then all of a sudden, you have the possibility to use 351 00:23:34,380 --> 00:23:40,560 this extra attribute ln address. But if you have type equals 352 00:23:41,490 --> 00:23:45,330 list, I don't know something. Take something else. A Mineiro 353 00:23:45,630 --> 00:23:48,030 or some some i Let's just take some other crypto crypto. 354 00:23:48,420 --> 00:23:52,740 Cryptocurrency in ln address as an attribute doesn't make any 355 00:23:52,740 --> 00:23:57,060 sense. Because there's there's nothing there that fits what 356 00:23:57,060 --> 00:24:00,150 that is. So you have an attribute. And while it is 357 00:24:00,150 --> 00:24:02,850 optional, which is fine, but you have this attribute that only 358 00:24:03,990 --> 00:24:06,960 depends on the value of a different attribute in order to 359 00:24:06,960 --> 00:24:11,490 sort of activate. And that's, I mean, it's not the end of the 360 00:24:11,490 --> 00:24:14,700 world. It's fine, but it just feels a little that doing that 361 00:24:14,700 --> 00:24:17,640 always feels a little bit awkward to me. Well, I'm 362 00:24:17,640 --> 00:24:19,410 wondering if we can have a difference? 363 00:24:19,830 --> 00:24:23,070 Well, here here's my here's my question. So if I have Adam add 364 00:24:23,070 --> 00:24:26,490 to get albie.com or Adam mccurry.com is make it easy. And 365 00:24:26,490 --> 00:24:31,380 that's my lightning address, which means that you can use 366 00:24:31,380 --> 00:24:35,490 that to resolve my node ID or whatever details. But will it 367 00:24:35,490 --> 00:24:44,670 also be my Ellen URL address? I believe no. Because that would 368 00:24:44,670 --> 00:24:45,810 be very confusing. 369 00:24:46,920 --> 00:24:54,210 Yeah. Yeah. I wonder if the I wonder if the way forward here 370 00:24:56,010 --> 00:25:03,030 is to is to just write this back so that there's an expectation 371 00:25:03,030 --> 00:25:06,450 that if the address is formatted in a different way, that it's a 372 00:25:06,450 --> 00:25:09,750 different thing. I mean, sort of like the way that if you have, 373 00:25:10,020 --> 00:25:12,840 you have different Bitcoin wallets and based on the prefix 374 00:25:12,840 --> 00:25:17,310 of the way that the hash is, you know, which wallet address type 375 00:25:17,310 --> 00:25:21,390 it is, whether it's seg wit or piano, or whatever, like, you 376 00:25:21,390 --> 00:25:23,970 kind of know, is you're looking at almost like looking at a 377 00:25:23,970 --> 00:25:28,170 header to determine what what you're dealing with. So I mean, 378 00:25:28,170 --> 00:25:31,650 it could be something as simple as if it has an add symbol in 379 00:25:31,650 --> 00:25:36,540 it, which is not in A, which is not in a lining address, excuse 380 00:25:36,540 --> 00:25:42,090 me, which is not in a node, ID. It's got an add symbol. Try to 381 00:25:42,090 --> 00:25:47,790 resolve it as a as a as a lightning address. But I don't 382 00:25:47,790 --> 00:25:48,570 know, I'm gonna assume 383 00:25:48,570 --> 00:25:51,300 Yeah, anyway. So this is why I bring it up, because it feels 384 00:25:51,300 --> 00:25:56,970 very confusing. ln URL is used a lot. And we spun our wheels 385 00:25:56,970 --> 00:26:00,240 forever on the Ellen URL mafia to get it all into the spec. 386 00:26:00,240 --> 00:26:02,880 Thanks, guys for not developing anything after all that noise. 387 00:26:04,590 --> 00:26:07,590 So annoying, because you know, upfront, it's they're just doing 388 00:26:07,590 --> 00:26:11,550 it to say it and a habit. But Ellen URL is a payment mechanism 389 00:26:11,550 --> 00:26:15,090 is extremely handy. And a lot of people use it. So we think it's 390 00:26:15,090 --> 00:26:20,340 a bad idea. If, if you have the same concept adam@curry.com to 391 00:26:20,340 --> 00:26:25,260 pay me like a Venmo address. And then Adam mccurry.com to resolve 392 00:26:26,550 --> 00:26:31,410 a my node ID. But if I don't have a lightning, an ln URL 393 00:26:31,440 --> 00:26:33,900 attached to that, then that's going to fail. And so it has to 394 00:26:33,900 --> 00:26:38,190 either both work or your, as you said, be a different identifier. 395 00:26:39,450 --> 00:26:45,570 My, my, I guess the thing I would want the most. And and I'm 396 00:26:45,570 --> 00:26:50,130 not sure if this is just me being idealistic would be that 397 00:26:50,370 --> 00:26:54,210 whatever happens on this shouldn't even be need to be in 398 00:26:54,210 --> 00:27:00,000 the spec. That this should be well, I mean, we're getting off 399 00:27:00,000 --> 00:27:05,100 in the weeds here. But but the API involved would resolve this 400 00:27:05,100 --> 00:27:10,320 on its own on its own because like that the Okay, so Elena for 401 00:27:10,320 --> 00:27:14,220 the for instance, LM pay, the LMP would do the resolution of 402 00:27:14,220 --> 00:27:17,580 that. And so in the address field in the split is just 403 00:27:17,580 --> 00:27:21,120 whatever it is just whatever it is, it's either a node ID or a 404 00:27:21,450 --> 00:27:26,730 lightning address or whatever. But then, but I understand that 405 00:27:26,730 --> 00:27:29,400 that that puts, because it here's here's what I'm imagining 406 00:27:29,400 --> 00:27:32,730 I'm imagining is to cast thematic cast, thematic does all 407 00:27:32,730 --> 00:27:38,940 of its stuff on in app. And so cast thematic is going to have 408 00:27:38,940 --> 00:27:42,540 to resolve potentially a whole bunch of lightning addresses 409 00:27:42,540 --> 00:27:45,840 ahead of time, it's already having to make a lot of web 410 00:27:45,840 --> 00:27:50,220 requests, a lot of API requests to do these payments to begin 411 00:27:50,220 --> 00:27:55,710 with. If we then hit it with a value block that has nine splits 412 00:27:55,710 --> 00:27:59,700 in it, and all of them are our lightning addresses, then cast a 413 00:27:59,700 --> 00:28:03,750 man is going to have to resolve not do nine lookups. And then 414 00:28:03,750 --> 00:28:06,630 nine more API requests, like you're talking about potentially 415 00:28:06,630 --> 00:28:10,830 20 API requests, and web resolutions, the these are no 416 00:28:10,830 --> 00:28:14,880 longer even API requests. These are general get requests for 417 00:28:14,880 --> 00:28:16,290 various web domains. I 418 00:28:16,290 --> 00:28:19,830 would say you've answered my question sufficiently that this 419 00:28:19,830 --> 00:28:23,070 is not ready to be set to be put to bed, there's a lot of thought 420 00:28:23,070 --> 00:28:27,600 needs to go into it. And I would say for the splits that I see a 421 00:28:27,600 --> 00:28:30,270 lot of comments in the in the chat room, we are late, by the 422 00:28:30,270 --> 00:28:34,680 way, for those who don't know, now available on podcast addict 423 00:28:34,740 --> 00:28:39,780 pod verse, we are let the place for your comments on how you 424 00:28:39,780 --> 00:28:43,500 want to do splits is in the GitHub. And all of this comes to 425 00:28:43,500 --> 00:28:48,000 mind because I was not paying attention. I was just going 426 00:28:48,000 --> 00:28:50,910 along with the chatter and I'm very sad about something that 427 00:28:50,910 --> 00:28:53,460 got put to bed and I think fucked up my life and other 428 00:28:53,460 --> 00:29:04,200 people's life. The Lord Jesus help me witness. We spent 429 00:29:04,200 --> 00:29:06,780 horrible, yes, it is horrible. It really is. You know, I've 430 00:29:06,780 --> 00:29:10,650 been taking over some of the duties of the day to day when 431 00:29:10,650 --> 00:29:14,820 people are asking for feed changes, feed removal, mainly 432 00:29:14,820 --> 00:29:17,700 the feed removals is a big thing. And what I'm doing is I'm 433 00:29:17,700 --> 00:29:21,180 handling the incoming, I'll make sure that it's you know that I 434 00:29:21,180 --> 00:29:25,020 see it's legit, and then I'll my answer. My final answer will be 435 00:29:25,320 --> 00:29:29,610 we'll do this within 24 hours and I copy BCC you on it and 436 00:29:29,610 --> 00:29:34,200 then I know it'll get done within 24 hours. There was a 437 00:29:34,200 --> 00:29:38,370 huge thing. We've got to get email addresses out of feed for 438 00:29:38,370 --> 00:29:41,640 the spam. I mean, James Cridland got a lot of spam it pissed him 439 00:29:41,640 --> 00:29:45,570 off. I've always said I liked getting the emails. And the My 440 00:29:45,570 --> 00:29:50,550 email address is still in my feed. But now we have a 441 00:29:50,550 --> 00:29:54,840 situation where I know Buzzsprout has removed it. So 442 00:29:54,840 --> 00:29:58,680 I'm getting people asking for a removal of feeds and I have no 443 00:29:58,680 --> 00:30:02,310 way to authenticate them. I used to be able to say, could you 444 00:30:02,310 --> 00:30:07,770 please send me this request from the same email that is in the in 445 00:30:07,770 --> 00:30:11,580 the feed. And then I then it's close enough for me to know that 446 00:30:11,610 --> 00:30:14,520 I can authenticate you as the owner of this feed. Now that's 447 00:30:14,520 --> 00:30:18,000 gone away. Congratulations. Because no one's using the text 448 00:30:18,000 --> 00:30:22,020 field, I have no mechanism to do a text verification. And I don't 449 00:30:22,020 --> 00:30:24,570 know what to ask people to do. I want you I mean, I should I say, 450 00:30:24,570 --> 00:30:28,530 go ahead and put something into your feed into a show notes. I 451 00:30:28,530 --> 00:30:32,730 mean, it's so antiquated. And I'm kicking myself because I 452 00:30:32,730 --> 00:30:36,090 just laughed at it. And I didn't think it through. And now that 453 00:30:36,090 --> 00:30:39,210 it's been implemented, you know, here we are. And I know that 454 00:30:39,390 --> 00:30:43,860 Buzzsprout is getting a lot of the there was the James did a 455 00:30:43,860 --> 00:30:47,310 story about it this morning. Oh, there's all these customer 456 00:30:47,310 --> 00:30:50,220 service requests. Yeah, we know, we can't find an email address 457 00:30:50,220 --> 00:30:58,770 in the feed. So I think we blew it. blew it on this one. A made 458 00:30:58,770 --> 00:31:05,490 made by life harder. For no good. Yes. Yeah. Yeah. No one 459 00:31:05,490 --> 00:31:11,220 cared about that. Not about me, specifically, but I'm customer 460 00:31:11,220 --> 00:31:15,360 service now for podcast index. And I can't authenticate people 461 00:31:16,169 --> 00:31:18,839 a bit. I bet our guests have thoughts about this. 462 00:31:19,620 --> 00:31:22,980 No, before we get to our guests, I want to hear Hallelujah, Amen. 463 00:31:22,980 --> 00:31:24,330 That I'm right about this. This? 464 00:31:24,360 --> 00:31:26,910 I don't know. I just don't know that I agree with it. I don't 465 00:31:26,910 --> 00:31:29,430 know that I think is so 466 00:31:31,140 --> 00:31:36,270 I have I have people saying take my feet down. Yes. So if I can't 467 00:31:36,270 --> 00:31:41,010 authenticate that person, what do I do? How do I authenticate 468 00:31:41,010 --> 00:31:43,770 that they have the right to tell me to take this down? 469 00:31:45,540 --> 00:31:48,990 We need we have to solve this with software. 470 00:31:50,130 --> 00:31:52,470 I know. But my point is, this guy 471 00:31:52,500 --> 00:31:55,470 does read lazy piece of crap. And oh, no, no, no, no, no, 472 00:31:55,500 --> 00:31:59,670 this, it's no, you're not a lazy piece crap. My point is, this 473 00:31:59,670 --> 00:32:03,930 got done, rammed through by a relatively small group who did 474 00:32:03,930 --> 00:32:07,830 not consider all the players, all the people involved. And 475 00:32:07,830 --> 00:32:12,480 granted, hand on my own bosom. I didn't think through what that 476 00:32:12,480 --> 00:32:15,810 would mean to me. In fact, because it was only about spam, 477 00:32:15,810 --> 00:32:19,710 spam, spam, but it turns out, you can't sign up for lots of 478 00:32:19,710 --> 00:32:23,130 services, and they want to authenticate you through email 479 00:32:23,130 --> 00:32:27,990 address. And so that now puts a burden on customer service of 480 00:32:27,990 --> 00:32:29,850 companies who have implemented this. 481 00:32:30,300 --> 00:32:35,310 Yes, but then you but most of these companies have taken the 482 00:32:35,310 --> 00:32:38,010 email addresses out of feeds also have a way to temporarily 483 00:32:38,010 --> 00:32:43,170 turn it back on for a certain amount of time, 2448 72 hours, 484 00:32:43,170 --> 00:32:46,710 you can turn it back on long enough to authenticate and then 485 00:32:46,710 --> 00:32:48,630 turn it back in, then it will go back. 486 00:32:49,050 --> 00:32:52,890 Okay, perfect. So there's a perfect example. I'm just saying 487 00:32:53,370 --> 00:32:56,580 that, okay, so Buzzsprout does that I presume you Buzzsprout 488 00:32:56,580 --> 00:33:01,530 you turn it back on. And so it puts a burden on their customer 489 00:33:01,530 --> 00:33:05,760 service, because a I didn't know to tell anyone that and B that 490 00:33:05,760 --> 00:33:08,010 people probably don't know that. So they're gonna have to go 491 00:33:08,010 --> 00:33:11,160 through a cycle. I'm just saying, when we change things or 492 00:33:11,160 --> 00:33:14,730 decide things, we everyone has everybody not saying that this 493 00:33:14,730 --> 00:33:18,180 was anyone's fault? I'm saying everyone's got to think it 494 00:33:18,180 --> 00:33:21,120 through because down the line, there's implications that that 495 00:33:21,420 --> 00:33:23,790 we often don't think about, I certainly didn't think about it. 496 00:33:24,480 --> 00:33:28,260 But I did think about it, and we're running out, we're sort of 497 00:33:28,260 --> 00:33:32,640 running out ahead of our skis, you know, which is that analogy 498 00:33:32,640 --> 00:33:33,120 didn't work. 499 00:33:35,370 --> 00:33:38,520 Now, try something we actually can't We can't ski try something 500 00:33:38,520 --> 00:33:38,880 else. 501 00:33:38,909 --> 00:33:44,669 Yes. We're doing something that revolt involves skis. The the 502 00:33:44,669 --> 00:33:48,899 way that the way that see what the problem the problem is not 503 00:33:48,929 --> 00:33:54,119 with the with the spec, the problem is with is with us Yes, 504 00:33:54,119 --> 00:33:57,029 not just what I'm saying the fact that we're is the way we're 505 00:33:57,029 --> 00:34:00,599 doing this through email requests, see what the proper 506 00:34:00,599 --> 00:34:04,709 structure for this should be a take my feed down, and then you 507 00:34:04,709 --> 00:34:08,039 reply with a form letter that says, here's the web page where 508 00:34:08,039 --> 00:34:11,909 you go and verify that you own this feed, and it will take it 509 00:34:11,909 --> 00:34:14,999 down automatically once you finish that process. It should 510 00:34:15,179 --> 00:34:18,089 like that we shouldn't even be having to handle these manually. 511 00:34:18,539 --> 00:34:20,369 My that's the entire point. Okay, 512 00:34:20,400 --> 00:34:24,120 so But my point is still valid when we do these things. 513 00:34:24,570 --> 00:34:28,020 invalid. Yeah, the invalid point. I just didn't validated 514 00:34:28,020 --> 00:34:28,170 it. 515 00:34:29,850 --> 00:34:35,940 So my invalidated point, which still stands, is yeah, we got to 516 00:34:35,940 --> 00:34:39,000 think about the implications all the way down the line. That's 517 00:34:39,000 --> 00:34:45,150 all I agree. I didn't think about it. And believe me, it's 518 00:34:45,150 --> 00:34:47,820 all good. But anyway, we'll never we're not we're never 519 00:34:47,820 --> 00:34:51,420 going to build that page either. So that's okay. You have to tell 520 00:34:51,420 --> 00:34:56,910 me, I'm gonna build it. No, I'm just kidding. But now I but I 521 00:34:56,910 --> 00:35:02,370 didn't even know that that that you can temporarily turn it back 522 00:35:02,370 --> 00:35:04,920 on. So there's just a lot of things that when these changes 523 00:35:04,920 --> 00:35:08,940 are made, and I felt that we're ramrodded, because the spam, 524 00:35:08,940 --> 00:35:12,600 spam, I'm getting spam, I'm just angry about that for myself, I'm 525 00:35:12,600 --> 00:35:15,630 like, whatever you and your spam, go do whatever, and didn't 526 00:35:15,630 --> 00:35:20,070 throw up the flag and say, Oh, this may bring some problems 527 00:35:20,070 --> 00:35:22,470 down the line for people, and we've got to alert them and have 528 00:35:22,470 --> 00:35:25,080 solutions. And then we could have circumvented all 529 00:35:25,080 --> 00:35:29,250 that it's all I just wrote it on the PED Build page. Oh, please. 530 00:35:32,070 --> 00:35:33,180 Here, no, I know, 531 00:35:33,180 --> 00:35:33,810 you wrote it down. 532 00:35:34,620 --> 00:35:41,550 I'm gonna do it. To see this. So here's a problem with with me, 533 00:35:42,120 --> 00:35:44,970 this, this is a problem with me, you know, you have these people 534 00:35:44,970 --> 00:35:47,220 that are like, and I saw this cartoon about this the other 535 00:35:47,220 --> 00:35:51,900 day. It was like, when there's this old adage, like, if you 536 00:35:51,900 --> 00:35:55,440 have to do something more than, you know, more than three times 537 00:35:55,440 --> 00:35:59,100 you ought, you should automate it. And, and I just completely 538 00:35:59,100 --> 00:36:03,390 ignore all of that advice. And the there's this cartoon about 539 00:36:03,390 --> 00:36:06,300 that the other day, it's like, as soon as you take you say, 540 00:36:06,300 --> 00:36:10,590 Okay, I'm going to spend over the course of of six months, I'm 541 00:36:10,590 --> 00:36:15,210 going to end up spending 25 hours dealing with this one 542 00:36:15,210 --> 00:36:19,890 specific problem. He's like, okay, I can, what I need to what 543 00:36:19,890 --> 00:36:25,680 I should do is peel off five hours, and build an automated 544 00:36:25,680 --> 00:36:29,130 solution to this problem so that I net save myself 20 hours of 545 00:36:29,130 --> 00:36:33,420 work over six months. Oh, that is a very difficult thing to 546 00:36:34,110 --> 00:36:38,250 do. But this is this is not about this is not about us. It's 547 00:36:38,250 --> 00:36:42,510 not about you. Here, John, you trust your John Spurlock as a as 548 00:36:42,510 --> 00:36:46,410 a developer. Oh, yeah. incredibly intelligent manner. 549 00:36:46,410 --> 00:36:50,820 And so he just posted 100% agree about removing emails being a 550 00:36:50,820 --> 00:36:54,330 total pain. I'm in the same boat as Adam when verifying ownership 551 00:36:54,330 --> 00:36:57,120 for op three. Now I have to tell them to go deep into the 552 00:36:57,120 --> 00:37:00,060 settings to re enable the email or paste some text in the feed 553 00:37:00,060 --> 00:37:03,690 anywhere Good luck having anyone knowing anything about txt way 554 00:37:03,690 --> 00:37:06,870 worse than dealing with some unwanted attention to email 555 00:37:06,870 --> 00:37:13,950 addresses revert, he says that was the word I was always 556 00:37:13,950 --> 00:37:19,350 looking for. Rolling back, just pointing something out as a non 557 00:37:19,350 --> 00:37:23,970 technical person as someone who just is in the trenches. And all 558 00:37:23,970 --> 00:37:27,510 of a sudden, this happened and you know, I didn't think about 559 00:37:27,510 --> 00:37:29,970 it. No one else thought about it and it just, it just ruined my 560 00:37:29,970 --> 00:37:30,420 day. 561 00:37:31,170 --> 00:37:33,270 Okay, and I have marching orders now. 562 00:37:33,300 --> 00:37:38,040 No, no, no, no, you don't. I understand what to do. I'm gonna 563 00:37:38,040 --> 00:37:42,150 push this back. Well, if, if if a host does not have email 564 00:37:42,150 --> 00:37:45,360 addresses, I will say please ask your host. How you can 565 00:37:45,360 --> 00:37:46,140 authenticate? 566 00:37:46,500 --> 00:37:48,240 is Ted Hoffman's fault. 567 00:37:49,350 --> 00:37:52,440 No, I blame it on James crude wrote this I blame it on James 568 00:37:52,440 --> 00:37:53,970 Cridland. What do you blame everything 569 00:37:53,970 --> 00:37:54,420 on Jason? 570 00:37:54,810 --> 00:37:56,310 It's all his fault, obviously. 571 00:37:58,440 --> 00:38:02,460 This is this is this is somebody else's fault. But mine let's 572 00:38:02,460 --> 00:38:03,660 let's leave it at this. It's not 573 00:38:03,660 --> 00:38:08,310 your fault. But I certainly was told it was totally my fault for 574 00:38:08,310 --> 00:38:12,750 not for joking around about it because I like I like spam. You 575 00:38:12,750 --> 00:38:13,560 know, this is a 576 00:38:13,560 --> 00:38:19,020 serious quiz. This is a serious question, though. I'm very 577 00:38:19,020 --> 00:38:24,180 willing to create a service of some sort. Because we need it. I 578 00:38:24,180 --> 00:38:27,480 don't we need to get out of the manual curation of feed business 579 00:38:27,510 --> 00:38:32,100 anyway. I'm very willing to write some sort of service that 580 00:38:32,100 --> 00:38:32,700 will 581 00:38:33,780 --> 00:38:35,040 your comms the but 582 00:38:35,850 --> 00:38:39,960 Yuko I know there's nobody in here. I mean, there's one in the 583 00:38:39,960 --> 00:38:44,130 room. But I mean, like there's there's there's no I'm very 584 00:38:44,130 --> 00:38:48,390 willing to write a service that will that everybody can use to 585 00:38:48,390 --> 00:38:53,640 do feedback ownership validation on the on the new sort of in the 586 00:38:53,640 --> 00:39:00,150 new way or in the old way like email to TXT record Thing and 587 00:39:00,180 --> 00:39:04,590 Thing in the feed somewhere like I don't that's not a hard thing 588 00:39:04,590 --> 00:39:08,550 to write. And we need it and other people could use it I 589 00:39:08,550 --> 00:39:11,100 mean, there could just be a dog you just have a service you know 590 00:39:11,130 --> 00:39:15,060 about owner validate.io 591 00:39:15,660 --> 00:39:18,090 But I don't think we should be the ones mainly making that 592 00:39:18,090 --> 00:39:22,170 service. Why should we take your valuable resources be doing that 593 00:39:22,200 --> 00:39:26,850 for effectively something hosting companies do for us? For 594 00:39:26,850 --> 00:39:30,210 us or just for us know denote but then we get we're not 595 00:39:30,210 --> 00:39:31,530 getting rent charge people to use it. 596 00:39:32,340 --> 00:39:39,360 Okay. 100 bucks a month. $1,000 a month splits split. I don't 597 00:39:39,360 --> 00:39:43,350 know. I don't know. I mean, I get being ornery on purpose. But 598 00:39:43,350 --> 00:39:48,180 I get your I get your I get your point. And I get John John's 599 00:39:48,180 --> 00:39:49,890 point. I'm not 600 00:39:51,810 --> 00:39:55,470 just looking. I just want to say the genesis of this did not come 601 00:39:55,470 --> 00:40:00,570 from a good place. The Genesis came from a cast taking people's 602 00:40:00,600 --> 00:40:04,140 email addresses from hosting companies and trying to hijack 603 00:40:04,140 --> 00:40:08,700 customers. That's, that's the genesis of this. And so I think 604 00:40:08,700 --> 00:40:12,690 as a group, as a loose group, we responded knee jerk and didn't 605 00:40:12,690 --> 00:40:15,570 think about what we were doing. It was more like fuck a caste. 606 00:40:15,570 --> 00:40:20,160 And I was all in on that part. I mean, of course, I'm all in 607 00:40:20,160 --> 00:40:23,010 fact, those guys. Fuck anchor, anybody, anybody who's not part 608 00:40:23,010 --> 00:40:28,230 of our team is is by definition enemy or potential ally, enemy 609 00:40:28,230 --> 00:40:28,740 first 610 00:40:30,750 --> 00:40:34,170 enemy of the state. But that's that. That makes sense. 611 00:40:34,320 --> 00:40:37,800 I'm just I'm just pointing out that, you know, I think that was 612 00:40:38,760 --> 00:40:41,250 all of us when we were we weren't really thinking 613 00:40:41,250 --> 00:40:44,370 straight. We could have had, it's not a huge deal. But we 614 00:40:44,370 --> 00:40:47,010 could have had a little more thought about what are we really 615 00:40:47,010 --> 00:40:50,850 doing here? Well, I mean, what? 616 00:40:51,480 --> 00:40:51,840 Sorry, are 617 00:40:51,900 --> 00:40:52,740 you running away? 618 00:40:53,340 --> 00:40:57,870 I hit I hit the mic back. I mean, this is but you know, this 619 00:40:57,870 --> 00:41:03,420 is what happens. You run with scissors, you sometimes you 620 00:41:03,600 --> 00:41:05,340 sometimes you fall and hit the jugular. 621 00:41:06,000 --> 00:41:08,880 Now gonna have one I left because I poked one out with the 622 00:41:08,880 --> 00:41:14,070 scissors. Yeah, that's it. You know, I'm just saying, we all 623 00:41:14,070 --> 00:41:16,110 just need to think about what we're doing. So that's when, 624 00:41:16,320 --> 00:41:19,260 when when I see ln URL and lightning addresses and like, 625 00:41:19,260 --> 00:41:23,580 Let's all think about everything down the line where that might 626 00:41:23,580 --> 00:41:26,400 screw something up, because we're not necessarily all 627 00:41:26,400 --> 00:41:29,880 thinking about it in the same way. Does that make sense? I 628 00:41:29,880 --> 00:41:30,300 agree. 629 00:41:30,570 --> 00:41:33,240 I agree. 100% With that, yes. All right, 630 00:41:33,240 --> 00:41:43,260 everybody. 100% 100 100 So today's unless you have 631 00:41:43,260 --> 00:41:45,540 anything, unless you have anything else to annoy you with? 632 00:41:46,169 --> 00:41:47,759 No, I mean, I mean, granola. 633 00:41:48,810 --> 00:41:53,280 Granola. Yeah. What happened to your beef milkshakes? That's 634 00:41:53,280 --> 00:41:54,660 what I want you eating? Or do you have 635 00:41:54,660 --> 00:41:57,240 one of those, I have one of those before the show. That was 636 00:41:57,600 --> 00:41:58,710 my Bistro, 637 00:41:58,740 --> 00:42:02,010 I really got to try these beef milkshakes out. It's pretty 638 00:42:02,010 --> 00:42:05,520 good. You've been you've been been high status, praise has 639 00:42:05,520 --> 00:42:11,370 been high. We have two guests in our board board meeting for 640 00:42:11,370 --> 00:42:16,860 today. And one of them. One of them did a live show the other 641 00:42:16,860 --> 00:42:21,630 day, which was, I would say one of my most favorite experiences 642 00:42:21,630 --> 00:42:23,940 of all time. And it really proved to me that we're onto 643 00:42:23,940 --> 00:42:28,530 something with a new format here. Something that's new, I 644 00:42:28,530 --> 00:42:31,950 mean, it's it's a little bit like the YouTube model where you 645 00:42:31,950 --> 00:42:36,030 do a YouTube Live, except this is done by people who kind of 646 00:42:36,030 --> 00:42:38,430 know what they're doing when it comes to doing something live. 647 00:42:39,240 --> 00:42:45,240 So it's live audio smash cuts, live audio stream. And but with 648 00:42:45,240 --> 00:42:49,830 booster grams coming in, it really made for an experience 649 00:42:49,830 --> 00:42:53,160 that, you know, we know that you will talk about, well, if you do 650 00:42:53,160 --> 00:42:56,250 a YouTube Live, you have the Super Chat. There was nothing 651 00:42:56,250 --> 00:42:59,760 like this. When you hear the pew pew, which is now kind of 652 00:42:59,760 --> 00:43:02,850 universal for something coming in. And then there's a response 653 00:43:02,850 --> 00:43:05,820 from the people doing the show live. Then at a certain point, 654 00:43:05,820 --> 00:43:09,060 you and I were boosting just talking to each other. And Todd. 655 00:43:09,990 --> 00:43:14,160 Todd was literally in the middle just like here's 20,000 SATs, 656 00:43:14,160 --> 00:43:18,480 Adam waves to Dave. I mean, come on. That's something very cool. 657 00:43:18,990 --> 00:43:22,620 And then at the end of all this, the end of this this this lit 658 00:43:22,620 --> 00:43:28,680 session. It was like this realization from Rob co host of 659 00:43:28,680 --> 00:43:32,100 a new media show that oh man, maybe there's some other way to 660 00:43:32,100 --> 00:43:35,760 do things than what we've been doing. And I think I got the ISO 661 00:43:35,760 --> 00:43:37,470 of all ISOs and this is it. 662 00:43:38,100 --> 00:43:44,520 Ding ding ding ding ding ding ding ding ding ding ding ding 663 00:43:44,520 --> 00:43:47,280 ding ding ding ding ding ding ding. Ladies and 664 00:43:47,280 --> 00:43:50,190 gentlemen, say hello to the man behind that voice along with his 665 00:43:50,220 --> 00:43:52,500 partner, Mike Dell, Todd Cochran. Everybody from 666 00:43:52,500 --> 00:43:59,280 blueberry. Hey, everybody. Hey, Mike. You they're thinking Ding 667 00:43:59,280 --> 00:44:01,770 ding ding ding ding ding ding ding ding. 668 00:44:03,120 --> 00:44:05,880 I heard that. I knew you guys. Were gonna ISO. 669 00:44:06,330 --> 00:44:10,830 Yeah, make sense? I was. I actually, I spent some time 670 00:44:10,830 --> 00:44:13,920 getting that like, Oh, stop the stop this show. Oh, roll that 671 00:44:13,920 --> 00:44:16,440 back a little bit. I'm doing Oh, yeah, I was recording it in real 672 00:44:16,440 --> 00:44:17,340 time was beautiful. 673 00:44:18,540 --> 00:44:22,290 And I think Rob at that moment, had the epiphany moment. He's 674 00:44:22,290 --> 00:44:25,650 like, oh, oh, yeah. It was hilarious. 675 00:44:25,920 --> 00:44:31,620 So me a little background here. Todd has been in the podcasting, 676 00:44:31,710 --> 00:44:39,330 almost as long as I have early proponent, early promoter, early 677 00:44:39,330 --> 00:44:42,570 part of the infrastructure, literally wrote the book about 678 00:44:42,570 --> 00:44:49,980 podcasting and has as run so many different really coming 679 00:44:49,980 --> 00:44:53,940 community based initiatives which I've been so appreciative 680 00:44:53,970 --> 00:44:57,930 of. Also longtime supporter of the no agenda show understood 681 00:44:57,930 --> 00:45:04,530 the value for value model year A deck more than a decade ago and 682 00:45:04,920 --> 00:45:09,870 had your own I guess, epiphany of sorts, and seeing you with 683 00:45:09,870 --> 00:45:14,220 that exact same vigor from almost two decades ago. I gotta 684 00:45:14,220 --> 00:45:19,350 tell you, it really lifts my heart, Todd, I'm so pleased to 685 00:45:19,350 --> 00:45:23,700 see it and immediately have to ask, what's going wrong that you 686 00:45:23,700 --> 00:45:25,020 jumped on this bandwagon? 687 00:45:26,130 --> 00:45:30,690 I think it had that. I think it was, I got hit in the mouth on 688 00:45:31,080 --> 00:45:34,140 one of your guys's episodes, I can't remember the number I was 689 00:45:34,140 --> 00:45:37,320 literally driving down the highway and it was like, bands 690 00:45:37,320 --> 00:45:39,480 like somebody slapped me upside the head. And I'm in the in I've 691 00:45:39,480 --> 00:45:42,120 been thinking about this all wrong. That is really, it really 692 00:45:42,120 --> 00:45:44,010 was listened to and one of the board meetings. 693 00:45:45,660 --> 00:45:50,460 So I think the whole industry had pretty much just completed 694 00:45:50,460 --> 00:45:54,060 their dynamic ad insertions, more or less at the same time. 695 00:45:54,090 --> 00:45:58,200 This was nothing. And it's, it's almost like it's almost as funny 696 00:45:58,200 --> 00:46:02,340 as divorce, like bringing out the too many eggs book at the 697 00:46:02,340 --> 00:46:08,130 moment, there's an egg shortage. Which, you know, and so the 698 00:46:08,160 --> 00:46:11,460 everyone came out with their egg insertion system. And then when 699 00:46:11,460 --> 00:46:14,670 we It seems like eggs are just kind of a thing of the past, you 700 00:46:14,670 --> 00:46:18,900 know, advertising is slowing down? I mean, I know it works. I 701 00:46:18,900 --> 00:46:22,980 know what's out there. But is this just a question of, okay, 702 00:46:22,980 --> 00:46:26,100 we've completed that it works. And now we're moving on to the 703 00:46:26,100 --> 00:46:31,410 next thing, or or is this more structural? Take me through that 704 00:46:31,410 --> 00:46:32,160 process? 705 00:46:32,670 --> 00:46:35,400 Well, you know, we spent two years rebuilding our platform, 706 00:46:35,400 --> 00:46:39,960 and I had this like, huge list of stuff I wanted to do. And we 707 00:46:39,960 --> 00:46:44,070 got the rebuild done of the platform, reskin it and launched 708 00:46:44,070 --> 00:46:46,590 it and then we started adding add ons. And then I started 709 00:46:46,920 --> 00:46:50,700 really thinking about how do we really help the listeners 710 00:46:50,700 --> 00:46:54,000 because I talked to content creators that are not listeners, 711 00:46:54,060 --> 00:46:56,910 graders, how do we how do we I know you hate that word. But how 712 00:46:56,910 --> 00:47:01,380 do we help the podcasters? Because it talks them on the 713 00:47:01,380 --> 00:47:03,600 phone and it's about Grow, grow? How do I grow my show? How do I 714 00:47:03,600 --> 00:47:05,940 grow my show, I don't even hear people talking to me about 715 00:47:05,940 --> 00:47:08,820 monetizing here. And then growing your shows we really, 716 00:47:08,850 --> 00:47:11,280 but this is your fault. It's true, but we 717 00:47:12,480 --> 00:47:13,920 hear Mr. Grow your show 718 00:47:14,130 --> 00:47:18,750 so far. So we always like a chia pet. So we started really 719 00:47:18,750 --> 00:47:22,380 focused on you know, bringing stuff to the podcasters is going 720 00:47:22,380 --> 00:47:24,570 to help them grow their show and connect with their audience. So 721 00:47:24,960 --> 00:47:28,200 the podcasting 2.0 stuff just kind of fit perfectly into that. 722 00:47:28,200 --> 00:47:30,390 But be honest with you, I was kind of holding back because it 723 00:47:30,390 --> 00:47:33,600 was again that chicken and egg. And I finally realized, Okay, 724 00:47:33,600 --> 00:47:37,350 we've got about a access to about 100,000 podcasters. Not 725 00:47:37,350 --> 00:47:39,600 all of them host with this, I need a lot of them that use 726 00:47:39,600 --> 00:47:42,930 power press are hosted on Lipson, you know, variety of 727 00:47:42,930 --> 00:47:47,430 different platforms. And I said, we can dump this into power 728 00:47:47,430 --> 00:47:49,980 press, and we can also build it in their blueberry dashboard. 729 00:47:50,010 --> 00:47:54,090 And we can one full swoop, give 100,000 podcasters the ability 730 00:47:54,090 --> 00:47:58,290 to turn this on. So I said let's do it. And the team agreed and 731 00:47:58,290 --> 00:48:02,820 metric, Dave, and you and Dave came on and talked to my team 732 00:48:03,090 --> 00:48:06,630 graciously. And my whole team was like, high five, let's go. 733 00:48:06,630 --> 00:48:08,640 And that was you know, last summer when you guys came on and 734 00:48:08,640 --> 00:48:09,210 talk to us. 735 00:48:10,170 --> 00:48:12,150 Yeah, that's that was good. Hey, those are fun. Yeah, those are 736 00:48:12,150 --> 00:48:18,120 fun. Fun get together. And that. I mean, when you think about it, 737 00:48:18,570 --> 00:48:22,110 I mean, I guess you realize you sort of that you're the egg in 738 00:48:22,110 --> 00:48:24,810 the chicken. Yeah, I mean, because the that's the that's 739 00:48:24,810 --> 00:48:27,210 the thing. I had a great little gig great call with the guys 740 00:48:27,210 --> 00:48:32,010 from wave Lake yesterday. And we were just talking about, we're 741 00:48:32,010 --> 00:48:35,220 talking about the app side of things. And it sort of we got 742 00:48:35,220 --> 00:48:38,220 into this, we got into this discussion about this debate, 743 00:48:38,220 --> 00:48:40,830 the classic chicken egg problem when it comes to decentralized 744 00:48:40,830 --> 00:48:42,960 stuff like this. And I was telling them, I'm like, you 745 00:48:42,960 --> 00:48:46,890 know, we really decided at some point, we just had to focus 746 00:48:46,890 --> 00:48:50,700 almost exclusively. It's like we, we love the apps. And we 747 00:48:50,700 --> 00:48:54,150 want to add that the app developers are who were who were 748 00:48:54,150 --> 00:48:58,050 trying to do all this stuff for. But in order, it's like in order 749 00:48:58,050 --> 00:49:03,000 to love them, we have to get the the content because nobody's 750 00:49:03,000 --> 00:49:06,720 going to write app features for content that doesn't exist, 751 00:49:06,840 --> 00:49:10,830 right? That's it really goes from the producer, to the 752 00:49:10,830 --> 00:49:14,820 consumer. And you know, hosting companies being the producer. 753 00:49:15,090 --> 00:49:19,260 It's like we had to get traction there. Because if you produce 754 00:49:19,260 --> 00:49:23,490 the content, then the apps over time evolve to consume the 755 00:49:23,490 --> 00:49:27,030 content that you're giving them. Like it's, it's, that's one of 756 00:49:27,030 --> 00:49:30,450 the most exciting things about all this, that all the just 757 00:49:30,900 --> 00:49:33,270 avalanche of features you've put out as you went, you went a 758 00:49:33,270 --> 00:49:37,890 whole hog like, yeah, we're going all phase one. And you 759 00:49:37,890 --> 00:49:41,520 know, you unleash the Kraken. And now you've got all these now 760 00:49:41,520 --> 00:49:45,750 you get so many feeds that have like a like a, like a sandbox, a 761 00:49:45,750 --> 00:49:48,480 playground of stuff that app developers can fool with is 762 00:49:48,480 --> 00:49:49,020 awesome. 763 00:49:49,440 --> 00:49:51,510 And Mike's working on list number two, 764 00:49:51,990 --> 00:49:55,410 yeah. Well got nine more tags in the list. 765 00:49:55,440 --> 00:49:58,380 Okay, so, Mike, where do you fit into the story? 766 00:49:59,010 --> 00:50:03,660 Well, I volunteered to be the project manager for this 2.0 767 00:50:03,660 --> 00:50:07,950 project at blueberry. And I've been the one that's been sort of 768 00:50:08,070 --> 00:50:10,320 making making sure you're hurting the cat. 769 00:50:11,580 --> 00:50:13,440 I haven't been the same since I'm sure. 770 00:50:13,590 --> 00:50:18,330 Although tat Todd kind of takes that job a lot to between us 771 00:50:18,330 --> 00:50:23,550 where we're keeping them busy. But I'm, I'm super excited about 772 00:50:23,550 --> 00:50:26,820 this stuff. It kind of reminds me when podcasting started, I 773 00:50:26,820 --> 00:50:31,620 didn't come in too far behind Todd, in podcasting. And this 774 00:50:31,620 --> 00:50:33,270 just feels like the beginning again. 775 00:50:34,500 --> 00:50:39,930 Yeah, yeah. So what helped? Let's, let's just go ahead and 776 00:50:39,930 --> 00:50:43,620 hit some some features here. Because I guess the one that I'm 777 00:50:43,650 --> 00:50:46,680 most interested in kind of right off the top is is the live item. 778 00:50:46,920 --> 00:50:51,150 So how, how are you handling that? Are you just allow? Are 779 00:50:51,150 --> 00:50:56,970 you allowing a podcaster to put the live information into their 780 00:50:56,970 --> 00:51:01,290 feed or you facilitating a communication back and forth 781 00:51:01,290 --> 00:51:05,670 with a with a live stream? Like how how's that? Explain how 782 00:51:05,670 --> 00:51:06,990 that's functioning? Yeah, 783 00:51:07,440 --> 00:51:11,790 we're allowing them to put in the information into the feed, 784 00:51:12,930 --> 00:51:14,700 bulletin, both platforms 785 00:51:15,810 --> 00:51:19,650 that were not facilitating the stream part yet. But I have said 786 00:51:19,650 --> 00:51:22,980 to our traders, if you want to be an I have a shoutcast stream. 787 00:51:22,980 --> 00:51:25,110 And I basically said, if you want to experiment with this, 788 00:51:25,110 --> 00:51:29,100 and you want to, you know, a time slot, we'll give you one on 789 00:51:29,100 --> 00:51:32,070 something we're running. But you know what, we've got to look at 790 00:51:32,070 --> 00:51:34,980 this long term and decide if we're going to if we're going to 791 00:51:35,010 --> 00:51:37,530 add some sort of streaming service to the platform that 792 00:51:37,680 --> 00:51:40,920 that hasn't been decided yet, but definitely getting the 793 00:51:40,920 --> 00:51:43,350 function in there. And you know, here's thing, we get the 794 00:51:43,350 --> 00:51:46,230 function, and then it's going to take us six months to get people 795 00:51:46,230 --> 00:51:47,220 to fully understand it. 796 00:51:48,390 --> 00:51:55,200 Well, and this, this is what I love about you. All the podcast 797 00:51:55,200 --> 00:51:58,470 host, basically, let me step back for a second. So there's 798 00:51:58,500 --> 00:52:03,390 always been this in podcasting. Before this project started has 799 00:52:03,390 --> 00:52:06,030 always been the world. You know, Apple doesn't do it. Well, 800 00:52:06,030 --> 00:52:12,300 Spotify does No Baba. So we have now apps, which and that's the 801 00:52:12,330 --> 00:52:15,480 praise, praise the Lord for the app developers who said, You 802 00:52:15,480 --> 00:52:19,080 know what, this is fun. I don't expect much, I'm just going to 803 00:52:19,080 --> 00:52:22,170 build an app with different experiences. And we're seeing 804 00:52:22,170 --> 00:52:24,570 the people getting pretty busy apps are getting pretty busy, 805 00:52:24,840 --> 00:52:29,040 that it's still a minut percentage of the overall 806 00:52:31,680 --> 00:52:36,120 landscape of apps and the big apps. But as Dave pointed out 807 00:52:36,120 --> 00:52:42,540 chicken and egg, when content is being produced 300,000 from 808 00:52:42,540 --> 00:52:47,250 Buzzsprout. I don't know how many 100,000 for let's forget 809 00:52:47,250 --> 00:52:51,450 the numbers rss.com, RSS blue.com. Blueberry, now we're 810 00:52:51,450 --> 00:52:54,870 talking hundreds of 1000s, half a million, maybe moving towards 811 00:52:55,050 --> 00:52:59,100 a million feeds that will have some version of the namespace in 812 00:52:59,100 --> 00:53:03,210 it. It is it is as far as I'm concerned and and foregone 813 00:53:03,210 --> 00:53:09,210 conclusion that every app will eventually have to surface this 814 00:53:09,210 --> 00:53:14,070 dead data. It is in fact the nature of publishing. That when 815 00:53:14,070 --> 00:53:19,620 features are being utilized, and being published, apps eventually 816 00:53:19,620 --> 00:53:23,430 cannot. It's like it's a human thing. You can't even I think as 817 00:53:23,430 --> 00:53:27,780 a developer, you look at that, like, Ah, I want to put that 818 00:53:27,780 --> 00:53:31,110 into my app, somehow. The only thing stopping it is corporate 819 00:53:31,110 --> 00:53:36,090 structure. It is a human developer thing. Am I correct 820 00:53:36,090 --> 00:53:38,040 there Dave? Is that what you were saying? Yeah, 821 00:53:38,040 --> 00:53:38,460 the 100 822 00:53:45,030 --> 00:53:47,400 You're gonna do that you're going to shame me into stopping 823 00:53:47,400 --> 00:53:53,580 soon. Thank you, by the way, that I should be ashamed. That 824 00:53:53,580 --> 00:53:56,670 is 100%. Right? I just did it again. I'm gonna hold back. 825 00:53:57,030 --> 00:54:01,980 Okay. So the, when you whenever you're a developer, and you look 826 00:54:01,980 --> 00:54:06,840 out there and you say, Okay, I got this podcast app. And, and 827 00:54:06,840 --> 00:54:10,410 then I see that there's all of these tags in here with this 828 00:54:10,410 --> 00:54:14,580 rich content, that that my app does nothing with, it's just 829 00:54:14,580 --> 00:54:17,820 basically ignoring it. It's just, it's just a green field 830 00:54:17,820 --> 00:54:20,940 that you would, you can't help it you have to go in there and 831 00:54:20,970 --> 00:54:24,570 and, and start doing start coding towards it. Because 832 00:54:24,840 --> 00:54:27,330 otherwise, it's just you feel wrong, not doing it. 833 00:54:28,110 --> 00:54:31,680 And I think what also happened to is if Marco and some of the 834 00:54:31,680 --> 00:54:34,530 other folks podcasts, add a confound, and they start adding 835 00:54:34,530 --> 00:54:39,420 everything, then what will happen is, is listeners and even 836 00:54:39,420 --> 00:54:42,210 the podcasters themselves will be in these apps and say, Well, 837 00:54:42,240 --> 00:54:45,660 how does he have his guests listed there? How does he have 838 00:54:45,660 --> 00:54:50,040 his location data in there? How How come that's not in my feed? 839 00:54:50,040 --> 00:54:52,440 How come and then they're gonna go back to their hosting 840 00:54:52,440 --> 00:54:56,580 provider and say, Why can't I do this? And that's going to drive 841 00:54:56,580 --> 00:54:58,020 it fullcycle correct. 842 00:54:58,080 --> 00:55:01,650 And that happens already taught with you Yes, it's like a wind 843 00:55:01,650 --> 00:55:05,100 bed. Like when you have those preview card embeddings and 844 00:55:05,100 --> 00:55:07,290 social media and stuff. Yeah, see those things? And they're 845 00:55:07,290 --> 00:55:09,870 like, Oh, what is that? How can I do that in my posts? So 846 00:55:09,870 --> 00:55:14,820 when I hear that some unnamed person high up in the podcasting 847 00:55:14,820 --> 00:55:19,050 industry, James who was it says, Well, you know, it's not going 848 00:55:19,050 --> 00:55:23,430 anywhere, they got no marketing. We have more marketing than 849 00:55:23,430 --> 00:55:27,510 anybody could ever purchase. We have hundreds of 1000s of 850 00:55:27,510 --> 00:55:32,220 podcasters. who eventually will say, you know, that's why we 851 00:55:32,220 --> 00:55:38,190 make new podcast apps.com. Just, it's a call to Cluj. It's not a 852 00:55:38,190 --> 00:55:43,080 great way to do it. But it's a way then I see. We have the 853 00:55:43,080 --> 00:55:46,740 excitement around fountain with their top 10 most supported 854 00:55:46,740 --> 00:55:50,580 episode list, which is is on Twitter, and I think goes pretty 855 00:55:50,580 --> 00:55:54,570 viral. And people like, Well, how do I get on that list? This 856 00:55:54,570 --> 00:55:58,140 is how podcasting has always been marketed. There's no 857 00:55:58,140 --> 00:56:01,740 marketing team for podcasting. Nor should there be a podcasting 858 00:56:01,740 --> 00:56:05,400 to point. In fact, podcasting. 2.0 It's just podcasting. It's 859 00:56:05,400 --> 00:56:10,380 just with new features. And it will always get we are so far 860 00:56:10,380 --> 00:56:12,690 beyond maybe it'll happen is happening 861 00:56:13,920 --> 00:56:18,000 in you know, go ahead. And you and I know what happened. You 862 00:56:18,000 --> 00:56:21,360 know, as soon as Apple came in, in 2005, and introduced 863 00:56:21,360 --> 00:56:25,710 podcasting, iTunes, everything stopped, there was no more 864 00:56:25,740 --> 00:56:26,370 innovation, 865 00:56:26,580 --> 00:56:29,610 mistakes were made, I made mistakes that I made mistakes 866 00:56:29,610 --> 00:56:30,210 myself, 867 00:56:30,420 --> 00:56:36,960 it just it just stopped. And so we've allowed Spotify, Apple, 868 00:56:37,080 --> 00:56:41,580 Google, to set the tone, and introduce their own namespace 869 00:56:41,580 --> 00:56:45,180 and their own, you know, was what we want? Well, and we've 870 00:56:45,180 --> 00:56:50,580 taken that back now. And my, my perspective is, I understand 871 00:56:50,580 --> 00:56:53,640 that, but for the average podcaster, they don't give two 872 00:56:53,640 --> 00:56:56,940 shits. So we have to explain. Yeah, what the features are. 873 00:56:56,970 --> 00:56:59,610 But that's what that's what you do. That's what podcast hosts 874 00:56:59,610 --> 00:57:04,770 have always done. You do weekly shows, you have FAQs, you have 875 00:57:05,010 --> 00:57:07,470 the I think you can actually just put yourself on your 876 00:57:07,470 --> 00:57:10,530 calendar and waste your time for an hour. I mean, it's not can I 877 00:57:10,530 --> 00:57:15,630 just get on the CEO, blueberries calendar? You have that? I know 878 00:57:15,630 --> 00:57:20,850 you can. I know. Right? Yeah. I mean, that's amazing. That's 879 00:57:20,850 --> 00:57:23,670 what has to be done. And it's happening. It'll just take a 880 00:57:23,670 --> 00:57:26,610 while. So we have what five people raise their hand at pod 881 00:57:26,610 --> 00:57:29,220 fest when you said Who knows what podcasting. 2.0 is, 882 00:57:29,520 --> 00:57:33,990 it blew me away. So you know, I got 10 minutes to do 22 slides 883 00:57:33,990 --> 00:57:35,730 and I'm you know, I'm hitting all the key points, you know, 884 00:57:35,730 --> 00:57:39,360 Valley free value for value dot info, new podcast, apps.com, you 885 00:57:39,360 --> 00:57:42,420 know, I'm hitting them hitting it hitting them. And, and I 886 00:57:42,420 --> 00:57:46,950 think when I went and did a procession later, I got to break 887 00:57:46,950 --> 00:57:49,680 this up, those same five people were in the back of the room. So 888 00:57:50,280 --> 00:57:53,760 the pros knew about it, but the general population did it. So I 889 00:57:53,760 --> 00:57:55,560 think it's just gonna be one of those things, they're gonna go 890 00:57:55,560 --> 00:57:58,290 home. And, you know, they've been fed by the firehose at a 891 00:57:58,290 --> 00:57:59,910 conference, because they've listened to a bunch of stuff. 892 00:57:59,910 --> 00:58:01,470 And then I'm gonna think about what that dude was talking 893 00:58:01,470 --> 00:58:03,870 about, what was he talking about podcasting? 2.0, and he's gonna 894 00:58:03,870 --> 00:58:06,690 start looking around. So now we need to make sure that the 895 00:58:06,690 --> 00:58:11,070 resources online, are there for those folks that go to look for 896 00:58:11,070 --> 00:58:11,430 the, 897 00:58:11,910 --> 00:58:14,370 for the education piece education piece. 898 00:58:14,940 --> 00:58:18,450 And it's specific to each individual hosting company. 899 00:58:18,660 --> 00:58:21,750 Absolutely, you have a different UI, you have a selected amount 900 00:58:21,750 --> 00:58:24,600 of features that you're supporting. And I see that 901 00:58:24,600 --> 00:58:28,470 happening everywhere. And I hear that, you know, it's taken a 902 00:58:28,470 --> 00:58:31,500 couple years, but I hear the words I hear I hear the right 903 00:58:31,500 --> 00:58:35,880 words being used by a lot of different people. And with how 904 00:58:35,880 --> 00:58:38,760 it works, how value for value works, I'm kind of hearing the 905 00:58:38,760 --> 00:58:43,380 words, it's working. So it is out there, what do we have you 906 00:58:43,380 --> 00:58:46,710 track now how many feeds that are connected to your 907 00:58:46,710 --> 00:58:51,690 infrastructure, either through power press is what it's called, 908 00:58:51,690 --> 00:58:52,530 I think power press 909 00:58:52,860 --> 00:58:55,620 that Well, I think, you know, probably Dave has better data on 910 00:58:55,620 --> 00:58:58,320 how many people have turned stuff on. So again, is just, you 911 00:58:58,320 --> 00:59:01,590 know, we finally released everything final in power press 912 00:59:01,590 --> 00:59:05,610 on Monday. So again, now it's, we're going to do one feature at 913 00:59:05,610 --> 00:59:08,490 a time, like matter of fact, we're restructuring our internal 914 00:59:08,490 --> 00:59:12,750 podcast to be able to focus on talking about in depth one 915 00:59:12,750 --> 00:59:16,020 feature per episode so that we can make people understand, 916 00:59:16,020 --> 00:59:19,350 okay, this is why you need to do credits and this is the benefit. 917 00:59:19,920 --> 00:59:23,520 And little by little get people kind of up to speed but again, 918 00:59:23,520 --> 00:59:26,310 it's going to take time and we're going to have to socially 919 00:59:26,310 --> 00:59:28,560 hammer them and we're going to have to do on Facebook and we're 920 00:59:28,560 --> 00:59:31,890 going to have to you know, reach out as much as we can, some will 921 00:59:31,890 --> 00:59:35,310 some won't, but that's okay, as long as we get in as much as 922 00:59:35,310 --> 00:59:40,440 much as this geeks like to talk geekery getting this out to the 923 00:59:40,470 --> 00:59:45,540 normal podcaster you know, using the word feature instead of tag 924 00:59:45,540 --> 00:59:50,550 right and using other things like that, that just make it 925 00:59:50,550 --> 00:59:53,820 seem like it's a you know, something that you know, that's 926 00:59:53,820 --> 00:59:58,650 been around a while they'll they may you know pick it up and you 927 00:59:58,650 --> 01:00:02,400 know as this Brad's out more. Like I said, I really wish Marco 928 01:00:02,850 --> 01:00:06,600 would start doing that. Because overcast is one of the bigger 929 01:00:06,600 --> 01:00:10,800 apps, at least on my personal show. That, you know, most of my 930 01:00:10,800 --> 01:00:13,950 listeners come from that I don't have very little apple on that. 931 01:00:13,950 --> 01:00:14,490 And for some 932 01:00:14,490 --> 01:00:16,980 reason telling my audience you're using a legacy app if 933 01:00:16,980 --> 01:00:20,250 you're not using a podcast app from new podcasts apps.com And 934 01:00:20,250 --> 01:00:23,280 they say legacy Yeah, yeah, yeah. Oh, land, 935 01:00:24,030 --> 01:00:28,440 you know, so. So the, one of the great ways to promote this, of 936 01:00:28,440 --> 01:00:32,040 course, is just by say, at telling or asking your listeners 937 01:00:32,040 --> 01:00:35,580 to try out a modern podcast app. I do it twice a week. I know 938 01:00:35,580 --> 01:00:41,610 agenda. I know pod verse has quite a share amongst Spurlock 939 01:00:41,610 --> 01:00:44,370 May, maybe he can run the numbers for me. I think no 940 01:00:44,370 --> 01:00:48,750 agenda shows a quite an impressive number for pod verse. 941 01:00:49,560 --> 01:00:53,580 Curio caster probably as well. And now I'm also promoting 942 01:00:55,350 --> 01:00:59,280 podcast addict, because they have delete feature. And that's 943 01:00:59,280 --> 01:01:03,120 a feature that we use. And we've actually without No, I mean, 944 01:01:03,120 --> 01:01:05,550 we've had, we've had all the pieces, we've had the chat room, 945 01:01:05,550 --> 01:01:08,130 we've had the stream, we had the batch signal. And the batch 946 01:01:08,130 --> 01:01:10,230 signal is just a Twitter thing that goes off and actually 947 01:01:10,230 --> 01:01:13,950 people had tied into it. And when I, when I send the so 948 01:01:13,950 --> 01:01:17,520 called bad signal, which is Twitter, and it has to come from 949 01:01:17,520 --> 01:01:20,880 my address, and it has some a tag in there like pocket, 950 01:01:21,090 --> 01:01:25,530 podcast pocket, some I can't remember what it is. It triggers 951 01:01:25,530 --> 01:01:28,410 all kinds of stuff like a Rube Goldberg machine, you know, 952 01:01:29,580 --> 01:01:32,670 recording, start, start, start. So people have backup 953 01:01:32,670 --> 01:01:34,950 recordings, if the stream goes down, there's all these things 954 01:01:34,950 --> 01:01:37,980 that have taken place through that one mechanism. And now it's 955 01:01:38,010 --> 01:01:43,140 all been brought together inside inside the app, which makes it 956 01:01:43,140 --> 01:01:46,650 so beautiful, along with and believe it or not, no agenda, 957 01:01:46,650 --> 01:01:49,980 we'll be accepting bitcoin payments, and we'll be accepting 958 01:01:49,980 --> 01:01:53,250 boosts and booster gram booster grams, hopefully, by the end of 959 01:01:53,250 --> 01:01:55,590 this month, you know, we're still waiting for Ibex to finish 960 01:01:55,590 --> 01:02:01,380 some stuff up. So that's promotion. You know, it's, and 961 01:02:01,380 --> 01:02:02,160 that works. 962 01:02:02,760 --> 01:02:07,950 There was a naysayer out call him that at pod fest. And I was 963 01:02:07,980 --> 01:02:11,460 explaining to him, he says, what's on these apps, and no one 964 01:02:11,460 --> 01:02:14,940 knows about it. I said, Listen, I said, look at this screen. I 965 01:02:14,940 --> 01:02:20,310 said, Have you ever on your own podcasts, gotten 20 comments on 966 01:02:20,310 --> 01:02:22,380 your show from the time you published the time you did the 967 01:02:22,380 --> 01:02:25,860 next episode and got and got some money along with that. And 968 01:02:25,860 --> 01:02:31,980 he looked at it. I said, that's probably from one half of 1% of 969 01:02:31,980 --> 01:02:36,120 my audience. That's Have you ever got that just to any other 970 01:02:36,120 --> 01:02:39,930 app or any other function, and he didn't really know what to 971 01:02:39,930 --> 01:02:43,530 say. So I think once the masses, like you said, Adam, you're 972 01:02:43,530 --> 01:02:47,850 getting people to move, this thing is going to explode out 973 01:02:47,850 --> 01:02:50,910 casters are going to be like, This is gonna be like crack. So 974 01:02:50,940 --> 01:02:54,720 no, go ahead. When you Yeah, when you when it comes to 975 01:02:55,080 --> 01:02:57,210 application development of it. This is this is across the 976 01:02:57,210 --> 01:03:00,330 board. It doesn't. And it's not just with podcast apps with any 977 01:03:00,330 --> 01:03:05,550 app that gives you a certain functionality. There's a for 978 01:03:05,550 --> 01:03:08,490 each person, but I think this is maybe especially true with 979 01:03:08,490 --> 01:03:13,200 podcast apps. For any person. For each gift for each a unique 980 01:03:13,200 --> 01:03:15,840 person, there's going to be a set of features that they 981 01:03:16,320 --> 01:03:20,820 themselves cared deeply about. So each and that's why you know, 982 01:03:20,820 --> 01:03:23,640 people sometimes they ask podcast apps are very personal. 983 01:03:23,970 --> 01:03:26,730 And I don't disagree with that. But there's it's really about 984 01:03:26,730 --> 01:03:29,160 okay, this app has this particular feature. And 985 01:03:29,160 --> 01:03:32,250 sometimes it's not even sometimes it's not even what you 986 01:03:32,250 --> 01:03:36,360 might consider a feature necessarily, sometimes they just 987 01:03:36,360 --> 01:03:40,740 like the way that this particular app is more feels 988 01:03:40,740 --> 01:03:43,980 more like a native iPhone app, then very, 989 01:03:43,980 --> 01:03:47,850 very personal choice want them I agree completely. 990 01:03:48,480 --> 01:03:53,010 And so all it takes if you have in that in that Paris, in that 991 01:03:53,010 --> 01:04:01,410 paradigm, all it really takes is one solid feature that a person 992 01:04:01,410 --> 01:04:05,250 can't live without. And then you've got to you've got as an 993 01:04:05,250 --> 01:04:08,940 app developer, you have a customer like that. And that 994 01:04:08,940 --> 01:04:14,520 could be and it already is, for me that could be live. Addicted 995 01:04:14,520 --> 01:04:18,390 to live stuff. Now the live item tag just is it's it's just has 996 01:04:18,390 --> 01:04:24,180 kind of made me starry eyed. I love it. Now, I need an app that 997 01:04:24,180 --> 01:04:28,320 gives me a lot that lets me tune in to podcast it gives me a push 998 01:04:28,320 --> 01:04:32,430 notification when the thing goes live. I can't not have that in 999 01:04:32,430 --> 01:04:33,660 my life. Now. You said 1000 01:04:33,660 --> 01:04:37,410 something very important there. Yeah, go. What you said was now 1001 01:04:37,410 --> 01:04:41,730 I have a customer. This I think is at the core whether we want 1002 01:04:41,730 --> 01:04:46,560 to admit it or not. At the core of what we're doing here is the 1003 01:04:46,560 --> 01:04:50,100 idea that you actually get a paying customer when you 1004 01:04:50,100 --> 01:04:56,820 implement at minimum value for value. So it to up your customer 1005 01:04:57,210 --> 01:05:00,060 either to grow your customer base. How about that, too? to 1006 01:05:00,060 --> 01:05:04,680 grow your customer base, you add a feature of live or lit, and 1007 01:05:04,680 --> 01:05:08,790 you automatically just by the nature of it receive more 1008 01:05:08,820 --> 01:05:15,030 Satoshis. You see, I'm saying, yeah, so you can measure what's 1009 01:05:15,030 --> 01:05:17,940 really what is really what features are really worth it to 1010 01:05:17,940 --> 01:05:21,360 you to build your as a hosting company or as an app developer, 1011 01:05:21,420 --> 01:05:24,780 your customer, your customer, to me is only your customer, when 1012 01:05:24,780 --> 01:05:26,790 they're paying you for something, they're paying you on 1013 01:05:26,790 --> 01:05:29,340 a monthly they're paying you through subscription, or 1014 01:05:29,340 --> 01:05:32,820 whatever it is. It doesn't have to be streaming sites, but 1015 01:05:32,820 --> 01:05:35,880 whatever it is, I think that should be the goal, because 1016 01:05:35,880 --> 01:05:38,160 that's what binds all of this together. 1017 01:05:39,149 --> 01:05:44,189 In that regard, it's like a, you can look at app, like app 1018 01:05:44,189 --> 01:05:49,169 breakdown percentage, for it feels like and you can back me 1019 01:05:49,169 --> 01:05:54,869 up on this or not Todd, it feels like that each hosting company 1020 01:05:54,869 --> 01:06:00,629 has sort of their own fingerprint within the listening 1021 01:06:00,629 --> 01:06:04,409 apps that tend to look didn't tend to be the biggest 1022 01:06:04,409 --> 01:06:08,009 downloaders of that hosting companies podcasts. Like I think 1023 01:06:08,249 --> 01:06:11,189 some have a heavy Spotify presence, some have a heavy 1024 01:06:11,189 --> 01:06:14,759 Apple presence, some have our heavy with overcast and like the 1025 01:06:14,759 --> 01:06:17,969 mix, it feels almost sort of like a fingerprint. And if you 1026 01:06:17,969 --> 01:06:21,719 think about it that way, you could almost say Oh, two, yeah, 1027 01:06:21,719 --> 01:06:26,909 per day, you could say that the the app breakdown, or the finger 1028 01:06:26,909 --> 01:06:30,689 app, the user agent, fingerprint for a certain hosting company 1029 01:06:30,689 --> 01:06:34,799 profile is sort of a referendum on what the hosting company's 1030 01:06:34,799 --> 01:06:38,789 priorities are. And if there's these new if the if you're 1031 01:06:38,789 --> 01:06:43,109 swinging heavy towards sort of indie apps, and, and heavier 1032 01:06:43,109 --> 01:06:47,159 with new podcast apps, and these these newer featured apps, you 1033 01:06:47,159 --> 01:06:50,519 can say, Well, I mean, that hosting companies clearly, you 1034 01:06:50,519 --> 01:06:53,309 know, a forward looking company and trying to further the 1035 01:06:53,489 --> 01:06:54,689 further podcasting. 1036 01:06:55,290 --> 01:06:59,010 You know, I think the when it comes to app break down, it gets 1037 01:06:59,040 --> 01:07:02,430 very lonely once you get below 1% global market share, because 1038 01:07:02,430 --> 01:07:05,880 no one else does not lonely, there's a lot of apps in there. 1039 01:07:05,880 --> 01:07:11,040 But really the Delta really is is in Spotify. For us, Spotify 1040 01:07:11,040 --> 01:07:13,860 never has gotten much more higher than 8%. Globally, for 1041 01:07:13,860 --> 01:07:16,710 all the shows measure then, but Buzzsprout, they're pretty high. 1042 01:07:16,710 --> 01:07:21,030 They're like 1820. And I think a lot of that has to do number one 1043 01:07:21,030 --> 01:07:23,910 is really the audience that uses Buzzsprout, maybe a little 1044 01:07:23,910 --> 01:07:28,410 younger, have a little different show show type. You know, we 1045 01:07:28,410 --> 01:07:30,540 have a lot of folks that are on WordPress, they're established 1046 01:07:30,540 --> 01:07:34,440 businesses. So maybe they're not more as of tractive. To a 1047 01:07:34,440 --> 01:07:37,110 listener on Spotify as a show this may be got someone that's 1048 01:07:37,110 --> 01:07:41,400 22 doing a podcast, but I think in the end, that's really the 1049 01:07:41,400 --> 01:07:45,000 only true delta we see. Because everything else stays pretty 1050 01:07:45,000 --> 01:07:49,140 steady. You know, Mark, overcast pocket, podcast, attic, all 1051 01:07:49,140 --> 01:07:52,140 those numbers stay pretty close across almost all shows. Here's 1052 01:07:52,140 --> 01:07:57,630 the thing though. Spotify gets exactly zero Satoshis, 00, 1053 01:07:57,630 --> 01:08:01,590 Satoshis. From from all shows they have. Thank God. So 1054 01:08:02,190 --> 01:08:06,510 everyone does, everyone does have a way. Everyone does have a 1055 01:08:06,510 --> 01:08:10,350 way to measure their own market share. That's right, based upon 1056 01:08:10,350 --> 01:08:17,970 that. And it's curious. There's always been this camaraderie 1057 01:08:17,970 --> 01:08:23,370 amongst hosting companies in the podcast in the podcast space. 1058 01:08:24,150 --> 01:08:27,810 And I've never understand, I was gonna say, never understand what 1059 01:08:27,810 --> 01:08:29,910 you guys just don't undercut each other and why you aren't 1060 01:08:29,910 --> 01:08:33,510 just super competitive? Or maybe you are and maybe it's all just 1061 01:08:33,510 --> 01:08:37,410 kind of a front. And people talk about everybody behind their 1062 01:08:37,410 --> 01:08:39,810 back. I mean, there may be some of that going on. It's just 1063 01:08:39,810 --> 01:08:43,470 always interesting to me. And maybe I'm moving towards the 1064 01:08:43,470 --> 01:08:46,950 question of why the heck are you still trying to get some kind of 1065 01:08:46,950 --> 01:08:49,650 group together some kind of commie group, like, we're all 1066 01:08:49,650 --> 01:08:52,590 going to Kumbaya and we're all going to promote 2.0 which will 1067 01:08:52,590 --> 01:08:55,740 never happen, because it always fails. 1068 01:08:56,219 --> 01:09:00,089 And you know, even getting 10 people to agree to the same 1069 01:09:00,089 --> 01:09:03,509 thing is difficult getting 30 is almost impossible. So we'll see. 1070 01:09:04,529 --> 01:09:08,819 But I think the ultimately what the goal was and trying to form 1071 01:09:08,849 --> 01:09:12,359 this new group is basically to have a coalition or whatever you 1072 01:09:12,359 --> 01:09:15,179 want to call it to basically promote podcasting. 2.0 But 1073 01:09:15,179 --> 01:09:18,599 we've been trying to get organized for six, eight months, 1074 01:09:18,629 --> 01:09:22,169 and yeah, it's not going so good. It's going slow. So so 1075 01:09:22,229 --> 01:09:24,239 we're gonna continue to do what we have to do to promote 1076 01:09:24,239 --> 01:09:26,249 regardless of a group organization. 1077 01:09:26,280 --> 01:09:31,110 So John Spurlock just thank you. I Spurlock if ever heard of a 1078 01:09:31,110 --> 01:09:35,730 boosted grant man you're doing that's just because alright 1079 01:09:35,730 --> 01:09:38,070 because I'm taking you're giving me information but you should be 1080 01:09:38,070 --> 01:09:42,540 boosting booster grabbing this info for no agenda in January 1081 01:09:42,570 --> 01:09:48,600 2023 31 points 37% Apple podcast then we have unknown Apple app 1082 01:09:48,600 --> 01:09:52,050 which is you know that the ongoing core media whatever who 1083 01:09:52,050 --> 01:09:57,390 knows what it is? Probably just from a website 26% pod verse 1084 01:09:57,420 --> 01:10:02,340 eight point 11 podcast attic six point Five Pocket Casts that 1085 01:10:02,340 --> 01:10:10,530 will who I think 00 2.0 or 2.0 features four and a half 1086 01:10:10,560 --> 01:10:16,260 overcast for 21. And then we go Google Stitcher, fountain 1.4, 1087 01:10:16,260 --> 01:10:21,150 which is low. I'm surprised how low fountain is but you know, on 1088 01:10:21,150 --> 01:10:24,990 this list at least, charismatic is on there as well. But now 1089 01:10:24,990 --> 01:10:28,110 that what this doesn't represent is the amount of Satoshis 1090 01:10:28,110 --> 01:10:31,440 because it's right, the number one center of Satoshis is 1091 01:10:31,440 --> 01:10:35,430 fountain number two, it's a toss up but it's usually pod verse. 1092 01:10:35,940 --> 01:10:39,180 And then so the top the top three would be fountain pod 1093 01:10:39,180 --> 01:10:44,790 verse, curio caster cast, thematic, for, for me for for no 1094 01:10:44,790 --> 01:10:51,690 agenda. This is serious. I mean, even 8.5% of the 850,000 people 1095 01:10:51,690 --> 01:10:55,350 that listened to no agenda every episode. So you know, the 1096 01:10:55,350 --> 01:10:57,930 universe is bigger, I guess. But every episode, that's what 1097 01:10:57,930 --> 01:11:00,480 you're kind of looking at. That's not bad. 1098 01:11:01,049 --> 01:11:03,509 It's not bad. And I think we're in a chicken and egg situation 1099 01:11:03,509 --> 01:11:06,539 there, too. Let's say we get up to 50,000 shows that are valid 1100 01:11:06,539 --> 01:11:10,169 for value enabled. And then these apps are going all of a 1101 01:11:10,169 --> 01:11:12,599 sudden starting to see that they're leaving money on the 1102 01:11:12,599 --> 01:11:15,959 table. And this is what I love about this piece of it is 1103 01:11:16,169 --> 01:11:19,589 sustainability for app developers, if we can, you know, 1104 01:11:19,589 --> 01:11:23,969 I care about the app developers as much as I care about the our 1105 01:11:23,969 --> 01:11:26,099 hosting customers, because we want to make sure that 1106 01:11:26,099 --> 01:11:28,199 developers are fed can eat. 1107 01:11:29,640 --> 01:11:33,600 Yes, another minor thing that has been added to this whole 1108 01:11:33,600 --> 01:11:37,290 game? That's right, you're in the money flow. You're you're 1109 01:11:37,290 --> 01:11:40,560 still not getting anything from the ad insertions, right? Not 1110 01:11:40,560 --> 01:11:43,980 getting anything from the host reads? No, would you please go? 1111 01:11:44,460 --> 01:11:48,330 Go beg people to send you 99 cents. 1112 01:11:49,170 --> 01:11:54,030 And with all these independent apps, that keeps a lot of this, 1113 01:11:54,060 --> 01:11:59,070 you know, I would hate to see podcasting only be available in 1114 01:11:59,100 --> 01:12:01,980 two big apps because nobody else can make any money. 1115 01:12:02,010 --> 01:12:06,360 Right on. Yeah, we don't want to happen to podcasting. What 1116 01:12:06,360 --> 01:12:10,500 happened to the open web where you've basically got, you know, 1117 01:12:10,500 --> 01:12:14,250 everything's come down to Safari and Chrome. I mean, we you know, 1118 01:12:14,250 --> 01:12:17,670 that's there's no diversity within the browser ecosystem 1119 01:12:17,670 --> 01:12:21,180 anymore. There's everything's just all running on the same 1120 01:12:21,240 --> 01:12:24,180 rescanned engines. I mean, we really don't want that mean, 1121 01:12:24,180 --> 01:12:28,230 podcasting is probably I think podcasting almost stands alone 1122 01:12:28,230 --> 01:12:33,630 now. Maybe second only to something like Mastodon as far 1123 01:12:33,630 --> 01:12:36,420 as or something like that, or it was as far as just distributed. 1124 01:12:36,780 --> 01:12:39,570 Where, where the where the listeners and the consumers of 1125 01:12:39,570 --> 01:12:44,460 the content use, like dozens and dozens of different have 1126 01:12:44,460 --> 01:12:47,700 completely different apps to access the same content. That's 1127 01:12:47,700 --> 01:12:50,640 something you don't want to give up. Because it's, it's 1128 01:12:50,640 --> 01:12:52,770 beautiful. And we have and it's helpful 1129 01:12:52,800 --> 01:12:57,510 and and the features that are new are specific incentives for 1130 01:12:57,720 --> 01:13:00,540 not every podcast is the same, you know, some podcast 1131 01:13:00,540 --> 01:13:03,840 transcripts are very important, I put a high value on 1132 01:13:03,840 --> 01:13:07,170 transcripts, mainly for just finding something in the show. 1133 01:13:08,460 --> 01:13:12,570 To prove Dvorak wrong. But But other people use it for 1134 01:13:12,570 --> 01:13:16,050 different reasons, Chapter chapters, was chapter images, or 1135 01:13:16,050 --> 01:13:20,100 high value to no agenda. That's where we put a lot of the art 1136 01:13:20,100 --> 01:13:22,650 that is not used as the album art, we can still put that in 1137 01:13:22,650 --> 01:13:28,080 there and make use of it. So these, these are all reasons 1138 01:13:28,350 --> 01:13:33,690 for, for a podcast or to ask their listeners to try a new 1139 01:13:33,690 --> 01:13:37,230 podcast app. And I think with that should also go the hey, you 1140 01:13:37,230 --> 01:13:39,960 know, you could if you if there's something you you'd like 1141 01:13:39,960 --> 01:13:43,500 to see change, here's how you can contact the developer. If 1142 01:13:43,500 --> 01:13:45,690 there's something that you're missing from that fabulous 1143 01:13:45,690 --> 01:13:51,930 Spotify experience, then contact your developer and in this case, 1144 01:13:52,050 --> 01:13:56,370 with podcasting, I disagree. I fundamentally disagree with the 1145 01:13:56,370 --> 01:14:01,290 radio mindset of wherever the listener is I want to be No, 1146 01:14:01,710 --> 01:14:06,270 that's it has very low value. Value, because we know 1147 01:14:06,270 --> 01:14:10,320 advertising is just not going to pay off for 99% of anyone who's 1148 01:14:10,320 --> 01:14:14,340 trying it. It's low value, what you want is your community, you 1149 01:14:14,340 --> 01:14:17,760 want to know where you want to have your community there, where 1150 01:14:17,760 --> 01:14:20,430 the features that your community is using and where you can 1151 01:14:20,430 --> 01:14:25,200 actually have a value exchange. That is Go ahead. 1152 01:14:26,700 --> 01:14:30,840 But here's an interesting development on our site, is we 1153 01:14:30,840 --> 01:14:34,110 built our platform to add all these features to make it 1154 01:14:34,170 --> 01:14:37,800 enhance the idea that someone might want to move to us because 1155 01:14:37,800 --> 01:14:40,110 when someone signs up for hosting business hosting 1156 01:14:40,110 --> 01:14:43,560 service, they go to Lipson pod, bean pod, and wherever they go 1157 01:14:43,560 --> 01:14:46,890 host they usually there for life. There's very few people 1158 01:14:46,890 --> 01:14:49,650 that actually move their shows and you have to have huge 1159 01:14:49,650 --> 01:14:52,710 incentives for a podcaster decide to move to another 1160 01:14:52,710 --> 01:14:53,250 platform. 1161 01:14:53,280 --> 01:14:55,860 I got an email from a cast. I thought it was a good idea. 1162 01:14:56,520 --> 01:14:57,150 Yeah, well 1163 01:14:57,179 --> 01:15:00,359 guess what you went for two weeks. Back we saw All night all 1164 01:15:00,359 --> 01:15:04,289 the time. So do that all the time. So now what we're starting 1165 01:15:04,289 --> 01:15:08,549 to see is all of a sudden, hey, wow, look what you guys are 1166 01:15:08,549 --> 01:15:13,529 doing. We're gonna move. So I put a challenge out there. For 1167 01:15:13,559 --> 01:15:16,139 every hosting companies, every, everyone's listening to the 1168 01:15:16,139 --> 01:15:19,049 show. If they're not, then they're an idiot. But all these 1169 01:15:19,049 --> 01:15:22,349 hosting companies that are not doing anything, I'm gonna start 1170 01:15:22,349 --> 01:15:30,239 stealing your customers. So hey, I have an agenda, I run a 1171 01:15:30,239 --> 01:15:34,169 business, I have employees to take care of my agenda is to 1172 01:15:34,169 --> 01:15:37,679 build build my business. But we at the same time, I'm a 1173 01:15:37,679 --> 01:15:39,839 podcaster, at heart, and I understand the value of this. 1174 01:15:39,839 --> 01:15:42,689 And I think there's a lot of podcasting companies that are 1175 01:15:42,689 --> 01:15:46,529 run by individuals that have never picked up a microphone. 1176 01:15:46,889 --> 01:15:48,539 And I think that's a fundamental problem. 1177 01:15:48,900 --> 01:15:50,010 Get to course. 1178 01:15:51,180 --> 01:16:00,330 Yeah, I agree with that. 100%. Okay, so when we You said 1179 01:16:00,360 --> 01:16:05,370 something that I want to ask you about? You said that your the 1180 01:16:05,370 --> 01:16:08,280 people you talk to are not really even talking about 1181 01:16:08,970 --> 01:16:11,430 growing their show anymore? Or excuse me, they're not talking 1182 01:16:11,430 --> 01:16:13,830 about monetization, they're only talking about growing their 1183 01:16:13,830 --> 01:16:17,100 show? What, what is the disconnect there? Because 1184 01:16:17,100 --> 01:16:21,030 usually one, you would think that one entails the other. But 1185 01:16:21,030 --> 01:16:23,220 it's interesting that they're, that they're concerned about, 1186 01:16:23,400 --> 01:16:26,520 that they want to grow, but they don't really are not focused on 1187 01:16:26,520 --> 01:16:29,940 monetizing is that the reason I'm asking this for a reason, 1188 01:16:29,940 --> 01:16:36,240 because I feel like it that that strikes a chord with me because 1189 01:16:36,240 --> 01:16:40,080 I really don't care. It feels good to have a big audience, 1190 01:16:40,230 --> 01:16:42,840 whether you want money from it or not. You think that's what's 1191 01:16:42,840 --> 01:16:43,290 going on? 1192 01:16:43,380 --> 01:16:47,310 Well, what it is, is they want to grow, to have a big audience, 1193 01:16:47,430 --> 01:16:50,520 then to be able to monetize, if they don't grow to a big 1194 01:16:50,520 --> 01:16:52,980 audience, they're not going to significantly monetize and the 1195 01:16:52,980 --> 01:16:57,360 traditional methods that we've been using for the past 18 1196 01:16:57,360 --> 01:16:58,110 years, can you 1197 01:16:58,110 --> 01:16:59,370 definitely connected? 1198 01:16:59,940 --> 01:17:03,000 Can you can you really break it down? Todd, I mean, I've never 1199 01:17:03,000 --> 01:17:06,630 done the advertising game and podcasting. Let's just forget 1200 01:17:06,630 --> 01:17:11,280 host reads just programmatic. If you I think the number of these 1201 01:17:11,280 --> 01:17:14,280 days is well 10,000. If you have 10,000, you can start to 1202 01:17:14,280 --> 01:17:18,960 monetize, what can someone seriously consider making on a 1203 01:17:18,960 --> 01:17:23,430 monthly basis with 10,000 downloads in a whole month. 1204 01:17:24,210 --> 01:17:27,330 If they're doing a straight deal, nothing special, probably 1205 01:17:27,330 --> 01:17:32,190 about 250 bucks, or 25 on per 1000. That's pretty average for 1206 01:17:32,190 --> 01:17:35,340 host read. For programmatic role. It's a whole big different 1207 01:17:35,340 --> 01:17:38,520 number changes by the second longer you're on programmatic at 1208 01:17:38,520 --> 01:17:41,370 least on our system, the higher the CPMs get. But if you're just 1209 01:17:41,370 --> 01:17:45,120 starting out first month or so, you're probably seen six to $9 1210 01:17:45,120 --> 01:17:50,280 CPM, maybe as high as 11. We haven't seen much above $11 per 1211 01:17:50,280 --> 01:17:56,340 1000. On programmatic. So you know, on 10,000 for programmatic 1212 01:17:56,340 --> 01:18:01,470 maybe 60 to $100 or more before split before admission split. 1213 01:18:01,740 --> 01:18:05,250 Are you in your educational materials? Are you showing 1214 01:18:05,250 --> 01:18:12,540 people how to view streaming set statistics either through Saturn 1215 01:18:12,540 --> 01:18:14,970 on Git Alby or one of these other systems? Are you going to 1216 01:18:14,970 --> 01:18:16,920 surface that in your interface itself? 1217 01:18:17,370 --> 01:18:20,880 And not yet, we're not showing that in documentation yet. But 1218 01:18:20,910 --> 01:18:23,820 it's, again, it's a work in progress. I just be honest with 1219 01:18:23,820 --> 01:18:26,520 you. My development team is like, I'm having a hard time 1220 01:18:26,520 --> 01:18:28,620 keeping up with documentation. They're just not going out of 1221 01:18:28,620 --> 01:18:30,840 the ballpark. So we're running behind the ever written 1222 01:18:31,140 --> 01:18:31,740 paperwork. 1223 01:18:31,860 --> 01:18:35,070 I'm just saying because that for for, you know, the entire 1224 01:18:35,340 --> 01:18:39,540 existence of hosting companies, the number one feature was we've 1225 01:18:39,540 --> 01:18:43,380 got great stats, you can see all the look at these countries. 1226 01:18:43,590 --> 01:18:47,760 Look at the women look at the men look at the age groups. Now. 1227 01:18:47,790 --> 01:18:52,230 That's and look at the map. That's been the main driver, and 1228 01:18:52,230 --> 01:18:56,910 it's showing when PeepSo I help launch, living up in a down 1229 01:18:56,910 --> 01:19:01,830 world, it's a it's a half hour a week. It's a pastor here with 1230 01:19:01,830 --> 01:19:06,330 his wife in Fredericksburg. So not even your typical Wow, this 1231 01:19:06,330 --> 01:19:11,160 is going to be a top of the apple podcast front page 1232 01:19:11,160 --> 01:19:17,790 listing. But they a meet so two things happen. One, I showed him 1233 01:19:17,820 --> 01:19:22,200 because he he went with rss.com. And so they're they have a 1234 01:19:22,200 --> 01:19:24,450 partnership with Albie as well. And so I said, Hey, you know, 1235 01:19:24,450 --> 01:19:27,630 here's your, here's your Saturn interface, you can see stuff 1236 01:19:27,630 --> 01:19:31,920 coming in live. And you can look at how much you got per episode 1237 01:19:31,920 --> 01:19:35,520 and just, you know, a couple of ways to slice and dice it. And 1238 01:19:35,520 --> 01:19:40,680 then all of a sudden, the ad, he shows up in the top 10 on the 1239 01:19:40,680 --> 01:19:45,240 fountain weekly list. And the activity stream is showing 1240 01:19:45,240 --> 01:19:48,360 people interacting and now he's like, Oh, but we have a 1241 01:19:48,360 --> 01:19:53,970 community over here. And that for Episode Four has been a 1242 01:19:53,970 --> 01:19:57,660 beautiful thing to witness because he now he knows that 1243 01:19:57,660 --> 01:20:00,900 they're not just talking in space and Coming back, as you 1244 01:20:00,900 --> 01:20:05,340 know, an email here or there, or kudos on Facebook, but actual 1245 01:20:05,340 --> 01:20:09,270 statistics that he can now for himself measure get Okay, how 1246 01:20:09,270 --> 01:20:12,210 did we do? What's the engagement? All these things 1247 01:20:12,210 --> 01:20:15,720 come to life with with that actually a very small show. 1248 01:20:16,110 --> 01:20:19,680 And it's more valuable than money. It's that engagement. 1249 01:20:19,710 --> 01:20:24,390 Amen. Yes, it is. Because oftentimes podcasts are feel 1250 01:20:24,390 --> 01:20:27,300 like they're talking into space. And the audience are listening 1251 01:20:27,300 --> 01:20:29,370 on their app, and there's no way interact with them. You know, 1252 01:20:29,370 --> 01:20:32,550 maybe they send you an email if you're lucky. And you can get 1253 01:20:32,550 --> 01:20:34,740 pretty lonely as a content creator. Yeah, you shouldn't 1254 01:20:34,740 --> 01:20:36,270 try doing a show with the Borak 1255 01:20:37,440 --> 01:20:40,530 boost booster, booster grams, and you know, get having it read 1256 01:20:40,530 --> 01:20:43,050 on the show. I mean, as a listener, that's fun. So 1257 01:20:44,880 --> 01:20:47,430 one of the reasons I started doing live when so many years 1258 01:20:47,430 --> 01:20:51,540 ago is because I was in Hawaii, and it was boring, doing a solo 1259 01:20:51,540 --> 01:20:53,760 show, and I just would start doing live because I wanted the 1260 01:20:53,760 --> 01:20:57,330 interaction. This has taken interaction to just like, more 1261 01:20:57,330 --> 01:21:00,090 or less new media show he talked about in the beginning, took the 1262 01:21:00,090 --> 01:21:03,750 whole show to a whole nother level. I had, I probably had the 1263 01:21:03,750 --> 01:21:07,860 most fun that I've had on a podcast episode in years. It was 1264 01:21:07,860 --> 01:21:08,280 a good time. 1265 01:21:08,490 --> 01:21:11,850 What did you What did you make on the last episode? I think I 1266 01:21:11,850 --> 01:21:14,070 must have sent 100 bucks to you and saps. 1267 01:21:14,160 --> 01:21:18,090 Oh, he sent me two or 300,000 SATs at least. So I don't know 1268 01:21:18,090 --> 01:21:20,370 what the number was. It was quite a bit. It was it was big. 1269 01:21:20,400 --> 01:21:23,580 But it was still you know, it wasn't even about I had the 1270 01:21:23,580 --> 01:21:24,000 money. 1271 01:21:24,030 --> 01:21:27,420 No, but the fun. I had fun sending sending you my cash. It 1272 01:21:27,420 --> 01:21:28,740 was great. I loved it. 1273 01:21:29,370 --> 01:21:32,700 Yeah, again, it was about the interaction. You know, that was 1274 01:21:32,700 --> 01:21:33,510 a big driver. 1275 01:21:33,900 --> 01:21:37,890 So you we talked about live item tag at the beginning. And then 1276 01:21:38,400 --> 01:21:41,760 you know, and same thing with with avviso. With value for 1277 01:21:41,760 --> 01:21:47,940 value. Some of these tags are features that are that are more 1278 01:21:47,940 --> 01:21:51,660 complicated. How, what is your what's your strategy been for 1279 01:21:51,660 --> 01:21:54,540 the UI? Because I know that's always the most difficult part 1280 01:21:54,540 --> 01:21:58,680 is like how, okay, we've got this thing we want to do. How do 1281 01:21:58,680 --> 01:22:01,200 we do this in a way that doesn't confuse the hell out of our 1282 01:22:01,200 --> 01:22:05,820 customers. And but still make it like keep the fidelity to what 1283 01:22:05,820 --> 01:22:07,890 the feature is supposed to be heavy? Do you have like an 1284 01:22:07,890 --> 01:22:10,830 overall kind of game plan or strategy that y'all tried to hit 1285 01:22:11,250 --> 01:22:14,610 me and blueberry dashboard, we did the full integration with lb 1286 01:22:14,610 --> 01:22:18,270 API. So basically, it's a one click, they put their rate their 1287 01:22:18,270 --> 01:22:21,540 account, and bam, the data comes back to us. But because 1288 01:22:21,540 --> 01:22:24,540 PowerPress is hosted on, you know, 80,000 different websites, 1289 01:22:24,540 --> 01:22:27,510 we couldn't do the API. So we did the lookup. So they put 1290 01:22:27,510 --> 01:22:30,060 their we said go over and get in, I'll be account, put your IP 1291 01:22:30,060 --> 01:22:33,420 address in here, click this button, and we suck the data. 1292 01:22:33,420 --> 01:22:37,980 And we did that for fountain as well. And the ability to enter 1293 01:22:37,980 --> 01:22:41,550 the data manually is the last option. So really, it was about 1294 01:22:41,580 --> 01:22:44,940 ease of getting them set up. But it was you know, literally, I 1295 01:22:44,940 --> 01:22:49,830 think, as we're testing, you could really probably get your 1296 01:22:49,830 --> 01:22:53,190 value from value set up in less than a minute. Just through the 1297 01:22:53,190 --> 01:22:54,630 API integration with lb, 1298 01:22:55,080 --> 01:22:58,680 I just set up podcast insider with without being I mean, it 1299 01:22:58,680 --> 01:23:05,040 was like, no time flat, was there and looked over on index, 1300 01:23:05,040 --> 01:23:07,500 and it was there after I figured out what I was doing. 1301 01:23:09,900 --> 01:23:14,280 I'm seeing you know, I'm starting to see these feeds come 1302 01:23:14,280 --> 01:23:17,370 in. Luckily, there was one that just came in a little bit 1303 01:23:17,370 --> 01:23:23,850 earlier. And it was, yeah, on power press. So it's fun, it's 1304 01:23:23,850 --> 01:23:26,370 always interesting, this the same thing that happened when 1305 01:23:27,090 --> 01:23:32,130 when y'all put in pod ping all of a sudden, it's like the it 1306 01:23:32,130 --> 01:23:34,530 just wakes up, you know, it's like part of the index just 1307 01:23:34,530 --> 01:23:37,530 wakes up. And all of a sudden we start seeing this traffic come 1308 01:23:37,530 --> 01:23:42,420 in. And then you'll you'll see value value blocks and podcast 1309 01:23:42,450 --> 01:23:45,540 updates coming where you know, we know we're getting the 1310 01:23:45,540 --> 01:23:49,800 latest, the latest episode data immediately within, you know, 1311 01:23:49,800 --> 01:23:53,250 within a minute, it's like, it's a beautiful thing to see because 1312 01:23:53,250 --> 01:23:55,860 you put all this work in the building Billina like 1313 01:23:55,860 --> 01:23:57,960 infrastructure stuff and infrastructure stuff, a lot of 1314 01:23:57,960 --> 01:24:02,340 times it's boring. But then when you see like when y'all when 1315 01:24:02,340 --> 01:24:05,610 y'all put in a new feature, any host puts in a new feature like 1316 01:24:05,610 --> 01:24:08,160 this, it's like all of a sudden part of the index just comes 1317 01:24:08,160 --> 01:24:11,070 alive and you can start to see this traffic, it really brings 1318 01:24:11,070 --> 01:24:12,600 life to it. I've had to 1319 01:24:12,600 --> 01:24:16,410 make it simple because lot of these podcasters now don't know 1320 01:24:16,410 --> 01:24:20,220 how to right click a mouse. So we had to make it like, really 1321 01:24:20,220 --> 01:24:22,530 make it simple as much and I don't and I don't say that 1322 01:24:22,530 --> 01:24:27,450 lightly, because a lot of podcasters now, they are focused 1323 01:24:27,450 --> 01:24:30,690 on creating content. They're not techie. So we have to make this 1324 01:24:30,690 --> 01:24:33,690 non technical. You have to make them understand, hey, just click 1325 01:24:33,690 --> 01:24:36,660 here to get signed up. And then give them the education how to 1326 01:24:36,720 --> 01:24:37,410 how to move forward. 1327 01:24:37,710 --> 01:24:40,620 When we started. We were all geeks and everybody that 1328 01:24:40,620 --> 01:24:46,530 listened was a geek. Yeah. Now, literally weekly basis. I'm 1329 01:24:46,560 --> 01:24:50,820 teaching people how to cut and paste. I mean, it's that, you 1330 01:24:50,820 --> 01:24:56,070 know, that when we have a tech bar, they're there. They can 1331 01:24:56,070 --> 01:24:59,190 still do podcasting. They just need a little push and 1332 01:24:59,220 --> 01:24:59,970 interesting work. 1333 01:25:00,000 --> 01:25:03,690 Interesting story. A Tina is in Chicago right now visiting. 1334 01:25:04,800 --> 01:25:09,180 She's visiting her family, but we're in Indiana. But she's in 1335 01:25:09,180 --> 01:25:13,260 Chicago because they actually are doing a meet up a keeper 1336 01:25:13,260 --> 01:25:18,630 meet up, notice how the curry has been dropped the keeper 1337 01:25:18,630 --> 01:25:26,220 meetup. And, and so Kate who was organizing her husband, I think, 1338 01:25:26,220 --> 01:25:29,850 as a listener to no agenda from day one. But if I understand the 1339 01:25:29,850 --> 01:25:33,960 story, he was working at Apple at the Apple Store, and people 1340 01:25:33,960 --> 01:25:37,800 would come in, and they would have trouble setting stuff up. 1341 01:25:37,800 --> 01:25:41,040 And so he would allow the employee, the Apple employees 1342 01:25:41,160 --> 01:25:43,920 after work to go and help the older people to go and help them 1343 01:25:43,920 --> 01:25:47,940 set something up at home. And that was a show against Apple 1344 01:25:47,940 --> 01:25:51,210 policy that he actually had to let these people go because they 1345 01:25:51,210 --> 01:25:55,170 were doing that. And then he quit himself. And he started a 1346 01:25:55,170 --> 01:26:01,440 service of people going to your house to help you simply set up 1347 01:26:01,440 --> 01:26:04,860 the Zoom call or something like that. But if you think old 1348 01:26:04,860 --> 01:26:07,890 people equals poor people, you got something else coming. Oh, 1349 01:26:07,890 --> 01:26:12,060 that's true. He's he is making money. And he is making bank on 1350 01:26:12,060 --> 01:26:15,690 this bank. And he has, you know, I don't know how many employees 1351 01:26:15,690 --> 01:26:19,230 gone to people and everyone's making good money doing this. So 1352 01:26:19,230 --> 01:26:22,590 they can also serve, you know, the people who don't have a lot 1353 01:26:22,590 --> 01:26:27,390 of money. It's really beautiful to see. So you know, yes, yes, 1354 01:26:27,390 --> 01:26:31,440 holding people's hands does it, it pays off. The other British 1355 01:26:31,860 --> 01:26:35,130 support team are always you know, doing some hand holding 1356 01:26:35,130 --> 01:26:38,700 and, and it works out, you know, usually the first week or two 1357 01:26:38,700 --> 01:26:41,790 there's a lot of questions and then they disappear. And they're 1358 01:26:41,790 --> 01:26:42,750 podcasters. 1359 01:26:44,280 --> 01:26:48,300 Exactly as we wouldn't have a customer one if Mike wasn't lead 1360 01:26:48,300 --> 01:26:51,480 my support team and as I would, I would probably not be a good 1361 01:26:51,480 --> 01:26:53,430 customer service. Rep. I haven't. 1362 01:27:01,830 --> 01:27:06,480 Ding, ding ding on time. Where I didn't hit the button, right. 1363 01:27:09,120 --> 01:27:11,640 We've all been there, Mike. We've all been there. 1364 01:27:12,000 --> 01:27:14,310 Hey, who's pod surf.fm? 1365 01:27:16,530 --> 01:27:18,960 Or heard of it? Pods are? Yeah, 1366 01:27:18,990 --> 01:27:21,420 there is they're hitting pod ping. Pretty good pretty hard 1367 01:27:21,420 --> 01:27:26,190 with updates. Let's surf done interesting. Almost on why this 1368 01:27:26,190 --> 01:27:29,760 pod Pink Dot Watch is where you can go and see new feeds being 1369 01:27:29,760 --> 01:27:33,150 submitted that run through pod paying and save the Earth at the 1370 01:27:33,150 --> 01:27:37,710 same time by not using computer resources wastefully. 1371 01:27:38,250 --> 01:27:41,070 While we both were boiling the oceans with Bitcoin and saving 1372 01:27:41,070 --> 01:27:43,080 it. We balance 1373 01:27:43,710 --> 01:27:47,250 our carbon credits are equalized is good. Good deals a good deal. 1374 01:27:47,280 --> 01:27:47,640 Yeah, 1375 01:27:47,730 --> 01:27:49,260 I demand respect for this. So whoever 1376 01:27:49,260 --> 01:27:53,610 pod serve is Welcome to the party. They're pushing some 1377 01:27:53,610 --> 01:27:54,240 updates. 1378 01:27:56,760 --> 01:27:57,600 Go ahead and go ahead. 1379 01:27:58,320 --> 01:28:01,170 I've seen a lot of stuff that's been coming this coming because 1380 01:28:01,170 --> 01:28:03,240 you know people have got some projects they're working on so I 1381 01:28:03,240 --> 01:28:06,660 think we're you're gonna have a good podcasting 2.0 year because 1382 01:28:06,660 --> 01:28:08,730 there's a lot of people are building product right now. 1383 01:28:09,240 --> 01:28:13,020 Well, you're not getting you're not the official promotion King. 1384 01:28:14,670 --> 01:28:17,670 Do my best, you know, to be honest with you, Adam, I made a 1385 01:28:17,670 --> 01:28:21,090 commitment this year, whenever I was going to, you know that I 1386 01:28:21,090 --> 01:28:23,790 take a topic every year and talk about it for the whole year. So 1387 01:28:23,790 --> 01:28:26,430 this year, if I applied to speak somewhere, it's going to be 1388 01:28:26,430 --> 01:28:30,720 podcasting 2.0 all year. So that if I go somewhere that's going 1389 01:28:30,720 --> 01:28:33,420 to be the topic that we're we're going to cover if they don't if 1390 01:28:33,420 --> 01:28:34,200 they want me to speak 1391 01:28:35,130 --> 01:28:40,170 they love I think the I think the we may be starting to see 1392 01:28:40,170 --> 01:28:44,790 some real a real shift or real turning the corner on so on the 1393 01:28:44,790 --> 01:28:46,920 social interact on cross app comments. 1394 01:28:46,950 --> 01:28:49,710 Oh, stop threatening me. No, no, this 1395 01:28:49,710 --> 01:28:51,420 is for reals. For reals 1396 01:28:51,930 --> 01:28:53,820 at the top of our list. Yep. 1397 01:28:53,850 --> 01:29:02,130 Well, the because gamma in Nathan gay thrive and assisted 1398 01:29:02,130 --> 01:29:06,750 by John Spurlock are really working to put cross out 1399 01:29:06,750 --> 01:29:11,280 comments to surface them on the pod on our website, podcast. 1400 01:29:11,280 --> 01:29:15,000 index.org. I love that as a bootstrap. Yeah. And I think 1401 01:29:15,480 --> 01:29:19,230 like, that's, that's how podcasts distribute. That's how 1402 01:29:19,230 --> 01:29:23,610 cross app comments is going to evolve, is is going to evolve by 1403 01:29:23,610 --> 01:29:28,800 people. But by slow momentum of things beginning to pop up in 1404 01:29:28,800 --> 01:29:32,550 various places. It's got to be surfaced in order for people to 1405 01:29:32,550 --> 01:29:36,000 know that it's a thing and to know what's there. But I really 1406 01:29:36,000 --> 01:29:40,770 love this idea of putting it on on the web, because that's kind 1407 01:29:40,770 --> 01:29:45,360 of like the wheat. We get a lot of web traffic. I mean, you know 1408 01:29:45,360 --> 01:29:49,140 people go and they search you know, hat is may podcasters go 1409 01:29:49,140 --> 01:29:51,570 and they want to search the AES my podcast in this in this 1410 01:29:51,570 --> 01:29:54,060 directory is it in this directory people people like to 1411 01:29:54,060 --> 01:29:57,870 do searches for themselves? You know, and we are I don't know 1412 01:29:57,870 --> 01:30:00,540 how many I don't know how much traffic we Because I haven't 1413 01:30:00,540 --> 01:30:02,850 looked at stats in a long time, but we actually get a pretty 1414 01:30:02,850 --> 01:30:07,020 substantial amount of just raw web traffic to our website. And 1415 01:30:07,020 --> 01:30:11,070 I think that will, that could be a big deal to have that show 1416 01:30:11,070 --> 01:30:12,810 that stuff show up. And then we'd send 1417 01:30:12,810 --> 01:30:16,080 people over there all the time. Yeah, since we've implemented 1418 01:30:16,080 --> 01:30:20,280 pod ping, there's no onboarding for you guys. I just tell them 1419 01:30:20,280 --> 01:30:23,280 to go over search for their show, grab the link, they can 1420 01:30:23,340 --> 01:30:27,270 throw that wherever they want. And so I'm sending lots of 1421 01:30:27,270 --> 01:30:27,780 people there. 1422 01:30:28,620 --> 01:30:30,900 Yep, yep. And that, I mean, I think it's gonna be a big deal. 1423 01:30:31,560 --> 01:30:32,910 process by dad. 1424 01:30:33,090 --> 01:30:34,500 Oh, no, go ahead. Go ahead, please. 1425 01:30:34,680 --> 01:30:37,500 No, I think the cross app comments piece for me is the one 1426 01:30:37,500 --> 01:30:39,690 I struggle with the most. And then the conversations you guys 1427 01:30:39,690 --> 01:30:41,520 have had during the board meeting has been good for me. 1428 01:30:41,520 --> 01:30:44,400 But as a hosting provider, I'm like, Okay, it's easy. It's an 1429 01:30:44,400 --> 01:30:47,700 easy thing to implement from a technical standpoint. But I'm 1430 01:30:47,700 --> 01:30:50,430 gonna have to go a different an extra step, we're going to have 1431 01:30:50,430 --> 01:30:53,010 to give him some sort of endpoint because you know, the 1432 01:30:53,010 --> 01:30:55,860 average content creator, they're not running the mastodon box, 1433 01:30:55,920 --> 01:31:00,750 they were going to have to give them a place where that origin 1434 01:31:00,750 --> 01:31:04,740 point can be. And that's the biggest challenge that I'm going 1435 01:31:04,740 --> 01:31:07,950 through my head is how do I implement it? So that is, okay. 1436 01:31:08,040 --> 01:31:10,980 When you create a new episode, where I want to populate this 1437 01:31:10,980 --> 01:31:13,950 with a link on where your cross app comments are going to 1438 01:31:14,340 --> 01:31:17,580 originate, do it for them, so they don't have to think about 1439 01:31:17,580 --> 01:31:21,180 it. That's the biggest gonna be the biggest challenge for us. 1440 01:31:21,270 --> 01:31:21,810 You know, 1441 01:31:21,810 --> 01:31:27,300 this. I'm glad you you just gave me a brainstorm Todd. This is 1442 01:31:27,330 --> 01:31:29,790 this is, this is actually really interesting, because we've had 1443 01:31:29,790 --> 01:31:33,870 this the biggest issue is moderation. And we've had this 1444 01:31:33,870 --> 01:31:39,840 debate about whether or not hosting companies should you 1445 01:31:39,840 --> 01:31:43,050 know, should be a dirty word, whether or not they should be 1446 01:31:43,080 --> 01:31:48,540 rolling their own Mastodon or just calling a Macedon API 1447 01:31:48,540 --> 01:31:54,420 somewhere that the Creator owns. And it just it strikes me that 1448 01:31:54,420 --> 01:31:59,610 you don't you can do it either direction. So you could say this 1449 01:31:59,610 --> 01:32:01,560 is what you're talking about. That would be sort of a hard 1450 01:32:01,560 --> 01:32:04,830 sell to your customer base. You could say okay, well you aren't 1451 01:32:04,830 --> 01:32:07,530 you know, you need to put in your own Mastodon you need to 1452 01:32:07,530 --> 01:32:11,550 link your own Mastodon account to your dashboard so that we can 1453 01:32:11,550 --> 01:32:14,370 create a post on your behalf when you post a new episode. 1454 01:32:14,520 --> 01:32:17,340 That's one way to do it that's they'll never do it right never 1455 01:32:17,340 --> 01:32:21,060 gives the so the the other option and I think this is just 1456 01:32:21,060 --> 01:32:26,010 as legit is what you said you run you run your own Mastodon or 1457 01:32:26,010 --> 01:32:31,230 activity poke client. But then you block Federation initially 1458 01:32:31,920 --> 01:32:36,930 to only to only other instances where you know that they have 1459 01:32:36,930 --> 01:32:40,320 solid moderation. So, so initially, you say, Okay, we're 1460 01:32:40,320 --> 01:32:43,020 going to run a mastodon, but we're not going to allow 1461 01:32:43,020 --> 01:32:46,680 comments from other instances except these on this approved 1462 01:32:46,680 --> 01:32:51,030 list. And maybe over time, you slowly expand that to include 1463 01:32:51,030 --> 01:32:54,180 more but at the beginning you say okay, Mastodon dot social, 1464 01:32:54,540 --> 01:32:58,830 you basically curate you whitelist the activity pub world 1465 01:32:58,830 --> 01:33:03,030 initially so that you don't have to, so that you're only dealing 1466 01:33:03,030 --> 01:33:06,960 with comments possibly coming from other sites where you know 1467 01:33:06,960 --> 01:33:09,900 that the monitor they're going to take care of the moderation. 1468 01:33:10,500 --> 01:33:15,600 That way you don't you have you lower your risk of having your 1469 01:33:15,810 --> 01:33:17,880 day having to moderate stuff yourself. 1470 01:33:19,110 --> 01:33:20,280 And I think that's a good idea. 1471 01:33:21,900 --> 01:33:25,920 Because Because you get you get this you get the solidity of 1472 01:33:25,920 --> 01:33:30,390 having your own platform, but you get the safety of not having 1473 01:33:30,390 --> 01:33:35,640 to accept content from the entire world from you because 1474 01:33:35,640 --> 01:33:38,730 there's if you if you restrict to just let's just say the top 1475 01:33:39,090 --> 01:33:43,620 you know, 20 well known respected Mastodon hosts by 1476 01:33:43,620 --> 01:33:49,050 size, you're probably in great shape. Because if because if a 1477 01:33:49,380 --> 01:33:53,820 if a podcaster does not have their own Mastodon account, the 1478 01:33:53,820 --> 01:33:58,230 likelihood of them carry carrying to receive comments 1479 01:33:58,230 --> 01:34:01,950 from from some Mastodon instance, it only only has six 1480 01:34:01,950 --> 01:34:07,950 people on it, it's probably zero. That's a pretty good that 1481 01:34:07,950 --> 01:34:10,170 might be the way forward, you know. 1482 01:34:12,570 --> 01:34:15,660 Yeah, you know, again, it's just how do we get the adoption? We 1483 01:34:15,660 --> 01:34:17,970 can put it in there things slap that in there and have that in 1484 01:34:17,970 --> 01:34:21,990 there a week. But how do you you know, how do you make it so 1485 01:34:21,990 --> 01:34:23,700 they're actually going to use it all adoption 1486 01:34:23,700 --> 01:34:27,480 is slow with podcasting. And from time to time from time to 1487 01:34:27,480 --> 01:34:34,140 time? Something happens. And 2016 I believe was cereal. It 1488 01:34:34,140 --> 01:34:38,250 happened at this which cereal have made a difference two years 1489 01:34:38,280 --> 01:34:42,750 earlier, maybe not. All all elements of the universe, 1490 01:34:42,750 --> 01:34:45,750 everything kind of melded together, and then it just 1491 01:34:45,750 --> 01:34:48,810 happened. But you can't force that. You can't. I mean, how 1492 01:34:48,810 --> 01:34:51,540 many people told me Oh, man, you gotta get draw up, I guess. Do 1493 01:34:52,380 --> 01:34:56,880 you wanna get drawers gonna be like, Yeah, I'm sure Joe Rogan 1494 01:34:56,880 --> 01:34:59,460 would make a huge difference, but we don't have to sit around 1495 01:34:59,460 --> 01:35:02,550 and wait for that. It is right, the little things will happen 1496 01:35:02,550 --> 01:35:07,350 and the Bitcoin community, which is not small, that, you know, 1497 01:35:07,380 --> 01:35:11,100 they've grabbed it ran with it, they get it, they love it. And 1498 01:35:11,130 --> 01:35:15,270 they're now the big promoters, and they're making memes and 1499 01:35:15,270 --> 01:35:18,660 tweeting and et cetera, et cetera and spreading the word 1500 01:35:18,660 --> 01:35:27,000 love on noster. Last Do you know what nostril nostril stands for? 1501 01:35:27,420 --> 01:35:31,080 It's like notes and other stuff through relays. 1502 01:35:31,500 --> 01:35:36,810 Exactly. Notes. Exactly. notes and stuff through realize. Okay, 1503 01:35:36,810 --> 01:35:37,200 definitely 1504 01:35:37,200 --> 01:35:39,630 some geek name that yes, 1505 01:35:39,840 --> 01:35:43,620 you know, young young master Mitch is very enamored by noster 1506 01:35:45,780 --> 01:35:46,890 metrum pod verse. 1507 01:35:47,219 --> 01:35:50,879 It makes me tired. It makes you tired. Why does he why does it 1508 01:35:50,879 --> 01:35:51,749 make you tired? I'm 1509 01:35:51,750 --> 01:35:52,620 just curious to 1510 01:35:52,620 --> 01:35:56,550 the pub is hard enough in that's the thing is activity Pub is 1511 01:35:56,550 --> 01:36:00,390 hard enough. And we know we're going we can't the world as it 1512 01:36:00,390 --> 01:36:04,830 is now. We have to activity Pub has to be the first class 1513 01:36:04,830 --> 01:36:10,140 citizen. I totally agree. And so any other protocol, anyone just 1514 01:36:10,140 --> 01:36:14,010 makes me tired. Any other any other social protocol? I mean, 1515 01:36:14,340 --> 01:36:17,850 like I said, um, I mean, I just don't know enough about it to 1516 01:36:17,850 --> 01:36:21,000 even to even comment. Unlike Leo Laporte, I don't comment about 1517 01:36:21,000 --> 01:36:21,840 these, I have no idea. 1518 01:36:23,670 --> 01:36:26,610 The one thing I like about nostre, which I just is, there's 1519 01:36:26,610 --> 01:36:29,790 something incredibly cool about it is you can take your public 1520 01:36:29,790 --> 01:36:34,830 and private key. And you can log into noster on any app, any 1521 01:36:34,830 --> 01:36:37,230 service, you know, obviously have to be careful what you're 1522 01:36:37,230 --> 01:36:39,300 doing. Because you know, you could be posting your private 1523 01:36:39,300 --> 01:36:43,710 key into into some trap, but is really interesting, like, oh, 1524 01:36:43,710 --> 01:36:46,350 try this one, you just try this desktop client, and you and you 1525 01:36:46,350 --> 01:36:49,500 try it. And that's all you need. And it brings up everything. 1526 01:36:49,530 --> 01:36:53,340 Like, there's my whole profile, there's my follows. There's 1527 01:36:53,340 --> 01:36:58,050 something magical about the key pair, which I think may be even 1528 01:36:58,050 --> 01:37:01,560 more important than noster itself, people understanding a 1529 01:37:01,560 --> 01:37:05,910 public and private key could be revolutionary, to so many 1530 01:37:05,940 --> 01:37:07,020 aspects of life. 1531 01:37:07,440 --> 01:37:10,410 I'm gonna have to agree with Alex on this one, though, 1532 01:37:10,440 --> 01:37:15,120 though, in this regard, that the universal keys that serve as 1533 01:37:15,120 --> 01:37:20,760 universal identities scare me a bit. Oh, really? Yeah. Because 1534 01:37:20,760 --> 01:37:24,120 you because all of a sudden now you're now your identity is 1535 01:37:24,120 --> 01:37:29,070 known across your egg, your your identity travels with you all 1536 01:37:29,070 --> 01:37:32,820 the time, my public dead? Yeah, your public identity. And that 1537 01:37:32,820 --> 01:37:36,240 feels a little creepy. Like, like, I'm not sure that that's a 1538 01:37:36,240 --> 01:37:39,000 road we want to go down because there's some there's some, you 1539 01:37:39,000 --> 01:37:42,270 know, there's some nice M and N and Amity that comes from Okay, 1540 01:37:42,270 --> 01:37:45,300 well, I'm going to Mike Dells WordPress site, and I'm gonna 1541 01:37:45,300 --> 01:37:47,940 leave a comment there, but I can just make up, you know, it 1542 01:37:47,940 --> 01:37:52,230 doesn't have to be real. Like I can not have to expose myself 1543 01:37:52,620 --> 01:37:56,310 fully on every single service. Like, it's the same way with a 1544 01:37:56,310 --> 01:37:59,160 bitcoin address. I mean, if I, if I want to send if I don't 1545 01:37:59,190 --> 01:38:01,740 want you to send me some bitcoin, I mean, I can generate 1546 01:38:02,100 --> 01:38:04,980 a random wallet address for every transaction. Yeah. And I 1547 01:38:04,980 --> 01:38:07,200 have, and I have some sort of, you know, have a measure of 1548 01:38:07,200 --> 01:38:10,230 anonymity there. It's not absolute but, but there is some 1549 01:38:10,230 --> 01:38:12,870 protection there. And I'm a little, I'm a little nervous 1550 01:38:12,870 --> 01:38:15,600 about the about, there's a lot of talk, you know, with blue sky 1551 01:38:15,600 --> 01:38:19,440 and all this stuff about these, these D IDs and universal 1552 01:38:19,440 --> 01:38:21,930 identities. I don't know, they just creeped me out a little 1553 01:38:21,930 --> 01:38:22,200 bit. 1554 01:38:23,550 --> 01:38:27,060 And I think also, what we want to make sure we watch out for 1555 01:38:27,090 --> 01:38:29,730 is, you know, I've had a philosophy for a long time, then 1556 01:38:29,730 --> 01:38:33,990 basic say you never build your castle on rented land. So 1557 01:38:33,990 --> 01:38:37,320 whatever we do, we have to make sure that, you know, monkey 1558 01:38:37,320 --> 01:38:39,840 business by other companies like Twitter, shutting off their free 1559 01:38:39,840 --> 01:38:44,610 API and stuff like that is not going to affect what has been 1560 01:38:44,610 --> 01:38:47,790 built. So I'm always kind of looking down the road. I'm like, 1561 01:38:47,790 --> 01:38:50,010 what happens if somebody unplugged something now I know 1562 01:38:50,010 --> 01:38:54,210 if this podcast is index got unplugged, we would continue to 1563 01:38:54,210 --> 01:38:56,400 run we'd be pod pinging something that would hit 1564 01:38:56,400 --> 01:39:00,240 nothing, but everything would still continue to work. So I 1565 01:39:00,240 --> 01:39:04,200 think that the way we kind of look at things too is if 1566 01:39:04,200 --> 01:39:07,050 blueberry went out of business today, our PowerPress users 1567 01:39:07,050 --> 01:39:09,600 would be would be absolutely fine. They would just have to 1568 01:39:09,600 --> 01:39:14,970 find a new host. So I think as we're looking at advancing stuff 1569 01:39:14,970 --> 01:39:17,430 and podcasting 2.0 We want to make sure we tighten to stuff 1570 01:39:17,430 --> 01:39:19,890 that just can't We can't have the plug plug pulled on us. 1571 01:39:20,610 --> 01:39:22,950 Yeah, and that's the that's a great point. Todd because we 1572 01:39:22,950 --> 01:39:26,490 have like that's what we've tried to do from day one is to 1573 01:39:26,490 --> 01:39:30,720 make it where we don't to where all this stuff continues can 1574 01:39:30,720 --> 01:39:34,380 continue to exist without us. I mean, like if we just 1575 01:39:34,740 --> 01:39:38,130 podcasting we general is that way though. That's the beauty of 1576 01:39:38,130 --> 01:39:40,350 RSS you got this. 1577 01:39:40,590 --> 01:39:43,260 You try to change that it's not podcasting anymore. That's 1578 01:39:43,260 --> 01:39:43,740 right. 1579 01:39:45,870 --> 01:39:50,850 So we think a few people here while while we have the Yeah, we 1580 01:39:50,850 --> 01:39:53,070 got a couple of booster grams that have come in during this 1581 01:39:53,070 --> 01:39:59,970 lit session. Let me see. We will and thank you, by the way 36,009 1582 01:40:00,000 --> 01:40:06,360 112 Satoshis from Chimp, Adam. All caps, you say 100% All the 1583 01:40:06,360 --> 01:40:08,310 freakin time shame yourself 1584 01:40:08,670 --> 01:40:09,300 100% 1585 01:40:12,420 --> 01:40:17,400 atone wrecker 1050 rung the curio caster wallet dry with 1586 01:40:17,400 --> 01:40:22,080 this bottom of the barrel boost. Alright man, very much chimp. 1587 01:40:22,170 --> 01:40:28,590 Oh, oh chimp comes in again 33,333 ADAM You say 100% All the 1588 01:40:28,590 --> 01:40:31,650 freakin time. Thank you. You tell me again. Tell me a couple 1589 01:40:31,650 --> 01:40:34,770 more times. That's really driving that home. Yeah, but I 1590 01:40:34,770 --> 01:40:38,400 like it. I like people yelling at me while sending SATs, Eric p 1591 01:40:38,400 --> 01:40:45,330 p 33,333 330 333. Couldn't podcasters use the podcast block 1592 01:40:45,330 --> 01:40:48,990 tag to remove their podcast from the index? That still doesn't 1593 01:40:48,990 --> 01:40:51,840 solve the ownership problem. But what solves this is very 1594 01:40:51,840 --> 01:40:57,180 interesting. Maybe new rule, if you're going to take out email 1595 01:40:57,180 --> 01:40:58,770 addresses enabled the block. 1596 01:40:59,820 --> 01:41:03,330 I've told people to do that on on more than one occasion. They 1597 01:41:03,510 --> 01:41:09,630 they'll say, Hey, I've got I've got this feed. And for amusing 1598 01:41:09,930 --> 01:41:15,270 Oh, it's perfect is Apple Andy layman. He said he's using a 1599 01:41:15,270 --> 01:41:18,750 search as using a hosting company to host his his media. 1600 01:41:19,140 --> 01:41:22,410 But he's writing his own feed. He's just using them as a CDN 1601 01:41:22,410 --> 01:41:25,230 and he's got his own feed coming from PowerPress but he didn't 1602 01:41:25,230 --> 01:41:28,440 want the feed from that other hosting company coming coming 1603 01:41:28,440 --> 01:41:31,830 through in the index. So he put the blog tag in there and it 1604 01:41:31,830 --> 01:41:32,670 goes away and you're good. 1605 01:41:32,969 --> 01:41:37,079 I'm just saying hosting company should implement that. That will 1606 01:41:37,079 --> 01:41:41,189 make a lot of sense. made a note Martin Linda's CO on my list has 1607 01:41:41,189 --> 01:41:48,419 a row of ducks 222222 And he says May I plug my conversation 1608 01:41:48,419 --> 01:41:51,389 with Mitch Downey of pod verse while yes, you may episode nine 1609 01:41:51,389 --> 01:41:55,049 of Tea Party media podcast a pretty long row of ducks all the 1610 01:41:55,049 --> 01:42:00,899 best Martin Linda's cope. You bet. And we have Dred Scott 1611 01:42:00,899 --> 01:42:06,539 coming in with 121,212 20 his 1612 01:42:06,540 --> 01:42:07,830 blades on him 1613 01:42:07,830 --> 01:42:12,210 Paula go podcasting also special shout out to Mike November 7 1614 01:42:12,210 --> 01:42:15,300 Lima Mike Juliet as he is directly responsible for me 1615 01:42:15,300 --> 01:42:18,420 passing my ham radio exam several years ago with the ham 1616 01:42:18,420 --> 01:42:24,930 radio pod class. Yay. Congratulations. Yeah, I'll jump 1617 01:42:24,930 --> 01:42:27,930 in on that. 70 threes Matt keto five Alpha Charlie, Charlie. 1618 01:42:28,950 --> 01:42:30,750 Come on. Mike. Sahand Mike, I know 1619 01:42:30,930 --> 01:42:31,710 what you call it. 1620 01:42:32,099 --> 01:42:34,679 That was me. Kate lmJ There you go. 1621 01:42:34,710 --> 01:42:40,380 There you go. Exactly. Nerds Sam says the listening live over 1622 01:42:40,380 --> 01:42:44,430 there in the UK on a pulling a tug whatever talking to Paul I 1623 01:42:44,430 --> 01:42:51,630 don't fully agree Adam a cat. Oh, I'm sorry. I fully agree 1624 01:42:51,630 --> 01:42:54,390 Adam a cast were spamming everyone so Buzzsprout got 1625 01:42:54,390 --> 01:42:59,670 angry. But it doesn't work. If you don't have podcast dot txt. 1626 01:42:59,700 --> 01:43:03,840 txt. Implemented Buzzsprout has no UI for host they say you can 1627 01:43:03,840 --> 01:43:06,750 turn it back on but I can't find it. Okay, so thank you, Sam. 1628 01:43:06,750 --> 01:43:09,420 Tell me the story of how the emails disappeared out of out of 1629 01:43:09,420 --> 01:43:13,110 podcast feeds Wilson. A castle spamming everybody there was 1630 01:43:13,110 --> 01:43:16,380 this company called a cast and then bug spray. Yeah, exactly. 1631 01:43:19,590 --> 01:43:24,450 Okay, let me see we have 10 Another 10,000 from San Sethi. 1632 01:43:24,480 --> 01:43:28,170 Sam Sethi again. Why can't Oh, this is around the splits. Okay, 1633 01:43:28,170 --> 01:43:31,560 so we I'll read it. We don't have to get into it. Because 1634 01:43:31,560 --> 01:43:34,350 it's real. It's hard. It's hard enough and I'm reading it. It's 1635 01:43:34,350 --> 01:43:37,860 hard enough. Why can't we do it based on 100% This is crazy 1636 01:43:37,860 --> 01:43:41,790 doing 103% Just calculate based on 100%. So 100 SATs is easy to 1637 01:43:41,790 --> 01:43:44,970 work out. 1% fee is one set. So 99 should be 99 left to split 1638 01:43:44,970 --> 01:43:49,290 with, with why recalc if you have 30% Atomy gets which is 30 1639 01:43:49,290 --> 01:43:51,600 sashes. recalc is totally mad. Sorry. 1640 01:43:53,850 --> 01:43:58,350 The proper answer to that is do it that way. Yes. Yeah. Do it 1641 01:43:58,350 --> 01:44:01,950 that way. And then and then for your own sake of your own math. 1642 01:44:02,370 --> 01:44:06,570 It makes it simple. Yeah, you've totally everybody should be 1643 01:44:06,570 --> 01:44:10,380 doing it based on base 100. That's what we did. The issue is 1644 01:44:10,380 --> 01:44:10,770 that if you 1645 01:44:11,100 --> 01:44:14,220 are a fighter jets go to 104%. 1646 01:44:15,150 --> 01:44:21,630 Oh, my was to 11. I know. Yeah. I think we've kind of figured 1647 01:44:21,630 --> 01:44:24,750 out that this is for under the hood and not on top of the 1648 01:44:24,750 --> 01:44:29,880 blankets. Under the hood is Sockeye the horse 1000 Go 1649 01:44:29,880 --> 01:44:37,920 podcasting. Who was this? Todd Cochran? 122,222 Oh 1650 01:44:40,260 --> 01:44:41,490 20 Is blade. 1651 01:44:44,880 --> 01:44:52,770 And then we have 44,100 from Mike Dell, who says your guest 1652 01:44:52,770 --> 01:44:57,870 today are rockstars do this illegal. That's illegal. That's 1653 01:44:57,870 --> 01:45:01,560 a violation violation violation. violation of all rules. 1654 01:45:05,009 --> 01:45:07,619 Taxes on that, Mike. It's not it's not right, dude. 1655 01:45:07,800 --> 01:45:11,580 When did you when did you? Okay, I think I think we can leave it 1656 01:45:11,580 --> 01:45:14,040 here because everything after that is four hours ago you 1657 01:45:14,040 --> 01:45:16,710 should we thank the people who came in and support our value 1658 01:45:16,710 --> 01:45:19,350 for value proposition, Mr. Mr. Jones. 1659 01:45:19,649 --> 01:45:23,099 Oh, we've got one. We've got one mega Paixao here. 1660 01:45:23,249 --> 01:45:26,399 We do. Yeah, you ready? I'm ready. I'm sitting down 1661 01:45:27,660 --> 01:45:33,540 from Ben and Alberto at our Cisco comm. Send us 1010 dot 1662 01:45:33,540 --> 01:45:39,480 101 $1,010.10 Whoa. 1663 01:45:40,800 --> 01:45:46,650 Oh, man. Oh, thank you so much to have a note with this 1664 01:45:46,650 --> 01:45:47,940 wonderful support. 1665 01:45:48,300 --> 01:45:51,210 There is a note Adam and Dave all the bits referenced the 1666 01:45:51,210 --> 01:45:54,750 amount and pieces of podcasting to Puno makes such a beautiful 1667 01:45:54,750 --> 01:45:58,080 opportunity for podcasting and podcasters. Thanks for working 1668 01:45:58,080 --> 01:46:00,660 so hard to bring opportunity into reality for so many from 1669 01:46:00,660 --> 01:46:02,310 your friends@rss.com. 1670 01:46:03,300 --> 01:46:06,870 Guys, thank you so much. That is humbling, man. Thanks. That's a 1671 01:46:06,870 --> 01:46:09,510 lot of value. You get out of this and you returned it that 1672 01:46:09,510 --> 01:46:11,880 way. And thank you. Thank you. Thank you. Thank you. 1673 01:46:12,390 --> 01:46:15,840 Pretty Yeah. Now, yeah. That is 1674 01:46:15,930 --> 01:46:19,080 the that's the Pay Pal. Because we've transitioned. 1675 01:46:19,350 --> 01:46:24,030 That is we have transitioned the I'd have a make good though. Oh, 1676 01:46:24,600 --> 01:46:28,590 Martin. Martin from pod friend. I missed his boost last week. 1677 01:46:28,770 --> 01:46:35,010 Oh, so he sent in 2018 and 20 to 22 to two to two. And he said I 1678 01:46:35,010 --> 01:46:37,710 just wanted to say that to everyone that re implementing a 1679 01:46:37,710 --> 01:46:40,020 podcast app from scratch seemed like something that could be 1680 01:46:40,020 --> 01:46:43,860 done decently quickly. Spoiler spoiler alert. It is not. But 1681 01:46:43,860 --> 01:46:47,700 fun. Can't wait to join the new feature dev race again in some 1682 01:46:47,700 --> 01:46:50,340 months. Oh, so it sounds like he's doing it from scratch. 1683 01:46:50,340 --> 01:46:50,880 rewriter 1684 01:46:51,000 --> 01:46:56,130 Wow, hold on. We get some ducks out for me. I still have my 1685 01:46:56,130 --> 01:47:00,570 pillow. We still use our mug. I'm drinking out of my mug and 1686 01:47:00,570 --> 01:47:03,540 we love the pot with the we love the pod friend. 1687 01:47:04,260 --> 01:47:06,960 And he sent another 10,000 SATs and he did his message was 1688 01:47:06,990 --> 01:47:07,950 relevant boost. 1689 01:47:07,980 --> 01:47:09,690 Yes. Okay. Thank you. 1690 01:47:12,060 --> 01:47:15,960 Thank you. Appreciate that. Martin. Yeah. And we've got from 1691 01:47:15,960 --> 01:47:21,750 Borlaug. 25,000 SATs. He says the two of you are a gift to the 1692 01:47:21,750 --> 01:47:23,910 industry. And I appreciate all your hard work. Well, thank you 1693 01:47:23,910 --> 01:47:25,080 Borlaug. Appreciate that. 1694 01:47:25,350 --> 01:47:27,390 A gift gift to the industry. 1695 01:47:27,600 --> 01:47:31,800 That's Yes, I tell them that's my motivational speaking to 1696 01:47:31,800 --> 01:47:33,030 myself every morning when I wake up. 1697 01:47:33,600 --> 01:47:36,900 You're a gift to the industry. Dave, you're a gift to the 1698 01:47:36,900 --> 01:47:39,600 industry. I want to every morning I'm gonna send you a tax 1699 01:47:39,810 --> 01:47:42,840 day. You're a gift to the industry. 1700 01:47:43,170 --> 01:47:44,700 And I'm just gonna replan is that yes, 1701 01:47:44,910 --> 01:47:49,080 yeah. Word Up. One 100% 1702 01:47:50,640 --> 01:47:55,290 roster Calavera fire roster Calavera 2000 sets through 1703 01:47:55,290 --> 01:47:57,900 fountain says bless you Dave Jones heal up more beef 1704 01:47:57,900 --> 01:47:59,340 milkshakes are needed Yes. 1705 01:48:00,360 --> 01:48:02,010 Hey, how are you feeling? You sound good? 1706 01:48:02,759 --> 01:48:05,969 I've got a lot more energy it's just the linger you know that's 1707 01:48:05,969 --> 01:48:10,409 crap just lingers forever but I'm good I'm good. Good. Yay. 1708 01:48:11,909 --> 01:48:17,459 Oh, here's a mike Dell 12345335 Verse he says go podcasting 1709 01:48:18,119 --> 01:48:27,059 unanimous safe in in for VX? Send us through curio Castro 1710 01:48:27,119 --> 01:48:30,509 2102 And he says thank you for your coding 70 threes and such 1711 01:48:30,539 --> 01:48:34,739 dash 70 threes and such the mere mortals podcast are ready Kira 1712 01:48:34,739 --> 01:48:39,119 and 2222 through fountain he says Dave stat saved the day. 1713 01:48:39,269 --> 01:48:43,709 1.5 million poop casts Wow, that's a lot of crap. 1714 01:48:44,790 --> 01:48:46,620 Referring to anchor I presume. 1715 01:48:46,980 --> 01:48:51,840 Yes. We're doing another another chop and drop. Chopping drawers 1716 01:48:51,840 --> 01:48:54,840 we as as we speak. This one's going to be brutal. 1717 01:48:54,900 --> 01:49:00,570 That's our title home. Beautiful. Yeah, stop dancing on 1718 01:49:00,570 --> 01:49:01,830 graves. Come on, man. 1719 01:49:03,150 --> 01:49:04,380 We're doing a bit of that too. 1720 01:49:05,160 --> 01:49:08,580 Are you well, the current, the current, the current expanded 1721 01:49:08,580 --> 01:49:13,890 criteria for getting the CHOP is if you've only got one episode 1722 01:49:13,890 --> 01:49:19,920 in your feed, and you haven't published for for a year, you're 1723 01:49:19,920 --> 01:49:23,220 gone. You're gonna and I'm not even looking at how long the 1724 01:49:23,220 --> 01:49:27,330 episode is. Just to make it be an hour. It's not it's a goner. 1725 01:49:27,870 --> 01:49:30,120 And I don't care if that's too zealous. I just don't care 1726 01:49:30,120 --> 01:49:30,480 anymore. 1727 01:49:31,500 --> 01:49:36,180 Wait, and if okay, you know, so how long how long is 1728 01:49:36,180 --> 01:49:38,520 this only applies to this only applies to anchor and 1729 01:49:39,420 --> 01:49:41,850 Okay, why don't we just shut anchor off altogether? 1730 01:49:44,400 --> 01:49:45,630 Don't Don't hit me. 1731 01:49:46,200 --> 01:49:49,020 Like three. There's three shows over there at least that are 1732 01:49:49,020 --> 01:49:49,560 decent. 1733 01:49:52,830 --> 01:49:55,110 That's a little aggressive. Like, I think if you're 1734 01:49:55,110 --> 01:49:58,650 hosted anger, you should request it to be added. You know, it's 1735 01:49:58,650 --> 01:50:01,350 like you shouldn't you should Really you should beg us. 1736 01:50:02,190 --> 01:50:06,540 Yes. That's begging is not a bad system. This there could be 1737 01:50:06,570 --> 01:50:10,710 there could be a part of the protocol. Yeah, yeah, we're 1738 01:50:10,710 --> 01:50:13,530 chopping so you think of your chop and drop more than egg 1739 01:50:13,530 --> 01:50:16,170 insertion system? I mean that's that's a pretty strong title. 1740 01:50:16,229 --> 01:50:22,139 I like chop and drop. Alright job, but it Hey, it's your show 1741 01:50:22,139 --> 01:50:26,189 to you want egg and egg and it sounds like artificial 1742 01:50:26,189 --> 01:50:28,229 insemination in some weird ways. 1743 01:50:28,620 --> 01:50:31,170 It does. We'll we'll put out a poll. 1744 01:50:31,739 --> 01:50:33,299 Oh, yes. Every is on Twitter. 1745 01:50:35,580 --> 01:50:40,200 Elon Spotify, Jean Everett 33 333 Your fountain and he just 1746 01:50:40,200 --> 01:50:41,790 says boost Yeah. 1747 01:50:42,630 --> 01:50:43,830 Gotcha brother. Thank you. 1748 01:50:45,930 --> 01:50:48,810 Fountain mere mortals podcast Karen back again. He says the 1749 01:50:48,810 --> 01:50:51,840 blurring of your mouth was crazy. Good thing you still 1750 01:50:51,840 --> 01:50:54,390 don't have that glam rock hair would have censored that for 1751 01:50:54,390 --> 01:50:54,840 sure. 1752 01:50:55,440 --> 01:50:58,950 That's on Joe Rogan. Did you hear my Joe Rogan? Episode? 1753 01:50:58,950 --> 01:51:02,310 I'm about halfway through. Yeah. Yeah. Yeah. 1754 01:51:02,940 --> 01:51:04,770 I tried to fire him like I tried. 1755 01:51:05,850 --> 01:51:09,720 Yeah, or default. I heard they heard the attempts, the aborted 1756 01:51:09,750 --> 01:51:10,740 abortive attempts. 1757 01:51:11,520 --> 01:51:15,360 You made the news a little bit there you were you were shown on 1758 01:51:15,570 --> 01:51:18,000 least Fox as far as I know. You know, so 1759 01:51:18,000 --> 01:51:21,030 many people sent me that because it was a rant to Joe was doing. 1760 01:51:21,870 --> 01:51:25,710 About about the news, specifically CNN. Like, Hey, 1761 01:51:25,710 --> 01:51:29,850 man, you made the news. Like yeah, okay, so, of the 2 million 1762 01:51:29,850 --> 01:51:33,510 people on Fox and Friends in the morning. 12 million people on 1763 01:51:33,510 --> 01:51:35,400 Joe Rogan. It's like, okay, yeah, 1764 01:51:35,640 --> 01:51:38,880 it was a nice addition. Yeah, it's just a little backwards. 1765 01:51:38,880 --> 01:51:39,090 Right? 1766 01:51:39,120 --> 01:51:41,580 You have no idea what happens when you go on Joe Rogan. 1767 01:51:42,360 --> 01:51:45,120 But you are a right wing nut job. So I mean, 1768 01:51:45,150 --> 01:51:48,810 we know that and by the way, you know, this is all just for one 1769 01:51:48,810 --> 01:51:51,300 reason. And that's to get Alex Jones back on the air. 1770 01:51:51,780 --> 01:51:59,430 Yeah, absolutely. Mission accomplished. I am Mr. Robot 432 1771 01:51:59,460 --> 01:52:02,190 through fountain he says love the show, the stats, the tech, 1772 01:52:02,220 --> 01:52:06,210 et cetera, about Patreon people, especially Canadians and 1773 01:52:06,210 --> 01:52:09,270 Bitcoiners lost trust in it after the trucker strike in 1774 01:52:09,270 --> 01:52:12,630 Canada last year when they froze those Patreon funds because it's 1775 01:52:12,630 --> 01:52:15,300 a centralized entity. Yeah, that was messed up. 1776 01:52:15,360 --> 01:52:20,970 Yeah, Mr. Robot. He helped get Texas limbs podcast up and 1777 01:52:20,970 --> 01:52:21,300 running. 1778 01:52:21,870 --> 01:52:26,580 Oh, good. Okay. Joel ws Sachtler Richards through fountain no 1779 01:52:26,580 --> 01:52:31,680 note. I am Mr. Robot again. 3456 through fountain he says booths 1780 01:52:31,680 --> 01:52:35,700 got cut off wanted to add that podcasting. 2.0 is the future 1781 01:52:35,700 --> 01:52:37,290 and here to stay go podcasting? 1782 01:52:37,320 --> 01:52:41,370 Yeah, Brother You got got cut off. 1783 01:52:43,350 --> 01:52:47,760 Gene been 1337 elite booster cast Matic and he says Adam, 1784 01:52:47,940 --> 01:52:51,570 following up on moon pay KYC stuff. I'm in the US. 1785 01:52:52,590 --> 01:52:57,030 Oh, okay. Yeah, some people apparently do have to take a 1786 01:52:57,030 --> 01:53:00,450 picture and turn their head and cough. That was not my 1787 01:53:00,450 --> 01:53:03,690 experience. But thanks. Thanks for the updates. Good to know, 1788 01:53:03,720 --> 01:53:08,010 good to know. And the people who implement Moon pay let let your 1789 01:53:08,250 --> 01:53:12,480 users know you may be asked to cough. Yeah. Just add that 1790 01:53:12,510 --> 01:53:17,520 people get when it comes to funny enough how easy people are 1791 01:53:17,520 --> 01:53:21,270 to post their location, you know, selfies, everything. But 1792 01:53:21,480 --> 01:53:25,800 oh, man, someone's asking me for my driver's license. Now, they 1793 01:53:25,800 --> 01:53:26,700 get really worried. 1794 01:53:27,240 --> 01:53:30,540 It's funny, because it's really no different than anything else 1795 01:53:30,540 --> 01:53:34,980 we do. It's just that you're hit with it all at once. Like, like 1796 01:53:34,980 --> 01:53:40,140 when not people say things like, you know, oh, the Apple 1797 01:53:40,140 --> 01:53:44,010 subscription thing is so seamless. And it is. But the 1798 01:53:44,010 --> 01:53:47,280 reason is because you did the KYC stuff for all your financial 1799 01:53:47,280 --> 01:53:51,660 accounts, months and yeah, nor years ago. Exactly. Right. And 1800 01:53:51,660 --> 01:53:54,030 now and with the Bitcoin thing you're hit, you're getting hit 1801 01:53:54,030 --> 01:53:57,420 with it right now for the first time. So it's really the in the 1802 01:53:57,420 --> 01:54:01,230 grand scheme of things. It's not different. It's not more onerous 1803 01:54:01,230 --> 01:54:04,200 than than having a credit card or bank account or something 1804 01:54:04,200 --> 01:54:07,260 like that. It's actually less, but you just have to do it. 1805 01:54:07,260 --> 01:54:08,910 Whereas the other stuff you just always had 1806 01:54:09,360 --> 01:54:14,070 people expect a credit card to just work and not have to show 1807 01:54:14,070 --> 01:54:16,980 all this stuff just to use your credit card or your debit card. 1808 01:54:16,980 --> 01:54:20,970 Yeah, yeah, that's that's where it's different. Yeah. 1809 01:54:22,410 --> 01:54:26,220 Chris last for Jupiter broadcasting. Mr. Chris Fisher. 1810 01:54:26,340 --> 01:54:31,800 He sends us a 808 80,000 SATs through pod version. He says the 1811 01:54:31,800 --> 01:54:35,640 whole episode was a was a great conversation. Dave and Adam he 1812 01:54:35,640 --> 01:54:38,220 both had been showing up and kicking butt while dealing with 1813 01:54:38,220 --> 01:54:41,340 a rebuilt mouth and getting sick show hasn't missed a beat your 1814 01:54:41,340 --> 01:54:42,000 pros. 1815 01:54:46,800 --> 01:54:48,630 Adam and Dave swinging from the vine. 1816 01:54:48,870 --> 01:54:54,150 Thank you, Chris. Appreciate that SLC through fountain 12 for 1817 01:54:54,150 --> 01:54:58,260 90 days as Fiat goes out and BTC goes in and only comes out for 1818 01:54:58,260 --> 01:55:01,740 beef and boosts Nice. Let's go some reverb on you equals bless 1819 01:55:01,740 --> 01:55:05,160 your heart. Anyone running a church soundboard for the band 1820 01:55:05,160 --> 01:55:12,300 knows this little more reverb Gladys, more reverb. Oh, Mike. 1821 01:55:12,300 --> 01:55:12,630 Sorry, 1822 01:55:12,720 --> 01:55:15,870 I gotta set that up so I can add. I don't know. I won't be 1823 01:55:15,870 --> 01:55:17,130 able to you won't be able to hear it if 1824 01:55:17,130 --> 01:55:19,500 you have reverb, the church soundboard. 1825 01:55:20,010 --> 01:55:21,330 I know what you mean. 1826 01:55:22,320 --> 01:55:26,040 SLC again, 12 498 through foundry says Hey, Adam is me 1827 01:55:26,040 --> 01:55:30,000 your son. Don't worry, I'm doing great. Good to hear from you. 1828 01:55:32,640 --> 01:55:38,970 Hello, Steven, the pneumatic coder 1555 through the podcast 1829 01:55:38,970 --> 01:55:41,610 index website and he says podcast platforms like Spotify 1830 01:55:41,850 --> 01:55:45,360 are about owning podcasters and the products of their work go 1831 01:55:45,360 --> 01:55:46,380 value for value 1832 01:55:46,500 --> 01:55:49,860 nice. We don't I don't like it. 1833 01:55:51,000 --> 01:55:56,760 6969 from pay citizen through pod versed proverbs. He says I 1834 01:55:56,760 --> 01:56:02,340 love you guys. A lot. Thanks, brother. Love you too. Love you. 1835 01:56:02,910 --> 01:56:10,830 Booster. LSA magenta monkey through breeze, send us 54321 1836 01:56:10,860 --> 01:56:14,040 And that just says that you would think that's Roy 1837 01:56:14,550 --> 01:56:17,610 Yeah, that's that's his that's his handle almost. 1838 01:56:17,730 --> 01:56:21,450 Yeah, the 54321 and just as podcast index.org is the only 1839 01:56:21,450 --> 01:56:23,850 thing in the note. And then he but then he follows up so I 1840 01:56:23,850 --> 01:56:27,210 think he Oh yeah, that's exactly what this really follows up with 1841 01:56:27,210 --> 01:56:32,880 another 543200 sending another boost because I used an 1842 01:56:32,880 --> 01:56:34,470 anonymous profile previously. 1843 01:56:34,650 --> 01:56:36,630 And what was that? What was that profile? 1844 01:56:38,040 --> 01:56:41,310 Crimson monkey. Crimson magenta mug. 1845 01:56:42,750 --> 01:56:45,570 Alright, so now we know if we see magenta monkey anywhere we 1846 01:56:45,570 --> 01:56:51,090 know it's Roy well, those two booths together Oh, he hit 1847 01:56:51,990 --> 01:56:55,320 20 his blades on him Paula thanks Roy. 1848 01:56:56,250 --> 01:57:01,620 Love you Roy comes with Gemini had done head tone record 10,000 1849 01:57:01,620 --> 01:57:04,530 says through fountain he says great seeing days post that the 1850 01:57:04,530 --> 01:57:07,650 meeting with Michael and Sam the wavelength went well. The four v 1851 01:57:07,650 --> 01:57:12,330 music surf swell increasing also confirming curio Castro music 1852 01:57:12,330 --> 01:57:14,880 section displays my feeds added from wave Lake testing 1853 01:57:14,880 --> 01:57:18,450 continues. Thanks to everyone working on this area. Yeah, it's 1854 01:57:18,480 --> 01:57:21,030 it's it was a good meeting and we're going to have them on the 1855 01:57:21,030 --> 01:57:26,280 show. On March the like first weekend in March, our cool 1856 01:57:26,280 --> 01:57:30,900 Friday and I'm very excited about that. Great, great guys to 1857 01:57:30,900 --> 01:57:34,890 talk to you. They totally get it. Yeah, it's there. This is 1858 01:57:34,890 --> 01:57:39,270 going to be fun. As the gore log again 20 It 1859 01:57:39,270 --> 01:57:40,950 will good no no go no, continue. 1860 01:57:40,950 --> 01:57:44,190 I'm sorry. That's 25,000 SATs through pod verse and he says 1861 01:57:44,190 --> 01:57:46,980 thank you for everything you do. And I'm grateful this podcast 1862 01:57:46,980 --> 01:57:47,460 exists 1863 01:57:47,490 --> 01:57:49,800 Oh thank you. That's real. That's true value man. 1864 01:57:49,800 --> 01:57:50,940 Appreciate that period. I'm 1865 01:57:50,940 --> 01:57:54,810 grateful that you exist for beautiful and they delimiter 1866 01:57:54,810 --> 01:57:58,590 chemistry blogger 30 3015 through fountain and he says in 1867 01:57:58,590 --> 01:58:01,800 a world where mindsets are besieged by parasitical 1868 01:58:01,800 --> 01:58:05,700 information gatekeepers caretakers of the cast dashing 1869 01:58:05,700 --> 01:58:09,330 Dave Jones in a Sergent Adam curry step up every week to 1870 01:58:09,330 --> 01:58:12,480 provide protective powers preserving podcast prowess, we 1871 01:58:12,480 --> 01:58:15,960 were honored to promote the AI dot cooking podcast, a show 1872 01:58:15,960 --> 01:58:20,070 about existential cutting edge tech enlivened by boundlessly 1873 01:58:20,130 --> 01:58:25,170 enthusiastic family man Gregory Forman, yo, boost Thank 1874 01:58:25,170 --> 01:58:28,830 you comics for Blogger. I'm all for AI now now that I know what 1875 01:58:28,830 --> 01:58:32,400 it stands for Adam intelligence there you go, everybody boom, 1876 01:58:32,790 --> 01:58:38,370 there it is. Ai rocks. Ah, thank you all very much monthlies 1877 01:58:38,430 --> 01:58:41,040 months. Oh, yeah, do the monthlies and I will check the I 1878 01:58:41,040 --> 01:58:42,600 will check the the tally coin. 1879 01:58:43,710 --> 01:58:49,140 Chad Pharaoh $20.20 Thank you brother Chad. Scott Jalbert $12 1880 01:58:49,140 --> 01:58:55,110 Pedro gun calvess $5 Aaron Renaud $5 Jouvert Garate new 1881 01:58:55,110 --> 01:59:00,090 donor $3 Thank you and Schubert, Martin, Linda Skog. $1 Thank you 1882 01:59:00,090 --> 01:59:03,210 Martin and Mark Graham $1. And that's our group 1883 01:59:03,240 --> 01:59:05,910 and Dred Scott as he left the chat room. 1884 01:59:07,320 --> 01:59:09,300 Did he did he throw sets into the room? 1885 01:59:10,530 --> 01:59:13,260 Yeah, he did. Like just threw some on the floor through tally 1886 01:59:13,260 --> 01:59:15,960 coin. He says just wanted to make sure you had something to 1887 01:59:15,960 --> 01:59:21,840 be here in the tally coin. 85,450 Satoshis tallyho he says 1888 01:59:23,790 --> 01:59:26,520 Bruce Wayne of podcasting everybody. We have no idea how 1889 01:59:26,520 --> 01:59:29,220 he does it where his family wealth comes from but we love 1890 01:59:29,220 --> 01:59:32,490 him. We love and afford. He's got a cave for sure. 1891 01:59:32,520 --> 01:59:36,840 Huge library on the on the sixth floor, huge library where he 1892 01:59:36,840 --> 01:59:41,340 keeps all of his his legion that legion of superhero costumes and 1893 01:59:41,340 --> 01:59:41,670 everything. 1894 01:59:42,180 --> 01:59:47,640 So we this is two hours on the nose. No punches kind of good. 1895 01:59:47,640 --> 01:59:51,060 You gotta go back to work Dave. I think they do the do the 1896 01:59:51,060 --> 01:59:54,570 actual actual work. This is a value for value podcast. 1897 01:59:54,960 --> 01:59:59,190 Everything that comes in is appreciation and value for what 1898 01:59:59,190 --> 02:00:03,210 this podcast And what the index the whole project is funded by 1899 02:00:03,210 --> 02:00:06,690 the people who support it, who get value out of it. podcast 1900 02:00:06,690 --> 02:00:10,290 index.org You can go to this scroll to the bottom there's a 1901 02:00:10,290 --> 02:00:13,890 big red donate button that'll take it to the Fiat fund coupon 1902 02:00:14,040 --> 02:00:17,610 system from PayPal, which as you can hear is not very popular 1903 02:00:17,610 --> 02:00:21,600 anymore. Although for some of those bigger bigger supporters, 1904 02:00:21,630 --> 02:00:24,750 it's always appreciated and of course, you might want to try 1905 02:00:24,750 --> 02:00:28,830 out a new and modern podcast new podcasts apps.com Kick out those 1906 02:00:28,830 --> 02:00:33,390 legacy apps also new to podcast it completely works absolutely. 1907 02:00:34,200 --> 02:00:37,320 Todd and Mike brothers thank you so much it was great to have you 1908 02:00:37,320 --> 02:00:41,160 guys on and really appreciate the enthusiasm and and all the 1909 02:00:41,160 --> 02:00:44,160 work you're putting on into it and please thank your your team 1910 02:00:44,160 --> 02:00:45,450 at blueberry as well. 1911 02:00:46,440 --> 02:00:48,750 And thanks Adam for having us on and Dave and I do want to give 1912 02:00:48,750 --> 02:00:52,620 one shout out to Andy layman Thank you brother for carrying 1913 02:00:52,620 --> 02:00:55,800 us for a long time by making that add on plugin for power 1914 02:00:55,800 --> 02:01:00,090 press it was it was a it got it got us over the hump so Andy 1915 02:01:00,090 --> 02:01:01,020 thank you so much for that 1916 02:01:01,140 --> 02:01:04,470 another hero of podcasting 2.0 The Revolution 1917 02:01:05,040 --> 02:01:06,840 Yeah, thanks. Thanks for having us. 1918 02:01:07,050 --> 02:01:11,010 Oh yeah, and well we'll have you guys on again soon I'm sure when 1919 02:01:11,190 --> 02:01:13,800 when you have an update when when stuff was flying around or 1920 02:01:13,800 --> 02:01:16,650 not if you're if you go bankrupt either way we'll have yon 1921 02:01:18,060 --> 02:01:19,320 not planning on it. No. 1922 02:01:20,250 --> 02:01:24,480 We were in this for the vow of poverty as well. So for sure. 1923 02:01:25,440 --> 02:01:30,840 Dave anything else? Anything else we need? Are we good? Are 1924 02:01:30,870 --> 02:01:32,370 we good for the weekend? 1925 02:01:33,089 --> 02:01:36,959 We're good for the weekend. I have a I have a podcast 1926 02:01:36,959 --> 02:01:38,969 ownership verification service to build 1927 02:01:41,880 --> 02:01:45,000 Please don't Don't build it please 1928 02:01:45,030 --> 02:01:48,150 don't gonna build it I'm gonna build it I'm gonna build it and 1929 02:01:48,150 --> 02:01:49,770 but it didn't build it Okay, he's 1930 02:01:49,770 --> 02:01:52,320 gonna build it and then challenge has been thrown down 1931 02:01:52,350 --> 02:01:55,740 it feels kind of like you're gonna build it and never be used 1932 02:01:55,740 --> 02:01:59,370 kind of like I got a generator two years ago and I can't get 1933 02:01:59,370 --> 02:02:03,090 the power to go out here now like all the Texas is down and 1934 02:02:03,120 --> 02:02:06,180 we still have power like come on, man. I want that thing to 1935 02:02:06,180 --> 02:02:06,960 kick in. 1936 02:02:07,200 --> 02:02:10,230 You're gonna have to pay somebody in Hill Country to EMP 1937 02:02:10,230 --> 02:02:12,600 you you know, so you can test it. 1938 02:02:12,630 --> 02:02:16,110 They are pulling cape of fiber and fried by right by our 1939 02:02:16,110 --> 02:02:16,710 property 1940 02:02:17,250 --> 02:02:22,410 that you need to say Oh, really? Yes. Yeah. Yeah. Good Juju. You 1941 02:02:22,470 --> 02:02:26,280 all have Hill Country is getting lit. Oops. Is getting fiber. 1942 02:02:26,310 --> 02:02:26,790 Yeah. 1943 02:02:27,240 --> 02:02:29,610 Now you need to pay you need to pay a good old boy and he'll 1944 02:02:29,610 --> 02:02:33,900 country to chop your power for what just so you can say to 1945 02:02:33,900 --> 02:02:37,200 Tina, see? See, I told you we had to do this. 1946 02:02:37,679 --> 02:02:40,919 I have friends who have those big, like belts, you know, that 1947 02:02:40,919 --> 02:02:44,039 are like motorcycle chains and just throw one of those wires. 1948 02:02:44,039 --> 02:02:45,209 It'd be fine. Oh, yeah. 1949 02:02:45,210 --> 02:02:47,340 You'd be fine. Yeah, they'll be alright everybody 1950 02:02:47,340 --> 02:02:50,070 that was in podcasting. 2.0 For today, the board meeting. We 1951 02:02:50,070 --> 02:02:52,800 appreciate having our guests here. And we'll be back next 1952 02:02:52,800 --> 02:02:55,110 week with another board meeting to bring you up to speed on 1953 02:02:55,110 --> 02:02:57,960 what's happening right here podcasting 2.0. 1954 02:03:12,030 --> 02:03:13,170 affect your chat room. 1955 02:03:14,670 --> 02:03:18,600 You have been listening to podcasting. 2.0 To visit 1956 02:03:18,600 --> 02:03:25,590 podcasts index dashboard for more information. Or cool Ding 1957 02:03:25,590 --> 02:03:28,410 ding ding ding ding ding ding ding ding ding ding