Re:Google Talk Syntax Highlighting
by saurik on Wednesday January 30, 2013 @03:59AM
(#5138684)
So, it obviously needs permission to modify mail.google.com, as that's where the Google Chat boxes are that it is messing with. The only other thing it wants is "storage" (which Google considers harmless enough that it doesn't even generate a wanring).
Re:Google Talk Syntax Highlighting
by ldng on Wednesday January 30, 2013 @09:01AM
(#5139464)
Maybe but when I see "All data on your computer and the websites you visit
This item contains an NPAPI plug-in.
Caution: NPAPI plug-ins can do almost anything, in or outside of your browser. For example, they could use your webcam, or they could read your personal files."
it kind of put me off. And I see it on a lot of extensions.
Maybe permissions system is too coarse, I don't know.
I really would like to make it as safe and constrained as possible, but by nature this is working with personal data. I think the best thing I can do is to keep it all open source, think about privacy, and encourage people to read the code as much as possible.
Re:Google Talk Syntax Highlighting
by ldng on Friday February 01, 2013 @04:21PM
(#5153571)
Right, I understand now. I read too fast, my apologies.
Still that link is misleading because it made me feel I was going to have more information on _that_ extension in particular, not a generic page talking about permissions in general.
Now I'm wondering if the android market isn't clearer in show that king of information. Lesson learned, I'll check more carefully next time.
This item contains an NPAPI plug-in.
Caution: NPAPI plug-ins can do almost anything, in or outside of your browser. For example, they could use your webcam, or they could read your personal files."
it kind of put me off. And I see it on a lot of extensions. Maybe permissions system is too coarse, I don't know.
And view all the source code, right here: https://github.com/pehrlich/GTalkSyntax/blob/master/javascri... (This is the one file that does almost all the work)
I really would like to make it as safe and constrained as possible, but by nature this is working with personal data. I think the best thing I can do is to keep it all open source, think about privacy, and encourage people to read the code as much as possible.
Anyway, thanks for having a look!
Now I'm wondering if the android market isn't clearer in show that king of information. Lesson learned, I'll check more carefully next time.
Thanks for correcting me.