sage

Moderation is best left to client and server implementations, as long as we're not painting people in to a corner in the spec somehow IMO.

I was interested logging all computed routes on service startup, in a cheap way, so did a small investigation. You can traverse the tree of `Route`s, picking out leaves by...

An immediate concern I see here is ordering. Perhaps there would need to be some non-normative rules about the order in which to apply formatting and how they might overlap?

Thanks for the feedback! Front loading the formatting facilitates additions much better. Taking the examples of double underline and double strikethrough, if that were added as an inline formatting code,...

More thoughts: I agree about a registry, and yes I don't think the types I've listed aren't the limit of what could be added. I do think we'd need to...

The trouble is that I think there are fundamental problems with formatting strings inline to begin with, and I'd definitely be hesitant to extend them in any way right now,...

I also don't agree about the "crufty" comment - is this not the point of advertising CAPs? Assuming the server translated it, if a client supports the "formatting" tag, then...

Another thought: ending up with old clients (read: mIRC) having no formatting capability sounds totally reasonable. I don't think we should expect both to be supported indefinitely, and there would...

I agree about writing a spec, and between here and IRC I think I have enough considerations. I'll get on it in the near future so people can critique a...

Hey Abe - thanks for the kind words about the library 🙂 All the code in that file is automatically generated from the libvips API, and that function is marked...