| > there's a replicated consensus of all this attributions. Every single company agrees and has a shared database of the rights and the licensing. Riiight. They can't agree on a standard describing their music and licensing now. But blockchain will magically create that shared database out of thin air. BTW. Again. That same word, database. Nothing a relational database couldn't handle with much more ease and efficiency. > there's not necessarily a need to have a middle man managing this informations and agreements Riiight. Because every single company will provide an up-to-date complete information with no omission and mistakes. Magic of blockchain! > you have this immutable record of when songs were released, who held their records, who and when licensed them, etc. Riiight. Because there's not even a consensus on what to define as a song, it will somehow magically be solved by blockchain which will automagically identify and attribute eve ry song/track/music correctly, completely, and without omission. Just some brain teasers for you: - is a single in Europe the same song as the same single released in Japan? - the single in Japan is 12 seconds longer, though. - The authors and the singer are the same. The publishers are different. - There's the same song, with the same people + a different drummer released two years later. Is it the same song? - All three variations appear on fifteen different albums in 7 different countries, spanning 4 major and 5 regional publishers. - Oh. I forgot to say, it's the same classical Tchaikovsky music which is in the public domain. Yet surprise! You still have to pay money (you may research why as a part of your answers to the brain teaser). - Also, the global and regional distribution, performance, streaming, and radio rights may or may not be be different for each of those. > ny interested party can join and get the information it wants without needing APIs Because blockchain is a magical technology that transmits all this information directly into your brain without the need of APIs. Also, the article you linked is a bunch of demagoguery with zero practical applications that for some reason equates blockchain with TCP/IP and not, let's say, Tamagotchi. |
It won't, and it's a strawman you are setting up. Of course you have to design your business logic and rules and answer all the questions. There's nothing a blockchain, a relational or a nosql database will do for you there. They will give you different options and different tradeoffs. The point here is that this distributed solution has interesting trade-offs and opportunities that makes this a good match for this particular problem, regardless of rules of what defines a song or how licensing rights rules are defined.
> BTW. Again. That same word, database. Nothing a relational database couldn't handle with much more ease and efficiency.
Yes, sure. You can have a third party with a central relational database that does all that, and all companies trust it. The proposed solution is more akin to a relational database replicated between all interested parties. All the parties having the same vision of immutable data allows interesting tradeoffs for this particular problem, that's all. No one is claiming it will identify or classify songs for you.
> Because blockchain is a magical technology that transmits all this information directly into your brain without the need of APIs.
No, because you can design a solution where any interested party can join the network and have a copy of the data. Or not. Trade-offs.
> Also, the article you linked is a bunch of demagoguery
I think it's a very pratical way of understanding the oportunities and capabilities that open up with new technology, particulary if you have a knee-jerk reaction such as shown above. Scepticism is healthy particularly given all the hype and magical promises around it but if you look at it through the framework proposed there I hope you can see how it opens design space that was unpractical before.