fireflash38

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.

If you select the spell by filtering by spell slot first does that work?

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

Yeah, but then you find out Gith lay eggs, which raises weird questions. Idk, maybe their closest analog is a platypus, which would make them far more adorable if they werent trying to separate your head from your neck so often.

You know what’s cool fanservice? Andor using a Bryar Pistol. You know what’s not cool fanservice? Seeing the same 10 characters again and again and again. Seeing the same bar in an enormous galaxy.

Kenobi at the very least added some linking character development between ROTS and ANH, despite how awkward some of it was. So that I’m OK with.

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.

Plant growth is insane area denial for things that can’t teleport. Definitely have to be careful with fire spells cause the burning ground is so much less useful than restricting movement.