81–90 of 98 posts
For anybody interested, they missed: https://www.n2yo.com/?s=12443|10820 (Link further in thread.)
Edit: as of 2021-04-09T20:21:00Z EUSST thinks they missed. https://twitter.com/EU_SST/status/1380601898164744199
Earlier quoted context omitted.
Replace `twitter.com` with `nitter.eu`: https://nitter.eu/EU_SST/status/1380120766071635968
I was pretty excited when I found out about nitter. After some months I realized that every nitter mirror only stays up for a few weeks before it becomes so popular it's throttled most of the time (like nitter.net). Also, it's 17:41 UTC now... the events of this post should be occuring now. Or not occuring.
Mine isn't publicly accessible so never gets throttled.
For anybody interested, they missed: https://www.n2yo.com/?s=12443|10820 (Link further in thread.)
We don't know yet. Satellites (especially defunct) don't have active live tracking like ships. Satellite sites show them based on calculated trajectories. Edit: as of 2021-04-09T20:21:00Z EUSST thinks they missed. https://twitter.com/EU_SST/status/1380601898164744199
next anticipated contact with OPS 6182 at 20:00UTC https://platform.leolabs.space/catalog/L11618#next-planned-p...
So what's that, about 90 minutes from now assuming I've got the right info?
Earlier quoted context omitted.
We don't know yet. Satellites (especially defunct) don't have active live tracking like ships. Satellite sites show them based on calculated trajectories. Edit: as of 2021-04-09T20:21:00Z EUSST thinks they missed. https://twitter.com/EU_SST/status/1380601898164744199
leolabs' next anticipated contact with SL-8 R/B 12443 is at 21:06UTC https://platform.leolabs.space/catalog/L5136#next-planned-pa... next anticipated contact with OPS 6182 at 20:00UTC https://platform.leolabs.space/catalog/L11618#next-planned-p... So what's that, about 90 minutes from now assuming I've got the right info?
Here's the text without having to execute arbitrary code from twitter. --- Update: according to #EUSST's latest estimates using data from its surveillance radars, the close approach between #space objects SL-8 R/B & OPS 6182 expected by tomorrow will have a miss distance under 10m and a Scaled Probability of Collision over 20%! +updates to follow soon See the below plot for the conjunction plane at Time of Close Appr…
Here's the text without having to execute arbitrary code from twitter. --- Update: according to #EUSST's latest estimates using data from its surveillance radars, the close approach between #space objects SL-8 R/B & OPS 6182 expected by tomorrow will have a miss distance under 10m and a Scaled Probability of Collision over 20%! +updates to follow soon See the below plot for the conjunction plane at Time of Close Appr…
Please omit flamebait from your comments here. You started a totally off-topic argument about Javascript which got upvoted to the top of the thread, gaining mass and choking out interesting discussion. Not cool. https://news.ycombinator.com/newsguidelines.html
[Er… commit = comment… TGIF, leaving it in for fun ;D]
> UPDATE: #EUSST’s network of sensors has only detected a single object or echo at passes over three radars after close approach. Most likely, the collision between SL-8 R/B and OPS 6182 did not take place. We will continue observing the objects to confirm this assessment.
Earlier quoted context omitted.
leolabs' next anticipated contact with SL-8 R/B 12443 is at 21:06UTC https://platform.leolabs.space/catalog/L5136#next-planned-pa... next anticipated contact with OPS 6182 at 20:00UTC https://platform.leolabs.space/catalog/L11618#next-planned-p... So what's that, about 90 minutes from now assuming I've got the right info?
Are these satellites visible by telescope, can someone in e.g. Ankara try to spot SL-8 R/B 12443 as it as it flies over there in a few seconds?
Tangent: I went to find UTC, and they've redesigned time.gov, it looks great on my desktop. https://time.gov/
Earlier quoted context omitted.
Please omit flamebait from your comments here. You started a totally off-topic argument about Javascript which got upvoted to the top of the thread, gaining mass and choking out interesting discussion. Not cool. https://news.ycombinator.com/newsguidelines.html
While I agree with hiding the parent commit for the flamebait, that also hid my on-topic layman's explanation of what's happening :( [Er… commit = comment… TGIF, leaving it in for fun ;D]