signature placement is dumb

B

Brian Donohue

Hi,

Is there any way to make our signatures follow immediately after our reply
text when sending a reply to someone (in an email)? Entourage has always had
this annoying habit of placing the signature far, far at the bottom of the
entire email message... after all of the indented "original poster's"
message. This is just plain stupid.

MS Outlook on the PC does NOT do this.

Thanks!
 
R

Rob Buckley

Hi,

Is there any way to make our signatures follow immediately after our reply
text when sending a reply to someone (in an email)? Entourage has always had
this annoying habit of placing the signature far, far at the bottom of the
entire email message... after all of the indented "original poster's"
message. This is just plain stupid.

MS Outlook on the PC does NOT do this.

Thanks!

It's not stupid. It's proper email and newsgroup etiquette. In fact, it's in
one of the Internet RFCs.

http://www.faqs.org/rfcs/rfc1855.html

You should actually chop out anything irrelevant anyway. Take a look here as
to why "top-posting" is bad compared with "bottom-posting":

http://www.caliburn.nl/topposting.html

Basically, standard Entourage behaviour is correct, while Outlook is the
source of evil, not the other way around.
 
B

Brian Donohue

No.

Posting a signature at the bottom is bad usability for the vast majority of
email users today. Forcing someone to delve through something that they
already wrote... to get to what you wrote back to them... is bad usability.
In a highly technical conversation it may be an advantage to re-read what
you wrote for the sake of keeping the context of a conversation, but this is
completely unnecessary (and, in fact, a burden) in common email usage.

The FAQs.org write-up is 10 years old. That's an aeon in web time... back
when we didn't know jack about how to cater websites/email/etc to the common
user. A great many things about the internet have changed drastically since
1995, not the least of which are the ideas and developments in usability. In
other words, we learned something since then :)

"...proper email and newsgroup etiquette" is only your statement based on
someone's ancient "techie" idea of how things should work. Ditto for the
Caliburn write-up. They are both opinions based on an incorrect assumption
that everyone is using email to hold technical conversations. While that
USED TO be true (and may still be true for certain users such as yourself),
today the MAJORITY of users are just normal folks emailing their friends and
family. If I email my little sister at college, I don't NEED to re-read what
I wrote to her when she replies back to me... I can EASILY remember the
content and context of my original message. This holds true for the vast
majority of legitimate emails in the world today.

If you're an "old-head" techie-type and like it at the bottom, that's fine.
I've got no problem with that. But at least give the other 95% of us the
option to put it at the top, where it feels natural and makes sense to us.
 
C

Craig Deutsch

Hear, hear! :)


No.

Posting a signature at the bottom is bad usability for the vast majority of
email users today. Forcing someone to delve through something that they
already wrote... to get to what you wrote back to them... is bad usability.
In a highly technical conversation it may be an advantage to re-read what
you wrote for the sake of keeping the context of a conversation, but this is
completely unnecessary (and, in fact, a burden) in common email usage.

The FAQs.org write-up is 10 years old. That's an aeon in web time... back
when we didn't know jack about how to cater websites/email/etc to the common
user. A great many things about the internet have changed drastically since
1995, not the least of which are the ideas and developments in usability. In
other words, we learned something since then :)

"...proper email and newsgroup etiquette" is only your statement based on
someone's ancient "techie" idea of how things should work. Ditto for the
Caliburn write-up. They are both opinions based on an incorrect assumption
that everyone is using email to hold technical conversations. While that
USED TO be true (and may still be true for certain users such as yourself),
today the MAJORITY of users are just normal folks emailing their friends and
family. If I email my little sister at college, I don't NEED to re-read what
I wrote to her when she replies back to me... I can EASILY remember the
content and context of my original message. This holds true for the vast
majority of legitimate emails in the world today.

If you're an "old-head" techie-type and like it at the bottom, that's fine.
I've got no problem with that. But at least give the other 95% of us the
option to put it at the top, where it feels natural and makes sense to us.
 
B

Brian Donohue

Heh, don't get me wrong... I am not knocking anyone's choice. I just think
we should have a choice between the two.

