[irc/rqf/shadowircd.git] / IDEAS

Some of this may not be possible to do in 2.3...

- go TS6 only? [partially done; TS6 is always enabled now]
- client.c, channel.c is very 2.8 style still. it'd be nice to pack them into their own namespace and 
  such. moreover, the other 2.8 code needs similar rewriting/reworking too...
- internally split out +o/+v "ranks" into a series of permissions. this could allow for configure-defined 
  special access levels, halfops, etc. (would need to match globally, somehow. extra SVINFO param?)
- somehow hide channel operators like ircnet can do?
- SASL opering?
- link failover?

--
$Id: IDEAS 3552 2007-08-09 06:50:13Z nenolod $
Commit	Line	Data
a6ac2e91	1	Some of this may not be possible to do in 2.3...
a6ac2e91	2
abe616bb	3	- go TS6 only? [partially done; TS6 is always enabled now]
a6ac2e91	4	- client.c, channel.c is very 2.8 style still. it'd be nice to pack them into their own namespace and
	5	such. moreover, the other 2.8 code needs similar rewriting/reworking too...
	6	- internally split out +o/+v "ranks" into a series of permissions. this could allow for configure-defined
	7	special access levels, halfops, etc. (would need to match globally, somehow. extra SVINFO param?)
	8	- somehow hide channel operators like ircnet can do?
	9	- SASL opering?
7fd77cb0	10	- link failover?
a6ac2e91	11
a6ac2e91	12	--
abe616bb	13	$Id: IDEAS 3552 2007-08-09 06:50:13Z nenolod $