#3 Need a way to jupe nicks

[Reed Loden]

We need a way to specify in the euworld config file a list
of nicks for euworld to jupe. The only way to modify this
list *must* be to restart euworld. This provides
protection against anyone abusing the service. euworld
*should* kill anyone that already has the nick and
replace it with it's own one, if the nick is taken for
whatever reason. In particular an oper /kill'ing the nick,
should cause euworld to "retake" it.
(Originally submitted by Isomer)

[Reed Loden]

Logged In: YES
user_id=586984

Hmm, this functionality would be much more useful if they
can be created dynamically (i.e. /msg ccontrol nickjupe
<nick>). Why must it be done via the config file+restart?
(Originally submitted by Sengaia)

[Reed Loden]

Logged In: YES
user_id=586984

Since then admins can complain that
opers/admins/coders/smt are/can (ab)use euworld to jupe
their own personal nicks. Forcing a restart of ccontrol means
that if someone was to abuse the service then it would be
very obvious. And besides, in several months we've only had
2 new nicks to jupe network wide.
(Originally submitted by Isomer)

[Alexander Maassen]

Logged In: YES
user_id=628992

<quote>... In particular an oper /kill'ing the nick,
should cause euworld to "retake" it. .... </quote>

set the nick to be +k, then it cannot be killed :)

[Alexander Maassen]

Logged In: YES
user_id=628992

<quote> ... We need a way to specify in the euworld config
file a list
of nicks for euworld to jupe. </quote>

Move this into an sql table, for example:
create table jupenicks (
nickname varchar(64) UNIQUE,
created int4,
creator int,
reason varchar(64)
);

nickname containing the nicknames to 'jupe'
created the TS when the entry has been created,
creator the userid of the one who created the entry,
reason being the reason WHY the nick has been juped.

the nickname would be created then by (e)uworld with
realname: JUPE: <reason>

[Alexander Maassen]

Logged In: YES
user_id=628992

Summarizing all the stuff here would result in:

/msg euworld nickjupe <nickname> <reason>
- Spawn a client called <nick>
- Maintain active list through database
- Set client +k (to prevent it from getting killed)

/msg euworld unnickjupe <nickname>
- Remove nickjupe from the network.

If this idea would be accepted I could start working on it..
shouldn't be hard.