If I don't interact with your message, it probably contains one of these keywords:
nostr
(to be updated)
Podcasting 2.0 consultant
Master of the protocols
Knight of Podcasting 2.0
INTJ-A
Essays | https://write.agates.io |
GitHub | https://github.com/agates |
GitLab | https://gitlab.com/agates |
XMPP | xmpp:agates@chat.agates.io |
If I don't interact with your message, it probably contains one of these keywords:
nostr
(to be updated)
Hi.
I'm thinking about adding a new reason code to Podping to indicate that an RSS feed has added a new item.
This would primarily serve as a means to allow consumers to prioritize parsing of new episodes vs regular updates -- similar to "live" and "liveEnd" but for standard items.
It would particularly be useful for notification systems on the client side. But we also use different reasons to prioritize Podpings in podping-hivewriter to (so "live" is sent before "update").
Pros/cons?