Menu
▾
▴
#39 Possibility to implement GUI safeguards?
I understand the reasoning behind limited GUI operands
to M3 by default, the dreaded 'X10' scenario, as many
know it by. However, perhaps make the operands
available to anyone with even an M1, but make the
tunable parameter affect what level is needed to
inflict others with a GUI?
I.E. Allow an M1 to use the operands on themselves, but
only themselves, and as a MUCK decides either an M2 or
an M3 be allowed to use them on other users.
This would allow coders to experiment more safely, be
it to implement better client-side support for the
functions or to add the functions to their own
utilities, and without needing a possibly-risky level
of access to simply learn how to use the new operands.
Logged In: YES
user_id=7718
Reassigned as Feature Request datatype, to show up under
RFE.
Logged In: YES
user_id=7718
Considering for fb5.06. I'll be examining the code for the GUI
commands to see if it's doable.
Part of the problem is figuring out what the actual user of the
program is, if it's running under SetUID or HardUID
permissions, etc. (Do zombies get marked as GUI-capable if
their owner is?)
Logged In: YES
user_id=7718
er. 6.06. I'm too tired. :P