Re: Strange error messages
Look, it's YOUR app that does the deletion. Tell YOUR app not to do that.
Out of what, a dozen newsreaders, (we won't mention web-based readers), how
many perform as you think they should? Two? Three?
I dunno, it just cracks me up when people whine about things they personally
have the power to fix almost instantaneously. Does it actually cause you any
problems, or even inconvenience, to reconfigure your app to stop deleting
content based upon the fascistic idea that yours is "well-behaved" and mine
isn't. YOUR app is in the minority and forever will be, YOUR app is the one
that is doing the deleting, not mine. Tell YOUR app to stop that.
In short, you're fighting a decades-old war that your side LOST years ago.
It *is* a top/bottom posting issue, you know. Your stupid apps think that a
signature (and its delimiter) must always come at the end of a post. That's
because its programmers were so fascistic as to insist that if you want talk
to their app, you MUST bottom-post replies. When a top-posted reply comes
in, your app is too stupid to allow for the possibility that there's more to
read after the signature.
--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com
PS --
"... et al." <look@sig.bcause.this.is.invalid> wrote in message
news:eDPW3N$WIHA.3400@TK2MSFTNGP03.phx.gbl...
> glee wrote:
>
>> It's the old top-or-bottom post whinge again, Gary, or so it seems.
>
> It may seem like it but, since it was you and me that went through this
> last time around, you know it isn't.
>
>
>> OE top-posts by default, so the latest signature is at the end of the
>> uppermost reply. The so-called "well-behaved" newsreaders are set by
>> default to delete text below the signature delimiter (two dashes followed
>> by a space followed by a Return, such as you and I and Robear
>> use).....the original idea being to remove the sometimes overlong
>> signatures in posts, from subsequent replies, IF only bottom posting was
>> used throughout.
>
> That's about it, except for it NOT being about top- vs. bottom-posting.
> It's about OE, when constructing a reply, putting 'content'/'quoted text'
> in the footer/signature. Stupid, but so be it i suppose. But don't then
> complain about it to your conversation-partner if the news-clients he/she
> uses follows standard practices.
>
>
>> The actual problem is the fact that the users of these so-called
>> well-behaved readers are apparently not capable of changing the setting
>> to accommodate the variety of posting methods in use today: top, bottom,
>> and inline....all of which are valid forms, as you know. These
>> self-appointed 'net police would rather whine about others not using the
>> only posting method *they* approve.
>
> Ah, come on now! When do i ever try to police the way Gary, you OR Robear
> posts? I on occasion stand up for the bullied, hopefully getting across
> that it is not anything wrong that they do, that is causing them to be
> barked at.
>
>
>> --
>> Glen Ventura, MS MVP Shell/User, A+
>> http://dts-l.net/
>> http://dts-l.net/goodpost.htm
>>
>>
>> "Gary S. Terhune" <none> wrote in message
>> news:e2RPpFzWIHA.6140@TK2MSFTNGP02.phx.gbl...
>>> Oh, we're into that "well-behaved" newsreader thing again, eh? I find it
>>> hard to believe that OE deletes any content from incoming messages, or
>>> from replies. I have yet to see mine do it. If your "well-behaved"
>>> newsreader is having problems dealing with that, or with any other such
>>> issues, seems to me that's a problem with being "well-behaved".
>>>
>>> Seems that Google News also deletes such content. What DO your
>>> "well-behaved" newsreaders insert, anyway, that would piss off Google
>>> and OE so badly?
>>>
>>> --
>>> Gary S. Terhune
>>> MS-MVP Shell/User
>>> www.grystmill.com
>>>
>>> "... et al." <look@sig.bcause.this.is.invalid> wrote in message
>>> news:Om9llgyWIHA.5132@TK2MSFTNGP02.phx.gbl...
>>>> Gary S. Terhune wrote:
>>>>
>>>>> Henry's first reply (15:26 UTC) to Robear did not include all of the
>>>>> previous content.
>>>>
>>>> Of course it didn't and that was not what i said. Of course, you can
>>>> not see in this reply what i said because, just like 'PA Bear', you use
>>>> the same news-client that is intentionally broken to cause
>>>> 'content-omissions' from people they communicate with if these people
>>>> use any well-behaving news-client.
>>>>
>>>>> Robear <pasted> in the previous stuff in his subsequent reply (18:02
>>>>> UTC).
>>>>
>>>> Yes, 'PA Bear' did. Furthermore, 'PA Bear' also manually ( for that
>>>> post only ) modified the signature-delimiter so that the next reply
>>>> from 'Henry' not only included the full body of what he replied to
>>>> (which was done also in the first reply and which what i claimed in my
>>>> post) but also included all of the 'content'.
>>>>
>>>> Note! Henry didn't change anything to get things to work since there
>>>> was never anything wrong at that end. 'PA Bear' /temporarily/ corrected
>>>> the broken posting-style of 'Outlook Express'.
>>>>
>>>> The interesting question is why, knowing the above, 'PA Bear' while
>>>> helping different people at the same time inaccurately accuses them of
>>>> doing wrong by omitting things in their replies.
>>>>
>>>>
>>>> --
>>>> "Broken lines, broken strings,
>>>> Broken threads, broken springs,"
>>>>
>>>> Please followup in the newsgroup.
>>>> E-mail address is invalid due to spam-control.
>>>
>
>
> --
> My Dylan-quote quota for this post is already used up
> as part of glee's signature above. :-(
>
> Please followup in the newsgroup.
> E-mail address is invalid due to spam-control. 
