Book Bingo: O1 | Graphic Novel or Comic | The Vanishing of Lake Peigneur
Jun. 6th, 2026 09:52 amThe Vanishing of Lake Peigneur by Allan Wolf

Blurb:
Very entertaining read about an event that I had never heard of. Natural history plus human error/greed. A really quick read - I read it in about an hour or two. My library does not have a huge selection of graphic novels or comic books. One of the choices was Watership Down, but I decided I didn't need to be traumatized by visuals of that book. Although it's been so long since I read it last that I should do a re-read.
With that, I have another bingo. Three books to go, and I'm currently reading two out of the three.


Blurb:
Home to catfish and crawdads, shrimp and spoonbills, even a gator or two, Lake Peigneur—pronounced “your pain,” only backward—bustles also with human life. Each day, the bean-shaped freshwater lake and its shores hum with folks going about their work: a devoted gardener’s apprentice and his dogs, fishermen, oilmen drilling at Well P-20, and the fifty-one miners employed by the Diamond Crystal Salt Mines. For most, November 20, 1980, began as “just another day on the lake.” But as the lake itself reflects, humans had, over time, left behind a honeycomb of salt highways deep beneath its surface, and water and salt mix all too well. Bracing, suspenseful, and packed with dramatic illustrations and dense end matter, this story of a catastrophic accident—narrated with the homespun voice of a “tall” tale, but true nonetheless—will amaze science and history buffs alike.
Very entertaining read about an event that I had never heard of. Natural history plus human error/greed. A really quick read - I read it in about an hour or two. My library does not have a huge selection of graphic novels or comic books. One of the choices was Watership Down, but I decided I didn't need to be traumatized by visuals of that book. Although it's been so long since I read it last that I should do a re-read.
With that, I have another bingo. Three books to go, and I'm currently reading two out of the three.

(no subject)
Jun. 1st, 2026 10:56 pmQuick note that post-by-email and comment-by-email is (sometimes?) failing silently without actually posting right now! I'm pretty sure this is related to last night's shenanigans and will be fixed once Mark can finish the full fix for it, which he's working on, but if you've posted or replied by email in the last 24 hours, fish it out of your sent folder to check if it posted!
EDIT: This should be fixed as of around 7AM EDT! We *believe* everything that was stuck in the plumbing has been sent along to your journal or the comment thread it was meant for; it's definitely not where it was stuck anymore, at least.
EDIT: This should be fixed as of around 7AM EDT! We *believe* everything that was stuck in the plumbing has been sent along to your journal or the comment thread it was meant for; it's definitely not where it was stuck anymore, at least.
Question thread #151
Jun. 1st, 2026 07:44 pmIt's time for another question thread!
The rules:
- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
The rules:
- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
(no subject)
May. 31st, 2026 10:00 pmRobby has managed to put in a temporary fix for the site errors and things failing to refresh or not showing up where they should! The permanent fix is going to need Mark's experience, and unfortunately -- seriously, this literally never fails -- Mark has been on an international flight all day, because of course he has. (Never. Fails. He and I are not allowed to both take vacation at once.)
The site will work just fine with the temporary fix in place, things just might be a little slow here and there. We'll keep you updated.
(no subject)
May. 31st, 2026 08:59 pmWe're aware of site traffic issues and are working to fix them for the people who are having problems! (The tactics the damn bot traffic uses are endlessly shifting, and they're really good at looking like real traffic, sigh.)
Book Bingo: B3 | Figures without Facial Features on the Cover | All Systems Red
May. 31st, 2026 08:43 amAll Systems Red by Martha Wells

Blurb:
This is the May read for
bookclub_dw, so I'll save most of my comments for there. But I will say that this was a completely fun read and now I want to watch the Murderbot Diaries, and also the other books in the series.
With this I have 4 bingo squares to go; I'm simultaneously reading three books that will satisfy three of those squares. Trying to decide what to do with the 4th, which is a book older than I am. I thought about finally trying to get through all of Wuthering Heights, something I've tried multiple times over the course of my life and never managed. Maybe with the incentive of finishing that last square, I'll finish it this time.

