Scripting News

Google gets a patent on reading lists

Thu, 17 Sep 2009 13:08:13 GMT

Google will probably protest that the patent they filed on reading lists was defensive. But it's a bad patent, based on an "invention" that was already out there, being discussed openly on Scripting News at least a year before they filed it. If you can subscribe to a feed, why not subscribe to a collection of feeds? And when an item is removed, you no longer are subscribed to it, and when one is added, you are now subscribed to it.

Google should explain to the RSS community how they supposedly invented this and what their process was. If it turns out that we had prior art, they should tear up the patent and apologize from trying to hijack something that doesn't belong to them.

I worry about big companies doing awful things because they do them. It's dangerous to have Google control so much of the RSS infrastructure, from Feedburner to Google Reader to Blogger. They could easily pass information between those systems without sharing the information publicly. They could, right now, deliver features to users that competitors would be locked out of. All this built on ideas, formats, protocols and know-how that were contributed by others without any limits on how they could be used. And now this patent.

River2 in EC2

Thu, 17 Sep 2009 02:25:52 GMT

I'm working on an EC2 image that, when you boot it up, is a River2 installation. Since it's outside any firewall or NAT, it's ready to wire into the realtime feed network. Cloud-enabled feeds connect into Amazon's cloud. It's almost mathematical. I'm lovin it. I think we're getting close to the promised land. Hah.

I need a Domain Name Server with a REST interface

Thu, 17 Sep 2009 00:41:29 GMT

Here's what I need:

1. A server I can use to manage hosts for a domain that I own that am currently not using. I have many. I will pick one.

2. Ideally I don't even want to run the server myself. Someone from the community of people who read this blog who are interested in distributed realtime message systems and want to play a role in their development. This project will not use a lot of bandwidth or server resources. It's primarily for development. The other users will be geeks like you and me.

