Post

TL;DR: non-SHA256 proof of work support has finally landed after a year of stilted development, many failed attempts, and learning things no mortal should comprehend about browser internals.

One of the cool parts about how this was implemented is that the same binary is executed on both the client and server in lockstep. This means that the code only has to be updated once.

In order to be maximally compatible, the WebAssembly is also recompiled to JavaScript for clients that disable WebAssembly for whatever reason. This prevents the need to have to re-implement all the logic in JavaScript.

This also adds prebuilt #NetBSD binaries, logs when challenges are accepted, cleans up and consolidates the worker code, fixes an edge case in Content-Security-Policy parsing, and more.

30/8/26, 10:22 pm0 reposts2 likes

Packager note: If you build Anubis entirely from source, you will need to add these dependencies to your packaging of Anubis: - rustc v1.80 or later - cargo v1.80 or later - Either wasmtime (any version) or binaryen (version == 130) These are required to build the WebAssembly components.

anubis.techaro.lolPackaging Anubis | AnubisAnubis is a web application written in Go with components in JavaScript. Packaging it should be similar to other applications with the same constraints.

Please test packaging this and if you run into issues, please make sure your packaging follows the updated packaging docs: anubis.techaro.lol/docs/develop...

github.comPackaging issues megathread following the release of v1.28.0-pre1 · Issue #1918 · TecharoHQ/anubisIf you run into issues packaging Anubis after the release of v1.28.0-pre1: https://github.com/TecharoHQ/anubis/releases/tag/v1.28.0-pre1, please leave comments asking for help here.

If you still run into issues, please leave a comment on the packaging issues megathread. We want to help you but can't if you don't speak up! github.com/TecharoHQ/an...