Early Access Policy

Content Release Model

When a dual feature is released, there’s:

  • A video on YouTube
  • An article, time-locked for 6 months
  • Optionally, some bonus “companion” code to the article/video

Here are examples of dual features:

The article version is accessible in advance for sponsors/patrons of tiers Silver and above (~10EUR + VAT/month)

The bonus code, (like in the virtue of unsynn) is accessible for sponsors/patrons of tiers Bronze and above (~5EUR + VAT/month).

Six months after the video is released, the article automatically unlocks for everyone.

Generous sponsors are able to buy a time-release for an exclusive article.

This makes the article accessible for everyone immediately, and adds a banner to the article indefinitely to advertise whatever the generous sponsor would like to.

If you’re interested in buying a time-release for an exclusive article, reach out to amos@bearcove.eu directly and we can discuss prices and copy!

For an example of a sponsored early access, check out

(JavaScript is required to see this. Or maybe my stuff broke)

Here's another article just for you:

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.