On Fri, 21 Aug 2009 10:01:20 -0400, Gary R. Schmidt wrote
(in article ):

hielan' laddie wrote:
[SNIP]
1 you don't have to put any kind of a proxy between your newsreader and a
server to read yENC posts. You can get a real newsreader which will read
them
directly, or you can download them as text and have a utility convert them
after the fact. And they are hardly 'mangled' if they are delivered
properly
to those who have real newsreaders and/or decoding utilities.
Yes, I *could* change, but why should I have to?

You don't. Carry exactly as you do. It will mean that you miss some posts,
but this is _your_ choice.


If the bloke who came up with yEnc had the sense to comply with the
various RFC's for Usenet news, these discussions would *never* happen.

Nah. If Mickeysoft had included a yENC decoder on their crap this would never
happen. The boys who did Thunderbird would have included a yENC decoder in
there, too, just because one was in MSOE... and between them, the presence of
yENC decoders in MSOE and Thunderbird would eliminate 99.999% of those who
complain about yENC 'cause they'd have nothing to complain about.


And if something looks worth a view, I can always fire up bnr and try to
work out how to use it. :-)

Your system. Your choice. If you don't want to view yENC-encoded posts, this
does not affect me in the least. My problem is when someone else tries to
tell me to reconfigure _my_ system for _his_ convenience. My system is
configured the way _I_ want it. If this causes problems for others, then
those others can:

1 use the various free or cheap methods to get around the problem

2 killfile me

3 post whinges, and thereby generate amusement.

Thank you for choosing option (3).