<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.network.gopher.general">
    <title>gmane.network.gopher.general</title>
    <link>http://blog.gmane.org/gmane.network.gopher.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4296"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4293"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4275"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4267"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4266"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4260"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4256"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4230"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4225"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4210"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4197"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4186"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4180"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4174"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4168"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4165"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4151"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4117"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4096"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.gopher.general/4090"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4296">
    <title>[gopher] Robots.txt</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4296</link>
    <description>&lt;pre&gt;Could I have the spec to, or perhaps somebody's explanation of, the
robots.txt file?  This will help me to explain it in my RFC.

&lt;/pre&gt;</description>
    <dc:creator>Nick Matavka</dc:creator>
    <dc:date>2012-05-23T20:17:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4293">
    <title>[gopher]  Minimalist Graphical Gopher Client</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4293</link>
    <description>&lt;pre&gt;Hello everybody !

I working on graphical gopher client.

(No java, it use C++ and QT.)

You can test it here : gopher://dams.zapto.org/1/gogoph-browser

To compile, install libraries for QT 4 and run :

$&amp;gt; qmake &amp;amp;&amp;amp; make

THAT'S ALL !

Regards,
&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-23T15:54:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4275">
    <title>[gopher] caps.txt complete syntax</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4275</link>
    <description>&lt;pre&gt;Doc (and other readers):

Would it be possible for you to please furnish the complete syntax of
capability files for Gopher?  This will make my job easier.

&lt;/pre&gt;</description>
    <dc:creator>Nick Matavka</dc:creator>
    <dc:date>2012-05-23T02:24:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4267">
    <title>[gopher] Nmap 6 supports Gopher!</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4267</link>
    <description>&lt;pre&gt;From the release notes at http://nmap.org/6/

"Nmap now supports the old-school Gopher protocol thanks to our handy gopher-ls NSE script. We even support Gopher over IPv6!"

I have absolutely no idea what that means... and I use Gopher and nmap almost daily.

(WTF is NSE?)


- Kim
&lt;/pre&gt;</description>
    <dc:creator>Kim Holviala</dc:creator>
    <dc:date>2012-05-22T18:54:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4266">
    <title>[gopher]  GOGOPH Server 2.4 release is out !</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4266</link>
    <description>&lt;pre&gt; Hello gopherspace !

A new version for gopher server from GOGOPH project is out !

*What is GOGOPH Server ?*

GOGOPH Server is a gopher server (RFC 1436 compliant). The main goal is
simplicity.
The server display the content of the live folder to the world.

*Bundle ?*

This software is mainly a Java program. It use 1 configuration file.
All your need is archive file from HERE :
gopher://dams.zapto.org/1/gogoph-server

*Why choose this one ?*

