The - prefix operator is very useful and still works.
Google should reinstate the + prefix operator. It was only taken out because it screwed up the search results for Google+, which is dead now.
Dorking: the use of search engines to find very specific data
171–180 of 207 posts
Re: Dorking: the use of search engines to find very specific data
#172Earlier quoted context omitted.
Nope. It is deprecated -- it's use is disapproved of, you should stop using it. In the future it will go away but for now it works, so you can use it, but its use is discouraged. Depreciated doesn't make any sense -- the value of the deprecated API does not diminish over time. It works, until it stops working. It's on or off. It doesn't work less and less every month or anything. It currently still works completely,…
Yeah, nope yourself. It seems like a lot of people aren't really thinking this through very much. And that is absolutely the wrong way to approach API development. An API that is being sun-setted should never be removed, because older clients could still use it but sometimes can't be upgraded to newer clients. Removing a v1 API breaks those clients and it's a shitty thing to do to users. Yeah, people should be buildi…
Deprecated is a word. No negativity implied, but equating "deprecated" to "depreciated" is insular. It is okay to be wrong, I have been wrong (George Foreman Grill dissenter..."it drips fat in the front? Gross."). I am not sure what your native language is, and I wish I did so we could communicate, but it is like calling a "warning" as "decay" in English (US).
Typo corrected.
Re: Dorking: the use of search engines to find very specific data
#173The - prefix operator is very useful and still works. Google should reinstate the + prefix operator. It was only taken out because it screwed up the search results for Google+, which is dead now.
I find myself having to use the "-" prefix a lot these days.
Re: Dorking: the use of search engines to find very specific data
#174Why 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
Having a reliable search syntax would commoditise Google as other search engines could offer the same options. Having just a search box, instead of lots of options was how they moved ahead of e.g altavista in the first place. Google would rather people are trained to just type human speak into the search box.
> would commoditise Google as other search engines could offer the same options
i highly doubt that's a concern. Google's competitive advantage will not be eroded if they did have operators clearly documented. Another search engine could not replicate google's index, even if they could replicate the operators.
And most people do want to just type human speak and have the machine magically interpret it correctly.
Re: Dorking: the use of search engines to find very specific data
#175A 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…
Google has been gradually becoming useless for anything but the most basic/popular terms, over the last few years.
Just now I had to give up trying to look up "the term for fans that are paid actors" and variations.
Asking on Reddit or Stack Overflow would be faster than Google's search engine for some things now.
Re: Dorking: the use of search engines to find very specific data
#176Don't you just love it when you're carefully crafted search finally displays the words or phrases you want in the snippet on the results page but then when you actually open the link and CTRL+F for it it's nowhere to be found? Not even in the raw HTML?
I sure do.
Re: Dorking: the use of search engines to find very specific data
#177Last 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 .
What is it you are searching for that the results are useless?
For example a specific error string which is definitely in a github repo - it won't find it. I was trying to find why the error is printed. In the past, I used google to even find codes related to my interest (so I additionally specified language keywords like "void" "define" "float") - not working anymore. Fortunately github search works for that but it's slow. In the past, Google ignored "c++", amusingly now it doesn't ignore it but it has much much smaller index, it seems. Google is now useful only for "programming" queries like: why is c++ popular. And most results are then Quora / Stack Overflow / YouTube. Google is sadly a tool for masses and their simple queries about restaurants, actors, etc now. :(
Re: Dorking: the use of search engines to find very specific data
#178[deleted]
Re: Dorking: the use of search engines to find very specific data
#179Earlier quoted context omitted.
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. "Depreci…
In French, we have an equivalent for "depreciate": déprécier. But we don't have a close relative for "deprecate" (which translates to "désapprouver, dénigrer" and would never be used for an API).
We tend to use the terms "déprécié" (~depreciated) or "déprécaté" (~deprecated but not valid French).
On the other hand, "deprecate" seems to also translate to "mark as obsolete" according to https://www.wordreference.com/enfr/deprecate
I guess both terms make sense but I would keep using "deprecated".
Re: Dorking: the use of search engines to find very specific data
#180I live two towns over from Dorking. https://en.wikipedia.org/wiki/Dorking
Almost due south of Dorking, down the road in Horsham. The small town was the first thing I thought of on seeing this title. I'd imagine this area actually has a fair few HNers, as it's in the tech catchment area for London, Reading, etc.