I’ve spent the last week lurking this forum and I’m happy to see how many people are as excited as myself to build solutions for the broken parts of the music world. In the era where high quality engineering isn’t the moat, what matters is gonna be communities and good ideas, and we have both!
The biggest realization we had while cooking up tangle.music, is that the music collecting world needs a common base for all of us to build on top of.
Here’s what my friend Prakhar wrote up about it, the working copy of the spec is here.
If we make it easy for all the emergent apps to talk to each other and for users to play with them, we can create a wild ecosystem. That’s the only way to experiment and find the right solutions (or a combination of them) that are fair to artists and convenient (to the right point!) for the fans, whether our individual projects succeed or not.
The above spec may even become useless as integrating with an API starts costing few tokens, but we must all build those APIs. They should be straight-forward, and expose most operations (especially purchasing and streaming).
If any of you want to play and help iterate on it please post or reach out directly!
We’re all very excited and fully committed to tackle this problem, and I’m looking forward to any candid feedback.
N.B:
-
I’m not native to the fediverse and I’m now learning how it works, what problem it solves, and how it fits into the vision of solving the platform-agnostic music collection problem. To do so I’ve fully integrated support for OpenSubsonic in Tangle (super interesting to see it on equal grounds with other streaming platforms) and built a POC using Chorus for an incoming Inbox feature we’ll work on.
-
The spec has been written iterating together with the best models at the time of writing (Opus and Fable). I suggest you also go through the spec using your favorite model to understand it and challenge it.