@whittmann.bsky.social, @saracodes.bsky.social, @stackwild.bsky.social & @webdevour.bsky.social got any idea how that happened? I mean - it's great that you're following along, but I'd be curious how you all found me the same day?

Also why are @github.com actions (especially the automatically scheduled kind) not disabled on forks by default? 🤔

Disabling actions seem to be an easy way to contribute a bit less to the waste of resources on our beautiful globe: See for yourself on github.com/settings/bil...

Reading this I wonder if what we need is actually a standard addendum to open source licenses expressing a non-legally binding but explicit non-enforceable expectation of companies "paying for it"? With explicit and easy to execute instructions to actually get those payments flowing.

The real @seth.blue - I saw some familiar faces following the other account and assumed it was you 😅

@sethwebster.bsky.social this is who you're looking for 👆 Does a lot of amazing visuals for the @automerge.org project. If it's good enough for them it's good enough for the React Foundation 😅

Refreshing 💙 Thanks for sharing *that*.

And that totally happens too 👍 That does require some level of engagement from the "maintainer" though. I've found it hard, as there's not always an updated 1-1 between packages and their author.

(just like @tannerlinsley.com did 😅🧌)

Totally makes sense for some projects 🙂 At the same time, we're cohabiting a global namespace (domain names, NPM package names, GitHub orgs and usernames). If you claim a good one, I'd say you'd better live up to the name. If its just for you and your buddies to hack around, prefix it with you name.

Or come to think about it 🤔 ... I'm the one in need of that link 🙈

You need an affiliate link for that shirt 🎮