2017-10-16 UTC
# 
sknebel so HWC Berlin didn't end up in the newsletter because someone put "open end" as the end time and (surprise) the parsing script didn't manage to make a useful timestamp out of that. I'll fix the newsletter script to handle that more gracefully, but any suggestions how to publish something like that? "open end" as text, and have let'S say midnight in a machine-only mf2 attribute? /cc aaronpk