On the related note: how do you keep track of which comments are new since your last visit of the thread?
HN/reddit system with comments jumping around based on votes makes it hard just to quickly skim for differences.
Could there be a way to highlight not seen items? I found this a big help for information overload on the sites that do it (e.g. Google Reader, Bloglines).
However, I couldn't figure out how to do it elegantly (i.e. not needing to keep state on the server for each user) for prioritized threaded comments systems like HN/reddit.
For updates of a single page it's easy, you just need to bake timestamps for each item and page creation into HTML/JS and check them against the last page timestamp stored in the cookie.
But this system breaks down for multiple pages, as each one would need own cookie entry, otherwise any site visit would mark all new items as read.
That's btw MetaFilter's problem with highlighting new comments. Though there it's easier to follow the conversation due to linear nature of comment system.
Maybe the solution could be to have some dual way of accessing comments? Like prioritized threaded view for the first view and linear time ordered view for subsequent following?
I wrote a greasemonkey script to help me. It marks comments that have already been read. The way it marks comments is ugly and probably backwards (i.e. you probably only want to mark new comments, not the other way around). I did it as a proof-of-concept, mostly, but this thread convinced me to make it available.
I agree about the comment movements but it has been discussed here before. It would be nice to have the option to keep comments the way they are (moving) or to view them based on the time they were left.
If you know which comments on a page are new, then you also know which ones are old. The easy answer is to just gray out the older posts (only remotely challenging because the gray background of the page is about the color I WOULD have suggested for old comment text) -- and just leave the new comments as they are.
That allows you to easily skim the page for new content, while still allowing you to see the new posts in context.
A Digg-style collapse would also probably work, but for some reason, I see grayed out text more in line with the ycombinator mantra.
I really like this idea too, just like stars in Gmail. A star would appear next to the article name in the index page (and detail page). One click and a star next to the article.
Works like a charm in Gmail. No need to even float stars to the top, just allow the user to filter only starred articles with one click.
I like the way Reddit does this -- when someone replies to a comment you made, your mailbox icon at the top right glows red.
Doesn't solve the question of following whole threads, but it's great for dialogue (not just because I notice when people reply to me, but because other people notice when I reply to them).
This would be nice. I'd like to suggest a few things too. Sometimes I find good threads or interesting submissions that I want to read/analyze in the future, mainly because I don't have time at the moment, so I upvote threads. My saved list keeps growing even though I have done dealing in some of them. it would be great if you can delete it from saved list.
Let the server remember when a user has last opened a thread. If it is re-opened by the user, show only (or emphasize) postings with a newer timestamp.
My random thoughts on a way to keep track of this:
1. RSS feeds where the link goes to the hn thread instead of the linked page? Though not everyone uses an RSS program integrated with their browser and opening an external program to keep track of HN threads isn't exactly good UX.
2. Keep track of how many comments were made when someone first views the thread and if there's any new comments, change the link color back to black instead of the grey that would show that it was already viewed.
3. The star icon previously mentioned. Have items automatically decay from the list after a certain amount of time (or time without a comment) to keep it clean. Upvotes can/should double as favorites since hn keeps track what someone voted for already.
I would like the option to get a summery email every 12 to 24 hours that shows which of my comments where responded to. I know you can look through your personal comments, but it's easy to miss someones response and after a few days it seems silly to send a detailed answer which is unlikely to be read.
I track conversations I'm involved in through the Threads link at the top (which is quite useful). I'd like to be able to have a one click add-this-conversation-I'm-not-involved-in-to-my-Threads-list button.
1 point by emmett 1 hour ago | link | parent |edit | flag | track
For code blocks, instead of "two-spacing", could you implement a delimiter, e.g. [code][/code]? For something more elegant than BBCode, maybe ##...## could delimit code.
Same here.
Someone wrote a Web ap that would sort of do this for you, and emit an RSS feed (It think), but it would create an entry for each up or down vote, which was not that useful to me.
My technique is super low-tech. In my bookmarks bar, positioned conveniently below the site's favicon, I have a folder which is called "For Later". Into this folder I drop stuff I'll want to come back to at some point. Then (and here's the super part of my super low-tech claim), when I'm done with it I move it to another folder called "x" which I periodically delete and re-create.
This works everywhere with no extensions or anything, I use Foxmarks to sync the bookmarks themselves between machines (which you could skip if you only used the one machine), that's it.
To be honest, I usually just keep the thread open in a tab for a few hours until things die down. That said, I generally only comment on a handful of threads per week, so that's a manageable system for me. For those of you who participate more, I think that wouldn't work so well.
I upvote articles that I don't have time to read, but want to keep track of. I've been doing this for at least a year, since the /saved?id=vlad feature came out (articles a user upvotes are available via that suffix to the url.)
HN/reddit system with comments jumping around based on votes makes it hard just to quickly skim for differences.
Could there be a way to highlight not seen items? I found this a big help for information overload on the sites that do it (e.g. Google Reader, Bloglines).
However, I couldn't figure out how to do it elegantly (i.e. not needing to keep state on the server for each user) for prioritized threaded comments systems like HN/reddit.
For updates of a single page it's easy, you just need to bake timestamps for each item and page creation into HTML/JS and check them against the last page timestamp stored in the cookie.
But this system breaks down for multiple pages, as each one would need own cookie entry, otherwise any site visit would mark all new items as read.
That's btw MetaFilter's problem with highlighting new comments. Though there it's easier to follow the conversation due to linear nature of comment system.
Maybe the solution could be to have some dual way of accessing comments? Like prioritized threaded view for the first view and linear time ordered view for subsequent following?