Scripting News

River2 is ready

Thu, 03 Sep 2009 22:58:09 GMT

Or as ready as it'll ever be. :-)

http://newsriver.org/river2

It's an aggregator that runs on your desktop and supports reading lists, rssCloud and is a podcatcher.

I'm sure there are bugs and know there are still features to come, but I and others are using it all the time to keep up with what's new in RSS feedland, and to download podcasts, and as more cloud-aware apps come online, we're going to need software that can subscribe to the. That's what River2 is for.

If you have questions or comments, post them here or on the howto linked above.

Here we go and good luck to all of us!

PS: Now I've hit my first milestone due before the rssCloud meetup next Wednesday. I have a few others to cross off the list. Wish me luck!

Hire execs who love the product

Thu, 03 Sep 2009 18:37:52 GMT

I've been in and around the tech industry since 1976, which makes me a 33-year veteran. The industry loops every 5 to 10 years so I've seen something like five or six iterations. There are some mistakes they make over and over. Wish I could tap them on the shoulder and say Don't Do It but it wouldn't make a diff. Every crop of entrepreneurs thinks it's different. They never are, but they have to learn that for themselves.

One thing they do over and over is hire execs who don't love the product.

It's as if the guy who ran professional football didn't like football. Or if Valentino Rossi didn't love MotoGP. Or the CEO of a vintner didn't like wine. Or if Alice Waters who runs Chez Panisse and is Berkeley's most famous entrepreneur didn't have a passion for great food.

Yet Twitter just hired a COO who has one of the most out-of-whack follows-to-follower ratios out there. He follows 40 and is followed by 650,263. This is probably why his RSS company, Feedburner, made it to be acquired by Google and then crashed. It wasn't built on a foundation of love for RSS (I can attest to that) and while the people of Twitter use it and they have very passionate users, the execs at Twitter, at best, dabble. And now we know they hire dabblers. (An instance of A people hiring A people and B people hiring C people?)

When your ratio of follows to followers is 0.00006151 it's inevitable that you see Twitter as a stage like the one Barack Obama stood on in Berlin or in Denver. "I'm up here," he must think, and "they're out there." His ability to understand how people see his product is limited because his view is of users as little dots, and he and his 40 insider friends loom large.

I've sat in board meetings listening to other board members explain our users, having never met one, having never used the product. Needless to say their advice is pretty general and usually wasn't very useful.

I've had it explained to me that cancer doctors don't have to get cancer to be good doctors, and of course I agree. But using a product like Twitter is supposed to be a joy. It's supposed to be an expansive thing, not a life-threatening one. And I'd add, every company that viewed its own products with fear fails. If you make a product that is not a disease and you treat it like one, people will find some other place to congregate.

Why I love my Sony Walkman

Thu, 03 Sep 2009 17:43:36 GMT

My mother has a friend who was raving about the new Sony Walkman, so I bought two, one for Mom and one for me. They're not expensive, and I've never been happy with the way my iPod worked for podcasts, which is 90 percent of the use I have for them.

Do I like it? I do! I've been using the Walkman ever since, and the iPod has become a hard disk for my BMW (which has an iPod interface).

I like the Walkman because it works way better, for me, than the iPod does.

The Walkman connects easily to both Mac and Windows without any weird dialogs that warn me that it's about to erase everything on the device. It presents as a disk drive. I copy files into the Podcasts sub-folder of the Music folder. When I'm out, I click the top-level Music icon then choose Folder, and navigate to the file I want and it plays. Click Next to go to the next one.

Back at home, next time I load it up, I just empty out the folder and copy in a new batch of podcasts. Or if I'm on the road with my Windows XP netbook, or traveling with my 13 inch MacBook Pro. Or in my office using my iMac. Or at a friend's house. You get the idea. It's totally not fussy about what you connect it to, and it never gets an idea that it knows better what should be on your device than you do.

My iPod ends up with all kinds of junk on it because even though I've been using one for seven years and I still don't understand how it works. I understood the Sony the first time I used it and it's never thrown a curveball at me. A few weeks ago I had to post here to find out how to get my iPhone out of shuffle mode.

Apple really does do nice user interfaces, but I think they either don't understand users, or don't like or trust them. The Walkman has lots of nice features, but it's nicest feature is that it's really simple.

BTW, last time I was in NY I saw that my mom had taken it with her on a walk and asked if she knew how to put new stuff on it, and she said yes. I consider this a major victory for tech!

Anyway it might not be for you. But a lot of people don't know that Sony now makes a good MP3 player. Hopefully I've done my part to help correct that.

