• 0 Posts
  • 199 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
    7 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.


  • The process is supposed to be sustainable. That doesn’t mean you can take one activity and do it to the exclusion of all others and have that be sustainable.

    Edit:

    Also, regretably, I’m using the now-common framing where “agile” === Scrum.

    If we wanna get pure about it, the manifesto doesn’t say anything about sprints. (And also, you don’t do agile… you do a process which is agile. It’s a set of criteria to measure a process against, not a process itself.)

    And reasonable people can definitely assert that Scrum does not meet all the criteria in the agile manifesto — at least, as Scrum is usually practiced.


  • It’s funny (or depressing), because the original concept of agile is very well aligned with an open source/inner source philosophy.

    The whole premise of a sprint is supposed to be that you move quickly and with purpose for a short period of time, and then you stop and refactor and work on your tools or whatever other “non value-add” stuff tends to be neglected by conventional deliverable-focused processes.

    The term “sprint” is supposed to make it clear that it’s not a sustainable 100%-of-the-time every-single-day pace. It’s one mode of many.

    Buuuut that’s not how it turned out, is it?




    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.







  • The author seems to have fallen for two tricks at once: The MPAA/RIAA playbook of seeing all engagement with content through the lens of licensing, and the AI hype machine telling everyone that someday they will love AI slop.

    He mentions people complaining that stock photo sites, book portals, and music streaming services are all degrading in quality because of AI slop, but his conclusion is that people will start seeking out AI content because it’s not copyrighted.

    Regardless… The position of those in power has not changed. They never believed in copyright as a guiding concept, only as a means to an end. That end being: We, the powerful, will control culture, and we will use it to benefit ourselves.

    Before generative AI, the approach was to keep the cultural landscape well-groomed – something you’d wanna pay to experience. Mindfully grown and pruned, with clear walking paths, toll booths at each entrance, and harsh penalties for littering or stepping on the grass. You were allowed to have your own toll-free parks outside of the secure perimeter, that continue the walking paths in ways that are mutually beneficial, as long as visitors don’t track mud in as a result.

    But now? The landscape is no longer about creating a well-manicured amusement park worth the price of admission. There’s oil under the surface. And it’s time to frack the hell out of it. It’s too bad about the toxic slurry that will accumulate up top, making the walled and unwalled parks alike into an intolerable biohazard. There are resources to extract. Externalities are an end-user problem.

    Yeah, turning culture into an expensive amusement park was a horrible mistake. But I wouldn’t get too eager to gloat over seeing the tide of sludge pour over their walls. We’ll still be on the outside, drowning in it.