I realized there's a pun opportunity.

Instead of NG Meetup they should be called Angular Circles

Barely related but there's a crisis in the UX community because most of them got to a point where they're tired of getting pressured to add one more dark pattern to capture more attention or sales and still remember the early spirit of making things better for thr users and advocating for them.

[⚠️ I'm a troll]

Weird term for polygons.

Here's a stackoverflow on unions of polygons
stackoverflow.com/questions/26...

As my annoyance grew, I started just pasting the error without explanation, especially if its something stupid. It trained on plenty of stupid errors.

Slam dunk.

I once left a pumpkin in the oven for 2 days (it turned off after the preset time passed but I already forgot)

It's still happening on CI side, so if someone gets somewhere in the dependencies of your project or actions you use or their dependencies, they could steal a credential sufficient to publish to npm without going through the step.

That's nice for a large GH org, or if you're doing complex things. It doesn't prevent malware being published when your CI or one of the maintainer gets its/their access leaked.

For larger projects - N approvals required within X hours or 1 veto within 30 minutes to block.

It does do something like that behind the scenes, but regardless, what I'd want is:
1. CI or anywhere - sends a package to registry with existing security
2. The package doesn't become public, instead - maintainers get notified.
3. Maintainers use strong 2fa to approve making the version public

Do treat it like a flow with a token tho. If someone controls your workflow code they can extract that auth too.

The darker shape in that slice on the right, while not healthy for the tree, should make a good looking coffee table if you took a slice and processed it

oh my god

Wow. Glad it ended up mostly slapstick and not harm.

The build looks fun tho.