Given the current web front-ends to UseNet, I think you're fighting a losing
battle here. Just be overjoyed when people don't have CAPS LOCK stuck down.
Plus, given the current frontends (versus the old nn / rn) it's kind of
easier for most novices to track via top post. This is especially relevant
given the current state of DejaNews ( http://www.yqcomputer.com/
) and other archival
I'm with you, but -- welcome to the future of 2007. No jet packs yet, but
we do have a lot of top posting to offer you. =\
As re caliburn:
1: etiquette? arguable, that's contextual
1b: context: actually easier to follow by leaving the relevant snippets
below. a consumption of data and response in full is easy to read on top,
or an inline response can respond to data points.
1c: the timing issue: not realllly critical anymore. UNAARTCM - usenet
ain't a real time communicative medium
2: A limitation/feature of one app isn't the definition of the field. It
actually seems easy enough to have Forte smartly understand --EOP vs --ROP
(end vs rest of post).
3: seems outvoted by the new nested messaging hierarchies which are becoming
the standard for most reads
4: arg hinges on bottom-posters kindly removing message snippets, not a real
strong argument when the population is 99.99% transient
5: my rebuttal: reading speed increases significantly with top-posting:
there's never any random guesses at where to jump the reader to
6: ? no ramifications due to top/bottom posts
7: that presumes people fighting with different standards
8: not relevant
I think the trump card here is the web newsreaders and online front ends. I
think it's Deja that actually loses context (or makes it hard to find) when
people bottom-post. Regardless, to each their own.
-Zach (who's been on UseNet since he was a *** )
Speaking for myself only.
This posting is provided "AS IS" with no warranties, and confers no rights.