Replies: 1 comment
-
|
Quick update — the "sidecar registry, keyed by URL, zero feed changes" variant (option 3 above) is now running end-to-end:
So the zero-change, URL-keyed path is proven viable today. The only open call is whether RSSHub wants to bless an opt-in payout convention so any route can advertise one — e.g. a namespaced optional element a la Podcasting 2.0's Would a minimal PR adding an optional per-route payout field (emitted as a namespaced element, off by default) be something you'd consider? Happy to open it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
RSS made content portable. It never made it payable. And the dominant "reader" is increasingly an AI agent: it pulls a feed, uses the author's words to answer someone's question, and sends back no click, no view, no cent. The author funded the work; the agent captured the value.
There's already a precedent for fixing this in the feed layer: Podcasting 2.0's
<podcast:value>lets a podcast declare a payout destination so apps can stream micropayments to the creator. It works, it's adopted, and it's just a namespaced element in the feed.Proposal: generalize that to any RSS/Atom feed — an optional payout address a feed can advertise, so an AI that cites the content can pay the author a micropayment, weighted by how much the source actually contributed to the answer.
Two things make this realistic with RSSHub specifically:
Reference implementation: I built Keryx (open source) to prove the loop end-to-end — an agent that decides which sources are worth reading, reads enough to answer, writes a cited answer, then settles a per-citation micropayment to each source it actually cited (multi-author works split automatically). It already consumes RSSHub-style feeds unmodified; the only thing missing from the standard is a place for the author to say "pay me here." (Settlement is on a testnet rail today.)
The ask: would the maintainers/community be open to an optional
payoutconvention at the feed level? I'd be happy to open a PR. Two open questions:<podcast:value>-style namespaced element) vs. a lightweight RSSHub-native config field?Curious what shape you'd actually merge.
Beta Was this translation helpful? Give feedback.
All reactions