Nice tribute to *Kentucky Fried Movie*.
--
Carl Fink nitpi...@nitpicking.com
Read my blog at blog.nitpicking.com. Reviews! Observations!
Stupid mistakes you can correct!
Right! Wait...huh?
It's considered polite not to quote .sig files.
> Right! Wait...huh?
In the long "Fistful of Yen" sub-movie? The toy robot?
--
Carl Fink nitpi...@nitpicking.com
> On 2009-11-06, MarkT <heartof...@hotmail.com> wrote:
> >> Read my blog at blog.nitpicking.com. =A0Reviews! =A0Observations!
> >> Stupid mistakes you can correct!
>
> It's considered polite not to quote .sig files.
Another unfriendly thing about Google Groups[1] is that it doesn't
auto-trim .sigs in replies, the way most newsreaders do (or can be set
to do). Of course, that doesn't allow GG users to abrogate their
responsibility to properly trim their replies.
1. Apparently created by incompetent software engineers who were
almost, but not completely, unfamiliar with usenet.
Brian
--
Day 277 of the "no grouchy usenet posts" project
> 1. Apparently created by incompetent software engineers who were
> almost, but not completely, unfamiliar with usenet.
What they do is "suppress" a space character when it ends a line (is
followed by a CR or LF). The .sig delimiter of "dash, dash, space"
becomes "dash, dash" and of course that's not the proper delimiter for a
.sig. I *bet* that if they didn't suppress the space then when you
clicked reply the .sig would be automagically removed, like any good
news reader or email client does.
Just another case of Google thinking they know "better" how to treat
content than the user does. (They still "suppress" received copies of
email sent to mailing lists, making it impossible to verify that your
email was distributed to the list thru the well known and often used
process of receiving your own copy back FROM the list server.)
jc
> Default User wrote:
>
> > 1. Apparently created by incompetent software engineers who were
> > almost, but not completely, unfamiliar with usenet.
>
> What they do is "suppress" a space character when it ends a line (is
> followed by a CR or LF). The .sig delimiter of "dash, dash, space"
> becomes "dash, dash" and of course that's not the proper delimiter
> for a .sig.
I know, every attempt at a signature coming from GG is broken.
> I bet that if they didn't suppress the space then when
> you clicked reply the .sig would be automagically removed, like any
> good news reader or email client does.
You think so? They'd have to build that into their software, even
though it couldn't ever work. On second thought, that might be their
style. I guess we should be happy they switched to automatically
quoting on replies and not conflating leading spaces so it destroyed
indentation for code, as they did in the beginning.
It's "dancing bear-wear"[1] - it's not that the bear dances well, it's
that we are amazed that a bear dances at all. The programmers want us
to be amazed that there's this online usenet archive and access, and
ignore that they really didn't do the job well.
jc
[1] From _The Inmates are Running the Asylum_.
It's been so long since I saw that movie, all I remember is Betty Thomas
naked. And I'm not sure if that was "KFM" or "The Groove Tube".
It's hilarious and worth finding again, IMO.
IMDb says Betty Thomas was in Loose Shoes. The reviews say it wasn't as
good as KFM, Groove Tube, American Raspberry, Tunnelvision, etc.
jc
-Mike "it's against the rules to post "me too""...
>> Another unfriendly thing about Google Groups[1] is that it
>> doesn't auto-trim .sigs in replies, the way most newsreaders
>> do (or can be set to do). Of course, that doesn't allow GG
>> users to abrogate their responsibility to properly trim their
>> replies.
=v= Though of course they routinely do abrogate it. It's all
part of the problem of using lameoid browser "textarea" controls
to do all the editing in.
> And never-ever top post. These "rules" were made up back when
> people had to wait forever for a page of text to load on their
> dialups. I can't imagine what they were thinking as they paged
> through eight days of quotes to get to the bottom and find
> that someone had posted "me too"...
=v= The "rule" to trim replies is still a very good idea.
=v= Good newsreaders knew to collapse eight days of quotes into
one line that you could choose to expand as needed, a technology
introduced in the 1980s. (GG does have an implementation of
this, but it's basically worthless.)
=v= Between top-posting or bottom-posting, the best choice is to
do neither; but in cases where people absolutely refuse to trim,
edit, or otherwise maintain any semblance of context within the
message body, bottom-posting was recommended simply because,
duh, that's the sequence people read in. At least, it was the
sequence before blogs flipped everything upside-down.
<_Jym_>