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
Wow! You can see the chunk nail the corner of the NASASpaceflight stream van (on the left of the frame) at 0:15.
Unlucky hit! But I guess lucky it missed the camera gear.
The team was chuckling on the stream about how they opened the vehicle windows for airflow to the electronics gear inside... but SpaceX helped them open it even more.
> It's really the most divisive issue I've ever seen in my life.
I've been yelled at and called very awful things by people I know in real life. Biggest clue that this is 90% hysteria and 10% real.... What ever happened to keep calm and carry on.
Or there are financial incentives, which may justify paid interventions online to create the appearance of divisiveness. There are PR agencies which specialize in "grassroots PR".
Users can email hn@ycombinator.com to ask for human review of flagged articles. If the article still remains flagged, only then is the flag sanctioned by HN moderators. Otherwise, flags could be anywhere on the spectrum between organic users, troll botnets and paid interventions.
Is there an API to HN data which could report granular data on article flags, e.g. timestamps or user IDs doing the flagging?
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
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.
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
I really wanted this back then when it felt like I was missing out. Then twitter released their version and I got a taste and decided I wasn't into it after all.
> Does this make it "freshly-re-copyrighted until 2004 + 70 years?", or is the year that counts for copyright the original publishing date?
Any changes (spelling, typos, the typesetting) in the new publication would be under a new copyright term. In practice, if you make your copy from the earlier out of copyright edition then you're fine. (Assuming you are correct that the earlier edition is truly out of copyright)
This is incorrect. In the US new copyright is only awarded for acts of authorship. Minor spelling or punctuation changes, or typo fixes, are not authorship. See https://en.wikipedia.org/wiki/Sweat_of_the_brow
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