| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 50:10:51 |
| Calls: | 583 |
| Files: | 1,138 |
| Messages: | 111,309 |
If you're going to post a binary, please encode it with yenc, uuencode,
or some other appropriate armor.
The webp sent was garbled.
kthx.
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode,
or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc.
The image is WebP format,
chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
I had no problem downloading and viewing it. But since I uploaded
it, this may not mean all that much. After all, I should be able to
decode a binary I posted. It would be really sad if *I* couldn't decode something I posted.
On Sun, 27 Jul 2025 04:13:19 -0700, Kenito Benito wrote:
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc.
That's not what I see -- no yEnc header, just the RIFF following
the post:
Now what LIE(S) will you offer? I'm honestly excited to learn.
Enjoy the included image :-D
[Cue Jenny running away from the truth. Or diverting from it.]
--
A small number of the documented lies of Jerry "Jenny" Sauk. >http://jerrylies.byethost22.com/?i=2
RIFF[...rest of binary file follows...]
The image is WebP format,
I see the tag "WEBPVP8X", so I assume that is correct.
chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
I had no problem downloading and viewing it. But since I uploaded
it, this may not mean all that much. After all, I should be able to
decode a binary I posted. It would be really sad if *I* couldn't decode
something I posted.
Well, Pan is a yEnc newsreader, but chokes on the pure binary data.
I guess ForteAgent can handle that.
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode,
or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc. The image is WebP format, chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
If you're going to post a binary, please encode it with yenc, uuencode,
or some other appropriate armor.
The webp sent was garbled.
On Mon, 28 Jul 2025 05:58:41 GMT, Frank <frank@creon.earth> wrote:
On Sun, 27 Jul 2025 04:13:19 -0700, Kenito Benito wrote:
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc.
That's not what I see -- no yEnc header, just the RIFF following
the post:
Now what LIE(S) will you offer? I'm honestly excited to learn.
Enjoy the included image :-D
[Cue Jenny running away from the truth. Or diverting from it.]
--
A small number of the documented lies of Jerry "Jenny" Sauk. >>http://jerrylies.byethost22.com/?i=2
RIFF[...rest of binary file follows...]
There was much more to the post.
I did encode it as yEnc. I can't explain what might have
happened.
On Sun, 27 Jul 2025 04:13:19 -0700, Kenito Benito wrote:
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc.
That's not what I see -- no yEnc header, just the RIFF following
the post:
"Kenito Benito" <Kenito@Benito.naw> wrote in message >news:r72c8ktee5v22233n6gf0tmal500ds9lb9@4ax.com...
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc. The image is WebP format, chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
And it appeared garbled and unseeable, which is EXACTLY why I banned it in >the first place.
"Frank" <frank@creon.earth> wrote in message >news:KZjhQ.7078$v9ff.834@fx42.iad...
If you're going to post a binary, please encode it with yenc, uuencode,
or some other appropriate armor.
The webp sent was garbled.
Having a little bit of trouble there, kwillsy? Don't you know how to send a >binary file in a usenet message? On that alledged modern, advanced machine >that DOESN'T run Outlook express? (Which BTW has no trouble at all sending >binary file's) I'd help you out, but I don't have time to give you internet >lesson's.
Except one: THIS IS NOT A BINARY NEWSGROUP YOU MORON.
"Frank" <frank@creon.earth> wrote in message >news:KZjhQ.7078$v9ff.834@fx42.iad...
If you're going to post a binary, please encode it with yenc, uuencode,
or some other appropriate armor.
The webp sent was garbled.
Having a little bit of trouble there, kwillsy?
Don't you know how to send a
binary file in a usenet message?
On that alledged modern, advanced machine
that DOESN'T run Outlook express? (Which BTW has no trouble at all sending >binary file's)
I'd help you out, but I don't have time to give you internet
lesson's.
Except one: THIS IS NOT A BINARY NEWSGROUP YOU MORON.
"Kenito Benito" <Kenito@Benito.naw> wrote in message >news:r72c8ktee5v22233n6gf0tmal500ds9lb9@4ax.com...
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc. The image is WebP format, chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
And it appeared garbled and unseeable, which is EXACTLY why I banned it in >the first place.
On Wed, 20 Aug 2025 14:19:51 -0500, "Jerry Sauk"
<jerrysauk@hotmail.com> wrote:
"Kenito Benito" <Kenito@Benito.naw> wrote in message >>news:r72c8ktee5v22233n6gf0tmal500ds9lb9@4ax.com...
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc. The image is WebP format, chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
And it appeared garbled and unseeable, which is EXACTLY why I banned it in >>the first place.
You are the only one who *CLAIMS* not to be able to see this 14 year
old format. You're probably lying.
At any rate, you never banned it.
RIFF[...rest of binary file follows...]
There was much more to the post.
I did encode it as yEnc. I can't explain what might have
happened.
I can explain it.
You need to use APPROVED machines, and APPROVED format's.
On Wed, 20 Aug 2025 13:25:33 -0700, KlausSchadenfreude ><klaus.schadenfreudeREMOVE@gmail.com> wrote:
On Wed, 20 Aug 2025 14:19:51 -0500, "Jerry Sauk"
<jerrysauk@hotmail.com> wrote:
"Kenito Benito" <Kenito@Benito.naw> wrote in message >>>news:r72c8ktee5v22233n6gf0tmal500ds9lb9@4ax.com...
On Sun, 27 Jul 2025 06:49:14 GMT, Frank <frank@creon.earth> wrote:
If you're going to post a binary, please encode it with yenc, uuencode, >>>>>or some other appropriate armor.
The webp sent was garbled.
kthx.
It was sent as yEnc. The image is WebP format, chosen solely to
mock Jenny's fantasy rule that WebP is forbidden.
And it appeared garbled and unseeable, which is EXACTLY why I banned it in >>>the first place.
You are the only one who *CLAIMS* not to be able to see this 14 year
old format. You're probably lying.
This may be an instance of his actually being honest. If he's
using Windows Millennium, the most recent version of Windows he's
permitted for himself since he can't view WebP format under any
circumstances (recall his first complaint was in regards to your
linking to one on a web site), it would appear garbled.
Add that I sent it in yEnc encoding and Jenny doesn't stand much
of a chance. Microsoft has always refused to allow the decoding of
yEnc. Since MS didn't develop the compression method, it refuses to
ever allow its decoding to be a native part of the Windows
architecture. There were, and maybe still are, third party
applications to enable the viewing of yEnc files in Outlook Express.
But most people simply left OE for Thunderbird, which has the look and
feel of OE, while being able to do all the neat things the superior
readers can do. Like decode yEnc.
This may be an instance of his actually being honest. If he's
using Windows Millennium, the most recent version of Windows he's
permitted for himself since he can't view WebP format under any >>circumstances (recall his first complaint was in regards to your
linking to one on a web site), it would appear garbled.
Add that I sent it in yEnc encoding and Jenny doesn't stand much
of a chance. Microsoft has always refused to allow the decoding of
yEnc. Since MS didn't develop the compression method, it refuses to
ever allow its decoding to be a native part of the Windows
architecture. There were, and maybe still are, third party
applications to enable the viewing of yEnc files in Outlook Express.
But most people simply left OE for Thunderbird, which has the look and
feel of OE, while being able to do all the neat things the superior
readers can do. Like decode yEnc.
GEMINI says:
Users on Windows ME cannot directly view WebP images without
additional software.
Many older web browsers that still function on Windows ME may not
support WebP. However, some browsers might have a plugin available
that allows for WebP viewing, although this is unlikely given the age
of the OS. Jenny is unlikely to know how to choose, install, setup, or
use the appropriate plugin, however.
Nobody is harmed by Jenny being unable to view webp files,so it's not
a problem.