3 ms·
Oooooh. This is the best news of the week, maybe of the month. We've been waiting for sooo long for this. I never thought it would actually happen. So sometimes
by bambax 16y ago
Oooooh. This is the best news of the week, maybe of the month. We've been waiting for sooo long for this. I never thought it would actually happen. So sometimes Google does listen.
So maybe we can hope that not hiding http://www http://www in Chrome will become an option someday...?
- eitally 16y agoHow will you use it in a way that benefits you? My experience has been that it makes the experience much worse since you have to search for everything to find related messages and you can't click-to-sort the column headers (like on a thick client).
- bambax 16y agoI use a thick client mainly; I use GMail as an archive or when I'm away; GMail downloads my mail via POP (my primary address is not GMail). So, usually, I read mail outside GMail -- but GMail does not know what mail is already read. In a big thread, it opens all "unread" emails: the tens I read already and the last one I'm interested in. This is crazy and infuriating. Also, why are most recent emails in a thread at the bottom?? (maybe it can be configured somewhere?) And finally, like most "intelligent" features, it's much too smart (or not enough): it adds new mails to old threads. Many non-techies (and some techies as well) take an old email that has the list of recipients they're looking for, to start an entirely new discussion. Aggregating those new emails to an old thread that has nothing to do whatsoever with the subject at hand is idiotic. I just want mail sorted ante-chronologically; and then I just deal with the sorting myself.
- eitally 16y agoI understand your POP-related complaints completely, and they're all 100% valid. For the others, though.... Most recent at the bottom: because people read from the top down, I'm sure. It only adds new mails if the heuristics are correct, those primarily being the subject, but also taking into account the recipients the timestamp, and who knows what else (they won't say). If you start a new conversation from an old thread, just change the subject... especially if it has nothing to do with the subject at hand. If the subject of two messages is different, Gmail will never group them, ever. The biggest complaint I've heard from non-techy users is that with conversations they frequently miss messages because they can't adequately gauge what is unread, especially if the volume is high enough that things move off the first page with rapidity.
- bambax 16y ago> If you start a new conversation from an old thread, just change the subject... I'm not the one starting the conversation so I'm not at liberty to do anything. There is a thread. Then, days later, some member of this thread decides to start a new conversation by replying to this thread. It's the same "mailing list" but it should be a different thread. (But GMail has no way to know; this isn't a failure of GMail. The failure was, until today, to not allow to do without the threaded view). At least GMail should have had the option of breaking a thread; for each message in a thread, display a button that says "start a new thread here".
- bambax 16y ago> Most recent at the bottom: because people read from the top down, I'm sure. For one, most people is not all people: why not let us set the sort order? And secondly, I too read "from the top down", but I want to start with most recent emails; and then when I have read them all (if I read them all) I'll know the whole of the conversation -- but I can stop at anytime and still have the most recent status. If you start reading the most ancient emails, then if you stop before arriving to the most recent ones (because of a distraction, a phone call, etc.) then you have an "open" conversation in your head that is waiting to be completed. That will create a memory leak ;-)
- ax0n 16y agore: FW: re: RE: re: re: Re: fw: re: re: re: re: thursday meeting Sorry, I'm forever spoiled by GMail's automatic threading now.
- bmelton 16y agoDoes the hiding of 'http://www http://www really bother you? I remember it bothering me, until the first time I copy / pasted the URL and it is there in the pasted output.
- saurik 16y agoIt doesn't bother me /much/, but I can feel it: as I copy/paste things from there a lot, as well as sometimes edit URLs, I'm in this interesting position of having to remember weird rules regarding what is theoretically in the box and what is actually in the box, which seems really silly.
- bmelton 16y agoI personally prefer it. I don't need to see the http://www http://www before each link, and if I'm just glancing up at the location bar to see where I am, on browsers that do show it, I have to mentally parse that out. On the other hand, when I copy and paste it, that means I intend to DO something with it, like send it to a friend over IM, or email it or something, during which case I want a full, clickable link. Which is exactly what they give me. On the off chance that I want to copy and paste the de-http'd URL, then I am in no better (or worse) shape than I would be with any other browser, in that I have to paste it and strip the 'http://www http://www as I ordinarily would.
- bambax 16y agoSame for me. But the upsetting part is the attitude of the Chrome Team, who says "if you don't like it just use another browser". Well, there are lots of things I like about Chrome; this seems too small a detail to stop using it. An option buried somewhere would make me completely happy. "Too many user choices are bad", certainly; but advanced options are a different thing from decisions every user would have to make. For now the only possibility is to download the source, set a boolean somewhere in the code, and compile your own version. How crazy is that?
- lt 16y agoIt's not about user decisions. It's about maintainability and testing. These are factors that are hugely affected by the combinatorial explosion of a ton of different settings. Developers often have to make a choice, and this is one of those times. You may not like it, but I don't blame them.
- slig 16y agoChrome doesn't hide the "www", only the http:// http:// protocol, as there might be differences between the www.example.com and example.com DNS settings.
- bambax 16y agoOk, maybe. http: and // are two different things anyway; http is the protocol and // is the start of the path. (They (the Chrome team) seem to put them in the same "useless" basket.)