• lad
    link
    fedilink
    English
    442 days ago

    The screenshot seems to violate the licence it contains.

    • @Klear
      link
      English
      492 days ago

      There is no screenshot. You are imagining it. Fuck you and your screenshot!

      • lad
        link
        fedilink
        English
        92 days ago

        Oh, that explains it. Well, I imagine a license that also forbids people to imagine it. Fuck you and your imagination

        • @Klear
          link
          72 days ago

          Yeah, I imagine.

          Fuck.

  • @otacon239
    link
    802 days ago

    Sadly, this has the same issue as the DO WHATEVER THE FUCK YOU WANT license because it doesn’t protect the creator from liability. Otherwise, I always love these parody licenses.

    • @db2
      link
      152 days ago

      WTFPL rules. 🤷

  • @db2
    link
    532 days ago
    $ sudo ./gaslight.sh
    
  • @RustyNova
    cake
    link
    28
    edit-2
    2 days ago

    I’m going to burst your bubble but GitHub doesn’t allow non open source licenses on public repositories.

    Just ask winamp lol

    Edit: not open source, but at least forkable and viewable

    • @[email protected]
      link
      fedilink
      12
      edit-2
      2 days ago

      Winamp had a bunch of other issues with code they didn’t own being stuck in that repo. Github encourages FOSS licenses, but doesn’t require it.

      https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

      You’re under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.

      If you publish your source code in a public repository on GitHub, according to the Terms of Service, other users of GitHub.com have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see “Setting repository visibility.”

      • @RustyNova
        cake
        link
        22 days ago

        My bad! Said open source instead of forkable + viewable. Derp is me

    • qaz
      link
      English
      22 days ago

      I’m not so sure about that

  • @nialv7
    link
    52 days ago

    what you gonna do if I do view your code? revoke my license?

  • @finitebanjo
    link
    272 days ago

    Is there a name for this license framework?

    FU License?