I was wondering how I ought to process the posts in the archive. I didn’t want to just do chronological, because that is boring and I can’t be bored during this. I need something to achieve, aside from long term storage of messages.
My first strategy will be to knock out some categories! There were a few core categories that went through multiple instances of the site, such as journal
, but I also have a few that have one or two posts, and processing those will be very satisfying.
And so, I begin with a category called… Webcraft.
At the end there the webcraft category had a single post, preserved at Open Guide to Amazon Web Services – interi.
OMG, I just realized they replace all the links in the page with Wayback Machine links! That makes shoving stuff away a lot easier, since I can just copy those links over! Wayback as Proxy for the win!
I wrote:
I primarily just use S3 for backups, but I’ve considered playing with EC2 instances, but most webcraft I do requires a consistent server life that isn’t compatible with stateless, 12-factor apps.
And of course, given my history of incredibly small edits to READMEs on GitHub, I submitted a patch to this guide removing a single word.
I am proud of my small edits, but since I posted this in 2016 I’ve completely boycotted Amazon services, and I minimize my interactions on GitHub, even before MS bought 'em.
I just like guides! And look at that guide: GitHub - open-guides/og-aws: 📙 Amazon Web Services — a practical guide
There are up to three guides per topic, with many topics. Where can I get that for actual open tech? I suspect it just needs to be compiled/curated.