After talking to Claude 2 there are a few potential things
------------
There are a few things that could potentially trigger tracking blockers on this page:
- Google Analytics (gtag.js) - The Google Analytics tracking code at the top of the page will be blocked by many ad blockers and privacy extensions.
- External asset links - Links to JS files hosted on external domains like jszip.min.js and FileSaver.min.js could also trigger warnings in some cases.
- Fetching remote text files - The code that fetches text files from js/Icons/ and js/Backgrounds/ folders could trigger blocks if those are on an external domain.
- externals links - Any links to external sites like the MediaFire download URL or links in the generated HTML could also trigger warnings.
Some things you could try to avoid issues:
- Use locally hosted versions of external libraries instead of CDNs when possible.
- Proxy remote requests through your own server instead of accessing them directly from client.
- Disable or anonymize Google Analytics tracking.
- Clearly communicate why any external requests are needed (e.g. hosting costs, content sources etc).
- Limit external links to only necessary destinations.
- Implement a service worker to cache and serve some of these requests locally after the initial load.
- Detect ad blockers and gracefully handle blocking of certain functionality.
Overall it's a balance of providing a smooth user experience while limiting unnecessary external connections that might trigger blocks. Hope this gives you some ideas on things to look out for! Let me know if any part needs more clarification.
---------------
Very fustrating