chamomile

joined 2 years ago
[–] chamomile@furry.engineer 13 points 5 months ago* (last edited 5 months ago)

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

[–] chamomile@furry.engineer 10 points 7 months ago* (last edited 7 months ago) (1 children)

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

[–] chamomile@furry.engineer 0 points 8 months ago (1 children)

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

[–] chamomile@furry.engineer 7 points 8 months ago* (last edited 8 months ago) (9 children)

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

[–] chamomile@furry.engineer 20 points 9 months ago (10 children)

@UrLogicFails I feel oddly mixed about PH's response to these bills. I share their opposition to these laws, but their proposed solution effectively requires locked-down device attestation ala the Chrome proposal from a few months ago, which would... also be very bad. I don't want a world where I can't control my own web browser any more than one where I need to dox myself to view porn.

[–] chamomile@furry.engineer 12 points 1 year ago (1 children)

@elfpie Somewhat tangential, but this sort of thing is why I almost categorically disregard any review that primarily complains about how "rude" staff was. More often than not this seems to translate to "acted in a way not exactly in line with my cultural and generational norms" or "didn't give me exactly what I wanted." Give the underpaid service workers some slack.

view more: ‹ prev next ›