[gopher] Gopherplus.org management

[James Mills]

Yes you are correct. Gopher+ was/is extensions to the original protocol.

Details here: https://en.wikipedia.org/wiki/Gopher%2B

Also out of curiosity what Linux cli client are you using?

cheers
James


James Mills / prologic

E: prologic at shortcircuit.net.au
W: prologic.shortcircuit.net.au

On Thu, Jan 28, 2016 at 3:22 PM, Héctor A. <habreu71 at gmail.com> wrote:

> I am still new to gopher, so my question may or may not make sense: isn't
> "Gopherplus" different to "Gopher"?
>
> I read somewhere that Gopher+ is more specific to some additions that were
> made to the protocol.
>
> The command line client I am using in Linux shows "non gopher+" next to
> the first link that appears when I start the application, which takes me to
> the floodgap gopher server.
>
> Thank you in advance for the info.
> --
> Héctor
> On Thu, Jan 28, 2016 at 02:02:02PM -0800, James Mills wrote:
> > I wholly agree ;)
> >
> >
> > James Mills / prologic
> >
> > E: prologic at shortcircuit.net.au
> > W: prologic.shortcircuit.net.au
> >
> > On Thu, Jan 28, 2016 at 1:52 PM, Kevin Veroneau <kevin at veroneau.net>
> wrote:
> >
> > > I believe the port 80 version of gopherplus.org should be a fancy
> > > gopher2web proxy or we'll be mocked as a community for being
> hypocritical.
> > >
> > > For example, the Python Web development community has many unfortunate
> > > blogs which are not made in Python.  This has lead to some interesting
> > > arguments online about how some Python Web developers are hypocrites.
> I
> > > personally made a custom blogging platform when I launched
> PythonDiary.Com
> > > to avoid this criticism...
> > >
> > > So gopherplus.org:80 should a fancy gopher2web proxy of
> gopherplus.org:70
> > > to easily showcase the gopher protocol.  So RSS feeds should be either
> fed
> > > in via a cron script, or dynamically using a mole.
> > >
> > > Personally I'd like to see a tree view of all of gopherplus.org, much
> > > like that Java gopher client is being built.  It would be interesting
> for
> > > people who may have never seen gopher before understand the fundamental
> > > advantage of gopher menus.
> > >
> > >   Original Message
> > > From:denis.bernard at laposte.net
> > > Sent:January 28, 2016 12:59 PM
> > > To:gopher-project at lists.alioth.debian.org
> > > Reply-to:gopher-project at lists.alioth.debian.org
> > > Subject:[gopher] Gopherplus.org management
> > >
> > > Many thanks for your offerings of hosting gopherplus.org! However it
> not a
> > > technical support I am requesting: I can host this Internet site on my
> own
> > > home server (both for 70 and 80) like I do it for my domain
> oceamer.com.
> > > Today, gopherplus.org is hosted on a commercial web site provider that
> > > already mirror my home server under the domain oceamer.fr. (yes, only
> on
> > > port 80!) for a cheep price. This is to prevent power or ADSL outage
> since
> > > I
> > > moved last year from a big city into a small village.
> > >
> > > My idea for gopherplus.org is to do something like these planet
> websites
> > > using RSS/ATOM feeds to aggregate posts from several personal weblogs.
> I am
> > > looking for somebody fluent in English to receive voluntary posts from
> > > Gopher users, edit these texts (mistakes, typos…) and moderate them if
> > > necessary. An other difficulty is about clock time: we are all living
> all
> > > around the planet, we need some rest, so this task can’t be distributed
> > > among several editors living in different time zones.
> > >
> > > As the goal of this new Internet site is to inform on a large scale
> people
> > > about Gopher, it is absolutely necessary to be on the port 80; it is
> > > necessary too to have a Gopher version of that website as a proof of
> > > concept. More, I think it is important that the port 80 version of this
> > > site
> > > should look like any mainstream websites. (Using graphical chart like
> those
> > > websites owned by geeks or activists could ruin our credibility!)
> > >
> > > Today, gopherplus.org is a simple static website powered by a soft I
> > > wrote.
> > > My blog engine is a replacement of Nanoblogger blog engine wrote in
> Bash. I
> > > did, in the a past, a converter (nb2gopher) to provide Gopher menus
> > > (translating HTML posts into plain text using the “dump” option of
> Lynx)
> > > from Nanoblogger. For the present time, I am rewriting fBlog because
> > > Fortran
> > > programming is in strong progress. I plan, in the future, to have fBlog
> > > playing 70 port. This is a huge task because I want to code everything
> by
> > > myself even for Markdown support. In fact, I don’t have choice
> according
> > > there not libraries available for Fortran outside intensive computing.
> But
> > > for the person accepting to steer gopherplus.org, the choice of the
> > > software
> > > is up to him!
> > >
> > > There is no urgency, I am waiting for any offer posted to my mail box
> for a
> > > while.
> > >
> > > I am also writing an introduction what about what Gopher is that I will
> > > publish on this site. Soon, I will ask you to verify this text!
> > >
> > > -- deber
> > > _______________________________________________
> > > Gopher-Project mailing list
> > > Gopher-Project at lists.alioth.debian.org
> > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
> > > _______________________________________________
> > > Gopher-Project mailing list
> > > Gopher-Project at lists.alioth.debian.org
> > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
> > _______________________________________________
> > Gopher-Project mailing list
> > Gopher-Project at lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20160128/3b81a7ef/attachment-0001.html>