Anyway, I will try out the Apple Script that was mentioned earlier :)
 
R

Rob Buckley

No.

Posting a signature at the bottom is bad usability for the vast majority of
email users today. Forcing someone to delve through something that they
already wrote... to get to what you wrote back to them... is bad usability.

That's why you chop out the extraneous or irrelevant. Hence...

"...proper email and newsgroup etiquette" is only your statement based on
someone's ancient "techie" idea of how things should work. Ditto for the

Actually, some _people's_. Isn't that what etiquette is supposed to be: The
rules put together by society on how to behave? I'm not so deluded as to
think I should be making up my own etiquette that others should follow.

Whether you agree or disagree with etiquette, that's what you're supposed to
go by. Etiquette can evolve or change but as the result of _people_ changing
it, not Microsoft. Unless you want to learn your social skills from Bill
Gates, of course.

You can _flout_ etiquette if you want or argue that netiquette is
irrelevant, but those are different matters from arguing that etiquette is
something different from what it actually is. And I at least have an RFC to
back me up...
family. If I email my little sister at college, I don't NEED to re-read what
I wrote to her when she replies back to me... I can EASILY remember the
content and context of my original message. This holds true for the vast
majority of legitimate emails in the world today.

Then you delete the stuff you don't need to repeat, which is also suggested
by the RFC. In fact, if you want to argue on usability grounds, it's
mandatory. Check item five of this guide to avoiding information overload:

http://www.useit.com/alertbox/20040105.html

I'm not sure you could argue Jakob Nielsen is an old-style usability expert.
You can try, I suppose.

Anyway, editing out the extraneous reduces the amount of text your sister
needs to download and saves her modem costs if she's on narrowband. Or space
in her DB or her hard drive. Or whatever.

In fact, you can delete the entire message and just send her a completely
fresh message without any quoting. In fact, why don't you? Unless it's for
the sake of some kind of 'etiquette'. ;-)
If you're an "old-head" techie-type and like it at the bottom, that's fine.
I've got no problem with that. But at least give the other 95% of us the
option to put it at the top, where it feels natural and makes sense to us.

I don't believe I said you shouldn't be able to, only that you shouldn't.
And the option's there in Entourage. I don't remember asking for its
removal. Unless I'm having those blackouts again, of course.

Notice, incidentally, how bottom-quoting allows me to respond to each point
of your posting in turn, rather than sticking everything at the top and
forcing you to scroll down and then back up again to read my next paragraph.

Anyway, before this turns into a flame war of rampant silliness, I just
thought I'd say you're free to do whatever you want. Top quote if you want.
And if you think it's because it's better, all the better indeed. It's good
for people to think about usability and politeness on this InterWeb thing. I
just think that existing RFCs, etiquette, usability and indeed costings lead
to bottom-posting being better and more polite.
 
B

Brian Donohue

No flame-war, I promise :) Not from me, anyway.

"Etiquette" is only relevant to the group that creates it. For example, in
the USA, people greet by shaking hands. In other societies, people greet
with a kiss on the cheek.

While you and your peers may think it polite to bottom-post, not all user
groups agree with that. Many of us consider it IMpolite to bottom-post, as
it is confusing, and a hassle for us to read your messages. An RFC, ideal,
or whatever written by one group really means absolutely nothing to another
group. You cannot make the mistake of treating EVERYONE who uses the
internet as being the same "type" of user as yourself... there are many
"types". I'm not trying to discriminate against any "group", just realize
that there are different groups of internet users that behave in different
ways. This may be hard for people to understand, but one person's view of
etiquette is not necessarily another's view.

The RFC you referred to wasn't written by the average internet user. It
wasn't written by any "society". The real here "RFC" isn't something on
paper, it's the way the majority of people feel/act. Like you said, that is
"...what etiquette is supposed to be: The rules put together by society on
how to behave...". Bill Gates isn't a society. Neither is Jacob Neilsen. Nor
are faqs.org or www.caliburn.nl.


All Jacob N's article (item #5) says is "Write short. J. K. Rowling is not a
good role model for email writers." That hardly proves or disproves anything
we're discussing. It simply means that we should cut out extraneous
information...


