Details on rss cloud calls for protocol http-post

[johnspurlock]

Hi there - I'd like to support the cloud element over http-post.

Given an rss feed like: https://rss.firesky.tv/?filter=quake

<rss version="2.0" xmlns:source="http://source.scripting.com/">
  <channel>
    ...
    <cloud domain="rss.firesky.tv" port="443" path="/rss-cloud-notify" registerProcedure="" protocol="http-post" />

I'll just be using the web standard fetch api on the server side.

It would help to see:

• an example HTTP request/response incoming subscription call from clients
• an example HTTP request/response outgoing notification call to notify clients (guessing something like this?)

HTTP method/url/headers/bodies/status should be enough.

Thanks! - John

[scripting]

Thanks to both of you for joining up with blue.feedland.org. :smile:

Here's the punchline in case it wasn't clear from what I wrote before.

https://blue.feedland.org/?username=dave

The checkboxes work. Anything that isn't checked is a feed I'm subscribed to that you aren't subscribed to.

It's how feed discovery works in FeedLand. Key feature.

[scripting]

Could we move the call to tomorrow. I’m pretty tired, did a lot of work today.

[johnspurlock]

No worries, tomorrow works too

[scripting]

The feed-level pubDate appears to just be the current time.

The way I usually do it for these kinds of feeds is I make it the most recent of the pubDate's of all the items in the feed.

Also note that the feed-level pubDate is optional, so leaving it out is also an option. Esp if there are no items in the feed or they don't have pubDates for some reason.

https://cyber.harvard.edu/rss/rss.html#optionalChannelElements

[johnspurlock]

ah good point, these feeds are effectively live, so feed-level pubDate doesn't make sense, and the lastBuildDate communicates when the feed was put together.

I'll remove the feed-level one