Yes, the angle above the horizon is usually what is most useful because it is used to find something small but visible. In the case of my ascii moon, the angle below the horizon, is there to explain why something is not visible. The Moon is large enough that people can easily find it on their own if it is not obstructed by the Earth itself.
Consider the Moon as viewed from NYC at time of comment [0], it is hiding below the horizon. If you were to look at my website and then at the sky you might become upset that I am reporting the shape of the moon, but obviously it can't be seen. Hence why the website reports the angle below the horizon roughly half the time it isn't visible.
Adding Azimuth and Elevation when the Moon is above the horizon would be for completionism only and not the real enterprise use-cases served by ANSI compliant renderings of the Moon.
I fully expect in such a regime, people would be complaining about how the leap second insertion caused their recurring meeting to shift from 9am to 8:59:59
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.
https://www.wsj.com/articles/taylor-lautner-taylor-dome-wife...
reply