#chorusprotocol — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #chorusprotocol, aggregated by home.social.
-
Anyway hopefully @fairplayer and @mirlo get their stuff updated too! And then hopefully a whole ecosystem of stuff shows up around these things.
Like my Master Plan involves a #ChorusProtocol aggregator that then provides a web player and subsonic implementation and then can track listener activity and ratings and such to build a full recommendation engine and a "hey you seem to like this artist's music, you should send them some money or buy their albums" and so on.
-
Anyway hopefully @fairplayer and @mirlo get their stuff updated too! And then hopefully a whole ecosystem of stuff shows up around these things.
Like my Master Plan involves a #ChorusProtocol aggregator that then provides a web player and subsonic implementation and then can track listener activity and ratings and such to build a full recommendation engine and a "hey you seem to like this artist's music, you should send them some money or buy their albums" and so on.
-
The "correct" way to do this would be to build an entire ontology or build it on top of JSON-LD and schema.org and whatever but holy crap does that lead to a whole bunch of added complexity that gets in the way of what #ChorusProtocol is meant to solve.
At some point what I *should* do is build an actual Python library for handling Chorus documents (which would also be a useful spot for validation tools) and then that makes my life a lot easier, but for now ad-hoc JSON serialization is it.
-
The "correct" way to do this would be to build an entire ontology or build it on top of JSON-LD and schema.org and whatever but holy crap does that lead to a whole bunch of added complexity that gets in the way of what #ChorusProtocol is meant to solve.
At some point what I *should* do is build an actual Python library for handling Chorus documents (which would also be a useful spot for validation tools) and then that makes my life a lot easier, but for now ad-hoc JSON serialization is it.
-
#ChorusProtocol update: added a chorus feed to https://sockpuppet.band/ which should be discoverable at https://sockpuppet.band/chorus.json
There are still no validation tools so I probably fucked something up :)
-
#ChorusProtocol update: added a chorus feed to https://sockpuppet.band/ which should be discoverable at https://sockpuppet.band/chorus.json
There are still no validation tools so I probably fucked something up :)
-
There’s a lot to be done. Big things that would have the most impact:
* more implementations, both on the publishing and consuming side
* a validation suite for the format
* an aggregator that can build a collection and make it available to a player via subsonic or similar
* help with building an informational website to make it easier for more folks to #JoinTheChorus -
There’s a lot to be done. Big things that would have the most impact:
* more implementations, both on the publishing and consuming side
* a validation suite for the format
* an aggregator that can build a collection and make it available to a player via subsonic or similar
* help with building an informational website to make it easier for more folks to #JoinTheChorus -
It’s worth noting that the #fairplayer and #mirlo integration isn’t a one-off thing between the two platforms - it’s the first large-scale test of the Canimus protocol! It’s been pretty successful and is what has informed the next revision of the protocol, which is now called Chorus. Want to help guide its future? Join in at https://github.com/PlaidWeb/Chorus
-
It’s worth noting that the #fairplayer and #mirlo integration isn’t a one-off thing between the two platforms - it’s the first large-scale test of the Canimus protocol! It’s been pretty successful and is what has informed the next revision of the protocol, which is now called Chorus. Want to help guide its future? Join in at https://github.com/PlaidWeb/Chorus