Requests matching against the deny list are blocked

[lfilho]

First real release of a usable extension! 🎉

Acceptance criteria:

AAC, I want to access a site with a known tracker and not be tracked

Thoughts on performance

For this MVP we'll probably will go with a simple Set (<= O(n) as per javascript Set specification).
But for the future we need to consider the best data structure and matching algorithm for the deny / allow lists. Imaging they could get pretty huge, we need to consider performing cases like the ones below. But even then we should confirm those assumptions with load tests and some data gathering about how big those lists can realistically get.

• Adding matched trackers to a memory cache -- it's likely a webpage might call a certain tracker endpoint more than once throught their session, so we could avoid parsing the whole deny list and start looking on the cache instead.
• choosing a different data structure other than a set: maybe shard the trackers tld -> domain -> subdomain (similar to a dns lookup); maybe a BST; maybe a Trie?

[lfilho]

For reference: headless automated testing seems to be indeed impossible these days: microsoft/playwright#2172

[lfilho]

Lost some time in here trying to test things locally (both file:// and http:// until I discovered this:

Hence using the great https://itty.bitty.site/ for a quick https:// content provider :-)

[lfilho]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

• v1.1.0
• GitHub release

Your semantic-release bot 📦🚀

[lfilho]

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

• v1.2.0
• GitHub release

Your semantic-release bot 📦🚀