Skip Navigation
The graying open source community needs fresh blood
  • When I read code under GPL source and write something like that under a different license, I'm legally liable for copyright infringement. Of course the original owners need to prove it first, but still there's problems from that.

    Neat. But if you create your own version based off what you read that's fine. You can't copy it, but you can learn from it.

    I can read the Linux source code and use it to create my own compatible kernel.

    Some open source projects outright disallow you from contribution if you tell them you're working on a closed source competitor.

    So? They can refuse submissions to their code but they couldn't stop you from using what you see to create your own product.

  • Everything wrong with DroidCam and how to solve it
  • This is sooo verbose.

    TLDR:

    1. Install the latest droidcam from github
    2. Install the latest v4l2loopback from source

    And you never mention what problems this solves.. I use the package manager version of v4l2loopback and have no problems, and it auto updates. And I would use a package manager version of droidcam for the same reason.

  • A strange "terminal emulator" idea I got, tho I bet this exists
  • I mean, there are already tons of applications that lets you e.g. update, like apt update/upgrade does.

    Bingo.

    while apt is good on this front.. what about the CLIs whose --help gives hundreds of lines?

    Read them. There's a reason some programs have many options. Avoiding the CLI isn't the solution.

  • Monolithic setup vs dedicated devices
  • Kubernetes is super easy with k3s and easier to maintain than Docker

    I don't think I've ever heard anyone say this... Kubernetes is a massive pain in the ass to learn, maintain and troubleshoot. If you find it easy that's great, but it's not for everyone.

  • Restart an OOM killed docker automatically
  • It's fairly obvious I feel.

    You're saying rather than use a system tool that does the exact thing that you want you should bodge together a cron job that accomplishes your goal but doesn't actually do what you want.

    Like say you want to stop the docker service for some reason? systemctl stop docker will do that. Then your cron job will restart it. That's not the desired outcome. You want the service running IF the service SHOULD be running. Which is a different thing than "always running". And its' exactly what you get for free with systemd without any silly custom BS.

  • InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AT
    atzanteol @sh.itjust.works
    Posts 0
    Comments 1.7K