content/news/2019-06-17-ircd-update.md

   1 ---
   2 author: edk
   3 date: 2019-06-17 10:15:00+00:00
   4 slug: seven-118
   5 title: ircd-seven 1.1.8
   6 category: freenode
   7 category: announcements
   8 ---
   9
  10 Hi all,
  11
  12 We're preparing to release version 1.1.8 of ircd-seven and deploy it to the
  13 production network over the coming weeks.
  14
  15 This release incorporates a number of user-facing changes:
  16
  17  - [Monitor][monitor] is restored to a usable state, and will be re-enabled.
  18  - Spam filtering can be opted-out of. Setting mode `+u` on yourself (
  19    `/umode +u` or `/mode yournick +u`) will disable filtering for messages
  20    sent to you. Setting it on a channel will disable filtering for all
  21    messages sent to that channel.
  22  - `/motd` and `/stats` are no longer ratelimited unless directed at a
  23    specific server.
  24
  25 We're also introducing support for several IRCv3 features that may improve the
  26 experience on capable clients:
  27
  28  - [Away Notifications][away-notify] are supported.
  29  - [CHGHOST][chghost] is supported.
  30  - [Strict Transport Security][sts] and [STARTTLS][tls] are enabled. (We know
  31    STARTTLS is deprecated and a bit out of date, but we'd still like to get
  32    as many people as possible using TLS one way or another.)
  33  - [Userhosts in NAMES][userhost-in-names] is supported.
  34
  35 There's one more change that is not related to this release, but deserves
  36 mention: nearly two years ago, we developed an improvement to the `+z` channel
  37 mode, which sends messages that would have been blocked by `+q` or `+m` to
  38 channel operators instead. Our new version sends these messages to ops from the
  39 `@`-prefixed version of the channel:
  40
  41 ```
  42 :e!e@freenode/staff/spy.edk PRIVMSG @#test :I'm quieted
  43 ```
  44
  45 to make it easier for operators to distinguish between messages everyone can see
  46 and messages they can see due to `+z`.
  47
  48 This borrows the syntax from an existing feature, [STATUSMSG][statusmsg], but
  49 is easy to tell apart from it, because only ops and voiced users can send to
  50 `@channel` normally.
  51
  52 We gated this behind a feature switch, and we've been waiting, largely
  53 passively, for client support to increase. It appears that everyone who wants to
  54 act on warnings has done so, and we'd like to commit to a date to enable it.
  55
  56 **We'll be enabling this feature on the 31st of July 2019, UTC.** If you op a
  57 channel that uses `+z`, please make sure your client handles it correctly.
  58 You can send test messages by using `/msg @#channel test` using a second opped
  59 connection for any channel where you have ops—your client should associate
  60 this message with `#channel`, and preferably distinguish it from normal
  61 messages in some way.
  62
  63 Thanks for using freenode, and I look forward to collaborating with many of
  64 you via a slightly less-antiquated medium.
  65
  66 [monitor]: https://ircv3.net/specs/core/monitor-3.2
  67 [away-notify]: https://ircv3.net/specs/extensions/away-notify-3.1
  68 [chghost]: https://ircv3.net/specs/extensions/chghost-3.2
  69 [sts]: https://ircv3.net/specs/extensions/sts
  70 [tls]: https://ircv3.net/specs/extensions/tls-3.1
  71 [userhost-in-names]: https://ircv3.net/specs/extensions/userhost-in-names-3.2
  72 [statusmsg]: https://tools.ietf.org/html/draft-hardy-irc-isupport-00#section-4.18