My Reaction to the NYTimes Announcement

Today, the NYTimes announced their digital subscription offering.

In reading through the 6 major bullet-points describing the subscription offering, my initial reactions as a reader are:

  1. This sounds hard and complicated.
  2. Can I become a home delivery subscriber and opt out of receiving the paper?

Earlier this week, Elko pointed me to NYTimes Chrome – a non-scrolling, HTML5 implementation of NYTimes’ top news…that looks just like the print edition. Only much, much smaller and harder to both read and navigate.

Take a look at this article: 2 columns spread across multiple pages. We solved this interaction problem thousands of years ago.

The problem I don’t see the NYTimes solving in either of these efforts is relevance, clarity, expertise, and guidance.

I don’t have time or inclination to read every section head, let alone every article. What would a presentation look like that only gave me the stories, coverage, and writers that I find most compelling.

Yes – let me filter and block stories from ever being shown to me.

Today, here’s how I solve this problem:

  1. Not read NYTimes.
  2. Wait for someone I trust and respect to point me to a NYTimes story.

“if it’s important, it will find me.”

What if the NYTimes knew me well enough to be that trusted and respected link source – by not giving me everything – just the most compelling & relevant.

For example – take a look at amazon.com, I’m assuming the sections below the big Kindle ad don’t look much like this to you.

I’m assuming our pages look different because Amazon discovered that promoting different items to different individuals increased overall sales.

And maybe, just maybe, I’ve grown weary of the Fukushima story.

To me that sounds like a compelling, useful, differentiating, chargeable news offering.

Elsewhere:

“They’re not offering anything to readers other than the Times’ survival, and they’re not even explicit about that”. – Dave Winer

“This paywall is anything but simple, with dozens of different variables for consumers to try to understand… If you’re already paying $15 every four weeks to have full access to the website, why on earth would you pay extra just to be able to read the paper on its own dedicated app rather than in Safari? I, for one, prefer the experience of reading nytimes.com on the web on my iPad, rather than reading an iPad app which has no search, no links, no archives, no social recommendations, etc etc. If the NYT wanted to kill any incentive to read and develop its iPad app, it’s going about it the right way.” – Felix Salmon

“Now, there are those who will tell you that your business model couldn’t be more doomed if you opened a chain of in-temple money changers, which is no doubt why you wanted to try it out on Canadians before attempting any human testing.” – Marcus Carab

“The NYT arguably will be running fewer cliched or predictable or easily substitutable articles. It should make the paper less comprehensive, but sharper at the edges..” – Tyler Cowen

“I don’t have the patience for convoluted overpriced schemes like this. I’ve had it with ultimatums. This is just one more lopsided End User License Agreement. And it’s one that I can walk away from, so I’m walkin’.” – Richard Fink

Update 19 Mar 2011:
I’m intrigued with this notion of charging those whose world-view requires the NYTimes and no one else. Perhaps I’m missing something, but the incentives to migrate into that world-view don’t seem very strong.

Goodhardt’s Law: Web Advertising Edition

When a user visits one of these …. sites, the Web page launches dozens of pages that are hidden from the computer user. These hidden sites are filled with paid links to legitimate websites. Unbeknownst to the user, software built into the …. sites forces the user’s computer to click on these links, sometimes hundreds of times, sending a flood of computer-generated traffic to legitimate websites. – Emily Steel

Note: I removed the adjective Emily used in her piece to describe these sites for its not that different from what JCPenny was accused of doing.

“Someone paid to have thousands of links placed on hundreds of sites scattered around the Web, all of which lead directly to JCPenney.com.” – David Segal

Towards a Modern Weblog Architecture

“It should be as easy-to-install and easy-to-use as WordPress — easier, actually, would be better. Not-requiring a database at all would be awesome. To be successful, like WordPress it would probably have to be done in PHP, since PHP remains the commonly-installed scripting system on shared webservers.” – Brent Simmons

I’m still using WordPress personally, and I still recommend it professionally. I do great deal of new site prototyping in WordPress (even if the final site isn’t). Even with the flexibility of custom post types, a fairly robust plug-in architecture, and the option of the multi-user network – I long for the lean, mean WordPress of 2004.

Or at least a viable competitor for a simple weblog in 2011.

I agree with Brent Simmons that this hypothetical system needs to have a 5-minute or less setup time. I don’t believe it should be in PHP.

I think client-side Javascript – it’s even more prevalent than PHP

For a while now I’ve been tracking Aaron Quint’s work on using sammy.js & CouchDB to build out web applications. While it’s not as technically mature as I’d like (nor do I have a sandbox up) it’s very compelling. Especially with CouchDB’s baked in versioning, feeds, and replication.

Consistent for Whom?

“A lot of Twitter’s success is attributable to a diverse ecosystem of more than 750,000 registered apps. We will continue to support this innovation. We are excited to be working with our developer community to create a consistent and innovative experience for the many millions of users who have come to depend on Twitter every day.” – Ryan Sarver

I do know that if Twitter pushed consistency from day one – it would have never reached 750,000 registered apps. And it would have never attracted the developer ecosystem it attracted.

I would have found it far more compelling if they embraced diversity, utility, and the developer ecosystem. Instead, they’re fighting to shake off the barnacles.

Bug in my Hand

Wednesday night, I came down with strep throat. Thursday, after a nurse at the clinic confirmed it – I started taking penicillin. Almost immediately, my throat was better. Also almost immediately, my hand started swelling up.

Back to the clinic, where the doctor suspects cellulitis from a minor burn I received a week ago (so minor it’s not even visible on these pictures). That was being aggravated by the penicillin She gave me a different antibiotic – one focused on the cellulitis, less so on the strep.

If the swelling goes past the black line – I head back to the clinic.


Thankfully, Jonathan Coulton has a song for this:

Obviously

“These are all fundamental aspects of Twitter, and they have been mangled. And these items do not even get into the more technical issues with Twitter’s API implementation, which I could write another blog post about. Or about how Twitter took a vibrant ecosystem full of capable developers excited about their platform that other companies can only dream about, and flushed it down the toilet.”

“From top to bottom Twitter has made product mistake after product mistake, fundamental and obvious mistakes that have significantly confused and detracted from the simplicity of the service, for little or no gain. The DickBar is just yet another of these, not some existential struggle for monetization.” – Eric Woodward

also

“In case it isn’t obvious, Twitter is a morass of inconsistent rules…” – Dave Winer