....And there's the beauty of top-posting... with top posting, you don't NEED
to edit anything out. It's effectively "edited out" for you (automatically)
by the simple fact that all of the "old" text is PLACED BELOW the new stuff.
When the reader opens a top-posted email, they...

1st: read the NEW relevant information (aka the reply)
2nd: come to the signature line, which signifies the end of the new
information
3rd: they then have the OPTION of reviewing any/all of the previous
information as needed

Readers can clearly see the delineation between the new info and the old,
from the placement of the signature and by the indented "old" text.


This, of course, leads to the inherent FLAW of bottom-posting... people's
tendency to be "lazy" and *NOT* edit out all of the extraneous info when
bottom-posting. While YOU seem to be very good at weeding out the junk, most
are not (especially common users). While the IDEA of bottom-posting may be
good, the implementation of it is not, because it requires users to take an
extra step (bad usability).


Simply put, top posting is perfect for most common users. Bottom posting
seems to be perfect for more technical users like yourself. I happen to be
part of the in-between generation I guess. I'm a technical person in a
technical career, but I prefer top posting. Many of us in my age group are
like this :)


I have no problems with anyone's opinions, so I'm not flaming you in any way
at all. I guess I'm just sick of hearing "techie-type" people trying to
dictate to the layman on how they "should" be doing something. That's just
nonsense.
 
R

Rob Buckley

While you and your peers may think it polite to bottom-post, not all user

Could you explain to me who my "peers" are? Do you think I hang out with The
Bottom-Posting Gang or something?
groups agree with that. Many of us consider it IMpolite to bottom-post, as
it is confusing, and a hassle for us to read your messages. An RFC, ideal,
or whatever written by one group really means absolutely nothing to another
group. You cannot make the mistake of treating EVERYONE who uses the

The RFC is designed for etiquette and making messages easier to read. Since
it's a "Request for Comments", you could always comment on it and get it
changed. Unless you're feeling conspiracy-theory minded and believe that
some unseen cabal has written these rules purely to annoy you.

Maybe it wasn't put together by an "average Internet user", but it was put
together by people who had been having discussions on newsgroups, etc (there
were 1,000 comments on the RFC when last I looked) about what was the best
and most efficient way of responding in their experiences.

Of course, if etiquette is just about some arbitrary series of rules and the
"tech guys" just telling the "layman" what they should do, YOU WON'T MIGHT
IF I SHOUT THE REST OF THIS MESSAGE. I'M SURE IT'LL BE AS EASY TO READ. Oh
wait, it's not.
internet as being the same "type" of user as yourself... there are many
"types". I'm not trying to discriminate against any "group", just realize
that there are different groups of internet users that behave in different
ways. This may be hard for people to understand, but one person's view of
etiquette is not necessarily another's view.

Indeed. I'm from England and my most immediate friends are English, Welsh,
Scottish, Irish (Northern and Southern), Greek, Italian, Indian, Pakistani,
German, Danish, Swedish, Norwegian, South African and Australian. You know
what? They all, I don't know... behave slightly differently from each other.
Astonishing. I also find it quite easy to understand that there's this big
group of people on the Internet called "Americans", for example. They talk
differently, spell differently and everything, too. It's amazing. What a
weird and wacky world we live in, full of these "differences" of which you
speak.

This new embracing of differences is good, though. However, just in case
you've forgotten, the thread you started is called "signature placement is
dumb" and you described bottom posting in your original message as "just
plain stupid". You have effectively gone to France and told them that their
cheek-kissing is "IMpolite", far inferior to the US handshaking ritual and,
to re-iterate, "just plain stupid".

My response was merely to point out that cheek-kissing has its advantages in
France and that when in France, you're supposed to do as the French do. You
can perhaps argue that handshaking has greater virtues and people in France
don't kiss on the cheek any more, at least judging by your friends at the
Ex-Pats party, but that's a different matter.

The RFC you referred to wasn't written by the average internet user. It
wasn't written by any "society". The real here "RFC" isn't something on
paper, it's the way the majority of people feel/act. Like you said, that is
"...what etiquette is supposed to be: The rules put together by society on
how to behave...". Bill Gates isn't a society. Neither is Jacob Neilsen. Nor
are faqs.org or www.caliburn.nl.

