• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Admin: a suggestion on the script corruption problem.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Admin: a suggestion on the script corruption problem.


  • Subject: Re: Admin: a suggestion on the script corruption problem.
  • From: JollyRoger <email@hidden>
  • Date: Fri, 16 Feb 2001 12:32:46 -0600

on 2/16/2001 11:56 AM, Chuq Von Rospach at email@hidden wrote:

> If the users of these lists agree with me and someone's willing to put the
> tools together, I'll be more than happy to host them on the list site for
> download, and update the documentation to describe them and how to use them
> and support their use on the list in an official way. I don't have the
> resources to write these tools myself right now (or I would), but it seems
> to me they'd be quick, straightforward, and easy to use.
>
> This seems to me a way to make this work for people NOW, until I have time
> to find a permanent solution that doesn't involve a workaround. And I
> promise I *will* continue to look at that, this won't cause me to downgrade
> it's priority or drop it off my todo list.
>
> What do people think? I'm willing if you are, but I don't want to shove this
> down your throats if you don9t think it's workable.

I am all for it (until the list server can be fixed, of course). My
question:

Should we go the "readable post" route, where the encoded script is made
readable by the encoding tool, and the decoding tool converts it from
readable form to usable form? This route seems problematic to me, because
we'd have to come up with an algorithm that would take into account every
single character and combination of characters that might get mangled by the
server. That's going to be a big job if you want to do it right.

Or should we go the "unreadable post" route, where encoded scripts are just
big blocks of numbers (or whatever), and the decoding tool converts them
from encoded form to usable form? The advantage to this is that every
single character is encoded, so the algorithm is simple, and works for all
cases. The disadvantage to this one is that there would be no way to tell
from the post what the script does.

Thoughts?

JR


  • Follow-Ups:
    • Re: Admin: a suggestion on the script corruption problem.
      • From: Dale Saukerson <email@hidden>
    • Re: Admin: a suggestion on the script corruption problem.
      • From: Chuq Von Rospach <email@hidden>
References: 
 >Admin: a suggestion on the script corruption problem. (From: Chuq Von Rospach <email@hidden>)

  • Prev by Date: XPress: color spec manipulation
  • Next by Date: Re: WHEN WILL THE LIST SERVER BE FIXED?
  • Previous by thread: Admin: a suggestion on the script corruption problem.
  • Next by thread: Re: Admin: a suggestion on the script corruption problem.
  • Index(es):
    • Date
    • Thread