X-Git-Url: https://arthur.barton.de/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=NEWS;h=143132e8743d4a517ff0f571374f1f65649ab1af;hb=refs%2Fheads%2Fbug249_MaxPenaltyTime;hp=b5c42bf3395c12a9dae7fcc0a93b6ce7b2edd602;hpb=3e447384168a619e79c163dab5bd5493acf33734;p=ngircd-alex.git

diff --git a/NEWS b/NEWS
index b5c42bf3..143132e8 100644
--- a/NEWS
+++ b/NEWS
@@ -2,16 +2,34 @@
                      ngIRCd - Next Generation IRC Server
                            http://ngircd.barton.de/
 
-               (c)2001-2016 Alexander Barton and Contributors.
+               (c)2001-2018 Alexander Barton and Contributors.
                ngIRCd is free software and published under the
                    terms of the GNU General Public License.
 
                                   -- NEWS --
 
-
-ngIRCd 24
-
-  ngIRCd 24~rc1
+ngIRCd 25
+
+  - Only send TOPIC updates to a channel when the topic actually changed:
+    This prevents the channel from becoming flooded by unecessary TOPIC update
+    messages, that can happen when IRC services try to enforce a certain topic
+    but which is already set (at least on the local server), for example.
+    Therefore still forward it to all servers, but don't inform local clients
+    (still update setter and timestamp information, though!).
+  - Update Xcode project for latest Xcode version (9.2). This includes adding
+    missing and deleting obsolete file references.
+  - Handle user mode "C" ("Only users that share a channel are allowed to send
+    messages") like user mode "b" ("block private messages and notices"): allow
+    messages from servers, services, and IRC Operators, too. Change proposed by
+    "wowaname" back in 2015 in #ngircd, thanks!
+  - Allow IRC Ops and remote servers to KILL service clients: such clients
+    behave like regular users, therefore IRC operators and servers should be
+    able to KILL them: for example to resolve nick collisions.
+    Closes #242.
+
+ngIRCd 24 (2017-01-20)
+
+  ngIRCd 24~rc1 (2017-01-07)
   - Log privilege violations and failed OPER request with log level "error"
     and send it to the "&SERVER" channel, too.
   - Immediately shut down connection when receiving an "ERROR" command,