Much of everyday etiquette is learned behaviour, rather than rules (in
comparison to true Etiquette, which unless you were born into High Society,
is very much something that has to be taught). What many people believe is
"natural" and "right" is what they've seen and got used to. Top-posting is
popular mainly because it is the default behaviour in Outlook Express and
Outlook and most people either don't know how to change it or choose not to.
My hazy recollections of email clients before then is that they all tried to
enforce bottom-posting. So top-posting is an etiquette that has been
determined by Microsoft, effectively. Had Outlook's default been
bottom-posting, I'm pretty sure this discussion would be moot.

Similarly, whether lots of people use frames in web sites is immaterial to
whether it's actually a Good Thing or not. Most first-time web designers use
frames move on to Flash intros, etc, because it's what they've seen and
associated with being professional. Doesn't mean that they're right. Doesn't
mean those web sites couldn't be improved.
...And there's the beauty of top-posting... with top posting, you don't NEED

to edit anything out. It's effectively "edited out" for you (automatically)
by the simple fact that all of the "old" text is PLACED BELOW the new stuff.
When the reader opens a top-posted email, they...

1st: read the NEW relevant information (aka the reply)
2nd: come to the signature line, which signifies the end of the new
information
3rd: they then have the OPTION of reviewing any/all of the previous
information as needed

Readers can clearly see the delineation between the new info and the old,
from the placement of the signature and by the indented "old" text.

Well, let's have a think about that. Maybe your email messages are less
discursive, in which case top-posting does have its advantages. But what do
you do if you want to respond to a long email, point by point, for example.
If it's a reply to a reply to a reply, how do you know who wrote what, once
one or more people join the conversation?

If we're talking about usability and different Internet sub-groups,
incidentally, then studies have shown that US email users tend to use it as
a replacement for the phone, to fire off short responses, usually in an
informal manner. European email users, however, tend to regard it as a
replacement for the letter (less so for the TXTing generation). So maybe
top-posting works better in the first context, but not so much in the
second.
This, of course, leads to the inherent FLAW of bottom-posting... people's
tendency to be "lazy" and *NOT* edit out all of the extraneous info when
bottom-posting. While YOU seem to be very good at weeding out the junk, most
are not (especially common users). While the IDEA of bottom-posting may be
good, the implementation of it is not, because it requires users to take an
extra step (bad usability).

Isn't the point of etiquette to improve things and to take consideration of
others needs? Holding doors open for people is harder than letting them just
slam in their faces, but isn't it the better thing to do? Are we now
changing etiquette to become "whatever takes the least effort"?

The _intent_ of bottom posting + editing is to make the reader's life
easier. Maybe top posting without editing makes the _sender's_ life easier,
but that's not the point.

Also, top-posting is easier when you're just firing back exchanges of
information and can't be bothered to delete previous data. But it's harder
as soon as you start interacting with the contents of the previous mail
since you have to scroll down to read, then scroll back up to write, scroll
down further to read more, then scroll back up again to write more.

The recipient then has to read the new message. If they can work out and
remember what each point is about, fine. If they can't, they have to scroll
down and down and down and down, then maybe back up, then down again. All
these things are extra steps. You only really get a usability advantage with
top-posting in brief exchanges.
I have no problems with anyone's opinions, so I'm not flaming you in any way
at all. I guess I'm just sick of hearing "techie-type" people trying to
dictate to the layman on how they "should" be doing something. That's just
nonsense.

Hmm. You're a "technical person in a technical career" writing about how
people should really top-post. I'm a journalist. For the sake of irony,
would you like to re-read and have a think about that last paragraph. ;-)

Sorry, couldn't resist.

We've probably exhausted this topic now...
 
B

Barry Wainwright [MVP]

We've probably exhausted this topic now...

