Episode 108: Hard Out

1 00:00:00,810 --> 00:00:07,020 podcasting 2.0 for October 28 2022, episode 108 part out 2 00:00:08,760 --> 00:00:13,110 hello everybody. And once again it is time for the weekly board 3 00:00:13,110 --> 00:00:16,800 meeting of podcasting 2.0 If you're a podcasting one point 4 00:00:16,800 --> 00:00:19,650 over you are welcome we're backwards compatible, everything 5 00:00:19,650 --> 00:00:23,730 going on a podcast index.org All the things that you need to know 6 00:00:23,730 --> 00:00:26,280 about the new standards, the namespace and of course 7 00:00:26,640 --> 00:00:29,790 everything we're discussing a podcast index dot social. I'm 8 00:00:29,790 --> 00:00:33,030 Adam curry here in the heart of the Texas Hill Country and in 9 00:00:33,030 --> 00:00:36,420 Alabama ladies, they'll get to your email eventually say hello 10 00:00:36,420 --> 00:00:39,390 to my friend on the other end Mr. Dame Jones 11 00:00:40,920 --> 00:00:43,470 were early victims of the tredinnick 12 00:00:44,670 --> 00:00:48,270 not you know if only they had used tried Demick instead, they 13 00:00:48,270 --> 00:00:52,260 use triple Demmick which is dumb is bad marketing. 14 00:00:53,159 --> 00:00:57,149 What would the twin demic was the one the previous one yes. So 15 00:00:57,149 --> 00:00:59,099 this is the I guess they couldn't they didn't set the 16 00:00:59,099 --> 00:01:03,419 standard with by by dynamic they had to go that it gets keep with 17 00:01:03,419 --> 00:01:07,829 the same off off label usage. So they went with try triple 18 00:01:07,829 --> 00:01:08,279 Dimmick. 19 00:01:08,460 --> 00:01:11,460 Now we discussed this on no agenda, and we decided that it 20 00:01:11,460 --> 00:01:17,670 was bad marketing because if you say dried Demick it sounds kind 21 00:01:17,670 --> 00:01:20,460 of scary. If you say triple Demmick it sounds like something 22 00:01:20,460 --> 00:01:21,570 you'd get at McDonald's. 23 00:01:22,860 --> 00:01:25,530 Or a ride at an amusement ride. Yes, 24 00:01:25,710 --> 00:01:28,350 it's a triple Demmick I want to go on the trip with David daddy. 25 00:01:30,000 --> 00:01:33,090 The like the sense it's like a rat in The Simpsons area of 26 00:01:33,090 --> 00:01:38,790 Universal Studios. Exactly. Mary, Mary marigold my youngest 27 00:01:38,790 --> 00:01:39,720 my 12 year old she 28 00:01:39,930 --> 00:01:44,670 beautiful. Marigold. Thank you. Do you call her Mary for short 29 00:01:44,670 --> 00:01:46,650 or just hey, you know what, 30 00:01:46,800 --> 00:01:49,920 when when everything's when times are good. Yeah, it's Mary 31 00:01:49,920 --> 00:01:50,250 Mary 32 00:01:50,250 --> 00:01:55,170 and Mary gold. Yeah. Yeah, 33 00:01:55,320 --> 00:01:59,130 she woke up this morning with fever. Then my wife's coffin and 34 00:01:59,130 --> 00:02:00,360 everything. Like oh crap, you 35 00:02:00,690 --> 00:02:04,560 see, triple damage down for the count. Super bug. We're all 36 00:02:04,560 --> 00:02:07,200 gonna die who has monkey pox these days. 37 00:02:07,860 --> 00:02:12,330 But it's coming. It just weighs it's gonna be the next big thing 38 00:02:12,330 --> 00:02:13,920 just you just got to wait. It's not here yet. 39 00:02:14,100 --> 00:02:18,900 Now just briefly, say my empty nester now, how you doing proper 40 00:02:21,210 --> 00:02:23,820 Alright, it's I'm getting there. 41 00:02:24,090 --> 00:02:26,520 You'll be laughing about this and it's six months. 42 00:02:28,350 --> 00:02:31,860 It's been rough man. I'm Miss missed the hell out of my kids. 43 00:02:32,400 --> 00:02:34,140 So you just had the one left? 44 00:02:35,160 --> 00:02:39,270 Yeah, we spent. I mean, we spent 20 years 45 00:02:39,570 --> 00:02:40,470 trying to get rid of them. 46 00:02:41,280 --> 00:02:44,490 Ya know, in the trenches, I mean, like, not just not just 47 00:02:44,490 --> 00:02:48,240 with we didn't just have kids we like had day I had to manage 48 00:02:48,240 --> 00:02:53,010 them on a daily basis. You know, now then they leave and you're 49 00:02:53,010 --> 00:02:56,820 like, Ah, crap. You're like should we play a board game? 50 00:02:57,090 --> 00:02:57,990 What exactly should 51 00:02:59,250 --> 00:03:00,870 the little shit I know. 52 00:03:02,430 --> 00:03:05,940 I understand. We have that crocheted on a pillow the little 53 00:03:05,940 --> 00:03:06,450 shifts a 54 00:03:06,450 --> 00:03:11,040 little shit. Hey, nice to see the pod verse livestream page. 55 00:03:11,040 --> 00:03:12,450 That was kind of a cool idea. 56 00:03:13,139 --> 00:03:15,389 It's a very cool idea. I mean, 57 00:03:15,480 --> 00:03:21,360 pod verse.fm/live streams I think let me see. Let's Yeah, it 58 00:03:21,360 --> 00:03:24,390 is and there we are. We're live it shows us live and it shows us 59 00:03:24,390 --> 00:03:29,460 pending before and it shows the 100% Retro stream live it shows 60 00:03:29,460 --> 00:03:32,910 curio caster live which is I didn't know Steven B had a 61 00:03:32,910 --> 00:03:33,540 stream 62 00:03:34,800 --> 00:03:38,730 I didn't I think that may be the in a stream I don't think that 63 00:03:38,730 --> 00:03:43,200 it actually him let me see because I leave it in it. I told 64 00:03:43,200 --> 00:03:46,230 you it is thinks that may be the in a struggle you better cut 65 00:03:46,230 --> 00:03:49,920 that off its inception. We're gonna we're gonna die. Melt the 66 00:03:49,920 --> 00:03:50,400 internet. 67 00:03:50,580 --> 00:03:53,130 Well, that's that's okay. So I have a good question about this 68 00:03:53,130 --> 00:03:57,780 right off the bat. Is this a value for value? Just check. 69 00:03:58,440 --> 00:04:00,840 There's a link to the live stream things it's like a May 70 00:04:00,840 --> 00:04:03,240 it's a first class citizen right there on the left hand side of 71 00:04:03,240 --> 00:04:04,290 pod verse that FM 72 00:04:04,500 --> 00:04:08,670 Oh, yeah, no, I know I saw that cool. But so Okay, so this curio 73 00:04:08,670 --> 00:04:10,800 caster stream now this is interesting, because I think it 74 00:04:10,800 --> 00:04:15,870 was Chad F who said to me hey, can you make a feed of the no 75 00:04:15,870 --> 00:04:19,770 agenda livestream? Like Well, that's cuz I did the feed for 76 00:04:19,770 --> 00:04:24,600 100% retro, which I love how curio casters promoting it a 77 00:04:24,600 --> 00:04:30,810 little little banner there had you heard it yet? And I said, 78 00:04:30,840 --> 00:04:32,640 Oh, that's a good idea. We should do that. And then as I 79 00:04:32,640 --> 00:04:35,820 was thinking about it, this is an interesting challenge. 80 00:04:36,330 --> 00:04:41,760 Because the no agenda stream is used for podcasts, and 81 00:04:41,760 --> 00:04:44,040 increasingly more live shows. I'd say I don't know what the 82 00:04:44,040 --> 00:04:46,830 ratio is. But there's a lot of people going live particularly 83 00:04:46,830 --> 00:04:49,560 since the lit tag came into existence, because there's 84 00:04:49,590 --> 00:04:53,130 boosting and there's interaction that's fun. And man that is it. 85 00:04:54,060 --> 00:04:57,270 Is a bowl for bowl who have you know, you trigger a certain 86 00:04:57,330 --> 00:05:00,720 amount of SATs and a goat sound goes off and No, that's, that's 87 00:05:00,720 --> 00:05:04,260 behind the behind the schemes, right? So yeah, Insanity is 88 00:05:04,260 --> 00:05:08,970 beautiful. But if no, I love this, I wish that was packaged, 89 00:05:08,970 --> 00:05:12,180 I wish I could use it. I mean, I love those things, those little 90 00:05:12,390 --> 00:05:15,090 breaks, I'd set it really high and like I want the bell to go 91 00:05:15,090 --> 00:05:19,290 off and fireworks and so all this stuff. But if we do it on 92 00:05:19,290 --> 00:05:22,950 the stream, and then people are listening to the no agenda 93 00:05:22,950 --> 00:05:28,710 stream, the feed that I set up, that mean, there is currently no 94 00:05:28,710 --> 00:05:35,580 way to dynamically switch the value block based upon metadata 95 00:05:35,580 --> 00:05:39,180 coming from the spring from the stream or something else. 96 00:05:39,450 --> 00:05:42,480 Because otherwise, it'll just go into whatever splits or whatever 97 00:05:42,480 --> 00:05:46,380 I determined. And I feel it'd be beautiful, if somehow we can, we 98 00:05:46,380 --> 00:05:50,580 can. It's kind of follows on what we talked about. On the 99 00:05:50,580 --> 00:05:56,460 last show where 100% retro, they want to be able to trigger pod 100 00:05:56,460 --> 00:06:00,270 ping events. But it's kind of more interesting, when you can 101 00:06:00,390 --> 00:06:04,710 trigger just based upon the metadata of the stream, a switch 102 00:06:04,710 --> 00:06:07,830 in the value block. I'm not sure where that happens or how that 103 00:06:07,830 --> 00:06:10,470 works. But you understand that the basic issue why it wouldn't 104 00:06:10,470 --> 00:06:15,390 be right for me to have an overall stream whereas it would 105 00:06:15,390 --> 00:06:19,890 value for value. And if people are listening and curio caster 106 00:06:19,890 --> 00:06:23,550 and the listening to you know, Jean and and Darren and they 107 00:06:23,550 --> 00:06:25,470 want to boost they'd be there wouldn't be boosting them 108 00:06:25,470 --> 00:06:27,840 directly. If that makes sense. Yeah. 109 00:06:28,140 --> 00:06:30,510 Yeah, I understand exactly what you say. This is the thing that 110 00:06:30,510 --> 00:06:33,060 I brought up last week that you told me was no problem because 111 00:06:33,060 --> 00:06:36,210 icecast had metadata and there's not a problem. 112 00:06:37,140 --> 00:06:40,830 Right? But I mean, it has metadata data, but how do we how 113 00:06:40,830 --> 00:06:43,680 do we catch it? How do we how do you dynamically change the 114 00:06:43,680 --> 00:06:45,120 block? How does all that work? 115 00:06:46,920 --> 00:06:50,460 I think that first thing wouldn't be pod pay, I mean, pod 116 00:06:50,460 --> 00:06:56,520 pain, makes sense that there would be a pod paying event that 117 00:06:56,520 --> 00:07:04,380 fires off. Like that we'll see. So what you're doing like this, 118 00:07:04,830 --> 00:07:07,590 the, I guess we get about it, let's let's let's back up here 119 00:07:07,590 --> 00:07:10,170 for a second. So there's like a bunch of different things that 120 00:07:10,170 --> 00:07:18,030 we need to talk about in around this entire idea of stream of 121 00:07:18,030 --> 00:07:22,800 feeds, with things in them that don't have items. So we won't 122 00:07:22,800 --> 00:07:23,010 have 123 00:07:23,790 --> 00:07:28,170 I have items now. I mean, I feel that you should have items. And 124 00:07:28,230 --> 00:07:31,590 I didn't do that initially with 100 with 100%. Retro and now 125 00:07:31,740 --> 00:07:34,890 they actually cutting promos every week. That's, you know, 126 00:07:34,890 --> 00:07:38,280 this week on 100%. Retro and I make that an item? 127 00:07:39,030 --> 00:07:41,970 Because I don't feel like you should have items. Okay, I 128 00:07:41,970 --> 00:07:43,080 disagree. I don't 129 00:07:43,080 --> 00:07:46,740 think I didn't put it in and it broke a lot of shit. So that was 130 00:07:46,740 --> 00:07:49,560 my that was my cue. It was like, Oh, I think I need items. 131 00:07:49,950 --> 00:07:53,400 Right. So let's go down there reference eight. So the I mean, 132 00:07:53,430 --> 00:07:57,030 the first I think we talked last week. I think Harv has right, I 133 00:07:57,030 --> 00:07:59,910 think the chat. I think we talked about somehow attaching a 134 00:07:59,910 --> 00:08:00,930 chapters file. 135 00:08:00,960 --> 00:08:04,350 Right? Right, right. Live chapters. Yes, we did talk about 136 00:08:04,350 --> 00:08:05,280 that. That would 137 00:08:05,280 --> 00:08:08,550 be one way to do it. But then again, I think if you if you if 138 00:08:08,550 --> 00:08:14,940 we if we, you know, rewind here, if we go back to the original 139 00:08:14,940 --> 00:08:21,480 concept of a live item, then the live item is not meant to 140 00:08:21,480 --> 00:08:26,040 specify a stream, it's meant to specify an event. Yeah, event 141 00:08:26,040 --> 00:08:31,950 would be the change of DJ or the change of show. So you would 142 00:08:31,950 --> 00:08:36,300 have a feed that would have multiple live items in it. All 143 00:08:36,300 --> 00:08:40,380 with pending, except one of them is live. And then the next one, 144 00:08:40,380 --> 00:08:44,760 that one rolls off in the and the next one goes live. So like 145 00:08:44,760 --> 00:08:48,120 your so that's the way it's supposed to work. 146 00:08:49,050 --> 00:08:51,300 And then the value block changes automatically. 147 00:08:52,050 --> 00:08:56,220 Right? So you would just need to send another pod ping to say 148 00:08:56,490 --> 00:09:00,570 live, and it would reference the same stream and then things 149 00:09:00,570 --> 00:09:04,200 would refresh writing in the value block would come through. 150 00:09:05,070 --> 00:09:08,700 My My head's exploding. That's very cool. We basically have all 151 00:09:08,700 --> 00:09:09,540 the bits there. 152 00:09:10,200 --> 00:09:13,140 Yeah, I think it's already it's the problems already solved. The 153 00:09:13,140 --> 00:09:17,820 issue is that nobody's doing a feed that looks like that. So we 154 00:09:17,820 --> 00:09:22,680 don't see. Like, like, we don't see it. Okay, so perception 155 00:09:22,680 --> 00:09:23,070 issue, 156 00:09:23,100 --> 00:09:30,360 right. So what would basically have to happen this case? So if 157 00:09:30,360 --> 00:09:35,940 I put in 24 hours of it, by the way, I have no commercial 158 00:09:35,940 --> 00:09:38,610 involvement. I just liked this guy. I've known him for 100 159 00:09:38,610 --> 00:09:42,600 years. He used to book me on gigs in Belgium, and, you know, 160 00:09:42,720 --> 00:09:44,790 he's just, he's just a dude trying to do something 161 00:09:44,790 --> 00:09:51,870 different. And I appreciate it. Could I would fill up 24 hours 162 00:09:51,870 --> 00:09:58,710 which would say be like five different blocks of, you know, 163 00:09:58,740 --> 00:10:01,260 or six different blocks of four or our or something like that 164 00:10:02,190 --> 00:10:06,330 and put them pending in the feed? The only thing that would 165 00:10:06,330 --> 00:10:09,150 then still because the feed will read them and we'll know okay, 166 00:10:09,150 --> 00:10:12,210 that one's dead. This is this is the next this is the next one, 167 00:10:12,210 --> 00:10:16,770 but somewhere it has to flip to live in the in the feed, so that 168 00:10:16,800 --> 00:10:21,180 that would be a logic that logic would be on the publishing side. 169 00:10:22,050 --> 00:10:25,710 Yes, that's right. You know, actually, I think, 170 00:10:25,740 --> 00:10:27,990 do you think Stephen B is already built it? I mean, he's 171 00:10:27,990 --> 00:10:30,870 getting just excuses about being cut up and stuff. But um, 172 00:10:30,930 --> 00:10:34,230 yeah, I mean, like he got, he got knifed in the gut 20 times 173 00:10:34,230 --> 00:10:34,860 or something like, 174 00:10:34,919 --> 00:10:38,159 Oh, my goodness, I'm so happy. He's okay. We got real quiet 175 00:10:38,159 --> 00:10:40,559 around him like, oh, no, this is not 176 00:10:40,560 --> 00:10:44,100 good. I'm looking at live on him real quick, because I find out 177 00:10:44,310 --> 00:10:45,840 if I remember, 178 00:10:46,050 --> 00:10:49,320 I find this incredibly exciting. By the way, I don't know why. 179 00:10:49,350 --> 00:10:54,060 But I just and I still am not getting Todd's new media show. 180 00:10:55,110 --> 00:10:56,430 Live pod pings. 181 00:10:57,900 --> 00:11:01,290 That assay this time we'll see. I'm trying to look and see what 182 00:11:01,290 --> 00:11:06,630 the attribute. Okay, so status start and end are all required. 183 00:11:08,940 --> 00:11:12,120 Which is real easy with a with a linear radio stream, you know 184 00:11:12,120 --> 00:11:15,030 exactly when it stops, which is kind of cool. 185 00:11:15,210 --> 00:11:17,400 And that could be CMS can just drop that thing. Well, 186 00:11:17,640 --> 00:11:21,210 you could also it could be automatically generated by their 187 00:11:21,210 --> 00:11:22,260 playout system. 188 00:11:23,160 --> 00:11:25,200 So yeah, just come just straight. And just to try and 189 00:11:25,230 --> 00:11:27,510 just translate that right into XML. Yeah, 190 00:11:27,570 --> 00:11:31,560 they have, they have a full full scheduling system. With all the 191 00:11:31,560 --> 00:11:33,300 metadata, everything's in there. 192 00:11:33,630 --> 00:11:36,300 See, this is what Sam says he needs for his river radios. 193 00:11:36,300 --> 00:11:39,540 Well, this would be the same exact scenario you just wrote, 194 00:11:39,540 --> 00:11:44,400 he just run that playout system into XML to generate the feeds, 195 00:11:44,940 --> 00:11:47,910 I use em air list. And that's something that's highly 196 00:11:47,940 --> 00:11:50,670 configurable, you can do script some stuff. So that might be 197 00:11:50,670 --> 00:11:51,390 some of the low. 198 00:11:51,870 --> 00:11:55,920 Well, okay, so this, but on the broader, sort of, like on the on 199 00:11:55,920 --> 00:11:59,640 the bigger view here, this brings up what we were talking 200 00:11:59,640 --> 00:12:07,080 about while ago, which is having a feed that has nothing in there 201 00:12:07,080 --> 00:12:13,800 has no items in it. And this this can, if you will permit me, 202 00:12:14,580 --> 00:12:20,370 I would like to also bring in a discussion of the podcast remote 203 00:12:20,370 --> 00:12:24,420 item tag, which is phase six. Yes, of course. Because I think 204 00:12:24,420 --> 00:12:27,090 they are tangential to one another. So the 205 00:12:27,120 --> 00:12:30,270 just don't use don't use big words like tangential me just 206 00:12:30,270 --> 00:12:32,580 hit me like I'm five please share. 207 00:12:35,280 --> 00:12:42,090 The podcast remote item tag is going to suffer suffer the same 208 00:12:42,330 --> 00:12:48,960 sort of limbo as as a feed as the live item. Because what you 209 00:12:48,960 --> 00:12:53,700 can imagine is a we'll go over remote on a second, but you can 210 00:12:53,700 --> 00:12:59,160 imagine is a feed and RSS 2.0 feed that has no item tags in 211 00:12:59,160 --> 00:13:05,670 it. And off the bat that is fine. According to the according 212 00:13:05,670 --> 00:13:09,000 to the RSS 2.0 spec, it's fine to have a chance to have an RSS 213 00:13:09,000 --> 00:13:13,200 feed versus 2.0 feed with just a channel that has zero items in 214 00:13:13,200 --> 00:13:13,830 it. It's just 215 00:13:13,860 --> 00:13:18,930 a parsing issue and decision that the client makes. Yeah, 216 00:13:18,960 --> 00:13:23,190 in the language says quote any the channel can have quote any 217 00:13:23,190 --> 00:13:29,850 number of items. Zero. Yeah, so that means if any number or zero 218 00:13:29,850 --> 00:13:31,200 is a number so we can have zero 219 00:13:31,980 --> 00:13:33,270 with a zero exist. 220 00:13:35,010 --> 00:13:39,540 Zero in Infinity do not exist. Yeah, but they are numbers. Oh. 221 00:13:40,920 --> 00:13:45,510 So this so it's valid XML it's valid RSS. And so that means 222 00:13:45,510 --> 00:13:50,970 it's it's okay. So if we put in a bunch if we have a feed like 223 00:13:50,970 --> 00:13:54,450 we're talking about with the 100% Retro a feed with a whole 224 00:13:54,450 --> 00:13:59,370 bunch of let's just say for the for our blocks has six live item 225 00:13:59,370 --> 00:14:02,940 tags in it that all rotate and move up as the thing goes 226 00:14:02,940 --> 00:14:06,990 through. That's fine. I just it like the problem is the podcast 227 00:14:06,990 --> 00:14:13,710 index website does not recognize is not displaying remote live 228 00:14:13,710 --> 00:14:17,070 items yet. So it looks like that it looks like the feed doesn't 229 00:14:17,070 --> 00:14:20,670 have anything in it. That's Yes, it does. So that's 230 00:14:21,000 --> 00:14:25,260 that's our course. Our parser decision Right exactly. In that 231 00:14:25,260 --> 00:14:27,900 in those lot of those live items are actually in the database. 232 00:14:27,900 --> 00:14:30,630 We're just nobody has a website. 233 00:14:30,690 --> 00:14:34,110 Nobody's right. Nobody has done that. No one cares. No one wants 234 00:14:34,110 --> 00:14:34,590 to help 235 00:14:35,220 --> 00:14:39,900 and lazy when when I say nobody that's a deflection that's 236 00:14:39,900 --> 00:14:44,190 pointing the finger at somebody else besides me. Because why 237 00:14:44,190 --> 00:14:47,010 would I ever do something like that? I'm telling you man, never 238 00:14:47,040 --> 00:14:49,020 never ever such a lazy guys are in here. 239 00:14:49,080 --> 00:14:51,180 So explain to me remote item again. 240 00:14:52,140 --> 00:14:58,740 Okay, so remote item. And he just, he just updated the spec 241 00:14:58,740 --> 00:15:06,240 for it. This is Alex's proposal remote item list, I will read 242 00:15:06,240 --> 00:15:10,710 from our read from this proposal. The intent of this 243 00:15:10,710 --> 00:15:14,280 proposal is to provide a tag that allows another item to be 244 00:15:14,280 --> 00:15:19,050 referenced without outright copying it. This shouldn't be an 245 00:15:19,050 --> 00:15:22,680 item in another feed entirely. So this is like a playlist. 246 00:15:23,310 --> 00:15:24,990 Gotcha. Yeah, 247 00:15:25,680 --> 00:15:27,900 that's, that's really what this is supposed to be, um, you can 248 00:15:27,900 --> 00:15:32,010 have a remote item. It's perfectly valid to have a remote 249 00:15:32,010 --> 00:15:36,750 item in a normal RSS feed that has items. But you can really 250 00:15:36,750 --> 00:15:40,170 see the power of this that that would in that scenario, me back 251 00:15:40,170 --> 00:15:44,280 up in that scenario, that would prevent you from doing things 252 00:15:44,310 --> 00:15:48,120 from hand to do funky stuff like air dropping another person's 253 00:15:48,120 --> 00:15:50,160 episode into your RSS feed. 254 00:15:50,249 --> 00:15:56,099 Right? So the the item to be inserted can be an item or even 255 00:15:56,099 --> 00:16:00,209 a channel can only be an item itself. 256 00:16:00,930 --> 00:16:06,480 Yes. So you would have an item in let's just say, Oh, perfect 257 00:16:06,480 --> 00:16:13,170 example here. Immediate show. The there live episode from 258 00:16:13,170 --> 00:16:17,940 Podcast Movement. James was a guest on that show. So he just 259 00:16:18,390 --> 00:16:22,590 used that episode, Todd said it's cool if you just use this 260 00:16:22,590 --> 00:16:24,630 episode and drop this enclosure into your foot 261 00:16:24,629 --> 00:16:27,479 whereas it would have been easy for him just to say remote item 262 00:16:27,509 --> 00:16:28,949 boom and points to that. 263 00:16:29,370 --> 00:16:32,880 points to the media show feed and that good and he doesn't 264 00:16:32,880 --> 00:16:38,100 have to drop another person's feed enclosure into his I mean 265 00:16:38,160 --> 00:16:40,080 feed item into his RSS feed. 266 00:16:40,680 --> 00:16:44,970 So what you automatically want at least what I automatically 267 00:16:44,970 --> 00:16:50,490 want? No, Nevermind. Nevermind. Um, oh, no, no, no, no, no, no, 268 00:16:50,760 --> 00:16:55,860 no, I'm just trying to think, Is this more? Because you're James 269 00:16:55,890 --> 00:17:00,720 is I'm just going to guess you would not use that in that case, 270 00:17:00,720 --> 00:17:04,410 because he wants his own branding around the episode he 271 00:17:04,410 --> 00:17:08,100 wants to explain in his words, what, what what this episode is 272 00:17:08,100 --> 00:17:12,540 about. And so in that case, you really only limited the mp3. So 273 00:17:12,540 --> 00:17:17,340 this seems this remote item seems more applicable to music 274 00:17:17,340 --> 00:17:21,420 for creating playlists than anything else. Because then then 275 00:17:21,420 --> 00:17:26,250 you really want to give the creator of that item. The full 276 00:17:26,250 --> 00:17:30,450 control over what how that surface is not just the the 277 00:17:30,450 --> 00:17:34,740 media file, but also the album art and transcripts, which might 278 00:17:34,740 --> 00:17:40,650 be lyrics, etc. That's where it seems like super important. 279 00:17:41,490 --> 00:17:43,770 Yes, I think you're exactly right. I think what, 280 00:17:43,860 --> 00:17:46,830 but Alex designed it with that in mind. Oh, yeah, 281 00:17:46,830 --> 00:17:50,130 of course. Yeah, it's exactly what it was for. The remote item 282 00:17:50,130 --> 00:17:55,530 has utility outside of a playlist context. But play with 283 00:17:55,530 --> 00:17:57,780 play lists are really where it's distinction. I 284 00:17:57,780 --> 00:17:59,940 think we should talk about it in the context of what it was 285 00:17:59,940 --> 00:18:03,450 designed for. So it's not about James dropping in an episode. 286 00:18:03,450 --> 00:18:07,410 It's about me putting together a mixtape from my lover Dave. 287 00:18:10,290 --> 00:18:17,910 Oh, sweet. Yeah, bro. is what I was doing. I was I was laying 288 00:18:17,910 --> 00:18:23,430 out the, the use case where everybody would be like, then I 289 00:18:23,430 --> 00:18:28,140 was gonna follow it up with with the right hook playlist. And 290 00:18:28,140 --> 00:18:28,800 everybody's gonna be like, 291 00:18:29,400 --> 00:18:33,090 Okay, well, you got me, you got me? Yes, I was there. I was 292 00:18:33,090 --> 00:18:35,520 there. I was there, I just jumped the gun. I'm sorry, I 293 00:18:35,730 --> 00:18:37,170 didn't realize there was a punch line. 294 00:18:38,340 --> 00:18:42,330 The the first section of the proposal is cross app playlists. 295 00:18:42,960 --> 00:18:46,530 And this is as this allows one to provide lists of other items, 296 00:18:46,530 --> 00:18:50,280 which one does not own copyright to, such as playlists, and 297 00:18:50,280 --> 00:18:54,300 various different types of audio video mediums, in combination 298 00:18:54,300 --> 00:18:56,760 with list mediums, and we'll talk about the rule, we'll talk 299 00:18:56,760 --> 00:19:00,540 about that too. One can use a theme made entirely of podcast 300 00:19:00,540 --> 00:19:03,540 remote item tags, to share them in a manner that allows 301 00:19:03,540 --> 00:19:05,700 applications to recognize them as playlists. 302 00:19:05,730 --> 00:19:10,050 So then you get into the reverse issue, are you ready? I'm gonna 303 00:19:10,050 --> 00:19:17,310 blow your mind. So let's, so let's say I can, I can envision 304 00:19:17,340 --> 00:19:21,450 a world where making playlists of remote items with a very, you 305 00:19:21,450 --> 00:19:25,230 know, simple tool becomes incredibly fun. I mean, I can 306 00:19:25,230 --> 00:19:28,560 see exactly how the app taps into the index. It's you know, 307 00:19:28,560 --> 00:19:31,710 you can even drag and drop and all this stuff is the whole 308 00:19:31,920 --> 00:19:35,790 experience is very clear in my mind, and that all under the 309 00:19:35,790 --> 00:19:40,170 hood is you basically building up a feed of remote items. So at 310 00:19:40,170 --> 00:19:45,960 a certain point, some people will be very influential. And 311 00:19:47,250 --> 00:19:51,840 and people will, they will want to take advantage of that. And I 312 00:19:51,840 --> 00:19:54,840 think other people want to get on their list and there can be 313 00:19:54,840 --> 00:19:59,670 an economy there. If we can figure out how do you get that 314 00:19:59,670 --> 00:20:05,730 list? Creator into the remote Item Value block so that they 315 00:20:05,730 --> 00:20:09,180 can get a maybe it's a maybe it's a slug, a placeholder. 316 00:20:09,450 --> 00:20:12,330 Something like that, you know, here's 5% from whoever puts us 317 00:20:12,330 --> 00:20:14,070 into a playlist. Does that make sense? 318 00:20:15,600 --> 00:20:20,910 Yeah. The that I knew you were gonna go there. 319 00:20:21,810 --> 00:20:25,170 And do you prep do you use? Do you lay awake at night and think 320 00:20:25,170 --> 00:20:26,760 about what does Adam going to say about? 321 00:20:29,070 --> 00:20:30,810 First I'm gonna suck him in when flame 322 00:20:31,800 --> 00:20:38,760 Boom, baby, boom, I'm gonna need a whip. I do have a whip. 323 00:20:39,570 --> 00:20:44,460 Sorry. Um, yeah. So. So that brings up a good. That brings up 324 00:20:44,460 --> 00:20:49,230 a good point. I think in the original spec. I don't see it in 325 00:20:49,230 --> 00:20:56,880 this one I may be overlooking, I think. Alex said that the value 326 00:20:56,910 --> 00:21:01,680 blocks that this should not contain value blocks. The remote 327 00:21:01,680 --> 00:21:09,120 item tag? Oh, why? And I think we'll see what here it is. An 328 00:21:09,120 --> 00:21:11,910 element defines a remote item one or more may be defined per 329 00:21:11,910 --> 00:21:16,500 channel. It refers to an item outside of the feed. This should 330 00:21:16,500 --> 00:21:21,330 only be used for list medium types. We'll see. This should 331 00:21:21,330 --> 00:21:24,990 not utilize any value related tags contained within the feed. 332 00:21:25,140 --> 00:21:27,690 Only the value tags on the referenced feed should be 333 00:21:27,690 --> 00:21:33,390 respected. So right, like, right. Yeah. So that you're 334 00:21:33,420 --> 00:21:36,120 that and then there's the problem. How do you how do you 335 00:21:36,120 --> 00:21:42,090 get the how do you get? How do you reward someone for creating 336 00:21:42,090 --> 00:21:42,900 a playlist? 337 00:21:45,150 --> 00:21:46,410 Yeah, no, no, because 338 00:21:46,439 --> 00:21:49,829 because there'll be the DJs of the future, you see, and we need 339 00:21:49,829 --> 00:21:52,679 to cut them in because then it incentivizes people to do all 340 00:21:52,679 --> 00:21:55,709 kinds of cool stuff and promotion around it. And that 341 00:21:55,739 --> 00:21:58,619 and, and, and the tide lifts all boats. 342 00:21:59,040 --> 00:22:01,620 See, here's my, here's my, 343 00:22:03,090 --> 00:22:07,770 you know, don't say fear. Don't say you can't handle that. 344 00:22:08,580 --> 00:22:11,700 Here is my anxiety, 345 00:22:12,810 --> 00:22:14,610 anxiety, oh, my god, okay, 346 00:22:14,670 --> 00:22:21,210 that's even worse than fear. So, in one sense, you can say that 347 00:22:21,270 --> 00:22:25,590 making playlists and becoming a playlist, Curator or creator, or 348 00:22:25,590 --> 00:22:30,750 whatever you want to call it is awesome. And that should be 349 00:22:30,780 --> 00:22:35,940 rewarded with value. But then in the other sense, it feels like 350 00:22:36,750 --> 00:22:42,870 That way lies madness, because you could imagine a popular 351 00:22:43,980 --> 00:22:50,820 playlist curator, be like throwing in an EPA in reference 352 00:22:50,820 --> 00:22:55,560 to a remote item to let's just say no agenda every single week. 353 00:22:56,220 --> 00:22:59,070 And they're getting a cut, even though they're not really doing 354 00:22:59,070 --> 00:22:59,850 any work. 355 00:23:00,390 --> 00:23:03,750 Oh, nobody. I disagree. I could not disagree with you more. 356 00:23:04,439 --> 00:23:07,949 I mean, like the fuse, let me have it. I see that as value. 357 00:23:08,100 --> 00:23:12,690 Thank you for exposing me to your audience. As you can see my 358 00:23:12,690 --> 00:23:17,880 remote item. Thing about Bob Snicket Joker. I have reserved 359 00:23:17,880 --> 00:23:22,290 5% for anyone in the value blog for anyone who puts this as a 360 00:23:22,290 --> 00:23:26,190 remote item into their feed. I don't know how that happens, but 361 00:23:26,190 --> 00:23:29,340 that's what I want. I see it as added value. Not not like 362 00:23:29,340 --> 00:23:32,970 they're not stealing from me. I want to I want to cut them in. 363 00:23:34,050 --> 00:23:35,580 Okay, just like an app. 364 00:23:37,110 --> 00:23:39,630 Okay. Oh, okay. Well, there that may be your that. 365 00:23:40,020 --> 00:23:42,840 I think you just have it as habit as a fee. 366 00:23:43,439 --> 00:23:47,879 stumbled upon the answer there. There could be a there can be an 367 00:23:47,879 --> 00:23:51,989 entry. That's a certain type of entry in the value block. This 368 00:23:51,989 --> 00:23:56,669 says this that is for this this for it just a placeholder and it 369 00:23:56,669 --> 00:24:02,279 says remote. I have no idea what to call this. But when you parse 370 00:24:02,279 --> 00:24:06,029 it, you say, Okay, this podcast podcaster has just specified 371 00:24:06,299 --> 00:24:11,159 that whenever somebody places a reference to their episode into 372 00:24:11,459 --> 00:24:17,699 a remote item list, and that's the source, they get X, whatever 373 00:24:17,699 --> 00:24:20,729 it is a value, whether it's a percentage or hardcoded amount 374 00:24:20,729 --> 00:24:25,589 or whatever, they get this so so then you it's almost like a 375 00:24:25,800 --> 00:24:31,680 variable. It's, it's what I call a slug, like insert your, your 376 00:24:31,680 --> 00:24:32,730 value block here. 377 00:24:33,750 --> 00:24:37,470 Okay, yeah, and then this is just like a place a placeholder 378 00:24:37,470 --> 00:24:40,860 that can be that can mean anybody that does this. 379 00:24:41,280 --> 00:24:45,090 Yes. Anyone who anyone who is using this as a remote remote 380 00:24:45,090 --> 00:24:50,430 item, you get 5%. And okay, so this is where it gets beautiful. 381 00:24:52,680 --> 00:24:56,040 One of the things I've been looking forward to and comics to 382 00:24:56,040 --> 00:25:00,780 Blogger brought this up is to have no agenda producers uh art 383 00:25:00,810 --> 00:25:06,000 producers, I want them when we check pick their art I want them 384 00:25:06,000 --> 00:25:10,470 to automatically be added into the value block into the into 385 00:25:10,470 --> 00:25:13,920 the split, that with get Albie addresses this is really easy 386 00:25:13,920 --> 00:25:17,640 every artist can can sign up for get Alby address. And what 387 00:25:17,640 --> 00:25:21,210 comics or Blogger did what I asked you said, on the Art 388 00:25:21,210 --> 00:25:23,340 Generator putting your profile there because I looked at the 389 00:25:23,340 --> 00:25:26,220 profile, I get the name, I have to put that into the credits, 390 00:25:26,700 --> 00:25:29,700 put your lb address in there and then boom, if you're chosen, 391 00:25:29,700 --> 00:25:34,560 I'll put you into the into the value block. So same way I'd 392 00:25:34,560 --> 00:25:40,650 love to. Maybe it's overkill, but it seems like there's an 393 00:25:40,650 --> 00:25:44,310 opportunity there. It's all dynamic stuff, basically. Right? 394 00:25:44,580 --> 00:25:49,500 So maybe we're just making life harder that way? Well, now, 395 00:25:49,680 --> 00:25:51,510 because I'm thinking I was thinking put a slug in for the 396 00:25:51,510 --> 00:25:55,020 art and then that fog it I'll do it myself. I'll copy paste. It's 397 00:25:55,020 --> 00:25:59,700 easy. Let's get the remote item thing fixed. And I'll copy paste 398 00:25:59,700 --> 00:26:00,930 until then. Well, 399 00:26:01,920 --> 00:26:04,710 I think what you're thinking, recursion as 400 00:26:04,710 --> 00:26:07,980 everyone always, yeah, that's what I'm looking for. 401 00:26:08,100 --> 00:26:10,560 It's like what we did with free material editor where you could 402 00:26:10,560 --> 00:26:12,750 put these variables in there. And you could just generate a 403 00:26:12,750 --> 00:26:13,950 template. Yeah, it would be 404 00:26:13,979 --> 00:26:17,069 which I still use twice a week, but what more than twice a week, 405 00:26:17,069 --> 00:26:18,029 several times a week. 406 00:26:18,630 --> 00:26:23,040 And so that's, that can be I think we could forge a way 407 00:26:23,040 --> 00:26:26,310 forward with this one once we get the remote item in place. 408 00:26:26,310 --> 00:26:28,530 Because this doesn't really have to be part of the remote item 409 00:26:28,530 --> 00:26:28,950 spec. 410 00:26:28,979 --> 00:26:32,249 Well, but here's here's the next thing because I think this flows 411 00:26:32,249 --> 00:26:37,679 into in a weird way. Podcast events. 412 00:26:39,510 --> 00:26:41,700 Now we're gonna have John Spurlock on next week to talk 413 00:26:41,700 --> 00:26:42,090 about that. 414 00:26:42,120 --> 00:26:45,090 Oh, good as well. Good. But I think Sam Sethi is doing some 415 00:26:45,090 --> 00:26:47,700 praise, like hinting about it on Potlatch. Oh, I got something 416 00:26:47,700 --> 00:26:49,200 special to talk about next week. 417 00:26:49,560 --> 00:26:52,680 Oh, cool. Yeah. All right. Yeah, let it 418 00:26:53,760 --> 00:26:57,300 slide it up, Sam. Okay, good. Well, I'm excited about the 419 00:26:57,300 --> 00:27:02,040 podcast events that I'm starting to think about what that can 420 00:27:02,040 --> 00:27:05,580 mean, I think it's gonna be very invigorating. And I certainly 421 00:27:05,580 --> 00:27:10,710 when it comes to audience doing stuff, and I see it from music, 422 00:27:10,710 --> 00:27:13,740 too, I see all kinds of great things that can come from it. 423 00:27:15,180 --> 00:27:17,730 And I want to thank all of the developers for creating all 424 00:27:17,730 --> 00:27:20,610 those great music apps. You really, really right on point. 425 00:27:23,610 --> 00:27:28,620 Okay, oh, music. Yeah. Well, we're not done with remote 426 00:27:28,770 --> 00:27:30,180 remote. I'm 427 00:27:30,180 --> 00:27:33,030 sorry. I'm sorry. I didn't I was like, Okay, done the cross that 428 00:27:33,030 --> 00:27:33,930 off the list. I was 429 00:27:33,959 --> 00:27:37,709 I'm going to come back to I'm going to come back to music mark 430 00:27:37,709 --> 00:27:45,659 my sheet. remote, remote, yes. Just due to flesh this out. The 431 00:27:45,659 --> 00:27:52,469 current is like, imagine a feed alright. Do you have pictured in 432 00:27:52,469 --> 00:27:53,729 your mind an RSS feed? 433 00:27:54,330 --> 00:27:57,240 You bet I dream of this all the time. 434 00:27:57,660 --> 00:28:02,040 Okay. Inside the channel, you know, you have your various 435 00:28:02,040 --> 00:28:05,490 things like title, description, Link, language generator, all 436 00:28:05,490 --> 00:28:09,690 that kind of stuff well, in the channel have have a playlist of 437 00:28:09,690 --> 00:28:13,110 what is going to be considered a playlist, which is, you know, 438 00:28:13,110 --> 00:28:18,510 just an XML feed full of remote items. You would also have a 439 00:28:18,510 --> 00:28:22,560 medium in there as well. A medium tag. Yeah. So that that 440 00:28:22,560 --> 00:28:26,730 gives you so here's, this is the other part of this issue. So 441 00:28:26,940 --> 00:28:33,360 part of the struggle the apps have is when they hit a feed 442 00:28:33,360 --> 00:28:39,210 that doesn't have any content in it. Like content being defined 443 00:28:39,210 --> 00:28:40,830 as item tags, ie an 444 00:28:40,830 --> 00:28:48,060 anchor show. Sorry, man, I just got to contribute to the 445 00:28:48,060 --> 00:28:49,740 conversation somehow. No, I 446 00:28:49,740 --> 00:28:53,790 endorsed this. By the way, what happened to anchor it? They 447 00:28:53,790 --> 00:28:56,760 don't know. Nobody even talks about it's like they don't 448 00:28:56,760 --> 00:28:57,150 exist. 449 00:28:57,180 --> 00:29:01,560 All they are is just a counter for the Spotify press release. 450 00:29:01,620 --> 00:29:03,750 How many? What's the number? What's the number anchor? 451 00:29:05,370 --> 00:29:06,420 Puppet puppet puppet? 452 00:29:07,350 --> 00:29:09,870 People what's what's the number what you got up there? I 453 00:29:09,870 --> 00:29:18,390 got it. That's all in it. Spotify doesn't even talk about 454 00:29:18,390 --> 00:29:24,450 anchor anymore. It's like they don't exist now. So the podcast 455 00:29:24,480 --> 00:29:27,600 like you can imagine that you would need or it would be very 456 00:29:27,600 --> 00:29:34,230 helpful to have a medium designated for this type of 457 00:29:34,230 --> 00:29:39,420 thing. So in this feed, the aggregator sees there's no items 458 00:29:39,420 --> 00:29:45,300 in this thing. So there are you know WTF. So then the chat the 459 00:29:45,300 --> 00:29:51,630 channel tag within this feed can have a medium of something like 460 00:29:51,960 --> 00:29:57,540 music L and the L means list. So there's a new set as part of the 461 00:29:57,540 --> 00:30:02,190 Poke podcast remote items spec There will also be an update to 462 00:30:02,190 --> 00:30:07,590 the podcast medium tag that corresponds to new types of 463 00:30:07,590 --> 00:30:13,440 mediums. And the new mediums would all be an L version of an 464 00:30:13,440 --> 00:30:18,540 existing medium type. So you can have, you would have music l 465 00:30:18,570 --> 00:30:23,790 podcast, l, audio book, l net, the elders means list. So this 466 00:30:23,790 --> 00:30:30,120 feed, if it has a medium type of music L is a playlist, a music 467 00:30:30,120 --> 00:30:36,990 playlist. App can expect when it parses this feed, it can expect 468 00:30:36,990 --> 00:30:41,820 to find a bunch of remote items in here that are music that are 469 00:30:41,820 --> 00:30:47,640 of the medium type of music. Okay. So that that's going to 470 00:30:47,640 --> 00:30:52,530 help because right now, right now, you just don't decorators 471 00:30:52,530 --> 00:30:54,840 that haven't any, it doesn't have anything to 472 00:30:55,110 --> 00:30:58,110 add does? No, it has no context it does. There's no way I can 473 00:30:58,110 --> 00:31:00,900 know because the medium tag is channel level, you need to have 474 00:31:00,900 --> 00:31:02,610 that item level for the remote item. 475 00:31:03,300 --> 00:31:11,970 Right? Yes. So that's, that's the idea there and then remote. 476 00:31:12,930 --> 00:31:18,690 So here's something that needs to be discussed. It feels like 477 00:31:18,720 --> 00:31:29,460 there needs to be a new medium of live, live brand and live L. 478 00:31:30,030 --> 00:31:35,340 So for a list of live remote items, you get a remote, remote 479 00:31:35,340 --> 00:31:40,050 item could reference a live item, which would be you maybe 480 00:31:40,050 --> 00:31:41,700 you have a playlist 481 00:31:41,729 --> 00:31:46,289 we are literally building an automated radio station playout 482 00:31:46,289 --> 00:31:49,619 system. This has literally been developed 483 00:31:50,189 --> 00:31:53,159 in detail. It's this is like a deep like the chef's have like 484 00:31:53,159 --> 00:31:57,419 deconstructed chicken salad. Yeah. deconstructed playoff 485 00:31:57,689 --> 00:32:03,059 system. Yeah. Okay. So that's what this mean? Do you agree? I 486 00:32:03,059 --> 00:32:03,689 mean, if it feels like, 487 00:32:04,320 --> 00:32:07,410 I'm with you, and I'm gonna keep going, keep going. Yeah. So 488 00:32:07,439 --> 00:32:11,279 if you have a list of, if you have a medium type of live L, 489 00:32:11,399 --> 00:32:13,619 then you have a list of risks. And then people could curate 490 00:32:13,619 --> 00:32:19,739 lists of lives of live streams that they listened to, or that 491 00:32:19,739 --> 00:32:23,159 are interesting, or related, or whatever, and share those things 492 00:32:23,159 --> 00:32:27,809 out. And then you can have, so it would be almost just like the 493 00:32:27,809 --> 00:32:32,699 pod verse.fm live streams page. But you can handle you can 494 00:32:32,699 --> 00:32:37,079 curate them yourself, and share them. And if you're, like we 495 00:32:37,079 --> 00:32:39,119 were talking about with the value stuff, if we can figure 496 00:32:39,119 --> 00:32:42,809 that part out the fun, find new live streams and get value for 497 00:32:42,809 --> 00:32:42,869 it. 498 00:32:42,900 --> 00:32:47,820 I mean, you can also see if I have this right, you could 499 00:32:47,820 --> 00:32:53,850 literally program a station, which consisted of individual 500 00:32:53,850 --> 00:32:59,340 entities wherever they are. And as long as they have, you know, 501 00:32:59,370 --> 00:33:05,970 a stream, you can literally be listening to one, one feed, and 502 00:33:05,970 --> 00:33:09,720 it'd be switching between these different live streams. Yeah, in 503 00:33:09,720 --> 00:33:14,940 real time. Yeah. That's pretty cool. That's pretty cool. 504 00:33:15,449 --> 00:33:20,579 Yeah, you can do and also it becomes like a, like a radio 505 00:33:20,579 --> 00:33:23,879 dial. I mean, like, you're you have a list. Yeah, 506 00:33:23,880 --> 00:33:28,170 you can just and you know, what, what a concept to do a dial 507 00:33:28,170 --> 00:33:31,230 instead of a list, just as a UI UX moment. 508 00:33:31,709 --> 00:33:34,949 Yeah. Yeah. What they call that skeuomorphism we can just go 509 00:33:35,249 --> 00:33:35,699 back to this. 510 00:33:36,810 --> 00:33:40,200 Yes, make it look like a radio dial, that'll work. 511 00:33:42,540 --> 00:33:45,600 In the, like, you can just literally, like pop back and 512 00:33:45,600 --> 00:33:49,710 forth between between radio stations in real time. On the 513 00:33:49,710 --> 00:33:51,060 podcast on the podcast 514 00:33:51,060 --> 00:33:54,630 app, you know, I gotta tell you that 100% Retro guys there 515 00:33:54,660 --> 00:33:58,770 beside themselves with with joy about this. Because, you know, 516 00:33:58,770 --> 00:34:02,220 some people are boosting to get a little boost here and there. 517 00:34:02,760 --> 00:34:06,360 They definitely see the stream stream numbers, you know, this 518 00:34:06,600 --> 00:34:11,130 is very few. But you know, and I see people even tweeting about 519 00:34:11,130 --> 00:34:15,060 it like this kind of cool, what the hell is this thing? So it is 520 00:34:15,060 --> 00:34:18,630 live and more as most of us live, some of it may be tract 521 00:34:18,630 --> 00:34:20,010 but it has a live feel to it. 522 00:34:21,690 --> 00:34:24,570 Are you going to put in are you going to rearrange the fate so 523 00:34:24,570 --> 00:34:26,940 that has a bunch of live items? Are you going to try that 524 00:34:26,970 --> 00:34:32,550 technique? Because it feels like your feed is just a mad 525 00:34:32,550 --> 00:34:35,130 laboratory of trying things for this. 526 00:34:35,250 --> 00:34:40,860 Well, that's my life. That's the lifestyle I've chosen. Stephen B 527 00:34:40,890 --> 00:34:49,410 he posted he posted something that some generator that is his 528 00:34:49,410 --> 00:34:52,500 brain is already working. He's listening so he'll come up with 529 00:34:52,500 --> 00:34:54,570 something because the whole thing is I just need a 530 00:34:54,570 --> 00:34:58,920 programming thing. You know, that just fires at certain times 531 00:34:58,920 --> 00:35:01,500 and then hits the pod during the live update, 532 00:35:03,000 --> 00:35:07,290 we'll discover and fades. Can it handle multiple live items? And 533 00:35:07,860 --> 00:35:10,080 yes, it can. Okay, I'm good. 534 00:35:10,920 --> 00:35:13,710 But I still need to hit turn it live, I still need to switch it 535 00:35:13,710 --> 00:35:15,180 live and republish the feed. 536 00:35:16,350 --> 00:35:19,740 That's right. It's right. Or 537 00:35:19,770 --> 00:35:25,440 orc. And that's something I would enjoy. Hey, I put curio 538 00:35:25,440 --> 00:35:29,340 caster and sovereign feeds in my splits. You know, maybe they'll 539 00:35:29,340 --> 00:35:33,270 have figured out a way to automate that for me. You know, 540 00:35:33,300 --> 00:35:36,030 it's, it's feed generation logic. 541 00:35:37,350 --> 00:35:40,860 Could you do it? And this is all off the rails, but could you do 542 00:35:40,860 --> 00:35:46,620 it from the icecast metadata? When you see that change, that 543 00:35:46,620 --> 00:35:48,180 can regenerate the feed? 544 00:35:48,210 --> 00:35:53,010 That was my that was my thinking of after the fact. Well, but But 545 00:35:53,040 --> 00:35:56,130 yeah, yeah, exactly. And I'm also thinking, it makes so much 546 00:35:56,130 --> 00:36:02,160 more sense. If we have an ingest format, then people who use 547 00:36:02,160 --> 00:36:06,540 these playout systems can just export, their their schedule. 548 00:36:07,860 --> 00:36:10,680 And it should, and it lines up, I mean, obviously, if they get 549 00:36:10,680 --> 00:36:12,720 out of sync, then you know, that's their problem. But the 550 00:36:12,720 --> 00:36:15,870 whole idea is that it stays in sync, and then it I mean, it 551 00:36:15,870 --> 00:36:18,240 could even trigger, it could even trigger the pod ping, I 552 00:36:18,240 --> 00:36:21,330 mean, we have a way to go. But we'll get to that source where I 553 00:36:21,330 --> 00:36:24,930 think it will just generate a feed, upload it that make the 554 00:36:24,930 --> 00:36:28,230 changes, upload it, pod, ping, boom, good to good to go 555 00:36:29,190 --> 00:36:32,130 to that. So the playout system, their playoff system, we just 556 00:36:32,160 --> 00:36:36,660 export, like a structured file, whatever, 557 00:36:36,660 --> 00:36:39,390 whatever we need. Yeah, whatever we need to ingest to make it 558 00:36:39,390 --> 00:36:39,870 work. 559 00:36:40,140 --> 00:36:41,400 Will it be JSON? 560 00:36:42,000 --> 00:36:47,430 I gosh, I hope so. But, but I'm also thinking, why couldn't the 561 00:36:47,430 --> 00:36:53,010 playout system just generate the RSS feed? FTP at pod ping? 562 00:36:53,700 --> 00:36:55,200 I don't know you know about those play out. 563 00:36:55,260 --> 00:36:58,560 I mean, do that. Why would they have all kinds of stuff like 564 00:36:58,560 --> 00:37:05,100 that built in these days? Consultant let me let me if only 565 00:37:05,100 --> 00:37:09,150 I knew a radio consultant. Yeah, I bet you don't know any of 566 00:37:09,150 --> 00:37:13,500 those. I do. James Cridland he's the radio consultants. Alright, 567 00:37:13,500 --> 00:37:16,830 James marching orders. Isn't he the radiologists? Let me see 568 00:37:17,400 --> 00:37:20,700 layer process strong. Oh, I would strongly recommend you do 569 00:37:20,700 --> 00:37:23,310 not use this configuration program will play out as running 570 00:37:23,310 --> 00:37:28,350 continue anyway. Yes, of course. Of course. What could go wrong? 571 00:37:28,350 --> 00:37:31,680 My pussy? Yeah, let me see remote controls. That's the MIDI 572 00:37:31,680 --> 00:37:37,980 remote control what else kind of remote control by okay. Let me 573 00:37:37,980 --> 00:37:43,170 see advanced it has these things. Let me see the logging 574 00:37:43,830 --> 00:37:47,190 database. I mean it has it has a whole database you know, you can 575 00:37:47,220 --> 00:37:49,860 you can get into a database and just export it 576 00:37:52,110 --> 00:37:56,220 well, that I mean, that's just Well, there you go. I mean, I 577 00:37:56,220 --> 00:37:57,300 mean, everything's there. 578 00:37:57,990 --> 00:38:01,980 Yeah, you couldn't oh goodness nearly done in there last year. 579 00:38:02,070 --> 00:38:06,180 merilis. So you can do you can connect to an iTunes database 580 00:38:06,210 --> 00:38:09,570 you can connect to Sam broadcaster V four, which then 581 00:38:09,570 --> 00:38:12,420 will pass your meta that mean that's that's like an ice cast 582 00:38:12,420 --> 00:38:16,590 streamer. So you can then stream the metadata from your system. 583 00:38:16,920 --> 00:38:24,180 You can just a script whatever that is. Anyway, I get some info 584 00:38:24,210 --> 00:38:24,960 this 585 00:38:25,109 --> 00:38:28,199 Yamo Eric PP No, no, no, I handle please. 586 00:38:29,520 --> 00:38:33,540 Discard all changes and close. Yes. Okay. Does this. Oh shit. 587 00:38:33,570 --> 00:38:40,200 Oh, fuck. Honestly, do I spell Dr. Pepper hora. Oh, that's 588 00:38:40,200 --> 00:38:41,820 really bad. mush. Oh, no 589 00:38:41,850 --> 00:38:46,110 chips. Yeah, it's in the keyboard. Oh, oh, no. Disaster. 590 00:38:46,200 --> 00:38:56,280 Yeah, hold on. Oh, I could doodle do. Oh, no. Oh, no. Oh, 591 00:38:56,280 --> 00:38:58,200 no. Oh, no. Oh, no. 592 00:39:06,540 --> 00:39:08,430 Oh, did you like that was that was a good? 593 00:39:10,380 --> 00:39:12,060 I mean, I thought I was gonna have to play the show out 594 00:39:12,060 --> 00:39:12,540 myself. 595 00:39:14,490 --> 00:39:16,530 Let me just rub this. Okay, so 596 00:39:17,760 --> 00:39:19,500 yeah, I think rub it out. Just rubbish. I'm 597 00:39:19,500 --> 00:39:23,610 just rubbing one out here. Dave. Give me a second. The show is 598 00:39:23,610 --> 00:39:30,090 off the rails. And we have a heart out. The other day I 599 00:39:30,090 --> 00:39:33,750 spilled. I broke a wineglass and it spilled over it and it was 600 00:39:33,750 --> 00:39:36,840 kind of made my midi controller a little wonky. 601 00:39:37,740 --> 00:39:38,880 Built it in the keyboard. 602 00:39:39,270 --> 00:39:44,040 You both Yeah. Oh, that's very keyboard and I have backups if I 603 00:39:44,040 --> 00:39:45,180 need but we're 604 00:39:45,180 --> 00:39:47,970 gonna have to read it. We're gonna have to take away your 605 00:39:47,970 --> 00:39:49,380 drink privileges within the 606 00:39:50,220 --> 00:39:53,250 my own damn fault. I was horsing around I shouldn't have done I 607 00:39:53,250 --> 00:39:56,010 have special spots for drinks. It's almost like a cup holder. 608 00:39:56,010 --> 00:39:59,970 But do I use it new love course now. Okay, let me see you soon. 609 00:40:00,000 --> 00:40:04,470 scissors. Okay, we're back. We're back in business. So yeah, 610 00:40:04,470 --> 00:40:08,400 okay, so that's so that's something that can be worked on. 611 00:40:10,500 --> 00:40:16,440 I think we need to get the remote the remote item squared 612 00:40:16,440 --> 00:40:19,590 away and that'll start to play out and we'll we'll get there 613 00:40:19,590 --> 00:40:20,550 when it's time right? 614 00:40:22,530 --> 00:40:25,620 Yeah, was that a Diet Dr. Pepper no straight up Dr. Pepper the 615 00:40:25,620 --> 00:40:26,610 real things straight. 616 00:40:26,610 --> 00:40:29,460 It was a small can one of those little minis? Because I don't 617 00:40:29,820 --> 00:40:31,950 like a 10 ounce or something? Yeah, I don't really want the 618 00:40:31,950 --> 00:40:35,940 poison. But to do this show, you know, I'm stoned all day like 619 00:40:35,940 --> 00:40:36,840 I'm gonna go sugar on 620 00:40:37,350 --> 00:40:41,010 the phenol kid in neuro whatever. Yes, yeah. Yeah. So we 621 00:40:41,010 --> 00:40:44,520 can do that. Yeah, that's that. One interesting thing about this 622 00:40:44,550 --> 00:40:49,920 is that in we're gonna see more of this over time, I believe. 623 00:40:49,920 --> 00:40:53,580 And so we've got to figure out how to go down this road at some 624 00:40:53,580 --> 00:41:00,330 point. Is the podcast good? So the way these remote items are 625 00:41:00,780 --> 00:41:01,740 referenced? 626 00:41:02,520 --> 00:41:05,850 Oh, yeah, I have your own. I have a bad good. 627 00:41:06,840 --> 00:41:09,270 Do you? Oh, yeah. You're in Korean. The keeper? 628 00:41:09,480 --> 00:41:11,220 I don't know how that happened. But yeah. 629 00:41:12,360 --> 00:41:20,070 So you the what a remote item looks like, is it is a it's got 630 00:41:20,220 --> 00:41:25,440 three attributes. Two of which are required ones. One's 631 00:41:25,440 --> 00:41:31,230 optional. So the it's got the item good attribute, which is 632 00:41:31,230 --> 00:41:36,120 the GU ID from the feed that is being referenced. That's fine. 633 00:41:36,630 --> 00:41:41,400 For the most part, because you know, that's the I think, as an 634 00:41:41,400 --> 00:41:44,250 industry, we've pretty much with Apple coming on board to require 635 00:41:44,250 --> 00:41:48,660 Gu ID now EPS enclosure episode level Gu IDs. I mean, you can 636 00:41:48,660 --> 00:41:50,880 just say, Well, I mean, if you're not putting goods in your 637 00:41:50,880 --> 00:41:55,380 feed, you know, you don't get to play at the party. Right? The 638 00:41:55,380 --> 00:41:59,550 feed Gu ID is the one that's going to have to be dealt with 639 00:42:00,000 --> 00:42:02,790 over time, which in the feed good is a reference to the 640 00:42:02,790 --> 00:42:05,130 podcast co lon Gu ID tag 641 00:42:06,750 --> 00:42:10,140 that thank you for doing kolam. There's nothing in Britain. 642 00:42:12,900 --> 00:42:19,740 So the podcast guid tag is actually been adopted quite a 643 00:42:19,740 --> 00:42:22,770 bit. I mean, it's getting some reach. So 644 00:42:23,520 --> 00:42:27,660 it's really, it really needs to be promoted as the ISBN of 645 00:42:27,660 --> 00:42:30,780 podcasting. And people should do this. I mean, and then we can 646 00:42:30,780 --> 00:42:33,390 market it that way, people will say, Oh, I really need to get 647 00:42:33,390 --> 00:42:38,430 that. So that also means we need to surface easy to go in and say 648 00:42:40,170 --> 00:42:42,150 what is this podcast good. 649 00:42:43,470 --> 00:42:47,460 In that that's where I'm headed. So what? That's what there's 650 00:42:47,460 --> 00:42:52,200 already in the API, an API, there's already a podcast by 651 00:42:52,200 --> 00:42:58,620 GUID. API endpoint that will give you that result. But it 652 00:42:58,620 --> 00:43:04,140 feels like there needs to be it needs to be something. This 653 00:43:04,140 --> 00:43:09,330 almost needs to be a stand alone type of thing. Where you can 654 00:43:09,330 --> 00:43:16,230 just ask, you know, ask a where you can easily just grab a feed 655 00:43:16,230 --> 00:43:19,950 URL of a Gu ID and not even not have to necessarily use an API 656 00:43:19,950 --> 00:43:23,550 call. I mean, it'll ultimately it ultimately everything's sort 657 00:43:23,550 --> 00:43:24,750 of an API call, right? So 658 00:43:24,750 --> 00:43:29,310 in a script, you just say, podcast GUID, this, and then 659 00:43:29,340 --> 00:43:33,180 that, and then the script knows how to get that information? 660 00:43:33,480 --> 00:43:35,490 Yeah, yeah. That's one of the things it's really just for 661 00:43:35,490 --> 00:43:38,430 developers, because you're lazy to type all the information and 662 00:43:38,430 --> 00:43:41,370 you just want to token Am I right? Am I right? 663 00:43:41,370 --> 00:43:44,880 Yeah, yeah. So it could be something as easy as a service, 664 00:43:45,480 --> 00:43:52,620 where that's called like, I don't know. That's good podcast, 665 00:43:52,650 --> 00:43:57,750 Gu id.net, I don't know. And then you just give it in a slash 666 00:43:57,750 --> 00:44:00,960 into GUID. And it just returns nothing but the end, it just 667 00:44:00,960 --> 00:44:05,100 returns the feed URL. Like, like some simple result, like a 668 00:44:05,100 --> 00:44:11,160 resolver, not an API call. I feel like that's probably the 669 00:44:11,160 --> 00:44:14,610 way to go with this thing. Because the GU IDs are going to 670 00:44:14,610 --> 00:44:17,970 become more of a thing. And then we're going to start referencing 671 00:44:18,000 --> 00:44:20,520 them more in these tags. 672 00:44:20,550 --> 00:44:22,860 So are we going to be the centralized resolver? 673 00:44:23,850 --> 00:44:26,550 Well, I don't want to be the centralized resolver owner on a 674 00:44:26,550 --> 00:44:32,190 server but I mean, we could set up some sort of system like I 675 00:44:32,190 --> 00:44:34,860 don't know if clubs or workers are single, whatever 676 00:44:34,860 --> 00:44:38,940 we do, whatever we do before we make any decisions. Let's make 677 00:44:38,940 --> 00:44:40,440 sure we run it past GG 678 00:44:43,950 --> 00:44:49,530 Yes, yes, God knows. If you don't, there's hell to pay. 679 00:44:51,030 --> 00:44:53,520 That's my one joke for today about it. Okay. 680 00:44:54,900 --> 00:45:00,630 Yes, we must. It must be fully decentralized. Whatever in 681 00:45:00,630 --> 00:45:03,330 whatever way that that means whatever week way that that 682 00:45:03,330 --> 00:45:07,500 means. So anyway, I don't know about that. I'm just it feels 683 00:45:07,500 --> 00:45:09,180 like I would like to hear 684 00:45:09,209 --> 00:45:12,179 here's why. here's and here's a weird thing just just because 685 00:45:12,179 --> 00:45:21,629 I'm weird could I make my my podcast good? My lightning node 686 00:45:21,629 --> 00:45:24,359 or my bitcoin wallet? Address? 687 00:45:27,630 --> 00:45:33,510 Not the cording taka unit and the year on let me look at the 688 00:45:33,510 --> 00:45:34,200 spec Arnie 689 00:45:36,240 --> 00:45:40,230 does it have to be a certain number of numbers or patches or 690 00:45:40,290 --> 00:45:41,010 salted? 691 00:45:41,760 --> 00:45:45,270 It's it's supposed to it's supposed to be a V five Gu ID 692 00:45:46,050 --> 00:45:48,150 excuse me a V five UU ID? 693 00:45:49,710 --> 00:45:53,220 Oh, you know, you the composite of a UU ID is different from 694 00:45:54,030 --> 00:45:55,650 from a cryptographic address. 695 00:45:55,920 --> 00:45:59,310 Right. Yeah. Yeah, it looks a lot different format. And I 696 00:45:59,310 --> 00:46:02,940 think I'm afraid that if you did that, it's not going to follow 697 00:46:02,940 --> 00:46:06,330 the format, then it may get cut off in certain databases. Okay. 698 00:46:07,530 --> 00:46:10,080 Yeah, I don't think it's probably just better not to do 699 00:46:10,080 --> 00:46:15,630 that. Good. Yeah. So I'm thing is, I think a result, I would 700 00:46:15,630 --> 00:46:19,650 like to know if other people think a resolver of some sort is 701 00:46:19,650 --> 00:46:22,080 probably the way to go. And then how to properly properly go 702 00:46:22,080 --> 00:46:24,720 about that in a way that we liked. 703 00:46:24,720 --> 00:46:28,800 I really liked the idea. And I think it's critical that that we 704 00:46:28,800 --> 00:46:33,720 get that up and running. Because that is when you do that. Then 705 00:46:33,720 --> 00:46:41,190 you can also have a GUID for albums, songs. These are all 706 00:46:41,220 --> 00:46:44,280 these are all important things to have that people can confine 707 00:46:44,280 --> 00:46:46,350 them based upon that detail. 708 00:46:47,220 --> 00:46:53,010 Yeah. There's enough there's enough spread. Now. Buzzsprout 709 00:46:53,010 --> 00:47:00,090 includes Gu IDs, who was cast dos includes goods and all their 710 00:47:00,090 --> 00:47:04,860 feeds. I have to look at the list. But it's quite it's, 711 00:47:05,190 --> 00:47:08,640 there's quite a lot. So I feel like we're there. And we're 712 00:47:08,640 --> 00:47:11,190 ready to sort of like flip the switch and take the next step on 713 00:47:11,190 --> 00:47:13,890 that. And then it will I mean, we'll have to because in remote 714 00:47:13,890 --> 00:47:17,850 item will need it right. As long as we put it on. As long as 715 00:47:17,850 --> 00:47:20,970 whatever form it takes is on hive, then there won't be any 716 00:47:21,180 --> 00:47:22,110 push back ever. 717 00:47:22,170 --> 00:47:25,080 So we're good to go. Yeah. 718 00:47:28,440 --> 00:47:31,860 I don't want to so funny. Okay, so I think we're good on remote. 719 00:47:31,860 --> 00:47:34,350 And I think everybody probably understands what that does. 720 00:47:34,980 --> 00:47:38,520 Yeah, I like it. I really like it. These are exciting things. 721 00:47:38,520 --> 00:47:41,340 So how does this move forward? Just this is the 722 00:47:42,930 --> 00:47:44,340 basics just progresses. 723 00:47:44,370 --> 00:47:46,260 Okay, good. Good. Yeah. 724 00:47:46,920 --> 00:47:51,450 It's on it's on the list. And we're so in Well, one of the 725 00:47:51,450 --> 00:47:57,570 things Alex is finishing up the, the 2.0 version of pot of the 726 00:47:57,570 --> 00:48:00,030 pod paying hive writer, and that's going to have this stuff 727 00:48:00,030 --> 00:48:06,060 in it through the socket. So we can we can specify these 728 00:48:06,060 --> 00:48:08,370 mediums, these list of mediums and that kind of thing as part 729 00:48:08,370 --> 00:48:12,000 of the schema. That'll be in there. So we'll be good to go. 730 00:48:12,270 --> 00:48:13,710 Nice. Yeah. 731 00:48:15,870 --> 00:48:17,940 I don't want to keep going if you've got some you got anything 732 00:48:17,940 --> 00:48:20,910 else that you want to insert? I don't want to just steamroll. 733 00:48:21,780 --> 00:48:29,340 Just Just go on a different topic for a minute. Go for the 734 00:48:29,340 --> 00:48:32,490 squad cast patent, I think you and I have different ideas about 735 00:48:32,490 --> 00:48:34,710 that. I wanted to see where where you were at. 736 00:48:36,930 --> 00:48:41,730 I just don't like it. I don't like it feels and I could be 737 00:48:41,730 --> 00:48:44,310 completely wrong. I don't know this. I don't know those guys at 738 00:48:44,310 --> 00:48:47,190 all. Other than Harry Duran, I know him. I was on his show. And 739 00:48:47,190 --> 00:48:48,930 he seems like a really great guy. I think he's like an 740 00:48:48,930 --> 00:48:52,170 advisor or something. But I don't really know anybody else 741 00:48:52,170 --> 00:48:52,650 there. 742 00:48:52,680 --> 00:48:56,130 Well, let me ask you this. How did you interpret what you read 743 00:48:56,130 --> 00:48:56,760 about it? 744 00:48:58,470 --> 00:49:07,350 I interpreted it to be that they were trying to hit a broad a 745 00:49:07,350 --> 00:49:13,410 patent for something broad, that would be a natural evolution of 746 00:49:13,410 --> 00:49:19,590 any product like that, in order to carve out some mark in order 747 00:49:19,590 --> 00:49:21,840 to code like basically put a line in the sand for their 748 00:49:21,840 --> 00:49:25,800 market share, because that's a crowded market. There's a lot of 749 00:49:25,800 --> 00:49:29,220 people there's a lot of players in there like Riverside, clean 750 00:49:29,220 --> 00:49:30,660 feed shoutcast 751 00:49:30,720 --> 00:49:32,940 Did you have an opportunity to read the patent? 752 00:49:33,540 --> 00:49:38,220 I read I read the the first whatever you call it, like the 753 00:49:39,030 --> 00:49:43,560 the initial sizes, summary, probably summary, or any 754 00:49:43,560 --> 00:49:47,310 reasoning that he was like giving us like something like 755 00:49:47,310 --> 00:49:50,610 more broadly. And I can't remember the exact wording and 756 00:49:50,610 --> 00:49:54,480 that's what gave me pause. I was like, Oh, wait, whatever the way 757 00:49:54,480 --> 00:49:57,810 that it was worded made me think, Oh, they're going to try 758 00:49:57,810 --> 00:50:02,370 to come after anybody who He uploads parts of a file and 759 00:50:02,370 --> 00:50:05,280 stitches them together later in a way that doesn't lose the 760 00:50:05,280 --> 00:50:10,890 timestamping. Like, well, I mean, that just, that's the 761 00:50:10,890 --> 00:50:11,940 word, but he's had to do that. 762 00:50:12,270 --> 00:50:17,310 So the way I read it was, here's these problems. People have 763 00:50:17,310 --> 00:50:21,570 solved these problems in certain ways or not. We have solved 764 00:50:21,570 --> 00:50:24,120 these problems in this particular way. And we're 765 00:50:24,120 --> 00:50:29,310 patenting our solution. I don't think you can, you can patent 766 00:50:30,720 --> 00:50:35,040 the time to drift. Because there's too much prior art and 767 00:50:35,040 --> 00:50:39,150 people have done it. But just like Apple, they didn't know 768 00:50:39,150 --> 00:50:44,550 Apple patented, have passed podcast patents they patented. I 769 00:50:44,550 --> 00:50:52,710 think their namespace so. And I read through all the blog posts 770 00:50:52,710 --> 00:50:56,790 from squad cast and in what they were doing, and it was it seemed 771 00:50:56,790 --> 00:51:00,690 to me more really about the actual technology that they've 772 00:51:00,720 --> 00:51:04,500 or the algorithm or whatever they've developed than anything 773 00:51:04,500 --> 00:51:10,320 else, because it it, their way of doing it is apparently very 774 00:51:10,320 --> 00:51:14,280 lightweight. And now you can do a lot more on mobile and other 775 00:51:14,280 --> 00:51:16,710 things that you couldn't do before but I did not read that 776 00:51:16,710 --> 00:51:19,770 they were patenting the process itself. 777 00:51:22,170 --> 00:51:26,280 says in the description, it says the invention in one form is 778 00:51:26,280 --> 00:51:29,460 directed to a method that ensures that recorded all the 779 00:51:29,460 --> 00:51:31,200 Indian males are always except a 780 00:51:31,200 --> 00:51:34,860 method a method. Yeah, not the method a method. 781 00:51:36,420 --> 00:51:42,600 Okay, and so it gets in, save it has saved the file. Okay. Well, 782 00:51:42,600 --> 00:51:46,350 I haven't read step by step through this. And I may just be 783 00:51:46,350 --> 00:51:48,210 ignorant about what can be. 784 00:51:48,540 --> 00:51:51,840 And I understand that the knee jerk reaction, I'm not I don't, 785 00:51:51,990 --> 00:51:55,500 I don't participate in the patent system. But I'm certainly 786 00:51:55,500 --> 00:51:59,820 not anti patent, I feel I am anti the abuse of the patent 787 00:51:59,820 --> 00:52:03,360 system, which is what you were referring to. But my initial 788 00:52:03,360 --> 00:52:07,350 reaction to that, I was actually surprised when I saw all the 789 00:52:07,350 --> 00:52:11,520 posts about fuck these guys. I hate patent trolls like hohoho. 790 00:52:11,910 --> 00:52:15,270 Have we read this thing? And it to me, it was just like, Okay, 791 00:52:15,270 --> 00:52:18,630 we figured out some some new ingredient of how to do 792 00:52:18,630 --> 00:52:22,380 something that other people are doing, but our way it no one has 793 00:52:22,380 --> 00:52:25,020 done. We want to patent that because we want to take 794 00:52:25,020 --> 00:52:28,200 commercial advantage of that moving forward. But I didn't 795 00:52:28,200 --> 00:52:31,740 really get any of the feeling that they're out to potentially 796 00:52:31,740 --> 00:52:35,280 protect their turf or squash others. It seems like this is an 797 00:52:35,280 --> 00:52:39,030 innovation, at least what I read that it's an innovation on what 798 00:52:39,030 --> 00:52:40,980 is currently being done which you can patent. 799 00:52:42,660 --> 00:52:46,320 So I guess one, I guess one way to think about is what? Why 800 00:52:46,320 --> 00:52:48,870 would you in this? I'm not saying this the right way. But 801 00:52:48,960 --> 00:52:57,720 why would you patent something where you can't know if the 802 00:52:57,720 --> 00:52:59,880 patent is being violated or not? 803 00:53:00,750 --> 00:53:03,510 What do you mean that this is exactly what patents are about? 804 00:53:03,510 --> 00:53:06,840 Look at Silicon Valley, look at the look at the lawsuits that 805 00:53:06,840 --> 00:53:10,410 did go back 10 years you used our code here, you use their 806 00:53:10,410 --> 00:53:13,560 code there. That, of course is why I don't use the patent 807 00:53:13,560 --> 00:53:14,100 system. 808 00:53:15,690 --> 00:53:19,020 Well, I guess what I'm saying is like what? Coke, okay, so in 809 00:53:19,020 --> 00:53:22,950 this instance, if they've patented, if What if what 810 00:53:22,950 --> 00:53:28,320 they've patented is a specific algorithm like, like step one, 811 00:53:28,350 --> 00:53:32,400 do this, do you know, do this function on this part part of 812 00:53:32,400 --> 00:53:35,670 the audio to do to look at this step two, blah, blah, blah. So 813 00:53:35,670 --> 00:53:39,390 if, if, if that's if they've essentially patented, what will 814 00:53:39,660 --> 00:53:47,970 what amounts to pseudo code on how to do a thing? Then how can 815 00:53:48,990 --> 00:53:53,430 the only thing the only way they can know when they see let's 816 00:53:53,430 --> 00:53:56,250 just say that clean feed does the same at some point in the 817 00:53:56,250 --> 00:54:00,750 future. Also, on the fly, upload audio to a Citroen to back to 818 00:54:00,750 --> 00:54:05,190 the mothership, and stitches it together, then squad cast is 819 00:54:05,190 --> 00:54:10,530 going to have to sue clean feed in order to get discovery on 820 00:54:10,530 --> 00:54:14,070 whether or not their algorithm is the same as squad cast, which 821 00:54:14,070 --> 00:54:14,220 is 822 00:54:14,220 --> 00:54:18,600 a very risky business to be in. Because if you if you have a 823 00:54:18,600 --> 00:54:22,530 frivolous claim, then you can wind up paying for everything 824 00:54:22,530 --> 00:54:25,560 first off the bat. And then there could be a counterclaim, 825 00:54:25,560 --> 00:54:28,140 if there's any suspicion that you were doing this on anti 826 00:54:28,140 --> 00:54:29,340 competitive grounds. 827 00:54:30,690 --> 00:54:34,620 Okay, all right. So that's so would that be what it would be? 828 00:54:34,650 --> 00:54:37,080 will students be anti considered anti competitive? 829 00:54:38,190 --> 00:54:42,600 What if if, if they if they just start suing people look if you 830 00:54:42,630 --> 00:54:46,020 if you sue people and you're wrong, you definitely have to 831 00:54:46,020 --> 00:54:46,890 pay the cost? 832 00:54:47,940 --> 00:54:51,210 Right off the bat, right? Yeah, pay for the damages or whatever. 833 00:54:51,240 --> 00:54:51,630 Well, you 834 00:54:51,630 --> 00:54:55,740 got you got to pay lawyers fees, court fees, and then that can be 835 00:54:56,040 --> 00:54:59,550 that can be inconvenience fees, and then there could be Hey, 836 00:54:59,550 --> 00:55:02,820 wait a minute. Do you guys want to after us for no reason, I 837 00:55:02,820 --> 00:55:06,840 think really what they're they're trying to protect. And I 838 00:55:06,840 --> 00:55:10,170 don't know, I don't use squad cast, I use clean feet, I like 839 00:55:10,170 --> 00:55:13,440 clean feet, I certainly wouldn't want anyone to have any, any 840 00:55:13,440 --> 00:55:16,920 issues. I just think that they have created something that 841 00:55:16,920 --> 00:55:20,040 they're saying Holy crap, this is groundbreaking look at what 842 00:55:20,040 --> 00:55:23,430 we can do in a lightweight and even mobile environment with 843 00:55:23,430 --> 00:55:29,430 this stuff. And there's very, very specific about about that. 844 00:55:30,360 --> 00:55:33,630 And so they want to protect their competitive upside, which 845 00:55:33,630 --> 00:55:38,760 I think is marginal. Now, it could also be, just to be honest 846 00:55:38,760 --> 00:55:43,620 about it, that they're raising money. And, and you know, the 847 00:55:43,620 --> 00:55:47,010 final thing they had to do was show some patented technology. 848 00:55:47,160 --> 00:55:50,670 This is not uncommon. Yeah, this is not uncommon. Oh, look, we 849 00:55:50,670 --> 00:55:54,240 got we got into it. So they have some patented technology. And 850 00:55:54,240 --> 00:55:57,060 now yeah, now you're better for some investment. I mean, these, 851 00:55:57,150 --> 00:56:01,320 there's a lot going on. I just, I'm a conspiracy therapist, and 852 00:56:01,320 --> 00:56:03,690 when I see one where I just think, you know, everyone's kind 853 00:56:03,690 --> 00:56:06,510 of going off on this. And let me see what's happening. I just 854 00:56:06,510 --> 00:56:06,720 felt 855 00:56:06,720 --> 00:56:08,700 like you want to look at the other side, you want to look at 856 00:56:08,700 --> 00:56:11,520 the other side, I always try to look at all sides. Yeah, 857 00:56:11,520 --> 00:56:14,940 whenever it'd be, you're essentially a betting line. When 858 00:56:14,940 --> 00:56:16,500 everything's on one side, you look at the other 859 00:56:16,950 --> 00:56:19,920 100% That's the gig. 860 00:56:21,600 --> 00:56:24,840 No, I think that's I think that's fair. I mean, it you 861 00:56:24,840 --> 00:56:27,540 know, I think I grew up, I grew up in the open source, 862 00:56:27,840 --> 00:56:31,350 generation of Sun Microsystems coming after everybody has a 863 00:56:31,350 --> 00:56:35,640 patent troll. Oh, sure, you know, with the, with the SCO, 864 00:56:35,640 --> 00:56:40,020 Unix junk, and then, and then the podcast, that podcast, 865 00:56:40,110 --> 00:56:43,980 patent troll from, you know, seven or eight years ago, it's 866 00:56:43,980 --> 00:56:48,510 like, you've got so much of this stuff that use it a bad taste in 867 00:56:48,510 --> 00:56:52,020 your mouth. As soon as you see it. It's like, don't, don't do 868 00:56:52,020 --> 00:56:52,500 that, 869 00:56:52,680 --> 00:56:55,710 you know, Dave Weiner, and I didn't patent anything on on 870 00:56:55,710 --> 00:57:02,430 RSS, sort of not anything on podcasting, none of that. If we 871 00:57:02,430 --> 00:57:06,900 had you, and I most likely would not be sitting here talking and 872 00:57:06,930 --> 00:57:12,060 the people might not even know what a podcast is. And what I've 873 00:57:12,060 --> 00:57:16,350 discovered is I like the, the open way I like, you know, if 874 00:57:16,350 --> 00:57:19,560 you want to call it Foss, but you know, whatever this project 875 00:57:19,560 --> 00:57:23,910 is, because I know that just from the experience of RSS, 876 00:57:24,090 --> 00:57:28,080 throughout its its inception, I've made millions of millions 877 00:57:28,080 --> 00:57:31,560 of dollars, millions have spent more but millions of dollars. 878 00:57:33,750 --> 00:57:36,060 And I don't think I ever would have gotten that in any in any 879 00:57:36,060 --> 00:57:37,230 patent fees. 880 00:57:37,860 --> 00:57:44,550 No, no, yeah. Not at all. Well, kind of in a related note, if we 881 00:57:44,970 --> 00:57:49,440 I chose licenses for the namespace 882 00:57:49,800 --> 00:57:51,240 I saw you got 883 00:57:53,310 --> 00:57:57,870 that much. The choice I made was literally with I mean it was it 884 00:57:57,870 --> 00:58:00,930 can be boiled down to just rolling some dice. And just 885 00:58:00,930 --> 00:58:04,350 seeing what came out the other end I have no idea. I just use 886 00:58:04,350 --> 00:58:07,830 the same thing that I always use, which is first things like 887 00:58:07,830 --> 00:58:11,190 this. I think it was the Creative Commons. It was the one 888 00:58:11,190 --> 00:58:15,690 that basically does everything it puts it in public domain but 889 00:58:15,690 --> 00:58:19,350 in a safe way. It was that creative commons one is the Do 890 00:58:19,350 --> 00:58:20,910 you think that's the right one to go with? 891 00:58:21,030 --> 00:58:25,110 I as you know, I've defended Creative Commons in court and I 892 00:58:25,110 --> 00:58:27,780 one where do I see the license? 893 00:58:30,120 --> 00:58:34,770 It's on the on the podcast namespace on GitHub. Let me flip 894 00:58:34,770 --> 00:58:38,850 back up here. It's on the right hand side is the CC zero dash 895 00:58:38,850 --> 00:58:40,620 1.0 license I see 896 00:58:40,620 --> 00:58:42,900 CCS zero what is it? 897 00:58:43,770 --> 00:58:47,820 CC zero 1.0 Universal license point oh, 898 00:58:49,080 --> 00:58:55,740 I see what it entails Yeah, let me go let me see public let me 899 00:58:55,740 --> 00:59:00,450 just see what the protection is no copyright. Okay, the person 900 00:59:00,450 --> 00:59:02,580 who associated work dedicated the work to public domain 901 00:59:02,580 --> 00:59:06,840 waiving all of his rights you can copy modify, distribute in 902 00:59:06,840 --> 00:59:09,480 no way is in no way or the patent or trademark rights of 903 00:59:09,480 --> 00:59:12,630 any person affected unless expressly state otherwise versus 904 00:59:12,990 --> 00:59:20,760 power by bah. So where's the protection this this is just 905 00:59:20,760 --> 00:59:24,630 it's me You can copy modify, distribute and perform the work 906 00:59:24,660 --> 00:59:27,150 even for commercial purposes all without asking permission. 907 00:59:29,610 --> 00:59:33,210 I mean, that sounded like the way to get it because I've 908 00:59:33,210 --> 00:59:35,100 always heard you don't want to actually do you don't want 909 00:59:35,100 --> 00:59:37,620 actually want to use public domain you want to use a license 910 00:59:37,620 --> 00:59:39,690 that gives you public domain in a safe way. 911 00:59:41,550 --> 00:59:45,330 Yes, where you you can say I have this document that says I 912 00:59:45,330 --> 00:59:45,930 can use it. 913 00:59:46,800 --> 00:59:50,280 Yeah. It says limited permissions commercial use 914 00:59:50,280 --> 00:59:52,800 modification, distribution, private use limitations, 915 00:59:52,830 --> 00:59:56,700 liability trademark use patent use and warranty. Where's that? 916 00:59:57,090 --> 01:00:00,600 I don't see that. That's at the top of the page like it's GitHub 917 01:00:00,600 --> 01:00:06,210 giving you like a little a little rundown? If, if you're on 918 01:00:06,210 --> 01:00:09,540 the live if you go to podcast namespace slash licensed.md 919 01:00:10,440 --> 01:00:11,160 That's the 920 01:00:11,190 --> 01:00:14,040 Oh yeah. Oh, this is actually the whole thing is pretty long. 921 01:00:14,070 --> 01:00:16,410 It's good. Yeah. No, that's good. Okay. That's what we want. 922 01:00:16,440 --> 01:00:19,080 Yeah. Here no trademarks or patent rights. Yeah, this is 923 01:00:19,080 --> 01:00:22,410 good. Okay. All right. I think that's perfect. I love Creative 924 01:00:22,410 --> 01:00:24,990 Commons. I'm a I'm a fan. I think it's it's the way to go. 925 01:00:24,990 --> 01:00:29,670 I've used it I've again, I've I've used it to defend assholes 926 01:00:29,700 --> 01:00:32,610 against the assholes. I mean, oh, and it worked. 927 01:00:33,179 --> 01:00:36,479 Yeah, it was that the Dutch photographer stuff? Yeah, they, 928 01:00:36,809 --> 01:00:37,079 yeah, they 929 01:00:37,079 --> 01:00:40,349 took pictures from my Flickr at the time, which were all in 930 01:00:40,349 --> 01:00:42,869 Flickr, I put them on Flickr, because you could mark them with 931 01:00:42,869 --> 01:00:46,679 a Creative Commons license. And, and you're printing them on the 932 01:00:46,679 --> 01:00:49,559 front page of the gossip magazines. And I said, Well, 933 01:00:49,589 --> 01:00:52,139 what are you gonna pay me? They laughed, I said, Okay, I sue 934 01:00:52,139 --> 01:00:59,339 them. Now, you know, and you have to understand that in a 935 01:00:59,789 --> 01:01:02,069 socialist country, they're not going to give you some big 936 01:01:02,069 --> 01:01:04,769 award, but I said, Look, this is what I think it would be worth. 937 01:01:05,339 --> 01:01:11,309 And so they gave, they gave me no reward or award. But if it 938 01:01:11,309 --> 01:01:14,879 ever happens again, it's some ridiculous amount of like, 939 01:01:14,939 --> 01:01:19,169 10,000 euros per copy per day, you know, I would be a 940 01:01:20,009 --> 01:01:20,729 millionaire. 941 01:01:21,390 --> 01:01:22,740 Brian of London level money. 942 01:01:23,069 --> 01:01:26,489 I basically don't show up in any magazines ever again, like 943 01:01:26,489 --> 01:01:30,749 curry. He's like kryptonite man, which is, which is mission 944 01:01:30,749 --> 01:01:32,999 accomplished. I would say mission accomplished. 945 01:01:33,120 --> 01:01:36,390 Yeah, that's, that's That's it. They beat the intern. But if he 946 01:01:36,390 --> 01:01:42,930 tried if he tries to push them then on the CMS Yeah. Buzzsprout 947 01:01:43,140 --> 01:01:46,170 removed all the email addresses from their feeds. Would you say 948 01:01:46,170 --> 01:01:46,470 that? 949 01:01:46,620 --> 01:01:50,280 I saw the announcement. Yeah. Yeah. So that there's like, 950 01:01:50,280 --> 01:01:53,460 click here or forever hold your peace? Yes. 951 01:01:53,610 --> 01:01:57,540 So I feel like that means a couple of things like, 952 01:01:58,320 --> 01:02:00,480 well, there goes half my income. How are we going to spend 953 01:02:00,480 --> 01:02:02,490 podcasters with my great deals? 954 01:02:02,910 --> 01:02:07,620 Oh, I know, I know with with your beef initiatives that 955 01:02:07,620 --> 01:02:09,450 you're clearly a founder 956 01:02:09,450 --> 01:02:13,440 of Yes. Oh, obviously, the Oh coordinates. Yeah, I got I got 957 01:02:13,440 --> 01:02:16,710 points and everybody's deal. Sure. That's me. I'm not an 958 01:02:16,710 --> 01:02:19,770 advisor. Actually, I am an advisor. I'm an unpaid adviser 959 01:02:19,770 --> 01:02:22,020 of beef advisors. Right? That's right. 960 01:02:22,920 --> 01:02:28,650 So pod ping allows it so the way they're doing it, I thought this 961 01:02:28,650 --> 01:02:31,710 is interesting to bring up. The way they're doing it is they're 962 01:02:31,710 --> 01:02:36,510 removing the The email address is not going to be in there. And 963 01:02:37,380 --> 01:02:40,980 we made a change to the lock tag, because previously email 964 01:02:40,980 --> 01:02:46,530 address was required for the lock tag. Not right. We made it 965 01:02:46,530 --> 01:02:50,340 optional. And I'm not really sure why we ever made it mandate 966 01:02:50,430 --> 01:02:51,630 require just went 967 01:02:51,630 --> 01:02:54,120 in there. And without a vote you just willy nilly change 968 01:02:54,120 --> 01:02:58,080 something in the in the holy namespace? Yes, excellent work. 969 01:03:00,420 --> 01:03:06,930 Somebody stopped me. And I was like, wow, I kept thinking, I 970 01:03:06,930 --> 01:03:08,700 was like, there must have been a reason there must have been 971 01:03:08,700 --> 01:03:13,620 reason we did this. It made it required. And for the life of me 972 01:03:13,620 --> 01:03:16,710 could not check and can't remember and require and 973 01:03:16,710 --> 01:03:19,800 required things are like kryptonite anyway. So that you 974 01:03:19,800 --> 01:03:22,230 don't, you don't ever want to use them unless you actually 975 01:03:22,230 --> 01:03:26,370 have, like this supreme reason that makes sense to everybody. 976 01:03:27,209 --> 01:03:29,879 We can remember if we can't even remember them. It's 977 01:03:30,750 --> 01:03:34,170 ridiculous. Yeah. So remove that. And that allowed them to 978 01:03:34,170 --> 01:03:39,330 take that out of the law tech. So the, the pot, so they're 979 01:03:39,330 --> 01:03:43,590 going to remove that. And I'm just saying they can, they're 980 01:03:43,590 --> 01:03:45,270 not going to be in there. But then you're gonna have the 981 01:03:45,270 --> 01:03:49,530 option in their dashboard to turn it on for 24 hours. And 982 01:03:49,530 --> 01:03:53,670 then we'll put it back in there, send a pod ping, we will report 983 01:03:53,670 --> 01:03:57,000 the feed, suck the email address in if it's if we don't have it. 984 01:03:57,300 --> 01:04:01,620 So the neat there's like a filter. So I think we need to 985 01:04:01,620 --> 01:04:07,470 clean clean the database. When an email address is removed. I 986 01:04:07,470 --> 01:04:10,170 don't think the code is currently doing that. 987 01:04:10,200 --> 01:04:12,480 Oh, yeah. Well, of course you want to do that. Yeah, well, 988 01:04:12,510 --> 01:04:17,100 yeah. Okay. Yeah. Yeah, we don't want that if we don't want it 989 01:04:17,130 --> 01:04:22,260 otherwise. Or Or you still have some value. I'm good. bundle 990 01:04:22,260 --> 01:04:22,890 that shit up. 991 01:04:24,480 --> 01:04:28,620 Yeah, so yeah, we can make playlists out of it. Just you 992 01:04:28,620 --> 01:04:34,920 know, get get websites for spamming people's email. The 993 01:04:35,460 --> 01:04:39,030 Yeah, so that I think that's a Oh, one other thing I did. And 994 01:04:39,030 --> 01:04:43,710 this may be interesting. I started sucking in some music 995 01:04:43,710 --> 01:04:48,360 medium tags for this long running music analysis project. 996 01:04:49,620 --> 01:04:51,870 How many how many days is that been running? 997 01:04:52,800 --> 01:04:54,360 Many? I don't know how. 998 01:04:55,170 --> 01:04:57,900 I'll bet you you're probably like 30 or 40% through it all. 999 01:04:57,900 --> 01:04:58,680 If that. 1000 01:04:59,070 --> 01:05:02,070 I don't know where else Alex is on his because we split the load 1001 01:05:02,070 --> 01:05:02,820 half in half. 1002 01:05:02,970 --> 01:05:05,820 And I'm wondering what you're doing just so everyone knows. 1003 01:05:06,240 --> 01:05:13,770 Yeah. Okay, so we're, we wrote a tool called Slurpee that will 1004 01:05:13,770 --> 01:05:19,410 bring, they will suck down all of the enclosures, it'll suck 1005 01:05:19,410 --> 01:05:22,770 down all the the most recent enclosure from each feed in the 1006 01:05:22,770 --> 01:05:28,140 database in the index and save it as an mp3 file in the file 1007 01:05:28,140 --> 01:05:33,930 system. Then another, a Python script comes along behind it, 1008 01:05:34,440 --> 01:05:38,430 that does like a machine learning algorithm to detect 1009 01:05:38,430 --> 01:05:45,870 whether or not the mute the audio in that mp3 is music or 1010 01:05:45,870 --> 01:05:49,770 speech in and then it flags one or the other. So it just goes 1011 01:05:49,770 --> 01:05:52,680 through and does that all through. It actually gives it 1012 01:05:52,680 --> 01:05:59,010 three categories it gives it it gives it classifies it as either 1013 01:05:59,010 --> 01:06:04,080 music. Maybe, which is kind of like maybe music but I'm not 1014 01:06:04,080 --> 01:06:09,150 sure time to review or nothing. Yeah, or nothing. Yeah. So the 1015 01:06:09,270 --> 01:06:17,610 out of I am on podcasts index IDX 628,774. So I'm going 1016 01:06:17,610 --> 01:06:22,710 through up to 2 million. And then Alice has started at 2 1017 01:06:22,710 --> 01:06:25,380 million and is going to go through to the end. 1018 01:06:25,710 --> 01:06:30,060 There's a lot I'm looking at the curio Castro music tab. There's 1019 01:06:30,060 --> 01:06:34,230 more in here. Okay, definitely more than than the last time I 1020 01:06:34,230 --> 01:06:37,290 looked. Let me see. Let me see how many there it looks like I'm 1021 01:06:37,290 --> 01:06:40,020 missing a few like where did April Kirby go? 1022 01:06:41,310 --> 01:06:44,010 Oh, yeah. Okay, so this is yeah, this is from what I started. 1023 01:06:44,010 --> 01:06:49,440 Yep. Yeah, this is me putting these these in here. So what I'm 1024 01:06:49,440 --> 01:06:54,300 started doing this morning, is let's just say you queue 1025 01:06:54,300 --> 01:07:02,280 stories. The key is, we're gonna have to, we're gonna have to as 1026 01:07:02,280 --> 01:07:06,060 run some sort of verification on this. Because I'm already seeing 1027 01:07:06,060 --> 01:07:08,340 a few that may have been misclassified. You mean 1028 01:07:08,340 --> 01:07:09,240 conversations 1029 01:07:09,240 --> 01:07:17,790 with a chef? Let's see what let's see why the AI this would 1030 01:07:17,790 --> 01:07:20,910 be one of the reasons let's see how long the intro song is. 1031 01:07:23,160 --> 01:07:24,210 Hi, and welcome to 1032 01:07:24,210 --> 01:07:27,870 another episode of conversation with the chef. I'm Joe Ricci. 1033 01:07:28,110 --> 01:07:30,780 And I love sharing with you the conversations I get to have with 1034 01:07:30,780 --> 01:07:34,530 talented and passionate chefs. Interesting she had to mute her 1035 01:07:34,530 --> 01:07:38,070 mic is so tinny sounding it almost sounds like it's part of 1036 01:07:38,070 --> 01:07:39,660 the part of the song 1037 01:07:40,200 --> 01:07:44,040 I wonder if you keep going in that episode. Is there a Music 1038 01:07:44,040 --> 01:07:45,240 Bed through the whole thing? 1039 01:07:45,270 --> 01:07:50,640 I'll bet you there is not much and although we'd like to sit 1040 01:07:50,640 --> 01:07:53,610 Yeah, absolutely not the whole thing but the first 1041 01:07:54,690 --> 01:07:57,780 and then lots of background noise for that that first few 1042 01:07:57,780 --> 01:08:02,250 minutes man ai i can't wait until it's controlling my car so 1043 01:08:03,690 --> 01:08:08,910 good machine ml everybody machine learning 1044 01:08:09,930 --> 01:08:14,400 jealousy there's a bunch of things are clearly music but 1045 01:08:14,400 --> 01:08:17,460 yeah, wrapped out radio was wrapped out radio everybody. 1046 01:08:17,490 --> 01:08:18,900 Let's check it out. Ooh, they 1047 01:08:18,900 --> 01:08:20,550 talk to me. You talking about 1048 01:08:21,089 --> 01:08:25,109 talking about dropping a beat baby go home picking up. Yeah, 1049 01:08:25,109 --> 01:08:30,179 nice, man. It's good stuff. I gotta listen to I'm already 1050 01:08:30,179 --> 01:08:32,639 digging this. There's some good stuff. I'll bet where's this? 1051 01:08:33,539 --> 01:08:39,719 See what's the what's the website? There's, I wonder where 1052 01:08:39,719 --> 01:08:42,029 it's coming from? Is that coming from SoundCloud? Some of the 1053 01:08:42,029 --> 01:08:42,509 stuff. 1054 01:08:43,020 --> 01:08:45,540 Yes, all of this is actually coming from SoundCloud what I've 1055 01:08:45,570 --> 01:08:48,870 done what I'm doing right now in in in in an effort to get some 1056 01:08:48,870 --> 01:08:52,320 content in there for people to start playing with for music 1057 01:08:52,320 --> 01:08:56,670 apps. I'm trying to go ahead and suck in some some of these ones 1058 01:08:56,670 --> 01:09:01,170 that we feel pretty good about. But to make that even more 1059 01:09:01,170 --> 01:09:04,290 accurate, I'm just I'm only doing the ones that are on 1060 01:09:04,290 --> 01:09:07,410 SoundCloud for now if they have a SoundCloud URL, I'm going to 1061 01:09:07,410 --> 01:09:10,620 mark those with them within if they're on SoundCloud URL in the 1062 01:09:10,650 --> 01:09:15,180 in the the the machine learning was really confident that it was 1063 01:09:15,180 --> 01:09:20,370 music. I'm gonna I'm gonna mark those right, there's about nine 1064 01:09:20,640 --> 01:09:31,980 out of 628,774 it has found so far. 9775 So, I mean, this is 1065 01:09:31,980 --> 01:09:39,120 really just I want to say that we we know from talking to some 1066 01:09:39,120 --> 01:09:43,860 other people that there are definitely going to be music 1067 01:09:44,250 --> 01:09:47,400 podcasts coming down the pipe soon. 1068 01:09:47,430 --> 01:09:52,260 Oh, yeah. Let me just check this thing. What is this? I? Yeah, we 1069 01:09:52,260 --> 01:09:58,560 back. Me and Darren. Interesting. I got to say, Oh, 1070 01:09:58,560 --> 01:10:02,490 this is because people haven't entered To bite length I get 1071 01:10:02,490 --> 01:10:07,350 zero minutes one second but it's an hour. Oh, I see. Yeah. Anyway 1072 01:10:07,380 --> 01:10:12,000 okay, Dave I love this stuff man. I love this stuff I love 1073 01:10:12,000 --> 01:10:13,230 this this is so cool 1074 01:10:13,230 --> 01:10:17,280 ending on random music interface for a podcast app or a music 1075 01:10:17,279 --> 01:10:19,979 based your life just got a heck of a lot easier as what we're 1076 01:10:19,979 --> 01:10:21,089 saying yeah, you got 1077 01:10:21,089 --> 01:10:27,089 content now and then if you even if you have even thought about 1078 01:10:27,089 --> 01:10:30,119 doing that I encourage you to please go ahead and start coding 1079 01:10:30,119 --> 01:10:31,739 something because it's gonna 1080 01:10:31,740 --> 01:10:35,130 go fast it's gonna have an influx go ahead and say we're 1081 01:10:35,130 --> 01:10:36,900 gonna have an influx coming 1082 01:10:37,440 --> 01:10:40,080 yeah that's not that's not just a prediction That's for real 1083 01:10:40,110 --> 01:10:40,470 Yeah. 1084 01:10:41,100 --> 01:10:48,540 Blood force locked down rested volatile mix cool super duper 1085 01:10:50,220 --> 01:10:53,580 I love this what is air you on the curio caster pages that were 1086 01:10:53,610 --> 01:10:56,100 Yeah, the music and music Tennessee number three from the 1087 01:10:56,100 --> 01:10:58,710 Top Gun. Guns you underground radio? 1088 01:10:58,739 --> 01:11:03,449 Sure do. Let's give it a shot. I'm Joe hippie now. Gongfu short 1089 01:11:03,449 --> 01:11:05,459 Dushane mix present day 1090 01:11:07,020 --> 01:11:08,520 present time 1091 01:11:10,110 --> 01:11:10,860 nice 1092 01:11:18,510 --> 01:11:20,820 man, people doing some creative stuff. 1093 01:11:21,300 --> 01:11:24,390 Oh, yeah. This is a way to get out there. This is really cool. 1094 01:11:24,390 --> 01:11:26,610 All new opportunity. Man just 1095 01:11:26,610 --> 01:11:30,420 think anyone could help them. vie for V enable their feeds 1096 01:11:31,980 --> 01:11:34,140 wouldn't take much they can do it themselves. They can go to 1097 01:11:35,220 --> 01:11:36,840 podcast a wallet.com 1098 01:11:38,040 --> 01:11:41,520 I don't. I don't know if you've. Let's see. Is there anything 1099 01:11:41,520 --> 01:11:47,160 else on music? See? Now Oh, yeah. Well, here's what I guess 1100 01:11:47,160 --> 01:11:50,790 one more thing on music is? How do we want to go about there's 1101 01:11:50,790 --> 01:11:53,550 gonna be some cute human validation of these things to 1102 01:11:53,550 --> 01:11:56,850 weed out the ones that are misclassified. And how do we 1103 01:11:56,850 --> 01:12:01,230 want to do that? is sure to be a UI for that or what? Well, 1104 01:12:02,520 --> 01:12:03,900 podcast events 1105 01:12:07,079 --> 01:12:08,669 Oh, this this 1106 01:12:08,670 --> 01:12:12,090 song is is this this feed is misclassified? 1107 01:12:13,020 --> 01:12:15,690 Oh, okay, that's a good idea. Actually. 1108 01:12:15,930 --> 01:12:16,830 That's why I'm here brother. 1109 01:12:20,940 --> 01:12:23,550 Sir, you've you've proven your utility 1110 01:12:24,630 --> 01:12:27,180 should we think a few people considering Do we have a heart 1111 01:12:27,180 --> 01:12:31,860 out in 45 minutes? Well, we do we have a heart out we have we 1112 01:12:31,860 --> 01:12:35,550 got stuff to do. I can't believe we you accepted this invitation 1113 01:12:35,550 --> 01:12:36,000 time we should 1114 01:12:36,000 --> 01:12:38,280 have said I'm no years old. Every time you say heart out it 1115 01:12:38,280 --> 01:12:39,060 makes me giggle. 1116 01:12:39,930 --> 01:12:45,570 Here's what's been coming in lots of lots of live booths, we 1117 01:12:45,570 --> 01:12:49,290 really appreciate that value for value this entire project. It's 1118 01:12:49,290 --> 01:12:51,990 all run by the people who support it and they support it 1119 01:12:51,990 --> 01:12:54,840 because it get value from it and they send it back to us. So I'm 1120 01:12:54,840 --> 01:12:57,420 do it through PayPal. We'll talk about that in a moment that you 1121 01:12:57,420 --> 01:13:01,020 can get to it podcast index.org And of course we want you to 1122 01:13:01,020 --> 01:13:03,990 have an app that has a boost button. If you don't quickly 1123 01:13:03,990 --> 01:13:09,870 have a look up go to nude podcast app.com and select a new 1124 01:13:09,870 --> 01:13:14,640 one for nude one. Freudian slips 5000 SATs Can you explain why 1125 01:13:14,640 --> 01:13:18,990 the transcripts dot SRT spec is only 2032 character line 1126 01:13:18,990 --> 01:13:22,860 lengths? I can't find an export option with Wasko or whisper to 1127 01:13:22,860 --> 01:13:25,200 manipulate line length or segment length. 1128 01:13:26,880 --> 01:13:29,010 Then I do I need that even means 1129 01:13:29,640 --> 01:13:33,180 well it's the it's the output I this is something I don't know. 1130 01:13:33,300 --> 01:13:37,770 Well maybe someone can boost an answer floydian slips again 5000 1131 01:13:37,770 --> 01:13:40,950 Here's some stats to buy new Dr. Pepper. Although with all these 1132 01:13:40,950 --> 01:13:44,160 native ads, you probably have a solid cache of soda. Oh yeah, 1133 01:13:44,190 --> 01:13:48,960 sure. Native. Sure. Yeah, that's me, Mr. native ad. Oh, what is 1134 01:13:48,960 --> 01:13:55,320 this donation? In honor of episode 200 of grumpy old bands 1135 01:13:55,320 --> 01:14:00,120 and in case you need a new keyboard from Aaron Oh 500,000 1136 01:14:00,120 --> 01:14:01,830 SATs bolo. 1137 01:14:02,790 --> 01:14:05,460 20 is Blaze only Impala. 1138 01:14:06,659 --> 01:14:12,569 Do I get a t shirt now? He says. Yes, you do. Yes. Yes, you do. 1139 01:14:12,569 --> 01:14:17,549 And he ends up with a go podcasting. Thank you very much. 1140 01:14:18,150 --> 01:14:21,840 Yes. Just send me your Darren just send me your T shirt size 1141 01:14:21,840 --> 01:14:22,920 and your address. I'll get you one. 1142 01:14:23,340 --> 01:14:27,690 Thank you, brother. That's very cool. Yeah, Carolyn Carolyn 1143 01:14:27,690 --> 01:14:32,370 comes in with 18,888 No such thing as too off the rails when 1144 01:14:32,370 --> 01:14:38,820 it comes to podcasting. 2.0 run with scissors. One on One one 1145 01:14:38,820 --> 01:14:42,360 from hard hat 3333 from blueberry but my county says 1146 01:14:42,360 --> 01:14:46,740 it's 18 live shows per week on the no agenda stream. Well, 1147 01:14:46,740 --> 01:14:48,660 that's pretty good. I'd say there's a lot to be done. 1148 01:14:48,660 --> 01:14:53,370 They're 23 and live items 2300 from floydian slips enjoying my 1149 01:14:53,370 --> 01:14:56,730 curio Castor wallet. Anyone listening should do the same. A 1150 01:14:56,730 --> 01:15:08,670 row of ducks 22222 So two Only 2222 from Eric P. 1419 48. From 1151 01:15:08,670 --> 01:15:12,300 Brian of London pod ping is pinging and hive is living. Yes, 1152 01:15:12,300 --> 01:15:18,090 it is. More ducks for the pond 2222 from Mike Dell, the bird is 1153 01:15:18,090 --> 01:15:22,680 free. Oh yeah, well, I'll just say it right now. Don't be all 1154 01:15:22,680 --> 01:15:27,300 don't get too all giddy about Twitter being free. Because I'm 1155 01:15:27,300 --> 01:15:30,240 gonna I'm gonna tell you right now what's coming next, you will 1156 01:15:30,240 --> 01:15:33,960 be forced to verify your identity. It's the only way you 1157 01:15:33,960 --> 01:15:38,460 can get rid of the spam and the bots. And then the fun is over. 1158 01:15:38,490 --> 01:15:41,670 Because you can get sued for saying things for trolling, you 1159 01:15:41,670 --> 01:15:44,850 can do things that are wrong in certain countries. Certainly. 1160 01:15:45,329 --> 01:15:49,199 Did you see what Elon said when he posted his open letter to 1161 01:15:49,199 --> 01:15:53,789 Avatar advertisers? Did you see that? No. He said, he said a 1162 01:15:53,789 --> 01:16:01,169 lot. But he said, no doubt. As part of it. He said, I also very 1163 01:16:01,169 --> 01:16:04,169 much believed that advertising when done right can delight, 1164 01:16:04,439 --> 01:16:08,099 entertain and inform you. It can show you a service or product or 1165 01:16:08,099 --> 01:16:10,229 medical treatment that you never knew existed but is right for 1166 01:16:10,229 --> 01:16:13,229 you. Right for this to be true. It is essential to show Twitter 1167 01:16:13,229 --> 01:16:16,979 users advertising that is as relevant as possible to their 1168 01:16:16,979 --> 01:16:22,379 needs. Low relevancy ads are spam. But high relevant ads are 1169 01:16:22,379 --> 01:16:26,999 actual content. Fundamentally, Twitter aspires to be the most 1170 01:16:26,999 --> 01:16:30,539 respected advertising platform in the world that strengthens 1171 01:16:30,539 --> 01:16:33,539 your brand and grows your enterprise. Let's build 1172 01:16:33,539 --> 01:16:35,159 something extraordinary together. 1173 01:16:35,880 --> 01:16:38,490 No, okay, that's fair enough. Sounds good. Like, 1174 01:16:38,489 --> 01:16:41,789 that's good. But, I mean, if you think about it, in terms of 1175 01:16:42,179 --> 01:16:46,949 monetizing the network, you can't get high relevancy from 1176 01:16:46,949 --> 01:16:49,469 the network itself without invading people's privacy. 1177 01:16:49,890 --> 01:16:54,180 That's the only way and he will have that and, and the 1178 01:16:54,180 --> 01:16:58,320 government will love it. And lawyers will love it and the fun 1179 01:16:58,320 --> 01:17:00,780 will be over the trolling will be over. If it's not anonymous, 1180 01:17:00,780 --> 01:17:02,010 it's not going to be fun. Anyway, 1181 01:17:02,100 --> 01:17:04,530 they're gonna they're gonna be a better Facebook than Facebook. 1182 01:17:05,280 --> 01:17:10,110 Dude, Facebook is so dead. It's not even funny. They're the only 1183 01:17:10,110 --> 01:17:13,260 halfway down and they only have a billion dollars in free cash 1184 01:17:13,260 --> 01:17:15,240 flow they generated that's 1185 01:17:15,239 --> 01:17:17,699 a problem. That's not good at all. 1186 01:17:19,050 --> 01:17:25,170 3333 from servo boosting from Chrome tab 33,333 from blueberry 1187 01:17:25,170 --> 01:17:28,530 self hosting a mastodon instance has been most excellent join us 1188 01:17:28,530 --> 01:17:31,890 at spooked dot social, where instead of boosting posts you 1189 01:17:31,890 --> 01:17:35,460 can glow them like a true spook. Stay tuned after no agenda this 1190 01:17:35,460 --> 01:17:43,350 Sunday for a lit behind the scheme's all goats must go yeah 1191 01:17:46,170 --> 01:17:53,010 sure. 2022 for Macintosh row with ducks. Thank you we have I 1192 01:17:53,010 --> 01:17:56,100 think that is it. Yeah, those are our live booth sweep. And of 1193 01:17:56,100 --> 01:18:00,990 course, you can follow along and curio Kassar curio caster.com or 1194 01:18:01,020 --> 01:18:06,030 get your alerts right there in pod verse, pod verse.fm. Or you 1195 01:18:06,030 --> 01:18:08,910 have to go get the app and of course the pod verse, dot F m 1196 01:18:08,910 --> 01:18:11,430 slash live stream page, which is very cool. And thank you all so 1197 01:18:11,430 --> 01:18:14,640 much for supporting us early on. Pre boosting before we even got 1198 01:18:14,640 --> 01:18:15,750 to the donation segment. 1199 01:18:17,430 --> 01:18:23,910 There are 730 830-940-4010 My God 40 234 of us 1200 01:18:25,500 --> 01:18:30,480 don't have 52 Do do you? We got to have cut offs. Dave 16. Too 1201 01:18:30,480 --> 01:18:32,820 many too many. You got to cut off man. You got to start 1202 01:18:32,820 --> 01:18:35,580 cutting off at 10,080 1203 01:18:35,609 --> 01:18:41,519 I'm trying to add up all these streams 12345 streaming, what 1204 01:18:41,519 --> 01:18:41,969 streams 1205 01:18:41,970 --> 01:18:43,890 are you doing? I thought you were adding up number of 1206 01:18:43,890 --> 01:18:46,440 donations and like we can't do ad donations. 1207 01:18:46,530 --> 01:18:50,550 No. I mean, there's there's Okay, that would that was 90. 1208 01:18:50,700 --> 01:18:55,590 Auburn citadel. Sin us. Okay, we're gonna have to come back to 1209 01:18:55,590 --> 01:18:59,610 this. I'll do pay pal. First he he's got his stream amount set 1210 01:18:59,610 --> 01:19:03,900 to 3333 He's streaming is 3333 a minute. 1211 01:19:03,930 --> 01:19:07,380 Just do you think he realizes this? And he did it last week 1212 01:19:07,380 --> 01:19:07,710 too. He's 1213 01:19:07,710 --> 01:19:10,080 got to realize it. Surely he's done because he'd have to 1214 01:19:10,080 --> 01:19:10,800 reload. 1215 01:19:11,670 --> 01:19:13,530 Holy guacamole is 1216 01:19:13,530 --> 01:19:17,820 crap. I will we'll do math on that in a second. Let's see we 1217 01:19:17,820 --> 01:19:22,290 got some. We got some some papers starting off Buzzsprout 1218 01:19:23,340 --> 01:19:24,330 $500. 1219 01:19:24,390 --> 01:19:29,610 Ah Sakala 20 is blades on am Paula 1220 01:19:29,610 --> 01:19:32,910 so appreciated. Caller thank you so much. 1221 01:19:33,900 --> 01:19:37,080 Thank you guys. Thank you, Tom. so much, guys. Thank you, Kevin. 1222 01:19:37,560 --> 01:19:41,010 In the crew at Buzzsprout. Thank you every month for that. 1223 01:19:41,040 --> 01:19:44,220 Yeah, thank you for thinking of us. Yes, we do. Yes we do. 1224 01:19:44,940 --> 01:19:48,300 Also our buddy, Oscar at fountain 1225 01:19:48,449 --> 01:19:53,639 sorry. This is I just opened in the world. That's the that's the 1226 01:19:53,639 --> 01:20:00,419 Alby Saturn interface you can go to live and so it's shows you 1227 01:20:00,419 --> 01:20:04,469 boosts but it also shows you the per per minute so I was looking 1228 01:20:04,469 --> 01:20:06,779 to see if I can see the 3330 there's 1229 01:20:09,029 --> 01:20:11,219 I thought you're playing Subway Surfers to get us some more 1230 01:20:11,249 --> 01:20:12,209 download numbers 1231 01:20:12,210 --> 01:20:17,070 and this page has I have to say so massive, massive confetti 1232 01:20:17,070 --> 01:20:20,190 flying all over it when something comes in it's it's 1233 01:20:20,190 --> 01:20:24,930 quite spectacular. Oh my goodness. 1234 01:20:26,279 --> 01:20:31,889 Our buddies big spurt. Oscar and Nick over fountain gave us $200 1235 01:20:31,889 --> 01:20:34,709 They do this every month. I'll do we're very appreciative. 1236 01:20:34,739 --> 01:20:35,999 Yeah, not an advisor. 1237 01:20:36,750 --> 01:20:37,830 Not not a paid advisor. 1238 01:20:39,930 --> 01:20:42,960 Thank you so much. Oscar. You have been chatting with Oscar a 1239 01:20:42,960 --> 01:20:46,320 little bit about Bitcoin in the UK. 1240 01:20:46,470 --> 01:20:50,280 He also said that they're once he's done with all this this 1241 01:20:50,280 --> 01:20:52,530 most recent round of improvements. They're going to 1242 01:20:52,560 --> 01:20:53,430 work on lit. 1243 01:20:54,329 --> 01:20:57,299 Oh, that'd be good. That'd be good. That's a big missing piece 1244 01:20:57,299 --> 01:21:01,199 there for them. Yeah, it's because I messaged you because 1245 01:21:01,199 --> 01:21:05,669 you don't if you saw it, the UK had some like they've had some 1246 01:21:05,669 --> 01:21:06,899 regulations come. 1247 01:21:07,530 --> 01:21:12,180 I was not. Not not followed or what happened? What was the was 1248 01:21:12,180 --> 01:21:12,690 the rag? 1249 01:21:13,409 --> 01:21:17,789 I asked him what he thought about and he said he thinks is a 1250 01:21:17,789 --> 01:21:21,989 net positive. I don't remember the exact details. Take a look. 1251 01:21:22,439 --> 01:21:25,199 Yeah, they he thinks that he thinks it was a good thing. 1252 01:21:26,609 --> 01:21:31,649 Jennifer Navarette. She still has not said how to pronounce 1253 01:21:31,649 --> 01:21:34,229 her name. But she continues to come in every week. 1254 01:21:34,230 --> 01:21:36,180 It's okay. That way. 1255 01:21:37,050 --> 01:21:39,390 $30 this week, 1256 01:21:39,420 --> 01:21:41,460 thank you. Very appreciated. 1257 01:21:41,940 --> 01:21:45,360 First, thank you. Podcasting has new life because of podcast 1258 01:21:45,360 --> 01:21:50,040 index and 2.0. Y'all rock. This 30 is for the 30 upcoming 1259 01:21:50,040 --> 01:21:53,730 episodes of podcasting in the blockchain, which is part of the 1260 01:21:53,730 --> 01:21:58,890 November 1, the 30th National podcast post month mush national 1261 01:21:58,890 --> 01:22:06,480 podcast post month challenge, aka not pod Pomo hashtag. I aim 1262 01:22:06,480 --> 01:22:09,600 to teach folks a bit about the beautiful blend of podcasting 1263 01:22:09,600 --> 01:22:12,240 2.0 and web three, it's magic. 1264 01:22:12,269 --> 01:22:13,799 Nice to hear. 1265 01:22:15,239 --> 01:22:19,199 Thank you, Jennifer. Appreciate that. And we get $20 donation 1266 01:22:19,199 --> 01:22:21,869 from digitex solutions. No note but thank you. 1267 01:22:21,900 --> 01:22:26,010 Thank you digitary Which does help this just keep servers 1268 01:22:26,010 --> 01:22:27,630 running? This is really appreciated. 1269 01:22:28,140 --> 01:22:31,380 Yeah, we did lose. We lost a $20 monthly subscribers. 1270 01:22:31,500 --> 01:22:36,990 Yeah, people. Apparently PayPal just snuck their $2,500 fine 1271 01:22:36,990 --> 01:22:40,980 right back into their acceptable use policy and just Oh, yeah, 1272 01:22:41,010 --> 01:22:42,300 it's in there. Yep. 1273 01:22:43,050 --> 01:22:47,280 Are you kidding me? No, no no news at all. They just came 1274 01:22:47,280 --> 01:22:48,240 right back and no 1275 01:22:48,240 --> 01:22:52,230 reporting on it as you notice. It's important to note it's 1276 01:22:52,230 --> 01:22:58,050 important to note the under the Pay Pal terms and conditions you 1277 01:22:58,050 --> 01:23:03,030 may not post right speak fart negatively about Pay Pal. 1278 01:23:03,060 --> 01:23:08,340 Otherwise, that is grounds for them to cut you off. Just 1279 01:23:08,340 --> 01:23:10,200 letting you know. Yeah. 1280 01:23:10,350 --> 01:23:11,520 Well, that's that's a 1281 01:23:11,580 --> 01:23:14,790 that's long term policy. They've had that policy for a long time. 1282 01:23:15,330 --> 01:23:18,000 Let's do a riff in this way. It is in sports, too. If you 1283 01:23:18,060 --> 01:23:21,000 badmouth the referee or the conference that you're a part of 1284 01:23:21,000 --> 01:23:24,570 you get you get heavy, heavy fine, like they can they can 1285 01:23:25,290 --> 01:23:27,690 smack you down. So got on. 1286 01:23:28,409 --> 01:23:32,159 Yeah, but 2500 bucks right out of your bank account is a little 1287 01:23:32,159 --> 01:23:35,399 different than being smacked down. It's like, that's a lot of 1288 01:23:35,399 --> 01:23:35,939 money. 1289 01:23:36,510 --> 01:23:41,970 Now, that's no, that's, I mean, that would be devastating. So we 1290 01:23:41,970 --> 01:23:46,110 don't yeah, that's like three months worth of donations. Well, 1291 01:23:46,110 --> 01:23:51,000 it's not just that if you read the language, if you support 1292 01:23:51,630 --> 01:23:57,180 something that promotes dismiss information, you know, 1293 01:23:57,210 --> 01:24:01,710 terrorism, whatever else, you can get dinged as the financial 1294 01:24:01,710 --> 01:24:02,160 year 1295 01:24:03,089 --> 01:24:04,949 and you also get the 2500 hit 1296 01:24:05,520 --> 01:24:10,920 you get the $2,500 hit it's not the recipient necessarily if you 1297 01:24:10,920 --> 01:24:13,110 are funding that yes 1298 01:24:15,420 --> 01:24:19,800 it's it stands me that they did it and then apologized and said 1299 01:24:19,830 --> 01:24:23,250 oh no, no, we didn't mean to and then immediately went back and 1300 01:24:23,250 --> 01:24:23,940 did it again 1301 01:24:23,970 --> 01:24:28,500 doesn't does it as does it really it doesn't really 1302 01:24:28,500 --> 01:24:29,250 surprise you. 1303 01:24:31,079 --> 01:24:35,429 That kind of does honestly that that does because they were so 1304 01:24:36,209 --> 01:24:41,759 like I don't know they were so like anonymous apologetic but 1305 01:24:41,759 --> 01:24:44,489 they were like oh no, no, no, we didn't meet that wasn't supposed 1306 01:24:44,549 --> 01:24:48,209 to be that was just a draft proposal. Some wording. I don't 1307 01:24:48,209 --> 01:24:52,109 think that no one does surprise me. Yeah. That they came back 1308 01:24:52,109 --> 01:24:53,579 within just went right back in there. 1309 01:24:53,909 --> 01:24:57,779 None of this surprises me. This is why we got together two and a 1310 01:24:57,779 --> 01:25:03,509 half years ago. Yeah. None of it surprises me all right we got 1311 01:25:03,509 --> 01:25:03,959 any more 1312 01:25:03,989 --> 01:25:05,969 prepare for the future but you don't like to see happen. 1313 01:25:06,719 --> 01:25:10,049 I think it's exciting that even though we got her we got her 1314 01:25:10,079 --> 01:25:15,479 pretty pretty good by by people canceling PayPal. Those are the 1315 01:25:15,479 --> 01:25:19,799 Sustaining monthly donations they matter. They matter. Six by 1316 01:25:19,799 --> 01:25:23,639 the way we celebrated 15 years of the it's the celebrate the 1317 01:25:23,639 --> 01:25:28,019 15th anniversary week this week for no agenda. Happy birthday. 1318 01:25:28,079 --> 01:25:30,869 Thank you. It was it's it you know what the hard part about 1319 01:25:30,869 --> 01:25:33,989 value for value? It's hard after all these years and for all the 1320 01:25:33,989 --> 01:25:36,959 value that people have provided. I'm talking and of show mixers, 1321 01:25:36,959 --> 01:25:41,669 artists, I mean, you know, you can't thank everybody. And if 1322 01:25:41,669 --> 01:25:47,099 you try you, you'd miss hundreds. It's possible. Yeah, 1323 01:25:47,129 --> 01:25:51,179 but it's anyway. Yes. We made it 15 years, we're still alive. 1324 01:25:51,720 --> 01:25:55,440 Do you have access to a calculator? I do. Can you 1325 01:25:55,440 --> 01:26:00,120 calculate what 3333 times 108 is? 1326 01:26:00,930 --> 01:26:09,090 Okay. 3333 times 108 359,964 1327 01:26:09,480 --> 01:26:12,090 Bagram citadel? Yeah. Oh. 1328 01:26:13,260 --> 01:26:17,070 SATCOM Sakala 20 his blades only Impala 1329 01:26:17,550 --> 01:26:20,970 nice so I don't think he had the streaming set for that. I think 1330 01:26:20,970 --> 01:26:23,130 it was just he was boosting without a boost to Graham. 1331 01:26:23,850 --> 01:26:25,620 Every minute. Yeah, why 1332 01:26:25,620 --> 01:26:29,280 not? It wouldn't it wouldn't show up in your list if it 1333 01:26:29,280 --> 01:26:30,150 wasn't a boost 1334 01:26:34,260 --> 01:26:38,790 you may be right how did he I'm gonna have to invent this this 1335 01:26:38,790 --> 01:26:41,130 is calls for investing Where did he Where did where did he boost 1336 01:26:41,130 --> 01:26:43,410 from what app fountain 1337 01:26:46,350 --> 01:26:47,610 maybe just kept hitting it 1338 01:26:49,560 --> 01:26:53,700 huh? I'm gonna have this dis requires investigation. I'm 1339 01:26:53,700 --> 01:26:54,750 gonna get to the bottom of the web, 1340 01:26:55,140 --> 01:26:57,210 minus 30 minutes for your heart out. 1341 01:26:59,610 --> 01:27:04,320 That's what that means speed up. Really Schonfeld? 54321. 1342 01:27:05,520 --> 01:27:12,000 And may I say? The latest breeze update? Oh, my goodness. The 1343 01:27:12,030 --> 01:27:14,970 Have you have you used breeze since update? 1344 01:27:15,810 --> 01:27:18,960 I have not opened it. But I know that it notified me that I 1345 01:27:18,960 --> 01:27:21,240 needed to because it said my chain was out of sync. 1346 01:27:21,270 --> 01:27:27,870 You will love it. It feels like a feather. Oh, it is so fast. It 1347 01:27:27,870 --> 01:27:31,050 is it things are just it feels like it's like I don't know 1348 01:27:31,050 --> 01:27:33,480 what, I can't even explain it. But of course, you know, I use 1349 01:27:33,480 --> 01:27:37,410 all these apps. So you feel that difference? The payments work 1350 01:27:37,410 --> 01:27:41,220 faster, or at least what's shown. It's good is and the 1351 01:27:41,220 --> 01:27:43,560 podcasting features are kind of coming up there and is that 1352 01:27:43,560 --> 01:27:46,080 really working hard or making a good podcast app in it? 1353 01:27:46,829 --> 01:27:50,429 Okay, I just opened in Linux sync and then I'll use it on way 1354 01:27:50,429 --> 01:27:55,169 back to the office. Rosenfeld 54321 Thank you, Roy. 1355 01:27:55,530 --> 01:27:55,890 Roy. 1356 01:27:56,220 --> 01:28:01,890 Yeah 10,000 SAS from absurd didn't note thank you absurd 1357 01:28:01,890 --> 01:28:06,600 isn't 2222 from coal McCormick, he says boosting while having my 1358 01:28:06,600 --> 01:28:09,510 nightly dessert, frozen blueberries and raw cream from 1359 01:28:09,510 --> 01:28:11,610 rural farms in Fresno, California. 1360 01:28:12,750 --> 01:28:24,030 Ducks. 5552 from Satoshi stream will smiley face. And another 1361 01:28:24,030 --> 01:28:29,160 one for 5252 Excuse me 5582 From Satoshi stream in the Gnosis 1362 01:28:29,310 --> 01:28:37,410 speaking slowly as hard. It is. Mere Mortals podcast is our 1363 01:28:37,410 --> 01:28:40,710 friend chyron. He says long form and unedited are my favorite 1364 01:28:40,710 --> 01:28:45,420 podcasts by far. One and I also regularly call each other out on 1365 01:28:45,420 --> 01:28:50,010 and off air for the repetitive non useful words. Like is a 1366 01:28:50,010 --> 01:28:52,890 serial offender for me. And the classic Aussie positive 1367 01:28:52,890 --> 01:28:55,170 negative. Yeah, no or no. Yeah. 1368 01:28:55,740 --> 01:29:00,270 Yeah, no. This I think relates to the conversation we had about 1369 01:29:00,270 --> 01:29:06,690 the editing the decent roof editing tool, I think. Yeah. And 1370 01:29:06,840 --> 01:29:09,510 there's one of the things I wanted to mention about that. I 1371 01:29:09,510 --> 01:29:17,790 hear in regularly, I'd say maybe once every 10 days out here, an 1372 01:29:17,790 --> 01:29:20,940 edit that was not picked up, which I think is the fault of 1373 01:29:20,940 --> 01:29:25,230 the script. And I'm not sure if it's a bug. And I and I hear 1374 01:29:25,230 --> 01:29:29,460 James do it a lot. And I heard one on pod news this week. Yeah, 1375 01:29:29,490 --> 01:29:32,400 I hear them all the time. And he'll he'll pick it up but then 1376 01:29:32,400 --> 01:29:35,700 it wasn't corrected and the Edit wasn't made. And I wonder if 1377 01:29:35,700 --> 01:29:39,840 it's, it could be where you're if you're just reading. If 1378 01:29:39,840 --> 01:29:42,720 you're just reading the transcript and you're making 1379 01:29:42,720 --> 01:29:46,110 your edits that way it may be very easy to miss a double word, 1380 01:29:46,110 --> 01:29:49,950 you know, end of end of previous line beginning of the next line. 1381 01:29:50,460 --> 01:29:54,660 That's what it sounds like a little bit sometimes when you 1382 01:29:54,660 --> 01:29:58,590 read it as a perfect sentence. Use your ears, people 1383 01:30:00,000 --> 01:30:03,270 I like I like it when that happens because I get to laugh 1384 01:30:03,270 --> 01:30:04,830 at him in the car while I'm driving. 1385 01:30:05,369 --> 01:30:07,619 Why are we even that you're right our secret little 1386 01:30:07,619 --> 01:30:14,459 humorous? Guilty pleasure. Yes. ruined it ruined it. 1387 01:30:15,300 --> 01:30:19,410 Okay. That was 22 to 22. From Karen. Thank you guys. 1388 01:30:19,650 --> 01:30:24,420 Appreciate you all anonymous 1337 says, what if? What if you 1389 01:30:24,420 --> 01:30:27,930 shift some of the opinions and thoughts on GitHub issues into 1390 01:30:27,930 --> 01:30:29,250 GitHub discussions? 1391 01:30:29,819 --> 01:30:32,219 I think that magazine trended Yeah, I think, given this 1392 01:30:32,219 --> 01:30:34,259 discussion, yeah, absolutely. Good idea. 1393 01:30:34,739 --> 01:30:39,719 I'm taking that that approach of feral apothecaries and as 1400 1394 01:30:39,719 --> 01:30:43,199 SAS they found a no note. Thank you, feral apothecary. True. 1395 01:30:43,259 --> 01:30:49,589 True ghee. True grits. True grits. Since 17010. That's the 1396 01:30:49,619 --> 01:30:53,909 Star Trek boost was 1701 says you have got to bring Chris last 1397 01:30:53,909 --> 01:30:57,029 from Jupiter broadcasting back on about this very subject of 1398 01:30:57,029 --> 01:30:59,489 using the Lightning Network to transform software development. 1399 01:30:59,669 --> 01:31:02,219 I know this is something that he has had a lot of thoughts on 1400 01:31:02,219 --> 01:31:05,279 over the past few months. I always was glad to have 1401 01:31:05,279 --> 01:31:10,139 Christmas. Yeah, for sure me. Boost. Permanent invitation. 1402 01:31:10,409 --> 01:31:14,369 Farrell, apothecary 20 202 Fountain No, no note again. He's 1403 01:31:14,579 --> 01:31:22,199 got Hey citizen through pod verse 6969. And the note here is 1404 01:31:22,499 --> 01:31:24,959 DROP TABLE gimlet semicolon 1405 01:31:31,199 --> 01:31:34,079 we've got another one from a citizen 6969 says Drop 1406 01:31:34,079 --> 01:31:37,469 tablespace podcasting underscore industrial underscore complex 1407 01:31:37,469 --> 01:31:44,489 semicolon 16 I did a bit of a little bit of database humor 1408 01:31:44,489 --> 01:31:49,739 there. Yeah, yes, yes, yes. Yes. 10,000 SATs from Sir. Doug go 1409 01:31:49,739 --> 01:31:59,309 podcasting. Thank you sir. Coral hummingbird says 69,420 SATs 1410 01:31:59,309 --> 01:32:01,019 through breeze. Wow. I 1411 01:32:01,020 --> 01:32:05,370 think we should get a little a little big boost. Maybe a boost 1412 01:32:05,370 --> 01:32:06,690 boost boost. Thank you. 1413 01:32:07,020 --> 01:32:09,720 Well, that matches up just fine because of coral hummingbirds 1414 01:32:09,720 --> 01:32:14,160 node is developers developers developers. Boost boost. You 1415 01:32:14,160 --> 01:32:14,640 felt it? 1416 01:32:14,880 --> 01:32:15,870 I did I guess 1417 01:32:17,399 --> 01:32:24,659 Steve Webb OG God casters 77777. Their fountain the striper 1418 01:32:24,659 --> 01:32:29,429 boost. That's right. The work he says the work of PC 2.0 is 1419 01:32:29,429 --> 01:32:31,379 changing the world at the speed of science. 1420 01:32:32,730 --> 01:32:38,460 Yeah, we're getting the the oh what's it called Dave the family 1421 01:32:38,490 --> 01:32:44,550 the family of ah, that huge podcast network they got 3 1422 01:32:44,550 --> 01:32:49,290 million Focus on the Family. Focus on the Family. Yeah. So 1423 01:32:49,290 --> 01:32:51,480 we're helping them out a little bit you more than me because you 1424 01:32:51,480 --> 01:32:53,760 know all this stuff better. But you figured out what their 1425 01:32:53,760 --> 01:32:56,490 problem was? I didn't quite understand the problem, I guess. 1426 01:32:57,029 --> 01:32:59,909 Yeah. Dewpoint no bringing bringing them along. 1427 01:33:00,569 --> 01:33:03,809 That's a big God cast network. Congrats to 1428 01:33:03,810 --> 01:33:06,600 everyone who has contributed their time talent or treasure to 1429 01:33:06,600 --> 01:33:10,200 make it happen. Thank you. I invite all to join me as we read 1430 01:33:10,200 --> 01:33:13,020 through the Bible in a year at audio Bible dot link go 1431 01:33:13,020 --> 01:33:13,710 podcasting? 1432 01:33:13,770 --> 01:33:15,390 Indeed go podcast 1433 01:33:19,050 --> 01:33:25,440 this is 2020 52 sets from the tone wrecker. I mean like 1434 01:33:25,440 --> 01:33:30,420 record. That sounds like a like a wrestler like a WWE thing. Oh 1435 01:33:30,420 --> 01:33:40,470 the tone. Thinking no note from the tone record 40 A 407 says 1436 01:33:40,470 --> 01:33:43,980 from Brian of London and hive Dao and V for V app and he says 1437 01:33:43,980 --> 01:33:46,890 I can't say much more but we largely won our little court 1438 01:33:46,890 --> 01:33:50,340 skirmish last week. Meta won't get too creepy personal details 1439 01:33:50,340 --> 01:33:51,210 they asked us for 1440 01:33:51,510 --> 01:33:53,610 are you better hurry up man that could be out of money by the 1441 01:33:53,610 --> 01:33:54,960 time you win all that crap 1442 01:33:58,050 --> 01:34:00,120 would that not be the biggest kick in the crotch? 1443 01:34:00,600 --> 01:34:03,570 It would be horrible if they completely went bankrupt just at 1444 01:34:03,570 --> 01:34:07,980 the time when and by the way, if Brian wins, they will bankrupt 1445 01:34:08,130 --> 01:34:10,650 they will be big they will be bankrupt yes 1446 01:34:12,750 --> 01:34:15,330 we're safe guys. We got $100 billion in the bank we got 1447 01:34:15,360 --> 01:34:22,140 injured the GM Brian comes along and bingo. Dobby dice 21 Oh 12 1448 01:34:22,380 --> 01:34:25,620 Oh nice. 21,012 sets the fountain and he says boost 1449 01:34:25,619 --> 01:34:28,319 and that is a rush boost boost. 1450 01:34:29,729 --> 01:34:32,939 It violates that is intended to be a rush boost. I've got a 1451 01:34:32,939 --> 01:34:33,659 yellow card. 1452 01:34:33,689 --> 01:34:34,919 That's right flag. 1453 01:34:35,579 --> 01:34:42,749 There's like a row in there. Yes. And 2222 for Macintosh row 1454 01:34:42,749 --> 01:34:45,419 ducks Macintosh. Nope. 1455 01:34:46,979 --> 01:34:48,209 Got your ducks right here. 1456 01:34:49,800 --> 01:34:53,010 And finishing up with the delimiter comma street blogger. 1457 01:34:53,640 --> 01:34:59,250 15,033 Sassy says howdy David Adam. live happy. And by the 1458 01:34:59,250 --> 01:35:02,520 way, a warm humbly invite you and your audience to listen to 1459 01:35:02,520 --> 01:35:05,610 the podcast about artificial intelligence neighbor narrated 1460 01:35:05,610 --> 01:35:09,630 by the British voice of Gregory William Forsythe Forman, the TV 1461 01:35:09,630 --> 01:35:13,440 show developer. Just enter AI dot cooking in your web browser 1462 01:35:13,560 --> 01:35:15,780 or in your podcast player app. Yo. 1463 01:35:20,069 --> 01:35:23,999 jasa, thank everybody. Thank you, everybody for your support 1464 01:35:24,029 --> 01:35:29,399 of the show. Good numbers. Nice. Nice boost today. Oh, I love 1465 01:35:29,399 --> 01:35:33,179 that. Thank you so much the valley. And so this is the value 1466 01:35:33,179 --> 01:35:37,109 return. And this is how it should work. And it's not going 1467 01:35:37,109 --> 01:35:40,019 to be much more than three or 4% of the people who participate in 1468 01:35:40,019 --> 01:35:43,439 the project, listen to the podcast, but everybody can 1469 01:35:43,439 --> 01:35:46,979 participate in many different ways, providing value back to 1470 01:35:46,979 --> 01:35:49,229 podcast and to porno, and thank you so much. 1471 01:35:49,859 --> 01:35:54,029 We get some get some monthlies to finish that off. And it's pod 1472 01:35:54,029 --> 01:35:57,029 news. James over there upon you send us $50 Thank you, James. 1473 01:35:57,719 --> 01:36:02,909 Well, Shawn McCune $20 Jeff Miller $20 And by the way, Jeff, 1474 01:36:02,909 --> 01:36:06,869 I looked, Jeff has been supporting us with a $20 1475 01:36:06,869 --> 01:36:08,999 subscription since September of 2020. 1476 01:36:09,359 --> 01:36:15,299 Hey, there's something wrong here. But I can't What is this? 1477 01:36:15,929 --> 01:36:20,849 It's very sad news. I just got a live boost from Sam Sethi. 1478 01:36:21,599 --> 01:36:26,459 10,000 SATs. Another great show guys can't wait for the Spurlock 1479 01:36:26,459 --> 01:36:31,409 interview. But it's goodbye from pod land episode 100. Next week 1480 01:36:31,529 --> 01:36:32,879 is our last one. 1481 01:36:33,689 --> 01:36:34,889 Whoa, what? 1482 01:36:35,550 --> 01:36:39,480 I what I understand 1483 01:36:41,040 --> 01:36:43,770 this is they must be I heard 1484 01:36:43,769 --> 01:36:46,919 him joking on the show. I'm like, maybe they're changing the 1485 01:36:46,919 --> 01:36:51,749 format or something. Don't get me all. If this is your idea of 1486 01:36:51,749 --> 01:36:55,709 some kind of promotional item where you get me all emotionally 1487 01:36:55,709 --> 01:36:59,849 involved. Because I like pod land is one of the podcasts I 1488 01:36:59,879 --> 01:37:02,519 listened to religiously. I'm pissed off when it doesn't come 1489 01:37:02,519 --> 01:37:03,479 in on Thursday. 1490 01:37:04,229 --> 01:37:07,499 Guys, it's it's October 28 is not April 1. This is not 1491 01:37:07,499 --> 01:37:08,069 appropriate. 1492 01:37:09,000 --> 01:37:14,730 Anyway, if it is, then you know, Sam, I'll do a podcast with Sam. 1493 01:37:14,760 --> 01:37:16,920 I have I have another I have a day somewhere don't I? 1494 01:37:17,489 --> 01:37:18,689 Yeah. Wednesday. 1495 01:37:22,290 --> 01:37:23,700 Thank you, Sam. Appreciate that. 1496 01:37:24,630 --> 01:37:28,350 Cone gloss bucks in his $5 Christopher Raymer $10 James 1497 01:37:28,350 --> 01:37:34,680 Sullivan $10 Jordan Dunnville $10 Paul Saltzman $22.22 Paul, 1498 01:37:35,430 --> 01:37:40,440 dribs Scott $15. Also a subscription since September of 1499 01:37:40,440 --> 01:37:45,000 2020, almost as the beginning, Michael Kimmerer $5.33 Lesley 1500 01:37:45,000 --> 01:37:51,420 Martin $2 Pedro con calvess $5. And also since September 2020, 1501 01:37:51,420 --> 01:37:53,820 Aaron Renaud $5 1502 01:37:54,060 --> 01:37:59,520 Thank you all so much for supporting podcasting 2.0 Boost 1503 01:37:59,520 --> 01:38:03,060 more often boost booths, people. 1504 01:38:04,649 --> 01:38:08,909 Do you know just on a lark? Well, we're at 211 1505 01:38:08,939 --> 01:38:14,429 we have we have 90 minutes to manage 19 for the heart. Ouch. 1506 01:38:18,329 --> 01:38:19,949 Thanks, control room. Thanks, 1507 01:38:20,280 --> 01:38:25,110 Rob. Just for just for giggles. I pulled our download numbers 1508 01:38:25,110 --> 01:38:26,040 from the OP three. 1509 01:38:26,670 --> 01:38:29,490 Oh, good, because I want to I had a question about that. Yeah. 1510 01:38:29,490 --> 01:38:32,550 So what range and what did you do? What did we get here? 1511 01:38:32,970 --> 01:38:38,610 And then while he's printed this out looks like just a few off 1512 01:38:38,610 --> 01:38:43,050 the off the cuff stats here. So we got our biggest podcasting 1513 01:38:43,050 --> 01:38:46,500 two point or the podcast Nippon 2.0 app that people listened to 1514 01:38:46,500 --> 01:38:55,170 us the most honest fountain and then we'll see looking through 1515 01:38:55,170 --> 01:38:58,920 so we got this fountain will obviously apples to the Apple 1516 01:38:58,920 --> 01:39:05,010 podcast app fountain, Google Chrome. That's number two. So 1517 01:39:05,010 --> 01:39:08,670 Chrome is the second most it's probably curio Castro, but I 1518 01:39:08,670 --> 01:39:12,240 would think so. Yeah, probably Pocket Cast is right behind that 1519 01:39:12,240 --> 01:39:16,620 then antenna pod, podcast addict, overcast. 1520 01:39:17,429 --> 01:39:23,039 And how many Apple will see seeing an apple it's only up to 1521 01:39:23,039 --> 01:39:25,589 seven. So it's very low on the scale. 1522 01:39:26,550 --> 01:39:30,180 Is the Apple iPhone generic is probably the streaming so it's 1523 01:39:30,330 --> 01:39:33,000 it's somewhere. I'm thinking that somewhere probably around 1524 01:39:33,000 --> 01:39:35,550 2500 app, Apple podcasts. 1525 01:39:36,359 --> 01:39:38,489 And this is over what period? 1526 01:39:39,479 --> 01:39:43,349 This is for. I just picked our steak and eggs episode one. Oh, 1527 01:39:43,409 --> 01:39:45,899 just one episode. Oh, so how many total? 1528 01:39:46,649 --> 01:39:54,509 How many total was flipped over here? 7355. There are 99 of 1529 01:39:54,509 --> 01:39:55,559 those were bots. 1530 01:39:56,489 --> 01:39:58,469 How many? Seven 7000 usin. 1531 01:39:59,100 --> 01:40:02,790 That's that's Total downloads. And so if you it's going to be 1532 01:40:03,060 --> 01:40:09,270 rearranged is somewhere around 1400 I think and so I think the 1533 01:40:09,270 --> 01:40:13,920 total true number is around 4000. 1534 01:40:14,550 --> 01:40:17,580 Now sounds good. Sounds about right. This more than I thought 1535 01:40:17,580 --> 01:40:18,090 actually 1536 01:40:18,689 --> 01:40:22,079 get a little more than that thought to. But then our, our 1537 01:40:22,079 --> 01:40:25,739 most will see we Chicago is still the first that's probably 1538 01:40:25,739 --> 01:40:29,459 just an artifact within Dallas, maybe get some regional stuff is 1539 01:40:29,459 --> 01:40:33,929 cool. Yeah, just curiosity. More than anything, 1540 01:40:33,989 --> 01:40:37,169 because I think how many episodes have no agenda have I 1541 01:40:37,169 --> 01:40:38,189 put up there now? 1542 01:40:39,569 --> 01:40:42,119 Quite a few. Yeah. We haven't that every week or? 1543 01:40:42,149 --> 01:40:44,339 Yeah, every show. Do we have a month's worth yet? 1544 01:40:45,420 --> 01:40:46,890 Oh, that we do. Do? 1545 01:40:47,040 --> 01:40:51,150 Do we don't let me see. That would be we have to finish up. 1546 01:40:51,330 --> 01:40:54,030 How does it work? You have to finish out the month right. So 1547 01:40:54,030 --> 01:41:00,750 we may see favorite feeds or favorite feeds? No agenda. Here 1548 01:41:00,750 --> 01:41:09,630 we go. Let me see. A month ago would be I think episode 1490. 1549 01:41:09,630 --> 01:41:13,380 That was on podcast index run now. Now that we need it needs 1550 01:41:13,380 --> 01:41:15,540 to be 1491. 1551 01:41:17,100 --> 01:41:23,070 Yep. 1491 had op three in it. Yep. Okay, so 1490 had it in it. 1552 01:41:24,420 --> 01:41:25,800 And 1489. 1553 01:41:25,949 --> 01:41:29,519 Right, right. But we need to finish out we need to finish out 1554 01:41:29,519 --> 01:41:32,099 the month. We'll just do it over the date range. Not not the 1555 01:41:32,099 --> 01:41:35,969 episode, but I just want to know how many suppose it so called 1556 01:41:35,969 --> 01:41:37,139 downloads in a month. 1557 01:41:37,800 --> 01:41:42,690 So not September 25 was the first episode that had mp3 in 1558 01:41:42,690 --> 01:41:45,360 it. And so we're already past the month mark. We're on October 1559 01:41:45,359 --> 01:41:48,329 28. Okay. Oh, so we can pull that we can pull that data? 1560 01:41:48,779 --> 01:41:51,569 Sure. Thanks. So we can calculate how much we would make 1561 01:41:51,569 --> 01:41:56,279 with advertising. That's the only reason I do it. Get a kick 1562 01:41:56,279 --> 01:42:00,959 out of it. But we look how rich we could be doing it right. 1563 01:42:02,010 --> 01:42:05,820 No, we don't have we don't have an exit. We'll just go down with 1564 01:42:05,820 --> 01:42:06,270 the ship. 1565 01:42:07,319 --> 01:42:10,109 Let me see. I don't think I had anything else. That's all. I 1566 01:42:10,109 --> 01:42:13,559 mean, at least not not that aren't longer topics to dive 1567 01:42:13,559 --> 01:42:14,039 into. 1568 01:42:15,090 --> 01:42:17,190 Oh, let's get some stuff. 1569 01:42:17,790 --> 01:42:22,020 I'm just looking at our 14 minutes we have left for our 1570 01:42:22,020 --> 01:42:26,370 hurricane. Okay, I'm just saying. Like, nevermind, we got 1571 01:42:26,370 --> 01:42:29,340 142 on the clock, buddy. I think we're good. We've done it. Once 1572 01:42:29,340 --> 01:42:31,350 again. We've gotten through a whole board meeting without 1573 01:42:31,350 --> 01:42:31,890 fighting. 1574 01:42:33,600 --> 01:42:34,830 Which we do so much. 1575 01:42:36,689 --> 01:42:38,939 Thank you everybody in the chat room. Thank you everybody who's 1576 01:42:38,939 --> 01:42:42,899 listening live. You can do that on curio cast or you can do it 1577 01:42:42,899 --> 01:42:46,859 on pod verse. But of course, all of the podcasting 2.0 apps add 1578 01:42:46,859 --> 01:42:51,119 new podcast apps.com Nude podcast apps.com And if you want 1579 01:42:51,119 --> 01:42:54,449 to join in, go to podcast index dot social and request an invite 1580 01:42:54,449 --> 01:42:57,539 and we'll hook you up. Thank you, brother. Another great week 1581 01:42:57,539 --> 01:43:02,369 Dave? Nothing but the future's so bright. You gotta wear 1582 01:43:02,369 --> 01:43:06,059 shades. We will be back next week with another episode or 1583 01:43:06,089 --> 01:43:09,269 should I just say another board meeting of podcasting? 2.0 Take 1584 01:43:09,269 --> 01:43:10,049 care everybody. See 1585 01:43:10,050 --> 01:43:30,660 you then. Bye bye. You have been listening to podcasting 2.0 1586 01:43:30,810 --> 01:43:34,440 Visit podcast index.org For more information