Slashdot Mirror


Slashdot Discussion System Updates

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.

21 of 345 comments (clear)

  1. Display bugs by schnipschnap · · Score: 5, Insightful

    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.

    1. Re:Display bugs by Anonymous Coward · · Score: 5, Insightful

      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.

    2. Re:Display bugs by Blakey+Rat · · Score: 5, Interesting

      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.

    3. Re:Display bugs by gad_zuki! · · Score: 5, Insightful

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

  2. Re:AWSD by garbletext · · Score: 5, Funny

    RTFM

  3. Re:AWSD by Vectronic · · Score: 5, Informative

    Similar thing it does in games...

    W = Up
    S = Down
    A = Out Of Thread and/or Last
    D = Into Thread and/or Next

  4. Re:crazy new idea.... by Danse · · Score: 5, Funny

    I've generally got better things to do with my time than clicking preview, waiting, blah, etc.

    Liar. I see you here on /.

    --
    It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
  5. Logging in without having to navigate away ... by apathy+maybe · · Score: 5, Insightful

    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 wank in the shower.
  6. Re:slashdot editor update: by Anonymous Coward · · Score: 5, Funny

    We can post anonymously? This makes trolling so much easier!!! Microsoft rules!

    Note to readers: I sacrificed any potential gain in fame and fortune to make this witty response work.

  7. Re:Not working by H0p313ss · · Score: 5, Insightful

    these changes seems to explain why i can't assign mod points with IE7 ?

    who knows..

    No, that's more likely to be a deliberate editorial decision. :-)

    --
    XML is a known as a key material required to create SMD: Software of Mass Destruction
  8. keep up the good work by Clover_Kicker · · Score: 5, Insightful

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

  9. Re:AWSD by Fred_A · · Score: 5, Funny

    Similar thing it does in games...

    W = Up
    S = Down
    A = Out Of Thread and/or Last
    D = Into Thread and/or Next

    But how do you fire and cycle weapons ? Mouse wheel screws up the display and clicking mostly does nothing.

    It's still very buggy IMO.

    --

    May contain traces of nut.
    Made from the freshest electrons.
  10. Re:AWSD by 0100010001010011 · · Score: 5, Insightful

    I use dvorak you insensitive clod.

    No really, I do. Any way we can change these or am I going to have to browse the web with 2 hands?

  11. Re:no h-j-k-l? by Anonymous Coward · · Score: 5, Informative

    Did you guys even try to use HJKL?
    It works perfectly for me.

  12. Re:AWSD by Anonymous Coward · · Score: 5, Funny

    browsing the web with two hands - that could make certain sites pointless

  13. What I'd like to see... by sm62704 · · Score: 5, Insightful

    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>

    --
    mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
  14. what's wrong with D2? by smittyoneeach · · Score: 5, Funny

    What's wrong with D2?
    Between me and you
    Omitting "R2", so brave
    Is a day without
    Burma Shave

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  15. Re:no h-j-k-l? by Argilo · · Score: 5, Insightful

    Or even better, just make it configurable. For Dvorak users, w-a-s-d is useless.

  16. Re:slashdot editor update: by pxc · · Score: 5, Funny

    You're posting from work, too, aren't you? ;-)

  17. Re:Require Downmodders to Justify by ChromeAeonium · · Score: 5, Insightful

    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.

  18. Re:slashdot editor update: by DrWho520 · · Score: 5, Insightful

    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, 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.

    --
    The cancel button is your friend. Do not hesitate to use it.