I doubt it :(

Exchanges like this keep cropping up from time to time and some people get
very entrenched in one position or the other.

Myself - I'm more flexible. These are my guiding principles:

1. If a thread has already developed, I will happily top post or bottom
post in line with the prevalent method already in use.

2. If I am replying to a long message from an individual with a simple, one
line or one word answer I will usually top-post.

3. If I am replying to a mailing list I will usually bottom post (it is a
lot easier for digest readers to follow), but heavily cut unnecessary text
(like here)

4. If a message needs several points addressing (like Rob's reply to
Brian), I will interleave replies with quoted text and leave the sig at the
bottom

5. I will feel free to vary from these guidelines to suit any particular
instance without the slightest twinge of guilt.

:)
 
R

Rob Buckley

Myself - I'm more flexible. These are my guiding principles:

1. If a thread has already developed, I will happily top post or bottom
post in line with the prevalent method already in use.

2. If I am replying to a long message from an individual with a simple, one
line or one word answer I will usually top-post.

3. If I am replying to a mailing list I will usually bottom post (it is a
lot easier for digest readers to follow), but heavily cut unnecessary text
(like here)

4. If a message needs several points addressing (like Rob's reply to
Brian), I will interleave replies with quoted text and leave the sig at the
bottom

5. I will feel free to vary from these guidelines to suit any particular
instance without the slightest twinge of guilt.

All sounds reasonable to me! I strayed to top-posting for a while once,
which was fine for 2), but hard for most other situations, I found. I'd
probably do 2) sometimes if it was easy to switch between styles (eg Reply
to message= Apple R, Reply at top of message=Apple, Ctrl R). Otherwise,
bottom-posting seems to work best for most instances.
 
F

Fonnesbeck, Chris

Posting a signature at the bottom is bad usability for the vast majority of
email users today. Forcing someone to delve through something that they
already wrote... to get to what you wrote back to them... is bad usability.
In a highly technical conversation it may be an advantage to re-read what
you wrote for the sake of keeping the context of a conversation, but this is
completely unnecessary (and, in fact, a burden) in common email usage.

Absolute nonsense. I suppose you read books back to front and from right to
left also? Recall that this is a newsgroup; you are saying you'd prefer to
find a thread, but start reading it from the bottom, scrolling upwards? Your
argument makes little sense.
 
T

Theresa

When my reply is placed at the top, I can plug in what I want to say,
find the point of replies I want to delete, and then click and flick
the ball on my Trackman to highlight extraneous matter, then hit
delete. I don't have to click to where I want to insert my reply,
especially if my mail and newsreader automatically plugs in a signature.

This is just so much easier. If I need to reference the reply, it's
there, but it's not obstrusive. I'm usally only replying to the last
reply anyway. I can't stand programs that force me to place my reply at
the bottom. I even recommended to the maker of my newsreader that
instead of automatically plugging the person's response at the bottom,
that he at least give users an option. He thought it was a great idea.



Hear, hear! :)

--
Theresa Mesa
Mesa Design House
http://mesadesignhouse.com

Please reply to newsgroup
 
T

Theresa

Simply put, top posting is perfect for most common users. Bottom posting
seems to be perfect for more technical users like yourself. I happen to be
part of the in-between generation I guess. I'm a technical person in a
technical career, but I prefer top posting. Many of us in my age group are
like this :)

Interestingly enough, the web developers on the two web development
mailing lists I'm on all top-post. Oh, and the CSS mailing list I'm on
top-posts. I'd say we're a pretty techie group. It's probably that
"above the fold" concept that's been ingrained in us. Don't make people
scroll and scroll to get to they information they need. Show them the
gist of what they need in the first screen - "above the fold." That's
usability. I'm sure Jacob N. would agree. If I'm responding to a post,
don't make me scroll and scroll to get to what I need to read. I've
already read the stuff at the top with the bottom-post way of posting.
Why do I want to look at it again?

We just tell people to remember to trim their posts to save bandwidth.
I have no problems with anyone's opinions, so I'm not flaming you in any way
at all. I guess I'm just sick of hearing "techie-type" people trying to
dictate to the layman on how they "should" be doing something. That's just
nonsense.


--
Theresa Mesa
Mesa Design House
http://mesadesignhouse.com

Please reply to newsgroup
 
Top