News for hackers. Stuff that matters.
Re:Letsencrypt, the Good, the Bad and the Ugly by jldugger on Thursday September 10, 2020 @02:35PM (#24435215)
> It logs failures. You should read your logs. > If you've built a system where silently failing is a problem, and you haven't configured any sort of "email me when anything isn't nominal" then you haven't finished configuring your server.

I mean, I built a system years ago then got a full time job. Shit breaking every 3 months is kinda bad for a hobbyist website / blog. Even when the monitoring is in place, there's ample room to decide 'you know, family emergency is more important than rearchitecting my TLS certs again.'

Re:Letsencrypt, the Good, the Bad and the Ugly by couchand on Thursday September 10, 2020 @05:29PM (#24436753)
Running your own server connected to the Internet is not a hobby and nobody should get the impression that it will be. Otherwise you're just making a donation to a DDOS swarm.
Re:Letsencrypt, the Good, the Bad and the Ugly by AlisdairO on Thursday September 10, 2020 @08:20PM (#24437994)
Do we have any real evidence that hobbyist servers are significant hitters when it comes to DDOSes? The idea that hobbyists shouldn't run a server is, IMO, misguided, and dangerous to the health of the internet.

A simple debian VM + nginx + $app_server with automatic updates turned on is not rocket science, and I struggle to see why one shouldn't run that as a hobbyist.

Re:Letsencrypt, the Good, the Bad and the Ugly by jldugger on Thursday September 10, 2020 @07:02PM (#24437488)
It hosts a static website with no meaningful network dependencies other than the control plane and letsencrypt. I'm relatively comfortable with the situation.