They're also not saying it couldn't have happened, are they? They're waiting for investigators to gather all the facts before making any statements, just like they should.
Meanwhile, we here on the internet are just speculating based on the limited information available (basically just the video footage). Based on the current information we have, my opinion is that pilot error is the most likely cause.
You're free to disagree about the likelihood of different scenarios, but right now we have no evidence that makes the theory of the pilots accidentally retracting the flaps instead of the gear impossible or "absurd." It's really counterproductive to start ruling out scenarios without concrete proof.
I don't get what you mean by "and no one figured that out yet." As you said yourself, no one knows what happened yet. Pretty much all we have at this point are the videos, and all we can confirm from them is a rough flight path of the plane and that the landing gear remained down after what appeared to be a normal takeoff. I haven't seen any footage that clearly shows the state of the flaps with any certainty, but please correct me if I've missed something.
In my mind, that leaves us with three possible scenarios:
Pilot error (retracting the flaps instead of the landing gear)
Dual engine failure at the critical moment (there's no evidence of this in the videos, but also nothing ruling it out)
Something else (we don't know what we don't know)
From the two scenarios (pilot error, engine failure) that fit the flight path from the videos, the option one seems more plausible to me. But that’s just my armchair opinion, it doesn't mean anything. All we can really do is wait for the investigation and the preliminary report.
There are minimum airspeeds the aircraft must reach before the flaps can be safely retracted. I don't know the exact numbers, but assuming a standard flaps 5 takeoff for B787, retraction to flaps 1 would occur around 1000 ft by earliest, that's typically 20 to 30 seconds after the takeoff.
Are the 787's controls arranged in such a way that you could accidentally retract the flaps instead of the landing gear?
Not in a sense that someone could just grab the wrong lever in the dark for example. The levers are in different parts of the cockpit and also shaped very differently. But we humans can do all kinds of weird mistakes that are hard to explain. Almost everyone has experienced this sometimes. Think something like searching for you phone while it's in your hand. Afterwards it's very hard to explain why would anyone do such a silly mistake but it still happened. This would be similar.
One theory circulating online is that the pilots may have accidentally retracted the flaps instead of the landing gear. Apparently that would result in kind of a flight path seen on the published videos.
While this cannot be confirmed or ruled out with the information we have, in my opinion the available videos seem to kinda support this theory. Initially the aircraft appears to take off and climb normally, but for some reason the gear is not being retracted when usually it would be retracted right after the takeoff.
Naturally the gear could be forgotten or left intentionally down if there were a dual engine failure right after takeoff, for example, but as the videos show no evidence of this, I'm more inclined to believe in simple pilot error.
As someone living in a green country, could someone explain how things work in practice in the yellow or orange countries? I understand that in places like Russia or China, journalists can end up in prison, or worse, if the government doesn't like their writing. But how exactly is the press not free in countries like Canada or most European nations that are labeled yellow here?
And why is the US labeled orange? As far as I know, the media there is highly politically polarized, with most major news organizations openly supporting a particular agenda. That's certainly a serious issue and not how the press should operate, but even Trump's government isn't actively limiting the freedom of the press to report on issues like they see fit? Or am I mistaken? I'm genuinely asking.
That's reassuring to know. What I don't understand is why you have the /api/v3/post/like/list route. You say you don't want votes to be snooped on, but then you add an endpoint that makes it very easy for instance admins to do exactly that if they choose to? Also worth pointing out that the tool linked here wouldn't work in its current form if this route didn't exist.
Compare your actions to releasing a 0-day exploit for a security vulnerability instead of responsibly disclosing. It doesn't help, it just causes chaos until the people who do the actual work can figure out a solution.
This comparison is not fair at all. It's not like the devs are unaware of this. They could start by removing the API endpoint that lists a post's votes, but they haven't, which means they seem to think it's okay for the instance admins to snoop on votes if they so wish.
For me accessing that site in Firefox on Windows (even with uBO) does trigger the scam popup, but in any other browser I tried (Edge, Chrome, FF dev edition), it doesn't. Kinda interesting.
The popup does not manage to add anything to the clipboard. There are tons of JS errors in the console, so luckily the thing seems to be pretty broken right now.
I think Microsoft should add a warning before allowing pasting into the Run dialog for the first time. Similarly like they already have in Edge's console
Just testing does it still count if the comment contains other text after the command. It's not immediately clear from the instructions how that works.
They can include runnable JavaScript too, which can cause vulnerabilities in certain contexts. One example from work some years back: We had a web app where users could upload files, and certain users could view files uploaded by others. They had the option to download the file or, if it was a file type that the browser could display (like an image or a PDF), the site would display it directly on the page.
To prevent any XSS (scripts from user-provided files), we served all files with the CSP sandbox header, which prevents any scripts from running. However, at the time, that header broke some features of the video player on certain browsers (I think in Safari, at least), so we had to serve some file types without the header. Mistakenly, we also included image files in the exclusion, as everyone through image files couldn't contain scripts. But the MIME type for SVG files is image/svg+xml... It was very embarrassing to have such a simple XSS vuln flagged in a security audit.
Might be an unpopular opinion but after around two hours of gameplay I'm perfectly happy with the performance on my 3060Ti. On medium-high settings it can easily maintain 60fps on 1440p. That is with DLSS of course and ray tracing turned down to minimum.
Usually the gear is retracted almost immediately after takeoff, as it creates a huge amount of unnecessary drag if left out when not needed.