Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LMMS Sharing Platform (LSP) content license issues (copyright, trademark) #277

Open
qubodup opened this issue Sep 13, 2019 · 7 comments
Open
Labels

Comments

@qubodup
Copy link

qubodup commented Sep 13, 2019

Hello, LSP is great! Unfortunately it hosts some copyrighted content:
https://lmms.io/lsp/?action=show&file=15389 (megaman trademark/copyright)
https://lmms.io/lsp/?action=show&file=15394 (billie eilish copyright)
[edit] https://lmms.io/lsp/?action=show&file=15370 (galantis copyright)

Some suggestions as food for thought:

  1. Make by-nc-nd default, so that people who don't pay any attention to license at least don't upload a license that encourages commercial use/remixing - actions that might lead to legal trouble to people downloading from LSP and believing the license
  2. Reduce the number of license options for new uploads while keeping old licenses (freesound did this to sampling+)
  3. Add some kind of explanation(s) to the license choice section
  4. Create a copyright report/moderation system
  5. Delete copyrighted content(?)
  6. Add a "fanart/unlicensed cover option (either as license or in addition to license - the latter is how blendswap does it)

The hope here is that these steps let LSP downloaders can more safely to remix without having to worry about infringing on 3rd party rights.

For reference, current license options:
image

@liushuyu
Copy link
Member

Hello, LSP is great! Unfortunately it hosts some copyrighted content:
https://lmms.io/lsp/?action=show&file=15389 (megaman trademark/copyright)
https://lmms.io/lsp/?action=show&file=15394 (billie eilish copyright)
[edit] https://lmms.io/lsp/?action=show&file=15370 (galantis copyright)

This really subject to the jurisdiction as some jurisdictions may classify these under fair-use for their transformative work.

Make by-nc-nd default, so that people who don't pay any attention to license at least don't upload a license that encourages commercial use/remixing - actions that might lead to legal trouble to people downloading from LSP and believing the license

Well CC-BY-NC-ND is much more strict than CC-BY and it forbids remixing/deriving and commercial use of the licensed work.

actions that might lead to legal trouble to people downloading from LSP and believing the license

I don't understand this statement. So are you saying that the people who uploaded their work does not actually agree they licensed their work under said license?

Reduce the number of license options for new uploads while keeping old licenses (freesound did this to sampling+)

Probably. But LSP is not actively developed at this moment AFAIK so making someone to implement a change might be difficult.

Create a copyright report/moderation system
Delete copyrighted content(?)

The system you are describing is a DMCA takedown system I think.

Add a "fanart/unlicensed cover option (either as license or in addition to license - the latter is how blendswap does it)

I am not sure about this one, unlicensed is more problematic in some jurisdictions since these will be automatically recognized as "all rights reserved" work.

@Spekular
Copy link
Member

Spekular commented Sep 16, 2019

@liushuyu regarding

actions that might lead to legal trouble to people downloading from LSP and believing the license

My understanding of the proposal is that a more restrictive default license mitigates the effect of people uploading content they don't have the right to.

  • I upload a remix of a song that I don't have the rights to
  • I ignore the license dropdown because I'm not familiar with or don't care about licensing
  • Scenario 1: The default license is "CC-BY". Anyone who comes across my remix thinks they can use it however they want with accreditation. They could make commercial use of it, not realizing that they don't have the right to do so.
  • Scenario 2: The license is more restrictive, perhaps even all rights reserved. People who see my remix and follow the license won't make derivatives, so the number of unlicensed works stays at 1.

Basically an unrestrictive license could lead to more unlicensed derivatives of copyrighted content.

@Spekular
Copy link
Member

I hit "submit" too early, but I've completed my earlier comment now via edit.

@Umcaruje
Copy link
Member

I don't think we should determine what is copyrighted and what is not, and delete content on our own. We should though state that we comply with the DMCA and maybe have a seperate email address for these infractions. If we get a DMCA takedown request for a file and it turns out to be copyrighted material, only then should we remove it.

@tresf
Copy link
Member

tresf commented Sep 17, 2019

Copyright (especially electronically, on mass) is a slippery slope. All points made are valid, but what I consider to be most interesting is the idea of a user clicking the checkbox that says "I own this and have the right to upload" when it's a bit more gray.

In the case of these tracks, the slippery slope comes in the downstream licensee. It's really not useful to claim the tracks uploaded to the LSP violate a copyright. As @liushuyu has pointed out, they fall under fair use since they give accreditation and don't try to pass off someone else's work as their own. (Yes, popular musicians can lose this battle, but it's nearly always when they DON'T give accreditation, "Bittersweet Symphony" being one famous exception, which was finally reversed this year and now it's their own work)

The loophole is created by the licensee. Anyone downloading this content can claim they're doing so under the license terms, so if a suit comes of it, they'll try to argue they were in compliance with the author's license.

Fortunately, judges are allowed to judge people and actions, and in the case of the listed tracks, each track is accredited by title and I'd be surprised to see a judge find either 1. Us (LMMS) or 2. Them (track authors) responsible for a violation. The license provides weaker information than the track title.

So what do we do? Well, the best is to fix the platform to embrace, but warn about this scenario.

  • by-nc-nd - I feel strongly, no. We're trying to move to CC0 to free our users of licensing restrictions, not encumber them. I feel strongly that that's in the wrong direction. Furthermore, masking ignorance with ignorance is just embracing some form of responsible licensing over these tracks. by-nc-nd is just as inaccurate as "common public license".

I feel we should embrace better moderation of the platform and we're open to ideas as how to flag these tracks properly without changing the philosophical foundation of what sharing's about.

@tresf
Copy link
Member

tresf commented Sep 17, 2019

Add a "fanart/unlicensed cover option (either as license or in addition to license - the latter is how blendswap does it)

👍

Add some kind of explanation(s) to the license choice section

👍

Reduce the number of license options for new uploads while keeping old licenses (freesound did this to sampling+)

👍

Create a copyright report/moderation system

👍

I'd like to note, all these ideas involve editing the lsp codebase, of which is not well maintained. We would be happy to accept PRs to enhance the platform. It was written by the original author of LMMS many years ago and it's just a ~~bunch ~~ very small number of volunteers keeping it going.

@tresf
Copy link
Member

tresf commented Sep 17, 2019

Oh one more thing... I'd like to share a resource that specializes more in this type of problem:

https://ocremix.org/remix/OCR03971

There's no copyright info specifically, instead it says:

Primary Game: Donkey Kong Country (Nintendo, 1994, SNES), music by David Wise, Eveline Novakovic, Robin Beanland

@Umcaruje Umcaruje added the lsp label Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants