I live two towns over from Dorking. https://en.wikipedia.org/wiki/Dorking
I live just a few miles to the North. Nice to see a few other ~Dorking locals here :)
Dorking: the use of search engines to find very specific data
61–70 of 207 posts
Re: Dorking: the use of search engines to find very specific data
#62Earlier 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…
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, but is deprecated -- that is, discouraged. At some point in the future, it will stop working, completely.
the rest of us don't just kind of but REALLY cringe when people say "depreciate" when they mean "deprecate". They are different words, "deprecated" is the right one, it is intentional, it is the word.
Sorry, you are the one using the wrong word.
Re: Dorking: the use of search engines to find very specific data
#63Why is this called "dorking"? "Dorking" is a word that just means using search engines to find very specific data? This seems bizarre to me. Why does this need a special word?
Or it actually means using search operators beyond natural language entry? That's what this page seems to be about? I don't know why that would be called "dorking" either?
Re: Dorking: the use of search engines to find very specific data
#64Syntax for doing things like this with DDG: https://help.duckduckgo.com/duckduckgo-help-pages/results/sy...
I'd switch to DDG in a half second if they supported the full query syntax of altavista.digital.com (see http://jkorpela.fi/altavista/ if you've forgotten). Disclaimer: I work for, um, Google.
Re: Dorking: the use of search engines to find very specific data
#65Earlier quoted context omitted.
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…
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,…
[deleted]
Re: Dorking: the use of search engines to find very specific data
#66I think it would be useful to be able to explicitly search around knowledge graph entities or site topics, e.g. a programming language, a city, a season, without having that single/specific term.
So a search including all sites related to an entity, say Munich or python along with the terms the user is searching because a page might then not specifically include the entity in its keywords or the text on the site or have a different language or use a synonym.
I’m sure search engines consider this somewhat, but explicitly activating such a feature would be a great improvement for the user.
Stackexchange has this feature with tags (using []), with user curated tags. Would be nice to have in DDG or google.
Re: Dorking: the use of search engines to find very specific data
#67Earlier quoted context omitted.
But "express disapproval of" is exactly the meaning intended when we say that a feature is deprecated. It signifies that it is best practice not to use it.
If it’s given as a warning then yes, e.g. the dplyr package in R sometimes outputs “feature xyz is deprecated and will be removed in version x.x”. Often though it’s used when the feature is already removed, i.e., it’s not only best practice not to use it, but also impossible with that version.
In this case, depreciated is incorrect. Removal has already happened, the "period of time" is already over.
Re: Dorking: the use of search engines to find very specific data
#68Why is this called "dorking"? "Dorking" is a word that just means using search engines to find very specific data? This seems bizarre to me. Why does this need a special word? Or it actually means using search operators beyond natural language entry? That's what this page seems to be about? I don't know why that would be called "dorking" either?
It all started with a def con talk if I remember correctly.
Re: Dorking: the use of search engines to find very specific data
#69Earlier quoted context omitted.
My guess would be because Google eventually wants users to find everything via natural language queries.
Actually, Google eventually wants users to find everything with predictive AI giving it to them before they search. That's not really a secret, they've announced more than once in the past that that is what they are increasingly working toward.
That would be great for malware researchers. Google can give them malware before they even search for it!
The reality is that all sorts of things are blocked now, including things that are perfectly legal.
Re: Dorking: the use of search engines to find very specific data
#70Syntax for doing things like this with DDG: https://help.duckduckgo.com/duckduckgo-help-pages/results/sy...
I'd switch to DDG in a half second if they supported the full query syntax of altavista.digital.com (see http://jkorpela.fi/altavista/ if you've forgotten). Disclaimer: I work for, um, Google.
I do wish they supported a larger search syntax. My current workaround is I have a massive bookmark folder of alternative search engines that I try if I'm not having luck narrowing things down enough.