RSS in your TV set

Thu, 03 Sep 2009 09:42:34 GMT

I am up late writing docs for the next River2 release and just got an email from Amazon about a new Samsung TV that has a built-in RSS reader. Here's a video report from CES 2008 where the TV was announced.

RSS is part of the fabric of the Internet which is now a feature of TVs. It's so cooool.

Is River of News enough?

Wed, 02 Sep 2009 18:43:39 GMT

For what seems like many years I was a lonely voice in the wilderness, whispering at first "River of News" then speaking more loudly and finally shouting from the rooftops, but people wouldn't listen. Developers patterned their "news readers" after email programs. Each feed was a box, and like a mail program it would tell you how many unread messages there were. "This is wrong!" I would say -- RSS is not mail.

Well in 2006 or so, things turned in the other direction and rivers showed up everwhere. They call them streams, lifestreams, etc, but they're all the same basic idea. Park yourself on the riverbank and watch the news flow by. If you miss something, not to worry, if it's important some new story will refer to it.

Then an interesting experiment, the AnnArbor.com switched its home page to be a river. Wonderful, fantastic, futuristic. A long time ago I predicted the front page of every news site would be a river. But now Joshua Benton at Nieman Lab asks, basically, is a River enough? Do you need some other structure to hang the news on? Yes, imho, you do.

The question comes up on Twitter, when you want to know the context of a tweet, because sometimes people string them together. 140 characters isn't enough to express a full idea, so you write three or four. By the time you're at number four, someone has usually tweeted you back asking what you mean. The answer is in #1 or #2 of the 4-tweet sequence. If you answer the question, you'll just beget more questions, so you hope the person is savvy enough to click on your name and read your full stream to get the context.

In the 1980s I ran a system called LBBS on an Apple II in my living room. We had the exact same problem, and found a neat solution. At first the structure was strictly hierarchic. The sysop, me, would start a discussion area, and users would post questions or assertions as first-level subs. People would respond, and those would appear in reverse chronologic order as second-level subs. Responses to those would be third-level and so on. This was an early threaded discussion system. But how to find the new stuff? For that I added what I called a Msg Scanner, a reverse-chronolic browser that ignored structure. It would keep a bookmark for every user, a high-water-mark, and when you'd jump into the scanner that's where you'd start. You'd keep hitting Next until you reached the newest message. And here's the cool thing -- when you wanted to see the context, just type / and you'd switch over into the hierarchic structure, on the same message.

News will work the same way, except someone who is skilled at organizing stuff will figure out where each piece goes in the hierarchy. This will provide the context, and you will also be able to find out What's New.

Anyone who used the LBBS in 1981, that's 28 years ago, will understand, but in this world it's still a new idea.

I wrote a narrative of this development process in 1988 when I was starting up UserLand Software.

Sorry I still hate Comcast

Wed, 02 Sep 2009 16:05:21 GMT

Hate is a word I've tried to wipe from my vocabulary, along with need. You don't really need more than air, food, water, a warm place to sleep, basic medical care. There are lots of things that are nice to have, like hugs and kisses and great sound systems and business-class-or-better. But needs are pretty basic things.

Hate? People throw that word around far too casually. The other day a rep of SXSW said that I had hated on them because I suggested they were taking money to keep me off the speakers list since 1998 or so. I had asked many times why I couldn't get in, and was met with a stone wall. So like all human beings, my mind filled in the blanks. I asked to be enlightened, if it wasn't a payoff, what was it? I offered to run a retraction if they would tell me the real reason. Stone wall again. Oh well. I don't hate them. The word I would use to describe my feeling about SXSW is frustrated.

But Comcast? I think that's the real thing. I'll tell you why.

Love and hate have a mathematical relationship:

hate = love + betrayed

I would love to have Comcast service, but I would never sign up for it again unless they apologized for the treating me so badly. And while most companies apologize when they screw up, I have a feeling that Comcast thinks I should apologize to them. And that ain't never going to happen.

Why write about this today? Well they're getting a lot of kudos because they try to fix their fuckups with reps who use Twitter to find unhappy customers. When I got fired as a Comcast customer, I was in contact with their Twitter caretakers. Not only couldn't they stop the Comcast machine from chewing me up and spitting me out, they had the gall to say they liked me while they were doing it! Now that's really asking for the hate.

Imagine a girlfriend dumping you, hard, and while she's doing it saying she likes you. Well fuck that shit bitch. <-- There's the hate.

