Scripting News

Nice to be #1 at something

Tue, 02 Oct 2007 00:28:07 GMT

Fred Wilson noticed that on the new TechMeme list, his blog is the sixth written by a person. Mine is first.

Ben Metcalfe raised a similar question earlier today, noting that TechMeme didn't differentiate between professional publications like the NY Times, Reuters and CNET and TechCrunch, Engadget and GigaOm. It's not clear what the distinction is. I don't see any of those pubs as being blogs, so I think Gabe did the right thing, just lump them all together and let god (or mashups) sort them out.

A pragmatic question for people who want to follow the TechMeme LeaderBoard -- it's clearly not practical to look at it as frequently as it could change, every 20 minutes.

So what kind of tool do we need to tell us about change? Email notification? An RSS feed for each site? I'm interested in knowing what people think.

Speaking of being #1, this blog is first on MSN for bricked iPhone. Needless to say it's generating a fair amount of traffic.

Optimizing Flickr RSS reads

Mon, 01 Oct 2007 23:16:40 GMT

There's a lot you can do with the Flickr API, I've pretty much mastered it, and it may look a bit intimidating at first, but it's well designed, and once you learn how to do one set of calls you pretty much know how to do the others. I would have relied more heavily on XML-RPC encoding for uploading pictures, but now that I've been uploading pictures for a couple of months, the pain of developing that glue is fading.

BTW, I've got glue for the OPML Editor, it should work well in Radio or Frontier. I've exported a snapshot of the system.verbs.apps.Flickr, for all to use. It may be included in any distribution. (To be clear, OPML Editor users don't need this, it's already in the update stream, just choose Update opml.root from the File menu.)

Anyway, I want to expand the Flickr/Twitter experiment, but before I do that I wanted to check with the Flickr folk because this service does a lot of polling of their RSS feeds. I suggested it might make sense to create a service that would allow a caller to find out which of the feeds its interested in have changed since the last time it checked.

They responded with a simpler feature, they implemented a Last-Modified header on the RSS feeds, so that you could skip processing if a feed you're interested in hadn't changed. I've now updated my code so it does that, and everything seems to work. You'll find the script at Flickr.readFeed. Here's a text listing of the script.

A new top 100?

Mon, 01 Oct 2007 12:43:39 GMT

12PM: The TechMeme Leaderboard site is live.

Like almost everyone else, I keep track of who's pointing to me in Technorati, a service that was created in a Thanksgiving programming binge by David Sifry, based on the output of (my own labor of love) weblogs.com.

Technorati grew to become a blog search engine, and much more, but as Mike Arrington points out on TechCrunch, their unique position has been whittled down by other blog search engines who are doing a better job technically. Not hard, since Technorati is famously unreliable.

Technorati is also famous for its top 100 list, ranking blogs according to the number of in-bound links. Scripting News started out as the #1 blog on Technorati, and occupied a top 10 slot for a long time, until they changed the algorithm to place less weight on long-term links, so Technorati's list became a measure of recent popularity. News sites, that aren't actually blogs (imho) became the mainstay of Technorati's list. Today, Scripting News is solidly in the second 100 on Technorati.

Last night Mike Arrington got a scoop, as he so often does, that there's a new list coming soon, from TechMeme, that ranks the sites based on some other measure, which is not (yet) understood in detail. Mike also has a screen shot, which teases, by showing that TechCrunch is number 1 (all those scoops make a diff) followed by Engadget and the New York Times. The Techmeme list doesn't pretend to know what is a blog or isn't they rate all sites regardless or race, creed or color.

But Mike's screen shot teases, stopping at #30. What about the rest of the list? There are a hundred or more bloggers who want to know if they made the list, and if so, where they are. Brilliant marketing by Gabe, and damn you Mike.

So I begged Gabe for the list, and he relented, and sent me an OPML file containing the data which I then turned into the list below. Enjoy!

  1. TechCrunch

  2. Engadget

  3. New York Times

  4. Ars Technica

  5. CNET News.com

  6. Read/WriteWeb

  7. GigaOM

  8. BBC

  9. InfoWorld

10. Wall Street Journal

11. The Register

12. Reuters

13. Silicon Alley Insider

14. paidContent.org

15. Between the Lines

16. Gizmodo

17. Google Operating System

18. eWEEK.com

19. Search Engine Land

20. Computerworld

21. Crave: The gadget blog

