Protocol options for interoperation of music hosting services

We are working on ActivityPub integration (it’s a pain, by the way, not a lot of support, complex, and hard to navigate) and where we’re looking for that integration is basically that you can follow artists, and you’ll receive their posts (WIP but this is what that looks like) on Mirlo (alongside, likely notifications that they published an album).

However there’s a couple of things here. Artists likely want a more nuanced control of their tweets / whatevers, because they’re operating under patterns that they’re used to. So they will already have their own accounts. Will they want to be responsible for another account posting to a social media space? Unclear to me if that’s actually desirable from their point of view. To me there’s a difference to the press releases and blog posts on your website and the toots or whatever that you fire off a million times a day. (We’re going to let artists choose). tbh I think RSS and mailing lists solves this much simpler and with a lot less unnecessary energy expenditure than ActivityPub does and are much better understood by every day people.

Additionally, a lot of what we’re trying to solve here aren’t “activities” or telling people about those activities. Instead we’re talking about catalogs and the ability to look at catalogs and listen to music on the catalogs. That’s not what ActivityPub is for. Even bandwagon, which started from the ground up as an ActivityPub project, isn’t handling catalog search that way (or wasn’t anyway when @bandwagon wrote this Building a Federated Search Engine ). That’s what @fluffy is trying to accomplish with Canimus.

When I’m searching FEP I’m not seeing anything that actually solves this idea of a catalog. There are “music” events. No idea what that means. There’s something about sharing playlists (but it’s only used as an example) but playlists don’t have the same functionality as an album.

3 Likes