A place to discuss all things Interledger
He Simon. Sorry for missing this question. In short: you don't need a new CC license to do this. The right combination/selection of CC licenses will do the trick.
But: do you have any ideas about embedding the payment pointer in the actual music file? And (advocate of the devil) how easy would it be to detach the payment pointer and replace it with another payment pointer resulting in "paying the wrong person"?
my email address: firstname.lastname@example.org
It’s pretty trivial to remove/replace a pointer. I was thinking along the lines of “you can embed this via these means”, as opposed to more permissive things. Reusing to soundtrack a video would be difficult, too, though @antoniotalarico
and the @kendraio folk could maybe help there...?
This is a bit of a tricky thing to do and, from what I know, you need an extra level of abstraction to pull it off. I've been thinking about it too an, to me this is the perfect use case for Paystring potentially. With the idea that an TrackID (possibly generated through ISRC/ISWC if registered) gets linked to a payment pointer and therefore creating a new clause. It would look something like: Paystring = TrackID + Payment pointer.
So far, we've managed to dynamically "swap them" as you play, but it's more of a good work around to the limits of having a payment pointer restricted in a metatag. The "trigger" of a track becomes the attribution to its play button as to make it look like they're linked, but aren't really.
Hope this helps.
“you can embed this via these means”.. ok, I hear you. The answer is not black or white. Even within the open licensing communities you will find multiple answers. The core feature of Creative Commons of course is the "allowed to share" mentality. So we think our glass is half full / most people are good people.
On top of someone's copyright is an agreement (the CC License) asking you to respect the rightsholder's wishes and allowing you to do certain things with the copyright protected work e.g. download, share, build upon, monetize etc.
But that's part of the story. If hundreds of thousands of people download music on your website, do they understand what is allowed and what isn't allowed without additional consent? And in this case I am talking about rightsholders who are not playing with WM models yet.
But now you want to add a WM model to a downloadable song. So on top of the CC conditions you are applying a fair revenue model based on a payment pointer. So misusing the CC conditions is illegal and replacing the payment pointer is illegal or in many cases unfair. But again, there are totally legal examples like: download a CC BY licensed song with the original creator's payment pointer embedded. Replace the payment pointer with your own payment pointer, keep the attribution part in tact (crediting the rightsholder) and upload / monetize the song to your favorite platform. Totally legal.
One (technical) solution is to connect fingerprinted assets (songs) and payment pointer(s) with the unique verified rightsholder ID. There are multiple scenarios out there, they are not a one-size-fits-all solution. However, rightsholders should be and stay in control to decide the licensing terms, monetization model and the level of protection.
From a psychological perspective there is nothing new happening here. Most creators are very proud at first when their creations are shared and their audience is growing. But when the artist finds out someone else makes (more) money from his/her music ... that's the moment when the lawyers are contacted.
And there are always smarter people out there who like to test your (security) system. Here is an example of YouTube and RIAA using MD5 hashing to follow music files online while others just publish a script to download the YouTube file and delete the MD5 information:
Anyway, I don't want to return to the bad old days of blocked content / DRM so let's work on fair WM models and keep faith: most people are good.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
For further actions, you may consider blocking this person and/or reporting abuse
A place to discuss all things Interledger