Ideally, site visitors should not need to install any special software nor change any browser or system settings to continue being able to access an overloaded or otherwise inaccessible LibResilient-enabled site, as long as they were able to access it once before.
The project is generously supported by a grant from the NLnet Foundation.
While a number of content delivery technologies exist, these typically require enormous centralized services. This creates opportunities for gate-keeping, and causes any disruption at these centralized providers to become a major problem for thousands of websites.
And if you’re eager to try LibResilient out, the Quickstart guide should help.
Current status and project updates
LibResilient is currently considered beta: the code works, and the API is mostly stable, but it has not been deployed in production and would benefit from real-world testing. During development it has been tested on Firefox, Chromium and Chrome on desktop, as well as Firefox for mobile on Android, but it should work in any browser implementing the Service Worker API.
You can find news about major project-related developments on the blog.
This site does not gather personal data other than what is strictly necessary to serve the content (that is, your IP address and time of your visit). No cookies are set, no trackers (neither third-party, nor self-hosted) are used.
Website logs are imported into a local, self-hosted Matomo instance to generate basic website visit statistics. IP addresses are anonymized beforehand. Log data is discarded afterwards.
No data will ever be shared with any third parties.