In my experience, you really want licensing to be on a release basis.

Reply to this note

Please Login to reply.

Discussion

But hey, i hope i am NOT discouraging you. It's dope stuff. I can sort of imagine you put the licesning there to not mess with the existing datamodel. But if y'all can agree on expanding it together, we'll end up with a solid nip! Maybe nostr:nprofile1qqsp0c5gn7aqzqsaqj9p8lgt5yy26vwrsvnzj4rqcg0xn3pl4ra729gppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7kug8ue should be plugged in here too...?💜

i'm all in for licencing per release, will add it to my list, I think nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy8hwumn8ghj7mn0wd68ytnddaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcqyqduwzspfzelx9k6x0lrez0j8cl8rtz0lxvqylk8z2ustnfy76jpzdvclzp has copyright tickbox which can also be extended

Might I suggest we follow the pattern of text structure in .content field for license and don't add another tag? There are no existent concept of license in tags in any Nostra event and we already have clients that does "Credits:" and "Lyrics:".

So I suggest we parse license from the text content:

"License:

Creative Commons CC0"

It means you can't query for a license with the relay. Also if we wanted to do indexing, license names would need to be standardized.

I think license names are standardized. Sure you got some odd ballers, but they're generaöly backed by thorough law text. Licenses are a very commom and battle tested data point. Take a look at the way podcast does it: generally a standardized abreviation and a link to the actual text. Winging it on a licensing can have devastating legal implications.

(I hate everything i wrote in the above note… In my ideal world, everything is public domain because the market is fair enough to foster a fair music market. Until then, i find myself moraly obliged to apply creative commons on everything i do to keep my work from being abused)

I'm fairly new to NIPs so not sure if context is good enough cause anything can be context but then you need to agree on the format of context at the very least. Curios to hear nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy8hwumn8ghj7mn0wd68ytnddaksqgqmcu9qzj9n7vtd5vl78jyly037wxkyl7vcqflvwy4eqhxjfa4yzyr2p7gd take on licences format for tracks/releases

Here is my suggested format of content field, it's how I've implemented it in Nostria:

https://mibo.eu.nostria.app/d8d10b28402e2d816bfc5d4eced06b31852c560559cccb3288f1be6c1120cf5e.webp

cool, makes sense!