# declarativeNetRequest in Firefox?

**URL:** <https://discourse.mozilla.org/t/declarativenetrequest-in-firefox/35347>\
**Category:** Development\
**Created:** [January 23, 2019, 2:11pm UTC](https://discourse.mozilla.org/t/declarativenetrequest-in-firefox/35347 "2019-01-23T14:11:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![juraj.masiar](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/juraj.masiar/32/30587_2.png) [@juraj.masiar](https://discourse.mozilla.org/u/juraj.masiar)\
**Post date:** [January 25, 2019, 9:15am UTC](https://discourse.mozilla.org/t/declarativenetrequest-in-firefox/35347/2 "2019-01-25T09:15:36Z")

</div>

I think we are safe here. There is just no way the most popular add-ons of all times would just disappear.

From what I can see, the worst case scenario is that one add-on will have a limited filters amount, so instead of installing one adblock with multiple filters, you will install multiple addblocks, each for a specific filtering.

Also people comparing this with Firefox 57 add-on “Armageddon” are not correct, since as an add-on developer I can see the benefits of Webextension API and I know this was just necessary step towards brighter future 🙂.  
Similarly comparing this with Play Store removing adblocks is also not good since Android has no real competition that allows adblocks so they can do whatever they want.

---

_[View the full topic](https://discourse.mozilla.org/t/declarativenetrequest-in-firefox/35347)._