Have to disagree, even though I'm a big gmail user and I do like it way better than the other webmail systems. A thread in gmail looks more like a pile than a real thread - it's nowhere near as smooth as navigating in a newsreader. It presents newer messages on top, and I sometimes find myself confused when I can't tell if certain text is new or quoted in an old message.
And there is no "kill thread" - you can set up a filter, but that's a longish operation and I don't think it lets you say "I don't want to follow this particular discussion" as opposed to "filter out this subject/author".
It all comes down to gmail being a mail system, not a forum system. And goog's forum system, groups, is pretty sad.
You should really read through http://mail.google.com/support/bin/answer.py?answer=6594 to find out what gmail does that you don't know it does. For instance the "kill thread" functionality that you don't think exists is called mute and is available by pressing m.
I stand by my previous comment. Every piece of basic functionality that was requested is actually present in gmail. The aesthetics are not the same, and some things require hitting two keys (for instance y then o to archive the current message and move to the next - keeping the current one from showing up again unless you look for it). But the basic functionality is all there.
Killing a thread is not the same as killing a branch. Gmail linearizes multi-branch conversations. Multi-branch conversations occur more naturally in fora and mailing lists, but it can be useful to ignore a branch.
Is there a way to get gmail to highlight posts on mailing lists that are replies to one of your own messages to the list? That's one of the main features of newsreaders I miss (HN's threads?id= view is kind of a clunky approximation).
Not reliably, but here is the best substitute that I am aware of.
Click on the icon at the top left, select Email Settings.
Search for Personal level indicators and turn them on.
Save changes.
You'll now have indicators of which emails were sent to you personally, and a stronger indicator of emails sent only to you. When people respond to you they tend to reply to you, so it tends to work out reasonably well.
That's pretty useful, thanks! It seems like they ought to be able to directly mark messages which are reply to one of my messages via message-ids, but this does catch the majority of them.
I didn't know about the "mute thread" capability - thanks. But maybe "the aesthetics" are somehow crucial - I've always had keyboard shortcuts enabled in gmail, but following a modern mail thread (in which most people top-post, in any case) is still not the same as following one of the old usenet threads. Not the same feeling of smoothness or being aware of the flow of conversation and a message's place in it.
I was, in any case, talking about forums, not mail systems. It seems that none of the modern forum software even wants to give me something as super-basic as not showing messages I've already read. Exceptions are few. And it's in forums that I need "kill thread" and "kill followups" (I suppose gmail labs has that, too), not in my email. I have no idea why that is; certainly it's possible to replicate the old software with today's tech, and for all I know the wonderful new forum software already exists, but it's not being used very widely. And here I am in 2011 using phpBB boards and livejournal and HN, and they are all much clunkier and less-featured than tin and trn, when it comes to actually following conversations.
I looked at it now, and it seems like you can mark forums read, but once inside a forum, like http://iwt.mikevitale.com:8080/gaming/forum/show.iwt?forumid..., you can't mark messages and threads read - they all show up. Or maybe I missed something. Anyway, it still gives me the same feeling as virtually every forum - here is a space in which people converse 99% of the time in plain text, and the technology they use to structure and follow these conversations is far more primitive that what we used in 1991 (when threading really came into its own) and very arguably worse than in 1981-1990, too.
And all this while the technology used to zip their messages around the globe and display them is the stuff of fantasies.
In today's world, all of the information for personalization has to be tracked on someone's central server. That's a lot of data per user. If you have a lot of users, that doesn't scale very well. And thanks to the stateless nature of the web, it is natural to have to process that data on every single hit.
Historically with Usenet, all of the information for personalization was distributed along with the data. The information for personalization was generally much less than the data for Usenet. And the processing of the data set was generally done once per forum per Usenet session, followed by much viewing and reading of data.
The result is that when sites like Slashdot popularized web forums, tracking that kind of detailed individual reading history didn't seem like a critical feature. If you've got one or two webservers serving a semi-popular forum (I believe that HN runs off of a single CPU), that feature just isn't going to be seen as a critical need.
I do understand that the current web infrastructure is not made for this, but given demand, it /could/ be adapted for the sort of reading that we are nostalgic about. There are obscure forums that I sometimes read on the portal bsh.co.il - this is an Israeli social work portal. Click on a message in a forum like http://www.bsh.co.il/forums/AllMessages2.asp?Fnumber=10 - there is going to be a checkmark next to the message you clicked from now on, even if you reload the browser (presumably, there is a cookie). This is a small custom-written forum with very little programmer muscle behind it, I doubt it's more than a couple of guys. If they can do it, everyone can do it - and it's a small step to hiding threads completely, etc., etc.
I've concluded that there is just no demand for sophisticated threading/reading software of the type we had in the '90s. If there was demand, there is certainly technology to fill it. If they can run Linux in a browser complete with a little C compiler, they can run the equivalent of trn. As you pointed out yourself, Gmail covers the basics already - why not make it more sophisticated and bring the technology to Google Groups? No demand. Otherwise, one of the sources of innovation in this industry - big corps, startups, or academic/open source, would have filled it. Even if it required extending HTTP/HTML somehow - these extensions happen quickly when really needed.
The features that you are talking about are essential for carrying on extended, complex conversations in a high volume environment.
The high volume discussion forums that we have today are mostly geared towards providing and filtering discussions of topical items for short periods of time, while blocking spam. (Not a big problem on the classic Usenet.)
The result is that we have things like voting systems, but the implicit assumption that any old conversation is automatically dead. (An assumption that is implicitly guaranteed by the fact that the forum becomes unusable.) So that leads to lack of motivation to improve software for this use case.
Yeah, tell me about it - I poked in here more or less by accident (tab still open) and found your reply. Everyone else is long gone, of course.
You're right about topicality being important, but there are tons of forums which I've followed (on history, for example, or on science) where nothing is topical and threads go on for 140 phpBB pages or more. Needless to say, these threads are unusable, especially compared to Usenet. So why not make software for it? People write software for more obscure niches all the time.
> The aesthetics are not the same, and some things require hitting two keys (for instance y then o to archive the current message and move to the next - keeping the current one from showing up again unless you look for it).
Looks like you don't know everything about Gmail shortcuts yourself. The same feature is available under '{' and '}' (or '[' and ']', but in this case the behavior depends on the label you are currently in).
