software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002344.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Version 5's features
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Version%205%27s%20features&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002343.html">
  11    <LINK REL="Next"  HREF="002345.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Version 5's features</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Version%205%27s%20features&In-Reply-To="
  17        TITLE="[IRCServices] Version 5's features">achurch at achurch.org
  18        </A><BR>
  19     <I>Thu Sep 27 16:42:01 PDT 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002343.html">[IRCServices] Question about 4.5.27
  22 </A></li>
  23         <LI>Next message: <A HREF="002345.html">[IRCServices] Help!  Notice -- Link [unknown@ip.address] dropped, no N: line
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2344">[ date ]</a>
  27               <a href="thread.html#2344">[ thread ]</a>
  28               <a href="subject.html#2344">[ subject ]</a>
  29               <a href="author.html#2344">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>ok, so we have all been sitting around awaiting the arrivial of Services
  35 </I>&gt;<i>Version 5, but exactly what new features will it have? we have heard you
  36 </I>&gt;<i>concider loads of new features, but which have you decided?
  37 </I>&gt;<i>I bet i'm not the only one asking this question Andrew, and i know u do a
  38 </I>&gt;<i>good job.. but...?
  39 </I>
  40      Well, to be honest I'd hoped to get a beta version ready in the near
  41 future and surprise everyone with all the new stuff, but as usual things
  42 aren't moving as quickly as I'd hoped, so for the time being, here's the
  43 tentative (as in everything I've done so far) What's New section for 5.0.
  44 Note that this isn't complete by any means; there's still plenty left in
  45 the TODO file, and I'm deciding whether to add them or not on an item by
  46 item basis, so the list below will probably grow, but this should be good
  47 for starters.  Note: PLEASE do not spam me with &quot;please add feature X&quot;
  48 where X has already been requested before (check the TODO file).  Doing so
  49 won't make it any more likely that I'll add it, and I may even decide not
  50 to add it just to spite you.
  51
  52      If this doesn't seem like a very long list, well, it's not (yet).
  53 That's mainly because module support has required restructuring and/or
  54 rewriting a large part of the Services code, which already stands at over
  55 30,000 lines of code--not even including language files--and that takes a
  56 lot of time, particularly trying to figure out the best way to restructure
  57 it (and I'm not even convinced I've done that yet, but if not, I guess
  58 there's always version 6.0).  As always, patience, please.
  59
  60   --Andrew Church
  61     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
  62     <A HREF="http://achurch.org/">http://achurch.org/</A>
  63
  64 ------------
  65 Version 5.0:
  66 ------------
  67 The single biggest addition to this version of Services is module support.
  68 This allows the various functions of Services to be added to and modified
  69 without having to touch the main source code itself.  Modules also provide
  70 much more flexibility in configuring Services; IRC server support and
  71 database file format can be selected by simply loading the appropriate
  72 module, and you can even choose which of the pseudoclients (NickServ,
  73 ChanServ, etc.) you want available.  See the example configuration files
  74 in the &quot;data&quot; subdirectory and the &quot;README.modules&quot; file for more
  75 information.
  76
  77 Services is now capable of sending mail.  Currently, this functionality is
  78 used by the new &quot;authorization&quot; feature of NickServ (in the
  79 &quot;nickserv/mail-auth&quot; module), which sends a message to a user upon nick
  80 registration or E-mail address change and requires the user to &quot;authorize&quot;
  81 their nickname with a random numeric code included in the message before it
  82 is recognized as a valid registered nick by Services.  In the future,
  83 forwarding of memos to an E-mail address is also planned to be added.
  84
  85 Also, nickname links have been redesigned for simplicity and robustness.
  86 In the new linking system, nicks are organized into &quot;groups&quot; which share
  87 settings the way linked nicks did in previous versions.  The LINK command
  88 has changed as well: instead of creating a link from the current (unlinked
  89 but registered) nick to a registered master nick, the link is made from the
  90 current registered nick to a new (unregistered) nick, to simplify
  91 registration of multiple links at once and to offer slightly better
  92 protection against &quot;rogue links&quot; created by guessing nick passwords (though
  93 as always, the best defense is to use good passwords).  The old behavior of
  94 the LINK command is still available through the &quot;nickserv/oldlink&quot; module.
  95
  96 Please see README-5.0 for important information if you are upgrading from
  97 version 4.x or earlier.
  98
  99 Other changes:
 100   + Services now records the last time an autokill was triggered.
 101   * The configuration file has been changed to accommodate modules;
 102         services.conf now contains only options related to core Services
 103         functionality, while module-related options (including NickServ,
 104         ChanServ, etc. settings) are in a new file called &quot;modules.conf&quot;.
 105         Many options have been removed or changed; see the example
 106         configuration files for details.
 107   * Channel autokicks specified by nickname will now work for that nick
 108         only, not for any nicks linked to it.
 109   * Newly-registered nicks will now always use the default language set in
 110         config.h, even if that language is changed after registration.
 111   * The deprecated CheckClones functionality has been removed in favor of
 112         session limiting.
 113   * The configuration script &quot;configure&quot; now asks fewer questions, and can
 114         be completely automated if the &quot;-prefix&quot; option is used.
 115   * &quot;configure&quot; now understands GNU-style long options, e.g.: --prefix=/usr
 116
 117 </PRE>
 118
 119 <!--endarticle-->
 120     <HR>
 121     <P><UL>
 122         <!--threads-->
 123         <LI>Previous message: <A HREF="002343.html">[IRCServices] Question about 4.5.27
 124 </A></li>
 125         <LI>Next message: <A HREF="002345.html">[IRCServices] Help!  Notice -- Link [unknown@ip.address] dropped, no N: line
 126 </A></li>
 127          <LI> <B>Messages sorted by:</B>
 128               <a href="date.html#2344">[ date ]</a>
 129               <a href="thread.html#2344">[ thread ]</a>
 130               <a href="subject.html#2344">[ subject ]</a>
 131               <a href="author.html#2344">[ author ]</a>
 132          </LI>
 133        </UL>
 134
 135 </body></html>