Earlier this week, I updated the outline with my list feeds of the sites I regularly read. I'd previously set up my reading-list river, at my.zuiker.com, to watch for changes to that opml list, but the river stopped working once I had changed the outline. I guess I was expecting River5 to work in a way it's not meant to, though I think the Duke River is doing what I wanted my personal river to do.

Anyway, I tried to restart the river, getting an error every time, so then recreated the river on my webhost trying to remember the steps I'd previously taken, and finally figuring out that I needed River5 to use the opml list directly and not via an include.

All this, by the way, as I prepare my short presentation about the "river of news" concept for the AAMC GIA17 professional development conference I'll attend this spring.

UPDATE the next morning

I've borked it again:

• I added a new feed to my Little Outliner opml file.
• I stopped river5.js.
• I replaced the list.
• I started river5.js using forever, and briefly saw the river page at river.zuiker.com. Then it went to a 502 bad gateway message. Forever list shows the process is stopped.
• Trying to start river5.js with node reports an error. I suspect there is a problem feeds in my list. So I take out the 2 feeds I changed this morning, and reloaded the list. Still errors. 
• This is frustrating. I don't know what I'm doing, or doing wrong.