How does this work without the 'source code' of the tracks being provided - e.g. the Garageband files or Logic files or Reason files or even just the 'stems' (separate audio tracks).
Like its really hard to, say, change the drum pattern on a track if you dont have access to the underlying files that were used to produce it.
Why not? I see music rights as a great use-case for NFTs. The owner of the NFT unambiguously has those rights—however you may define them e.g. exclusive usage rights and sub-licensing rights—and you can trade it like any other good on any exchange.
I just want to point out that the use-case that I was talking about was around music-rights, the one you're discussing is art-works :) but that said,
> If you want to authentify an artistic piece, you can just sign it with a private asymmetric key.
Isn't this exactly what NFT-artwork is though? The difference is that the signature is now in a publicly accessible space, like the ethereum blockchain rather than an email. And you now have the option of selling that artwork forward because, unlike an emailed and signed piece of art, there is only a single NFT.
> NFT is just built on the artificial market for rarity and currencies made of pure energy use... useless.
Every time I've tried to address comments like these, the conversation is less-than-constructive. I'm not sure if it's the backfire effect coming into play, or if there's something wrong with the way I'm presenting my information. Regardless, despite my best efforts it ends the other person saying things like "beanie babies", "cult", or "I don't care", and so I've just stopped trying.
You don't need the blockchain to have a public key.
Https certificates and PGP signatures are some examples perfectly fine without requiring the whole world to make bazillions of hash calculations on your block.
Hey, two quick suggestions, mostly related to the actual beatoftheday.org website:
1) Put some info on your homepage about what this actually does. When I first landed I wasn't sure what the purpose of the website was.
2) Resize your images! For example your header logo is massive and took a good 5+ seconds to download. You have a max-width of 994px, but the image itself is a whopping 14,976px wide!
Some info would go a long way. I'm still not sure what kind of collaboration you are referring to. Are we talking collecting mp3 files? Curating playlists? Or creating music?
There's a link tucked away in the upper right (on desktop) labeled "Info" that explains the site. I agree with you though that at least a sentence or two on the main page would be smart.
I'd like to be able to sort by 'liked' and by 'baked'. If I'm looking for a new track to collaborate on I want to see the ones with the fewest 'baked' ratings.
Also, I'd love for there to be a way to see the full lineage of a given track. Perhaps even be able to fork it if, e.g., I liked what contributors 1, 2 and 3 did, but not #4, I could work off of #3's rendition.
I broke the site 2 days ago by swapping my AWS key... fix coming soon. And I’m having a designer make new mocks for the site, will post before we start building!
Like its really hard to, say, change the drum pattern on a track if you dont have access to the underlying files that were used to produce it.