09:45
<zcorpan>
MikeSmith: https://checker.html5.org/ gives me 502. maybe set up statuscake or something?
09:46
<zcorpan>
or is it just me?
09:51
<zcorpan>
seems like "down for everyone?" services don't care about http response code
10:14
<annevk>
zcorpan: I also get a 502
12:17
<MikeSmith>
https://checker.html5.org/ is back now. restarted the server
12:18
<MikeSmith>
*restarted the validator process
12:18
<MikeSmith>
the reason it was down was the somebody from the systems team had restarted the machine without letting me know
12:18
<MikeSmith>
the validator process never goes down otherwise
12:19
<MikeSmith>
so I just need to add a script that will automatically restart it at boot time when the machine’s restarted
13:58
<hsivonen>
annevk: is https://github.com/whatwg/encoding/issues/115#issuecomment-447773485 on your radar? Should I send my feedback to the Unicode Consortium as drafted?
14:03
<annevk>
hsivonen: I asked somewhere what exactly the middle ground meant
14:04
<hsivonen>
annevk: the middle ground fixes the pressing issue without security benefit and leaves the door open toward later movement toward either extreme
14:04
<annevk>
hsivonen: I'm fine with either more principled generation of U+FFFD or removing the state member we currently have
14:04
<annevk>
hsivonen: okay, that's fine with me
14:05
<annevk>
hsivonen: I should have mentioned it in the issue after the lack of reply, but I forgot
14:05
<hsivonen>
annevk: i.e. it would remove U+FFFD generation only in the case where the first of the two transitions with nothing in between is a transition to the ASCII state
14:05
<hsivonen>
annevk: sorry about missing your question
14:07
<hsivonen>
researching the feasibility of end state 2 requires an archive of a lot of real-world Japanese email new and old, and my own mailbox isn't like that
18:33
<annevk>
So let { x } = y(); { x } = y(); throws, that's unfortunate
23:30
<Domenic>
I think you need `({ x }) = y();` or `({ x } = y());`