in Feed Readers, Rivers of News

Creating and Displaying Rivers of News

I wrote a post several years ago on this topic, but decided to refresh it since some of the links don’t work any more…and also because I am setting up a new river for Ron Chester….

In the same vein as “own your data” or “supporting the open web”, it’s important for users to be able to set up their own tools for collecting/reading information on the Web, and not be dependent on other people’s tools. Having said that, I have been happy to provide a river resource for the 1999er community (http://1999bloggers.andysylvester.com/). This post will help you to do the same for any blogs/feeds that you are interested in following.

There are two pieces to the river resource given above:

1. A installation of the River5 RSS aggregator running on a server

2. An HTML page that displays a river or rivers created by River5

At the River5 Github site (https://github.com/scripting/river5), there are several tutorials in the site wiki on installing River5:

Another option is to buy my book on setting up an Ubuntu server on Amazon Web Services (the last chapter shows how to set up River5)….

Once you have River5 set up on a public server and creating river files (Javascript files that can be read/displayed by other applications (for example, 1999bloggers.js)), you have some options for being able to display those files. When River5 is running, you can direct people to the public display of the rivers being created. An example can be seen at http://fedwiki.andysylvester.com:1337, which is my main River5 installation. This install is creating multiple rivers, which are displayed in multiple tabs. If you only had one river, you would see only one tab.

Another option for making your river public without pointing to the River5 app display is to use a separate HTML page that accesses the river files. Dave Winer has created a toolkit for display of River5 river files (https://github.com/scripting/riverBrowser). To test the app, copy two files from the repo (frozenriver.js and riverbrowserdemo.html) to a directory on a web server. You should then see the contents of the frozen river file as shown in Dave Winer’s demo app.

To set up your own public display of a River5 river, make a copy of the riverbrowserdemo.html file. Next, edit the file and find the line with the phrase “httpGetRiver”. It should look like this:

httpGetRiver(“frozenriver.js”, “idRiverDisplay”, function (){

Next, you will be replacing the text “frozenriver.js” with a URL to a list in your River5 installation. For example, I have a file called readinglist.txt, which contains a list of over 40 RSS feeds that I follow. When your River5 installation is running, you can feed a URL corresponding to a River5 list of feeds that you have created. The following is the line of Javascript from above with the URL for readinglist.txt from my server:

httpGetRiver (“http://fedwiki.andysylvester.com:1337/getoneriver?fname=readinglist.txt”, “idRiverDisplay”, function (){

For your setup, replace the URL part (http://fedwiki.andysylvester.com:1337) with the URL  for your River5 server, and replace the text following “fname=” (readinglist.txt) with the name of your file in the lists folder within your River5 installation.  Finally, upload the HTML file to a server. As long as the River5 server is running, your HTML page will display the latest version of the river. An example is available at http://andysylvester.com/files/riverbrowserdemo.html.

OK – now get started making rivers!

Write a Comment

Comment

  1. Decided to shift my artcasting focus to creating a river of art (think River of News or the current “news product” feature in FeedLand). I…

Webmentions

  • I have been in several conversations in the last week (voice and email) where the concept of “working together” in software development came up, and several threads emerged:

    how the original developer doesn’t/shouldn’t have to do everything – others can contribute (to me, a key concept in open source)
    how interested/engaged users can be an important force in the direction in which a software application or tool goes forward

    Dave Winer has written about this many times:

    The magic of working together

    Key concept of the open web: working together

    Working together means this: If someone else has a good-enough way to do something, rather than reinvent what they do, incorporate what they do into what you do.

    Working together (SOTN 2018)
    Working together in 2019

    I have tried to follow that second point in several ways:

    My blog uses WordPress, I did not develop my own blogging tool
    I use River5 as my RSS reader engine
    I use RiverBrowser to display my own rivers of news

    I document and evangelize how to create your own rivers of news
    I document how to use tools like River4 and 1999.io

    I help others set up these tools

    I am getting ready to start working in the computer music area again after a long absence, and I am reviewing available tools to see if they fit the areas I am interested in. In that way, I am trying to practice the concepts of working together as I have outlined above.
    Anyone want to work together with me? Let me know!

  • Looking back over my posts, this has been my most prolific year in blogging (posted something in every month except August!). At the start of the year, I was trying to post a link a day, and managed to get into early February before dropping off. In March, I did a first-ever podcast to look at how my feed would capture the enclosure, as Pocket Casts (my phone podcast client) seemed to be having problems with picking up podcasts that were part of blogs (like Scripting News). April and May each had a link post, but June showed more activity (a Pocket Casts bug report, some links, a blog conversation with John Philpin about the micro.blog service, and getting my Technician ham radio license). July brought a return to link posts, and I began to start responding to other posts trying to use the Webmention protocol. In September, I got interested in Federated Wiki again, had a phone call with Ward Cunningham and wrote a post or two on that topic, as well as some links. October had 3 posts, but a key one was a link to an item by Seth Godin encouraging the reader to do something every day that builds an asset for you. I decided to rededicate myself to posting something daily, whether it be just a link or something more substantial. This lead to 18 posts in November and 27 posts in December! In November, I began to get more involved with users of the micro.blog service, particularly John Philpin and Ron Chester, who I met while I was using the 1999 blog tool from Dave Winer some years ago. I did a few more podcasts, and started work on a new book (listen to podcast episode 2 for more information on that!). I have also been working with Ron Chester to set up a river of news for Bob Dylan sites, and helping with setting up some WordPress blogs for Bob Dylan writing and ham radio writing. I also wrote up instructions to help others set up rivers of news for their areas of interest. The most exciting event for me in December was to see one of my posts (Is there a RSS revival going on?) appear in Stephen Downes’ OLDaily newsletter – wow!
    With this increase in posting, I am getting more and more in the habit of posting. If it is getting near the end of the day with no post, I work to at least find a link that I want to save on my blog. I have enjoyed playing with IndieWeb technologies like Webmention, and starting my “In The Car” podcast has been fun. I have even told John Philpin that I would love to be a guest on his new podcast – whoa! Finally, I have enjoyed reading and interacting with fellow bloggers on micro.blog, have had a taste of community, and I like it! I am looking forward to many great posts to come. Here’s to a great year in 2019 and a post a day!