Very small program.
Very small memory footprint. (files are loaded on-the-fly)
Design of gogoph server is KISS. Very simple to use. Only one program for
one configuration file (plain text) for one live folder..
Based on modern Java NIO framework, can manage &amp;gt; 1K connections in the same
time. You can't do that with inetd.
Effective asynchronous network framework with Netty (JBOSS open source
library).
NO external library or framework or whatever. Only need basic Java version.
(Works with open source implementations)
Can handle download of VERY big files ( &amp;gt; 100 Mo test&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-22T15:06:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4260">
    <title>[gopher] Line terminators in Gopher transactions</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4260</link>
    <description>&lt;pre&gt;I understand that obsolete Mac OS sends CR as an EOL indicator, UNIX
sends LF, and Micro$haft Winblow$ sends CRLF.  How does all this get
fixed in Gopher?  What I mean is, how come a Windoze client, expecting
CRLF, is unburdened by a UNIX server sending it LF's only? Has Gopher
standardized on CR/LF/CRLF?  Is it the client's responsibility?  Is it
the server's responsibility?

&lt;/pre&gt;</description>
    <dc:creator>Nick Matavka</dc:creator>
    <dc:date>2012-05-22T00:49:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4256">
    <title>[gopher] ﻿Mime under Nine</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4256</link>
    <description>&lt;pre&gt;             Mimed File under Gopher Item Type 9

  Damien Carol made a proposal to use mimed file under the Item 0 to
carry all kind of binary files that could be base64 encoded; so, to be
assimilated to an ascii file. This proposal gave the possibility to
know which type of file is as reading the first blocks of that file
containing the label MIME. Furthermore, one could notice that using
"multipart", it is possible to know if that file is shortened or not
during the transmission according the boundary is displayed or not.
More, adding a checksum after this first part could verify the
integrity of the said file.

  Some persons said the item type "0" doesn't apply to this kind of
mimed file, even ascii encoded, due to the need to have a base64
decoder.

  From my side, I agree to the opinion that item type 0 must not be
used for mimed file.

  I saw, last days, many discussions about which item type to apply to
mimed file, PDF files, video files and so on. We all agree the fact
that item type is coded usin&lt;/pre&gt;</description>
    <dc:creator>Denis Bernard</dc:creator>
    <dc:date>2012-05-21T18:32:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4230">
    <title>[gopher] last call for OverbiteFF 3.0 beta comments</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4230</link>
    <description>&lt;pre&gt;I want to get this into Mozilla's loving arms before Fx13 comes out because
there is a minor bug fix related to that version. Please report serious bugs
promptly. Assuming none, this will be uploaded to them probably next Friday.

gopher://gopher.floodgap.com/9/overbiteff.xpi

&lt;/pre&gt;</description>
    <dc:creator>Cameron Kaiser</dc:creator>
    <dc:date>2012-05-19T18:42:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4225">
    <title>[gopher] Which itemtype for video (vote)?</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4225</link>
    <description>&lt;pre&gt;Gentlemen and ladies:

It has come to my attention that the choice of item-type for video is
somewhat controversial.  The existing, but somewhat awkward, choice is
';' (semicolon), which is my own preference, but there are some who
have floated the idea of it being changed to 'v' (lowercase vee).  The
sole reason I prefer the semicolon is that it is the (unofficially)
established standard.  If the selector were changed, admins would have
to update their sites to accomplish the change, and some Gopher sites
are... shall we say... updated once in a bit over a millennium.
Furthermore, clients would have to be reprogrammed to accept the 'v'
selector as video.

Cordially,

Nick

vee: 0
semicolon: 1

&lt;/pre&gt;</description>
    <dc:creator>Nick Matavka</dc:creator>
    <dc:date>2012-05-19T16:18:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4210">
    <title>[gopher] Soo sad today...</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4210</link>
    <description>&lt;pre&gt;my NAS is out...


4To fo data lost  :/

!!! NetGEAR ReadyNAS RND4000 !!!

&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-19T09:15:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4197">
    <title>[gopher] Gopher RFC propositions</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4197</link>
    <description>&lt;pre&gt;printf("Hello, World!\n");

OK, so I've followed teh discussions about the proposed changes to the RFC. To be honest, I've not read of *any* change that would actually make sense. None of the changes proposed are backwards-compatible, and they really don't help the cause at all.

Say, the MIME thingy; yeah, let's decide that MIMEs are type M. Fine. What then? No client in teh whole universe supports such a filetype. And even if they did support it, why would I use it? I can serve out menus with type 1, text with type 0, html (which is stupid) with type h etc etc. There absolutely *no* need for sending out MIME, ever. Well... except for mailing list messages. But even then Jacob's neat mbox script works way better.

Anyway.

What I would like to see is (and I'm always right, so hear me out):

* what do about teh US-ASCII vs. Latin-1 vs. UTF-8 issue?
* are PDF's really type "p", or "d" - a definite list of filetypes
* should the server end the transmission with a dot or not?

And that's about it. Those are the&lt;/pre&gt;</description>
    <dc:creator>Kim Holviala</dc:creator>
    <dc:date>2012-05-17T18:36:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4186">
    <title>[gopher] Support for MIME type</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4186</link>
    <description>&lt;pre&gt;Hello everybody !

I read the RFC of gopher 1.0 protocol and I can say that MIME is already
possible.

Read that :
1) MIME file is '0' type item
2) all clients are compatible they can get '0' type files

