Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Removed site: searches of my sites

Nobody but me cares about searching my own sites, removed,
put elsewhere.
  • Loading branch information...
commit ed7ca2986616787bedd5d29fd1fb7ce73ffa4204 1 parent 54ef245
@dtaht authored
Showing with 8 additions and 19 deletions.
  1. +4 −4 doc/history.org
  2. +4 −15 src/lisp/gnugol.el
View
8 doc/history.org
@@ -39,7 +39,7 @@ In the race to add feature after feature after freature, google and other search
A typical google page is now over 25K long, not counting the image, contains dozens of extra links, and takes 5-10 seconds to download and render over slow, international links. Not only that but the various search engines are contributing to breaking the Internet, by, for example, increasing the default MSS size to 10 from 2...
-Dave had always admired the DNS system, and felt that now that "search" is almost a commodity, that it would be possible to define a binary (udp) based protocol for search. There are plenty of unused, useless services in /etc/services - having a special port number for search makes sense.
+Dave had always admired the DNS system, and felt that now that "search" is almost a commodity, that it would be possible to define a binary (udp) based protocol for search, this time using a flexible header format, and compression and encryption of that. There are plenty of unused, useless services in /etc/services - having a special port number for search makes sense.
Problem with that was that most query-response protocols don't work well through a firewall.
@@ -48,7 +48,7 @@ Enter IPv6. Without NAT, you have end to end networking. Response problem solve
** Gaining speed
The original version of the gnugold network protocol used 2!! packets to get a query out and a response. If you went through a 6in4 tunnel, it was 4 packets. (2 very short ones, however)
-This means that by the time you completed a tcp handshake vs the normal google, you've already got a response from gnugold, on a long latency link.
+This means that by the time you completed a tcp handshake vs the normal google, you had already got a response from gnugold, on a long latency link.
The earliest prototype came in at *half* the time to transmit a query from australia and get the response that google.com.au did, best case. Due to the unreliable network I was on, it was actually often 5-10 times faster.
@@ -59,13 +59,13 @@ Additional benefits - vastly reduced data traffic. Control of the formatting can
The second nice thing about end to end networking is that it makes it easier -assuming a static ip address - to have for-pay search. Dave would gladly pay a few bucks a month for faster - and ad-free searching!
* Death #1
-Unfortunately the UDP based network system described above proved unreliable enough in practice for Dave to discard it (at least temporarily) in favor of a few other network backend ideas.
+Unfortunately the UDP based network system described above proved unreliable enough in practice for Dave to discard it (at least temporarily) in favor of a few other network backend ideas. (See also: [[http://gettys.wordpress.com/category/bufferbloat/][Bufferbloat]] ) The ad-hoc protocol was also a terrible design, too close to HTTP in origination.
* Death #2
And THEN google obsoleted their soap API in favor of json, rendering the original front-end client useless.
* Death #3
Finally that soap API went away...
* Rebirth - October, 2010
-After encountering [[http://nex-6.taht.net/posts/Beating_the_speed_of_light_on_the_web/][Google's latest results page]], Dave blew a gasket, IPv13 was now a reality!!??
+After encountering [[http://nex-6.taht.net/posts/Beating_the_speed_of_light_on_the_web/][Google's latest results page]], Dave blew a gasket. [[http://the-edge.blogspot.com/2003/09/paul-vixie-vs-verisign.html][IPv13]] was now a reality!!??
So he dusted off the client, and rewrote it (with the help of some friends) to drop the network backend entirely in favor of curl, and incorporated the json API. After some positive feedback the new gnugol client seemed useful enough for general use, so he released it on github.
View
19 src/lisp/gnugol.el
@@ -2,7 +2,7 @@
;; Copyright (C) 2010 Dave Täht
;; License: GNU Public License, version 3
;; Author: Dave Taht
-;; Maintainer: d + gnugol AT @ taht.net
+;; Maintainer: d + gnugol AT taht.net
;; Created: Dec-2008
;; Version: See git tree
;; Keywords: extensions, web, search, google
@@ -105,7 +105,7 @@
;; FIXME figure out how to search the buffer-modes
-;;(defun gnugol-get-output-mode
+;; (defun gnugol-get-output-mode
;; "Get the gnugol output mode from the current buffer mode."
;; (if gnugol-default-output-mode-sensitive
;; ()
@@ -258,18 +258,6 @@
(gnugol-search-google (concat "site:gnugol.taht.net " str))
)
-(defun gnugol-search-the-edge(str)
- "Search the-edge via gnugol."
- (interactive "sSearch the-edge: ")
- (gnugol-search-google (concat "site:the-edge.blogspot.com " str))
- )
-
-(defun gnugol-search-nex-6(str)
- "Search nex-6 site via gnugol."
- (interactive "sSearch Nex-6: ")
- (gnugol-search-google (concat "site:nex-6.taht.net " str))
- )
-
(defun gnugol-search-koders(str)
"Search koders.com site via gnugol."
(interactive "sSearch Koders: ")
@@ -328,4 +316,5 @@
-(provide 'gnugol)
+(provide 'gnugol)
+

0 comments on commit ed7ca29

Please sign in to comment.
Something went wrong with that request. Please try again.