the wide angle makes it look a lot further away from the rocket than they really were - The camera is about 440m away from the rocket.
The damage shown in the video appears to be entirely caused by debris while the article was suggesting possible property damage ("shattered glass and damaged foundations ... from a miscalculated sonic blast") to towns 8500m away - 20 times further
Having never actually seen the statue of liberty my sense when seeing these comparisons is that it's much smaller in real life than the version in my imagination - no matter how many times I see the comparisons, the statue remains much bigger in my head
Our API is just appsync (graphql) + lambdas + dynamoDB so, theoretically, we shouldn't have been affected. But about 1 in 3 requests was just hanging and timing out.
As others have said, they are not being forthright about the severity of the issue, as is standard.
Yes, all of the headsets do some form of reprojection if frames are not generated fast enough, or to account for the latency between generation and display.
If you turn your head fast you'll see black at the edges where it's not caught up
Sure but in small GA planes you're not likely to be travelling so far that the magnetic declination is significantly different so just keep it in mind each time you reset the DI. Or if you are travelling long distance you could make a note of it along your planned route, or your GPS app could let you know.
My point was that this shouldn't require any instrument upgrades to the GA fleet
The direction indicator is gyro based rather than magnetic so for most GA it would probably be enough to just learn the offset for the area you are flying and add that when you set/check the DI.
"In Port Isabel, a city about six miles northwest where at least one window shattered, residents were alarmed. " from [0] posted to HN [1]
I stand corrected - the warning article was pretty accurate
[0] https://www.nytimes.com/2023/04/21/us/spacex-rocket-dust-tex...
[1] https://news.ycombinator.com/item?id=35651757