But their service is much faster than my AT&T DSL. I pay my bills, in full and on time (as I did with Comcast), and they don't have Twitter accounts. They never cut me off (knock wood), and I never have to talk to a Twitter rep who likes me. Maybe I'm weird but that's kind of how I like to do business.

Learning from the fire of 1991

Wed, 02 Sep 2009 14:45:39 GMT

Fires are on the minds of Californians, esp ones who live in the hills, like the ones in Berkeley and Oakland.

In 1991 these hills burned. I watched the fire, safely, from a friends' deck on Potrero Hill. It seemed far away, but now I live here.

In the RTN podcast on Monday I asked Doc Searls if we could learn from the fires in Southern California.

Today, on InBerkeley, I ask if there are any old-timers who were here during the fire of 1991 who would share what they learned.

rssCloud meetup at UC Berkeley, Sept 9

Tue, 01 Sep 2009 00:20:36 GMT

The first rssCloud meetup in NYC in July was a great success.

Now we're ready for rssCloud Meetup 2.0, on Wednedsay September 9, 7-9PM at 110 South Hall on the UC-Berkeley campus. South Hall is the gothic brick building in the center of the UC Berkeley campus, just across from the iconic clock tower.

It's a 15-minute walk from the downtown BART station.

The meetup is open to all, but primarily for developers. The goal is to bootstrap the loosely-coupled 140 character message network. One that's open on all sides, so anyone can add an aggregator, cloud server or authoring tool, yet still have the feel of a centralized system. There may be tradeoffs, but the benefits of not having a company at the center of the network should create great opportunities for news organizations, innovative developers, designers, businesses, and users everywhere. Twitter is great, but we want something that works better for all of us.

We hope to see one or more new implementations come online before or at the meetup.

The way it'll work is: 1. I'll talk for 20-25 minutes, review the walkthrough, technology, philosophy, then briefly answer questions. 2. We'll go around the room and people will say what they're doing, and what kinds of help they could use. 3. Then an open discussion, and we adjourn.

There will be free wifi, but if it's like the NYC meetup you won't need it. This is a complex and interesting topic that seems to hold people's attention. But it's California and you never know, so bring your laptop, just in case.

If you know you're going to be there, please post a comment on this blog post.

Thanks to the UC Berkeley School of Information for generously offering to host this event.

Wanted: A simple DNS app for Mac or Windows

Sun, 30 Aug 2009 17:24:43 GMT

In the early-mid-90s there was a Mac desktop app that was a Domain Name Server. Here's how you'd set it up.

1. Put it in your Startup Items folder so it would launch at startup.

2. When it booted a window opens with a list of all the domains it was managing. Of course initially it was empty. You could click on the name of any of them to edit the settings in a dialog. There was a place to edit the name of the domain. A place to add an A record or a CNAME. (In other words it works more or less the same as any web app we use to manage DNS.)

3. An Add button at the bottom of the window. Click it and a dialog like the one in #2 would appear, except all the fields would be blank.

4. There was a text file that also configured the server, in fact the dialogs above just served to add, remove or change the text in the file. I suspect the file was in a standard format that all DNS's use.

Anticipating what people are going to say, yes, I know there's a DNS built into the Mac, but it doesn't have a graphic interface and the instructions for setting it up are ridiculous. I think the one on Windows has a graphic UI, but I can't find any comprehensible instructions that explain how to set it up.

A college classmate, Sandy Wilbourn, who I think of as a brother, is an expert in DNS, and he says the app I'm looking for doesn't exist. I threatened to write it myself, he advised against it. Oh man. What is it with these simple web services that we're allowed to use them through a web app, but they don't want us running our own. I'm going to run my own DNS at some point, and I'd rather do it sooner than later.

Someone is going to ask why I need to do this. I have a good reason. You can either take my word or pay me $1000 and I'll explain.

Update: Chuck Shotton points to MenAndMice's server for Windows, and JY points to CutEdge's server for Mac. Both appear to fit the bill. Thanks guys!!

Joe Hewitt on Bad Hair Day at 7PM

Fri, 28 Aug 2009 00:57:29 GMT

Our special guest for the Bad Hair Day podcast at 7PM Pacific is Joe Hewitt the author of Facebook for the iPhone. What a great day to talk with Joe!

You can listen live on BlogTalkRadio.

I had lunch with him yesterday in Santa Cruz. I said that if Facebook wanted to compete with Twitter they needed a vastly simpler version of Facebook. Little did I know that 24 hours later I'd be looking at it.

