Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key but modern and easier to use)

  • 0 Posts
  • 8 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle

  • Shitty job.
    She lied, behaved irrationally, couldn’t get her story straight ahead of time, scenario too implausible.

    You gotta admit fault, hate yourself for killing everyone. Buying poisonous mushrooms is implausible, admit you got them yourself right away, admit accidentally killing them. Swear to never touch mushrooms again.

    And find a better excuse for not poisoning yourself, noone individually prepares mushroom sauce per person.


  • Good deniability though.
    Be publicly into micology and commonly collect mushrooms to cook when you have guests over.
    Only issue would be to somehow plausably not poison yourself to death. Maybe taking little enough you survive.

    And take care you aren’t quite known as fully competent, spread the air of knowledge without any solid proof or association.
    I’ll look like you were a sham and amateur overestimating themselves.

    Or just accidentally run them over with a car.






  • Don’t wanna interrupt your rant, but “determinism and verifiable integrity” doesn’t sound like it’d impede changes.

    Determinism/reproducible builds allow independent verification that a source corresponds to the binaries some repo ships. You can set up most languages, build systems, and environment to be reproducible, and once done it doesn’t have any additional effects, except maybe when changing build procedures you have to maintain the reproduceability.

    “verifiable integrity” to me sounds like computer proof systems. Showing an algorithm/code/program corresponds exactly to some written spec, mathematically.

    The project seems to be positioned explicitly against points of authority and “security” through compliance checks and certifications.