Live data from Hacker News

United B772 at Denver on Feb 20th 2021, engine inlet separates from engine

avherald.com

481–483 of 483 posts

Re: United B772 at Denver on Feb 20th 2021, engine inlet separates from engine

#481

Earlier quoted context omitted.

LiveATC uses volunteers to record well-known frequencies at various airports. 120.15 may have been stood-up in an ad hoc fashion, so there was no radio configured to record it. * https://en.wikipedia.org/wiki/Airband

When control described it as "discrete" was it because they know that listeners wouldn't be prepared to monitor it? I find it odd that a public frequency would be described as discrete without some greater barrier to listening in.

You are thinking of "discreet":

* careful and circumspect in one's speech or actions, especially in order to avoid causing offense or to gain an advantage.

The word they were using was "discrete":

* individually separate and distinct.

120.15 is/was not used for anything else at Denver, so people could talk about the situation on the ground without effecting the operations elsewhere. Once the problem was 'contained', the rest of the airport could go back to operating 'normally' on the other runways.

Re: United B772 at Denver on Feb 20th 2021, engine inlet separates from engine

#482

Earlier quoted context omitted.

When control described it as "discrete" was it because they know that listeners wouldn't be prepared to monitor it? I find it odd that a public frequency would be described as discrete without some greater barrier to listening in.

You are thinking of "discreet": * careful and circumspect in one's speech or actions, especially in order to avoid causing offense or to gain an advantage. The word they were using was "discrete": * individually separate and distinct. 120.15 is/was not used for anything else at Denver, so people could talk about the situation on the ground without effecting the operations elsewhere. Once the problem was 'contained',…

I see. Thank you for clarifying that.

I'm still a bit surprised that the audio went uncaptured. It is interesting how much information that would be interesting to the public still spills into the ether.

Re: United B772 at Denver on Feb 20th 2021, engine inlet separates from engine

#483
post #401

Earlier quoted context omitted.

It would also be the correct technology for most sites - you don't need fancy Javascript for just the contents. Navigation, ads, etc., maybe, but not the contents itself. Most webpages could be perfectly useful with Javascript completely disabled. Sadly, many aren't.

Fancy JavaScript has nothing to do with serving static content. JavaScript itself is (or should be) static content anyway. If you're talking about using JS to load content on page load, for whatever reason, that async content can also be static. For example some sites use the URL fragment (hash parameter) to load content, but the server does not receive this: The fragment identifier functions differently to the rest…

> Fancy JavaScript has nothing to do with serving static content

Still, I visit websites all the time that don't work with Javascript disabled. They don't work at all, or the images don't load, or the formatting breaks down.

None of this is necessary. In principle, static content should work fine with Javascript disabled.

Post reply on HN