systems_glitch

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.

We all know that's what it is, I don't know why people aren't willing to just say it.

It has a domain, it has a logo, they were going for maximum impact because it's their business.

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)

End of an era. We used to get it on CD in school.

And it'll be open sourced once everything is done!

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.

Still the FPS I play the most! We organize LAN parties at some of the vintage computer events.

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

"I dunno...is magic" (engineering Calculus II GTA, Virginia Tech, 2006)

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.