Right now Dave Jones of @podcastindexorg and @alecksgates are testing the new 2.0 version of the Podping Hivewriter software which is used to write most podpings to Hive. I'm using the new Podping Pingslurp dashboard to monitor the testing.
Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
We have done some testing on the Mirrornet but we really do have to test some aspects of the new writer on the live Hive chain and when we do that these tests show up on my dashboard:
That looks like a bad game of Missile Command from the early '80s when it should look more like this:
Each of the coloured circles represents a minute's worth of Podpings from each of the accounts which are listed on the right of the graph. Their vertical position on the right hand scale shows the number of IRIs (which are URLs of podcasts) sent by each account in a given minute. That value is typically below 10 but for the three main accounts, podping.aaa, podping.bbb and podping.ccc, it can be 40 to 100 IRIs in a minute: that's normal load.
You can learn about the dashboard and play with it yourself from this post.
Reasons and Mediums
The biggest new feature of Podping Hivewriter 2.0 is its ability to handle "Medium" and "Reason" codes.
Mediums
Up to now almost every podping sent has been either a podcast or a video. Everything sent by Dave's Podping.cloud service was a podcast and everything I send for @threespeak is a video.
Going forward there will be new mediums such as music, film and audiobook (schema is on Github).
Reasons
This is where the new magic comes from. Whenever a podcast or video podcast updates we just use the reason code update. The most important new Reason codes relates to signaling that a livestream has started. We are adding live and liveEnd to the existing update. (schema on Github).
This is where the magic happens and has already been in use for signaling the live streams from the No Agenda Podcast and other shows which then show up in Podverse and Curiocaster. There are other apps working on surfacing these live streams.
Rates
So why the missile command look on my dashboard? We are stress testing. Now that we're using multiple reasons and mediums in our podpings, we have also moved to writing multiple different Podpings (each a custom_json) into a single Hive transaction. That looks like this on the Hive chain.
And this is to ensure that we can comfortably handle more than the entire world's podcasts.
Right now Podcastindex.org records that 360,000 new podcast episodes were published in the last 30 days.
Podping broadcast 823,622 individual RSS feeds in the last 30 days. Whilst Podping appears to carry a higher number, not every time an RSS feed gets Podping'ed is it to announce a new episode. Many of those pings will be updates to show notes or other details.
We don't know exactly what proportion of new episodes are announce with Podping, the best guess is around 15%. But we want to make sure that when it rises to be all of them, we can cope.
Testing indicates we have plenty of overhead.
Podping's transaction volumes
~~~ embed:1596907162617397251?s=20&t=R7I2umvRXmD4-wECyPfW5w twitter metadata:djR2YXBwfHxodHRwczovL3R3aXR0ZXIuY29tL3Y0dmFwcC9zdGF0dXMvMTU5NjkwNzE2MjYxNzM5NzI1MXw= ~~~
Thank you for looking all the way down to here, if you value my work on Podping, and on @v4vapp, please consider voting for my latest proposal #244, links:
Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
💪🏻 Impressive numbers what Podping already deals with. Really looking forward to the new functionalities, especially the „Live“ pings seem to add value.
🙈 What I am only not getting yet…how can you Podcast live if normally you record and upload new episodes, at least this is how I do it. Is there already a scheme/description to that?
Podping requires use of The Podcast Namespace, in which we developed the <podcast:liveItem> tag.
Recommend joining podcastindex.social and asking around for advice.
https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/1.0.md#live-item
Fabulous! Looking forward to hearing all about it on the next Podcasting 2.0 episode.
I've really got to explain it properly. Perhaps you and I should do a video chat and record it? I've thought about doing it myself but I kinda like having someone to talk to and who can ask questions, is that interesting?
Count me in!
We will set a time next week I hope.
This is awesome and there's really a lot of work being put to it. Keep up the good work @brianoflondon I appreciate every part of it.
The rewards earned on this comment will go directly to the people( @v4vapp ) sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at https://hiveposh.com.
It is a great job you are doing and I strongly believe after the testing, it will be much more perfected. Kudos to your effort
Very nice and it's really show your great hardworking, keep it up
Click on the badge to view your board. Click [here](https://hivebuzz.me/rankingWC) to check your ranking.
Thank you to our sponsors. Please consider supporting them.
Check out the last post from @hivebuzz:
Click on the badge to view your board. Click [here](https://hivebuzz.me/rankingWC) to check your ranking.
Thank you to our sponsors. Please consider supporting them.
Check out the last post from @hivebuzz:
Hi @brianoflondon,
I don't understand the part about
And then why
Is there a reason why #Podping seemed to broadcast more Podcast instances than the Podcast Index indicates is available?
Thank you for your time, and I am interested in understanding.
This is a good point I need to explain.
Sending out Podpings is a behind the scenes activity, very few users do it directly or are aware of it. 95% of Podpings are sent by a podcast hosting company sending a signal with just the podcast RSS feed address to podping.cloud which then gathers up all those RSS feeds and writes them to a custom_json every few seconds.
When designing Podping we deliberately made the messages as small as possible. It isn't Podping's job to tell you what has changed in a podcast's RSS feed, just that it needs to be checked. Parsing and decoding RSS feeds and looking for changes is a big deal and we don't do that, but those entities (like PodcastIndex or Apple, Google and Spotify) all have to do this to run Podcast indexes.
So if you publish a new show, then go back in and edit the show notes or update the title, those things can result in a podping going out again and again. This generally accounts for the multiple sending.
Oh okay, so a Dapp like D.Buzz could organize & render the Podpings, and display it on our site for #DBuzz users.
Posted via D.Buzz
There isn't much point to that. Podping is more like a behind the scenes communication protocol. Automated systems tell each other to do something out start something with it.
Eventually Dbuzz might like to show live podcasts for example but unless Dbuzz wants to be a general purpose podcast listening app I'm not sure what else they could do with podping.
fantastic! I am actually starting to get interested in trying out a podcast myself. Having had 0 experience in anything in regard to setting a podcast up, do you have any tips on how to get started (and using podping)?
That's cool!
Keep up the good work