22. Associated Press

23. TorrentFreak

24. Webware.com

25. VentureBeat

26. The Unofficial Apple Weblog

27. Business Week

28. CrunchGear

29. Business Wire

30. Google Blogoscoped

31. Techdirt

32. Microsoft

33. Bits

34. Rough Type

35. DailyTech

36. Scripting News

37. mathewingram.com/work

38. PR Newswire

39. CenterNetworks

40. The Boy Genius Report

41. ZDNet

42. Guardian

43. All about Microsoft

44. PC World

45. Wired News

46. Inquirer

47. AppleInsider

48. Epicenter

49. Tech Trader Daily

50. Washington Post

51. Forbes

52. Bloomberg

53. Times of London

54. Apple

55. BoomTown

56. InformationWeek

57. Publishing 2.0

58. Scobleizer

59. A VC

60. iLounge

61. Download Squad

62. All Facebook

63. Financial Times

64. Boston Globe

65. Electronista

66. Yodel Anecdotal

67. apophenia

68. Official Google Blog

69. Google Public Policy Blog

70. USA Today

71. Compete Blog

72. AdAge

73. Apple 2.0

74. WebProNews

75. Mashable!

76. New York Post

77. Googling Google

78. iPhone Central

79. Todd Bishop's Microsoft Blog

80. NEWS.com.au

81. DigiTimes

82. Digital Daily

83. BuzzMachine

84. comScore

85. Security Fix

86. CNN

87. Andy Beal's Marketing Pilgrim

88. NewTeeVee

89. istartedsomething

90. Think Secret

91. ProBlogger Blog Tips

92. Reflections of a Newsosaur

93. GNUCITIZEN

94. O'Reilly Radar

95. MediaShift

96. ipodminusitunes

97. Doc Searls Weblog

98. Kotaku

99. Valleywag

100. Los Angeles Times

PS. This is a snapshot taken last night. The list is fairly volatile, according to Gabe, and will change quickly as stories move up and down the ladder at TechMeme.

PPS. The existence of this list will probably make getting stories on TechMeme even more highly valued than before, if this list is taken as gospel, as Technorati's was, even with its flaws and skews. There was no correlation, for example, between flow and rank, a site with very high flow could have very low rank on Technorati, if it didn't get many inbound pointers. It was just one measure, as TechMeme is just one measure.

The end of the road for Office?

Mon, 01 Oct 2007 17:42:40 GMT

Since the re-rollout of Office in 1996, it's been really clear why Microsoft was so hell-bent at first owning and then suffocating the web browser, along with the web.

Tim Berners-Lee understood, before there was a Mozilla and a Netscape, he said the web was inherently a two-way medium. We struggled against the inadequacies of MSIE as a writing environment when blogging was booting up in the late 90s and early 00s. The air was mighty thin, which was no accident, Microsoft deliberately tried to keep us from breathing. Because for them, writing was not something that would be done in a web browser, if they improved their browser as a writing tool, that would be the end of Word, and with it, a big reason for using Office.

Synopsis: Microsoft wouldn't let MSIE become a decent writing tool, because they were protecting Office.

That eventually had to run its course, they couldn't hold back the inevitable forever. Sooner or later the web would route around their roadblock, and we'd be writing on the web, as we are today. It didn't happen the way I wanted it to happen, with decent writing software built into the browser, rather through the ingenuity and peseverence of programmers who managed to make HTML and Javascript approximate the user interface of a desktop app closely enough to make simple writing tasks work inside the web browser. It probably helps that today's computers have gigabytes of internal memory and several gigahertz of processing power. If instead, Microsoft had embraced the web, and with it the shift in their product line and economics, in 1995, we'd have a much richer writing environment today. Blogging would have happened sooner, in a bigger way. It's hard to imagine how much the sins of Microsoft cost all of us.

I won't shed a tear for Office. Good riddance, I say.

I use Google spreadsheet happily, even though it doesn't have anywhere near the features of Excel, and is way slower. Every sacrifice I make there is something I'm giving back to the web to heal the Microsoft wound.

However, we traded one monster for another. It seems there must always be a certain amount of evil in the tech business. The Java Wars are behind us, as are the Browser Wars. No one is going to fight Google in the next war, I doubt if many will even protest.

Payloads for Twitter, round two

Mon, 01 Oct 2007 00:09:59 GMT

