Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: ext bans and chmode +I  (Read 5550 times)

0 Members and 1 Guest are viewing this topic.

ups

  • Anope User
  • Offline Offline
  • Posts: 6
ext bans and chmode +I
« on: August 16, 2007, 02:27:58 PM »

1) In my opinion i think would be great if services support extbans (on unrealircd) on /cs akick, /cs unban and /cs ban.

2) I think /chanserv clear #chan excepts , should remove +I excepts, too.

Tks!
Logged

Jan Milants

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1372
(No subject)
« Reply #1 on: August 16, 2007, 03:11:36 PM »

1) services is under feature freeze till the upcoming release of the 1.8 branch

2) +I are not excepts, it are invites..
  /msg chanserv clear #chan invites
 though i must admit it seems to be missing in the help...

[Edited on 16-8-2007 by Viper]
Logged
If you like me donate coins to 1FBmZVT4J8WAUMHKqpWhgNVj3XXnRN1cCk :)

SNU

  • Anope User
  • Offline Offline
  • Posts: 158
    • http://www.firstclassirc.com
(No subject)
« Reply #2 on: August 16, 2007, 03:42:03 PM »

Hi

1) so why not assign it as "1.9" feature suggestion ?

2) oh an unknown featrue :D yeah its missing :D
Logged

jilles

  • Anope User
  • Offline Offline
  • Posts: 7
(No subject)
« Reply #3 on: August 16, 2007, 09:53:32 PM »

Missing extban support for ban exceptions (vs akick) and /cs unban can be considered a bug. The former may cause a flood, the latter leads to unexpected behaviour.
Logged

katsklaw

  • Guest
(No subject)
« Reply #4 on: August 17, 2007, 12:59:38 AM »

Quote
Originally posted by jilles
Missing extban support for ban exceptions (vs akick) and /cs unban can be considered a bug. The former may cause a flood, the latter leads to unexpected behaviour.


I think I'd have to conditionally agree. Yes, lack of support for a specific ircd feature in services is a bug as the ircd is supposed to be fully supported. The condition doesn't apply to this ircd, but could apply to the scenario if the ircd was different.

Some ircds even labeled as stable still release and change their features often which makes it hard for Anope to incorporate support while testing for stability in a devel branch to insure a good stable release. IF the ircd is constantly changing so fast that we literally can't keep up, it could potentually create a situation where we either choose to release a stable without 100% support or never release a stable version as we are continually changing src code/protocol modules.

again, this ircd in not included in the condition.
Logged
Pages: [1]   Go Up