Correct. Not sure about a sql archive, but the kiwix ZIM archive of the top 1M English articles including (downsized but not minimized) images is 43GiB: https://download.kiwix.org/zim/wikipedia/

And the entire English wikipedia with no images is, interestingly, also 43GiB.

I don't know; we also grow corn for ethanol and add it to gas.

It goes a lot further than plan mode though, in fact I would say the key difference of mikado refactors from waterfall refactors is that you don’t do all the planning up front with mikado. If anything you try to do as little planning as possible.

I’ve been using a form of the Mikado Method based on a specific ordering of git commits (by message prefix) along with some pre commit hook scripts, governed by a document: https://docs.eblu.me/how-to/agent-change-process

I have this configured to feed in to an agent for large changes. It’s been working pretty well, still not perfect though… the tricky part is that it is very tempting (and maybe even sometimes correct) to not fully reset between mikado “iterations”, but then you wind up with a messy state transfer. The advantage so far has been that it’s easy to make progress while ditching a session context “poisoned” by some failure.

I recently orchestrated this, although in my case I've chosen to use 1password's cloud based store as my primary secret store, so I'm accepting some exposure right off the bat that you might not be comfortable with.

I've documented the recovery process here: https://docs.eblu.me/how-to/operations/restore-1password-bac...

Basically, I have a borg backup job which runs every day, in a 3-2-1 replication strategy with the backups being sent both to a locally encrypted NAS (backups themselves have an additional layer of encryption via borg) as well as off-site with BorgBase. Those backups scoop up an export of 1password that I have a reminder to kick off manually about once a month via this script: https://github.com/eblume/blumeops/blob/main/mise-tasks/op-b...

The password that decrypts the key (along with the password that decrypts the backup) is stored on a piece of paper in a fireproof safe in my house. I've got a reminder to practice the entire DR process every six months, although I've only done it once so far as this is all pretty new.

It was fun to build!

Just a heads up, Fireproof Safes are not failure proof, you should have that key securely stored somewhere else as well.

Thanks, it's also available via my 1password cloud account, so it'd have to be a joint fire at my home and the 1password data center (and my phone, for that matter). Pretty bad day I feel.

Unrelated note: this was the first time I've linked to my static generated docs for this project and it was really fun watching the grafana dash of my fly.io nginx proxy pick up all the scraping traffic. Thanks for warming my cache :) I work with this tech all the time at my day job but this is the first time I've hosted something from my home, it's genuinely made my afternoon to see it light up.

I've sworn off Sony products - well, as much as one can do so - for the past, what, 20 years? - because of that. It's kind of funny to me because I don't usually have a high opinion of "wallet activism", but one day when I was 20 I found out I had a rootkit installed on my computer by Sony and now they are _dead to me_.

I still hate that they got away with deleting my linux partition on my PS3.

That was a completely useless instance of linux and I think it was only ever done to get around some kind of tax or tarrif on game systems vs generic computers, but those are both beside the point.

When I gave them the money, I no longer controlled the money. It remained and still remains fully functional for them after that and I did not get to reach into their bank accounts and remove part of it or even just control what they can and can't spend it on. They got 100% of everything expected out of an exchange of ownership. And they also got to retain partial control of the PS3! What a great gig!

I just deployed my own forgejo instance on my private tailnet this week. I've had a ton of fun mirroring up to or down from github, I set up a devpi proxy for my python packages, and just generally "cleaned house" in my personal infrastructure. Delightful! Forgejo was an absolute breeze to install. I chose homebrew for installation and service management because I'm running on macos and I'm trying to avoid containers for key services (for no particular reason other than "it's my homelab and I'm gonna do what I want"). A few short lines in an app.ini and `brew services start forgejo` and it all just unfolded from there. Great job, forgejo team!

A quick search for "Audi recall" shows several recalls this year. Here's the first official link I found: https://www.audiusa.com/en/compliance/takata/

Not stupid at all. Definitely yes. Don't have the numbers on hand but it's orders of magnitude more CO2-equivalent released per kg-mile, especially when you factor in the fact that they are using methane.

Of course the reality is that this tech won't ever see adoption used that widely, but where is the break-even point?

Rocket launches emit less CO2 than a trans-pacific airline flight.

> CO2-equivalent

I think what they were trying to get at is GHG emissions in general which there are more of than just CO2.

Full flow staged combustion engines like Starships do not have significant un-burnt methane. They run slightly fuel-rich, but that results in extra CO emissions rather than CH4 due to the temperatures involve -- methane cracks at 1200C, Starship engine temperature is 3000C.

Starship's operations in Boca Chica do emit methane during ground operations. The mitigation for that is to use a pipeline rather than trucks for delivery.

Solid rocket motors emit all sorts of nasty stuff, like aluminum particles.

That's my thought as well. I predict we'll be seeing SDK's for generating github workflows by mid-2026. Maybe pulumi will get an extension for it. (I'm well aware that codegen yaml has been a thing for a long time, but I'm thinking about something targeting github workflows _specifically_.)

TBH it's getting a bit exhausting watching us go through this hamster wheel again and again and again.