itch.io app timeline 2016

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

I’ve been working on the itch.io desktop app for about a year now, so I thought I’d make a quick recap:

At the time of this writing, the app has been downloaded about 460K times (including updates). Not counting the back-end, the app and its various components are made up of around 100K lines of code (mostly javascript and golang), most of which is open-source.

You’d think after all that I’d go take a nap or something, but the Winter 2016 season is far from over and I couldn’t be more excited about what is still to come.

In the meantime, be sure to check out:

These are both part of itch.io refinery, a customizable toolset for first releases & playtests.

If you have any questions, we’re always listening at mailto:[email protected]!

I’d like to thank my itch.io colleagues, all our testers, translators, and the game developers who adopted the system early and have shown incredible kindness and understanding, taking the “stress” out of “stress testing”!

Talk to you in 2017 with hopefully a lot more bullet points :)

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

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.