If you have been enjoying the Digest for many years, and you’d like to buy me a nice sandwich, you most certainly can.
It’s been a quiet week and I’ve finally caught up on my backlog of things to post, so I’ll take this moment to say: thank you, for reading. Especially, thank you to the Patreon supporters who have thrown in a few dollars; it’s actually paid forward to others I support on Patreon and bought me a nice coffee drink.
If you enjoy the Digest and want to get me to my goal of a free sandwich, I have a Patreon account. Merry Christmas/happy holidays! Normal article posting resumes tomorrow, of course.
I have stuff to post, but moving DragonFly to 5.4, php to 7.2, postgres to 9.5, WordPress to 5.0, etc. Regular Digest transmissions should resume tomorrow.
I realized I’ve been working on the Digest for almost a decade and a half now, and I have readers outside of just DragonFly. I’ve always been grateful for the attention people pay to my aggressive trips down the rabbit hole.
I’m also always hungry. Hungry for more information, sure, but also for a sandwich. If you want to send me a link, that’s great, but until now you couldn’t really send me a sandwich. I’ve set up a Patreon page, so now you can.
It’s bothered me for a while that I’m autoposting Digest headlines to Twitter, which is useful for Twitter users but still supporting a walled garden. Mastodon is a better implementation of a similar idea, and bsd.network nicely groups all sorts of BSD people in one place. Right now I’m just posting the Digest headlines here into the Mastodon account there, but there’s added value from the additional BSD-specific conversation around it.
I haven’t (yet) found a way to translate the local timeline on bsd.network into a RSS feed, which would be super-handy…
dragonflydigest.com is changing providers today, so the site may go missing for a while as DNS updates, and as I scramble my config.
I had a spurious carriage return in the RSS feed output that some I think xerxes based RSS readers like spaRSS didn’t like. It’s fixed now – can someone else running spaRSS confirm in a comment? Or just confirm that you aren’t getting RSS errors now if you were for the last few days.
I’ve gradually been leaning towards two opinions:
1: Having the Digest load as fast as possible is a benefit for everyone, and
2: I want to get off the PHP/Wordpress vulnerability merry-go-round.
Does anyone have specific experience with static site generators? Ideally there’s something out there as polished/unfiddly as WordPress, but I don’t know what. The Digest started using the Movable Type product, and I’m tempted to return.
Update: People have been recommending Hugo, Pelican, and Jekyll. It looks like comments would end up going into Disqus, which is an external not-under-my-control application. There are other plugins for comments, but none of them as straightforward. What are people’s thoughts on using an outside service?
The insulation on the external lines leading here are apparently delicious, if you’re a squirrel.
I’m moved over to new hardware for the Digest. Tell me if you see issues, please.
shiningsilence.com/dragonflydigest.com will be going down for a brief period in the next 24 hours, for a hardware upgrade.
The machine this site runs on just had a fan die, so somewhere in the next 24 hours, I’m going to be installing a new fan, and a new hard drive while I’m at it. Expect a few hours of downtime as I rebuild both hardware and software.
Quiet for you, the reader, at least. My schedule is irregular because of work over the next few days – including the weekend – so regular posting may not resume until next week. Sorry!
For some reason, OpenSSL-using command line clients – but not any browsers – are choking on the RSS feed for this site when fetched via https. So, the site no longer defaults to https. It’s still available if you want to use it, and I’ll work on fixing the setup.
The way to see it is:
openssl s_client -connect www.dragonflydigest.com:443
You will notice an error in the output like this:
672060044:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_lib.c:184:
There’s lots of references to errors like this out there – many different, some for bugs long fixed. I daresay it’s a configuration screwup I haven’t figured out yet; I’ve noticed that adding -tls1 or -no_tls1 or -ssl2 or -ssl3 to the above command makes the problem go away.
Since the switch to https here, the RSS feed has been having trouble, as several people reported. I haven’t had time to look into it much so far. Though I suppose it’s only likely that you are reading this if you are unaffected by it.
I need to get a legit certificate for this domain. I’ve never done serious https cert shopping – who has, and what’s your opinion of the vendors? (“Not Network Solutions” I can already guess).