From: "J.P." <jp@neverwas.me>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 51342@debbugs.gnu.org
Subject: bug#51342: 29.0.50; remove non-CAPs from rcirc capability list
Date: Mon, 25 Oct 2021 20:50:29 -0700 [thread overview]
Message-ID: <87y26ge96i.fsf@neverwas.me> (raw)
In-Reply-To: <87r1caseo5.fsf@neverwas.me> (J. P.'s message of "Sun, 24 Oct 2021 07:03:38 -0700")
"J.P." <jp@neverwas.me> writes:
> However, I *have* noticed at least one progressive IRCd sending
> standard replies not defined in any spec [1].
>
> [...]
>
> [1] https://github.com/ircv3/ircv3-specifications/pull/276
That link is bogus/unrelated (sorry). It's actually a
:irc.org FAIL NICK NICKNAME_RESERVED tester :Nickname is reserved ...
that I encountered, but it's not documented anywhere (that I could
find). It's sent by Ergo 2.6.1 whether or not you request any caps.
NICKNAME_RESERVED was ostensibly created to prevent confusion with the
traditional 433/ERR_NICKNAMEINUSE, which accompanies it in the same
burst.
Whether it's safe to expect such redundancy across the board when
nothing dependent has been negotiated is anyone's guess, but the
existence of the vendor cap inspircd.org/standard-replies [1] perhaps
tips things in favor of the yeas. This cap gives permission for a server
to send undeclared replies in standard-replies form, possibly in lieu of
traditional ones, like 433.
> I can only guess they assume clients not privy to the new syntax are
> resilient enough to take these in stride [2].
Yeah, "new syntax" is just confusing. What I meant was rather than
extending the IRC message format, a standard-replies declaration merely
specifies a concrete reply within the constraints of the broader
protocol, meaning
[@tags] [:src] cmd p0 p1 p2 ... pn-1 :pn
[@tags] [:src] <type> <req> <code> [<cxt0> ... <ctxn>] :<desc>
from the spec is just a way of getting us ready for specific interface
descriptions, like those for setname [2]. So when folks talk about
safely degrading in this context [3], they mean devolving to a catch-all
handler (usually NOTICE) for all unrecognized/unhandled replies. Thanks.
[1] https://docs.inspircd.org/3/modules/cap/
[2] https://ircv3.net/specs/extensions/setname#errors
[3] https://github.com/inspircd/inspircd/issues/1809
next prev parent reply other threads:[~2021-10-26 3:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 0:08 bug#51342: 29.0.50; remove non-CAPs from rcirc capability list J.P.
2021-10-23 1:59 ` J.P.
2021-10-24 10:05 ` Philip Kaludercic
2021-10-24 14:03 ` J.P.
2021-10-26 3:50 ` J.P. [this message]
2021-11-14 18:10 ` Philip Kaludercic
2021-11-14 23:07 ` J.P.
2021-11-17 20:22 ` Philip Kaludercic
2022-09-13 14:49 ` Lars Ingebrigtsen
2022-09-13 18:30 ` J.P.
[not found] ` <877d15yxun.fsf@neverwas.me>
2022-10-12 13:36 ` J.P.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y26ge96i.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=51342@debbugs.gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).