Slashdot Mirror
Specs of Salons Subscription System
legLess writes "Scott Rosenburg, Salon's VP of operations, wrote an interesting article for Web Techniques about Salon's subscription system. It goes into a fair amount of technical detail (JavaBeans and JSP on Linux for login and authentication; Perl, HTML::Mason and MySQL (CD: and oracle) for content). He also talks about their subscription numbers, what drove them to do it, and their plans for the future (technical and operational). A little fluffy, but still a good read."
After reading this article, I begin to see why it will be doubly tough for Slashdot to make the jump to subscription-based revenue.
The biggest problem I see with Slashdot is that Slashdot doesn't have a Cringely or a Coursey or a Dvorak. Sure, Slashot has Jon Katz, but I just don't find his articles as readable as a Cringley column or a Dvorak rant.
I see the real difference between Slashdot and Salon on a couple of other fronts as well. Besides not having several columns by intersting authors, most of Slashdot's content is made interesting by the readers, not by the story submitters. Personally, I am horrified by both the obvious lack of attention given to grammar, as well as the oft-biased one-liners added by the story submitters. Finally, although it has gotten better in recent times, Slashdot seems to crash a lot... even more than an overloaded MySQL database would suggest.
For Slashdot to take a viable community and turn it profitable, the story editors do a lot more than Salon did. The fact remains that Salon's content is mostly unique, whereas Slashdot's content (in terms of story submissions) is mostly regurgitated. Salon's readers will pay because it's hard to find Salon-like articles anywhere else. On the other hand, I can honestly say that if ZDNet had a moderation system, I'd only rarely visit Slashdot. ZDNet's columnists keep me entertained, and their news is grammatically correct and up-to-date because they pay people to go out and write it.
It all boils down to whether Slashdot can successfully differentiate itself from the hundreds of other "Cool Linux Stories" sites. In the end, what keeps Slashdot's readers coming back is the discussion and the attached moderation system. What remains to be seen is whether or not people will pay for that.
From previous postings on this site, it seems that Slashdot will be going to subscription route as well. I think its a good idea.
I'm all for improved discourse, and I'd be disappointed if Slashdot had trouble staying afloat, but I don't agree that a subscription-based revenue model would improve the quality of the site.
Not too long ago, Salon's "Table Talk" message board was a great place to find reasonably intelligent talk. There were no trolls, and it seemed that most everybody could spell.
Then, sometime in the past year but I'm not sure when, Salon took their message board to a subscription-only model. Anybody can read, but only paying subscribers can post. It's not expensive, either; something on the order of six bucks a month, I think?
The result? The boards that I used to frequent on Table Talk are now ghost towns. Tumbleweeds and cow skulls, and Yul Brynner wandering around dressed all in black.
I, too, used to think that taking Slashdot to a read-for-free, pay-for-post model would be a good thing, keeping some of the riffraff out. But I don't think so any more.