UWCS/choob — Issue #401: Don't allow admins to silently overwrite aliases
Author: FauxFaux
Created: 2011-11-03 11:59:59+00:00
State: open
Labels: bug-p2, plugin

Currently it's very easy to break other people's aliases:

```
alias colour
'colour' (LOCKED) was aliased to 'MFJ.Colour' by 'SpeshulChoob'.
alias colour reply RED
Aliased 'colour' to 'talk.reply RED' (was 'MFJ.Colour').
alias colour
'colour' (LOCKED) was aliased to 'talk.reply RED' by 'Faux'.
```

Lock, on the other hand, has a much more sensible behaviour:

```
alias commands
'commands' (LOCKED) was aliased to 'help.commands' by 'SpeshulChoob'.
alias.unlock commands
Unlocked 'commands'!
alias.lock commands
Locked and taken ownership of alias by SpeshulChoob: 'commands': help.commands
```

I propose the above `alias` failing (like it would for a non-admin), and require admins to `unlock`/`lock`.

Additionally, probably worth removing the unlock, and just have lock do it directly. Currently it prints:

```
alias.lock commands
'commands' is already locked!
```