Slimelite BBS

Haynie Conference

Back to CLUB_AMIGA

From Peter Hans van den Muij · 1996-04-09 11:40 · #70468 in CLUB_AMIGA

In reply to Re: Haynie Conference by Asha Develder

Asha Develder wrote to me in AMIGA about Haynie Conference:

Asha,

  AD>>> Never ceases to amaze me when people uuencode text files to upload to public boards.

 PHM>> Well, maybe the files contain something that's not ASCII, for example non-ASCII ANSI characters or, as in this case, an lha-archive.

  AD> The LhA archive that was included with this file was an archived version of the text from the conference.  Even LHA'd up it was longer than the actual text file (not LHA'd and not uuencoded).

Hey, that's strange! I looked this up after I posted it, and found that I had been wrong and it had not been lha-ed, so I had been wrong in this case. But I didn't correct it as the general idea still holds.

Now, who is wrong, who didn't look it up, or who is not telling the truth? (I can't look it up, because the messages are in the virtual dustbin by now.) Strange!


 PHM>> I don't know. An uuencode of a crunch might well be shorter than the original.
  AD> I don't know what you mean by "uuencode of a crunch".

Sorry!

A crunch (crunched file) is a compressed file. For example a file that PowerPacker has been applied to, or Imploder. If the main reason to archive a file is the smaller size then archived files could also be considered "crunched".

An uuencode is, of course, the product (or action) of uuencoding (using a program to uuencode a file).

An uuencode of a crunch is the product of a program used to uuencode an archive, or a compressed file.


  AD> In my experience most uuencoded files are longer than the original,

I think I once had someone explain me uuencoding, though I could use a refresh-course, and from vague memories I would say that uuencoding will always be longer.

  AD> and definitely longer than the LHA'd file used to create it.

Yes, longer than the archive, for the same reason as above. But it will sometimes be shorter than the original file (before archiving).
(If you don't believe me, just try writng "Asha is not persuaded easily." thousand times in a file, make an lha-archive of that, and make an uuencode that. You'll see that the final final is about 1% of the original.)

This means that it *can* make the message shorter. Of course, this should be checked before using this. (Otherwise one behaves like the version of PowerPacker that will proudly claims it compressed the file, even when it really expanded it.)


  AD> I want to make things EASIER for the readers, not harder, and many people haven't got a clue as to what uuencoding is or what to do with the file once you've got it.

If those people made it into an echo, they can ask and they will usually be helped. (Fidonet is about being friendly.)
And it is easier for the readers to have a popular item uuencoded than to all have to look for it themselves, so one could be making it easier for them by uuencoding.
(Not to say you're wrong, just that the "easier" argument in itself is not enough.)


  AD> Add to that the fact that a LOT of uuencoded files get corrupted while passing through the various Fido systems, ...

Are you sayin "a LOT" of echo messages "get corrupted while passing through the various Fido systems"? Maybe that's something we should do something about, then? )-:

I did get an un-dearchiveable (sp) uuencode of the walker saturday, but that was the first time anything went wrong with that, as far as I know. How much is a LOT, by your standards?


I don't know, I feel like Joyce is right here. Occasionally there is a good reason, but they should ask her first. Maybe she should ask people she gives permission to to mention that in the file, so others would be reminded they had to ask her. (Joyce?)
 
Team-amigo                                    Peter Hans van den Muijzenberg

... I think the others in this echo made up that moderator bit.

--- April V1.05 
 * Origin: The world is beautiful, from my viewpoint. (2:282/357.36)