Reason why I ditched slashcode was that it was never updated, and it was never documented. The upgrade paths from the builds was a nightmare. Stuff would work, then not. 

Migrating to wordpress has resulted in a faster site, and I can take advantage of a huge supply of plugins and interest in the platform. And the upgrade path to new versions is well documented and easy

There isn't anything remotely like with slashcode. Ever. Since 98 or whenever. It was a pain until 2008 when I decided to figure out how to migrate my stuff to wordpress.

Sent from my iSomething

On Feb 3, 2011, at 9:03 PM, Clifton Wood <> wrote:

The problem here is that we'd spend more time making Drupal into Slashcode than making a better Slashcode.

- Cliff

On Thu, Feb 3, 2011 at 10:28 PM, T. J. Brumfield <> wrote:
There are some Drupal modules that were started to add Slashcode style features, such as Slashcode moderation.

In a perfect world, I think Slashcode might be better off recreated in Drupal 7.

There are far more extensions/modules for it. It is mature, stable, tested and well used. It would be easier to get support for. I would seriously kill for a slick, Drupal 7 powered Slashcode of the future.

On Thu, Feb 3, 2011 at 8:44 PM, A H <> wrote:
And can Wordpress do moderation points like Slash?

The moderation system was what attracted me to Slash but I had to give
up on it - too many undocumented "features".

I think it's still a relevant format and I would love to see it
flourish. My contribution would need to be in documentation because I
am not a programmer.


On Thu, Feb 3, 2011 at 8:39 PM, Eric Dannewitz <> wrote:
> I'd ditch slash for wordpress. I did and have never regretted it
> Sent from my iSomething
> On Feb 3, 2011, at 4:23 PM, George Taft <> wrote:
>> An Open Letter to the Developers of Slashdot, and What's Left of the
>> Slashcode Community --
>> I'm an avid reader of Slashdot. I don't comment much, but I've always
>> been impressed by Slashdot's moderation system. It manages what should
>> be an unmanageable task: ensuring a civil discussion among thousands
>> and thousands of users.
>> I've come into a situation where I now need a system much like
>> Slashdot's: an extensible and scalable readership-moderated online
>> discussion forum. Lo and behold, Slashdot make Slash open source years
>> ago. They even got an O'Reilly book.
>> But Slashcode was never the priority of the coders. The last official
>> release is, what, nine years old? There's been much more modern code
>> released, but even that's a couple of years old. What little traces I
>> can find of other sites using Slash involve those sites migrating to
>> something else. This message is evidently the first post on
>> slashcode-general in almost a year. The coders have written that
>> management of the open-source branch of the codebase is still not
>> their priority. And so the userbase has almost disappeared, like so
>> many Mac clones.
>> Over the past three months, I've tried to install Slash myself, and I
>> run into the sorts of problems that are documented elsewhere. I relied
>> on the woefully out-of-date alternate install document at
>> And I still don't know: am I using the right
>> there a best distro? Is this version of Perl too new? This
>> version of MySQL or Apache? Why is this thing not working...and why is
>> it so hard to make work? The friend who's been helping me through this
>> process has constantly grumbled about the suite's age, its reliance on
>> aged platforms, and wouldn't I like to try something more modern?
>> Nevertheless, no one can name me a CMS that does as good or better a
>> job of moderation. (I desperately wish someone could, because I'd be
>> pleased to go use that.) The coders have given their reasoning for why
>> they still use Perl and Apache 1.3: because they still work. Slashdot
>> is living proof that Slashcode works. I buy their logic.
>> I believe so strongly in its value as a discussion-moderating tool
>> that I'm pledging to volunteer time to revive the Slashcode project.
>> I'm asking for help from whoever will give it.
>> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>> night, a typo that screws up the install at the creation of the
>> "Preview" table. I was able to fix it and get the whole install done,
>> but it took forever and it only half-works.) But I know what good user
>> interface design looks like, and I'm an excellent writer and
>> documenter. I'd like at least to help make the installation more
>> user-friendly.
>> Perhaps it's naive of me to think that this email will make something
>> happen. But if you have even a smidgen of interest in making Slash
>> accessible to a slightly more general audience, please, please post
>> here. Let's begin this project anew.
>> == George


-Andrew Holden
cell/text: 610-212-3466

"I'm questioning my education
Rewind and what does it show?
Could be, the truth it becomes you
I'm a seed, wondering why it grows"
-- Pearl Jam, Education

The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
Slashcode-general mailing list