From b1dfa5435f8853abaeba80d5f136437cc8c82036 Mon Sep 17 00:00:00 2001 From: Les De Ridder Date: Sun, 19 Mar 2017 22:46:05 +0100 Subject: [PATCH] Update readme --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 80ba373..0cc9ae6 100644 --- a/README.md +++ b/README.md @@ -6,9 +6,10 @@ salty-ircd is an [Internet Relay Chat](https://en.wikipedia.org/wiki/Internet_Re The main goals of salty-ircd are strict RFC compliance and security. ### RFC compliance -salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2811](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned). +salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2811](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned). +Newer RFCs take precedence over older RFCs. -Any features breaking RFC compliance will be made available through compile-time options. +Any additional features breaking RFC compliance will be made available through compile-time options. ### Security * salty-ircd will require TLS for all connections. An exception could be made to allow hosting a Tor hidden service.