[gopher] spreading gopher
I think I'm losing the war on Mozilla bug 388195, the infamous decommission
Gopher bug for Mozilla 2/Firefox 4. In fact, the defeat may be worse than
I had thought because it appears that CPOWs (such as how Jetpacks are
implemented) cannot rewrite content, so even OverbiteFF might not work.
They are conceiving of a reverse CPOW since other protocols have a similar
problem, but the tentative deal Brendan extended in #67 seems to be off.
The worst case scenario has not only core Gopher disappearing, but also any
hope at add-ons. Reverse CPOWs are just concept, they don't exist, and they
might not exist for some time. We need to get Gopher into the core of more
things to continue to infect virally.
I know someone here was thinking of submitting patches to add it back to
cURL. This would be a really great thing. Who was planning on doing that?
There is still kio_slave for Konqueror, but there is nothing for Chrome.
I should try to get my AIR-based client off the ground again. It works,
but it has no real interface of any sort.
We need to get gopher to where people live. Even if we're not the core
part of popular clients, we should still be an option.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- The son becomes the father, the father becomes the son, the uncle has a beer.
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/gopher-project
Reply to: