Chamomile 🐑

@AVincentInSpace @remington The Lemmy devs are infamously difficult to work with. They’ve repeatedly shown an unwillingness to even acknowledge the existence of the many problems that instance admins face. That has been a big driver in Beehaw’s decision to move platforms, not just because of a difference in political views, and they’ve been pretty open about discussing it. You’re way off-base.

@Templa Codidact seems promising in this space. They have a non-profit organization and run on an open-source (but not federated) platform: https://codidact.com/

@kid TL;DR: If you have a secret variable in your CI/CD pipeline and it’s written to a file that subsequently gets artifacted, anyone who can access that artifact can also read your secret variable.

Feels like a “no shit” moment but I guess I can see how someone could make this mistake in a more complicated setup than the example in the blog.

@remington There are few creators whose videos I will jump to view the instant they drop, and Lemmino is one of them. This is a pretty interesting subject that I haven’t heard of, despite it apparently being quite well-known.

Tbh, Sanborn not being confident/experienced with math and cryptography kinda tracks with his apparent surprise that expert cryptographers cracked a Vigenere cipher in a couple days rather than follow an obscure breadcrumb trail that’s still unclear, even after knowing the key. For me, K4’s enduring mystery prompts comparison to the Zodiac killer ciphers, which ended up being so difficult to unwind not because they were brilliant ciphers devised by a mastermind, but because the author made a bunch of mistakes. Still, at this point it seems likely that Sanborn has checked his work over multiple times, so maybe there really is just some trick that no one has thought of. He’s clearly eager for it to be solved, so we may know in the coming decades!

@solitaire @erev Jesus, I had completely forgotten “tits or gtfo.” Every now and then I get hit with a reminder of how much more pervasive that kind of thing was as little as 10-20 years ago and it throws me for a loop.

@agressivelyPassive You should still clean your kitchen though, that’s my point.

@agressivelyPassive @technom That’s a self-fulfilling prophecy, IMO. Well-structured commit histories with clear descriptions can be a godsend for spelunking through old code and trying to work out why a change was made. That is the actual point, after all - the Linux kernel project, which is what git was originally built to manage, is fastidious about this. Most projects don’t need that level of hygiene, but they can still benefit from taking lessons from it.

To that end, sure, git can be arcane at the best of times and a lot of the tools aren’t strictly necessary, but they’re very useful for managing that history.