Bluegrass and folk ain’t bad. Modern country on the other hand…

Got a source for the majority claim?

I’d agree more if most docker stuff didn’t depend on running as root.

Your bones. It’s not good for osteoporosis IIRC.

Funny how it always comes out once you ask a few questions.

Now install tools that are only available as github released binaries. And ensure that hashes match for that. Maybe install a tool that needs to be compiled.

Trad bike.

Wait until this guy discovers you can cast away const! Or bypass private/protected with casting.

What if, get this, we put the bash scripts in yaml. And then put it in kubernetes.

There are “daily” quests that you can reroll into scrip rewards IIRC.

There are ways to have passwords transmitted completely encrypted, but it involves hitting the backend for a challenge, then using that challenge to encrypt the password client side before sending. It still gets decrypted on the backend tho before hash and store.

And what is the token in the link?

Define production lol. I’ve used it for a CI cluster for a few years. Have had to recreate it a few times due to database corruption (despite using etcd across 3 nodes).

Honestly Rancher management is more of a pain than manually managing via ansible or something. And swapping to CRI-O backend instead of containerd js a huge pain for Rancher/RKE2, but pretty easy with k3s.

But Google that high? I wouldn’t have expected as high considering Apple (another one who takes a cut of mobile gaming) isn’t.

End-to-end tests are basically non-deterministic state machines. Flakiness can come from any point in the test: bad tests, bad state management, conflicting tests, network hiccups, etc.

Your goal is to reduce every single point of that flakiness. Just make sure you keep track of it. Sometimes flakiness in tests is really pointing at flakiness in the product itself.

Some things that can help reduce that flakiness:

• Dedicated network
• No external dependencies
• Polling instead of static waits/sleeps

Consider that a ‘username+password’ is much harder to ‘revoke’ individually. As in, you can have 3-4 API keys in use, and can revoke any one of them without having to change a password.

You can also change password independently of the keys, or have it linked so keys are revoked on a password change. It also allows traceability as to where accesses are coming from (auditability). If everything is using the same client-id+secret (or usn/pwd), you don’t know which ‘client’ is doing what.

It’s the sort of thing that makes me really, really sad for the people working there. That crazy breakneck pace cannot be good for mental health.

Did you only make it past the first paragraph? Cause you missed the years of scummy shit they’ve done, completely unrelated to politics.

Having played DOS2 with a controller & split screen, it worked just fine.

Slay the Spire is a complete 10/10 for deck builder roguelike.