cy

Holy heck it just occurred to me. RETURNING is a terrible idea! You always want to query the database, then insert into it. Because if you insert with ON CONFLICT and RETURNING, it has to start a write transaction, and it has to touch the disk, and any caching would get invalidated. I just realized because my webpage thing was grinding the disk loading it, and it's because hundreds of write transaction journal files were being written, then committed, even if the record already existed. I'm going back to insert/select. #sql

I just love how valgrind doesn't work anymore. Anything that uses 'unrecognized instructions' and valgrind totally fails and dies, even if that's in a separate library. So any library that uses cryptographic hashes, or fast copying, anything that links to libnettle basically, you just sort of... can't use valgrind. The end. #FuckEverything

"I don't mind ads." is the same as saying "I don't mind scams."

So I'm writing a story, and it's super rough draft, with inconsistencies and janky scene transitions, paragraphs I'll have to flesh out into whole chapters. It's also approaching 129,000 words. I just have so much to write about here, it's hard to even get on with the plot. How long is this story gonna have to get before anything happens? I know nobody's ever going to read it, and my enjoyment is... not worth all this writing, but what else can I do? It's the only thing I'm good at, and the only coping mechanism I have for all this... loneliness.

Anyway I fixed my story website generator program, so it's up at https://fedicy.us.to/stories/exparesence/ on the unlikely chance anyone wants to take a look at it. I really could use some help, obviously.

i2pd web console
uptime 2 days
Tunnel creation success rate: 19%

Wait... seriously? No wait—seriously???

1. be me
2. bind 1733272193019267 using sqlite3_bind_int64 to an INTEGER column
3. sqlite3_step
sqlite error 778 disk I/O error

1. be me
2. bind 54992003 the exact same way
3. sqlite3_step
no error

18446744073709551615 is the biggest integer that will fit into 8 bytes! That's 10,642 times bigger than what I'm trying to insert. Even if I'm limited to signed 8 byte integers, 9223372036854775808 is the max, and 1733272193019267 is 5,000 times smaller than that. So there can't be an error here. It can't possibly fail to save the number 1733272193019267. How is it failing, then? Did they do something so idiotic as to use some of the high bits of those 8 bytes for vital database consistency state? There's no disk I/O error. This should never happen! #wtf

So your choice, chocolate that is high in lead and cadmium, or sex which has no lead or cadmium and you can't have it.

Huh, you know, maybe it's a really bad idea to update the version when you have backwards incompatible changes. No really. We do that, and everyone gets stuck using the old version, because they don't want to go through the massive pain of updating to the new one. We don't do that, and everyone calls us out for being massive assholes, so we only make incompatible changes when it's really really really important. Version changes are a poorly fitting bandaid, that lead to unpredictable behavior when different packages use different versions of the same dependency.

They don't save us from the pain of backwards incompatibility. They only defer that pain, making it worse and worse until it's practically impossible to update, and your software is doomed to obscurity and failure. Version changes are the equivalent of your benevolent government forgiving you of the obligation to pay rent due to certain emergency situations, then expecting you to pay it all retroactively in full as soon as they call off the emergency. (Yes that's what they're actually doing on this side of the pond.)

So I just update everything that depends on something, rather than updating the version of that something to keep all the other things still working. It keeps me honest, doesn't let huge changes build up, and makes updating simpler, since each individual change is very small and repetitive over many projects. Maybe I'm just a masochist, I dunno. If anyone else used my software, I'd start versioning it.