freenode / atheme-fn Goto Github PK

I suggest to add a command similar to /NS VHOST that works for group contacts.

It can work by checking in a flie/DB if the user that is triggering the command is a group contact, and checking if the cloak that the GC is attempting to add/remove have a prefix of that group. After that, it can work like NS VHOST.

Example: /NS CLOAK <account> ON <group_prefix/something>

With this command the GCs will can manage the group cloaks by themselves and reduce the staffs work.

Another suggestion is create a group of trusted users that can use this command to add unaffiliated cloaks, so these users can help to give unaffiliated cloaks when no staff is online.

As discussed: it would be nice if there was a single-line syntax for easy project registrations, something like

/msg projectserv register projectname #channelspace cloakspace contact1 contact2 contact3

chances are that space is not a good delimiter because for projectname it is potentially valid (didn't check the code), feel free to take whatever is sane.

A single-line syntax for projects with multiple channel / cloak spaces is debateable, but I'd say the above will cover 90% of cases and make people very happy.

Mainly by cloak namespaces. For instance, a command like /msg ProjectServ LISTCLOAK f* would list all projects with a cloak namespace starting with f, such as freenode with the freenode/* namespace.

Searching by channel namespaces would only be useful in edge cases where there exist no registered channels in a namespace (so ChanServ LIST and INFO don't help)

If ProjectServ marks exist, these should be noted in the GCs' NickServ info and channels' ChanServ info.

For example, I imagine this looking like (changes in italics):

ChanServ: Information on #acme:
ChanServ: Founder    : ...
...
ChanServ: Flags      : ...
ChanServ: The #acme namespace is registered to the MARKED acme project
ChanServ: *** End of Info ***

NickServ: Information on gc-nickname (account gc-account):
NickServ: Registered : ...
...
NickServ: Flags      : ...
NickServ: Group contact for acme (MARKED; #acme; acme/*)
NickServ: *** End of Info ***

(The bold, all-caps "MARKED" fits in well with atheme which uses the same style in other messages to sopers regarding NickServ marks)

Obviously, this info should only be shown to sopers. PRIV_PROJECT_AUSPEX specifically seems like a good fit.

e.g. SET abc NAME AbC says "A project named AbC already exists. Please choose a different name." even if SET abc NAME abc_; SET abc_ NAME AbC would work.

Adding the following metadata to projectserv as discussed:

• registration timestamp
• person who registered it
• primary flag for contacts
• public flag for contacts

The latter should affect the output in chanserv / nickserv as well, as in: contacts marked as public should be listed if even a user without service privileges does a lookup. Something like

Public group contacts for foo: baa, bar, baz

Primary / Alt group contact on the other hand can be internal information, similar to displaying all group contacts in chanserv as well to privileged users.

Right now, CLOAK ADD requires cloak namespaces to be given as just their base, e.g. foo or about/bar. People might try to give it as about/bar/ or about/bar/* and the intent with those seems clear enough, so it's probably reasonable to accept it and strip off the trailing /* when storing it.

CLOAK DEL probably should do the same.