If you have any questions for Joe, please post them as comments here, and Marshall and I will try to get to them.

You can listen to the show live on BlogTalkRadio, and of course it will be available as a podcast from the badhair.us site.

Here we go!

My one sentence review of the Facebook iPhone app

Thu, 27 Aug 2009 22:13:17 GMT

I wish the desktop version of Facebook was this simple, fast and elegant.

Update: Believe it or not I actually had lunch yesterday with Joe Hewitt, the developer of this app. I said that if Facebook wanted to compete with Twitter they needed a vastly simpler version of Facebook. Little did I know that 24 hours later I'd be looking at it.

Another screen shot shows why a simplified Facebook kicks Twitter's butt.

Health care in a nutshell

Thu, 27 Aug 2009 19:38:34 GMT

Health care is a lot like a fire department or police department. You never know when it's your house that's going to be on fire, that's why everyone pays equally for protection, and the person whose house burns gets the "benefit" if you can call having your house burn a benefit (or getting very sick).

The main difference is that very few houses burn, but eventually everyone needs life-saving or end-of-life care. Every responsible person must pay for care, and basically only the truly rich (multi-millionaires) can afford to self-insure.

If you assume that everyone has to pay for health insurance, then the question is how much do you want to pay. In the US, our current system costs 16% of GDP and we get less care, in some cases much less care than other rich countries that pay as little as 9% of their GDP.

So we're making poor choices here.

