« first day (1093 days earlier)      last day (1401 days later) » 

1:01 AM
I'm getting an Error: The server's response could not be decoded
 
1:24 AM
TIO is down for me as well
 
Looks like the HTTPS certs are out of date... paging certbot... certbot to the white courtesy phone please...
 
1:46 AM
@Dennis TIO certificate has expired
 
2:07 AM
Should be working again. Sorry about that...
 
Remember to set a reminder for next time
 
I'm positive I renewed them some 20 days ago. Must have missed a step...
 
2:36 AM
@Dennis Thanks for the quick response (and while I'm at it, everything else you do with TIO)! I use certbot.eff.org these days, which has made https a pleasure rather than a burden.
 
@ChasBrown I use Certbot too. My issue is that I use wildcard certificates, which use DNS challenges to validate. My DNS is managed by DigitalOcean, so automating renewal would require a DO API key, which grants access to everything on DO. I'm a bit paranoid and not really comfortable with that...
 
Ah! Yah, I can totally understand - I'm also mostly on DO as well.
 
 
17 hours later…
8:15 PM
@Dennis Can you pull Deorst please?
 
 
3 hours later…
10:46 PM
@Dennis I have V ready to be updated, but I just now realized a potential problem. The new way of calling V is v -f input [OPTIONS] source [ARGS]. Can TIO distinguish between "options" and "args"?
The only options V recognizes are -vhxn and -f file, everything other than that is an "arg"
Or is there a different way that it should be call that would be more idiomatic?
 

« first day (1093 days earlier)      last day (1401 days later) »