| 02:15 | <Domenic> | Someone tried to do our April Fools for us, it seems, in lieu of us doing one. https://couchblog.de/blog/2019/04/01/neue-html-tags-und-attribute-fuer-das-urheberrecht/ |
| 02:16 | <Domenic> | euillegal="" attribute, good stuff |
| 09:11 | <annevk> | Domenic: do you know what's up with request streams? |
| 09:50 | <tiborg> | given a plain text that may contain url links and email adresses, what are safe characters for spliting the text to potential candidates which would be validated futher? first thing that comes to mind are whitespaces |
| 12:33 | <Domenic> | annevk: haven't seen much movement; yhirano or ricea would be the people to ask. |
| 12:34 | <annevk> | I wonder what's holding it back |
| 13:31 | <Ms2ger> | annevk / Domenic: either of you have time to approve a trivial change in https://github.com/heycam/webidl/pull/693 ? |
| 13:35 | <Domenic> | done |
| 13:36 | <Ms2ger> | Thanks |
| 13:37 | <Ms2ger> | And if you have more time, there's the modules PR :) |
| 13:37 | <Domenic> | Yeah, hopefully today or tomorrow |
| 13:37 | <Domenic> | I spent Friday and Monday catching up on reviews and emails after TC39, now I should actually make progress on my work things... but then back to reviews. |
| 19:38 | <Domenic> | #lazyweb the canonical way to encode a potentially unicode string to ascii, in a bidirectional manner, would be, what? Percent encoding? UTF-8 encode -> base64? |
| 19:51 | <jyasskin> | Domenic: I don't think there's a canonical way. https://tools.ietf.org/html/rfc3492 is a third option. |
| 19:52 | <Domenic> | Hmm punycode would probably be more readable indeed |
| 19:57 | <Domenic> | OK well I went with UTF-8 -> base 64 because that maintained back-compat with my previous base64 strategy. Now live URL viewer properly supports Unicode URLs. https://jsdom.github.io/whatwg-url/#url=amF2YXNjcmlwdDphbGVydCgxKS8v77+/&base=YWJvdXQ6Ymxhbms= |