fluffy (beesbuzz.biz)
#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 :)
1 comments — live from bluesky
fluffy 💜 · 0 · 21h ago The way entity references work is still pretty awkward but that's one of those things that's like... Hard.
It *should* be pretty straightforward for simple cases, but nothing about my own catalog is particularly simple :P
fluffy 💜 · 1 · 21h ago 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 […]
fluffy 💜 · 0 · 21h ago Also the fact that I'm building the structure out of things that are represented in my website CMS data makes things tricky, especially since my CMS was built for blogging, not structured data. :P
fluffy 💜 · 0 · 21h ago 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 […]
fluffy 💜 · 0 · 21h ago (And of course it's quite plausible for that functionality to exist as part of Fairplayer! I'm not entirely sure what their long-term plans are but it'd certainly be compatible with what they've done so far.)