(   )
                          (    )
                           (    )
                          (    )
                            )  )
                           (  (                  /\
                            (_)                 /  \  /\
                    ________[_]________      /\/    \/  \
           /\      /\        ______    \    /   /\/\  /\/\
          /  \    //_\       \    /\    \  /\/\/    \/    \
   /\    / /\/\  //___\       \__/  \    \/
  /  \  /\/    \//_____\       \ |[]|     \
 /\/\/\/       //_______\       \|__|      \
/      \      /XXXXXXXXXX\                  \
        \    /_I_II  I__I_\__________________\
               I_I|  I__I_____[]_|_[]_____I
               I_II  I__I_____[]_|_[]_____I
               I II__I  I     XXXXXXX     I
            ~~~~~"   "~~~~~~~~~~~~~~~~~~~~~~~~

Thu, 10 Dec 2015

Making Gopher Search More Useful

The floodgap server has a decent gopher search service [0][1]. Unfortunately, it does not do full-text search. You can help make the search more useful by making your gopher filenames and selectors more descriptive. So, for example, say you create a gopher document on Linux security. Instead of creating 'sec.txt' name it 'sysadmin_tips_for_linux_system_security.txt'. Then you will see your document in searches for those component words. If you use a gophermap, create some nicely descriptive display text, something like 'Linux Security Tips for Sysadmins'.

Here is a concrete example - I posted the Edgar Rice Burroughs Barsoom novels on my gopher site. The selector is as follows:

read more after the break...

posted at: 21:32 | path: / | permalink | gopher, search, tips, veronica