Thanks, this is exactly the content I come here for. Apt handle :P
I am very not comfortable with the situation, as a seller. I mailed out the stuff that was paid for before the outage...but I don't think I'm mailing anything else until I can disburse.
Yeah this sucks, I have a bunch of hobbyist orders stuck in limbo since last week -- customers have paid, but I can't pull the orders down even through the API.
I really like Tindie as a platform and have been using it since nearly the beginning...but I'd have lost the contract if I pulled this level of nonsense on a customer's production application.
Nothing wrong with Rails in 2026. We still use it for both internal and customer projects. I haven't yet encountered anything that made me feel like switching. I'm also not interested in changing frameworks just to have the New Hotness die in 2-5 years (our oldest currently maintained Rails project is over 10 years old, and some stuff I started working on when Rails 2 was new is still being maintained, just not by us)
I don't always play UT2K4, but when I do, it's usually with Ballistic Weapons mod + Sergeant Kelly's weapon packs. I agree that the UT2K4 weapons just don't quite do it like UT99.
Probably the most likely explanation, given so many things do inherit idiosyncrasies from C. I'd always assumed it was from Perl, given its heavy use in CGI back then -- like $_ being the default var. But that would probably also eventually inherit from C :P
We're redoing some of our application servers to bring everything under Ansible management, modernize, etc. Most of what we write gets deployed on OpenBSD. It's mostly been a painless process, except for that nagging "have to build it by hand with command line switches" issue with Nokogiri :P
Anyway, this writeup is basically everything you need to get your Sinatra application deploying under Puma, using Capistrano to manage the deploys, onto OpenBSD hosts. Reverse proxying and TLS
Same basic experience. The colo ISP soaks up most actual DDoS. We had a couple mid-sized ones when we were hosting irc.binrev.net from salty b& users. No real effect other than the colo did let us know it was happening and that it was "not a significant amount of DDoS by our standards."
Plus, learning PDP-11 ASM explains some of the idioms from C as they map directly onto the architecture! "Pointer to a pointer" is just a native addressing mode, for instance.
Indeed, we donate to several open source projects on which we depend, but we're also a small two-person operation. No medium/large company I've worked for ever donated monetarily to open source projects, though one did encourage us to fix bugs and submit patches/pull request, which is at least something!
Slackware's the same way, most donations come from individuals and very small companies.
Oh man that sucks! I wonder if we could pull Alpine into our colo, we recently upgraded to a full rack from 2U (it was cheaper than a quarter rack!) and have a ton of space. Plus all of our libvirt/KVM HVMs run Alpine.
There's an old LCM (Living Computer Museum, RIP) video where they run off a card deck of a risque ASCII art program on an IBM mainframe's line printer. It feigns a printer fault after printing the subject down to the shoulders, only to finish the print suddenly (line printers are fast!) when the operator has gone over to the printer. IIRC the original livestream was unprepared for that :P
Yup, that's why they were such useful devices! Even if you were ending up with inefficient storage (punching ASCII vs. binary, or expanded BASIC source vs. tokens), it was built-in.
I am very not comfortable with the situation, as a seller. I mailed out the stuff that was paid for before the outage...but I don't think I'm mailing anything else until I can disburse.