On 2/1/12 4:16 PM, Sean Colyer wrote: > Replacing FireGPG was one of my motivating factors for starting work on > gmail-crypt. I still see that as an end goal. > > I know a few other people who might be interested in helping drive this > to completion. What kind of support would RFA be willing to offer? I > would also need to know more about the expectations for services. A > couple of questions to consider: > > Webmail vs Messaging > Webmail services are all different but similar (we can grab message > content, email addresses from the composition page which is exclusively > for sending). > Messaging services are a bit different -- I'm not sure if this is > intended to be facebook chat (which is essentially XMPP wrapped in a > browser sessions -- OTR could be a better fit for this than OpenPGP) or > facebook messaging. Facebook provides an API that allows us to read > messages externally but not one to write. The reason an API would be > useful here is that facebook is constantly changing their page, and > batch testing is constantly happening on different users. This means it > is harder to use a content script in the same style we can use it for > the more established web mail services.
How much of the logic currently implemented in the chrome plug-in is "cross-browser" and/or easily to be abstracted to be implemented with browser-specific hook? > Chrome/Firefox > Our development has so far focused on chrome -- it's easier to focus on > getting one extension working properly. What would be the expectations > for multi browser capability? That's a nice question, about the plug-in strategy how much "javascript-only" can they be? Which is the technological stack to make a plug-in available on almost all browsers? Does the concept of firebreath make sense to have a "thin-layer" that provide cross-browser support to integrate a fully-javascript engine? http://www.firebreath.org/display/documentation/FireBreath+Home webpg-npapi is using NPAPI provided by Firebreath to make it cross-platform: https://github.com/kylehuff/webpg-npapi I just don't know which are the "browser-dependant" part for: - Firefox - Chrome - Internet Explorer - Opera? Or we may want to target only power-user-oriented browsers such as Chrome/Firefox? -naif _______________________________________________ gpgtools-devel mailing list [email protected] Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-devel Unsubscribe: http://lists.gpgtools.org/mailman/options/gpgtools-devel/[email protected]?unsub=Unsubscribe&unsubconfirm=1 This email sent to: [email protected]
