{"id":4346,"date":"2009-12-07T13:20:18","date_gmt":"2009-12-07T13:20:18","guid":{"rendered":"http:\/\/jurnsearch.wordpress.com\/?p=4346"},"modified":"2009-12-07T13:20:18","modified_gmt":"2009-12-07T13:20:18","slug":"anonymous-google-cses","status":"publish","type":"post","link":"https:\/\/jurn.link\/jurnsearch\/index.php\/2009\/12\/07\/anonymous-google-cses\/","title":{"rendered":"Anonymous Google CSEs"},"content":{"rendered":"<p>There&#8217;s a newly released Firefox addon, called <a href=\"https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/13996\">Google Custom Search 1.1.2<\/a> and made by <a href=\"http:\/\/kloog.de\/\">Kai Londenberg<\/a>. It creates independently-hosted anonymous Google CSEs, which you can manage and refine from your Google search results \/ browser.  Although it uses the Google API, your engine&#8217;s data appears to be stored anonymously on a server in Europe&#8230;<\/p>\n<blockquote><p>&#8220;A Google Account is not required anymore, Custom Search Engines can be stored anonymously on quicksear.ch&#8221;<\/p><\/blockquote>\n<p>Basically, using this addon gives you a seamless melding of the normal Google results format with the major configuration possibilities of a CSE. It&#8217;s Google&#8217;s SearchWiki on steroids, in an exo-skeleton.<\/p>\n<p>But I don&#8217;t see any way to backup your CSE&#8217;s XML annotations file of URLs, which means it would be rather risky to invest large amounts of time building a subject-specific CSE this way, rather than using Google&#8217;s own interface.  Perhaps a backup option will appear once the quicksear.ch site goes live &mdash; the addon and service are currently very new, having seemingly been live since September.<\/p>\n<p>There&#8217;s no way to upload a &#8220;big list &#8216;o URLs&#8221; in the traditional manner, and have them automatically boosted in the CSE&#8217;s search rankings. Your CSE is currently a &#8220;add one URL at a time&#8221; job, as you surf the search results day in and day out.  Which perhaps gives your CSE some interesting anti-spam\/anti-SEO features, if your CSE is to be used as a mass collaborative anonymous engine (which it apparently can be &mdash; tick &#8220;accept volunteer contributions&#8221; when creating your CSE).  And it doesn&#8217;t seem to include Google Books results, even when you tell it to include them and boost their rating by 100%.<\/p>\n<p>You currently lose Google&#8217;s new &#8220;Options&#8230;&#8221; sidebar, when searching via your quicksear.ch CSE addon (which appears along with the others, in Firefox&#8217;s top-right mini search box).<\/p>\n<p>Just like the official Google CSEs, you get cut-and-paste HTML code, which lets others try out your CSE without needing to log in or install anything.  I created a new experimental CSE titled <strong><a href=\"http:\/\/jurn.org\/jurn-collab.html\">JURN collaborative<\/a><\/strong>, with permissions for collaborators, but how collaborators contribute to it is currently a mystery.<\/p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp;Update: it seems that to collaborate you would have to share your quicksear.ch password with your collaborators.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There&#8217;s a newly released Firefox addon, called Google Custom Search 1.1.2 and made by Kai Londenberg. It creates independently-hosted anonymous &hellip;<\/p>\n<p><a href=\"https:\/\/jurn.link\/jurnsearch\/index.php\/2009\/12\/07\/anonymous-google-cses\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/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":[9,16],"tags":[],"class_list":["post-4346","post","type-post","status-publish","format-standard","hentry","category-jurns-google-watch","category-spotted-in-the-news"],"_links":{"self":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts\/4346","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=4346"}],"version-history":[{"count":0,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts\/4346\/revisions"}],"wp:attachment":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/media?parent=4346"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/categories?post=4346"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/tags?post=4346"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}