Mitch Downey :pci: on Nostr: npub1dft4c…7ta3d npub1vpkys…g092y npub1dwufa…ahc2f ok, if the value tag was ...
npub1dft4ckvyhfpw3n56zm8j42nzrjeummudr2vmkf304eu5jhnn0ahqz7ta3d (npub1dft…ta3d) npub1vpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrsqg092y (npub1vpk…092y) npub1dwufaddv76r7saj4x9teyqzk70c7xapllnsa99l6r2c7f8x0tzdsyahc2f (npub1dwu…hc2f) ok, if the value tag was updated in the RSS feed *after* the "going live" Podping was sent, then a 15-20m delay could be significant.
Podverse re-parses feeds that send a "going live" Podping immediately.
But for "feed updated" Podpings (different than "going live" Podpings), there is a 10-15 minute delay before those changes are reflected in Podverse.
So if Spencer updated the feed *after* live, then sent a "feed updated" notification, that might explain the issue
Podverse re-parses feeds that send a "going live" Podping immediately.
But for "feed updated" Podpings (different than "going live" Podpings), there is a 10-15 minute delay before those changes are reflected in Podverse.
So if Spencer updated the feed *after* live, then sent a "feed updated" notification, that might explain the issue