Live data from Hacker News

Dorking: the use of search engines to find very specific data

alec.fyi

41–50 of 207 posts

Re: Dorking: the use of search engines to find very specific data

#41
post #2

Why doesn't google.com have a comprehensive list of these? I'm constantly seeing new ones that I didn't know about, but google never teaches you about them so you have to find them in obscure blog posts

One reason they might not have a comprehensive list is because some might be relatively expensive to execute, but they can't/won't disable them for legacy reasons.

Re: Dorking: the use of search engines to find very specific data

#43
post #16

Might be my librarian career bias but I'm always surprised at how few people know about query operators. Ironically as Google search seems to be ignoring vital parts of people's queries, they are becoming more needed now, whereas years ago I would have assumed a constantly improving Google search would get better at determining what I was looking for.

You don't even wanna know how many times specialized searches have saved my ass, after multiple years on uni, and working as a writer, journalist, programmer, en even a musician! You can safely say that my entire life revolves around being good at doing various forms of searches.

I have long believed that the art of precision search should be taught at the primary level. It is a necessary skill.

Re: Dorking: the use of search engines to find very specific data

#44
post #4
post #2

Why doesn't google.com have a comprehensive list of these? I'm constantly seeing new ones that I didn't know about, but google never teaches you about them so you have to find them in obscure blog posts

Google randomly ignores "search term in quotes". Related:examplesite.com used to work well. Now, it's better to use sites like alternativeto.net. ~phrase is unnecessary because but google searches for synonyms by default phrase1 + phrase2 - Google randomly ignores it. I use it this way +compulsoryTerm Although rare, there are things I simply can't find using Google. But Bing would. If Google keeps it up, other search…

I would be interested to see an example of it ignoring quotes silently because I've heard a lot about it. I use search terms in quotes relatively often and have never noticed that, although it does the 'did you mean without quotes' thing all the time.

In the past for very long tail content, I've found Bing and Yandex to be useful. Yandex image search in particular is often better than Google or Bing, particularly if you are searching for people because it does some facial recognition.

Re: Dorking: the use of search engines to find very specific data

#46

Does filetype: still work? I'm getting zero hits for example filetype:epub

It still work but some file type never return anything, I have the same problem with epub, pretty sure it's some google's shenanigan about books piracy.

https://support.google.com/webmasters/answer/35287?hl=en

Re: Dorking: the use of search engines to find very specific data

#48
post #39
post #25

A few corrections: The + (formerly used to force a term to be present in the result) and ~ (also find synonyms) operators have been deprecated. Google now advises to wrap the word in quotes instead of using the +. Google will also automatically look for synonyms without the use of ~. I have seen 'AROUND(n)' mentioned in many other places working as a proximity operator in Google, but I don't believe that is true and…

When you say "deprecated", you mean as in "discontinued" right? Not just like, discouraged?

Whoever the first developer was that used "deprecated" got it kind of wrong, the word should have been "depreciated".

Deprecate: "express disapproval of."

Depreciate: "diminish in value over a period of time."

I kind of cringe when other developers say "deprecated".

Edit: Versioning and not removing APIs is kind of the way to go, so you don't break client apps that possibly can't be updated easily or at all. "Depreciated" is a far better word to use with a far better outcome. AWS versions their APIs, they don't remove old ones. "I disapprove of using this API and we're taking it away at some random date" vs "this isn't the latest API, use the current one for new development" seems like a pretty stark difference in thinking to me. YMMV.

Re: Dorking: the use of search engines to find very specific data

#50

Last week I blocked every * .google.* domain on my network except "youtube-ui.l.google.com". Google Search: (1) ask a natural language question (since actual search is hobbled) (2) get unrelated garbage and ads back (3) blame yourself for "not being technical enough" to understand why the results aren't actually garbage. Google Search has deteriorated to the point that so far I haven't missed it at all .

Google still good for coding related searches

To be fair, I suspect "coding related searches" are easy for any search engine, given

1. the immense online/open-source nature of the profession: every blog/forum question and answer/documentation since the origin of the profession being in plain-text and mostly publicly accessible by default

2. and it all revolves around a precise, limited vocabulary.

Post reply on HN