Obligatory Manley analysis.

It’d be easier to train clamp scientists to static fire than to train rocket scientists to clamp.

wouldn’t changing it just end up performative

Exactly. Sidereal time does get rid of time zones and leap years, but it’s still referenced to a single physical object and relies on a arbitrary choice of start point. So it doesn’t create some perfect cosmic time standard.

The international date line doesn’t help since that’s just 180° offset from Greenwich itself.

The point of standards is that they can be followed by everyone. The AD/BC epoch is fine. The Greenwich meridian is fine. UTC is fine. Changing them would cause so much disruption that it cannot be worth it.

Daylight savings can go die in a ditch though.

doesn’t change

Citation needed.

Do you use leap seconds to stay in sync with earth’s rotation? When would they be applied? How would spacefarers be notified of these updates?

Also, what meridian do you choose for this ‘universal’ time? Is it still Greenwich? Because that’s peak colonial baggage.

I thought one thruster has been permanently disabled now? Not that that’s a major problem, but it does eat into their redundancy somewhat.

How will they filter it out? If they just don’t mirror anything with ‘forbidden’ terms, we can poison repos to prevent them being mirrored. If they try to tamper with the repo histories then they’ll end up breaking a load of stuff that relies on consistent git hashes.

Starship is about 80% the width of Falcon Heavy - but all the way around and practically all the way up!

RIP B1087.

That is fun, I didn’t know that was a thing. I imagine that roll-overs are more common than submersion in water, but even so, that doesn’t sound like a great trade-off. Even in a crash, being able to quickly jump out the window is good — especially if the vehicle is on fire.

The front ones don’t seem to be hidden, but yeah - if they’re not meant to be used regularly, people won’t remember them in an emergency. I guess the rear ones are hidden because they probably bypass child-locks.

I don’t know how child-locks work on mechanical door latches. If the vehicle locks when in motion and the child-locks are on I don’t think there are emergency releases on most vehicles? The only ways out would be to get into the front cabin, break the windows, or find the internal boot release.

There’s a panel that can be popped out to open the hood with a 12V power supply: https://www.tesla.com/ownersmanual/modely/en_us/GUID-34181E3A-B4A7-4658-906A-38C6647B5664.html

beneath the seat

For the toddler to use?

There is a mechanical door release if you’re trapped inside. To get in from outside obviously needs the vehicle to unlock, so it has to be jump started.

Even if there was some kind of back-up mechanical lock I can’t see anyone carrying around a key only for this specific eventuality. A glass breaker key-ring might be the best option — along with understanding how to use these emergency features in case you need them. A glass breaker might also save you in a fire or ending up underwater.

Wherefore art thou Gnomeo?

My my, here come the fuzz.

One would hope there’s never a need to restrict any content here for legal reasons, though.

I can see that, but surely there wouldn’t be much difference matching the first 4bits (0x2XXX, 0xfXXX) vs the first 16 (0x0001)?
0:: is presumably all for loopback-type stuff, but I don’t see a reason not to use 1:: through 1fff:: and they would be much easier to type/remember/validate for public DNS servers which are needed before name resolution is available.

Why start at 0x2001 though? Why not 0x0001? Then we could have addresses like 1:1:1::1 or 1:2:3::4.

2606:4700:4700::1111

Hmm, maybe Google is easier:
2001:4860:4860::8888

Quad9 is 2620:fe::fe or 2620:fe::9

I don’t understand why they can’t get better addresses than that. Like surely 1::1 would be valid?

Edit: So IANA only control addresses 2001:: and up and there are quite a few IETF reservations within that. I don’t know why they picked such a high number to start at. Everything else seems IETF reserved with a little space allocated for special purposes (link-local, multicast, etc.).

Kenya believe it‽

I’m using ATmega micros, on my Lily58. If I remember correctly, the default QMK behaviour was to use the USB to select which half was the master and what side it was on. That would work on RP2040 boards just as well so that may be what the provided firmware does.

I would suggest you just flash them both then see what they do. If they are swapped, try connecting the USB to the other half. If that works then you don’t have a problem. There’s no risk of damaging them and the RP2040 is pretty easy to reflash.

I wasn’t satisfied with that method and set QMK to store the sides in eeprom so I could use the same firmware but connect to either one. I’m not sure if the 2040 has a separate non-volatile memory so you’ll likely need a different method. I think a GPIO can be grounded to set the side but the Lily58 doesn’t do this. You could add a bodge wire if you want this but you have to customise QMK to use that method.

Still easy to miss. Would be better in red.