The file get is something like that :

*MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=frontier

This is a message with multiple parts in MIME format.
--frontier
Content-Type: text/plain

This is the body of the message.
--frontier
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64

PGh0bWw+CiAgPGhlYWQ+CiAgPC9oZWFkPgogIDxib2R5PgogICAgPHA+VGhpcyBpcyB0aGUg
Ym9keSBvZiB0aGUgbWVzc2FnZS48L3A+CiAgPC9ib2R5Pgo8L2h0bWw+Cg=
--frontier--*


Clients can easily manage data because many lib exists to read MIME.

The only thing to do is to add feature to client that read the first line
of '0' type item.
If this line starts with "*MIME-Version:* " , then it's a mime encoded file
and client can offer to extract file or something else.

It's very very simple to manage mime type this way.

I wil&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-17T11:07:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4180">
    <title>[gopher] ExitEnclave: revenge of Gor</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4180</link>
    <description>&lt;pre&gt;https://trac.torproject.org/projects/tor/wiki/doc/ExitEnclave

Thinking about setting one up locally.

&lt;/pre&gt;</description>
    <dc:creator>Cameron Kaiser</dc:creator>
    <dc:date>2012-05-17T00:47:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4174">
    <title>[gopher] Strange implementations of "Missing file"</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4174</link>
    <description>&lt;pre&gt;Hello everybody,

I'm facing a big pb with my search engine/crawler.

The crawler sends selectors that don't exists sometimes. (Updated / removed
/ don't exists / whatever)

I use to handle error like that :
1) parse response
2) Try to parse as Menu
3) If the first item of the menu is '3' error item type then ERROR

But this method don't works. Mainly because some servers reply very odd
responses

Some old servers sends that :

*BAD:*
==&amp;gt; 0Sorry, but the requested token could not be
found&amp;lt;TAB&amp;gt;Err&amp;lt;TAB&amp;gt;localhost&amp;lt;TAB&amp;gt;70
gopher://wss-ds.no-ip.info:70/0/robots.txt

==&amp;gt; 0'/robots.txt' does not exist&amp;lt;TAB&amp;gt;&amp;lt;TAB&amp;gt;error.host&amp;lt;TAB&amp;gt;1
gopher://gdead.berkeley.edu:70/0/robots.txt
gopher://net.bio.net:70/0/robots.txt
gopher://newkraitch.cs.berkeley.edu:70/0/robots.txt
gopher://nemesis.cs.berkeley.edu:70/0/robots.txt
gopher://quix.us:70/0/robots.txt

=&amp;gt; &amp;lt;Empty String&amp;gt;
gopher://sdf.org:79/0/robots.txt

=&amp;gt; finger: /robots.txt: no such user
gopher://holviala.com:79/0/robots.txt


*GOOD:
gopher://gopher.r-36.net:70/0/robots.txt
gop&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-16T13:07:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4168">
    <title>[gopher] Found treasur</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4168</link>
    <description>&lt;pre&gt;Hello !

My crawler found a treasur.

Yeeehaaar !

=&amp;gt; gopher://gopher.viste-family.net/1/NES/

&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-15T17:57:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4165">
    <title>[gopher] Need advice</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4165</link>
    <description>&lt;pre&gt;I'm working on Gopher Client and I have a pb.

My client works with URL.

But for type item 7, I don't know how to manage them.

Basically what my client do :

URL =  gopher://example.com/7/search?foo%20bar      =&amp;gt;     request to [
example.com] port [70] wtih selector [/search&amp;lt;TAB&amp;gt;foo bar]

BUT there are many gopher sites that use '?' in there selectors :/   what a
crap !

Another detail, in RFC 4266 specify that '?' character is reserved for ASK
Gopher+ feature.

What's your opinion gopherspace ?
Regards,
&lt;/pre&gt;</description>
    <dc:creator>Damien Carol</dc:creator>
    <dc:date>2012-05-15T09:32:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4151">
    <title>[gopher] Finally: Chrome extensions have real sockets</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4151</link>
    <description>&lt;pre&gt;It's only in Canary. But finally we can ditch the proxy kludge and
