like god fucking damn what did keepassxc do that made all these little fuckers pledge allegiance to it? what about this mediocre blog post is convincing? did y’all miss the context that this post is accompanied by a bunch of posts on other official keepassxc accounts where they give incorrect and potentially dangerous information in defense of their use of LLMs?
gonna have to start cleaning up some of the posts from the more long-winded assholes with opinions that aren’t more complex than “well I trust them to not let the technology known for creating security vulnerabilities run wild on their codebase, because they made the exact same promises every other project makes when they go all-in on slop”
oh no what happened to that thin veneer of reasonable centrism when you were defending a password manager of all fucking things incorporating slop code? could it be you just fucking love slop?
I saw that! fortunately once iocaine is configured it seems to just work, but it's also very much software that kicks and screams the entire way there. in my case the problem wasn't even nginx-related, I just typoed the config section for the request handler and it silently defaulted to the mode where it returns garbage for every incoming request.
nope, you’ve been getting caught in the fallout from us not having this yet. the scrapers have been so intense they’ve been crashing the instance repeatedly.
it’s only a double down if it’s a kfc sandwich where the bread is replaced by chicken. i see no chicken sandwich here, alleged posters, unlike in fuck ai where it’s chicken sandwiches all day
froztbyte’s criticism crossed the line by a bit for a couple of admins who weighed in, and they’ve been warned to ease up. reporting a post like that isn’t bannable; we’ve got more context for a report like that than we do for some rando doing a drive-by report for a tone rule that doesn’t exist, for example.
blue misused the report system in a way that wasn’t accidental or incidental, and we felt the best course of action was a cooling off period. given that they’re welcome back in less than 4 days, I’d prefer to leave it at that.
lightly used thinkpads are the classic choice for this — IT departments buy high spec ones then dump them for cheap a few years later in surplus sales or on eBay, and there are usually repair manuals and spare parts readily available. usually you can type the specific model and generation into a search and get a wiki page or at least a couple blog posts reporting how well they’re supported under linux, and Lenovo seems to intentionally do very well on compatibility since Linux compatibility is a nice checkbox for an enterprise laptop to have. just be careful you don’t get bamboozled into buying any of Lenovo’s consumer laptops, since they tend to be a fair bit cheaper and don’t have the same compatibility guarantees, repairability, or ample spare parts availability.
you know, I shouldn't be surprised by the extremely toxic lead developer to prompt enthusiast pipeline, but... slopcode in gzDoom of all things? fucking why?
uggggh yep sorry, I meant to deploy some changes that would mitigate this a couple nights ago but had a bunch of things crop up. I’ll do my best to work it in tonight!
some specifics for the changes to expect:
iocaine finally
some better nginx settings to kill likely scraper connections faster
thanks! I tried to link it in the usual way, but I think a bug might have blanked the url box before I hit post.