Re: Retaining Nightly users after disabling of legacy extensions

2017-08-26 Thread sime . vidas
Fwiw, after Adblock Plus stopped working, I switched to Ghostery. I also have Firefox’s Tracking Protection on at all times. I am confident that these two tools in combination keep me safe while browsing. ___ dev-platform mailing list dev-platform@lists

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-24 Thread Jorge Villalobos
On 8/24/17 2:08 AM, Andrew Swan wrote: > On Thu, Aug 24, 2017 at 12:03 AM, Alessio Placitelli < > aplacite...@mozilla.com> wrote: > >> 2017-08-24 0:00 GMT+02:00 Andrew McKay : >>> The recommendations are being populated and other changes are being >>> made. For example, on September 1st only WebEx

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-24 Thread Andrew Swan
On Thu, Aug 24, 2017 at 12:03 AM, Alessio Placitelli < aplacite...@mozilla.com> wrote: > 2017-08-24 0:00 GMT+02:00 Andrew McKay : > > The recommendations are being populated and other changes are being > > made. For example, on September 1st only WebExtensions will be > > featured on AMO (as oppos

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-24 Thread Alessio Placitelli
2017-08-24 0:00 GMT+02:00 Andrew McKay : > If an extension updates to a WebExtension, users will automatically > get that update. > > If the author or another author creates an alternative then a user > will have to find that. > > The recommendations are being populated and other changes are being

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-23 Thread Andrew McKay
If an extension updates to a WebExtension, users will automatically get that update. If the author or another author creates an alternative then a user will have to find that. The recommendations are being populated and other changes are being made. For example, on September 1st only WebExtension

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-23 Thread Chris Hutten-Czapski
For those interested, preliminary data shows a continuing increase in the Nightly population since 57. The number of users using Nightly 57 on August 17 was the highest number of users on any day on any Nightly version since... well, our data retention policy cuts out at 6 months, so since at least

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-14 Thread Andrew Swan
On Mon, Aug 14, 2017 at 6:16 AM, Honza Bambas wrote: > Ed already mentioned that the addons manager doesn't automatically suggest > or even update to webext alternatives. We really should have something > like this SOON - the more automatic or fluent the better. There is a "find a replacement"

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-14 Thread Honza Bambas
On 8/13/17 6:42 PM, Ed Morley wrote: For the short term, Nightly users therefore have the following options: a) Use latest nightly with legacy extensions disabled, and make do without their extensions. There is also a2): find webext based alternatives "by hand" (what I have done and intend to

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-14 Thread mlopatka
This is not a specific solution for Nightly users, but I thought that it should generally known that we are working on a solution for when the same problem occurs with Release channel users. The TAAR (telemetry aware addon recommendation) project will use legacy addon information to prioritize

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-13 Thread Daniel Veditz
Don't do (c) -- its pointless. You won't be helping us test nightly changes and will miss any important fixes (especially security ones). Go ahead and switch to beta if you have to. Your extensions will work, you'll be helping us ship a good 56, and you'll get security fixes. Hate to lose nightly t

Retaining Nightly users after disabling of legacy extensions

2017-08-13 Thread Ed Morley
Some context: - As part of Firefox 57 no longer supporting legacy (non web extension) add-ons, the `extensions.legacy.enabled` preference was flipped to false in the Aug 11th Nightly build [1]. - Several backwards incompatible changes have already been made to Nightly that can break legacy extensio