Repository navigation
Dethrottled 1.4.1 — clearer hardware comparisons and Halonyx style
Dethrottled's showcase now describes the hardware rather than using hostnames, and follows Halonyx's charcoal, off-white and cyan visual style.
- ARM64 edge device: eight cores (four Cortex-A55 + four Cortex-A78), 11.29 GiB OS-visible RAM, Ubuntu 24.04.5.
- x86_64 mini PC: AMD Ryzen 7 5800U, eight cores / sixteen threads, 30.76 GiB OS-visible RAM, Debian 13.
- New hardware comparison graphic; specifications appear alongside benchmark charts. Architecture, recovery and worker diagrams share the same palette and hierarchy.
- Showcase images stay inline without image-only links. Documentation and explanatory reports use architecture/device-class labels; raw capture IDs remain stable for evidence traceability.
This documentation patch also publishes the corrected README on PyPI. Benchmark values are unchanged and refer to the retained 1.4.0 cohort. Application behavior is unchanged apart from version identity and its matching default user-agent string.
python -m pip install --upgrade dethrottled==1.4.1
dethrottled stack up
dethrottled stack statusDocker Engine and Compose are prerequisites. Package installation starts no services. The managed default stack includes the API, browser, SearXNG, Crawl4AI and format worker; media/layout remain optional profiles.
Validation: 631 local tests passed; 67 skipped and two network tests deselected. Ruff, generated HTTP/MCP references, 58 documentation pages, 367 links/image paths, metadata and bundled deployment-source checks passed. All eight graphics were rasterized and reviewed; GitHub preserved fourteen inline image placements and PyPI preserved four README images. The wheel started five ready services and passed 21/21 browser/document contracts plus worker-restart restoration on both native architectures, outside the source checkout. All fourteen checks on the released commit subsequently passed, including macOS/Windows/Python and both native container jobs. The Trusted Publishing workflow completed successfully; attached wheel/source hashes match PyPI. The packaged deployment bundle is byte-identical to the one used for both local native validations.
Complete native CI · Successful PyPI publisher
Post-publication checks passed on the ARM64 edge device using both the actual PyPI package and a fresh v1.4.1 clone: five services ready, 21/21 functional contracts and four-storage worker-restart restoration per route. Fresh optional libraries and full-profile startup also passed; uncached inference workers report initialization honestly. The package-managed default stack is running at 127.0.0.1:8787. Existing mini-PC production services were untouched.
See the attached installation-verification-1.4.1.json for commands, timings, dependency versions, original record hashes and per-case results; native-verification-1.4.1.json contains both native candidate runs.
Live presentation verification also passed on GitHub and the browser-rendered PyPI page: four README graphics, zero image links. A plain HTTP PyPI request received a Client Challenge; the explicit /drive browser read loaded the actual project page. PyPI proxies its image URLs through Camo; decoded sources match the expected graphics. This single-page observation is retained in presentation-verification-1.4.1.json and is not a new general anti-bot benchmark.