Overbite Chrome can be a real gopher client just like OverbiteFF.

http://blog.alexmaccaw.com/chrome-tcp-udp

&lt;/pre&gt;</description>
    <dc:creator>Cameron Kaiser</dc:creator>
    <dc:date>2012-05-14T19:30:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4117">
    <title>[gopher] Capability files are dangerous</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4117</link>
    <description>&lt;pre&gt;Capability files are dangerous!

  Overbite Project provides a module for the Internet browser FireFox
to ease Gopher netsurfing. This project is going to promote a
capability file (caps.txt) to be installed inside a Gopher server.
This practice is dangerous for users of the Gopher space and the
administrators of Gopher servers.

  Up to day, any Gopher client was able to deal with any Gopher server
(more or less). The spirit of Gopher is to keep it as simple as
possible and, mainly, for retrieving files anonymously. Up to day, it
was impossible, for an administrator of a Gopher server, to know which
flavor of a Gopher client was browsing its site. The only information
available was from the IP address. Now, with a capability file like
“caps.txt”, there is a fingerprint. Without to be paranoiac, everybody
heard of web sites serving contents (or refusing to serve!) according
the software or the system that the client have. That will happen for
the Gopher space too!

  A capability file creates an indirect&lt;/pre&gt;</description>
    <dc:creator>Denis Bernard</dc:creator>
    <dc:date>2012-05-14T08:48:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4096">
    <title>[gopher] OverbiteFF 3.0 beta</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4096</link>
    <description>&lt;pre&gt;OverbiteFF 3.0! Now with caps!

This needs testing, so this is a beta with debugging on. Locales are
incomplete.

Caps support right now allows you to navigate "up" paths. Eventually it
will be expanded. Because threading extensions is a bit tricky in Firefox,
the caps is fetched when an "up" is requested and then cached. If it turns
out there is no caps, then the root is fetched as a bailout. Caching is
for the life of the browser instance, since this is simpler, but if you
visit pseudo-URL gopher:/// it will be cleared out.

There is machinery already to display a formatted caps display, but that's
all it supports right now. But this is now the first "major" client to
support caps and Overbite Android will be next once the kinks are worked
out of OverbiteFF.

The code is based mostly on the Public Proxy.

Firefox 3.6+ required (current SeaMonkey also okay). Fx10+ or TenFourFox
recommended. This is a beta only.

gopher://gopher.floodgap.com/9/overbiteff.xpi

&lt;/pre&gt;</description>
    <dc:creator>Cameron Kaiser</dc:creator>
    <dc:date>2012-05-12T03:27:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4090">
    <title>[gopher] Overbite Chrome WFM</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4090</link>
    <description>&lt;pre&gt;I just tried Overbite Chrome on Chrome 18 on my Mac mini, and it works fine
with gopher:// URLs in the omnibox. So you must have a different search URL.
Please send me what search URL you get when you type in a gopher:// URL so
I can compare it.

&lt;/pre&gt;</description>
    <dc:creator>Cameron Kaiser</dc:creator>
    <dc:date>2012-05-11T21:51:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.gopher.general/4082">
    <title>[gopher] New gopher proposal</title>
    <link>http://comments.gmane.org/gmane.network.gopher.general/4082</link>
    <description>&lt;pre&gt;Greetings,

in  accordance  to the discussion on this list about some maybe flaws of
gopher I wrote down a simple proposal on how to do gopher but  including
the modern ideas.

http://sprunge.us/DMSE

The whole proposal does break backwards compatibility and I don’t expect
it to be adopted, because one intention of this  mailinglists’s  efforts
is   to  preserve the old gopherspace and its history. Maybe it is worth
to do another gopherspace?


Sincerely,

Christoph Lohmann


_______________________________________________
Gopher-Project mailing list
Gopher-Project&amp;lt; at &amp;gt;lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project&lt;/pre&gt;</description>
    <dc:creator>Christoph Lohmann</dc:creator>
    <dc:date>2012-05-11T14:23:34</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.gopher.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.gopher.general</link>
  </textinput>
</rdf:RDF>

