ldenneau

3 ms·

1.
by ldenneau 7y ago
This issue astronomers have with Starlink is not with increased light pollution per se, where the effect is negligible, but with the fact that when there are 10,000 of these in the sky at one time, it will be much more difficult to point a
2.
by ldenneau 8y ago
This was answered non-facetiously after discovery: https://arxiv.org/abs/1902.04935
3.
by ldenneau 9y ago
The ATLAS near-Earth asteroid survey (full disclosure: I am on this project) detected the Roadster last night as part of routine operations: https://twitter.com/fallingstarIfA/status/962013418143195141
4.
by ldenneau 9y ago
If there is one within 1 AU of the Sun at any given time, then there are ~10^16 of them within a sphere out to the nearest star. I'll leave it to you to decide whether that's teeming or not.
5.
by ldenneau 9y ago
Co-author here. We obtained spectroscopic measurements of 'Oumuamua, and its surface closely matches D-type asteroids and comet nuclei, which are dark, reddish and organic-rich.
6.
by ldenneau 9y ago
Does not handle leap seconds: https://api.epoch.sh/2016-12-31T23:59:60Z Edge case, but 2016-12-31T23:59:60Z is a valid UTC time.
7.
by ldenneau 9y ago
Comet Shoemaker-Levy 9 in 1994. The comet had been captured decades earlier after entering Jupiter's Roche limit and was actually in orbit around Jupiter. Collisions in the main asteroid belt have been observed, but only after impact.
8.
by ldenneau 12y ago
I do get the point, but simply preserving the local time isn't the right answer. I'd argue that when you change your local timezone offset, then your future schedule is indeterminate and all events have to be reverified. What if t
9.
by ldenneau 12y ago
This article is way overthinking it. It's better to simply store the UTC time of the event, and nothing else. Local time zone conversions can be done when displaying/editing. Presumably at the time you are reading your calendar, y