Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Discuss - bundled module/core functionality - auto update access on add/remove  (Read 6740 times)

0 Members and 1 Guest are viewing this topic.

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405

/CS ACCESS #chan add chaz 5
/CS ACCESS #chan del chaz

Should Chanserv act upon this immediately?

Config or channel option?

Discuss.

Logged

LEthaLity

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 307
    • LEthaLity

I've always thought it would be smart if it did it automatically, like vipers cs_statusupdate iirc, probably a config option
Logged

Taylor

  • Contributor
  • *
  • Offline Offline
  • Posts: 100

I requested this to be added to the core months ago, I use vipers module cs_statusupdate and its very very handy imo. And I figure config option.  I usually like very configurable settings, but doesn't seem like it should be a channel option.

Few reasons why it should be done
Constantly people add me to access lists and say "hop" or for the ones that are smart "/ns update"  but I'm lazy I like automation. And hey when you delete someone thats abusing, wouldnt you like it to be quick? :P  sure thats a rare situation but still, could happen
Logged
Cronus
irc.cncirc.net
http://CnCIRC.net

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405

Lets expand this and discuss ANY modules that make you warm and fuzzy we should consider for inclusion.

Should we also ponder over a ./module-manager similar to inspircd?
Logged

Taylor

  • Contributor
  • *
  • Offline Offline
  • Posts: 100

Well I went through my modules i have loaded and here are the ones i'd like to see added and whatnot i'll describe what each module does for those who don't know and a reason why

ircd_vhostserv - pseudo client joins a channel and the cmd !vhost is available
cs_sync - Syncs the userlist with the channels access list  (removes -o add its, etc)
cs_statusupdate - Ofc i already said why i love this :P
cs_migrate - Migrates all channel information and settings to a new channel that you have registered , I've found it useful for when transferring channels or renaming a channel and keeping the access list in tact, or for network channels its easy to make new channels and keep all of your staff the same
cs_access_notice -  If the user is online they receive a notice they were added to the access list of a channel or a memo if they were offline, same for if they were removed from a channels access list, i find this nice.. its not necessary just throwing it out there
cs_opnotice_ext - extends the opnotice feature to voices and other ones that dont notice, not sure if its done already but yea there it is
ns_sagroup - groups nick1 to nick2, i use this often enough to group nicknames together
ns_ajoin - services side autojoin list, this one is on the TODO list :P
ns_saregister - /ns saregister nick pass email < you get the idea, again useful
ns_saupdate - lets you update a nicks status (/ns update)  maybe add a 3rd param to /ns update ?
m_connect_flood - sets defcon if x connections happen in x minutes, i dont even think this one works anymore rofl.. but it would be nice to have some type of anti conn flood, im sure most disagree that services should do this but im not one of those! :P
os_amode - set/remove channel modes on all channels- have used this a few times could be helpful in floods /os amode +R !!
os_forceid - forcefully identify a user to nickserv, use this one ALOT, and everyone i know loves it
os_killuser - kill a user with operserv! heh already can kick mode and akill might as well regular kill too!
os_modreload - reload a module ofc...
os_notinchanlist - used this the other day for a botnet, can kill/join/gline/etc to users not in any channels
os_lastreg - last channel and nickname registered
bs_uptime - Don't recall if bots can tell you services uptime... but anyways there it is

Alright thats it! Discuss ^_^
Logged
Cronus
irc.cncirc.net
http://CnCIRC.net

someone

  • Anope User
  • Offline Offline
  • Gender: Male
  • Posts: 42
    • http://www.somenet.org

imho: keep it as small as possible.

I would vote for the following:
* cs_statusupdate
* cs_migrate
* ns_sagroup
* ns_saregister
* os_amode
* os_modreload
* os_notinchanlist

Also i would not add antispam/antiflood stuff. its the ircd's task to handle.
ajoin: most networks have server specific ajoins.
Logged

Taylor

  • Contributor
  • *
  • Offline Offline
  • Posts: 100

Are there no developers besides Lethality interested in this? You are the ones that code for Anope, I'd like to see what you guys thought.
Logged
Cronus
irc.cncirc.net
http://CnCIRC.net

Jan Milants

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1372

Some of the modules you posted are mine, and those that won't end up in the core will be ported to 1.9, eventually.. not in short term though.. only after the modules api s a bit more stabilized and i won't have to update all my modules upon every new release..

features like os_forceid, ns_ajoin and cs_statusupdate should probably be core functionality though, not handled by 3rd party modules.
Logged
If you like me donate coins to 1FBmZVT4J8WAUMHKqpWhgNVj3XXnRN1cCk :)

someone

  • Anope User
  • Offline Offline
  • Gender: Male
  • Posts: 42
    • http://www.somenet.org

sry for offtopic: i do not understand the description of forceid.
how does it force the client to ID?
or what does this one do?
Logged

therock247uk

  • Anope User
  • Offline Offline
  • Posts: 51
    • http://www.247fixes.com/

/os forceid nickname

forces that nick to be identifed to services.
Logged
Pages: [1]   Go Up