4 ms·
FWIW, many email clients -- before Gmail dumbed down email forever and no one seems to understand that email replies form a tree anymore -- also had (and maybe
by saurik 2y ago
FWIW, many email clients -- before Gmail dumbed down email forever and no one seems to understand that email replies form a tree anymore -- also had (and maybe some still do?) that way of viewing the world.
- hvis 2y agoThunderbird is still alive and developing.
- alberth 2y agoOr like the HN comment system :)
- xyzzy_plugh 2y agoThe HN comment system discourages depth as there is a relatively shallow limit to threads. There also is no in-built concept of an inbox to monitor replies.
- alcover 2y agoThis baffles me so much. It would be so simple and valuable to add.
- krapp 2y agoHacker News prefers quality over quantity and signal over noise. Deeper threads tend to result in uninteresting, low quality comments as the subject matter diverges from the topic at hand, or flamewars, so long-term engagement is discouraged.
- cubefox 2y agoI think the main reason for flame wars isn't the depth of threads but the users. Usenet had no such depth limits, LessWrong doesn't have them today.
- Dessesaf 2y agoAll these decisions add up to people just not replying to interesting questions. More often than not, nobody will reply, so all threads are just one or two levels deep. Or in the rare case someone actually replies to an interesting point, it's usually not the original poster. Probably because they had no idea that anyone had even followed up on their post. Requests for elaboration mostly go unanswered, and comments are made expecting no replies. So people just shoot ideas into the void, with interesting interactions only happening when someone famous comments.
- TeMPOraL 2y agoIt discourages reflexive replies. The depth limit is a soft one, just an extra step that perhaps gives one a chance to pause and cool down.
- layer8 2y agoNo, HN doesn’t have read/unread state, and also cuts off discussions after a day. This makes checking for new comments tedious, and prevents any longer discussions.
- dredmorbius 2y agoThere arae numerous email clients for Linux-like platforms that provide this, both text-based adn GUI. Text: Mutt, Alpine, and emacs's mailer off the top of my head. There's a listing of other clients here: <https://www.tecmint.com/best-commandline-email-clients-for-linux/ https://www.tecmint.com/best-commandline-email-clients-for-l...> GUI: Sylpheed, Thunderbird, KMail (KDE's Kontact suite still strikes me as one of the best I've encountered), Evolution, and Clawsmail. My own strong preference remains mutt, and the ability to process huge amounts of complex email reasonably well is still utterly unmatched.
- Ringz 2y agoI like mutt, but aerc [0] is imho much better. But no matter which solution you prefer, editing emails in the terminal is so much more efficient. If the majority would switch to pure text emails instead of HTML...
- dredmorbius 2y agoMissing a link?
- Ringz 2y agoSorry! https://aerc-mail.org/ https://aerc-mail.org/ And some additional sources: https://www.dennisc.net/writing/tech/gmail-aerc https://www.dennisc.net/writing/tech/gmail-aerc https://www.julioloayzam.com/guides/email-with-aerc/ https://www.julioloayzam.com/guides/email-with-aerc/ My simple config and binds that are a little bit more "vim-like": https://github.com/rafo/aerc-vim https://github.com/rafo/aerc-vim
- dredmorbius 2y agoThanks!
- steve_rambo 2y agoaerc sometimes breaks on non-compliant email because the author of the header parser refuses to introduce kludges to handle broken email. When it happens, the mail in question simply doesn't show up in the list. I fully understand that position, but it's not really ideal as a user who can't simply refuse to deal with broken crap. So after using it for a couple of months I reverted to neomutt.
- fifticon 2y agoOutlook killed it, gmail arrived at a scene with an already dead body :-(