With this fix, you can now nuke the ~/better.fyi/.private/cache folder without impacting future build integrity. (The cache, including rule partials, will be re-created if it doesn’t already exist.)

This is because of a difference in directory nesting level between development and production.

(To debug issue where I am seeing different behaviour on the deployment machine.)

We are no longer generating/using separate data for the app. The blocker list file is generated for the site and used by the app from there.

(We use the content cache to calculate the diff of blocker rule changes between deployments and expose this information in the metadata.json file.)

(Using sets instead of arrays to correctly count changes without duplicates.)

Currently only has the md5 hash of the WebKit blocking rules file.

Update for iOS Launch

See merge request builder!11

As Spotlight is out-dated

We already link to the forum from the support page

Will be used to check for updates by the apps.