![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
On Mon, 17 Aug 2009 13:42:27 -0400, D Wright wrote
(in article ): Here we go ....... getting flooded with that "yenc" crap again. Why can't people who play with that stuff just submit a few good examples, instead of dumping their entire portfolio? Not surprising the offender doesn't have the stones to sign his/her name. Well, some of us might be able to repost 'em without using yENC... if we gave a damn. Ain't gonna happen given the behaviour of certain anti-yENC clowns around here. You don't see the pics. Pity. |
#2
|
|||
|
|||
![]() "hielan' laddie" wrote in message ... On Mon, 17 Aug 2009 13:42:27 -0400, D Wright wrote (in article ): Here we go ....... getting flooded with that "yenc" crap again. Why can't people who play with that stuff just submit a few good examples, instead of dumping their entire portfolio? Not surprising the offender doesn't have the stones to sign his/her name. Well, some of us might be able to repost 'em without using yENC... if we gave a damn. Ain't gonna happen given the behaviour of certain anti-yENC clowns around here. You don't see the pics. Pity. I can post perfectly good images which everyone can see without having to decode, good quality can be posted these days in .jpg files without resorting to some kind of encoding.........so why do it?.......................................As my wise teacher said many years ago "The bog mindles" |
#3
|
|||
|
|||
![]()
On Wed, 19 Aug 2009 21:24:26 -0400, Mike the Brewer wrote
(in article ): "hielan' laddie" wrote in message ... On Mon, 17 Aug 2009 13:42:27 -0400, D Wright wrote (in article ): Here we go ....... getting flooded with that "yenc" crap again. Why can't people who play with that stuff just submit a few good examples, instead of dumping their entire portfolio? Not surprising the offender doesn't have the stones to sign his/her name. Well, some of us might be able to repost 'em without using yENC... if we gave a damn. Ain't gonna happen given the behaviour of certain anti-yENC clowns around here. You don't see the pics. Pity. I can post perfectly good images which everyone can see without having to decode, good quality can be posted these days in .jpg files without resorting to some kind of encoding.........so why do it?.......................................As my wise teacher said many years ago "The bog mindles" Every single binary posted to USENET is encoded in some way. All of them. It's just that MSOE knows about some encoding methods but not others, while real NNTP clients know about the others. If you don't wish to use yENC, that is of course your choice. I prefer to use it. That is _my_ choice. You no like? Me no care. |
#4
|
|||
|
|||
![]()
hielan' laddie wrote:
[SNIP] Every single binary posted to USENET is encoded in some way. All of them. It's just that MSOE knows about some encoding methods but not others, while real NNTP clients know about the others. True. If you don't wish to use yENC, that is of course your choice. I prefer to use it. That is _my_ choice. You no like? Me no care. Now if the programs that are used to *post* the yENC'ed images were to adhere to NNTP posting RFC's, that'd be useful. AFAICT, *none* of the yENC posting programs reliably "do the right thing." And I'm not putting a stupid proxy between my newsreader and my NNTP server just to be able to view mangled posts. Cheers, Gary B-) |
#5
|
|||
|
|||
![]()
On Thu, 20 Aug 2009 11:46:51 -0400, Gary R. Schmidt wrote
(in article ): hielan' laddie wrote: [SNIP] Every single binary posted to USENET is encoded in some way. All of them. It's just that MSOE knows about some encoding methods but not others, while real NNTP clients know about the others. True. If you don't wish to use yENC, that is of course your choice. I prefer to use it. That is _my_ choice. You no like? Me no care. Now if the programs that are used to *post* the yENC'ed images were to adhere to NNTP posting RFC's, that'd be useful. AFAICT, *none* of the yENC posting programs reliably "do the right thing." In my experience yENC posts show up exactly as any other posts do. I usually can't tell the difference... until someone complains that they can't read it because they have chosen to not get one of the free or cheap utilities which will decode yENC for them. At which point I laugh at them. And I'm not putting a stupid proxy between my newsreader and my NNTP server just to be able to view mangled posts. 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. The newsreader I first used would not decode _any_ binaries on its own; it _did_, however, come with a Read Me which pointed me to where I could get 'helper apps' which _would_ decode binaries. And could be set up so that binary posts would be automatically piped to those helper apps and decoded on the fly. This was back in 1994. (It wouldn't post binaries, either... except when encoded by those same 'helper apps'. It was free, the helper apps were free, and it worked.) But, hey, man, do what you want. You don't like yENC? Cool. Don't download any yENC files. Kill all yENC posts. Ignore yENC posts. Whatever. That's _your_ choice, on _your_ system. I simply don't care what _you_ want to do on _your_ system. _My_ choice on _my_ system is to use yENC for every single binary I post. _My_ system. _My_ choice. You no like? Me no care. _You_ don't see all the posts, because _you_ don't want to use yENC. Carry on, by all means. _I_ will continue to see all the posts, including yENC posts. _I_ will post using yENC. And if you don't like it, that's just too damn bad for you. |
#6
|
|||
|
|||
![]()
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? 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. And if something looks worth a view, I can always fire up bnr and try to work out how to use it. :-) Cheers, Gary B-) |
#7
|
|||
|
|||
![]()
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). |
#8
|
|||
|
|||
![]()
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). |
#9
|
|||
|
|||
![]()
Sj wrote in
: On Thu, 20 Aug 2009 02:24:26 +0100, "Mike the Brewer" wrote: "hielan' laddie" wrote in message ... On Mon, 17 Aug 2009 13:42:27 -0400, D Wright wrote (in article ): Here we go ....... getting flooded with that "yenc" crap again. Why can't people who play with that stuff just submit a few good examples, instead of dumping their entire portfolio? Not surprising the offender doesn't have the stones to sign his/her name. Well, some of us might be able to repost 'em without using yENC... if we gave a damn. Ain't gonna happen given the behaviour of certain anti-yENC clowns around here. You don't see the pics. Pity. I can post perfectly good images which everyone can see without having to decode, good quality can be posted these days in .jpg files without resorting to some kind of encoding.........so why do it?.......................................As my wise teacher said many years ago "The bog mindles" All your posting software encodes ... MIME, UUencode, yEnc ... Most news readers will decode all of them ... it's just that MS does not support yEnc ... Years ago, Free Agent only decoded UUencode ... since many were posting in MIME, I moved the Agent ... when yEnc showed up, I upgraded to Agent 1.93 ... Sj Xnews decodes them all. And for free, too.......... ![]() |
#10
|
|||
|
|||
![]() Years ago, Free Agent only decoded UUencode ... since many were posting in MIME, I moved the Agent ... when yEnc showed up, I upgraded to Agent 1.93 ... Even though many cars are now equipped to burn gasoline or propane, gasoline is the choice most people choose to use. Then someone comes along and says that propane is the better fuel to use. I give rides to people, only if they give me propane for the ride in my car. There are people that give rides for the rider putting gasoline in their cars. Don't ignore the fact that most people still use gasoline in their cars. You can't ignore that, or change it. They like the gasoline choice, and it is easy to deal with. Some people can just barely figure out how to put gas in their cars, and will not be bothered with another way to fuel their car. It works like it is, so why try to fix something that isn't broken? So the person getting the ride is given the choice of finding someone to buy propane from, or to get a gadget that changes gasoline into propane, or to just get a ride from someone who uses gas in their car, and forget about the person that uses propane. What would you do? How does this not compute for some people? Use something that everyone can see, or just accept the fact that some people are not going to use your (propane.) -- Jim in NC |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
some planes [55 of 56] "wlhj_clart035_wwllerawindtunnel.jpg" yEnc (1/2) | no name | Aviation Photos | 0 | August 17th 09 02:43 AM |
some planes [10 of 56] "CAMP-JUSTICE-INDIAN-OCEAN-3.jpg" yEnc (2/2) | no name | Aviation Photos | 0 | August 17th 09 02:39 AM |
some planes [10 of 56] "CAMP-JUSTICE-INDIAN-OCEAN-3.jpg" yEnc (1/2) | no name | Aviation Photos | 0 | August 17th 09 02:39 AM |
some planes [11 of 11] "old-air-planes-crashed-underwater-photos-pictures.jpg" yEnc (1/1) | No Name | Aviation Photos | 0 | August 9th 09 09:36 PM |
Today at Oshkosh [20/34] - "19 One last look at the bes-sounding planes in the show.jpg" yEnc (1/1) | Just Plane Noise | Aviation Photos | 1 | July 25th 07 08:22 AM |