fireflash38

joined 1 year ago
[–] fireflash38@lemmy.world 6 points 8 months ago (2 children)

Got a source for the majority claim?

[–] fireflash38@lemmy.world 2 points 9 months ago (6 children)

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

[–] fireflash38@lemmy.world 2 points 11 months ago

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.

[–] fireflash38@lemmy.world 1 points 1 year ago

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

[–] fireflash38@lemmy.world 7 points 1 year ago (6 children)

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

[–] fireflash38@lemmy.world 1 points 1 year ago (1 children)

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.

[–] fireflash38@lemmy.world 3 points 1 year ago

And what is the token in the link?

[–] fireflash38@lemmy.world 1 points 1 year ago (1 children)

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

[–] fireflash38@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

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
[–] fireflash38@lemmy.world 2 points 1 year ago

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.

[–] fireflash38@lemmy.world 74 points 1 year ago (17 children)

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.

[–] fireflash38@lemmy.world 6 points 1 year ago (1 children)

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

view more: next ›