Terms and conditions

👋 This page was last updated ~3 years ago. Just so you know.

There are no goods or services being sold on https://fasterthanli.me: however, donations are accepted, through Patreon and GitHub Sponsors, and may in the future be accepted directly through a payment processor.

Anyone who is currently subcribed to me on either Patreon or GitHub Sponsors is hereafter referred to as a “sponsor”.

Sponsors may log in to this website using their Patreon or GitHub account and may, occasionally, read articles in “early access”, before they are made available for everyone.

Sponsors may cancel their subscription at any time and for any reason, and obtain a refund for the unused duration of their monthly/annual subscription.

By cancelling their subscription, sponsors understand they immediately lose the “early access” functionalities.

You can e-mail [email protected] if you have questions.

Did you know I also make videos? Check them out on PeerTube and also YouTube!

Here's another article just for you:

Thumbnail for crates.io phishing attempt

crates.io phishing attempt

Earlier this week, an npm supply chain attack.

It’s turn for crates.io, the main public repository for Rust crates (packages).

The phishing e-mail looks like this:

A phishing e-mail: Important: Breach notification regarding crates.io  Hi, BurntSushi! We recently discovered that an unauthorized actor had compromised the crates.io infrastructure and accessed a limited amount of user information. The attacker's access was revoked, and we are currently reviewing our security posture. We are currently drafting a blog post to outline the timeline and the steps we took to mitigate this. In the meantime, we strongly suggest you to rotate your login info by signing in here to our internal SSO, which is a temporary fix to ensure that the attacker cannot modify any packages published by you.
Andrew Gallant on BlueSky

And it leads to a GitHub login page that looks like this:

A fake GitHub sign-in page.
Barre on GitHub

Several maintainers received it — the issue is being discussed on GitHub.

The crates.io team has acknowledged the attack and said they’d see if they can do something about it.