| Re: Digest Authentication [message #179930 is a reply to message #179927] |
Wed, 19 December 2012 22:26   |
Twayne
Messages: 135
Registered: September 2010
Karma:
|
Senior Member |
|
|
In news:slrnkd48uu(dot)4ja(dot)hellsop(at)nibelheim(dot)ninehells(dot)com,
Peter H. Coffin <hellsop(at)ninehells(dot)com> typed:
> On Wed, 19 Dec 2012 09:40:52 -0800 (PST),
> dhtmlkitchen(at)gmail(dot)com wrote:
>> On Tuesday, December 18, 2012 6:08:59 PM UTC-8, Jerry
>> Stuckle wrote:
>>> On 12/18/2012 8:55 PM, xkit wrote:
>>>
>>>> On Dec 13, 8:15 pm, Jerry Stuckle
>>>> <jstuck...@attglobal.net> wrote:
>>>
>>>> > On 12/13/2012 7:49 PM, dhtmlkitc...@gmail.com wrote:
>>>
>> [snip entire quoted message NOTE:
>> Never fullquote on USENET (quotes the whole message,
>> signature). QUote *only* the parts you are replying to.
>> Otherwise, there is no dialogue; no back and forth.
And it limits responses too, if the reader only sees part of the problem
when the original post has been read already and is no longer visible. I
don't reassemble messages to get the original for anyone unless it's a rare
case.
>>
>> When replying type your reply, then review the entire
>> message.
>
> Sorry, but I'm not taking USENET lessons from someone who
> doesn't wrap his lines at 72 characters, as the good lard
> intended....
LOL! Good point! Same here. Whoever you mean there probably has a 200"
monitor in front of him and ... . I have a 24" LED but I don't set line
lengths to settings I know will annoy people.
A lot of people DO "fullquote" and it's not necessarily bad depending on the
length of the message.
IMO there always has to be enough of the original problem left so that
others don't have to reassemble read messages to see what it's all about. If
that's from stukey it's understandable - I don't read his posts anymore,
period. He just loves to thorn people in the ass and then proclaim how great
he is. Actually I don't generally even read replies to him anymore.
HTH,
Twayne`
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]