Threadtiquette
António Pedro Marques · 06 Jan 2011, 19:15
· from 2011-January.txt.gz
This is the message as the crawl holds it, before anything
here touched it. What the conversation shows has been through ingest: transfer
encodings decoded, attachments dropped, quote markers repaired, and the
archiver’s ? resolved into quotation marks and dashes. Those
repairs are judgements and some of them are wrong, which is what this page is
for. Email addresses are obscured here as they are everywhere else on the site,
so it is before our repairs rather than byte for byte.
From: entonio at gmail.com (=?UTF-8?B?QW50w7NuaW8gUGVkcm8gTWFycXVlcw==?=) Date: Thu, 06 Jan 2011 19:15:53 +0000 Subject: (urth) Threadtiquette In-Reply-To: <6AAEC320-D932-434A-9A60-7EC9B5F51AF5 at butcherbaker.org> References: <SNT123-W313C40B93C9724B6FA28F6CF0A0 at phx.gbl> <E6B6B0C272A4E74385ED136B08FDAF3502B2CD77 at timail.isys.tracegroup.com> <4D25F3C9.202 at gmail.com> <1FCCC4FE-AA5F-45B5-831D-326DAD8CBFE5 at butcherbaker.org> <4D26043F.8070103 at gmail.com> <6AAEC320-D932-434A-9A60-7EC9B5F51AF5 at butcherbaker.org> Message-ID: <4D2614E9.3050208 at gmail.com> Son of Witz wrote (06-01-2011 18:56): > So, we should quote only what is relevant, and shouldn't "top-post" > especially without deleting the long articles that trail it. Ok. That > all makes sense. I like that you top posted your reply though. Incidentally, I'm aware that it may be difficult not to toppost using an iThing. At least you're able to reply selectively - select the text you want to quote, hit reply, and it will only quote the selection in the reply. But more important than bottomposting, imo, are proper attributions, so one knows who wrote what and in which sequence. I think interleaved replying - which is incompatible with topposting - helps keep focus and avoiding repetition. It also kind of ensures that you read what you're replying to.
An unofficial mirror of a public mailing list · about & removal requests · download the archive · before the list · original archive at urth.net