Open RyanSquared opened 5 years ago
I think it makes sense for there to be some record of this, and a series of recommendations for IRC software (particularly client) devs. Definitely +1 on the point about having both the protocol recommendations, as well as more general ones.
While it may not strictly fall under the charter, I think it's related closely enough to fall under consideration. If all else fails, I'd be more than happy to have such work represented somewhere on ircdocs otherwise.
For now I've created this repo where these sorta docs can be built, and we'll decide where to put 'em later :)
Something that I brought up probably forever ago was the idea that clients should provide a consistent user experience. However, that isn't typically up for the protocol to decide, so I thought some kind of non-normative section with guidelines on how to improve user experience could be helpful. Things such as "happy eyeballs" (checking both IPv4 and IPv6 connectivity), checking port 6697 for TLS automatically, and other things that might not directly be on the protocol level - such as #16 (considerations for loading images).
Ninja-edit: Sorry, pressed enter instead of tab, editing comment now