Post a Comment
It seems that after I've posted to a "thread" I can't vote any comments thereunder up or down. They're greyed out just like they are for my own comments, but *not* like those from moderators where it actually says that they're a mod/admin.
My setting is set to "expanded".
In expanded view it still doens't work.
And it seems if I go to a specific comment (even my own, see link below) I can then vote up or down on them.
http://www.osnews.com/permalink.php?news_id=11684&comment_id=23...
Kudos to the OSNews people, threading is very cool.
The only thing that (IMHO) isn't the best is the "more..." thing. What about something like showing the exceeding comments all aligned to the last level of indentation?
Or maybe the "more" thing is made on purpose, to discourage from making the threads too long. 
How about an option to disable the password requirement every time you edit your preferences? Or is that not possible?
And perhaps we could have a link to http://www.osnews.com/topic.php
on the main page, it can take several clicks to understand what a topic icon stands for (since mouse-hover simply gives "read similar articles..."
Anyway, keep up the good job guys!
Looks good, but I prefer the flat view. But I am glad the people who like threaded have been made happy.
So, any movement on numbering comments or being able to rate (non-OSNews) stories?
By numbering comments, I just mean that the first comment to come in is 1. Comments that have been modded down still have their number, so I could be reading along and see
1. RE: Threaded view
2. Test
4. RE[2]: Threaded view
(because 3. was modded down.)
This doesn't have to be a per-user setting. That way I can easily remember which was the last post I read when I come back to read some more. Also when I decide to switch to a lower threshold I have an idea of where to look for those missing messages since they are not on their own page any more.
Rating stories would be an incredibly useful tool.
Numbering comments isn't going to work. It might have worked if we designed v3 to work that way, but we didn't, so I don't think it's practical, nor do I think the benefits are worth the time to do it. It would be cool, in hindsight, though.
Rating stories is something I'm all for, but not everyone agrees with me. Perhaps this is good topic for discussion here now. Would you all like to be able to rate ALL stories? And furthermore, would you like to see the ratings on the front page?
>Numbering comments isn't going to work. It might
>have worked if we designed v3 to work that way, but
>we didn't, so I don't think it's practical, nor do I
>think the benefits are worth the time to do it. It
>would be cool, in hindsight, though.
Pity. Maybe during the next big overhaul!
>Rating stories is something I'm all for, but not
>everyone agrees with me. Perhaps this is good topic
>for discussion here now. Would you all like to be
>able to rate ALL stories? And furthermore, would you
>like to see the ratings on the front page?
Well, since I brought it up I *will* vote for it.
Yes, I would very much like to be able to rate all stories and double yes that I'd like to see it on the front page. I hate to say it, but every now and then a dumb story (or factually incorrect one) slips through. It would be great to be able to avoid clicking into the story to find out. Having a "hide stories with score less than X" preference is the next logical step, but unessecary I think. Just showing the current score on the front page would be a boon.
Why not do some AJAX (for the browsers that support it), reload the page continioulsy in the background, on each iteration make new posts stand out. Eclipse has a nice way of marking importnat stuff in/by the scrollbar, it might be possible for to do something similar.
In any case, doing post numbering in javascript shouldn't be hard, isn't comment_id incremented with each post? Just sort them in an array and add the array index to the post.
One more thing:
when I decide to switch to a lower threshold I have an idea of where to look for those missing messages since they are not on their own page any more
Yeah, it's funny how that works. When we used to mod down comments the old way, when they were on their own page, users would flock to the comments to "see what was so bad that it got modded down." But see, the idea is that users mod down comments so people don't have to see the junk. We don't really want it all on a page, we want it out of the conversation, so to speak. You know?
>When we used to mod down comments the old way, when
>they were on their own page, users would flock to
>the comments to "see what was so bad that it got
>modded down." But see, the idea is that users mod
>down comments so people don't have to see the junk.
>We don't really want it all on a page, we want it
>out of the conversation, so to speak. You know?
I understand the concept, but it has the opposite affect sometimes. Maybe I should just set my threshold lower, but items that get -5 would still draw my attention.
I like the fact that modded down comments can be segregated from the primary conversation. But the curiosity to see what was so bad it got modded down is still there.
First off, let me say, way to go Adam and the rest of the OS News crew! (yes even you Thom).
As always, suggestions, feedback, flames, gift certificates and evites can be directed to osnews-crew at osnews dot com, or to me personally at adam at osnews dot com.
I just have to ask, has anyone really sent you a gift certificate?
I can't wait until Threading goes live for registered users. It should be interesting to see how it is visually implimented.
Although there is one thing ... In the article, it sounds like they are talking about "unthreaded views" and not "threaded views". A good example of threaded views is slashdot. There, you can easily follow a thread and replies via tree-like view. Makes it simple for both beginners and vets to follow.
Which one are you talking about?
"I don't really see the point in numbering the changes to OSNews. Does anybody really care if it's 3.0 or 3.1? I can't even see anywhere on the site where it gives the version number, besides these types of posts."
Nope. No one cares and it doesn't matter. It's just fun because lots of people use the site and enjoy new features.
Well, you don't have to reply to an IP, if you choose the "reply" to a comment, it will be linked, so you'll see which Anonymous it's directed to.
There are simply too many users who prefer to use the site anonymously for us to disable this access, although I agree that it would very likely raise the quality of the posts around here.
Why don't you just put [new] or something similar in front of new comments. Let say if the comment is less than 1 hour the [new] will be red, after 4 hours it will turn green and after 12 say black. When the comment is more than say 16 hours old you dont show [new] label at all. As I see you keep track to the time comments were submitted so no new datasets are necessary easy you just calculate the age on the fly.
Do you own research and find the appropriate timings.
Of course this does not reflect what is actually new for the users, but it is very handy when you come back say 5 hours later. Or if you wish you could track when user last visited the site and calculate the age of the comments according to that time (if cookies are not a problem for the users).
I don't know if it is possible to do in your current implementation, but I saw that on another site I regularly visit and this helps a lot.
Your post doesn't make any sense. If they feel like reinventing the wheel, its their right to do so. I am sure they have their own technical and 'political' reasons. You don't pay them to do this do you? So why are complaining? It's newsworthy because it concerns the site. Anyone who regularly visits would be interested in changes, this is especially true considering that one of the new features is threaded views.
Secondly, who are you to decide whats not newsworthy? If you don't like this article, just don't spend your time on it. Simple!








