A private fork?

Writing for my future self is all about leaving small nuggets of carefully crafted abstractions, only where they're needed - when extending my old code I get that warm fuzzy feeling of care from my past self ... I left this abstraction for me to enjoy.

This is less the case when AI was involved ...

Super interesting!

You too @adamwiggins.bsky.social! 😎

@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*.