I think the editors or owners of Slashdot are either 1) Trying to increase viewership by appealing to a lowest denominator (Star go boom! Big word scary! Chemicals are mean! Vroom vroom car!) or 2) Trying to deliberately weaken the readership for purposes I can only speculate that. That second theory is bolstered by the clumsy rolling out of 'features' during the past few weeks - breaking things that once worked, adding new features that don't, and in general doing their best to make the site almost more tr
I have no inside information, but it's apparent to me that Slsahdot is trying to be the new 'Facebook' or 'MySpace' for geeks. Or something. I'm expecting any day now the ability to add tacky photos, weird fonts and poor layouts to your journal pages.
Furthermore, I think that much of the original geek crowd is gone or mostly in lurk mode. So they are doing their best to attract a younger audience.
Can we see slashbug.png? I considered getting a screencap of my own window for inquiry as I've had those stupid gray bars in every comments section for weeks now. I thought, without reason admittedly, that I was the only one affected by the latest CSS garbage. Ridiculous what slashdot has devolved to over the last few years. Yet all the admins have ever said about it was something along the line of "lol hay guyz we broke the site again but we're positive you'll enjoy all the cruft, java and broken code beca
Yep, that would be this bug [sourceforge.net], which, like pretty much all bugs in slashcode, will probably not get fixed.
And then there's this bug [sourceforge.net], which they don't seem to be in any hurry to deal with. If you read through the comments on the bug, they add up to complete info on how to reproduce and fix the bug. The bug only occurs for stories in certain slashdot sections, because only those sections' CSS is messed up. So all they had to do to fix it was to copy the correct CSS out of the not-broken files into the broken
Wow, Great Summary (Score:5, Insightful)
Is it THAT slow of a news day, or could no one else possibly outdo this clown of a submitter?
Re: (Score:3, Insightful)
I think the editors or owners of Slashdot are either 1) Trying to increase viewership by appealing to a lowest denominator (Star go boom! Big word scary! Chemicals are mean! Vroom vroom car!) or 2) Trying to deliberately weaken the readership for purposes I can only speculate that. That second theory is bolstered by the clumsy rolling out of 'features' during the past few weeks - breaking things that once worked, adding new features that don't, and in general doing their best to make the site almost more tr
Re: (Score:3, Insightful)
I have no inside information, but it's apparent to me that Slsahdot is trying to be the new 'Facebook' or 'MySpace' for geeks. Or something. I'm expecting any day now the ability to add tacky photos, weird fonts and poor layouts to your journal pages.
Furthermore, I think that much of the original geek crowd is gone or mostly in lurk mode. So they are doing their best to attract a younger audience.
Re:Wow, Great Summary (Score:5, Informative)
tacky photos, weird fonts and poor layouts
Don't worry, they're currently hard at work on it.
http://www.cs.drexel.edu/~jlg95/stuff/shittycode.png [drexel.edu]
Re: (Score:2)
Something's only a social networking site if the poor layouts are the fault of the users, not the site administrators.
Re: (Score:0)
Can we see slashbug.png? I considered getting a screencap of my own window for inquiry as I've had those stupid gray bars in every comments section for weeks now. I thought, without reason admittedly, that I was the only one affected by the latest CSS garbage. Ridiculous what slashdot has devolved to over the last few years. Yet all the admins have ever said about it was something along the line of "lol hay guyz we broke the site again but we're positive you'll enjoy all the cruft, java and broken code beca
Re: (Score:2)
haha, I didn't even realize I still had that one open. It was the same bug but screenshotted by someone else.
Re: (Score:1)
Yep, that would be this bug [sourceforge.net], which, like pretty much all bugs in slashcode, will probably not get fixed.
And then there's this bug [sourceforge.net], which they don't seem to be in any hurry to deal with. If you read through the comments on the bug, they add up to complete info on how to reproduce and fix the bug. The bug only occurs for stories in certain slashdot sections, because only those sections' CSS is messed up. So all they had to do to fix it was to copy the correct CSS out of the not-broken files into the broken
Re: (Score:0)
Hey, I got that same effect in Opera not five minutes ago.
At least it's cross-browser shitty code!