Hi, @brianoflondon here, Podping has a new site. It's very much a work in progress but I'm trying to tie together multiple disparate sources of information about Podping.
Going forward the content will be on podping.org.
There's a front page with some text and links to other parts of the eco system and which needs a lot more work. Off the bat I'll say the site isn't really optimised for mobile, its much more of a desktop thing right now.
Then there are a number of graphical screens showing information about the current state of Pings and the Resource Credit system I've built to make sure the Podpings keep flowing.
If you want to just watch Podcasts updating in real time powered by Podping head to podping.watch
Just a reminder, I'm currently collecting votes for my ongoing work proposal #244
Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
Now back to the post....
RC Overview
This screen shows Delegating and Receiving Accounts. Most of the RC's for Podping come from the @podping account but I've given the bot I've written authority to dip into my @brianoflondon and @v4vapp.dhf RCs if necessary.
Graphs
- Blue line is the current RC % of the account (right scale).
- Red line is the absolute value of the RC's on the account (left scale).
- A vertical dashed line indicates that an RC delegation was either increased or decreased.
The bot behind this (which is open source hive-rc-auto) tries to keep the RC % of the target accounts behind 25% and 40%. In the following graph, looking from the left to right, you can see the blue line rising a few times and each time it hits 40% on the right hand scale, there's a dashed vertical line and it drops. That dashed line is the bot removing some RC's from the delegation to the account @podping.aaa.
At other times the value will dip below 25% and then the bot would hand out some RCs.
Largely through manual tuning, I've arrived at a fairly steady model for keeping the RC's on these accounts steady.
RC Delegation Details
The next screen is a fairly dull list of actual delegation changes: cuts or increases. There's also a link in the first table which will show you the specific transaction on Hive where the change happened.
Pingslurp Accounts
Pingslurp is my system for storing and indexing all Podpings. It holds around 90 days worth of Podpings. This page shows the Podpings sent out grouped by the Hive accounts which send them.
The upper graph looks back through the entire database and shows the total number of IRIs (each RSS feed URL is an IRI) sent per hour by each account.
The lower graph shows the last 4 hours of activity and shows IRIs per minute.
Podping.cloud is a service run by podcastindex.org which makes it easier for large podcast hosting companies to send Podpings. The following Hive accounts are controlled by Podping.cloud: podping.aaa, podping.bbb, podping.ccc, podping.ddd and podping.eee
Other notable accounts:
Sends out Podpings for 3speak.tv: podping.spk, podping.bol.
Development and testing: podping.gittest, podping.test
Pingslurp Hosts
This page gives an idea of which Podcast Hosting companies are actively sending updates via Podping. It allows us to spot if there has been an interruption in the stream from any of the larger hosts like Buzzsprout, Transistor or RSS.com.
The gauges show the number of IRIs sent in the previous full hour compared to the hour before that. The Blue mark on the gauge is the 8 hour moving average and the red area indicates the lowest number of IRIs seen in an hour over the previous 72 hours.
The graph at the bottom shows the total number of IRIs sent per hour with a trace line for the 8 hour moving average.
Just a reminder, I'm currently collecting votes for my ongoing work proposal #244
Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
