Chamomile 🐑

@KillingAndKindess @alyaza B&J’s have always been quite principled and outspoken about it - they’re also staunch critics of the US prison industrial complex.

@sharkfucker420 It’s a good thing “A Modest Proposal”[1] wasn’t titled “The Benefits of Cannibalism” because I guess people would have taken that at face value as well.

[1] https://en.m.wikipedia.org/wiki/A_Modest_Proposal

@Gaywallet I have a couple thoughts on this:

1. This seems like a way that device attestation could worm its way further into our devices. Right now Google is trying to watermark AI-generated photos as AI, but you could easily go the other way - if a photo hasn’t been manipulated, it’s signed with a key that is locked down to device attestation. What, your phone is rooted? That’s kinda suspicious - how am I supposed to know your photos are real?

2. Short of that, though, I suspect that the most likely consequence of this is the videos will start being increasingly seen as necessary for true proof, since those are harder to fake - for now, at least. And of course, there will be a lot more misinformation on the internet, especially in the short term while awareness of this catches up.

@SPAUZPiMP @scarabic Oh wow, did he literally say “irreducible complexity?” That is SO blatant lol.

@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!

deleted by creator

@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.