For the record: I really thought that champagne cooler was empty.

In 1997, right after Chips n' Dips had faded away, to be replaced by the enigmatically named http:///..org, all of us free software nerds hung on its every story, comment and poll like it was carved on tablet and flung from a burning bush. A year later I had started at hardware maker VA Research and /. was falling down for lack of machinery, so we rummaged through our returns piles and sent Rob and Jeff some 2u servers to help out. That was for me the beginning of some of the most important friendships in my adult life.

Its hard to explain how important Slashdot was to all of us 10 years ago. Indeed, without it it would be hard to imagine HN, Reddit, Digg, Fark or any of a thousand lesser sites. The editorial perspective of Rob and the other editors of /. is what kept people coming back and for a long time that perspective was Rob's, then Rob and Jeff and a bunch of us (some, like Timothy and samzenpus, still around!), but then Jeff left, now Rob. In some way I see this as a passing of an era in free software.

Throughout, while some have left for those greener shores, slashdot abided even while buffeted by the markets and the de/evolving internet news world, and it has remained a default tab in my and many others' browsers.

I didn't mean this post to be about Slashdot though, but about my friend Rob. I'll only say that while the site will be the lessor for you leaving, I firmly believe that computer science will gain my. While this note reads like an epitaph or the last pages of a book, it is really no more than a thank you note from me and many I know to your for your decade+ of work on the site. So...

Thanks.

Well, I remember the monetary pain of buying textbooks, and I know a lot of kids in college today. To them, the costs of textbooks are anything but chump change.

There is indeed value there, but of course the costs for this sort of work, amortized over many copies, it comparatively tiny. And I would point to the work of places like the California Open Source Textbook Project and Flat World for examples of how very good the content can be even though produced by "alternative methods".

Like prefect42 notes, the actual reviewing that filters our the cranks and such is *also* done by the academic community, usually at no charge to the publishers.

You're quite correct, of course. I've interacted a lot with GA Tech folks over the years, and it just popped out of my fingers. Sorry, GSU!

It has amazed me how long the current academic publishing regime has lasted. This dystopian fantasy by the publishers is the logical extension of a broken business model, where the publishers provide essentially zero value yet charge enormous fees. GA Tech should use this moment as a clean break point, and demand that all campus materials be either in the public domain or be available under Creative Commons license. Award tenure based only on publications which are under CC license.

Universities need to remember that they are the folks that generate *all* the content that publishers want to use against them. They can stop giving it away to these guys any time they like. In this era of global networking, there is essentially no added value in distribution, warehousing, and organizing papers into journals. Publishers need to be reminded of this fact.

Sorry, but Theora is still not as high quality as later codecs. That hasn't changed. But I was very happy to fund this work out of my group.

Hey, the fellows in netops asked me to clarify for you folks here's the story:

1e100.net is a Google-owned domain name used to identify the servers in our network. Following standard industry practice, we make sure each IP address has a corresponding hostname. Starting in October 2009, we started using a single domain name to identify our servers across all Google products, rather than use different product domains such as youtube.com, blogger.com, and google.com. We did this for two reasons: first, to keep things simpler, and second, to proactively improve security by protecting against potential threats such as cross-site scripting attacks. Most typical Internet users will never see 1e100.net, but we picked we picked a Googley name for it just in case (1e100 is scientific notation for 1 googol).

So there you go!

If you head over to LWN, we've already gone back and forth on this a bit. http://lwn.net/Articles/372419/. The short form is that if they don't like how we use the kernel, we're unlikely to be accepted upstream. It's all still released as source code to the world, but the mainline is not interested in most of what we've with to the kernel.

I'd like to point out that the Kogan phone folks could have adapted the code to the screen size, but it would have taken longer than their product plan would have allowed. So in that case, you are right, but if they had started the screen porting stuff earlier, then they probably could have shipped something like what they put on their website.

Let me remind you that the structure of the droid licensing is very clear: linux kernel, then apache/bsd all the way up from there (With a dollop of lgpl). You don't need googles permission to ship an android based device. There are some apps (maps comes to mind) that you do need googles permission to ship, but those are closed anyhow.

Chris

Man, no respect for writing 2 non-fiction books. -none-. Course the second one sold for shit...

Chris