Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Slashdot Discussion System Updates

Posted by CmdrTaco on Tue Jul 15, 2008 11:23 AM
from the stuff-to-play-with dept.
This week we have a few new functions for you comment readers guaranteed to amaze and enchant. Or at least to make your day a little more efficient. The biggest update is that the system should remember what comments you've already read (for a few weeks anyway) but there's some other less interesting stuff as well. Hit the link below to read more.

So D2 now remembers what you have read. This will mostly be useful to readers who use the key bindings to navigate -- we didn't really want to guess if you've read something, but if you use the WASD keys to navigate, moving on from a comment flags it as read. Read comments are slightly faded, and if you re-enter a discussion a few hours later, it should remember what you've read.

We've simplified comment retrieval as well. If you get to the 'End' of a discussion and try to get more comments (either by clicking one of the various 'More' links, or by pressing a keybinding like S or D that tells us to move on to the next comment) a dialog box will show up asking you if you would like to lower your threshold. So if you normally read at Score:4, and read to the end of the Score:4 comments, it will offer to lower your threshold to Score:3 either for all time, or just for this page. This means you don't need to constantly raise and lower your threshold to handle discussions of different sizes. This works really nicely.

Lastly is a user preference in the pref pane labeled 'Collapse Comments After Reading.' I'm actually considering making this one on by default but I'm open to feedback. It does what it says -- after you've navigated off a comment (using the keybindings again), it collapses the comment you just left. This makes it very easy to keep your place in a discussion as it grows. This is especially useful in discussions where you want to leave a tab open for several hours, or else come back later and figure out what's new.

There are undoubtedly bugs: feel free to email me or post them to the bug tracker. Thanks to pudge for hacking all this stuff too. Especially the bugs -- he wrote those first.

