It appears that #NASA were ready to announce #Ingenuity's mishap during #Flight72 by Jan 18, the same day the flight took place. Or, a draft of something related to that event *or an event during previous #Flight71* leaked to the internet and was scraped by the search engine before it was removed.
NOTE: I'm not a fan of conspiracy theories. This could have a much simpler explanation.
Here's a screenshot of the search result:
@stim3on
No full result, just the fragment shown. Try it here:
https://duckduckgo.com/?t=ffab&q=thanks+ingenuity&ia=web
I searched the Internet Archive and it has not stored that page. The page itself does not exist.
@65dBnoise There is something else we can try though. The number in the URL is an incremental counter.
https://mars.nasa.gov/resources/27899/
and
https://mars.nasa.gov/resources/27898/
both lead to a 404 page.
https://mars.nasa.gov/resources/27897/
and
https://mars.nasa.gov/resources/27896/
are a valid results dated January 25 from the same announcement
https://mars.nasa.gov/resources/27895/
is a MSL panorama from Sol 4076 (January 24)
so the incremental counter checks out to match a Jan 25 release.
@65dBnoise And while it would definitely be possible to fake an incremental counter, IMO in this context it doesn't make sense.
My guess is that duckduckgo just got confused haha.
@stim3on
Hm, that is logical.
Duckduckgo.com does have an "AI" engine, but I'm not sure if it's used for all searches.
Regional? That's interesting. Here is a better image of the result I'm getting:
@stim3on
Ha, ha! Does duckduckgo use ChatGPT? 🤣
Yes, date mixup is the "simpler explanation" I mentioned above, and there may be many others too, but the different text snippet you're getting now perplexes things.
@stim3on
Only a Quantum Intelligence can think of such conspiracies, unless ChatGPT has already reached ultimate hallucinatory enshitification 🤪
Seriously, I would very much like to know if duckduckgo uses some LLM behind the scenes, which would also explain why I see some shitty results lately, like 50 results of the same irrelevant page.
@65dBnoise I found something new. As you may or may not know, duckduckgo sources some of it's results from Bing. https://duckduckgo.com/duckduckgo-help-pages/results/sources/
Now, searching #ThanksIngenuity on Bing actually turns up the same result as duckduckgo, including the Jan 18 date! (curiously still not the same preview text as yours. )
But even better, Bing still has the page cached (perhaps the first time Bing was actually useful 😉 )
@65dBnoise As expected it's the catalog page for the #ThanksIngenuity video that was also posted to YouTube.
The cached result is from January 25, so at least it doesn't confirm any earlier date here. The video download links (which are not cached results) still work and let you download the video files from the NASA servers.
@stim3on
Google yields the same result (added flynn pratt) , but with a different date. Most probably duckduckgo mixed up its dates.
But still, those scuff marks on the regolith at the location of flight 71 landing have not been addressed yet.
@65dBnoise I hope we will get a n in depth blog post once everything calms down a bit.
I'm curious when they knew what happened. They likely had that broken rotor RTE image much earlier than the official update.
They only appeared on the public site when the update was out. I think the publication was artificially delayed for them.
I assume they already knew on Tuesday what happened, all their videos took time to film and edit, that's not something they can turn around in half a day.
@65dBnoise We just learned that the Ingenuity team saw the images of the damaged blades two days after the flight happened. This is also when they learned about the rotor damage.
This was stated by Josh Anderson, the Ingenuity Team Lead in a Reddit AMA that's currently ongoing. https://www.reddit.com/r/askscience/comments/1b1a674/comment/ksd7326/
65dBnoise
Simeon Schmauß
Undertow