Author Archive for Mathew Ingram

When It Comes to Social Networks, Uptime Doesn’t Matter

Mathew Ingram | Wednesday, February 18, 2009 | 7:57 AM PT | 12 comments

pingdom-small Updated: Users of social networks choose where to spend their time based on factors entirely outside of those such as uptime and reliability, according to report issued Tuesday (PDF link) by Pingdom, a service that tracks web site uptime and optimization for companies. Not that such things aren’t important — after all, a social network isn’t going to be of much use if people can’t log in or use the features. But the Pingdom report shows that when it comes right down to it, those things don’t matter nearly as much as one might think. Continue »

Social Atoms and the Twitter Ecosystem

Mathew Ingram | Monday, February 16, 2009 | 11:20 AM PT | 15 comments

twitter-birdWhen Twitter first hit my radar screen sometime back in 2007, I (like many others) immediately dismissed it as a gimmicky little time-waster with no real value. I mean, a message limit of 140 characters? Lame. And what was it for? Nothing, apparently. It was like the Facebook status message, but all by itself, with no other services or features around it. What could possibly be the point? Continue »

The NYT API: Newspaper as Platform

Mathew Ingram | Sunday, February 8, 2009 | 9:00 AM PT | 13 comments

There’s been a lot of chatter about the newspaper industry in recent weeks — about whether newspaper companies should find something like iTunes, or use micropayments as a way to charge people for the news, or sue Google, or all of the above — and how journalism is at risk because newspapers are dying. But there’s been very little discussion about something that has the potential to fundamentally change the way that newspapers function (or at least one newspaper in particular), and that is the release of the New York Times’ open API for news stories. The Times has talked about this project since last year sometime, and it has finally happened; as developer Derek Gottfrid describes on the Open blog, programmers and developers can now easily access 2.8 million news articles going back to 1981 (although they are only free back to 1987) and sort them based on 28 different tags, keywords and fields.

It’s possible that this kind of thing escapes the notice of traditional journalists because it involves programming, and terms like API (which stands for “application programming interface”), and is therefore not really journalism-related or even media-related, and can be understood only by nerds and geeks. But if there’s one thing that people like Adrian Holovaty (lead developer of Django and founder of Everyblock) have shown us, it is that broadly speaking, content — including the news — is just data, and if it is properly parsed and indexed it can become something quite incredible: a kind of proto-journalism, that can be formed and shaped in dozens or even hundreds of different ways. Continue »

Google Is Not Your Sugar Daddy

Mathew Ingram | Tuesday, February 3, 2009 | 2:10 PM PT | 32 comments

Everyone seems convinced that the Internet owes them a living, and that Google (being synonymous with the Internet the way it is for so many) is the best one to settle the bill, especially since it has billions of dollars just lying around, like Scrooge McDuck. Let’s call this the “Google as sugar daddy” argument. But why should Google pay? Especially when the main argument as to why it should seems to be because it can? Continue »

Yahoo Should Buy the New York Times? Puh-lease

Mathew Ingram | Tuesday, January 27, 2009 | 10:18 AM PT | 2 comments

As everyone waits to find out how new Yahoo CEO Carol Bartz plans to resuscitate the struggling Internet giant, in the meantime, the stress of watching Yahoo bungle one thing after another — such as coming within inches of a merger with Microsoft, only to blow the deal at the 11th hour — seems to have taken its toll on some otherwise perceptive stock analysts. Take Gene Munster from Piper Jaffray, for example. As described by Barron’s blogger Eric Savitz, Munster recently wrote yet another “open letter” to Bartz (man, she must be getting sick of those) in which he suggested that Yahoo buy the New York Times. And maybe Gawker Media as well. Oh yes, and Twitter too. And maybe FriendFeed.

Is this a strategy, or a laundry list? Continue »

Why Apple’s iTunes Concessions Are a Double-Edged Sword

Mathew Ingram | Tuesday, January 6, 2009 | 7:05 PM PT | 14 comments

Apple finally acquiesced to the demands of the record labels and introduced variable pricing to its iTunes music store. That’s good news for consumers, who also get DRM-free music. The problem is, it won’t fix what ails the music business, which by agreeing to 69-cents-and-up pricing might be setting consumer expectations even lower. No one ever said record labels were smart. Continue »

RIAA Drops Lawsuit Strategy for “Three Strikes” Plan

Mathew Ingram | Friday, December 19, 2008 | 9:35 AM PT | 5 comments

The Recording Industry Association of America, which has spent the past five years suing tens of thousands of individual file-sharers for copyright infringement, has apparently decided to change tactics, according to a report in the Wall Street Journal (hopefully this one is a little more reliable than the recent story about Google’s views on net neutrality). The good news is that they are going to stop suing 13-year-olds and retired war veterans and single mothers for downloading music. The bad news is that their new plan involves cutting sneaky backroom deals with Internet service providers to take a so-called “three strikes” approach: They let the ISP know when they think you’ve been sharing copyrighted material, and the provider agrees to send you an email warning; the second time, you get a letter; do it again and your Internet access gets cut off. Continue »

How the WSJ Failed the Web 2.0 Test

Mathew Ingram | Tuesday, December 16, 2008 | 2:17 PM PT | 15 comments

Traditional media outlets like the Wall Street Journal and the New York Times have begun to use some of the tools of social media — blogs, Facebook pages, even Twitter accounts. But they seem a lot less eager to adopt some of social media’s core principles, including a commitment to the two-way nature of the medium and all that it represents. This means a lot more than just talking about “the conversation” and how great it is to get links or comments. It’s about taking those comments seriously, responding to them regardless of whether they are positive or negative, and incorporating that approach into the way you do your job. It’s about looking at “journalism,” broadly-speaking, as a process rather than an artifact. Continue »

Native Client: An OS in Your Browser

Mathew Ingram | Saturday, December 13, 2008 | 9:00 AM PT | 7 comments

Earlier this week, I wrote about the launch of Google’s Native Client, and how the company hoped that the new software would help web-based apps run faster and more securely. After the post appeared, I got an email from Google, asking me if I wanted to find out a bit more about Native Client, and suggesting that they could help “clarify some misunderstandings” in the piece I wrote. Since I hate to think that there’s something I might have missed or described poorly in a post, I agreed.

What resulted was a phone call with three Google engineers: Linus Upson, an engineering director; Brad Chen, the engineering manager for Native Client (who wrote this post on the Google blog); and Henry Bridge, a product manager for Native Client. Continue »

Google: Fulfilling Netscape’s Original Vision

Mathew Ingram | Tuesday, December 9, 2008 | 7:59 AM PT | 10 comments

With Google’s release of a software platform known as Native Client, the company has moved even closer to fulfilling the early promise of a “web operating system” — a vision originally offered by browser-software pioneer Netscape Communications. By allowing browsers to run code in the language understood by a user’s PC, browser-based software and services will run faster and be able to offer more functionality than they can now — and browser-based services that could replicate all of the features of a desktop application would become a reality. Continue »

Page 1 of 212Older Posts »

Editorial Masthead

Carolyn Pritchard
Managing Editor
Celeste LeCompte
Special Projects Editor
Desiree DeNunzio
Copyeditor
Om Malik
Senior Writer
Stacey Higginbotham
Staff Writer
Jennifer Martinez
Staff Writer
Wagner James Au
Contributing Editor
Liz Gannes
Staff Writer
Chris Albrecht
Staff Writer
Katie Fehrenbacher
Staff Writer
Josie Garthwaite
Staff Writer
Close
E-mail It