• 0 Posts
  • 164 Comments
Joined 2 years ago
cake
Cake day: July 14th, 2023

help-circle

  • kibiz0r@midwest.socialtoLinux@lemmy.mlShare a script/alias you use a lot
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    1
    ·
    edit-2
    8 days ago

    I often want to know the status code of a curl request, but I don’t want that extra information to mess with the response body that it prints to stdout.

    What to do?

    Render an image instead, of course!

    curlcat takes the same params as curl, but it uses iTerm2’s imgcat tool to draw an “HTTP Cat” of the status code.

    It even sends the image to stderr instead of stdout, so you can still pipe curlcat to jq or something.

    #!/usr/bin/env zsh
    
    stdoutfile=$( mktemp )
    curl -sw "\n%{http_code}" $@ > $stdoutfile
    exitcode=$?
    
    if [[ $exitcode == 0 ]]; then
      statuscode=$( cat $stdoutfile | tail -1 )
    
      if [[ ! -f $HOME/.httpcat$statuscode ]]; then
        curl -so $HOME/.httpcat$statuscode https://http.cat/$statuscode
      fi
    
      imgcat $HOME/.httpcat$statuscode 1>&2
    fi
    
    cat $stdoutfile | ghead -n -1
    
    exit $exitcode
    

    Note: This is macOS-specific, as written, but as long as your terminal supports images, you should be able to adapt it just fine.




  • All of security is about trade-offs. “What does it protect me from, and what do I give up to gain that protection?”

    If you need to remember a lot of passwords, then having some kind of system makes sense.

    But most people don’t need to remember a lot of passwords. Most people can reasonably offload that job to a password manager.

    So without knowing anything more, I’d guess it’s not good security for them.


  • First thought: Damn, that’s crazy they went ahead and did it to get the footage even though they knew how bad it was.

    Then: Well, I guess the fishermen were gonna do it no matter what, huh?

    Wait, aren’t the fishermen worried that this footage could ruin their livelihood?

    Wait… Maybe they believe that the legality of this practice already has ruined their livelihood, and they want it to stop but can’t compete unless regulation forces everyone to stop…


    1. Fuck AI
    2. This judge’s point is absolutely true:

    “You have companies using copyright-protected material to create a product that is capable of producing an infinite number of competing products,” Chhabria said. “You are dramatically changing, you might even say obliterating, the market for that person’s work, and you’re saying that you don’t even have to pay a license to that person.”

    1. AI apologists’ response to that will invariably be “but it’s sampling from millions of people at once, not just that one person”, which always sounds like the fractions-of-a-penny scene
    2. Fuck copyright
    3. A ruling against fair use for AI will almost certainly deal collateral damage to perfectly innocuous scraping projects like linguistic analysis. Even despite their acknowledgement of the issue:

    To prevent both harms, the Copyright Office expects that some AI training will be deemed fair use, such as training viewed as transformative, because resulting models don’t compete with creative works. Those uses threaten no market harm but rather solve a societal need, such as language models translating texts, moderating content, or correcting grammar. Or in the case of audio models, technology that helps producers clean up unwanted distortion might be fair use, where models that generate songs in the style of popular artists might not, the office opined.

    1. We really need to regulate against AI — right now — but doing it through copyright might be worse than not doing it at all


  • It’s the #1 thing that drives me crazy about Linux.

    It seems obvious. You’ve got a Windows/Apple/Super key and a Control key. So you’d think Control would be for control characters and Windows/Apple/Super would be for application things.

    I can understand Windows fucking this up, cuz the terminal experience is such a low priority. But Linux?

    There’s some projects like Kinto and Toshy which try to fix it, but neither work on NixOS quite yet.










  • Meanwhile Nintendo in the 1980s:

    Yokoi’s most enduring contribution may have been his product philosophy, often translated to the almost luddite-sounding ‘lateral thinking with withered technology.’

    The genius behind this concept is that for product development, you’re better off picking a cheap-o technology (‘withered’) and using it in a new way (‘lateral’) rather than going for the predictable, cutting-edge next-step.