Went out for dinner this weekend, and stopped by a local Sears store to see if there were any bankruptcy bargains (there were…). The signs outside said “Store Closing”. The signs inside reminded me of the Radio Shack bankruptcy…”10% – 50% Off Everything!”…”All Sales Final”…

My rivers of news

Following up on my post yesterday, here are a list of rivers of news that I have created:

  • FullBlastNews.com – An app I put together to display multiple rivers using tabs. Unfortunately, the theme has stopped working in some ways (it won’t jump to sections within the site), but is still a nice app.
  • ReadingList – My main list of sites I follow
  • OpenSourceBridge – A river I built for the 2017 Open Source Bridge conference (article on how I built the site)
  • 1999 Bloggers – A river of people using the 1999 blogging tool by Dave Winer

 

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!

I don’t know about the “data transmission” item as one of the top items needed for space exploration, but I would agree with space medicine and STEM education…

@Ron @JohnPhilpin this is a test status post from my WordPress blog, see if you can reply to this post in micro.blog, thanks.

Working with callbacks in Javascript

I am playing with the sample code for Dave Winer’s feedRead Github repo, and wanted to refactor one of the examples. I have seen multiple examples of a callback function source code included in a call to another function, but I wanted to have it be a separate function. Here is the example code:
[cc lang=”javascript”]
feedRead.parseUrl (urlTestFeed, timeOutSecs, function (err, theFeed) {
if (err) {
console.log (err.message);
}
else {
console.log (“It took ” + utils.secondsSince (whenstart) + ” seconds to read and parse the feed.”);
console.log (“theFeed.head == ” + utils.jsonStringify (theFeed.head));
console.log (“theFeed.items [0] == ” + utils.jsonStringify (theFeed.items [0]));
for (var i = 0; i < theFeed.items.length; i++) {
console.log (“Item #” + utils.padWithZeros (i, 2) + “: ” + theFeed.items [i].title + “.”);
}
}
});
[/cc]
After some experimenting, I figured out that all I needed in the feedRead.parseUrl call was the function name (with no parameters, even though it had parameters), and then the function could be factored out:

[cc lang=”javascript”]
feedRead.parseUrl (urlTestFeed, timeOutSecs, myparser);

function myparser (err, theFeed) {
if (err) {
console.log (err.message);
}
else {
console.log (“It took ” + utils.secondsSince (whenstart) + ” seconds to read and parse the feed.”);
console.log (“theFeed.head == ” + utils.jsonStringify (theFeed.head));
console.log (“theFeed.items [0] == ” + utils.jsonStringify (theFeed.items [0]));
for (var i = 0; i < theFeed.items.length; i++) {
console.log (“Item #” + utils.padWithZeros (i, 2) + “: ” + theFeed.items [i].title + “.”);
}
}
}
[/cc]

Note that the function does not have a semicolon at the end, but the call to feedRead.parseUrl does…

References:

https://codeburst.io/javascript-what-the-heck-is-a-callback-aba4da2deced

https://javascriptissexy.com/understand-javascript-callback-functions-and-use-them/

Getting some traction on micro.blog

I made a post on Sunday, and it triggered a nice stream of comments from people on micro.blog, all of which appeared as comments on my post. Cool! It looks like the webmention support on both ends is working well. As another step in WordPress/micro.blog integration, I am adding my comments RSS feed as a cross-posted feed. After I post this, I will add a comment and see if that appears on micro.blog. Let’s see what happens!

Wither the history of podcasting?

This week, I listened to episode 167 of the Radio Survivor podcast, titled “Alternative Histories of Podcasting“. The guest was Andrew Bottomley of SUNY-Oneonta, and the conversation covered the “popular” start of podcasting (Dave Winer, Christopher Lydon, Adam Curry, et al), and a look at audio available on the Internet before the 2004-2005 time period. The hosts seemed to take issue with defining “podcasting” as the technical tools making it possible to subscribe to audio files (podcasts) and easily load them to mobile devices (MP3 players, smartphones). I do not deny that the examples that Dr. Bottomley gave of Internet audio files pre-2004 were correct, but I think there is a reason why they were not called podcasting – because there was no “pod” available! For better or worse, the iPod was the first convenient audio player, iTunes was the first convenient way to get audio on a device, and the name “podcasting” grew out of the development of these tools and other tools of audio production and distribution.

I hope that Dr. Bottomley will document his research in this area (seems like he is working on a book). However, I am more interested in finding good podcasts to listen to, and playing around with creating podcasts myself. As Dave Winer has pointed out, creating and distributing podcasts is an open platform – anyone can do it. People can disagree on “who was first” or “what is a podcast”, but I want to focus on the practitioners, the people who are creating podcasts, no matter what the topic.