Today I got a DMCA notice from Github to take down code for a Chrome extension I forked. Only problem is that the code has always been under the GPL for years. Apparently the original dev now wants money for his extension. Guess he’s now regretting his GPL decision.

The URL to the original repository now links to the company’s website.

  • cadekat@pawb.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 hours ago

    Ugh, reminds me of project babble and eyetrackvr. Went from open source to source available non-commercial.

  • x00z@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    6 hours ago

    It looks like the repo has at least one commit by a user named jellyfith. This might mean that besides being scummy towards forks, the original creator might also be using GPLv3 code written by somebody else, which would be a violation.

    Maybe they’re the one who should get a DMCA notice.

    • Grntrenchman@lemmy.world
      link
      fedilink
      English
      arrow-up
      27
      ·
      6 hours ago

      That’s the power of GitHub. The fork still shows idolize as the author and clearly has gpl3 license (added by idolize). They can change what they want in the original repo, but the fork is covered forever, and ironclad proof of the licensing. If OP’s code is based off this fork, unmodified (of which it’s a fork, also ironclad proof it’s that gpl3 version) then it’s also gpl3. Saaaafe. This should be open and shut on github’s end, just a dumb DMCA report.

  • chunes@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    2 hours ago

    Why even use a service that has the functionality to serve you dmca notices

  • bryndos@fedia.io
    link
    fedilink
    arrow-up
    7
    ·
    6 hours ago

    sounds very “embrace extend extinguish” to me.

    make sure to save all the evidence of GPL in some non-Gated community.