Forums Feature Suggestions lock option for /remove

I'm sure that some will not agree with me, and that is fine as I am not sure that I agree with myself, but it might be a good idea to add the ability to disable /remove via the lock options, due to the possibility of abuse, especially in conjunction with such items as $findfile. That is it

Seems like a good idea to me.

Eamonn.

If you're going to lock /remove then by the same logic you should also lock /write, /bwrite, /filter, /savebuf, /log, /remini, /rename, /copy, /rmdir, /save, and /writeini. I'm not necessarily saying it's a bad idea, just pointing out how much has to be locked in order to protect file/folder corruption/deletion.

not entirely true.. i do believe his suggestion is to lock /remove to stop findfile() loops from removing high volumes of files as scripts have done in the past.

The above "mentioned" commands, not all of them do bad things, but i do understand that given time and the knowledge any command can become a "bad command". However, /remove requires no knowledge whatsoever to use it.

Personally, i'd have liked if 'delete to recyclebin' was default but thats me.

Eamonn.

But most of the commands I've listed require as little thought or skill as /remove. The only one that is perhaps a little 'cleverer' is the use of /log.

yeah true i suppose.. i'd be nice though to give the added security, but then you might ask why isnt there a command to disable all scripting commands (not irc just scripting).

Eamonn.

There is, it's called /remote off

Not really, since /remote off stops automated tasks.

It would be nice if we could simply restrict the scope of all those file handling commands to $mircdir. This would make a much safer scripting environment while not limiting legitimate scripts, but I'm afraid it would require too much effort on Khaled's side.