Blurb:
A murderous android discovers itself in All Systems Red, a tense science fiction adventure by Martha Wells that interrogates the roots of consciousness through Artificial Intelligence.
“As a heartless killing machine, I was a complete failure.”
In a corporate-dominated spacefaring future, planetary missions must be approved and supplied by the Company. Exploratory teams are accompanied by Company-supplied security androids, for their own safety.
But in a society where contracts are awarded to the lowest bidder, safety isn’t a primary concern.
On a distant planet, a team of scientists are conducting surface tests, shadowed by their Company-supplied ‘droid—a self-aware SecUnit that has hacked its own governor module, and refers to itself (though never out loud) as “Murderbot.” Scornful of humans, all it really wants is to be left alone long enough to figure out who it is.
But when a neighboring mission goes dark, it's up to the scientists and their Murderbot to get to the truth.
This is the May read for
With this I have 4 bingo squares to go; I'm simultaneously reading three books that will satisfy three of those squares. Trying to decide what to do with the 4th, which is a book older than I am. I thought about finally trying to get through all of Wuthering Heights, something I've tried multiple times over the course of my life and never managed. Maybe with the incentive of finishing that last square, I'll finish it this time.
Testing needed in advance of code push!
May. 28th, 2026 04:10 pmIt's been a while since we've done a full code push rather than just hotfixes for bugs, so we are well overdue! Depending on availability, we're aiming to do one sometime soon; we'll let you know specifics once we've worked out good timing for everyone who needs to be available.
However! The reason it's been so long is we kept trying to get some of the stuff that's pending to "really finished" instead of just "mostly finished", and then we once again looked around and went "oh no, this is a really big code push with a lot of changes". Those make us nervous, because while we do a lot of testing ourselves, y'all are really creative in how you use the site and we inevitably find a bunch of edge cases when we let you loose on new code with your real-world data!
So, if folks have some spare time in the next few days, it would be a huge help if you could spend half an hour or so using the site the same way you normally do but with the "Site-Wide Canary" beta features flag turned on. Canary mode is a sort of "live testing" mode: it's your real data, but running the most up-to-date code.
Canary mode always does have a few glitches -- there may be missing text strings or errors about missing database properties, which is a limitation of how we run it. We don't need to know about those, but anything else weird that you run into, leave a comment with what you were trying to do and the error message you got.
I'll repeat that the "here be dragons" caution that's on the beta features page: some things may be broken, so don't use it for when you're doing something important. But a few more eyeballs on it before the push will help the push go more smoothly for everyone.
For folks who want to concentrate on what's changing, we haven't finished the second code tour of what's going to be in this push, but the ffirst one has a good chunk of what's going to be going live. (We'll get the second half done ASAP!)
However! The reason it's been so long is we kept trying to get some of the stuff that's pending to "really finished" instead of just "mostly finished", and then we once again looked around and went "oh no, this is a really big code push with a lot of changes". Those make us nervous, because while we do a lot of testing ourselves, y'all are really creative in how you use the site and we inevitably find a bunch of edge cases when we let you loose on new code with your real-world data!
So, if folks have some spare time in the next few days, it would be a huge help if you could spend half an hour or so using the site the same way you normally do but with the "Site-Wide Canary" beta features flag turned on. Canary mode is a sort of "live testing" mode: it's your real data, but running the most up-to-date code.
Canary mode always does have a few glitches -- there may be missing text strings or errors about missing database properties, which is a limitation of how we run it. We don't need to know about those, but anything else weird that you run into, leave a comment with what you were trying to do and the error message you got.
I'll repeat that the "here be dragons" caution that's on the beta features page: some things may be broken, so don't use it for when you're doing something important. But a few more eyeballs on it before the push will help the push go more smoothly for everyone.
For folks who want to concentrate on what's changing, we haven't finished the second code tour of what's going to be in this push, but the ffirst one has a good chunk of what's going to be going live. (We'll get the second half done ASAP!)