[kuschku]

That's certainly one approach.

The other approach is that, unless explicit consent is given, people are supposed to be safe.

Nightly is often required because a lot of functionality for developers is only available there, e.g. custom xpi legacy addons even in FF61.

It's nightly or nothing for this, and as a reminder, stable also was affected by CliqZ.

[dotsh]

You are using Nightly "wrong" because of attachment to old extensions that will perish in June when all legacy stuff will be blocked. Nightly is only for testing out new features and it's not intended to be production ready browser... but everyone has an own use case. Yet do not beat them for wanting to change something for the better after using testing technology.

[kuschku]

I'm not using it for "old" extensions.

Even today, every new feature you want to have in the WebExtension API needs to be implemented as a legacy extension providing this API first, then it will get tested, and then it will maybe become part of core Firefox.

The official process to add apis for WebExtensions is to write a legacy extension.

Which is exactly what I'm doing to support my custom extension that replaces the entire history and bookmarking system, UI and toolbars of Firefox, for which I need a custom API.

I suggest you read the wiki on why nightly still supports legacy extensions before judging people.

[dotsh]

I'm not judging I wrote that everyone has it's own use case. My only point is don't use test version if you don't want to be tested or opt-out of it. ;)

[throwawayReply]

You should be using Aurora not Nightly for those features.

[kuschku]

Aurora does, afaik, not allow extending the WebExtension API with a custom legacy extension, this is only available in nightly.