RE: [NeoStats-Devel] [Commits] r174 - branches/3.0

> > 
> > Maybe getting NeoStats to maintain the ban list and a new 
> > module, to handle management of bans? Then this could handle 
> > all bans, regardless if NeoStats set it or not? My experience 
> > with other service packages is that they don't really support 
> > bans not set by themselves, so this might come in usefull?
> 
> The only reason we store the bans provided from the IRCd was 
> in response to
> a request by Trystan for statistical purposes. I do not think 
> that providing
> a list for statistical reasons is a good reason to also 
> provide a management
> console for them. It also seems pretty pointless to provide 
> such a system
> since it is already provided at the IRCd level or through 
> services if they
> manage the bans.
> 

I can't speak for other IRCd's but at least Ultimate3 doesn't let you manage
anything except klines from the IRCd level. Management of akill's etc can
only be done via Ulined servers. Anyway, since we have that code there
already, why not take advantage of it with a bot?
And the services that I've seen for Ultimate only manage their own *kill's
and not everything. 



> > > Completed ban support would also be likely the best way to 
> > determine 
> > > the method used by NeoStats in determining ownership of a 
> > given ban. 
> > > Given that every ircd provides a way to remove bans placed by any 
> > > operator, a remove command in NeoStats is just nice to have 
> > so there 
> > > is no need to provide one at all. As mentioned in the 
> TODO comment, 
> > > allowing the removal of any ban from NeoStats is likely 
> to provide 
> > > opers an ability to remove bans they may not usually be 
> > authorised to 
> > > remove so IMO, if we cannot restrict it to removing bans 
> we own, we 
> > > should not provide the functionality at all.
> > 
> > Configurable maybe? Service roots can remove any, where 
> > standard opers can only remove a subset of bans?
> 
> Since services already handles appropriate access for their 
> bans and the
> IRCd handles removal of IRCd issues bans, this system already 
> exists without
> us supporting it at all. I see no benefit in NeoStats being 
> able to remove
> bans it did not set. The only benefit in being able to remove 
> bans it did
> set is if as with services packages it offered a view of only 
> bans set by
> it. 
> 
> Why reinvent the wheel?
> 

Well, like you say, we need to correctly handle ban removals for bans set by
NeoStats, so considering your previous comments about identifing which bot
set the bans etc, I just see that it wouldn't be much more work to handle
all bans.