Topic: Podping

8 chapters across the catalog

Episode 267: Chocolove
1:24 - 3:48

Episode 267: Chocolove

Podping Version 0.12.0 Release, Linode Server Management

Dave Jones announces the shipment of Podping version 0.12.0 following several weeks of development. The discussion covers the migration of servers to Linode and the influx of automated Showrunner alerts regarding egress bandwidth and CPU spikes on the Podcast Index database.

Episode 267: Chocolove
15:32 - 18:03

Episode 267: Chocolove

Podping Architecture Transition, Hardcoded Bootstrap Nodes

Dave Jones explains the decision to remove DHT from Podping due to stability issues with the Eero library. The system has transitioned to using five hardcoded bootstrap nodes located in Australia, Central, East, Europe, and West, which utilize permanent public keys for coordination.

Episode 264: Podcast Plebicide
1:02:19 - 1:08:55

Episode 264: Podcast Plebicide

Podping Alpha, Gossip Protocol and Node Trust

The Podping project is moving toward a more stable architecture by splitting its monolithic structure into separate listener, writer, and monitor repositories. A "plebiscite" voting mechanism is being implemented to manage trust within the peer-to-peer swarm, allowing nodes to inherit trust or be voted off the network. This decentralized approach aims to ensure the stability of real-time podcast update signals.

Episode 262: Podcleanse
55:00 - 57:27

Episode 262: Podcleanse

PodPing for Stats, CSV Data Standards

Dave Jones suggests using PodPing to broadcast URLs for publicly downloadable CSV files containing podcast stats. Adam Curry points out that making the data publicly downloadable would prevent them from charging for it, highlighting the conflict between open-source ideals and the need to fund the ecosystem.

Episode 260: Tennessee Trickshot
22:45 - 27:16

Episode 260: Tennessee Trickshot

Podping Gossip Swarm and PP Monitor Stability

The Podping gossip swarm is currently operating with 21 nodes and 18 active hosts, showing high stability over the last several months. Technical details are provided regarding the live tracking firehose, which uses a linked list of object storage files to allow users to ingest episode data without heavy API reliance.