Skip to main content

Top-Reply in Emails and More-Than-Text Body Formats

I commented to Fighting the top reply over at Signal vs. Noise and felt like writing a small bit about it here. The basic issue was where to place your reply in an email, as any modern mail client will quote the original text and most of them place your cursor right above it. I have a couple of angles to take on this, but the conclusions all arrive at the same place.

When I still worked at an office and spent a decent portion of my time tracking efforts and monitoring going-ons throughout the company, I used Microsoft Outlook, which was enforced by the corporate IT people. Although it did bug me that I was unofficially forced to top-reply, I admit that in certain situations I do it myself, anyway. Typically, my view is that if the conversation shouldn't go on for a long time with the need to review a chronological log of what was said, and is only between two parties who will know what was said before, top-reply is really OK. When you are on a mailing list or newsgroup or in a reply-all cycle with thirty other people, it can get a little confusing trying to track the conversation.

I have probably slipped even more once I started using GMail, because it makes it easier to track the converstation by showing me all the actual emails, with quoted text collaposed. This might seem lazy, but I am a firm believer that the software is here to make our lives easier, so why do we ignore so many ways it can do that? Why not take the next step and stop quoting text by prepending a bracket or indenting it and come up with some extensions to the email protocols, maybe some new headers or a modified Multi-Part header, which would let us specify "Quoted Text" and "Reply Text", with the reply associated directly with the quoted text.

How we want this to be arranged on screen when we write it and how someone wants to read it, should not be based on the order of the bytes representing the glyphs that display the text we read. It shouldn't be a convention, it should be a preference and that preference should be free for all. This all reminds me a lot of a vast HTML-vs-PlainText-Email flame I was on the painful end of a while back, all because some people still want to use some console based email apps (which is fine) that don't support Multi-Part messages properly (which is not fine).

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Pythonic Defined

Introduction Losing is Good Strings Dictionaries Conclusion Introduction Veterans and novices alike of Python will hear the term "pythonic" thrown around, and even a number of the veterans don't know what it means. There are times I do not know what it means, but that doesn't mean I can define a pretty good idea of what "pythonic" really means. Now, it has been defined at times as being whatever the BDFL decides, but we'll pull that out of the picture. I want to talk about what the word means for us today, and how it applied to what we do in the real world. Languages have their strengths and their idioms (ways of doing things), and when you exploit those you embrace the heart of that language. You can often tell when a programmer writing in one language is actually more comfortable with another, because the code they right is telltale of the other language. Java developers are notorious for writing Java in every language they get their hands on. Ho