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]

I had a post here, but it was wrong too.

I don't think I have example code for what you're looking for.

Back in a minute.

[scripting]

I use this cloud server in all my work.

<cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post"/>

@andrewshell runs the server. it's fast and reliable.

But you can run your own. Since I don't run a cloud server myself I don't have good example code for it.

I'd recommend sticking with rss.cloudPing, you get the benefit without any of the work. ;-)

[scripting]

@andrewshell has made the source for his cloud server open source.

https://github.com/rsscloud/rsscloud-server

[johnspurlock]

hmm, I'm fine with implementing it myself, since its only two calls. I need to be able to know who's subscribed and for what topics to avoid extra processing on every incoming Bluesky post!

I already have the endpoint specified in that rss cloud element ready to go: /rss-cloud-notify implemented on that domain. Just need an example of the two http-post calls.

Or maybe there is a public client that supports rss cloud, and will try to subscribe to this feed? I could then at least see what it sends : )

[scripting]

I think I understand what you’re looking for.

I would try river5, a feed reader I wrote a few years ago, it supports the client side of the protocol.

https://github.com/scripting/river5

[scripting]

Here’s the rssCloud code.

https://github.com/scripting/reader/blob/master/davereader.js#L1949

[johnspurlock]

thanks! will take a look

[scripting]

@johnspurlock -- checking in -- how's it going?

[johnspurlock]

I think I got it, should have it up and running in production later day (I'm in US central time)

For anyone stumbling across this thread, the http-post protocol appears to be:

Given a cloud element:

<cloud domain="server.example.com" port="123" path="/please-notify" registerProcedure="" protocol="http-post" />

The incoming subscribe HTTP request/response looks like:

POST http://server.example.com:123/please-notify
accept: application/json
content-type: application/x-www-form-urlencoded

port=<callback-port>&path=<callback-path>&url1=<feed-url>&protocol=http-post

200 OK
content-type: application/json

{ "success": true }

or

400 Client error
content-type: application/json

{ "success": false, "msg": "<error-message>" }

The server needs to remember the ip address of the subscribe request, let's call it subscriber-ip

Subsequent outgoing feed change notifications are sent to subscribers as follows:

POST http://<subscriber-ip>:<callback-port><callback-path>
content-type: application/x-www-form-urlencoded

url=<feed-url>

200 OK

Note everything is done with unencrypted http, not https

[scripting]

BTW, I should've sent you these pointers yesterday. I had guests over for a BBQ at the time, so I wasn't focused well enough.

http://home.rsscloud.co/

http://scripting.com/opmlHowto/dave/rssCloud/walkthrough.html

http://walkthrough.rsscloud.co/

I think there is other pointers as well.

[scripting]

Also I want to try adding a bit of social glue to the feeds you're building.

Can you surface the names of people other people have subscribed to, as an OPML subscription list?

Happy to show you how to do that..

[andrewshell]

Let me know if you have questions with my implementation.

The standard for http-post is not https but I added support as https-post which works exactly the same only https. There is also an optional domain property on pleaseNotify if you don't want to have it ping the ip address.

Here are the docs: http://rpc.rsscloud.io/docs

[scripting]

I just wrote a blog post about this stuff.

http://scripting.com/2023/05/15.html#a132038

[scripting]

@johnspurlock -- turns out we needed https support for it to work with FeedLand.

[johnspurlock]

Gotcha, I guess I can support https-post for subscribers as well. Hopefully you guys have reader/client software that can test it out (ie subscribe) to one of the firesky.tv feeds when it's live. Seems to be working with a local version of river5.

Keen on implementing any push notification systems for Firesky, given its real-time nature. I could see this being useful for folks subscribing to multiple people and getting new posts as soon as they're posted.

@scripting interested in what you're think regarding surfacing Bluesky graph over opml, maybe start a new issue dedicated to that and we can hash it out.