Jos Ahrens

>The affected sripts include "build" and "test" which make local development nearly impossible. >Also what would be the alternative? Just not supporting development on Windows anymore doesn't sound like a...

@ might be a channel prefix (in some twisted world?), in what scenario would opening a query with an user be beneficial? Without prefix for queries you're going to break...

The point is that ircds are still free to use and implement whichever part is in the specification, but that IRCv3 gets a lot of requests from private networks for...

Convieniently, someone just left the following comment showcasing why I think this is useful, and I think this metadata/note would have prevented the hassle: https://github.com/ircv3/ircv3-specifications/pull/289#issuecomment-272413251

Just to document for the future; A numeric (465) already seems to exist, but this idea is more to indicate to the client a "Please don't try to reconnect" without...

The ERROR already does this, but ERRORs are very generic and nobody should really be parsing ERROR messages from the sixty different ircds we have laying around.

Things that could be abstracted away are: - Vendor namespace definitions - Escaping values

My initial thought is that one way to achieve this would be to split each definition up in four files: - An importable errata section to be used in every...

Hi, I'm personally completely open to this switch (I'd love to get rid of date-fns myself), currently our engineering focus does not mark this as priority however, but we'd be...

@martijnrusschen I think we can make this happen, is this something you're okay with supporting as well? Was there a reason we need data-fns or purely convienience? From my POV,...