MajinBook: An Open Catalogue of Digitally Mediated World Literature

Making sure you're not a bot!
Loading...
You are seeing this because the administrator of this website has set up Anubis to protect the server against the scourge of AI companies aggressively scraping websites. This can and does cause downtime for the websites, which makes their resources inaccessible for everyone.
Anubis is a compromise. Anubis uses a Proof-of-Work scheme in the vein of Hashcash, a proposed proof-of-work scheme for reducing email spam. The idea is that at individual scales the additional load is ignorable, but at mass scraper levels it adds up and makes scraping much more expensive.
Ultimately, this is a placeholder solution so that more time can be spent on fingerprinting and identifying headless browsers (EG: via how they do font rendering) so that the challenge proof of work page doesn't need to be presented to users that are much more likely to be legitimate.
Please note that Anubis requires the use of modern JavaScript features that plugins like JShelter will disable. Please disable JShelter or other such plugins for this domain.

Facts Only

* The website uses a system called Anubis.
* Anubis employs a Proof-of-Work scheme based on Hashcash.
* This system aims to make mass scraping more expensive.
* The solution is currently a placeholder.
* The goal of the placeholder is to allow time for fingerprinting headless browsers.
* The system requires modern JavaScript features.
* Plugins like JShelter disable necessary JavaScript features.
* Disabling such plugins is required for Anubis to function on the domain.

Executive Summary

The website employs a system named Anubis to protect the server from aggressive web scraping by AI companies. This protection utilizes a Proof-of-Work scheme, similar to Hashcash, designed to increase the cost of mass scraping while keeping individual loads ignorable. The current implementation is described as a placeholder solution intended to allow more focus on fingerprinting headless browsers before presenting the proof-of-work challenge to legitimate users. Furthermore, the system requires modern JavaScript features that are disabled by plugins like JShelter, necessitating disabling such plugins for the domain to function correctly.

Full Take

The dynamic between security, accessibility, and technological resistance presents a tension between operational necessity and user experience. The implementation of Anubis suggests a layered approach: using an economic barrier (Proof-of-Work) to filter out automated bulk activity while reserving immediate effort for more sophisticated behavioral detection (fingerprinting). This structure implicitly acknowledges that the defense mechanism itself is temporary, prioritizing diagnostic work over a polished end-user interaction. The dependency on disabling specific plugins highlights a friction point where security protocols conflict with existing user tooling, creating an external dependency for basic functionality. The pattern suggests an evolving digital arms race where initial, imperfect solutions are deployed to buy time for more fundamental identification methods, reflecting a systemic struggle to balance resource protection against the demands of legitimate access.