software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2004/003010.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Feature request: No logonnews after netsplit
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20request%3A%20No%20logonnews%20after%20netsplit&In-Reply-To=12dc01c41f06%24b88eaf00%24024ea8c0%40wolfkiste">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="003009.html">
  11    <LINK REL="Next"  HREF="003011.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Feature request: No logonnews after netsplit</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20request%3A%20No%20logonnews%20after%20netsplit&In-Reply-To=12dc01c41f06%24b88eaf00%24024ea8c0%40wolfkiste"
  17        TITLE="[IRCServices Coding] Feature request: No logonnews after netsplit">achurch at achurch.org
  18        </A><BR>
  19     <I>Sun Apr 11 00:15:15 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003009.html">[IRCServices Coding] Feature request: No logonnews after netsplit
  22 </A></li>
  23         <LI>Next message: <A HREF="003011.html">[IRCServices Coding] ChanServ suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3010">[ date ]</a>
  27               <a href="thread.html#3010">[ thread ]</a>
  28               <a href="subject.html#3010">[ subject ]</a>
  29               <a href="author.html#3010">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>     This issue has been raised before.  Unfortunately, it's not as simple
  35 as you suggest; for example, new users may have logged on while the server
  36 was not connected to Services, or it could be a brand-new installation of
  37 Services or the introduction of a new server (in which case you'd _want_
  38 the news sent out).  I am considering options for 5.1 or later, but this is
  39 too complex an issue to be addressed in 5.0.
  40
  41   --Andrew Church
  42     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  43     <A HREF="http://achurch.org/">http://achurch.org/</A>
  44
  45 &gt;<i>Hi all,
  46 </I>&gt;<i>
  47 </I>&gt;<i>i think it would be very useful if services could detect when a netmerge (of
  48 </I>&gt;<i>any server on its own net, at any time) is completed. This would bring the
  49 </I>&gt;<i>following advantages/features:
  50 </I>&gt;<i>
  51 </I>&gt;<i>1.) If you know that a server is linking at the moment and merging its data
  52 </I>&gt;<i>with the net by sending its users, channels, etc., you would also be able to
  53 </I>&gt;<i>determine whether a new user (from services' point of view) is just being
  54 </I>&gt;<i>introduced as part of the netmerge and was still on his server or logged
  55 </I>&gt;<i>onto his server shortly ago.
  56 </I>&gt;<i>Currently services send their logonnews to every &quot;new&quot; user they see on the
  57 </I>&gt;<i>net, even if this user has already received them during his irc session.
  58 </I>&gt;<i>
  59 </I>&gt;<i>2.) Services would be able to wait until a linking server has completed its
  60 </I>&gt;<i>netmerge and then set chanmodes like autoop/voice - but only if necessary.
  61 </I>&gt;<i>
  62 </I>&gt;<i>All in all it would reduce the services traffic and the annoyance level for
  63 </I>&gt;<i>the users in case of a netsplit or svs restart.
  64 </I>&gt;<i>
  65 </I>&gt;<i>I think there is an easy way to determine the end of an netmerge without
  66 </I>&gt;<i>help of any special ircd features:
  67 </I>&gt;<i>You just need to send a PING to any new server on the net. If we can assume
  68 </I>&gt;<i>that every ircd software first sends all its own nicks/chans/.. and then
  69 </I>&gt;<i>starts to reply to commands, you should get the PONG after receiving all
  70 </I>&gt;<i>netmerge specific data. Before this PONG is being received, logonnews
  71 </I>&gt;<i>shouldn't be sent to users on this server and they also shouldn't get autoop
  72 </I>&gt;<i>or autovoice. When we get the PONG, we need to recheck the
  73 </I>&gt;<i>autoop/autovoice-status of every user on the server that just linked.
  74 </I>&gt;<i>
  75 </I>&gt;<i>Wolle
  76 </I>&gt;<i>
  77 </I>&gt;<i>
  78 </I>&gt;<i>------------------------------------------------------------------
  79 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
  80 </I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
  81 </I>
  82
  83 </PRE>
  84
  85 <!--endarticle-->
  86     <HR>
  87     <P><UL>
  88         <!--threads-->
  89         <LI>Previous message: <A HREF="003009.html">[IRCServices Coding] Feature request: No logonnews after netsplit
  90 </A></li>
  91         <LI>Next message: <A HREF="003011.html">[IRCServices Coding] ChanServ suggestion
  92 </A></li>
  93          <LI> <B>Messages sorted by:</B>
  94               <a href="date.html#3010">[ date ]</a>
  95               <a href="thread.html#3010">[ thread ]</a>
  96               <a href="subject.html#3010">[ subject ]</a>
  97               <a href="author.html#3010">[ author ]</a>
  98          </LI>
  99        </UL>
 100
 101 </body></html>