@authen @amerika @dj @ins0mniak @lanodan @phnt @polarisera @ryan :bigbosssalute:

The crawler now behaves correctly even in stupid new network topology and ships shit to Revolver and fetches it on demand so I just gotta get the crawlers deployed and then shuffle the DNS around (that's the easy part) and make a couple of other tweaks (which I have to make anyway for other stuff) and then the LetsEncrypt stuff (and probably crank out a script so that the crawlers start updating themselves once I've got it all HTTPS'd so I don't have to remember which machines are doing what, link the crawler's source from the About page and then clean up the frontend code so that I can just link all of the source and then if I go offline for a while someone else can just roll it out). I also wanna do something about the snac2-snacN.samedomain thing that one kid's doin' (trivially, like, "All of the new instances this one is listing in its peers point to the same IP" but that feels less than clean so I've been trying to come up with something that feels better); the big problem is still the domain squatting pages but that's throughput, not user-facing. (It would be fun to have the interactive-ish stuff available over the web, like the apotheosis stuff; the job scheduler spits out a lot of pretty fun information but only I get to see it at present.) I might roll out one or two crawlers in a couple of hours anyway so that it when I turn the site back on it's not *completely* outdated information.

I don't know, I haven't sliced up the day yet. It seems like an hour or two to do the stuff that gets it back up and running, maybe an hour or two more to get the well-defined tasks knocked out, getting fedilist rezzed seems like as good a use of my time as anything else.
1.09--shinra_corporation.mp3