Obama's plan is less comprehensive than the German, Canadian, French or Japanese plans. In each of these other rich countries, health insurance is a non-profit business. That doesn't mean insurance companies don't make money, they do, but not from health insurance. Obama isn't promoting that (although it's not clear why).

And for 40 million Americans they might as well live in the third world, for them health care is based on their ability to pay out of pocket. As long as they just get colds, they survive. As soon as they need more care, they either go bankrupt or become disabled, or die. This is their country too, they get a vote in how our system works. You're related to some of these people (unless you have no family). They're the ones who should be standing in anger at the town halls. And they're not all poor, many of them are middle class or upper middle class, they just happen to not be profitable for the insurance industry. These are the people whose houses burn to the ground when they catch fire.

The people who would vote against universal health insurance are stupidly cocky, because they will all need health care some day and for many of them it will not be there. Sometimes they're people who don't smoke or aren't obese, who don't have any personal bad habits. People get sick for a lot of reasons that no one understands. Maybe just bad luck or bad genes. In the wrong place at the wrong time.

Bottom-line, we could spend a lot less money on health care and take care of everyone. Instead we're opting on the worst approach, we spend a lot more, and a huge portion of the populace isn't cared for and the rest of us are treated not as patients but as profit centers. If you happen to need health care, you can't get it. This is some kind of way to run a country? Yikes.

If you want to understand what our options are, I highly recommend listening to the FreshAir interview with T.R. Reid, who has just written a book on health care systems around the world.

RSS is how the news flows

Wed, 26 Aug 2009 15:21:27 GMT

To Sam Diaz who says RSS was "a good idea at the time but there are better ways now," I have many things to say.

1. People confuse RSS with Google Reader. Let's be clear that there's a difference. Google Reader is an application that reads RSS-formatted data. There are many other applications that read and write RSS.

2. I think Google Reader was, on the whole, a good thing. It's probably the best reader of its variety. You have to go find the new stuff in Google Reader. I prefer a reader that finds the new stuff for me, and presents it in reverse chronologic order. This is known as a river of news reader.

3. Diaz more or less says that's his preference too. Interesting.

4. My newspaper doesn't tell me how many articles I haven't read going back to the date of my birth. I bet it would be in the millions. Why should I care. This was the worst idea ever in news readers.

5. The core problem -- so many programmers who write RSS software are not themselves news junkies. If they were they'd know when they got it wrong. News is about what's new! Show me the newest stuff first. Sorry to all the articles I didn't read, maybe in the next lifetime.

6. He may not use a RSS reader, but the news is still getting to him through RSS.

7. If all the RSS on the planet were all of a sudden to stop updating (key point) the news would stop flowing. Any news guy or gal who thinks they could get by without RSS -- think this through a bit more. We all love the Internet, but don't shut off your gas and electric because your computer and router wouldn't work without electricity. Same with RSS and news. RSS is how the news flows, whether you see it or not. If not RSS, something exactly like RSS.

8. The Internet is layered. New technology comes on line building on tech that already existed. RSS was like that. It built on XML and HTTP, which built on text and TCP/IP. The new things that Diaz likes so much, in exactly the same way, build on RSS.

9. When news authors don't understand how technology evolves, they propagate incorrect notions to everyone else, including would-be inventors, who have to figure it out for themselves, and then convince investors and partners they know what they're doing -- when they just read in ZDNet that things don't evolve at all. So Mr. Diaz does us all a disservice.

10. I object when technology writers tell the story of technology incorrectly. People say I should just be happy to see my name in the story, or in this case something that I fathered. No deal. I want the accurate story out there. I want people to understand how technology really works, because that's central to users being empowered by it, instead of being controlled by it.

Bonus: Marshall Kirkpatrick, my partner in the Bad Hair Day podcast (tomorrow 7PM Pacific) has his own excellent rebuttal to the Diaz piece.

Random Wednesday notes

Wed, 26 Aug 2009 15:08:57 GMT

Last Wednesday I did a Random Links post, and here goes another. A tradition begins?

Very little flamage over my What is an Asshole piece from last night. Guess people got the point. If you fail to understand Hitler, you deserve to get Hitler. Their only sin, beyond stupidity, is their inability to imagine that it could happen here.

What is an asshole?

Wed, 26 Aug 2009 02:17:14 GMT

An asshole is someone who says Obama is like Hitler because he wants everyone in the US to have health insurance.

These people are so stupid they need to be slapped in the face to wake them up. They need to have their mouths washed out with soap and be sent to bed without dinner. They need to be sent into hard labor and allowed to die of starvation.

Hitler gassed my people and incinerated them in ovens. Hitler came very close to wiping us out. Hitler was a monster. Hitler was the human race going insane on a mass level.

If you think Obama is Hitler you deserve to meet with others who agree with you, starving and freezing and dying in a cattle car, sitting in each others' excrement, on your way to a concentration camp and its ovens and gas chambers, along with your children.

You will not be allowed to bring your assault rifle.

How to fix URL-shorteners, part II

Tue, 25 Aug 2009 22:17:41 GMT

Last Wednesday I wrote a piece that explained how to fix URL-shorteners. Today, with the help of Joe Moreno at Adjix, I implemented it.

Here's how my new URL-shortener works.

1. Joe is running the shortener at adjix.com. It's the same one he's always been running, but it's got a few new features.

2. In the prefs for Adjix, I told it that I wanted to use my own domain, c.oy.ly. I also told it to write copies of all my shortened URLs to a bucket at Amazon, which I had given his app permission to write to. By using my own domain, one which I control the DNS for, and retaining a copy of all the data, I am fully protected against his service going away. And I can decide at any time to take over hosting of my own short URLs by directing the c.oy.ly domain to s3.amazonaws.com instead of partner.adjix.com.

3. When I create a shortened URL, I do it by calling an API routine that works exactly as the APIs of the other shorteners. I give it the long URL, some identifying information so it knows to associate it with my Adjix account, and it returns a token, which I smash together with http://c.oy.ly/ to form the shortened URL.

4. All this is done with a bookmarklet communicating with a web app on one of my servers. It then takes the title of the page I'm linking to and adds the full URL from step 3, and redirects me to twitter.com, where I can edit the tweet before clicking on Update.

5. Then, every few minutes I call the Twitter API and ask if Dave has posted any new tweets. If so, I parse them, store the long and short versions of the URL in my database (by dereferencing the URL). Then I call a second API on Adjix to ask it to give me the counts for the most recent 50 links created by Dave. I then update the counts in my database, sort them, and prepare the familiar Top-40 report.

Bottom-line: I am now using URL-shorteners in a way that does not make the Internet suck. I have done my good deed for the day!

Dear Disqus: Can I have the old interface back?

Tue, 25 Aug 2009 19:25:56 GMT

Near as I can tell there are no new features in the new interface. Things were just moved around and everything is way way slower. The UI was always bizarre, but I figured most of it out. Now you're telling me I have to learn it over again? Why? What's the benefit?

All I know now is that my bookmark to the dashboard broke, and to get to the unapproved messages or spam messages, the maintenence I have to do on a regular basis to keep my site working, I have to wait minutes for the page to load. I don't have any idea if there are any new features in this to justify the pain.

I would really like to go back to the way it worked this morning. You know, when it actually worked.

How to get Lessig to blog

Tue, 25 Aug 2009 14:23:04 GMT

It's sad that Lessig is "hibernating" his blog, but there's always hope. It's easy to say goodbye, but what's he going to do when he has something that has to be said right now. Wait two years to write and publish a book? I sure hope not!

In his supposedly last blog post (heh) Lessig points to his first post, which was a response to something I wrote in response to something he said. In 2001 and 2002. It's interesting to recount the exchange, because only seven years later things have changed a lot.

1. First Lessig tells a story of Hemingway and source code, an analogy that I feel is flawed. And I say so, very strongly, but hopefully not in a personal way.

2. Then in August 2002, I expanded it, and on re-reading it -- I said some things that were a bit too much. A difference of opinion between two learned people shouldn't involve throwing people out and "up yours."

3. This got Lessig to write his first blog post! So there is a silver lining.

Now the hindsight.

1. In 2002 I said in five years every member of the US House will have a weblog and will be communicating directly with the electorate. I'd say that's been realized now, only they're using Twitter and Facebook and blogs, and they have to communicate directly with the electorate because the news industry is crumbling.

2. The controversy betw Lessig and myself in 2001 and 2002 was over whether software developers should be required to release their source code to get copyright protection (at least that's how I interpreted it). I was vehement in saying no, that we were already putting our ideas out there and that putting the source code out there too would give us nothing to sell. I still believe the logic of that, but since then I gave up on commercial software and in 2004 I released my main work under the GPL. There was no parade, no new respect or even thanks from people outside the community that already used the software. Did it inspire any young would-be designers? Time will tell, but it's looking doubtful. Just saying it's harder to influence the future than it should be, or maybe not -- who knows.

3. I like to think that Lessig and I have now become friends. Just goes to show that when there's a spark between two people, it may express itself in a variety of ways. I admire Lessig, I've come to see him as an open-minded, generous person who really listens. All good things!

4. I don't believe for a second that he's given up blogging.

Urgently need an Intel build of OPML Editor/Mac

Tue, 25 Aug 2009 13:15:51 GMT

I thought about writing a more creative headline, but opted instead for a direct request for help.

1. Yesterday I pre-ordered a family pack of Snow Leopard. As I understand it, the new version of the Mac OS will run PPC apps only with special software loaded, the way earlier versions of the OS ran Mac Classic apps.

2. The OPML Editor for the Mac is a PPC app.

3. It is also an instance of the GPL'd Frontier kernel, which I understand has been converted to be an Intel app.

4. I can build the Windows version of the OPML Editor. However, I cannot build the Mac version. It's been a long time since I worked at the C level, last time I did was with THINK C on the Mac in the mid-90s. I've tried to build the Mac app on XCode, but I always hit a problem that I don't know how to work around, and honestly I don't want to struggle at this level. I'm going to stick to developing in the OPML environment. When I can do a kernel build on both Mac and Windows, I may look at working inside the C codebase.

5. I need someone to get a build of the Mac OPML Editor together asap and to do some basic testing to be sure it works with the current opml.root.

Resources: The Frontier Kernel project website. Source download of the OPML Editor from August 2008.

Thanks in advance!

What's in the next release of River2

Mon, 24 Aug 2009 17:18:54 GMT

The first release of the River2 aggregator was all about CSS. I wanted to be sure this new aggregator would be buzzword compliant and user-configurable. I wanted the design community to have their way with this tool.

The second release has a completely different set of goals, they relate to the subscription engine, realtime processing of updates, and podcast support. Specifically...

1. Dynamic reading list support. A reading list is an OPML file that contains a subscription list that is read every time the aggregator scans its feeds. Any new feeds are subscribed to, and any feeds that are no longer in the list are unsubbed, assuming they aren't in another reading list or were independently subscribed to. This feature has been in my aggregators but not in most others. Google Reader, for example, does not support this feature, but imho it should. I'm putting this out there to help lead the market.

2. Fully rssCloud compliant. If you subscribe to a feed that has a cloud element, and you aren't behind a firewall or NAT, River2 will request notification, so that updates are received in realtime.

3. A podcatcher that's not from Apple. The market needs more than one podcatcher. So if you subscribe to a feed that has enclosures, it will download them into a folder of your choosing. This works for photo feeds as well as feeds with audio and video.

Tying it all together, here's a reading list that contains podcast feeds, one of which is cloud-enabled.

This release is not ready for download yet. Because I got a bad cold, and was sidelined last week, the project was set back by a week. But developers are moving ahead with their rssCloud implementations, and will need something to test against. That's one important role of River2, it represents a reference implementation of the client side of the rssCloud protocol.

What's next after this River2 release? More cloud-enabled feeds. An editorial tool that produces cloud-enabled feeds.