On Friday evening I wrote a piece about integrating images, audio and perhaps other types with Twitter. There's been a bit of reaction, not too much, I think because most of the people who are adversarial about this kind of stuff either don't use Twitter, or because it's the weekend.

Most of the reaction was either puzzled or negative. An example of puzzlement. Isn't that what Pownce does? Yes, but... Two things: 1. Pownce is still invite-only and 2. Pownce doesn't have an API, so it's inherently not as interesting to me, as a developer, because I can't build things on it.

I like Twitter because it's open to anyone to use, without an invitation, and lots of people use it, people I care about, and it has a very nice API. Further, as I've gotten to know the people involved, I've learned that the API is of supreme importance to them. So our interests are in-line there. I see Twitter as a framework to build things on, a platform, like a big Christmas tree we can all hang ornaments on. I could build nicer ornaments with a few extra wires on the network that connects all the ornaments. In fact, I've already built two of them, and we use them all the time. But I couldn't ask too many people to use them because they're too ugly. What I've proposed is a way to make them pretty, to make them work the way people expect them to.

Now another form of pushback is, well why don't you just build your own framework, different from Twitter, that does what you want, and leave Twitter alone. To which I say, I can't do anything to Twitter, other than talk about it. Whether to build the interfaces or not is up to the people at Twitter. I can have an opinion, yet ultimately the decision, and responsibility is theirs. Now, why don't I clone it? Well that's something I'm just not going to do. I have relaxed lifestyle these days. I'm beyond the point where I feel the need to prove anything through my work. I like to play and try out new ideas, just for the pleasure of it. If I were 20 years younger, I probably would be approaching this differently, but I'm not 20 years younger.

No doubt there are people, lurking in the shadows, who would like to share some of Twitter's success. The idea is so good that we're just at the beginning of its adoption. Maybe there are as many as 50,000 people regularly using Twitter. I think in a few years there will be millions, using Twitter, or something very much like it.

But we're at a unique place in the evolution of this stuff, which in some ways is very good. Suppose there were 20 Twitter-like systems out there, and we wanted to add a feature to all of them. Forget it! Developers just don't like working with each other enough to overcome their competitive urge. But right now, with one player in the market, we could make 10 times the progress we'll be able to make when there are 2 or 3. And a million times the amount in a market with 20 Twitter-alikes.

Further, the richer the API is, and the more broadly supported it is, the greater the incentive for newcomers to be compatible with Twitter. I don't get the warm fuzzies from Pownce that they are willing to follow anyone's lead, even though they don't yet have an API. But if anyone out there is brewing another entrant, and reading this, please please be compatible with the Twitter API. Not just the spirit, but the letter. Make sure that all the tools built for Twitter run without modification on your system.

So these are just some of the additional thoughts. Evolution of APIs is an art, not a science. I've learned a lot about it before the Internet, and then in XML-based formats and protocols. We're at a sweet moment right now, and if the Twitter guys want to lead, and if the rest of us are willing to be led (I am) then we can really build something wonderful.

Will the US bomb Iran? Soon?

Sun, 30 Sep 2007 23:31:54 GMT

