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

help-circle









  • It was a different commenter, though I also like snacking on dark chocolate chips. Baker’s chocolate is also good, but the consistency of the squares isn’t great for snacking.

    I just read it as a tip for how to get chocolate anyways, even if all the chocolate bar makers stop using it. The chocolate-like but cheaper stuff they are using instead of chocolate sounds more like the dustbowl/depression era tricks to enjoy food while you can’t afford it.

    Though part of my perspective is from getting my cooking to a level where store bought prepared stuff is just the easy/convenient option, not the high quality one (for health or taste). I also love dark chocolate and prefer the high cocoa content ones over must chocolate bars.



  • Yeah, I think sucralose is the only one that doesn’t taste awful to me. Like I’ve always been skeptical of the defense of aspartame because it tastes like something I shouldn’t be eating. I was looking forward to stevia back when it got popular, but it also has that taste (I’m guessing from leftover solvent, since it’s not water soluable like sugar).

    There’s plenty of ways to make things taste great without relying so heavily on sweetness. I hate the western food industry’s obsession with it along with the capitalist obsession with selling as much as possible, because it’s resulted in the less sugar I’ve wanted to see instead meaning the sugar is replaced with other chemicals that taste sweet (and “chemically”).

    And I doubt safety studies looked at anything beyond “does it so obviously cause issues that we’ll be sued the moment we try to sell this?”








  • An alternative that will avoid the user agent trick is to curl | cat, which just prints the result of the first command to the console. curl >> filename.sh will write it to a script file that you can review and then mark executable and run if you deem it safe, which is safer than doing a curl | cat followed by a curl | bash (because it’s still possible for the 2nd curl to return a different set of commands).

    You can control the user agent with curl and spoof a browser’s user agent for one fetch, then a second fetch using the normal curl user agent and compare the results to detect malicious urls in an automated way.

    A command line analyzer tool would be nice for people who aren’t as familiar with the commands (and to defeat obfuscation) and arguments, though I believe the problem is NP, so it won’t likely ever be completely foolproof. Though maybe it can be if it is run in a sandbox to see what it does instead of just analyzed.