3. The server must have a REST interface. I need at least one call. It takes three parameters (that I can think of, there may need to be more). The three parameters are: name of sub-domain (something like george), record name (I'll explain below) and the value. The same call can be used to change the value. Probably should send a string that's a MD5 hash of all the parameters plus my password. Something like that. You can tell me what it should be, but nothing too fancy.

The record name is a DNS record name. Not A or MX maybe TXT. The value is the address of their cloud-enabled feed. So george.loose.ly would be the name of George Metesky's realtime feed. If you want to follow him, you wouldn't have to use his feed address you'd use george.loose.ly. The client would just do a DNS lookup to find his feed.

4. If no one is willing to operate the server, I'll operate it. It must be something that runs on EC2.

5. I need it soon. I want to start developing a prototype. Tomorrow? Friday? Please, no later than Monday. It seems like a fairly easy thing to do.

Anyway that's the idea. Comments welcome of course. And DNS gurus if I've made some egregious errors, please let me know, gently.

Do you have a cloud-enabled feed?

Thu, 17 Sep 2009 00:10:42 GMT

It's been over a week since Wordpress shipped their plug-in that added rssCloud capability. There are a bunch of feeds out there that are now cloud-enabled, actually a few million.

If you know of any especially interesting ones, news-oriented feeds that are frequently updated -- they could be pro or amateur, bloggers or BigPubs, commercial, academic or open source, left-wing or right, it doesn't matter -- what matters is that they are interesting and that they're real-time.

I'm looking for feeds to include in the default set of the next release of River2 which is coming together now. So if you know of some, either post a link as a comment here or send me an email with a link to the email address in the right margin on scripting.com.

What's wrong with this picture?

Wed, 16 Sep 2009 17:46:32 GMT

It took me a few minutes staring at it to figure it out.

With a hat-tip to David Rowland, iPhone developer, who sent it to a mail list I'm on.

Brad, let's get together

Wed, 16 Sep 2009 01:31:39 GMT

Brad Fitzpatrick did what I used to do, say what he really thinks in a blog post about RSS stuff. It's fine, but it is just his point of view. There are other points of view that are valid, like mine.

About "just happen to work at Google" -- come on, man -- how many people who don't happen to work at Google can add code to the following products: 1. Feedburner, 2. Google Reader, 3. Blogger.

Further, prior art is really important, it's how you keep the breadth of the pile of tech we create as small as possible, allowing us to build higher with the finite brain capacity each of us has. The cloud element was right there in the spec. And when we talked, you knew about it. So to say you never heard of it, well -- I think you had.

It's true -- I was pretty freaked when I saw the note at the top of your spec that RSS didn't matter. Sometimes I think Google really believes that. Now I'm here to say RSS does matter. You can't pretend it doesn't because it does. You blew every kind of smoke at it when we talked. That's really good motivation for a guy like me who takes pride in his work.

Now why did I get busy with rssCloud? Primarily because I wanted to remember how it worked. Once I got started, I remembered why I liked it, so I kept going. That's all.

Brad, we should get together and talk about bringing our projects together. This is what you were going to have to do whether I reactivated rssCloud or not, because RSS is there, and it's huge, and you were trying to ignore it.

Screen saver in Snow Leopard

Tue, 15 Sep 2009 17:20:50 GMT

Believer it or not there's been a lot of controversy about the screen saver in Apple's new operating system release.

I know this isn't something most people spend a lot of time thinking about, but I happen to think one of the nicest things about the Mac is its screen saver, cause I love high-res photography and one of the nicest ways to use great photos is to hang them on the wall on a 50-inch HD monitor and use the Mac screen saver to drive it. Try it sometime, you won't be disappointed.

That's why I was bummed when I did a complete fresh install on a Mac that's being turned into an art computer, first Leopard then Snow Leopard, when it appeared as if the "Choose Folder" option on the screen saver had disappeared. But I figured someone on Twitter would know what happened, and sure enough, Mike Murry pointed me to the new way of doing things.

There's a plus and minus at the bottom of the list. When you click the plus you can add a folder to the list. Nice little improvement. Used to be there could only be one folder, now you get as many as you like.

Just thought I'd leave a pointer here to anyone else who gets confused.

Monday morning stuffff

Mon, 14 Sep 2009 18:13:32 GMT

Chuck Barris used to announce The Gong Show as just some stuffff.

Of course our stuffff is very serious.

A new Rebooting The News with guest Dan Gillmor. One of our best. Dan drills into just what rssCloud is and realtime. He's one of the best interviewers out there. It was my turn this week to name inspirations, and I chose Young People, as exemplified by Blake Ross, Joe Hewitt, Matt Mullenweg and Joseph Scott. You can skip to the last five minutes of the podcast, it's worth listening to. Usually we choose older folk as inspiration, but we have to remember that youth, in the right hands, is itself inspiring.

I posted a proposed addition to the rssCloud walkthrough.

Typepad announced support for Pubsubhubub. I predict on Twitter that we will bridge it with rssCloud so support of one will get you compatibility with th'other. Earlier I admitted to being a dork and not seeing them as being in competition. After all, they're not commercial products. What I care about is decentralizing the realtime web, so we're not dependent on one company. Both methods accomplish that. The real problem is centralization.

Andy Oram at O'Reilly wrote a stirring ode to decentralization. At one time O'Reilly was a big proponent of P2P. Maybe they will be once again?

Zee is spelled Zed Eee Eee

Sun, 13 Sep 2009 17:40:48 GMT

My FriendFeed friend Zee is in town for a conference, and he's worried about how Americans will take to his name. At first I was puzzled. What's so hard about the name Zee, I wondered. I had only seen it spelled out -- Zee -- cause we've never talked verbally only digitally.

He explained: "I got a blank stare when I first said it in Starbucks. The barista asked, how do you spell that? I said 'Zed', 'E', 'E'. Received a blank stare. Then I said 'Zee', 'E', 'E', which then got him a little more confused."

Ahhh I get it now. His name is the same as the first letter in his name when you say it in American English. In British English there's no such confusion.

After a bit of back and forth I came up with a suggestion.

Make up some long incomprehensible name that begins with Z (how about Zarathustra). When you get the puzzled look, say "My friends call me Zee." They'll like that for two reasons: 1. They don't have to remember the name and 2. You said you want to be a friend. Americans generally like this.

Just a slice of life on the Internets.

Tornado

Fri, 11 Sep 2009 04:14:33 GMT

The former FriendFeed company now owned by Facebook did something very interesting today. They released Tornado which is the customized web server that runs the backend of FriendFeed.

I speculate in a thread on FF: "Just thinking out loud if there were a REST interface for the backend that worked like the REST interface for the client, I would be able to program both ends without having to learn the internals of your system. It would be really elegant, and probably wouldn't cost that much in overhead. I was able to create an interface to the client side of your realtime API in an hour or two. If I could sneak into the backend the same way that's all I'd need to at least put together a proof of concept. Does this make any sense?"

We need what their backend does to make the connection from rssCloud to desktops. This is something the FriendFeed guys mastered, and there's reason to believe it scales to the level we'd need since they are the guys who did GMail and Google Maps.

Interesting times we live in.

I also reminded people that when cool technologies are shipping everywhere it's not a time of death it's a time of life, as long as we have the web to connect our work, there's nothing exclusive about it. The engineers don't think we're wiping each other out, only the pundits and the hangers-on do.

Interesting times we live in.

And that's a good thing.

BTW, elsewhere on Facebook, our friend Blake Ross shipped Facebook Lite, which we heard was wonderful and are not surprised to find out is. Congrats all around!

Bad Hair Day at 7PM

Fri, 11 Sep 2009 01:00:55 GMT

We're having a special Bad Hair Day podcast which is a mini-reprise of last night's meetup in Berkeley.

Marshall is off tonight. I'll have two guests -- Doug Kaye of spokenword.org and Joseph Scott of Automattic.

Doug is working on a podcast aggregator that supports rssCloud.

Doug also founded IT Conversations that was a focal point in the podcasting bootstrap at the beginning of the decade. The Gillmor Gang got its start on Doug's network; we were inspired by his work.

Joseph developed the plugin for Wordpress that shipped at the beginning of the week. I haven't known Joseph a very long time, but we've already had a spectacular success, imho.

We'll talk about many of the things that were discussed at last night's meetup.

And for this podcast we'll have an IRC chatroom:

irc://irc.freenode.net/#badHair

Tune in at 7PM Pacific!

Twitter updating terms of use

Fri, 11 Sep 2009 00:21:09 GMT

Biz posted a list of changes to the terms of service.

They also published a draft of a short list of rules for developers.

Based on a quick read the changes seem reasonable, they reflect how the service is used and the role Twitter the company plays in it.

Clues for testing your rssCloud app

Thu, 10 Sep 2009 20:55:29 GMT

This is a frequently asked question.

If you're doing a cloud-aware app, a feed reader, skimmer or aggregator of any flavor or genre, you need feeds to test with. That was an issue a few weeks ago, but today it's not an issue at all. There's a huge variety of cloud-aware feeds updating all the time, for you to test with.

The original feed is one of mine that's announcing three new states every 15 minutes, day and night rain or shine. Not very interesting, but quite reliable.

Then there are the cloud-enabled feeds I've created from the people I follow on Twitter. Robert Scoble is the Old Faithful of this class. He's updating a lot, all the time. I have a changes.xml for all of these feeds, so you can see who's been updating.

Any of my feeds will also show up on the log page on my server, as will your registration. If you're not getting through you won't see anything there. It's very important for debugging.

And the new exciting way to generate a test feed is to create a wordpress.com blog, and post to it. Your feed has a cloud element and it will notify your app when you update. You control when it updates, so this makes it easy for testing.

InBerkeley.com, a Wordpress blog we host ourselves is cloud-enabled.

The feed for Scripting News is cloud-enabled as is the feed for Rebooting The News and Bad Hair Day.

Of course you should refer to the Implementor's Guide as you implement.

And finally, the punchline, the reason for all this michegas -- CNN has the first real news feed that's cloud-enabled. And it's a gem. When I got this one running in River2, I had to stop and pause and say, we got there.

Phil Jones on how things connect

Wed, 09 Sep 2009 23:23:58 GMT

Phil Jones and I agree on how bootstraps work.

He wrote a beautiful piece in 2006, and just re-ran it with links to 2009 bits that illustrate his points.

It's a case study in how Internet bootstraps work. They're about 10 percent technology and 90 percent working with people, trying to figure out what they want and getting it for them. In the process something builds out that has a cohesive whole, and another layer is formed.

A few years go by and we do it again.

I'm certainly not the only person who understands this process, I'm a student, and I've learned from many others that come before. I love reading books about how this works, and the latest inspiration was the Connections series by James Burke. He goes all the way back to the beginning of civilization and shows how ideas interconnect and build on other ideas.

In the end it really is all about working together. And I'm glad that Phil is there. It's nice to have someone watching who sees how it all fits together.

Then, this evening, a really insightful Webmonkey piece came out. It's the same insight that William Mougayar had, in a comment here yesterday. When this bootstrap plays out it will all be seen to have happened at the workstation. What Matt and Wordpress did over the weekend was the nuclear fuel that lit the fire. But the big winners will be the readers, skimmers and Twitter clients that will, as Webmonkey puts it so well: "We'll just have to stop calling them Twitter clients and start calling them what they should be referred to as: news clients." Amen.

Am I a hypocrite?

Wed, 09 Sep 2009 15:08:12 GMT

Sure. Of course. I am a totally f*cked up human being.

Now that that's out of the way, let me explain.

Last night on Twitter, Staci Kramer of PaidContent asked what's the difference betwen the default list in River2 and Twitter's suggested user list.

There's a qualitative difference and a quantitative one.

I use the default list for two purposes: 1. To provide an initial user experience that isn't blank. In this sense it is like Twitter's list. 2. To highlight interesting uses of RSS and clouds and reading lists, things I want to encourage people to support. By throwing them a bit of recognition, I hope to create an incentive to support the features that River2 is leading the way with. I did this with Radio too. I do it with Scripting News. I'm unabashed about it. It's how you bootstrap new stuff. It's a good thing.

No one has paid for position on the list, but I don't guarantee that I will never sell a position on the list. But I will never put a feed on the list that I wouldn't put there if they didn't pay.

Now for the differences.

1. My list is like the default list in Tweetdeck or Tweetie or Google Reader. I don't have a monopoly. I am not the only game in town. If people dislike my choices they can vote with their feet. Twitter is the whole ballgame. As I said yesterday, it's as if Google favored their friends in search results. Or if Tim Berners-Lee made it so that 1/4 of every web page had an ad for Om, ReadWriteWeb, Tim O'Reilly or TechCrunch.

2. I have a shopping list in my pocket. On it I list products I'm going to buy when I go to the supermarket. That's also like the Suggested User List. The products on the list profit from being there. But Chef Boyardee won't notice whether or not he's on my list (he's not). River2 is a teeny weeny little product compared to the mighty Twitter, which delivers hundreds of thousands of followers to people on its list.

3. I try not to influence editorial content through my choices. I've gone with big pubs like Reuters, BBC, the Guardian, CNET, NYT. Their techies hopefully will appreciate the respect, but if it influences the writers I will remove it immediately. In TwitterLand, the problem isn't so much that Twitter tries to influence, that's understandable, it's that the reporters don't object.

There will continue to be a default list in River2.

My code is a blog

Wed, 09 Sep 2009 14:42:26 GMT

Here's a screen shot of one of the objects that makes up the River2 aggregator.

The top of the script is a blog.

We've always done it this way. There are scripts in the system that are still in use with "posts" at the top that date back to the mid-90s. From lots of team members, most of whom have gone on to other things. I imagine they've taken some of our practices with them, as we inherited practices from teams we came from and code we used to work on. There's a culture to programming that's mostly invisible to non-programmers.

Another example of Narrate Your Work, the philosophy of the blogger and reporter.

Happy baby is happy!

Wed, 09 Sep 2009 00:06:58 GMT

Nothing more to say than what a hugely perfectly pretty happy baby!

She made me happy.

That's all.

What does rssCloud mean to you?

Tue, 08 Sep 2009 15:08:58 GMT

Okay I think it's time to explain what rssCloud means to people who use the web, as opposed to people who create it at a technical level.

The idea is to deliver news faster, without relying on a single company to do all the work.

Until now you could have one or the other, but not both.

You could have the news delivered via RSS, but if you wanted it fast you had to go to Twitter or Facebook or FriendFeed.

The problem with going to a company is two-fold: 1. The company might not be able to handle it. 2. The company might screw with it.

We saw both 1 and 2 with Twitter. Last summer they had trouble keeping the system up. They still "fail whale" a lot, and it could get worse, if they grow. Certainly if they grow to a billion users and become the "pulse of the planet" -- as they've said they want to. There are other reliability problems, like no good record of what's posted on Twitter. And all the trouble scaling has meant that new features show up in the center at a snail's pace, while the pace of innovation at the edges is furious, and limited by the slow growth at the center.

But even worse is that the company has not stayed out of the editorial flow of the community. At the beginning of the year, the basic metric, the Twitter equivalent of page-rank was follower count. Then all of a sudden some user's counts starting going up at an incredible rate. It came out that the company was recommending these people to new users. They were giving this flow to their friends, and to reporters who cover them, but not to people they don't know or don't like. They've even taken it away from reporters who have written stories they don't like. This is totally unacceptable, we've said so repeatedly. They ignore the concern.

Think about it another way. Imagine if Larry and Sergey's friends pages always showed up at the top of search results on Google, even when their pages had nothing to do with what people were searching for. Now you understand how un-Internet-like this is.

People say they're entitled to do this, and I suppose they are. But then we are entitled to take this idea and use the Internet to implement it, instead of all relying on a company.

That's how a techie like me, who loves the open-ness of the Internet, thinks.

To understand why, you have to understand that in 1993, I gave up on tech, because it was so utterly messed up by big companies fighting to control the users. A guy like me couldn't make software and sell it, because they were always screwing with us. They weren't doing it on purpose, they just didn't care. If you said "You should care" they'd call you a utopian or Mother Teresa and laugh. But in the end they got screwed by their own screwing around. The Internet straightened it all out, and newly charged with optimism, I learned something important. The tech world is cyclic. First it's wonderful, then it gets f*cked, then it gets wonderful again.

Our goal with rssCloud is to take what was wonderful about Twitter, that got f*cked by their Suggested Users List and the Fail Whales, and make it wonderful again.

I want everything fast with no company in the middle. That doesn't mean Twitter goes away, not at all. They just have to stop being in the middle.

That's what rssCloud is about. Fast news updates without the company in the middle. Small pieces loosely joined.

PS: And now maybe you understand why there was so much crap flying around RSS for the last few months. It always happens when the dam is about to break. No big deal. Just go right through it. The bark is worse than their bite.

Someone give Om an award

Tue, 08 Sep 2009 13:19:12 GMT

I just took a quick look at the RSS feeds of the major tech pundit blogs to see which had <cloud> elements.

I found one at Gigaom!

http://feeds.feedburner.com/ommalik

If you View Source you'll see it.

Something else worth noting, Feedburner preserves the <cloud> element. So two things are working!

I subscribed to his feed in River2 and it grokked his realtimeness. Oh life is sweet.

For techies, you might wonder why we received notification of an update after subscribing. That shows that Om's Wordpress installation is following the Walkthrough. You're supposed to test the notification handler before you register it. If it passes the test go ahead. If it fails, throw it away. This keeps the conversation real.

2002 != 2009

Tue, 08 Sep 2009 22:23:41 GMT

There's been concern expressed today in various Twitter messages that rssCloud might not scale to support all the people who might want to use it.

I'm not an expert in massive centralized systems, that's why I designed this to be decentralized, like RSS is.

I set up an rssCloud server, fairly confident that it would scale to meet the demand, and with a fallback if it shouldn't. I'm not risking anything, because we know that polling works for RSS. rssCloud is an optimization, its purpose is to make RSS faster. But if it fails RSS still works. As I wrote earlier, even though many people predicted in 1999 that RSS would never work, it's actually never failed, there is no RSS fail whale.

This is not my first time with rssCloud. My team at UserLand Software implemented it in 2002 in Radio and Manila. We had problems, but I've factored in what we learned in 2002 in the 2009 implementation. If you're interested in the details, I've spelled them out in the Implementor's Guide to rssCloud, which was published in mid-July and has been reviewed by dozens of programmers, and implemented by more than a few, including the people at Automattic.

I'm sure we'll talk about this at tomorrow's rssCloud meetup in Berkeley.