[gopher] [Gopher Clients]: Chrome Extension

[James Mills]

On Tue, Dec 16, 2014 at 10:41 AM, Cameron Kaiser <spectre at floodgap.com>
wrote:

> (You don't need to cc me, I read this list.)
>

Sorry :)


>
> The chief problem was the major change in permissions and the manifest with
> Chrome 24. It may not be complex to fix, but I don't use Chrome personally
> for philosophical reasons, and it became more of a headache to maintain
> especially since I never used it (and I have a somewhat solid rule not to
> maintain software packages I don't use myself).
>

Ahh right. I guess I don't have the same philosophical reasons not to use
Chrome (yet) :P
(That may come! But right now I find the usability of FF annoying :/)


>
> Realistically it should be rewritten anyway. There are now apparently ways
> to get a raw TCP socket in Chrome with appropriate permissions, and that
> would be much better than the hacky proxy forwarding method it uses now.
>

Yeah okay fair enough. Maybe I should give this a try :)
I might learn something!

Chrome extensions are written in JavaScript right?

cheers
James

James Mills / prologic

E: prologic at shortcircuit.net.au
W: prologic.shortcircuit.net.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20141216/e2c4f261/attachment.html>