SirvNET IRC Services

[key]

Not sure if anyone saw my announcement, under the Introduction section, about SirvNET IRC Services making a come back. I wasn't able to provide a features list at the time of that post, so I wanted to go ahead and offer one now.

If anyone is interested in learning more or has any comments/questions, please post them on the SirvNET forum at http://www.sirv.net/forum

Thanks,
-key

Features (provided by the coder):
Sirv3 has been completely re-written from scratch. Everything that was available in prior versions are available in Sirv3. The purpose of this thread is to inform what is the most notable changes since version 2.9.

* SQL real-time Database support

* All Sirv3 commands are permission configurable thru the oper conf file. The available permissions are: All users, Oper only, SOP+ only, SA+ only, SRA+ only, Root Master only.

* Ability to have multiple M:line nicks (root masters)

* Support for new user services stamping. In lamens, ircd remembers if you identified to your nick or not. If services restart, or are split and rejoin the network, you will not need to re-identify to your nick. Not only does this work for your active nick, but ALL nicks you are identified to!

* New high security for IRC Operator services. Opers must now supply an addiitonal password to OperServ to obtain extra privileges. When adding an oper to an oper access list, the oper will be given a temporary password. The oper will have 10 minutes to identify with the temporary pass and change their password. Otherwise, the new entry will expire.

* Oper nick tracing. In a nutshell, if I'm identified to oper services, and change my nick and decide to set an akill, services will display in the akill globops "current-nick (identified nick) has set an akill for etc etc.." It is always clear who is doing what actions.

* Addition of nick freeze system.

* MARK/HOLD/FORBID can now contain reasons, keeps track of who set them and the time they were set. (Freeze has the same functionality)

* Enhanced clone detection on the ip level. Much more efficient.

* Support for the new bahamut akill system.

* Support for 'JOIN 0'

* Suport for NOQUIT capab.

* Support for channel resynching.

* Now when supplying a password while using /NickServ GHOST/RECOVER/RELEASE identifies you to that nick.

* Addition of logon news system. - This is basically a network MOTD. It is not displayed in notices, but is shown as an actual motd after the local server's motd.

* Enhanced normal news system. Can now read history archived news articles. Opers can delete news articles via /MemoServ RESETNEWS.

* Addtion of /NickServ LISTEMAILS

* Addition of /NickServ GETEMAIL

* Addition of /NickServ AUTHINFO

* Enhanced channel access lists. Any list (ie: avoice/aop/sop/cf) may have a reason field attached to the entry (just like an akick reason)

* Addition of /ChanServ SET NOTIFY - Notify the channel and founder of chan access list manipulation.

* Addition of /ChanServ SET WHEN - View how long an access entry has been added for.

* Addition of /ChanServ OFFICIAL - set network official channels.

* Addition of /ChanServ SET TRIMBANS - have chanserv remove #x of the oldest bans from the channel so the active channel ban list doesn't become full. Useful for very large channels.

* Addition of channel successors.

* Addition of channel access list tracing. Under channel avoice/aop/sop/cf lists, services will show the proper nick of who added the entry under "Added By: ". Prior versions would record the "added by" nick as whatever the issuer was using at the time. Now services will trace to the nick with the highest channel authority the issuer has.

* Addition of /MemoServ SENT - views memos you have recently sent others, and see if they have been read or not.

* Addition of /MemoServ SET RECEIPT - receive a confirmation memo when someone reads the memo you sent them.

* Addition of /MemoServ DEL OLD - delete all read messages.

* Addition of /MemoServ UNDEL ALL

* Addition of "High Nick Security" feature. This is a new feature we feel makes nick exploitation nearly impossible. When enabled, during nick authorization, the user will pick a personal question from a list, and give an answer which will be kept on file. When the user wants to change their password or drop the registration, they will be required to authoize thru email. If the user wishes to change their email, they must give the answer to their personal quesrion - an answer only they would know. This makes stealing nicks nearly impossible, unless it is someone who knows the user on a very personal level. Examples of available personal questions are such as your mother's maiden name, name of the street of your first home, the name of your first employer, the name of your first love, etc etc.

* Addition of 20+ new configuration options to make Sirv3 even more configurable than in the past.

There are many other minor additions and enhancements, however I have to end the list somewhere. This gives you a taste of the features Sirv3 will have to offer.

Sirv3 still has all the functionality of previous versions, such the ability to have channel auto-ops and co-founders, being able to have memos sent via email, and to send channel memos, being able to send your password to your registered email address, access adjustable topic locks for channels, and much much more.