The trajectory depicted has them hitting the moon; it should instead show them passing 2+ lunar diameters behind the moon.

And a 27-byte key for AES-256 is also slightly undersized. Far from catastrophic but, like brown M&M's in the green room of a Van Halen concert venue, it's a strong signal that something is off...

age < 13

age >= 13 && age < 16

age >= 16 && age < 18

age >= 18

A non-maliciously compliant implementation would need to retain a date of birth or equivalent until the user was over 18.

A maliciously compliant API could just wait 18 years after account creation before yielding an answer. (remember folks: "real time" does not mean "fast").

One of the oddities about the way the law is phrased is that it requires the age band information about the user be provided to "the developer" rather than to the application.

Biometrics are not required.

The concept appears to be that a parent or guardian could enter the birth date before turning the device over to a child.

Malicious compliance would be providing this age bracket API:

boolean is_user_over_18() { sleep (18 * 365.25 * 86400); return true; }

This is a real-time interface (as required by the law) that takes 18 years to complete. (Remember: "Real-time" does not mean "fast").

https://www.wsj.com/articles/taylor-lautner-taylor-dome-wife...

https://en.wikipedia.org/wiki/Power_Macintosh_7100

Sagan sued. Engineers at Apple changed the name to BHA: "Butt-Head Astronomer".

He sued again. The final codename was "LAW: Lawyers are Wimps".

But the Internet's memory means that something being public at time t1 means it will also be public at all times after t1.

If you want to change the altitude of your orbit at a certain place, the most efficient place for that is generally when you're on the other side of the planet from that place.

In low earth orbit it takes about 90 minutes to go around the planet, so a small nudge 45 minutes before the potential intercept is going to be vastly more efficient than a big shove when the collision is 5 minutes away.

Starlink uses high efficiency ion thrusters so it has to do small nudges anyway..

So I would not be surprised if most of that hour is spent waiting for the right time to fire the thrusters.

Always send "pragma foreign_keys=on" first thing after opening the db.

Some of the types sloppiness can be worked around by declaring tables to be STRICT. You can also add CHECK constraints that a column value is consistent with the underlying representation of the type -- for instance, if you're storing ip addresses in a column of type BLOB, you can add a CHECK that the blob is either 4 or 16 bytes.

  0K..................100K
  Dead          Still Dead

A snapshot is a low-cost read-only view of a filesystem at a point in time; a clone is a writeable filesystem with initial contents shared from a snapshot.

It's an amazing safety net, though it requires understanding and sysadmin discipline to use well -- starting with keeping user/application data separated from the filesystems managed as part of the BE. ZFS makes this easy (a pool can contain many separate filesystems) but you have to do it.

One gotcha is that if you run an update that creates and activates a new BE but don't reboot right away, changes made to the BE-managed part of the running system after the snapshot creation will be "lost" (stranded in the old BE) when you reboot to the new BE.