I implemented license similar to "Lyrics" and "Credits", it's just part of the content, parsed from the text there.
License:
NAME
URL (optional)
Not sure if we should add separate tags for this or not? No matter what we end up deciding as a group, I'll update the implementation.
Example:
License:
CC0 1.0
I feel like tags would be better because every licence has a name and can have a link. So both licence name and link can be very strictly defined in terms of format and expected content. Also you can have a list of most used licences so it's more an enum / tag thing to me.
Also I can think of a few use cases quering those tags if let's say you'd like an app or page which displays tracks using certain licence. Let's someone only listens CC music or would like to play CC licenced music in public.
For this reasons I'm less in favour of using content because content is really freefrom. So it's great for lyrics and credits but maybe not licences.
In any case it'd good to get it into NIP. I'm not familiar how it's usually done. nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy8hwumn8ghj7mn0wd68ytnddaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcqyqduwzspfzelx9k6x0lrez0j8cl8rtz0lxvqylk8z2ustnfy76jpzdvclzpcan you update your NIP to capture how licences should be handled? Not a fan of forks.
I tried to update my custom NIP with artist info but it didn’t seem to be updating. Did you work off the one from nostrhub?
Perhaps we should use imeta? Someone might start spamming music with bad album arts that user's would want to block and support blurring?
This a good idea, need to check how to implement that
Yeah, ive been following your Nostrhub work
