Old site is cached very aggressively in the browser

[katomm]

The old Gatsby stack had a feature that caused the page to be cached very aggressively. In detail, it is a (local) service that ensures that the page is available even if it is not accessible.

We are monitoring this for a few days and we may consider forcing this update with the information provided on gatsbyjs/gatsby#15623

[katomm]

This issue is fixed in production with #57. That said people need to visit once the new page that will trigger the script that will delete this old worker, for example by sending them to https://cardano.org/research/

[messiisgreat]

Is this issue already fixed?

[katomm]

Technically yes but people need to visit once the new page that will trigger the script that will delete this old worker, for example by sending them to https://cardano.org/research/

[messiisgreat]

That is not ideal and and a bit noisy.