+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Display bugs (Score:5, Insightful)

    by schnipschnap (739127) * <formulatoocomplex&gmx,net> on Tuesday July 15 2008, @11:26AM (#24198053)

    Hmm, I think it's also about time to fix some display bugs. The most important one would be that replies to a given comment visually look like they're replies to the parent. And the lines that should tell you what nesting level you're at seem to disappear sometimes, especially when you collapse something. And collapsing a grand-grand-grand-parent, for example, also hides all children, but it triggers that triggers another kind of display bug: the boxes and hooks don't disappear.
    I usually use Opera, but I was able to see that Firefox doesn't do away with those problems either.

    • Re:Display bugs (Score:5, Insightful)

      by Anonymous Coward on Tuesday July 15 2008, @12:18PM (#24199073)

      Yes, agreed! Nested mode is so much worse than it used to be, because of these bugs.

      In addition, how about removing the longstanding restriction of only showing up to 100 nested comments per page? If you try to set your prefs above that, it just resets it to 100. Let me just load all 1000+ comments of a large story into one page and I won't hit the slashdot servers for another hour as I read through.

      And I'm pretty sure there's a longstanding bug there where if a long comment thread pushes the page well beyond 100 comments, the next page may completely skip some comments/threads. Besides, it's freaking annoying when you get one of those 400-comment threads on the page, and then the next 3 pages are exactly the same because they still start within that massive thread. Stupid.

    • Re:Display bugs (Score:5, Insightful)

      by gad_zuki! (70830) on Tuesday July 15 2008, @01:36PM (#24200473)

      Or why the heck is the 'Reply to This' button so fricking huge? Seriously think about shrinking it.

      • Re:Display bugs (Score:5, Insightful)

        by mikesd81 (518581) <`mikesd1' `at' `verizon.net'> on Tuesday July 15 2008, @12:08PM (#24198897) Homepage
        And yet, Open Suse has fixed, as of July 6, almost 3000 bugs from opensuse 10.3 to 11.0. Mostly typos. KDE has been making great strides in updgrades causing less crashes by updating bugs. And since you're attacking OSS, let's lay out all the cards. What has Microsoft done about their bugs? Oh, yea, they get hard coded into production releases.
            • Re:Display bugs (Score:5, Interesting)

              by Blakey Rat (99501) on Tuesday July 15 2008, @12:52PM (#24199713)

              And what kind of bugs are you submitting?

              Click the link, they're all listed. Mostly usability bugs, some extremely obvious visual bugs.

              Keep in mind big projects get alot of bug sumissions.

              Slashdot doesn't; maybe 5-8 on a busy day. Today it'll get a ton, but I've been watching their Sourceforge tracker for awhile.

              Did you do the research and see if it's a dupe?

              Yes. I used to work in QA, I do know what I'm doing.

              Is it a security bug, they'll probably get looked @ first. Then they'll look if it's cosmetic or functioning.

              My experience shows that they will not.

              You're the one that attacked OSS

              I'm not attacking OSS; I'm attacking projects that ask for contributions and then ignore the contributions. It just so happens these projects are usually open source projects.

              Commercial products generally don't ask for contributions, and yet I've had much better luck getting bugs fixed in them. I've pointed out bugs to Apple, Blizzard, Microsoft, Adobe, MySQL (on one of their closed-source utilities) all with positive responses. Many of these bugs have been fixed, or will be fixed when the next product revision comes out.

              Do you use a Mac? Do you play World of Warcraft? Do you use windowed mode? Did you notice about a year ago that windowed mode started remembering its position on the screen between runs? I submitted that bug, and it was fixed in the next Mac-specific client release. (Sadly, the Windows developers haven't yet implemented the same thing. I should pop off another email.) Blizzard doesn't ask for user contributions; in fact they make it pretty hard to even find what email address to use.

              so I figured you're a MS fan boy.

              Damn those shades of grey! I only see in black and white, and that's the way I like it, daggummit!

              Most open source programs, except for big ones like DEs and distros or office programs, etc, most developers aren't getting paid to make and are writing them in their spare time.

              Ok; that's fine. But if they don't have time to look at or fix bug submissions, they shouldn't ask people to submit them. They're just wasting our time and effort.

              I don't know what your profession is or what bugs you actually submitted or to what projects, but when submitting a bug, evaluate how important it is, to everyone, not just you, and set your expectations.

              I think it's a reasonable expectation that every bug, no matter how trivial, at the very least be assigned to somebody. Over 50% of the bugs I submitted were literally never read. Probably closer to 75%.

              If you can code, then submit a patch.

              I can code. But I don't have the free time to learn the coding style, build instructions, layout, possibly new programming language required to make the patch. Definitely not enough to make the patch when there's a good chance the patch will be rejected anyway.

              The best use of my talent to the open source community is to use my extremely low tolerance of bugs and ability to notice tiny annoyances for QA purposes. Turns out most open source projects don't actually want that.

      • Re:Display bugs (Score:5, Interesting)

        by sm62704 (957197) on Tuesday July 15 2008, @01:38PM (#24200535) Journal

        Hell I'd even consider subscribing if the editors could keep their "witty" comments to themselves or give us an option for viewing submissions without editor comments

        I've had half a dozen submissions posted (one last night, it was the first one this year) and sometimes submissions are straight from the submitter without even typos corrected, and sometimes they completely rewrite the submitter's summary (like the one I submitted yesterday afternoon so don't blame ME).

        Contrary to popular opinion, slashdot editors do edit. They may of may not be good at editing, but they do edit. Or not, as they see fit, I've found.

      • Re:Display bugs (Score:5, Interesting)

        by Alaska Jack (679307) * on Tuesday July 15 2008, @02:05PM (#24201085) Journal

        The best system for organizing a forum that I've ever seen is the left-hand pane on Google Groups (You have to enable Tree View to see it).

        I'm baffled by the fact that no other comments system seems to use it. I bet Google would donate the code to Slashdot, too.

            - Alaska Jack

  • Hmm...guess not.

  • AWSD (Score:4, Interesting)

    by KevMar (471257) on Tuesday July 15 2008, @11:30AM (#24198135) Homepage Journal

    what does awsd do?

  • no h-j-k-l? (Score:5, Insightful)

    by doug (926) on Tuesday July 15 2008, @11:40AM (#24198343)

    w-a-s-d might be fine for some, but for us old school vi types, h-j-k-l is hardwired into our brains. Could that be added along-side the w-a-s-d stuff?

  • Issues (Score:5, Insightful)

    by Maxo-Texas (864189) on Tuesday July 15 2008, @11:40AM (#24198349)

    I've never consistently gotten the correct threads when I have more than one page and say show me the next page. I see a certain thread in the first 50, then hit page down and there it is again. The only way I've been able to compensate is filter to a high enough level that all threads fit on one page and then drill down.

    And the biggest problem I have is lack of editing.

    Just 15 minutes-- or better yet- hold all versions so people can see what you posted first so you can't lie but CAN fix stupid errors.

    Also, there is no way to see level 0 posts only. That's very helpful when you want to up-mod folks who were silenced by a bad mod.

  • Logging in without having to navigate away from the page when replying would be nice.

    So, in the old system, you hit reply, realise you aren't logged in, type in user name and password (or have FireFox auto complete), type your comment and post.

    The new system, realise you aren't logged in, hit the login link, get taken to a different page, login, navigate back to the old page, have to find where you wanted to reply, and notice that in the three minutes you spent logging in (some people are on dial up, some people do other things while waiting for pages to load, some people do both), you notice someone else has made the comment you were going to make!

    So, how hard can it be to just include a username and password box when you hit reply and aren't logged in?

    • I vote for this (Score:5, Insightful)

      by JSBiff (87824) on Tuesday July 15 2008, @12:50PM (#24199667) Journal

      This has been driving me nuts ever since the new comment system was introduced. Overall, I mostly like D2, but since the old system has allowed me to login while posting for *years*, and now suddenly I can't, it feels like a step *backwards*. I especially I hate when I've typed 2 paragraphs of text, then suddenly realize I'm not logged in. Yeah, copy-and-paste are you friend in that situation, but it's still a pain. As the parent pointed out, after logging in, you have to find the main article, then find whichever discussion thread you wanted to reply to, which can be a major waste of time.

      Please, why in the world can't I login right in the comment box? I know you guys want to ajax-ify everything, but really, just having the username/password fields as part of the form with the comment summary and body was so simple and elegant, how could you possibly improve it? Since the code on the backend is already there to handle it, since the old system is still there, I can't imagine it would be terribly difficult to add this back into the new system?

    • by SydShamino (547793) on Tuesday July 15 2008, @01:04PM (#24199895)

      I wholeheartedly agree with you. This is less useful than it was before, and would be a great improvement.

      However, as a better workaround, note that the following works:
      1. Hit reply, realize you aren't logged on.
      2. Open the "log in now" link in a new tab. Switch to that tab and log in on that tab.
      3. Return to the original tab, type out your reply.
      4. When you hit the preview button, it updates you as logged in.

      This way you don't have to navigate back and find the post to reply to. As you said, it would be much easier if the log in boxes were right here on the same page.

  • by Clover_Kicker (20761) <clover_kicker@yahoo.com> on Tuesday July 15 2008, @11:48AM (#24198503)

    Soon you'll have recreated the functionality of a late 80's usenet client.

  • by linzeal (197905) on Tuesday July 15 2008, @11:54AM (#24198609) Homepage Journal
    Before all these changes this site was much easier to scan. Now it bunches comments up on the right side if they are nested to deep, the lines while clever are not ready for production and I just liked it better before all these CSS changes. If you guys need something to do, start reading more science and engineering sites and less game and sysadmin sites. I mean if you are having a slow newsday you aren't looking hard enough [eurekalert.org].
  • And yet... (Score:5, Insightful)

    by Reason58 (775044) on Tuesday July 15 2008, @12:00PM (#24198723)
    We still can't mod the editors.
  • Thats nice that the discussion system has been updated, but it would be even better if the moderation was improved. We have too many hacks running around with mod points that are ripping down comments that they disagree with, regardless of their relevance (look at the gun [slashdot.org] control [slashdot.org] threads [slashdot.org] to see good examples of irrational moderation.

    We need moderation methods that actually reflect the scoring more intelligently, or a scoring that more intelligently reflects the value of the comment. The "overrated" and "underrated" moderations are garbage. Hacks use it to promote their friends and demote their foes. Why should a comment that started at +2 ever be marked "overrated"?
    • my own follow-up (Score:4, Interesting)

      by damn_registrars (1103043) on Tuesday July 15 2008, @12:02PM (#24198767) Journal
      Can we at least make the meta-moderation system useful? I haven't seen any indication that meta-moderation feedback goes anywhere, or has any impact on the moderations themselves (or those who gave them). As best I can tell meta-moderation is just a way to get moderation points sooner.
      • Re:my own follow-up (Score:5, Informative)

        by Firehed (942385) on Tuesday July 15 2008, @12:11PM (#24198941) Homepage

        I'm pretty sure that quite a while back one of my moderations was meta-modded as stupid (or whatever, I can't be bothered with meta anymore) and I got an email for it and the user in question lost (or regained) the point. I don't think that Slashdot really needs to hand out gold stars for doing a decent job of moderating.

    • There was a big change in the moderator system some years ago. I think it was motivated by exactly the kind of abuse [slashdot.org] you're talking about. As I understand it, Rob decided to limit mod points to people in the middle of the range of posting rates. People who post a lot never get mod points, neither do people who post very little.

      IMHO, this change actually made things worse, because they excluded the regular participants who were most committed to making the community work. People who post haphazardly are exactly the people who should not be moderating; they're the snipers and "oh yeah" types who like to tell others they're FoS, but don't have the attention span to have a serious conversation.

      Rob and his editors obviously don't agree. My guess is they've had less occasion to "correct" moderations they consider unfair (because there are much fewer mods to correct) and they see that as evidence that the new system is working.

      As for "overrated" and "underrated": these are not supposed to reflect the quality of the comment, they're supposed to be a way of correcting scores that have gotten multiple mod points when only 1 was deserved because two moderators flagged it at the same time. Personally, I don't think this happens often enough to justify two mods with so much potential for abuse. But if we must have it, you should be allowed to apply "overrated" to a post with less than 2 upmods or "underrated" to a post with less than 2 downmods. Ideally, those two mods should come within a few minutes of each other, but I suppose that would be hard to detect.

      And whatever the quality of the moderator pool, it would make a lot of difference if people actually understood what the moderations are supposed to mean. The definitions are hard to find and hard to understand. What's the difference between "troll" and "flamebait"? "Interesting" and "insightful"?

      (Hey guys, I explain stuff for a living. Give me a call.)

      At this point, it would be helpful if one or more of the editors (Rob especially) butted into the conversation, defending their policies and correcting any facts I've gotten wrong. Never seems to happen. I guess they find the resulting flame wars taxing. Understandable, but frustrating.

  • by tchuladdiass (174342) on Tuesday July 15 2008, @12:03PM (#24198787) Homepage

    What I'd like to see is the option to gray-out / collapse any comments older than a certain timestamp. Then have that timestamp automatically set to the last time a particular discussion was brought up (allowing the user to adjust it if needed, i.e., if you didn't finish reading the whole page the last time it was brought up). That way, new comments would stand out.

  • by Doc Ruby (173196) on Tuesday July 15 2008, @12:34PM (#24199361) Homepage Journal

    The biggest problem with Slashdot is that anonymous downmodding is used to suppress comments instead of posting something disagreeing with them.

    If someone modding down a comment was required to post their reason, exactly like a reply comment, that could be viewed by both regular readers and metamoderators alike (and made hideable by default in preferences), that would probably cut back a lot of the frivolous downmods, and convert them to explicit disagreements instead. Since that feature is so similar to the regular comment system, it should be quick to develop, debug and deliver.

    • by ChromeAeonium (1026952) on Tuesday July 15 2008, @02:08PM (#24201149)
      While we're on the topic of mods, I think some work needs to be done on the Funny mod. Say some one is modded funny four times and troll once, that person loses karma. I'm fine with funny mods not giving karma, but I think they should at least act as buffers from losing it. For example, a score of two funny mods and three troll mods would be the same as one troll mod. I know it isn't that important or anything, it just irks me when a funny person loses karma because some people have no sense of humor.
  • by sm62704 (957197) on Tuesday July 15 2008, @12:46PM (#24199577) Journal

    I've seen a few sigs that echo this sentiment humorously; "Slow down cowboy, it's been 11 minutes since you last made a comment. Chances are, you type faster the 11 words per minute".

    I understand the reasoning for the "slow down, cowboy", and mostly approve, but there are a few times when the slowdown seems inappropriate.

    One is in one's own journal. I don't see any reason at all to have a "slow down cowboy" in your own journal.

    The second is responding to a response to your comment, especially when you are getting to the comment through the "slashdot message system". How can it truly be a discussion when you can't reply to a response?

    The third would be on stories older than 24 hours old. By then pretty much everyone has had a chance to comment.

    I almost never comment anonymously, so I was surprised the other day when I tried to. A user posted an anonymous comment with the statement "sorry for the AC posting but I just moderated in this thread." I was going to point out that what he was doing was a bit unethical; the system is set up so you can't comment in topics you're modding for a reason. I was also going to say "there are legitimate reasons for posting AC" and wanted to illustrate this by posting AC. An hour later I still couldn't submit the comment, so I gave up. I was logged in; I checked the "no karma bonus" and "post anonymously" for the offtopic comment. If I had been posting anonymously all day I would understand this, but it was my first anonymous comment in months. I don't understand why it was so much longer than my usual four minutes.

    I was surprised to find that you can metamoderate a comment that is in response to your own comment. I wouldn't have thought the system would have been set up like that, but I've seen it twice now.

    Another suggestion would be on a user's "journal" link. Often I'll see a funny or interesting comment and want to see a user's journal, click the link and find that he's only made two journals and the latest is from some time in 2003. Rather than the link saying simply "journal, I'd like to see "latest journal entry [&date]".

    And now for something completely different, I'd like to see TWO BRICKS BEING SMASHED TOGETHER</Python>

    • by Nerdfest (867930) on Tuesday July 15 2008, @11:27AM (#24198067)
      That's not the type of 'preferences' being referred to in the article.
        • by bigstrat2003 (1058574) * on Tuesday July 15 2008, @11:56AM (#24198665)

          how about you make those annoying Anonymous Coward trolls use the old discussion system? You know, as a sort of punishment for not logging in.

          That'd be a reward. The real punishment would be forcing them to use D2.

            • by smitty_one_each (243267) * on Tuesday July 15 2008, @01:08PM (#24199969) Homepage Journal
              What's wrong with D2?
              Between me and you
              Omitting "R2", so brave
              Is a day without
              Burma Shave
                  • by DrWho520 (655973) on Tuesday July 15 2008, @03:13PM (#24202325) Journal
                    At the risk of losing karma:

                    My sig is more hate toward the moderators...

                    Love them or hate them, moderators and meta-moderators are part of the system. If all you are concerned about is karma, then you will have to weigh you desire to post against your fear of loosing karma points. My suggestion is to say what you want intelligently and damn whether it is popular. Popular speech is boring.

                    As to your post above:

                    ...it's a site developer's responsibility to make their web site work in all browsers in common usage, not just the ones they feel like.

                    I must disagree. If it exists [w3.org], it is a developer's responsibility to code to a set of standards. It is a site and browser developer's responsibility to code to a set of standards.
    • by Gewalt (1200451) on Tuesday July 15 2008, @01:51PM (#24200797)

      When did you up the number of moderator points given out at one time? Used to be that you got 5. But today I find I have 15.

      That explains why I haven't gotten mod points in the last 5 week. NOW QUIT HOGGING!