There is a lot of random speculation in my aggregator today about "surgical" strikes by the US in Iran. It's unthinkable that the same process that led to the disastrous occupation of Iraq could stand, uncorrected, and get us into a much more serious conflict with Iran, one which we won't "win," (Bush's plan for Iraq, ludicrous) no matter what we do. When will we take control of our government and stop this?

Google search for "surgical strikes Iran."

The Mets on the last day of the regular season

Sun, 30 Sep 2007 17:35:25 GMT

I tuned in the Mets game a few minutes late, and they're already down 5-0 in the top of the first. Ooops. It's now 7-0.

The Mets don't have to win to make it to the postseason, if the Phillies lose. If that happens, they'd be tied, and would play a tie-breaker, winner-take-all game (I think tomorrow).

When Mets fans get a sense of entitlement, they break your heart. The Yankess are the entitled ones. The Mets are hapless.

"The nightmare is over for the Mets," says the announcer at the end of the Marlins at-bat. No, it's not over until it's over. A big lesson in the philosophy of baseball.

In all my years following the Mets I don't think I've ever seen them win easily. For that matter, I don't think I've ever seen them lose easily either.

As the Mets score their first run of the day, I'm reminded of Tug McGraw, an early Mets philosopher, who said "Ya Gotta Believe." I believe this is one of those moments when believing might make a difference.

Final: Mets lost, Phillies won. No joy in mudville tonight. :-(

Notes on the N800

Sun, 30 Sep 2007 02:11:22 GMT

I still didn't have the N800 working reliably on my home network, but it worked everywhere else I tried it, so I was determined to figure out what was wrong. I heard about a program called Kismac that helps you debug wifi, and it was a little bit of help. But the tide turned when I decided to turn off wifi routers (I had four running) and see if the N800 would start working. Well, one of my two Airport Extremes made the difference, when I turned it off, the N800 started working. So after a bit I tried turning it back on, and the N800 still worked. No explanation, but knock wood, it's still working an hour later.

One nice side-effect of having Flash on the N800 is that YouTube works. I was able to watch the great MoveOn ad about Senator Mitch McConnell. It looked great on the N800.

Now I'm looking for a VNC client. I'd also like to play old TV shows on it, but the video player doesn't have the rich set of codecs baked into VLC which has spoiled me.

Battery life on this thing is outstanding.

Payloads for Twitter

Fri, 28 Sep 2007 21:49:04 GMT

Back in 2001, I wrote a document called Payloads for RSS that explained how you could attach something to a RSS item. I didn't explain how a RSS app would display or play one of these things, that would come later.

Today, we may be at a similar place with Twitter.

Sometimes I want to answer Twitter's question, "What are you doing?" with a picture, or a bit of audio. Some people want to send videos. It's easy to imagine in the future that along with a Twit, I might also want to automatically send my location (obviously a preference), and maybe some other status information.

It seems that four bits of data are stored with each post: 1. the person who posted it, 2. the time it was posted, 3. how the post came to Twitter (web, Hahlo, Twiku, txt, twitterrific, twittergram are some examples) and 4. who it's in reply to (if it is).

Now suppose I wanted to allow for payloads, as RSS 2.0 does. The problem is a bit more complicated, because not only do we have to specify how the data is communicated, we also have to say how it's displayed.

Caveat: This is just a proposal, there are many ways to do it, this is just one way.

First, the "update" routine, as specified by the Twitter API, would add 2 optional parameters: 1. the url of a picture that's a thumb for the enclosed data and 2. the url of the data.

A couple of examples...

1. For Twittergrams, which are audible tweets, recorded on a cell phone, the image would be a small speaker, . The second paramter would point to the MP3 file.

2. For a Flickr pic, the image would be a tiny thumbnail of the picture, and the second paramter would point to the Flickr page.

Discussion...

I thought the whole thing could be shrunk down to one paramter, a pointer to a bit of text that Twitter would trustingly display, but that's the problem, you have to trust the app not to break Twitter, and we all know that wouldn't last. Even a well-intentioned delveloper can forget to close a table properly, and that would leave the Twitter display in disarray.

I also thought we might register data types with Twitter, but that's a likely black hole. Apple went down that path, so did Microsoft and the IETF. It's a lot of work to make those systems work, and it's just a matter of time before they break down in chaos.

I think that Twitter should probably handle two or three types specially because they are so common and useful. Those are pictures, audio and possibly video. But that's potentially a lot of work, and can be done later.

Some will object that this only makes sense in the web, and that Twitter is designed for SMS. To that I say two things: 1. Degrade gracefully. 2. You already have features that make sense only in the web, e.g. the pictures next to posts that show iconically who's saying what. That's a nice thing to have in the environments that can display pictures, and its presence there does nothing to diminish the experience for the environments (e.g. SMS) that can't.

Today's links

Fri, 28 Sep 2007 18:18:32 GMT

Ian Kennedy does a view-source on the NY Times and finds there's a lot of metadata in there. Cool!

Dustin Sacks has feature requests for Flickr, some very good ones, esp a Referrer log. Twitter needs this too.

Jeff Jarvis on newspaper blogs.

Republicans: A betrayal of trust

Fri, 28 Sep 2007 02:39:54 GMT

Excellent ad. They picked up the "betrayal" theme from the General Betray Us ad, and addressed the Republican's objections, by directing the betrayal theme at an obvious "Washington politician," Senate minority leader Mitch McConnell. It'll be interesting to see how the Republicans vote next time. Not claiming they read my advice, but it's almost exactly what I asked for, and I think it'll work well.

If you like the ad, give MoveOn money to run more ads.

Apple updates iPhone. Legal, unhacked phones become bricks?

Fri, 28 Sep 2007 00:08:20 GMT

According to Saul Hansell at the NY Times, Apple intends to break phones that have been unlocked.

But Francine Hardaway and Patrick Scoble both updated this afternoon, and bad things happened. Hardaway's phone was "fried," she needed a new phone, and Scoble lost all his data.

Hardaway: "Trust me, I didn't hack it."

Jeff Clavier: "This effing piece of s..t is bricked."

Robert Scoble, Patrick's dad, updated successfully, and got the new features. Scoble has guts.

Spaley's iPhone is now "a useless piece of crap."

Looks like Josh Bancroft's iPhone was hosed too. I would hold off on the update until we find out what's going wrong.

Sugar Attack: "It wasn't until I saw a friend tweet about the new iPhone firmware upgrade that I realized I could now access the iTunes WiFi store."

Twitter is taking a shower tonight

Fri, 28 Sep 2007 01:10:30 GMT

I love Twitter, but there have been a lot of problems, and this is too much. They're taking it down tonight, for two hours, and we're hot on a big story, and it's developing -- on Twitter.

This seems like a bad night for Twitter to go to sleep. (But there probably never is a good night.)

I don't think the Twitter guys really understand how much we're doing with their service.

It's been going down a lot lately. And while other people have been complaining about it losing posts, I had never seen it lose one, until yesterday, and now it's losing them regularly, for me too.

Read the first three words of this post again.

They raised $5 million, it seems now it's time for them to get the bugs out, hire some people who really understand scaling, if necessary re-implement the system from the ground up. Do whatever is needed to make it as reliable as the other tools we depend on. We need Twitter to work. It's not a fun experiment for us, we're using it.

Jack, Ev, Biz, Fred -- please take note.

Postscript: The announcement changed, now they're saying it'll be down on Sunday night. Much better. Thanks!

Good morning Internet!

Thu, 27 Sep 2007 15:10:00 GMT

An interesting discussion popped up on Flickr under the picture of the N800, which arrived yesterday. I'd like to get to the bottom of the problem and get it working. What I really want to know is if there's an Apache running on the device. If so, can the camera drop pictures into the htdocs folder? Can I record a podcast? Will it drop the MP3 file into the htdocs folder? We may just have to wait for Bug Labs to get the user programmable hand-held, but after a night of sleep, last night's failure is fading out and a teeny bit of enthusiasm is returning. But first I have to go to breakfast and do a couple of meetings.

Postscript: Apache for the N800.

Postscript: The N800 works at a local Internet cafe. I was able to browse the web and make a Skype call.

Finally: This thread had the answer... I have it running with no security, but it works, with the settings tweaked as indicated in the thread. I will have to get it working with security, but for now, I am able to connect.

Nokia N800 arrives, finally

Wed, 26 Sep 2007 23:23:49 GMT

First impression is no impression at all.

So far they make Apple look very very good.

To paraphrase a Cadillac ad, when you turn your mobile device on, does it return the favor?

Apple, yes. Nokia, the jury is still out.

A couple of hours later, the battery is charged, but it's taking forever just to get it connected to the Internet. I have good wifi in the house, my laptops and iPhone use it all the time. The iPhone "just worked." Oy.

Oh the humanity. To update the N800 you need Windows, with v2 of the .NET Framework. Yeah, I have Parallels on my MacBook, but I recognize an invitation to lose huge amounts of time when I see one. For a $350 impulsively purchased toy (a week ago) this is turning out to be a huge pain in the you know what.

Media you can't trust

Wed, 26 Sep 2007 14:57:07 GMT

I saw most of the speech given on Monday by Iranian President Ahmadinejad at Columbia University. I also watched a lot of the coverage that night and the following morning by MSNBC and CNN, and I gotta say, they behaved shamefully, as badly as Lee Bollinger, the president of Columbia University, who introduced Ahmadinejad.

Transcript of the Ahmadinejad speech.

Video of the entire talk and intro. 1 hr 21 min.

Ahmadinejad came off as a gentleman, he had every right to be offended. Had I been in his place, I would have found it hard to give a speech after the intro Bollinger gave. And then the cable networks completely misrepresented what happened. It was beyond spinning, it was outright propoganda. It wasn't until Hardball that a reporter, Chris Matthews, talked about what really happened.

It's basic decency to the guest and to the people watching, that they not tell us what to think. It's a very American thing to let people make up their own minds. That Ahmadinejad was able to claim this as an Iranian value, when it was so clearly not an American one that day, was shameful to me as an American.

What if Columbia had maintained neutrality. Asked direct questions, accepted his answers and moved on. We got the tiniest glimpse of how revealing that might have been when he said that Iran didn't have homosexuality. The audience laughed as if he was making a joke (not in derision as the TV anchors reported). At first it wasn't at all clear if it was humor, his delivery was so straight, he seemed serious, but how could he seriously expect us to believe there were no gay people in Iran?? When it was clear he wasn't joking, it was a chilling moment. There it is, that's the face of despotism. Now we know, despite his protests, that we're still better than he is, I haven't heard the US government claim that there are no gays in America (but I have heard them say things approaching that level of dishonesty).

Had they just let Ahmadinejad speak for himself there would probably have been no need to hit us over the head with what they want us to think about him. But as it stands, that was the only clear thing he said at Columbia that wasn't basically reasonable.

His pitch: I come from a place that's far away from here. You sent your army to fight on our border. We don't like the Israelis because they mistreat the Palestinians who had nothing to do with the Holocaust (a far cry from saying the Holocaust never happened). It's pretty clear, although he didn't say it, that given a choice, he would like to see the Palestinian people rule the space now occupied by Israel (this is probably what they mean when he says he wants to "wipe" Israel off the map). So, that's not our position, but it's not really different from ours. The reality is that there are two peoples who claim that territory. So Iran is on the other side. That's not exactly front page news.

An aside, very few Americans know the role we played in overthrowing Iran's attempt at democracy in the 1950's. I recommend Stephen Kinzer's All the Shah's Men. For an overview, Chris Lydon did a podcast interview with KInzer in 2003.

We lose so much when we don't have the courage to listen to our foes. Some of my countrymen see it as a sign of weakness to listen, but they're wrong -- if we're sure we're right, what exactly do we have to lose by listening? Only if we're concerned that we might be wrong, should we fear listening, and then only if we want to stay wrong.

Look, I know I'm not going to convince any of the people who say that everyone who uses their mind is weak, but to people who like to decide for themselves, and want free speech for everyone, don't be fooled by what you hear on TV. They act as if they are owned by people who desperately want a war with Iran, and are willing to sacrifice American freedom to get there. Bollinger is clearly one of those people. And so do Time-Warner, Microsoft and GE (the owners of CNN and MSNBC). If not, then please do something about it, shake up the media so that we get to really discuss this, openly and fairly, before we start yet another ruinous war.

President Betray Us

Wed, 26 Sep 2007 14:39:46 GMT

Living in Berkeley we're always just a few degrees away from the MoveOn people. I hear they're really freaked about all the attention the General Betray Us ad got.

I think it's good and they should follow it with a new ad, maybe not in the Times. "Okay, maybe we shouldn't have called him General Betray Us." Not quite an apology, not quite a retraction, just food for thought.

The next ad would have a big picture of the President, with a big headline: "President Betray Us." More fodder for the talking heads.

And then a FAQ, listing just a few of the ways the president has betrayed us. Not exactly calling for an impeachment, but starting the process of moving on from Bush, about a year early.

There's nothing wrong with humor, and political humor is almost always vicious. If Bush whines too much, follow all this with an ad calling him a coward. "Mr. President, if you can't stand the heat, you could always resign early."

And then, after having cleared the field of Republicans (they'd all be running for cover, hoping their face wouldn't be on the next ad), you could start putting pictures of Democrats in the ads. Senator Betray Us, with a big picture of Harry Reid.

I think it's time for The Rest of Us to start flexing our political muscle.

I'm a gun-totin liberal, Republics betta watch out!

Dave

PS: We should start another campaign that every time the President calls the other party "The Democrat" party, we should give $10 to them. That'd get him to shut up quickly.

Opportunities for integration

Tue, 25 Sep 2007 23:36:20 GMT

When everything gets an API then everything you can imagine will be possible if you can write a script.

And sometimes, to give you an idea, all that has to happen is that a wall come down. The latest, most intriguing such wall was the paywall at the NY Times. Now all of a sudden we find the wealth of information published by the NY Times over many decades is available without tariff. More important, we can point into the archive. We've gotten so accustomed to the wall, that you actually have to think when it may be possible to go in there, as if it left behind a wall in our minds, even after the wall on the web is gone.

For example, the first episode of Ken Burns's The War, an epic series about World War II from the American perspective, cited several NY Times articles. If you looked carefully you could see the dates, and the actual headlines, and then if you have a browser handy, as I do (I have an iPhone) you can actually read the article while the narrative continues. Today this is mostly a gimick, but I suspect as we get used to having history so available (like having a library microfilm machine, which I used to spend whole days playing with when I was a kid) it will change our sense of information, perhaps as much as anything else that's ever been on the web.

Take movie reviews for example. What a thrill to be able to read a review of a movie that I love that came out in 1932! The reviewers back then were more forgiving, less sarcastic, more enthusiastic. Consider their review of the Hollywood Revue of 1929, a favorite of mine that I've only seen once (I'd pay for a DVD, if it were available). They loved audible movies (that's what they called them) as if the term "talkie" was as elusive as "podcast" was in the summer of 2004. Again, we've just scratched the surface.

Wouldn't you like to have NY Times movie reviews integrated with Netflix? Or have Yahoo's movie rating service available on the NY Times site. And I have to wonder whether they really have gone all the way. You can't see the reviews unless you're logged in. Can Google's robots, therefore, see the movie reviews? Unless the've made some special arrangements, it seems not.

There is already empirical evidence. Try searching for a review of a popular movie from the past, and see if the Times review shows up. Some examples: The Sting. The Godfather. Casablanca. Field of Dreams.

It would be helpful to get a technical guide to the newly hatched NY Times on the Web, or (as in the old days of software) a reviewer's guide, so we get some ideas of what to look at. Clearly a lot of work went into opening up the Times archive. I'm going to be in NY the week of October 8 and will have some time toward the end of the week. If anyone at the Times would be willing to spend some time with me reviewing what's now open, that would be helpful.

In any case, at least the Times today is somewhat more available to be integrated into the fabric of the web. That's some progress. How much, remains to be seen.

Postscript: Kottke did a great job of skimming the surface of the newly opened Times when it first came online, just one week ago today.

Welcome to the 21st Century

Tue, 25 Sep 2007 22:57:55 GMT

Proof that there still is more to do.

On Saturday I got an email from Sylvia saying that a friend of mine had bought her first iPod. It took me a few minutes to figure out that she was talking about herself. Funny, I had never thought about whether she had an iPod or not, but I have been on her case to get a digital camera.

So she brought her iPod over, it's one of the new "fatty" nanos with video. It was so funny to see it through her eyes, and even cooler to read her story. I didn't realize that there was a reason she had never gotten an iPod.

Sylvia: Sliding into song.

I seek out experiences like this. Stones I can turn over that reveal a rich experience, an eye-opener, a bright horizon that doesn't take much time or effort to achieve.

Nokia N800 update

Tue, 25 Sep 2007 16:08:37 GMT

Amazon is usually pretty good at getting stuff delivered quickly, but this time they've really dropped the ball.

Last Wednesday I purchased a Nokia N800 from them, six days ago, and spent $3.99 to have it delivered overnight. It shipped that night. But instead of expediting it, they sent it UPS Ground from Dallas, with an estimated delivery date of October 1. Ouch.

So I started emailing with people at Amazon, and they wouldn't give me a straight answer to a direct question as to when I could really expect the product to arrive. There were three back and forths before I gave up. (They refunded the $3.99, which wasn't what I wanted, didn't ask them to.)

Luckily, it didn't take very long for the unit to travel from Dallas to San Pablo, which is a 20 minute drive from Berkeley, where it arrived on Sunday morning. I assume because it's marked as a low priority package in some way, it spent the whole day yesterday in the warehouse. According to the UPS tracking site, it isn't "on the truck for delivery" today, so I assume it will spend another day in San Pablo.

Now of course this isn't a world-shaking issue like war or famine, or the way the US media is trashing the president of Iran, but I did promise to let y'all know what I think of the Nokia product, so this is what I think -- anticipation is wearing off, I'm getting busy doing other things, and the impulse purchase feeling is gone. The sweaty palms I had last week are pretty dry now. :-(

Postscript: Engadget has a few clues about the follow-up to the N800. So while my palms dry out and coool down, I'm beginning to feel like returning the device and then asking Nokia to put me on the press list. It's ridiculous to pay for what amounts to a review unit. Is Nokia listening??