Headscale is the not-vendor-login version of Tailscale.

Sort of. Many tailscale clients you would use with headscale are closed source.

> Why is Github enforcing that decision..

Because at the end of the day, Github is responsible for _their_ runners.

If you want full control, install and use your own runners, which flips the responsibility to you.

> If you want full control, install and use your own runners, which flips the responsibility to you.

It's a bit tedious to have to explain that service providers have certain responsibilities and obligations too. Corporate culture has given bigtech a blank cheque to behave the way they want. That aside, based on the way you framed your reply, let me assure you that I don't trust them with even my projects, much less the CI system or their runner. And time and again, they vindicate that decision. I have posted the full argument as a reply to your sibling comment.

I'm still paying for these github runners. There is also some line between fully dictating which versions of languages and packages you are allowed to use and a managed runner that doesn't get in your way like a control freak.

From a drawing perspective the hat is fairly simple (3-4 lines), looks good and quick to sketch - speed mattered when drawing lots of Smurf’s.

Huh? I’ve used jellyfin on my chromecast for years

Maybe the taller aspect ratio is due to cockpit surfaces being more horizontal or vertical than eyesight..?

Like letters/words painted on the road for drivers to read them.

Take a look at Crystal for types: https://crystal-lang.org/

Crystal is cool but the only thing it shares in common with Ruby is a similar syntax.

If you actually want types in Ruby, you should check out Sorbet: https://sorbet.org/

Do you know if it says anything about restarting them simultaneously or not?

I would think trying to restart engines one at a time would be preferred, over both of them at the same time - or maybe thats not how it works..?

Just from a systems perspective if the actions to restart the engines can be parallelized then they should be; maybe only one engine will start. You don't want the 50% (for 2-engine aircraft) chance that you spend time on the one that won't start before trying the other.

But then you’ll no longer receive any future security fixes by the publisher.

It’s a hard problem to fix, when we can’t trust any publishers in the future :(

And the shortened form, eg. http://127.1/ (for 127.0.0.1)

TIL

or a public one, http://1.1/

They have a really great in-depth blog post describing how they do it: https://tailscale.com/blog/how-nat-traversal-works

This is a fascinating read!

i think they mean headscale's implementation specifics