Actually, I believe we can have _several_ "update" objects stored in a
_single_ update JSON file (in an array may be? My JSON is not fluent). The
extension then will download the appropriate rulseset, this choice may be
either hardcoded or set via (hidden) prefs.
PROS: Less hassle with signing and
On 06/08/2014 08:14 PM, Red wrote:
> Yan and Jacob and I have been talking about version number strings in
> the update manifest that we've been refining a little bit lately. I
> wrote in my comment on the gist
> (https://gist.github.com/redwire/2e1d8377ea58e43edb40) that I was
> thinking that we
Yan Zhu writes:
> Wouldn't this also be solved by making the ruleset versions sub-versions
> of the releases?
>
> ex: 4.0development.16.0 == first ruleset release corresponding to
> 4.0development.16
Does that mean that you can't update to a new ruleset release without
first updating to the corr
On 06/09/2014 09:50 AM, Seth David Schoen wrote:
> Yan Zhu writes:
>
>> Wouldn't this also be solved by making the ruleset versions sub-versions
>> of the releases?
>>
>> ex: 4.0development.16.0 == first ruleset release corresponding to
>> 4.0development.16
>
> Does that mean that you can't updat
(adding back HTTPS Everywhere list)
On 06/09/2014 10:07 AM, Red wrote:
>
> On 2014-06-09, 2:17 PM, Yan Zhu wrote:
>> Wouldn't this also be solved by making the ruleset versions sub-versions
>> of the releases?
>>
>> ex: 4.0development.16.0 == first ruleset release corresponding to
>> 4.0developme
On 2014-06-09, 2:43 PM, Yan Zhu wrote:
> (adding back HTTPS Everywhere list)
Whoops! I forget that Thunderbird doesn't include the list in the reply
by default! My bad.
> On 06/09/2014 10:07 AM, Red wrote:
>> On 2014-06-09, 2:17 PM, Yan Zhu wrote:
>>> Wouldn't this also be solved by making the rul
On 06/08/2014 08:47 PM, Jacob Hoffman-Andrews wrote:
> Russell,
>
> You're correct that there is no debug flag to build the Firefox XPI.
> Unfortunately, debugging Firefox extensions is kind of a hassle and
> generally involves building Firefox itself from source. I find that it's
> easier to add
Yan Zhu writes:
> We decided in IRC last week that this would be the desired default behavior.
>
> In general, it would be difficult to guarantee that a new ruleset
> version is compatible with *all* previous extension versions. Ex: we
> introduce a new XML property, "hasKeyPins", or change the X
