At the time [1990s], there was a new breed of web professionals proudly labeled “webmasters.” Part designer, part developer and part evangelist, webmasters held enough esoteric knowledge about the web to manage, edit and create websites, both large and small.
—Jay Hoffmann: The History of the Web, Volume I (2018).

Yes I wanted to be one when I was 14.

I believe that with the advent of AI, we are about to experience a renaissance. AI-augmented developers are operating well beyond the traditional scope of even a full-stack engineer. [...] AI enables and leverages, but the webmaster orchestrates and takes the responsibility.

How phishing attacks are hard to distinguish because even real pages looks suspicious

Here we go again

From other sources:

• Aikido: https://www.aikido.dev/blog/keyv-and-friends-compromised-in-npm-supply-chain-attack
• Bleeping Computer: https://www.bleepingcomputer.com/news/security/massive-chaindrop-npm-supply-chain-attack-infects-hundreds-of-packages/
• Microsoft: https://www.microsoft.com/en-us/security/blog/2026/08/04/chaindrop-supply-chain-compromise-anatomy-self-propagating-worm/#mitigation-and-protection-guidance

Five Rust working groups stance on the AI usage on Rust lang

But it does harm accessibility

FFmpeg toujours l'OG et le GOAT

Some pitfalls and cases where JSON has a default behavior.

Date, BigInt, circular dependencies, undefined property are not preserved and leads to different behaviors.

Serialization executes code and toJSON().

Take care of prototype pollutions (for example a __proto__ property).

There are also optimization with Message Pack that provides a compact ninary representation and CBOR.

Full of great explanations about securing (hardening) Rust code.

• treat panic behavior as part of your API. Decide explicitly whether panics should unwind or abort, and avoid uncontrolled panics.
• enable stricter Clippy lints (such as indexing and arithmetic checks) when panic freedom is important.
• use a panic hook to shutdown gracefully, set reports, cleanup, collect diagnostics and
• sanitize panic (and logging) messages while logging. veil is a good crate for that.
• avoid unbounded recursion. Prefer iterative algorithms or use depth limits.
• releases builds behave differently. They should be accordingly tested.
• audit dependencies with cargo-audit and cargo-deny
• secure allocation (for defense-in-depth when using unsafe code or FFI) with mimalloc or similar. Measure performance before enabling it globally.
• use minimal runtime images if needed (rust distroless). It reduces the attack surface.
• use multi-stage builds with cargo-chef, --locked and proper .dockerignore
• avoid alpine musl lib c as it introduces subtle runtime differences; at least be aware of them.
• use Linux landlock to restrict filesystem access even after compromission
• never run as root unless absolutely necessary. Drop as much Linux capabilities as possible.
• use Miri to detect undefined behavior, invalid pointer usage and unsafe-ode bugs.
• handle SIGTERM/SIGINT properly. Stop accepting new work, finish inflight requests, flush buffers and then exit cleanly
• protect external dependencies (database, API, cache) with circuit breakers so repeated failures don't cascade
• put explicit limits on everything: upload size, request bodies, queues, timeouts, thread counts,
• expose two health endpoints: a liveness probe and a readiness probe. The liveness probe checks if the process is alive at all, while the readiness probe checks if the process is healthy enough to handle traffic.
• Use fuzzing (cargo-fuzz, honggfuzz), coverage (cargo-llvm-cov), unsafe detection (cargo-geiger), and memory-analysis tools alongside Rust's compile-time guarantees.

L'IA est un outil, qui permet une certaine automatisation du métier de développeur.

Un autre discours qui dénonce l'IA et ö

Les promoteurs de l'IA passent leur temps à dévaluer ce que signifie être humain.

Note: leurs arguments peuvent être justifié, si l'IA elle-même est justifié; nous avons vu l'exemple d'AlphaGo jouer au go contre le champion du monde.

Atom has many advantages over RSS. Somehow I still use RSS for most of my feeds.

#idea #project given an RSS feed, search for an Atom feed alternative.

A list of IT projects

A ripgrep dedicated for Rust

Une alternative à Adobe Fill & Sign, plus efficace et légère.

(via https://janlukas.blog/appydroid/mj-pdf)