if you are interested in extending rss to pass more music metadata have a look at Making sure you're not a bot!
1 Like
Ooh, @lorenzosmusic have you spoken to the Fairplay folks?
1 Like
Just of curiosity @simon , which FairPlay were you referring to;
- https://fairplayus.com/ - If anyone has a way to contact them, they need to fix the SSL certificates on their site (as of today)
- https://www.fairplaysound.com/
- https://fairplaymusic.world/
- https://fairplayentertainment.com.au/
- FairPlay Streaming - Apple Developer - grApple FairPlay streaming protocol
- https://www.anticorruptionmusic.org/ - Fair Play campaign in Africa
As you can tell, the meaning of “FairPlay” is already a bit overloaded, and I would advise anyone who’s picked that as a name for a newish project to pick something more unique ; )
2 Likes
how to avoid impersonation and fake payment link? How to manage conflict between users/activitypub/rss metadata ? a draft reflexion can be found here : Making sure you're not a bot!. Any pov is welcome 
1 Like
Interesting work! Did you ever think about the ability to connect your Artist account with a “known identity”, eg, like Mastodon’s verification system with the artist’s website?
what is mastodon verification system ?
I had contacted them a few weeks ago. They said they were unavailable to talk and to check back in a few months.
Wait, now I think that may have been Subvert that said that. 
But I know I had contacted Fairplay, I think maybe they haven’t responded yet. I should check back with them.
1 Like
They use rel=me, so your website link shows up as verified on your Masto profile.
There really ought to be an FEP for this both supporting rel=me verification, and providing a simple interface for add the necessary code. For instance to easily show that @artist@mastodon.server is operated by the same people as @artist@funkwhale.server, or @artist@bandwagon.server, and that the channel for their music videos and interviews is @artist@peertube.server.
I doubt it’s super complicated to implement, and it’s a really helpful UX improvement.
The one you didn’t mention haha
1 Like
That would be because it’s FairPlayer, not ‘FairPlay’. No wonder I had some trouble trying to find it in a web search 
I’ll make sure it’s on the who’s missing list.
1 Like
This only works to verify the artist website, it can’t work to verify other links (you cannot add html to spotify for example and I doubt they will implement this). But thanks a lot ! it’s interesting and noted
1 Like
It’s not going to work for DataFarms, no. But I can’t see why it couldn’t work for anything where the necessary code and interface can be added at both ends.
If you’re sure this isn’t possible, can you please educate me on why?
of course it’s possible for mastodon since they implement it, I meant it’s not usable for other software. But it would be nice if this could be implemented widely.
1 Like
Hmm, if you reckon artist website isn’t enough, have you already looked into oauth? I think that must be what Liberapay is doing. See here (I had to sign into some other accounts to verify I was the owner): https://liberapay.com/Meljoann/donate
1 Like
yeeeess ofc this is perfect, how didn’t I though about it haha Thanks
1 Like
@fluffy @LLK I just implemented the rss improvement proposition in funkwhale serializer. It’s very easy to add the mmd namespace to an existing rss endpoint. You can look at the diff here.
Example of a track item :
<item>
<title>Out of Space</title>
<itunes:title>Out of Space</itunes:title>
<guid isPermaLink="false"><![CDATA[74071656-4b6a-4b36-a5e0-8752118d0c9d]]></guid>
<pubDate>Wed, 06 May 2026 16:08:44 +0000</pubDate>
<itunes:duration>00:04:58</itunes:duration>
<itunes:explicit>no</itunes:explicit>
<itunes:episodeType>full</itunes:episodeType>
<itunes:season>1</itunes:season>
<itunes:episode>1</itunes:episode>
<link>https://node1.funkwhale.test/library/tracks/693</link>
<enclosure
url="https://node1.funkwhale.test/api/v2/stream/842832c8-4216-4844-a7b4-5bd1212cc9de.mp3"
length="2317997" type="audio/mpeg" />
<mmd:recording>
<mmd:title>Out of Space</mmd:title>
<mmd:artist-credit>
<mmd:name-credit>
<mmd:name>node1@node1.funkwhale.test</mmd:name>
<mmd:tag-list>
<mmd:tag>
<mmd:name>Cumbia</mmd:name>
</mmd:tag>
<mmd:tag>
<mmd:name>Dance</mmd:name>
</mmd:tag>
<mmd:tag>
<mmd:name>Espagne</mmd:name>
</mmd:tag>
</mmd:tag-list>
</mmd:name-credit>
</mmd:artist-credit>
<mmd:release-list>
<mmd:release>
<mmd:title>loilol</mmd:title>
<mmd:tag-list>
<mmd:tag>
<mmd:name>Espagne</mmd:name>
</mmd:tag>
</mmd:tag-list>
</mmd:release>
</mmd:release-list>
</mmd:recording>
</item>
1 Like
Thanks, I’m interested in seeing how an album looks as well. In particular I don’t think it’s very good UX to have separate feed items for every track in an album in the general case of following a musician, since generally you release a buncj of tracks all at once and getting a flood of notifications/syndicated posts/etc. can be very quickly overwhelming to people who are following via an RSS reader, POSSE feed, etc.
You can use this to create any kind of feed you want, at funkwhale we have tracks feeds. But you could create a release feed and each item would be a release instead of a tracks. All the documentation can be found here : mmd-schema/schema/musicbrainz_mmd-2.0.rng at master · metabrainz/mmd-schema · GitHub
I also implement a parser that can create an ActivityPub channels from an rss feed with mmd namespace. Any project that implement the mmd ns will be connected to the fediverse through funkwhale o/
1 Like