I don't actually have anything to say. Kathleen is due any day, and I'm looking forward to a few weeks of staying home, getting poor sleep, and changing diapers.
But mostly I'm testing to see if journal saving works properly.
We've made some significant updates to the submission/journal system. Visiting Submissions and Journals yields a new form that allows stuff like tags to the data types. There are a number of annoying bugs, but for the most part the dust is starting to settle. More notes will be coming, but this journal entry is really just me putting the final test on the new Journal form.
We now abbreviate journals in the firehose... so they are more like slashdot stories with a Read More link to the full text.
The big user facing change this week was structural: historically we had 2 different "skeletons" on Slashdot, but with this refresh we unified to a single one. This change simplifies maintenance for us quite a bit (maintaining the idle section and the firehose views of the same data was a royal pain).
You also will see some changes to the firehose.pl layout. We're playing with the tab layout a bit, moving some menus around and better integrating the core functions into the site chrome. It's a bit buggy atm, so feel free to email me if you see something wonky. We're extinguishing a few minor brush fires but there's no forest fires that we're aware of.
The first real change is that we've changed the meanings of the UI around. The old system is 'Fair' and 'Unfair' and the new system is '+' and '-'. The meanings are subtly different. You are no longer rating individual 'Insightful' or 'Troll' or whatever... you are now stating basically "Is this comment good or bad for you". Personally, since I find very few Score:5 funny comments to be actually really funny (and not just cliche memes) I '-' most of them. You are encouraged to be harsh if you don't actually think something is insightful or funny, call it such. The system encourages more of what you + and less of what you -.
You are also welcome now to do more than 10 m2 per day... however we internally have diminishing returns after 10, so you can do more, but they start to matter less and less.
There will undoubtedly be bugs so feel free to email me or vroom at slashdot if you find them. Probably next week or so we'll move this out to everyone, so your assistance is appreciated.
The Studio Hybrid uses 20% of the material of a standard desktop mini-tower, and as little as 30% of the energy to run. Packing materials are 95% recyclable and have been reduced in weight by 30%. The printed documentation has also been reduced in weight by 75%. This gives the Studio Hybrid the title of Dell's most environmentally friendly PC.
We also added a thing to 'collapse comments after reading' which I think I might turn of as a default setting soon. This is only usable for subscribers atm as well. But basically, as you navigate through a discussion, it collapses the comments you've read after you move on. This makes it really easy to navigate large discussions without having to scroll over 150 comments you've already read.
we're aware of a number of annoying bugs, but hopefully most of them will be squashed by Pudge for this weeks code refresh. If things are stable, we hope to roll this out for everyone rsn.
also my baby cut his first tooth yesterday. My furniture will never be ungnawed upon again.
The issue is about the use of Flat/Threaded/Nested modes. D2 cleanly replaces both threaded and nested modes- you effectively get nested mode by bringing the 2 sliders together. And threaded mode is vastly more flexible because you can choose the level at which comments are abbreviated or displayed in full text. So users of those modes should be set (obviously there are other reasons not to use D2, I'm just talking about the layouts here tho)
What's left is flat mode, which has a number of sort options. Now flat mode is used by roughly 4% of our active population. When i think about flat mode, I think about 2 reasons you would have to use it:
Now I Would think that the only reason to use flat mode is #2... except that only a couple hundred Slashdot readers have the 'ignore threads' sort order enabled. So either they don't understand what they are doing, or #1 above is the real reason that they use flat mode.
So in a nutshell, the question I am asking in this journal is 'Why do you use flatmode?' Is it cosmetic? To more easily keep your place in a discussion? Something I'm just missing? We have plans to implement a read/unread state retention for discussions, so maybe would you migrate to a threaded view if that function exists? Or is it purely aesthetic... an irrational hatred of scrollbars and whitespace?
The reason this matters is that simply formatting the page flatly is easy. Probably a simple greasemonkey hack or maybe a few lines of CSS. But re-implementing the alternate sort is gonna take some work. And I'm ok with that... except that the logs say that nobody actually USES that sort... they ONLY are using flat mode for the cosmetic reasons.
Speak out! Stay on-topic or you WILL be moderated down.
A few new keybindings aren't documented yet... v (end) t (top)  change upper threshold and
The only major complaint so far is that the design changes consume a lot more whitespace. I have mixed feelings on the subject, but am aiming to strike a balance. We noticed 2 very clear places where the whitespace is excessive and hopefully that will be fixed RSN. But on the other hand, making deep threads visually clear, and drawing some attention to the 'reply' buttons is beneficial to everyone, so bare with us as we work to strike some sort of balance.
ASHes to ASHes, DOS to DOS.