You can have custody information be open for query without exposing all of the circumstances, and without releasing mugshots to private sites that will extort people to have them taken down.
You can do something very simple like having a system that just lists if a person is - at that moment - in government custody. After release, there need not be an open record since the need to show if that person is currently in custody is over.
As an aside, the past few months have proven that the US government very much does not respect that reasoning. There are countless stories of people being taken and driven around for hours and questioned with no public paper trail at all.
There is an entire world where arrests are not a matter of the public record and where people don't get disappeared by the government. And then there is US where it is a matter of public record and (waves hand at the things happening).
They call em Jump Outs. Historically the so called constitution has been worth less than craft paper. From FDRs executive order 9066 to today, you have no rights.
Orbital mechanics can be somewhat counterintuitive.
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.
Maybe I misinterpreted the statement - I thought it was talking about the time from detection to sending the command to the satellite, not the time until the satellite actually took action.
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.
There you go. Not to doubt what you say, but we definitely had the love seat yet we also had a tank of vaguely flourescing green liquid. Maybe we had some intermediate state, the cray-1 cpu form but the cray-2 upgraded coolant.
It wouldn't surprise me if we had the bastard love-child of leftovers from Boeing.
The GP also mentions X11 Terminals. My wiki-fu shows the X Windowing System came about on or around 1983, while Cray-1 was 1970s vintage. I assume that was an upgrade at some later point.
X Window Release 3 (X11R3) was introduced on Cray into UNICOS (a UNIX variant of Cray OS, COS) in late 1989 using ported 64-bit Xlib. But it was not widely used within small Cray community.
But MIT cooked up X11 "PROTOCOL" of Xlib in late 1985 to 1986 on Univac and Unix in C with many other X libraries written in Common Lisp.
X10R3 mostly stabilized the Xlib around a few platforms and CPU architecture (DDX) in a"long" preparation for X11R1 in September 1987.
It was fat finger memory. it was X10R3 or something similar, which I had previously used in UCL on Ultrix machines in the 80s. I don't think it was R5, I don't think much got upgraded in that space but .. it was a long time ago.
This was a SECOND HAND cray. It was a tax contra made in the 90s when Boeing sold a lot of stuff to the Australian Defence forces, and to avoid a massive tax burden donated science trash to the uni.
Long Island is even more of a long hallway than the peninsula. The LIRR manages to have multiple trunks and something like 10 different branch lines.
One thing that made it possible is LI is much flatter terrain than the peninsula.
The main trunk lines are in Long Island are about 3-4 miles apart. Northwest of around Cupertino or so, the mountains edge too close to the bay shoreline for you to make a second trunk line viable. Your best bet would be plonking a line around about 85, but the right-of-way doesn't exist to actually hook that line up to the existing line in any useful way.
And outside of that, basically everything you'd consider plonking another path already exists with some service: BART runs up the east shore of the bay, as it does west of San Bruno Mountain. You have two mountain crossings covered by BART and one by ACE. The main missing things are curving BART back into San Jose and reactivating the Dumbarton Bridge.
I've wondered about running BART from Fremont to East Palo Alto and Redwood City via Dumbarton. Not sure what the ridership would be though. I looked at the Dumbarton bridge traffic and it's the least of the three bridges and pales in comparison to the bay bridge.
Still if you built that the gap between Millbrae and Redwood city is 12 miles.
Your last sentence was going to be my reply. The peninsula is really linear along 101 / the historic el Camino. There really isn’t anything to connect to.
LIRR still had to do plenty of tunneling to build the East Side Access station though. Still, it opened in 2023! NYC is also still building the second avenue subway --- slowly, haltingly, and at near-ruinous expense, but it's actually a real expansion to the network is actually happening. By US standards, that's a miracle.
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.
There were significant power shutdowns in California in 2019 (affecting millions of customers in aggregate); the reason for the shutdowns was different from 2001 (preemptive shutdowns when the risk of downed power lines starting wildfires was thought to be high) but the impact on customers is the same: no power for an extended period.
But the Internet's memory means that something being public at time t1 means it will also be public at all times after t1.
reply