Subject: Re: Inspiring new approaches to Quota

From: Albert Paul Jimenez III <[email-masked]>
Date: Thu, 27 May 1993 18:53:45 -0700

One method thats possible, but takes server support is that of disk useage.  I believe that a 'blank' object takes up something under 100 bytes... so its not 
how many objects you have, but their actual *size* that counts.  OTOH, it could
be argued that using disk-based 'quota' discourages such space wasting niceties
as _comments_ and _documentation_ so this is not a completely satisfactory 
choice either. The only _real_ good way of enforcing good use of system 
resources is to give unlimited _allowable_ quota, but limited _acceptable_ use.
With the god or gods (er... system owners, admins, sysops, whatever) having the
final say on what is and isnt acceptable use and manually checking up on people
every once in a while.
  However, this is extremely time consuming, not to mention boring... hmm..
OTOH, it could be fun... have a 'showoff-day' on the mud where only programmers
and gods are allowed on, and they have to 'show-off' their stuff to the god, 
explain why its useful, etc...
  IMHO, no system is satisfactory to guarantee that someone in power can be
trusted... so dont give out that kind of power... when/if I run a mud, it will
probably have a set of tools, similar to that of a $builder, but more spec'd 
towards my mud, that will allow me to give the power of creation to people 
without having to give them programmer permissions...
They *will* have an object quota, but it will be in the 'finite, but very large
' category, meaning if they _ever_ reach their quota, something's run amok.

My humble opinion on a topic worth discussion...

 --Zachary

---

From: Blart Wendo <[email-masked]>
Date: Fri, 28 May 1993 09:31:37 -0700

One problem with the quota system is exits - they take up too much quota for
what they do. Ideally exits should be entirely free. We're considering
defining exits purely in a list defined on the room. One problem is allowing
aliases for exits, which we are thinking of getting round by defining default
exit names and aliases.

Andrew/Borogove

---

From: "Edward L. Wallace" <[email-masked]>
Date: Fri, 28 May 1993 10:11:48 -0700

>aliases for exits, which we are thinking of getting round by defining default

DragonsFire MOO has implemented something along these lines.  I'll leave it
up to our implementor to give you the full details.  However we've managed
to work aliases, etc. etc.  Even Multiple Word exits work (I believe).

F'lyr/Ted @ DragonsFire
Falryx @ Lamba