Statuses

Lazyweb followup – After some testing with opmlPackage, I figured out that I needed to get the OPML of my Zettelkasten file using this URL and then selecting View Source and copying. Once I did that, I was able to process it using Pandoc.

Lazyweb request – I tried converting my OPML Zettelkasten file into Markdown using Pandoc, but got an “Invalid XML” error, because I have URLs within the outline elements. Any suggestions for fixing this? I am looking at opmlToJs to get the OPML in JSON, then use sanitize-html to escape the URLs, then write it back out using opmlToJs. Other suggestions welcome!

I was able to confirm this morning that rssCloud support in FeedLand worked for my WordPress.com test site – hurray! Many thanks to Andrew Shell and Dave Winer for working things out, along with support from Joseph Scott at Automattic. Joseph Scott released a new version of the RSS Cloud plugin today for WordPress.org sites, I did an initial test, but FeedLand did not get a rssCloud update from my test site. I got some debug ideas from Joseph Scott, working on those now.

Update: I figured out that Gary Teter’s post I referenced on December 10 was not deleted from the FeedLand user view, so looks like it was my post that brought in the comment guidelines. I apologize for the error.

Lazyweb request – does anyone know of other feed readers besides FeedLand and River5 that support the rssCloud protocol? I am trying to collect data regarding the WordPress rssCloud implementation. Thanks.

I have been collaborating with Andrew Shell on the WordPress.com rssCloud issue. Andrew added a note to my support forum post that WordPress.com and the RSS Cloud plugin only accept aggregators running on port 80, 443, and 8080. I have confirmed that the RSS Cloud plugin will accept a registration from an app running on ports 443 and 8080 and provide the correct rssCloud response when the source feed updates. Andrew will be contacting Joseph Scott (plugin developer) at Automattic with this information.