I found out about these features today (from another help-channel helper). I played with them for 20 minutes, and found some things I guess... 1. Only Access 60/50 can modify the Manager list (add/del/wipe). 2. Access 40/30 cannot WIPE the akick list; only access 60/50 can wipe it. 3. Access (50 or 40)/30/(20 or 10, by address) - CS Why replies highest access level (if added as all 3... 1/2/3). 4. Successor can be named Manager. 5. Access 60/20/10/-1, added by fully-registered nick, cannot be Manager simultaneously. Exception occurs when Manager is named then access 20/10/-1 is added by hostmask. Why am I posting this (without testing more)? Normally I wouldn't, but I am lost as to why manager was added. I re-read the dalnet-services@ Dec 2009 thread, and manager was brought up there. Questions I have (without testing further)... 1. Why isn't Access 40/30 combined? What can 40s do that 30s cannot? One of the 2 can be eliminated if "powers" mimic the other. If they mimic, is it practical to have both? 2. What else can 60/50s do that 40/30s cannot (aside from what I posted above, and what is on the docs page)? 3. Why not make AOp/SOp registered nick only (like manager); not hostmask? 4. Wouldn't it be more practical to offer halfops (%)... a. Users from other servers/networks can transition into DALnet easier b. Help channels can use halfops to manage lamers if ops are not present. c. Allow 5 halfops and 5 managers (combining 40/30). Halfops can be proving grounds for staff promotions to AOp/SOp. I think the addition of manager blurs the lines of Access 10/20/30/40, and complicates access levels (more than meets the eye). For me, 30s make 20s look like 10s, and 10s look like nobodys/halfops. Is the goal to replace UNSECURE? I think users enjoy playing with the manager feature (feeling more free to manage their channels, etc). I can see rants ensuing from my lack of further testing, and my assertions. People like change, and greater freedom. Lemme know if I could ever weasel a spot on the new services features test squad (before they are implemented). I enjoy testing new features. For now, maybe some discussion/findings can occur (to liven up the mailing list). I didn't get to play with MemoServ Ignore much, but I found out that MS Forward bypasses MemoServ Ignore (just as it does NickServ NoMemo). Stored memos can be 52 (per nick) despite what the docs page states (50). Anyone test the ignore max (50, 52, other)? Sorry for being unprofessional (not testing thoroughly). I am starting classes Tuesday, and running around like a chicken with its head cut off for the next week or 2. Maybe we can get some debate going from this post. Thanks, PapaSmurf --- On Fri, 5/28/10, Kobi Shmueli <kobi@DAL.NET> wrote:
From: Kobi Shmueli <kobi@DAL.NET> Subject: [DALnet-services] Channel managers and MemoServ ignores To: dalnet-services@lists.dal.net, helpers@lists.dal.net Date: Friday, May 28, 2010, 6:19 PM Hi all,
We have added two new features to services: 1) Channel managers - lets founders give almost full control over a channel. http://www.dal.net/kb/view.php?kb=196 for the full list. 2) MemoServ ignores - lets users ignore other users and nick!user@host masks (see /MemoServ HELP IGNORE).
As a side effect, ChanServ ACC command's replies have been changed. The new replies are: -2 = Channel is frozen or closed -1 = User is autokicked from the channel. 0 = User has normal access. 10 = User has AOP access. 20 = User has SOP access. 30 = User has MANAGER access. 40 = User has founder access via a NickServ access list mask 50 = User has founder access via identification to NickServ 60 = User has founder access via identification to ChanServ
News announcement is available at http://www.dal.net/news/shownews.php?id=68
FYI,
-Kobi. _______________________________________________ DALnet-services mailing list DALnet-services@lists.dal.net https://lists.dal.net/mailman/listinfo/dalnet-services