Nostr Web Client

nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy8hwumn8ghj7mn0wd68ytnddaksqgqmcu9qzj9n7vtd5vl78jyly037wxkyl7vcqflvwy4eqhxjfa4yzyr2p7gd nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy08wumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jsqgplwuxkt5a8vj5utj6s8tsj8e3wcavc45p4mqmw92qs7wrh5azmys9f0hy6 nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqt79zylhgqsy8gy3gfl6zappzknrsuryc54gcxzre5ug0agl0j32r5td2a

Let's add "licence" and "licence_url" tags similar to "language" and "explict" to allow artists properly release their tracks following CC and copyright standards.

See https://nostrhub.io/naddr1qvzqqqrcvypzqx78pgq53vlnzmdr8l3u38eru0n3438lnxqz0mr39wg9e5j0dfq3qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqqp3kh2umfvvkhgunpvd4hx62pzs3

Reply to this note

Please Login to reply.

Discussion

IggyGolo 1w ago

nostr:nprofile1qy2hwumn8ghj7cnpwdehq6tnw3hkctn0wfnj7qg6waehxw309a3xzumnwp5hxar0dshx7un89a5kucn00qqzq0c34wewydw694xa5htdavh3yvtnga48gk3u545ftgws7ce2gt6qp79uku I've added licences to tracks on https://sunami-mocha.vercel.app/studio/tracks

We just need to standardise it so it can be used in the same way across Nostr Music apps.

set:// 𓁣 🏴 probably 1w ago

nostr:nprofile1qqsp0c5gn7aqzqsaqj9p8lgt5yy26vwrsvnzj4rqcg0xn3pl4ra729gppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7kug8ue implemented it very nicely a couple of days ago. Have you looked at his implementation? I really hope y'all talking with each other. You really want to look up to the bitcoin consensus and avoid the ego traps of solo stipulation a la fediverse. We're early so y'all can both move forward in usnisom AND back pedal to common grounds.

set:// 𓁣 🏴 probably 1w ago

s/usnisom/unison

SondreB 1w ago

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

https://creativecommons.org/publicdomain/zero/1.0/

IggyGolo 1w ago

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.

IggyGolo 1w ago

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.

HoloKat 1w ago

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?

SondreB 1w ago

Perhaps we should use imeta? Someone might start spamming music with bad album arts that user's would want to block and support blurring?

https://github.com/nostr-protocol/nips/blob/master/92.md

IggyGolo 1w ago

This a good idea, need to check how to implement that

IggyGolo 1w ago

Yeah, ive been following your Nostrhub work

IggyGolo 1w ago

yeah, from UI perspective it looks great, I'm just thinking how to manage it on backend

set:// 𓁣 🏴 probably 1w ago

Frontend looks are between people and their cousins. Only the kitchen (backend) create a good time for the whole extended family. 💜🛸

Derek Ross 1w ago

i think that's a find addition. i can add these tags to ZapTrax.