# Why I'm Not Behind Port 70
       
       2018.08.31/08:31
                           ... written by lambda
       
       As you may have noticed: fnord.one's gopher server doesn't
       use gopher's default port 70. This makes my burrow hard to
       find.
       
       Then, why don't I change the port number? There are clear
       reasons for this.  Wanna know them?
       
       
       ## Why, Oh Why?
       
       My shared-hoster - uberspace.de - allows (and encourages)
       its customers to setup their own server - especially if they
       don't provide the requested services themselves. I wanted to
       have gopher, they didn't provide a gopher service, so I
       decided to setup one myself.
       
       In case you setup your own server, the guys and girls
       @uberspace.de asks of you not to use any of the (well known)
       ports listed in /etc/services as well as some ports used by
       widely used, well known applications.
       
       Their reasons are to prevent visitors from confusing a
       user's services with their official ones, and to keep them
       the possibility of using standard ports to establish
       more/other official services of their own in the future.
       Also, they want to minimize reasons of traffic collision.
       
       I roll with this drawback for now, because I consider their
       reasons to be reasonable and fair. Last, but not least,
       their focus on free software, flexibility, assortment of
       tools, documentation, storage space and prices does
       "compensate" this - a lot!
       
       
       ## And Why 65446?
       
       As for the port number: I got it by chance and random. At
       the time I did check for a free port, 65446 was available.
       Then claimed it and I got it.
       
       So, there is no meaning behind the non-default port, only
       technical reasons - and a gopher daemon.
       
       
       
       # References
       
 (HTM) </www> Uberspace.de Wiki
       Last access: 2018-08-31.