Damian Sommer on The Yawhg

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

Contents 3 sections
  1. What brought you out of your usual “let’s make fucked up platformers” style?
  2. How did Emily and you decide to work on a project together?
  3. How was working together?

Damian Sommer did a casual AMA on Reddit recently, about his upcoming game, The Yawhg. I got to ask him a few questions. Here’s what he had to say.

What brought you out of your usual “let’s make fucked up platformers” style?

“I was just kind of tired of them. There’s still one more platformer I really want to finish, (The Clown Who Wanted Everything), but besides that, I’m just extremely bored of them now.”

How did Emily and you decide to work on a project together?

Damian: “We didn’t, actually. We got paired up by Miguel of Spooky Squid Games for an event he was running called Comics vs Games . The idea was to gather up some game developers and comic artists, and pair them up together! Emily and I both like”

How was working together?

Damian: “Everything actually went incredibly smoothly. I’d suggest something, and Emily would just go with it, and vice-versa. I kind of wish there were struggles to report to make things more interesting, but nope!”

From your tweets you’ve been working on it for about 1.5 years, correct? Could you draw a line graph of the progress during that time? Perhaps with important milestones? Bonus if there’s duck-sized horses in the corner.

Damian: “Correct. However, as you’ll see from the following graph, it was certainly not a full-time affair.”

(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.

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