Skip to content

Cap Clarifications#371

Merged
jwheare merged 4 commits into
ircv3:masterfrom
DanielOaks:master+cap-clarifications
Jan 30, 2020
Merged

Cap Clarifications#371
jwheare merged 4 commits into
ircv3:masterfrom
DanielOaks:master+cap-clarifications

Conversation

@DanielOaks
Copy link
Copy Markdown
Member

Clarifies some issues brought up with the CAP spec. Specifically, fixes #368 and #369, and adds some language along the lines of that suggested by jw in #359.

These clarifications should make CAP more future-proof and consistent.

I'm not quite happy with the "approaching the 510 byte limit" fragment of text in particular, but will continue editing it up. If anyone has recommendations, open to 'em!

@jwheare
Copy link
Copy Markdown
Member

jwheare commented Feb 22, 2019

The downgrade stuff should probably be a SHOULD/SHOULD NOT. There’s probably a bunch of implementations that get this “wrong” so I dunno if we can retroactively make this a hard requirement. Dunno, thoughts?

@jwheare jwheare added this to the Roadmap milestone Feb 26, 2019
@DanielOaks
Copy link
Copy Markdown
Member Author

Yeah that makes sense, I'll update that language

Comment thread core/capability-negotiation.md Outdated
Comment thread core/capability-negotiation.md Outdated
@jwheare
Copy link
Copy Markdown
Member

jwheare commented Jan 17, 2020

Is this good to go?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expected forward compat behaviour with CAP LS

4 participants