Bad UTF-8 encoding
d4rkn1ght
I know I have to plonk some one here, but I don't know who that person is?
Some one with some serious newsreader problems. They don't know how to
encode subjects properly. Some subjects come alright, but others come
mangle and unreadable.
This only happens here. I don't get it in other groups.
Sal Hepatica
Troll bait for _Jeff?
chuckcar
news:op.u2ufy...@dark-knight.myhome.westell.com:
Plenty of strange headers to filter on.
--
(setq (chuck nil) car(chuck) )
Pieter Zijlstra
> WTF :@
>
> I know I have to plonk some one here, but I don't know who that
> person is?
Maybe Jeff?
> Some one with some serious newsreader problems.
Most-likely Jeff!
> They don't know how to encode subjects properly.
Indeed that does sound like Jeff!
> Some subjects come alright, but others come mangle and unreadable.
Hm, that's weird, maybe it isn't Jeff (?)
> This only happens here. I don't get it in other groups.
a) you didn't subscribe to the proper groups?
b) I'm done with this silly stuff and I'm going to provide some
useful information about the posts concerned.
--
Pieter
"It's dangerous to underestimate the intelligence of a customer
who grew a business that's successful enough to require a large
and complex set of software" -- Grady Booch
d4rkn1ght
<p.zylstr...@hccnet.nl> wrote:
> d4rkn1ght wrote:
>
>> WTF :@
>>
>> I know I have to plonk some one here, but I don't know who that
>> person is?
>
> Maybe Jeff?
>
>> Some one with some serious newsreader problems.
>
> Most-likely Jeff!
>
>> They don't know how to encode subjects properly.
>
> Indeed that does sound like Jeff!
>
>> Some subjects come alright, but others come mangle and unreadable.
>
> Hm, that's weird, maybe it isn't Jeff (?)
>
>> This only happens here. I don't get it in other groups.
>
> a) you didn't subscribe to the proper groups?
> b) I'm done with this silly stuff and I'm going to provide some
> useful information about the posts concerned.
>
I guess is Jeff then??
It's just hard to know who is the one. I just want to make sure so I can
properly filter the person.
d4rkn1ght
Maybe I should block threads starting with the people in question??
d4rkn1ght
wrote:
lol :D
I didn't meant it to sound like that, but now I see it!
I'm just sick of coming here and find mangle subjects. I thought it was a
problem on my end but I check with other newsreaders and see the same.
d4rkn1ght
Michael Moroney
>d4rkn1ght wrote:
>> I know I have to plonk some one here, but I don't know who that
>> person is?
>Maybe Jeff?
>
>> Some one with some serious newsreader problems.
>Most-likely Jeff!
>> They don't know how to encode subjects properly.
>Indeed that does sound like Jeff!
>> Some subjects come alright, but others come mangle and unreadable.
>Hm, that's weird, maybe it isn't Jeff (?)
What you're seeing here are replies to Jeff, and the assortment of different
newsreaders that are trying to "fix" his broken Subject: lines, each with
their own idea how it's broken and how to fix it.
Expect to get flamed by Jeff for using a standard-compliant newsreader
and not following him like a rat following the Pied Piper.
Mike Dee
> http://img525.imageshack.us/img525/8216/manglethreads2.png
> http://img264.imageshack.us/img264/3190/manglethreads.png
Setting a filter on:
Message-ID: jeff_relf
References: jeff_relf
Would cure those.
--
dee
chuckcar
news:op.u2uks...@dark-knight.myhome.westell.com:
Have you ever used the filtering capabilities of your newreader or read on
the wherefore and whys of it existing? Blocking threads is pretty well
impossible to begin with as it depends on linked lists of the references
header.
Michael Moroney
>> Maybe I should block threads starting with the people in question??
>>
>Have you ever used the filtering capabilities of your newreader or read on
>the wherefore and whys of it existing? Blocking threads is pretty well
>impossible to begin with as it depends on linked lists of the references
>header.
Not really. You can block the thread that starts with article with
message ID <x...@y.com> simply by killing any/all articles with <x...@y.com> in
the References: header. It's not 100% since the specs allow long
Reference headers to be shortened by deleting message IDs from the middle
of the References: header to keep it at a sane length, but it does mostly
work.
chuckcar
news:hcsh55$o2j$2...@pcls4.std.com:
That would block any posts from that server. Not the same Thing at all.
Michael Moroney
> mor...@world.std.spaamtrap.com (Michael Moroney) wrote in
> news:hcsh55$o2j$2...@pcls4.std.com:
>> Not really. You can block the thread that starts with article with
>> message ID <x...@y.com> simply by killing any/all articles with <x...@y.com>
>> in the References: header. It's not 100% since the specs allow long
>> Reference headers to be shortened by deleting message IDs from the
>> middle of the References: header to keep it at a sane length, but it
>> does mostly work.
>That would block any posts from that server. Not the same Thing at all.
Nope. Message IDs are (supposed to be) unique. Any reply to a post adds
the Message ID of the post being replied to to the References: list. For
example, if you killfile any post with Message ID
<op.u2ufy...@dark-knight.myhome.westell.com> in the References: line
you'll kill all replies to the original poster's "Bad UTF-8 encoding"
post. Killfiling on <hcsh55$o2j$2...@pcls4.std.com> in References: will kill
your reply to my post, this reply which I am typing now, and any other
replies to my reply, but not the entire thread. Since those Message IDs
are unique, those rules won't kill any other posts, even from the same
host.
P.S. You may have a configuration issue, since your Message-IDs have
"127.0.0.1" after the @ sign, better known as the localhost IP address.
It's supposed to be a uniquely named internet host. There's an (extremely
low) chance that another similarly misconfigured host can post a post
with the same Message-ID as one of yours, causing problems.
Pieter Zijlstra
> Here's what I get:
>
> http://img264.imageshack.us/img264/3190/manglethreads.png
Yup, that's part of a Jeff thread.
> http://img525.imageshack.us/img525/8216/manglethreads2.png
Don't know this one, may very well be caused by a MSOE client used by,
for instance somebody from China/Korea/Japan.
--
Pieter
"The first half of our life is ruined by our parents and the
second half by our children." -- Clarence Darrow.
Pieter Zijlstra
> "Pieter Zijlstra" <p.zylstr...@hccnet.nl> writes:
>
> > d4rkn1ght wrote:
>
> >> I know I have to plonk some one here, but I don't know who that
> >> person is?
>
> > Maybe Jeff?
> >
> >> Some one with some serious newsreader problems.
>
> > Most-likely Jeff!
>
> >> They don't know how to encode subjects properly.
>
> > Indeed that does sound like Jeff!
>
> >> Some subjects come alright, but others come mangle and unreadable.
>
> > Hm, that's weird, maybe it isn't Jeff (?)
>
> What you're seeing here are replies to Jeff, and the assortment of
> different newsreaders that are trying to "fix" his broken Subject:
> lines, each with their own idea how it's broken and how to fix it.
Ah, Indeed ;)
> Expect to get flamed by Jeff for using a standard-compliant newsreader
> and not following him like a rat following the Pied Piper.
I dunno, he appears to be less active in that area and moved on to more
"important" things like the use of HTML and image-links.
--
Pieter
"University politics are vicious precisely because the stakes
are so small." -- Henry Kissinger (1923-)
chuckcar
Nope. I run a mail server so I have a decent retention. It's called
Hamster. If anyone tries to spoof my posts, I just switch to Tornvall. I
use 5 servers for news feeds.
_...@jeff_relf.seattle.invalid
esoteric/outdated NNTP·clients have problems with UTF·8 headers.
I LOVE watching them fuck things up, like little morons bumping heads.
Google Groups sniffs bytes, so it NEVER gets the charset wrong.
Google rules.
Google Groups, Windows Live Mail and ThunderBird ( Gecko-class clients )
―― THE BIG THREE ―― display my headers perfectly.
You know my header isn't US·ASCII... right ?
Is it Windows-1252 ? no, it's not, so don't assume it is.
Your first clue is this ( in my headers ):
Content-Type: Text/Plain; charset=UTF-8
If that's not enough for your ( updated ) client,
the UTF-8 signature (U+FeFF) in my “Subject:” line should be.
UTF+FeFF is white·space, same as ASCII 32 or U+00A0 (hard·space).
<Windows.H>'s GetStringTypeW() tells you what is (or isn't) whitespace.
RFC 2781 ( “ UTF-16, an encoding of ISO 10646 ” ) section 3.2 says:
“ In particular, in UTF-16 plain text,
it is likely, but not certain, that an initial 0xFEFF is a signature.
When concatenating two strings,
it is important to strip out those signatures,
because, otherwise, the resulting string may contain an
unintended "ZERO WIDTH NON-BREAKING SPACE" at the connection point.
Also, some specifications mandate
an initial 0xFEFF character in objects labelled as UTF-16 and
specify that this signature is not part of the object. ”.
Steve Crook
Message-Id: <_@Jeff_Relf.Seattle.2009_Nov5.0.58am.36>:
> esoteric/outdated NNTP·clients have problems with UTF·8 headers.
> I LOVE watching them fuck things up, like little morons bumping heads.
Jeff, I bet you can't wait for IDN's to appear on the scene? :)
Aleph
<_@Jeff_Relf.Seattle.2009_Nov5.0.58am.36>, _@Jeff_Relf.Seattle.inValid sat
down and wrote:
>
> esoteric/outdated NNTP·clients have problems with UTF·8 headers.
Yeah, god forbid that the way everyone else communicates should apply to
you.
Why do you even use English? Why not invent your own language then whine
that no one else speaks it properly?
(ah, now I understand why some of your posts read like they do)
--
Aleph
This message was posted to usenet so please reply that way. Emails to
this account are very likely to be ignored.
d4rkn1ght
> d4rkn1ght <nos...@nospam.invalid> wrote in
> news:op.u2uks...@dark-knight.myhome.westell.com:
>
>> On Tue, 03 Nov 2009 20:17:44 -0500, chuckcar <ch...@nil.car> wrote:
>>
>>> d4rkn1ght <nos...@nospam.invalid> wrote in
>>> news:op.u2ufy...@dark-knight.myhome.westell.com:
>>>
>>>> WTF :@
>>>>
>>>> I know I have to plonk some one here, but I don't know who that person
>>>> is?
>>>>
>>>> Some one with some serious newsreader problems. They don't know how to
>>>> encode subjects properly. Some subjects come alright, but others come
>>>> mangle and unreadable.
>>>>
>>>> This only happens here. I don't get it in other groups.
>>>
>>> Plenty of strange headers to filter on.
>>>
>> Maybe I should block threads starting with the people in question??
>>
> Have you ever used the filtering capabilities of your newreader or read
> on
> the wherefore and whys of it existing? Blocking threads is pretty well
> impossible to begin with as it depends on linked lists of the references
> header.
>
>
In Opera, I'm able to ignore threads by right clicking on them. It is not
really blocking, but I can at least ignore those threads with mangle
subjects.
http://www.opera.com/docs/changelogs/windows/960b1/
Follow/Ignore threads and contacts
Follow and Ignore are new features for users that receive numerous
messages. It makes it easier to dismiss unimportant messages and easier to
recognise important messages.
Activate this feature by selecting Follow/Ignore in the email context menu
(or click the message subject header), then select either Follow Thread or
Ignore Thread. Also, you can click the names in the From or To headers to
enable the following or ignoring of contacts.
d4rkn1ght
> esoteric/outdated NNTP·clients have problems with UTF·8 headers.
> I LOVE watching them fuck things up, like little morons bumping heads.
Ah! Now I see!
There's something that my and anyone else esoteric/outdated NNTP·clients
can do to fix this. :D
Plonk!
Michael Moroney
>I LOVE watching them fuck things up, like little morons bumping heads.
So this puts you more in the category of a grafitti vandal. Not only are
you proud of your "artwork" like the vandal, the vandal loves it when the
building owner gets upset when he sees his building has been "tagged"
and you love seeing the damage you do.
>Google Groups, Windows Live Mail and ThunderBird ( Gecko-class clients )
> THE BIG THREE display my headers perfectly.
Software isn't like voting for president, majority rules. Software means
following the design and specification.
>You know my header isn't USASCII... right ?
The specs say it is. So,... what should it do when it sees out-of-range
characters? It doesn't say.
>Is it Windows-1252 ? no, it's not, so don't assume it is.
The RFC-2047 spec tells you how to specify whether it's UTF-8,
Windows-1252, ISO-2022-JP or whatever. No assumptions are necessary,
other than the default (US ASCII) if not specified.
>Your first clue
Software specs aren't about following "clues".
>is this ( in my headers ):
> Content-Type: Text/Plain; charset=UTF-8
That's not a "clue". That explicitly states the body of the post is in
the UTF-8 charset, plain text.
What character set do we read the headers to find the Content-Type:
line?
>If that's not enough for your ( updated ) client,
>the UTF-8 signature (U+FeFF) in my Subject: line should be.
No, the RFC-2047 header that starts out "=?UTF-8?Q?" should be. Oops,
it's missing, you fucked up!
"Updated" readers will look for it and interpret it correctly.
> Also, some specifications mandate
Usenet isn't one of them.
Pieter Zijlstra
> esoteric/outdated NNTP·clients have problems with UTF·8 headers.
> I LOVE watching them fuck things up, like little morons bumping heads.
You still don't understand it!
> Google Groups sniffs bytes, so it NEVER gets the charset wrong.
> Google rules.
BS.
> Google Groups, Windows Live Mail and ThunderBird ( Gecko-class
> clients ) ―― THE BIG THREE ―― display my headers perfectly.
You're forget about another major player in this market, Forte Agent.
> You know my header isn't US·ASCII... right?
Indeed, it contains garbage.
> Is it Windows-1252 ? no, it's not, so don't assume it is.
Indeed, it contains garbage.
> Your first clue is this ( in my headers ):
> Content-Type: Text/Plain; charset=UTF-8
That only specifies the encoding of the *body* of a post.
To keep it simple, "oops", I already read/processed your subject line
before I read your Content-Type line.
> If that's not enough for your ( updated ) client,
> the UTF-8 signature (U+FeFF) in my “Subject:” line should be.
No that's meaningless.
> UTF+FeFF is white·space,
No it's a BOM.
> RFC 2781 ( “ UTF-16, an encoding of ISO 10646 ” ) section 3.2 says:
In what way is RFC 2781 related to NNTP?
> “ In particular, in UTF-16 plain text,
UTF-8 <> UTF-16.
--
Pieter
"The use of anthropomorphic terminology when dealing with
computing systems is a symptom of professional immaturity."
-- Edsger Dijkstra
Gregory Hall
come my photo doesn't show up like yours did here:
http://groups.google.com/group/alt.astronomy/msg/433c23112a2671ee
I copied your code and used the link to my photo but all it shows is a place
holder. Do I have to use a different client and set the following headers
Mime-Version: 1.0
Content-Type: Text/HTML; charset=UTF-8
Content-Transfer-Encoding: 8bit
in order for the html to work?
Thanks,
--
Gregory Hall
_...@jeff_relf.seattle.invalid
Re: Your ( Gregory Hall's ) TEST post: http://Google.COM/groups?selm=399ngd.5el.19.1%40news.alt.net news:399ngd....@news.alt.net The “ Content-Type: Text/HTML ” line MUST be in your header and, sadly, Windows·Mail can NOT add it. ThunderBird·3 MIGHT be able to do it, I'd have to check; it's here: http://download.mozilla.org/?product=thunderbird-3.0b2&os=win&lang=en-US Also, the link ( URL ) inside your < img> tag MUST be something like: “ www.jeffrelf.f-m.fm/Barbara.jpg ”, not “ www.badongo.com/pic/7726686 ” ( which is a web page, not a JPG·file ). Further, I recommend you give www.FastMail.FM 20 bucks for a year's worth of file·hosting ( and much more ). FastMail tells you the time·stamped IP·address of everyone who downloads your files, including the URL/search·string/client used to access it ! ! FastMail lets you create multiple web/FTP sites, including password·protected sites. FastMail gives you sub·domain addressing; so you get un·limited/discardable email aliases. “Barbara”, by Gregory Hall:
eric gisse
> Jeff Relf wrote:
>
>>not “ www.badongo.com/pic/7726686 �?
>
> http://www.badongo.com/pic/7726686.jpg
>
> All he needs is a "how to" on adding headers, and to modify the link
> with a file extention.
>
> Greg, try looking into the "usenet.offline-newsreader" group(s).
>
>
>
Why are these relf droppings being put in sci.physics?
Gregory Hall
news:_@Jeff_Relf.Seattle.2009_Nov10.7.00pm.Fi...
> Re: Your ( Gregory Hall's ) TEST post:
> http://Google.COM/groups?selm=399ngd.5el.19.1%40news.alt.net
> news:399ngd....@news.alt.net
>
> The " Content-Type: Text/HTML " line MUST be in your header and,
> sadly, Windows�Mail can NOT add it.
Thanks. Forte Agent can add it and NewsMaestro can add it. I'll give it a
try with one of those. I'd like for people to be able to see pictures
directly on Google. That would really bug her and other whiners.
>
> ThunderBird�3 MIGHT be able to do it, I'd have to check; it's here:
> http://download.mozilla.org/?product=thunderbird-3.0b2&os=win&lang=en-US
>
> Also, the link ( URL ) inside your < img> tag MUST be something like:
> " www.jeffrelf.f-m.fm/Barbara.jpg ",
>
> not " www.badongo.com/pic/7726686 "
> ( which is a web page, not a JPG�file ).
That might be a problem: Hmmmm, Would this do it?
http://www.badongo.com/t/800/7726686
>
> Further, I recommend you give www.FastMail.FM
> 20 bucks for a year's worth of file�hosting ( and much more ).
>
> FastMail tells you the time�stamped IP�address
> of everyone who downloads your files, including
> the URL/search�string/client used to access it ! !
>
> FastMail lets you create multiple web/FTP sites,
> including password�protected sites.
>
> FastMail gives you sub�domain addressing;
> so you get un�limited/discardable email aliases.
>
> "Barbara", by Gregory Hall:
>
>
Thanks, I'll look into that FastMail. I don't need much file hosting but
it would be good to have something for files other than just pictures and
vids. Knowing who accessed them would be fun, too. :-)
--
Gregory Hall
Gregory Hall
news:duhkf51iqeo2agu78...@shared-secrets.com...
> Jeff Relf wrote:
>
>>not �?o www.badongo.com/pic/7726686 �??
>
> http://www.badongo.com/pic/7726686.jpg
>
> All he needs is a "how to" on adding headers, and to modify the link
> with a file extention.
Thanks, I think I can do it now. I'll try it this afternoon when I get my
real Wi-Fi back. It's out of order this morning for some reason so I'm
pirating somebody's home network that isn't secured. Don't want to do
anything on it but some Usenet so maybe they'll never notice it's being
used.
The picture link is no problem now (I clicked on the picture on the Badango
web page and got the actual picture identifier.
http://www.badongo.com/t/800/7726686 and adding the right header should be a
piece of cake in two clients I have on this computer.
--
Gregory Hall
>
> Greg, try looking into the "usenet.offline-newsreader" group(s).
>
>
>
> --
> Robb | Shared Secrets Usenet
noauth
FREAK OUT!!!
This guy is really, really worried. He should be. Rapists need to worry about retribution for their crimes.
Keep looking over your shoulder rapist!
http://offender.fdle.state.fl.us:80/offender/flyer.do?personId=35467
Gregory Hall aka Wilbur Hubbard aka Neal Warren is Cecil Warren, a convicted rapist:
He's a RAPIST AND A COWARD!
How to make the grief stop??
I'll tell you how... drop dead! Or, if you're unwilling to do that, never post to Usenet again.
I can't stop you from trolling for rape victims, but I can make your life miserable here by reminding everyone in EVERY newsgroup you frequent EXACTLY who you are.
And, if you think that law enforcement isn't looking for you, since you've violating the terms of your release, keep thinking that!!
RAPIST NOTICE:
Gregory Hall aka Cecil Warren aka Neal Warren (Capt. Neal)
Designation: Sexual Offender
Name: CECIL WARREN
Status: Released - Required to Register
Department of Corrections #: Not Available
Date of Birth: 03/24/1943
Race : White
Sex: Male
Hair: Brown
Eyes: Blue
Height: 5'10"
Weight: 147 lbs
Binghamton, NY 13905-1829
Broome COUNTY
--
(s
Gregory Hall
news:_@Jeff_Relf.Seattle.2009_Nov10.7.00pm.Fi...
> http://Google.COM/groups?selm=399ngd.5el.19.1%40news.alt.net
> news:399ngd....@news.alt.net
>
> The " Content-Type: Text/HTML " line MUST be in your header and,
> sadly, Windows�Mail can NOT add it.
I did it and it displays now just fine in Windows Mail for me.
But, it doesn't display in Google Groups like your picture did. See:
nothing but the html showing and the Content-Type: Text/HTML that I added in
Maestro and sent out as such in Maestro is changed to something else.
http://groups.google.com/group/alt.paranoia/browse_thread/thread/d6e1987a8c0d6cbe?hl=en#
In alt.paranoia it is displaying just fine in windows mail:
Here are the headers of what I sent:
From: Gregory Hall <greg...@home.fake>
Newsgroups: alt.paranoia
Subject: test6
Date: Wed, 11 Nov 2009 13:25:17 -0500
Organization: Google Groups Hackers, Inc.
Message-ID: <tb0mf5h1qh4f5d4vmc4tblv01ocbe7peia@MAESTRO>
X-Priority:
Content-Type: Text/HTML
<PRE>
<img src="http://www.badongo.com/t/800/7726686">
And here is what it comes through as:
Xref: news alt.paranoia:4298
Path: news.alt.net
From: Gregory Hall <greg...@home.fake>
Newsgroups: alt.paranoia
Subject: test6
Date: Wed, 11 Nov 2009 13:25:17 -0500
Organization: Google Groups Hackers, Inc.
Lines: 2
Message-ID: <tb0mf5h1qh4f5d4vmc4tblv01ocbe7peia@MAESTRO>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Is the alt.net server perhaps changing it???
--
Gregory Hall
Gregory Hall
news:_@Jeff_Relf.Seattle.2009_Nov10.7.00pm.Fi...
> http://Google.COM/groups?selm=399ngd.5el.19.1%40news.alt.net
> news:399ngd....@news.alt.net
>
> The " Content-Type: Text/HTML " line MUST be in your header and,
> sadly, Windows�Mail can NOT add it.
>
OK, now I wonder what went wrong. It displays the picture just fine in
Windows Mail now. No place holder - it just downloads the picture.
But, Google Groups just shows the HTML. And, even though I added "
Content-Type: Text/HTML " in the client and it was sent out as such (I
checked the sent items folder) in Windows mail it says the following from:
http://groups.google.com/group/alt.paranoia/msg/657fadee930060b7?hl=en&dmode=source
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
How did it get changed? Do you think the alt.net server changed it? Or
perhaps I only THINK I changed it in the client but am doing something wrong
so it defaults back so some standard setting???
--
Gregory Hall
Gregory Hall
> Gregory Hall wrote:
>
>>How did it get changed? Do you think the alt.net server changed it? Or
>>perhaps I only THINK I changed it in the client but am doing something
>>wrong
>>so it defaults back so some standard setting???
>
> A Sharp Turn in the Internet Tube!
> Weak Magnets!
> Excessive Torque!
> Surface Imperfections!
> Impermeable Membranes!
>
> Or, or, it jus7 didn't work ovt.
>
> You've been given the answers, Greg, investigate.
>
> jejejeje
>
>
> --
> Robb | Shared Secrets Usenet
Thanks. I just succeeded. Bwahahahhahahah. What do I win?
http://groups.google.com/group/alt.paranoia/browse_thread/thread/3f7c9b3c6a26780f?hl=en#
--
Gregory Hall
_...@jeff_relf.seattle.invalid
Re: The <img> tag you ( Greg ) posted here:
http://groups.google.com/group/alt.paranoia/browse_thread/thread/3f7c9b3c6a26780f?hl=en#
Well done ! xNews did it.
You didn't need the <PRE> tag ( PREserve whitespace ), by the way.
I see I was wrong about “ www.badongo.com/pic/7726686 ”
( it's a JPG-file, not a web-page ).
Gregory Hall
> Gregory Hall wrote:
>
>>Thanks. I just succeeded.
>
> Yes. You success-fluffy converted 4 lines of text to 1071 lines.
>
>> <div id="body" class="mb cb fontsize2 ">
>> <div id="inbdy">
>> <PRE>
>>img src ---- http://www.badongo.com/t/800/7726686
>
>
>>Bwahahahhahahah. What do I win?
>
> or, an online audition for a starring role in the "Tokyo Pussy Garden".
>
>
>
> --
> Robb | Shared Secrets Usenet
I'll take the pRon!
--
Gregory Hall
Gregory Hall
news:_@Jeff_Relf.Seattle.2009_Nov11.1.09pm.R2...
You may have been right about it. It displays as a web page so I had to
right click on the picture itself which came up with a different url in the
properties. It has a longer number as you can see if you display the post in
message source.
XNews has a handy box for custom headers and it seems to work.
--
Gregory Hall
--
Gregory Hall
_...@jeff_relf.seattle.invalid
As your ( Greg's ) xNews post PROVED,
it was News·Maestro ( not Alt.NET ) that changed your:
Content-Type: Text/HTML
to:
Content-Type: text/plain; charset=us-ascii
Gregory Hall
> Gregory Hall wrote:
>
>>"Robb" <--ro...@shared-secrets.com> wrote in message
>>news:6f9mf55louv01spgl...@shared-secrets.com...
>>> Gregory Hall wrote:
>>>
>>>>Thanks. I just succeeded.
>>>
>>> Yes. You success-fluffy converted 4 lines of text to 1071 lines.
>>>
>>>> <div id="body" class="mb cb fontsize2 ">
>>>> <div id="inbdy">
>>>> <PRE>
>>>>img src ---- http://www.badongo.com/t/800/7726686
>>>
>>>
>>>>Bwahahahhahahah. What do I win?
>>>
>>> Your choice! A ten year subscription to the Jeff Relf fanboi magazine,
>>> or, an online audition for a starring role in the "Tokyo Pussy Garden".
>>>
>
>
>
> http://img514.imageshack.us/img514/6642/tokoyopussygardenstarri.jpg
>
> You should have asked first..
>
>
And you should have clicked first...
403 FORBIDDEN!!!
--
Gregory Hall
Gregory Hall
> Gregory Hall wrote:
>
>>"Robb" <--ro...@shared-secrets.com> wrote in message
>>news:jvumf5l313caci14e...@shared-secrets.com...
>>> Gregory Hall wrote:
>>>
>>>>"Robb" <--ro...@shared-secrets.com> wrote in message
>>>>news:6f9mf55louv01spgl...@shared-secrets.com...
>>>>> Gregory Hall wrote:
>>>>>
>>>>>>Thanks. I just succeeded.
>>>>>
>>>>> Yes. You success-fluffy converted 4 lines of text to 1071 lines.
>>>>>
>>>>>> <div id="body" class="mb cb fontsize2 ">
>>>>>> <div id="inbdy">
>>>>>> <PRE>
>>>>>>img src ---- http://www.badongo.com/t/800/7726686
>>>>>
>>>>>
>>>>>>Bwahahahhahahah. What do I win?
>>>>>
>>>>> Your choice! A ten year subscription to the Jeff Relf fanboi magazine,
>>>>> or, an online audition for a starring role in the "Tokyo Pussy
>>>>> Garden".
>>>>>
>>>>I'll take the pRon!
>>>
>>>
>>> k'. You're now an (un)official poser in "Tokyo Pussy Garden".
>>>
>>> http://img514.imageshack.us/img514/6642/tokoyopussygardenstarri.jpg
>>>
>>> You should have asked first..
>>>
>>>
>>
>>And you should have clicked first...
>
>
>>403 FORBIDDEN!!!
>
> I get a 404 too, try this:
> http://img697.imageshack.us/img697/5379/garten.jpg
> it's there, for now.
>
>
Ha ha. but they got the pussies all blurred.