Re: making posts unreadable for google groupers?

On 21 Sep 2007 01:32:08 GMT, in message <slrnff67q0.pk.no.spam@xxxxxxxxxxxxxxxxxxxxxx>,
Blinky the Shark wrote:

Ralph Fox wrote:
On 20 Sep 2007 17:21:41 GMT, in message <slrnff5b2e.p41.no.spam@xxxxxxxxxxxxxxxxxxxxxx>,
Blinky the Shark wrote:

Ralph Fox wrote:
On 20 Sep 2007 10:32:38 GMT, in message <slrnff4j3f.gbv.no.spam@xxxxxxxxxxxxxxxxxxxxxx>,
Blinky the Shark wrote:

X-WebTV-Stationery: Standard; BGColor=black; TextColor=black

Unfortunately, viewing the larger picture shows this: When people use
such kludges to obscure the content of their Usenet messages, they are
handing the Google Groupers a WIN, by requiring NON-Google-Groupers to
change THEIR Usenet participation habits by adding another step.
This is a bad idea: giving Google Groupers any wins is counterproductive.


Back in the DejaNews days, one could put HTML code into message
headers

Just to clarify, using ones NNTP client.

And still have a valid header?

Yes, it is still a valid header.
It was Deja that was mis-interpreting it.

Scripting in a header is legal?

The Organization header is plain text.

_Any_ string of us-ascii characters in the range ' ' (0x20) to '~' (0x7E)
is a legal value.

Any system that interprets it as scripting is buggy.



and have Deja interpret it as HTML. So for example

| Organization: <script type="text/javascript">top.location.replace("http://some.where.else/";);</script>

That was no more an extra step than is your WebTV header.

Of course it's not. It's another header. What's your point?

My point is that there was a way of making posts unreadable for
DejaNews users.

Unfortunately, this no longer works with Google (the new owner of
the Deja archive)


The
proposed body kludges that I pointed out are bad ideas are not headers,
so you're comparing apples to oranges. I never said automatically
inserted headers are bad.

And why did you imply that automatically-selected charsets are a bad idea?

Automatically? I thought the stuff proposed here was about the
non-GG-user having to futz around to read them.


Any scheme that requires the *reader* to futz around is not good.
OTOH if the *poster* wants to futz around, that is his/her own choice.

Nothing forces the *poster* to use the scheme to post.


As for charsets. A number of clients automatically interpret
the charset specified in the Content-Type header, so the *reader*
does not have to do any futzing around. [See RFC 1521 section 7.1.1
and RFC 2046 section 4.1.2.]

If the poster's audience are all using such readers, then your
comments do not apply to the charset scheme which I posted in
news:v2i4f316rtgnbassbqs774hj05abgcik51@xxxxxxx . The reader
does not have to futz around.

If the poster's audience are using readers which do not
automatically handle this standard header parameter, then
the poster should not use this technique.


--
Cheers,
Ralph










.

Relevant Pages

  • Re: X-No-Archive, here we go again ;-)
    ... Only google expires them in a week. ... We all know Google Groups ... Google will honor this header. ... Before 1992, and at my university, posts never expired until disk space ...
    (news.software.readers)
  • Re: X-No-archive considered harmful
    ... If Google didn't heed that header or have some other opt-out ... Their archive includes posts that predate Deja, ... Perhaps the earth was just reacting ...
    (comp.programming)
  • Re: X-No-archive considered harmful
    ... If Google didn't heed that header or have some other opt-out ... Their archive includes posts that predate Deja, ... Perhaps the earth was just reacting ...
    (sci.math)
  • Re: X-No-archive considered harmful
    ... If Google didn't heed that header or have some other opt-out ... Their archive includes posts that predate Deja, ... Perhaps the earth was just reacting ...
    (sci.crypt)
  • Re: Xnews out of memory problem
    ... appears on Google. ... You got the original Subject header right, ... evidence as part of an attempt to understand. ... toothy-yet-shit- eating grin (as stupid as judging people ...
    (news.software.readers)