Desiderius Price

41288

41286

41282

41280

Interesting timing on FFN too, but I don’t pay close enough attention to my hitcounts over there to notice. However, on AO3, I do, and haven’t seen any rollbacks on those. (I’m presuming that, like AFF, hitcounts are stored in the same database as the stories.) That’s another frustration with the archive being in read-only, I have no way to know if any of my stories have been read over the past three months…

41274

41272

🧨 (we need a mushroom-cloud emoji...) My way is different because… well, I have a tendency to turn problems into software projects as well. That’s why I write my stories as text files, annotating with a simple format what’s what (ie styles, version). When I want to post, I run the software, telling it what which version I want (clean vs explicit for my potter story), which archive I’m posting to (FFN, AO3, or AFF), and it’ll generate HTML files suitable for posting. Being a programming geek, I use a “makefile” to remember the command line options to be lazy/consistent. Bit more complex than most, but I do like the results.

41270

41266

I’d like to get more proactive, but I don’t have diplomatic immunity.

41264

41262

41260

41258

41256

41254

41252

Too late, I’ve already lost my mind 🤣

Had this issue when I decided to go and rework my potter story. First task, collecting them all, then I started purging the obvious duplicates. But hey, at least I didn’t lose much. (The *first* draft was, unfortunately, mostly lost—shame because that was the smuttiest too.)

Hang ‘em by their entrails!

Second @WillowDarkling to not rely on AFF or any other archive to retain your stories w/o incident. Keep in mind most archives, even google drive/dropbox/onedrive retain the right to *DELETE* your postings/files in their terms of service. OTOH, I’ll make copies of copies and I’m stuck wondering “which one of these is current?”

My guess is those reviews are lost to the ether, as the database is in read-only mode. IF my suggestion’s easy/fast to implement, it’s to put a spanner into the works, so to speak, do basically disable the review.php script so the user gets a 403/404 error instead of being led into thinking their hard crafted review actually made it to the author. (Of course, that’ll change this tech support topic to “why is reviewing busted”?) If it helps, @GeorgeGlass I’ll lie and claim that it was a beautiful and glorious review…. or that it was a flame and this empty review is better

41250