{"id":13560,"date":"2015-09-24T13:55:39","date_gmt":"2015-09-24T12:55:39","guid":{"rendered":"https:\/\/jurnsearch.wordpress.com\/?p=13560"},"modified":"2015-09-24T13:55:39","modified_gmt":"2015-09-24T12:55:39","slug":"duckduckgo-testing-2","status":"publish","type":"post","link":"https:\/\/jurn.link\/jurnsearch\/index.php\/2015\/09\/24\/duckduckgo-testing-2\/","title":{"rendered":"DuckDuckGo testing #2"},"content":{"rendered":"

I did a quick experiment in making a Custom Search Engine via DuckDuckGo<\/a>‘s link-chaining feature. In this experiment I enable a search across a small group of reputable crowdfunding services, via this search in DuckDuckGo. The search format is…<\/p>\n

\"open access\" site:patreon.com,gofundme.com,peerbackers.com,mysherpas.com,wedidthis.org.uk,crowdcube.com,cofundos.org,indiegogo.com,rockethub.com,kickstarter.com<\/code><\/p>\n

Works fine. WordPress.com refuses to embed an active link that contains “a phrase” (it’s the inverted commas, presumably), but this test link should work<\/a>.<\/p>\n

Unfortunately chaining a list of URLs appears to turn off DuckDuckGo’s intitle:<\/strong> search modifier, at least when searching for a phrase. But intitle:<\/strong> does work when using a single keyword, in a search such as… <\/p>\n

intitle:journal \"open access\" site:patreon.com,gofundme.com,peerbackers.com,mysherpas.com,wedidthis.org.uk,crowdcube.com,cofundos.org,indiegogo.com,rockethub.com,kickstarter.com<\/code><\/p>\n

A keyword \/ phrase that veers more into popular culture (such as Lovecraft<\/strong>) seems to cause Kickstarter results to swamp the search results.<\/p>\n

I also noted that the search results from the above example fail to distinguish between “open access” and “open-access”. Adding +<\/strong>, as in +”open access”<\/strong>, fails to force a verbatim search. There is obviously some slight wiggle-room in DuckDuckGo’s claim that they don’t try to second-guess your search terms. Google has the same problem with a verbatim that is-not-really-verbatim.<\/p>\n

There’s no sort-by-date filter on the search results, and adding the search modifier sort:date<\/strong> to the search causes a chained-URLs search to totally fail.<\/p>\n

Sadly a list of chained URLs just doesn’t work with DuckDuckGo’s Image Search. For instance, a searcher can’t constrain Image Search thus…<\/p>\n

\"cute cat\" site:flickr.com,deviantart.com,commons.wikimedia.org<\/code><\/p>\n

When looking for Creative Commons images using DuckDuckGo Image Search a better strategy is probably simply to dispense with the URL chain and use this…<\/p>\n

\"cute cat\" \"some rights reserved\" OR \"cute cat\" commons attribution -noncommercial<\/code><\/p>\n

This will still pick up “noncommercial” CC pictures on Flickr (since Flickr obfuscates the picture’s license behind a “some rights reserved” generality), but at least you’d be headed in the right direction. Note that it seems that DuckDuckGo only lets you use a single minus sign to knock out one keyword from the search, and it has to be at the end of the search to work.<\/p>\n

A “Region” filter doesn’t appear to work on Image Search. You can’t just see the “cute cats” of Japan, for instance.<\/p>\n

\"cats\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I did a quick experiment in making a Custom Search Engine via DuckDuckGo‘s link-chaining feature. In this experiment I enable …<\/p>\n

Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-13560","post","type-post","status-publish","format-standard","hentry","category-jurn-tips-and-tricks"],"_links":{"self":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts\/13560","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/comments?post=13560"}],"version-history":[{"count":0,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts\/13560\/revisions"}],"wp:attachment":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/media?parent=13560"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/categories?post=13560"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/tags?post=13560"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}