Slash 2.2.0 Released

If you meander over to Slashcode, you will notice that Slash 2.2.0 has been released. This is of course the website engine that runs Slashdot. The release has the message system, improved journal functions, new comment filters, and countless bug fixes. And of course a variety of optimizations that continue to make it possible to serve a quantity of pages that no other open source package like this can even touch :) Plus it's way easier to install. Now that we've got the Fry tree out of the way, its off to work on Zoidberg (which will include subscriptions, killfiles, and a few surprises)

Re:So when is /. going to get a facelift?

[the Man in Black]

Not that there's anything wrong with the current appearance, it's just time for a change.

How very Microsoft-ian of you.

"A few surprises"

[BarefootClown]

Any chacne one of thoes sprises could be a web itnerface to aspel?

Kill funny messages

[crow]

I'm still waiting for the option to recalculate the point value for articles based on my own preferences. I want funny to count as +0.

...Slash code has a...

[ekrout]

...Slash code has a variety of new improvements for users and administrators alike!

For example, the new SlashTag &ltgoatsex>, which saves you the tedium of having to do all that HREF and HTTP:// stuff.

Re:First Post

[Anonymous Coward]

"I there any plans to stop this first post c##p in the code"

Yes, I hear that Taco plans to introduce the following snippet into Slash:

if(comment.number() == 1)
{
post.abort();
}

ie. anybody trying to post a first comment to a story will be rejected, only the second, third etc. posts will be allowed.

HTH.

Re:Kill funny messages

[Anonymous Coward]

I don' think we can mod things up as funny anymore....

Database

[Anonymous Coward]

I hope that one of these "surprises" is the lack of database crashes!!!!!

Re:Spell Checker?

[ellem]

grammer trolls

grammar

Re:Kill funny messages

[ralmeida]

LOL! Someone mod this +0, Funny!

Dotslash.

[Odinson]

Oh oh oh, I want to change my prefrences to form....

Eeeeevvvvviiiilll Slaaaaaassshhdoooooot!!!

• Underrated +0
  
• Overrated +1
  
• Funny -1
  
• Offtopic +1
  
• Interesting -2
  
• Redundant +2
  
• Informitive -2
  
• Troll +2
  
• Insightful -3
  

and drum roll please.....

• Flamebait +5

Feature request

[Anonymous Coward]

I would like the ability to read the -1 posts only (all the other posts are crap).

BWAHAHAHA

[Pope Slackman]

It's open source, that's really the only documentation any reasonably intelligent person needs.

You've obviously never read slashcode.

C-X C-S

Surprises...

[Swaffs]

"Now that we've got the Fry tree out of the way, its off to work on Zoidberg (which will include subscriptions, killfiles, and a few surprises)"

The rest of the world calls these surprises "bugs". Except Microsoft, who calls them "features".

Slashdotted

[Pseudonymus Bosch]

So now we have to slashdot Slashcode?

Warning!

[RageMachine]

This release contains a security flaw. This flaw will not be revlealed in the ChangeLog, and is protected under the DMCA!

Re:Kill funny messages

[Corporate Gadfly]

Its true... I don't come to slashdot to catch up on funny punch lines. I would much rather go here [theonion.com]. Lately, /. has become a place for people to tickle their funny bone. Its a contest for who can come up with the funniest response? I already see people lining up to repond to this post in the funniest possible way.

Re:Improvement suggestions:

[jamie]

"But down here in the posters' trenches, the consensus is that it sucks ass. Way too many people catch the lameness filter for a short subject..."

It sucks ass to have to type more than one character for a subject?

I log every instance of the compress filter doing its thing. In the last 20,000 comments or so that have been posted to Slashdot, it's blocked exactly two attempts to post because of a too-compressible subject. Both times the poster could easily have added about one character and it would have gone through.

And of the last 20,000 successfully posted comments, there have been exactly 50 blocked attempts because of compression on the text. (Note that two blocked previews followed by a successful post, which is typically what happens, counts for 2 of that 50.) The blocked posts are mostly things like the same link pasted in over and over, or one that was 23K worth of "... testtesttestesttesttestesttesttestest..."

Big chunks of whitespace look too much like ascii art and are frequently caught (where "frequently" means "well under 1%"). The solution is simple: trim out the whitespace. Sooner or later I'll get around to a feature that lets the Slash code trim it out automatically if you ask.

As I say, the code changed a couple of weeks ago, becoming much better. I am always very interested to hear about its failures, please, submit bug reports and let me know exactly what legitimate comment you were stopped from posting. But be precise. I have the debug logs, so vague anecdotes aren't convincing. And in this case, you're complaining about stuff that has already been addressed. Get with the times :)