>Moreover, a search result returning "only" two results should be taken as a good thing for someone with confidence in their dataset
I completely agree with you here but in my experience it's not anything new with DDG, that's always been a problem as far as I'm concerned.
As a hobby I sometimes have to reverse engineer electronic circuits, when I'm not sure what a chip does I try to search the inscriptions on the package to see if I can find a datasheet online. Sometimes you end up with very cryptic strings like "xardc10-egh" or whatever. If you input this string on Google it gives you no results:
That being said DDG improved slightly, when I did searches like those a couple of years ago I'd often end up with results containing completely broken encodings, binary dumps as ascii and other obviously erroneous content that got indexed by mistake. Here the results at least appear to link towards proper pages.
I completely agree with you here but in my experience it's not anything new with DDG, that's always been a problem as far as I'm concerned.
As a hobby I sometimes have to reverse engineer electronic circuits, when I'm not sure what a chip does I try to search the inscriptions on the package to see if I can find a datasheet online. Sometimes you end up with very cryptic strings like "xardc10-egh" or whatever. If you input this string on Google it gives you no results:
https://www.google.com/search?hl=en&q=xardc10%2Degh
If I do it on DDG I get pages of irrelevant results:
https://duckduckgo.com/?q=xardc10-egh&t=ffab&ia=web
That being said DDG improved slightly, when I did searches like those a couple of years ago I'd often end up with results containing completely broken encodings, binary dumps as ascii and other obviously erroneous content that got indexed by mistake. Here the results at least appear to link towards proper pages.