On Sunday, June 14, 2015 at 5:31:06 AM UTC-5, Angly Cat wrote: > On Wednesday, June 10, 2015 at 11:11:39 PM UTC+6, Gervase Markham wrote: > > The API Firefox uses is documented in the Firefox codebase: > > > > https://mxr.mozilla.org/mozilla-central/source/browser/components/pocket/pktApi.js > > > > It's not a particularly complicated API AFAICS. > > > > Gerv > > I wonder which part of Pocket(tm) code was made open-source, as some @mozilla > claimed itt. Correct me if I'm wrong, but AFAICS Firefox utilizes Pocket(tm) > API (and so-called "Pocket Marks") only.
According to the code included in Firefox, all of it is under open-source terms except for the trademark/brand pictures (the "Pocket(TM) marks"). According to Pocket(TM)'s terms of service, none of the Pocket(TM) application provides the rights required to satisfy the open source definition. So, it appear the provide the source code as if it is open source and then revoke the rights as soon as it is installed/used based on the terms of service. At the very least, this should put a chilling effect on actually treating it as open source. In terms of it only utilizing the Pocket(TM) API, it depends on what you consider to be the Pocket(TM) API. If that just means it only accesses RPC style calls to Pocket(TM)'s website then you are correct. If, however, you consider the Pocket(TM) API only the calls documented at the Pocket(TM) developer's website then you are very wrong. The Firefox integration currently already uses a private (as confirmed by Pocket(TM) support) call of "/v3/firefox/save" which they have no intention of providing the documentation for. It really doesn't matter how simple this call is as the trend of using private undocumented calls means that future updates to Firefox may use additional private calls such that the "/v3/firefox/*" namespace will continue to grow over time. This will also puts a chilling effect on third-party involvement in maintaining the code since contributors will have to reverse engineer from the code what the new private calls do. The use of a private undocumented namespace will also make a mess of trying to provide compatible private servers. It is possible future updates of Firefox by calling new private namespace or undocumented extensions to the "save" call will break when going to a private protocol-clone server authored by someone that couldn't possibly know what additional calls would need to be supported. So, while doing everything to give the illusion of following open source to the letter, Pocket(TM) is far from following the spirit of open source. _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
