Re: The best way for @beep

• Date: Fri, 6 Sep 1996 16:40:33 PDT
• From:
  kai@xs4all.nl
• cc: darkowl@mcs.net, MOO-cows list <MOO-Cows.parc@xerox.com>
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-to: <32309EAC.17FC@las.es>

On Fri, 6 Sep 1996, Antonio Martos wrote:

> What I did to solve that is to store the strings in "binary" (It is
> posible after the hack) making a simple verb that makes the
> substitutions once. The problem is that this new prop must be -r or else
> anyone can get and use an ansi code, and this looks dangerous.
> Maybe filtering notify() can help.

Hia,

We had a problem with people who were smart enough to just eval one of the
verbs which did substitutions, and got an escape code back:

eval me.escape = $ansi:substitute("Blah[%red]Zoo")[5]
=> ""
(but this was an escape...)

Or bypassing their :notify(). The 1.8.0 option is far better, there aren't
any codes accesible /in/ the database.

Kai

--

• Re: The best way for @beep
• From: Don Schwarz <darkowl@darkowl.pr.mcs.net>

• Re: The best way for @beep
• From: Antonio Martos <martos@las.es>

• Prev: Re: The best way for @beep
• Next: Re: The best way for @beep
• Index: MOO-cows
• Thread: MOO-cows