top-posting

[Luke Plant-2]

A: It makes disk/bandwidth usage quadratic in the length of
   a thread instead of linear, and scanning a post take much longer
   since you don't know when it is going to end.
Q: What else is bad about it?
A: Because it breaks the logical sequence of the discussion.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Can we go back to what used to be pretty much universal on this list -
bottom/inline posting?  Please?

Thanks,

Luke (getting into his flame-resistant suit... :-)

--
OSBORN'S LAW
    Variables won't, constants aren't.

Luke Plant || http://lukeplant.me.uk/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jeff Anderson-6]

Luke Plant wrote:
> Can we go back to what used to be pretty much universal on this list -
> bottom/inline posting?  Please?
>  
The only problem is that this is a Google group. Google's interface by
default makes the user top post. I doubt very much that there are an
exceptionally large number of people that use Google's interface for
this group, but for the ones that do, they have to deal with Google's
silly decision.

Because they are using Google's reader, they likely aren't well versed
in mailing list etiquette anyway.

While I agree with you, I believe you may be fighting a battle already lost.

Cheers!


Jeff Anderson

[Waylan Limberg]

On Mon, Jul 28, 2008 at 10:54 AM, Jeff Anderson
<jefferya@...> wrote:
> Luke Plant wrote:
>>
>> Can we go back to what used to be pretty much universal on this list -
>> bottom/inline posting?  Please?
>>
>
> The only problem is that this is a Google group.

While I suspect that is part of it, there is also the issue of the
digest subscriber. They get all the messages for the day compiled into
1-2 emails and to respond they can't just hit reply in their email
client. Well, sometimes they do anyway and the subject line shows it,
but even if they edit the subject line to match the existing
discussion, it will still be top-posted. The only option that leaves
them is to visit Google's Groups interface and respond there, which as
Jeff pointed out, may be flawed as well.

As Jeff said:

> While I agree with you, I believe you may be fighting a battle already lost.

--
----
Waylan Limberg
waylan@...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---