On Sun, 23 Aug 2009 15:50:40 -0400, Mitchell Holman wrote
(in article ):

"John Crawford" wrote in
:

Yenc is suppose to save band width. No on my computer, all it does
is
flood it with useless unreadable
garbage.



Yenc might make sense when posting songs or video
clips but when it comes to simple images I have never
seen a reason to depart from the jpeg format that
everyone can read and is comfortable with.


One more time:

Every single binary posted on USENET is encoded using some method or another.
If you post a .JPG, you are posting it using some encoding system, MIME, or
UUNET, or yENC or something else. You cannot just post a .JPG, USENET is a
text-only medium and binaries must be encoded so that they look like text or
they will not show up on USENET. You choose to encode using UUNET or MIME,
depending on the default setting of your NNTP client; almost all NNTP clients
decode MIME and UUNET and yENC. Some just decode MIME or UUNET. Some still
don't decode any of those formats at all and must rely on 'helper apps' to
decode binaries. (And to encode them for upload) When I first started reading
USENET, my NNTP client at the time did not decode binaries of any format; I
had to use a helper app.

The two most prominent NNTP clients which do not decode yENC are MSOE and
Thunderbird. MSOE users, in particular, insist that others not use yENC
because their client won't read it. I tell 'em to kiss my ass. If you want to
see _all_ the pics, use a client which will decode them, or get a helper app
which will do it for you. If you insist on doing neither, that is _your
choice_. You don't get to see certain pix. Like it or lump it.