]> jfr.im git - irc/freenode/web-7.0.git/blame - content/news/2019-06-17-ircd-update.md
CertFP: use client.pem on hexchat
[irc/freenode/web-7.0.git] / content / news / 2019-06-17-ircd-update.md
CommitLineData
cdda4db0
EK
1---
2author: edk
3date: 2019-06-17 10:15:00+00:00
4slug: seven-118
5title: ircd-seven 1.1.8
6category: freenode
7category: announcements
8---
9
10Hi all,
11
12We're preparing to release version 1.1.8 of ircd-seven and deploy it to the
13production network over the coming weeks.
14
15This 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
25We're also introducing support for several IRCv3 features that may improve the
26experience 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
35There's one more change that is not related to this release, but deserves
36mention: nearly two years ago, we developed an improvement to the `+z` channel
37mode, which sends messages that would have been blocked by `+q` or `+m` to
38channel 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
45to make it easier for operators to distinguish between messages everyone can see
46and messages they can see due to `+z`.
47
48This borrows the syntax from an existing feature, [STATUSMSG][statusmsg], but
9b14299f
EK
49is easy to tell apart from it, because only ops and voiced users can send to
50`@channel` normally.
cdda4db0
EK
51
52We gated this behind a feature switch, and we've been waiting, largely
53passively, for client support to increase. It appears that everyone who wants to
54act 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
57channel that uses `+z`, please make sure your client handles it correctly.
58You can send test messages by using `/msg @#channel test` using a second opped
59connection for any channel where you have ops—your client should associate
60this message with `#channel`, and preferably distinguish it from normal
61messages in some way.
62
63Thanks for using freenode, and I look forward to collaborating with many of
64you 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