[gopher] Joining in: I'm the maintainer/host of Gopher Proxy

[Bradley D. Thornton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160



On 09/15/2013 01:15 PM, Cameron Kaiser wrote:

> 
> Bug 388195 brings back a lot of bad memories, sigh.
> 
> On the plus side, the JavaScript proof of concept I wrote up (and which
> they ignored) became the first version of OverbiteFF.
> 
> But yes, I agree with Nuno's recollection. The fix was in from the beginning,
> and mitigating factors weren't really part of their analysis. That said,
> that fight would have just been waged later, so moving to OverbiteFF was a
> good thing overall and put the client code in the hands of the community.
> 

Well, I doubt they're going to drop support for ftp:// anytime soon, but
other protocols that prolly *should* be inherent in the browser's core
code require plugins too - for example: irc:// - so I guess this isn't
particular to us.

Still, if they had competent and willing maintainers, and there was no
harm in continuing to support gopher, then I have to wonder what their
agenda was in dropping it.

I see we've already got precedence w/robots.txt too. Thanks guys, for
pointing that out to me :)

Kindest regards,


- -- 
Bradley D. Thornton
Manager Network Services
NorthTech Computer
TEL: +1.310.388.9469  (US)
TEL: +44.203.318.2755 (UK)
TEL: +41.43.508.05.10 (CH)
http://NorthTech.US

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Find this cert at x-hkp://pool.sks-keyservers.net

iQEcBAEBAwAGBQJSNh2JAAoJEE1wgkIhr9j3us8IAKfIdYNExuWGC8agXVjbskVQ
nlaE7TBrBZmU9yZgm5QKsbtiw1oaqNLWpednAqj+hSI8t4mUnlNZEogfJRTwEK4p
mqxMBXIRNYgjK4GfjjTDfgYlS5Ct7JlKm6ZR3U+AB+UfVuuzne5YyfHkUxEjPW1g
3M8PH1qPAbqI4xCCA1+A1ePuRftkawCFvTDcnRvvxfArDGqsLHVlDMO1WDiRZtO+
DYDWdflGrSTjIWcIuAUwRq1x+heZY1GIZ3bsus4/+X8x+P7kNByccqQ2BerfdLco
klpIflcmuxEeja47ayANymvYVn7gZl0343LnxyQaZf7AtrSG9QZBhVv+8fH+tlk=
=Tr3Z
-----END PGP SIGNATURE-----