To be frank I expect this feature to go nuts at any point, because I'm implementing a federated wiki-based workflow to allow Funkwhale users to suggest changes on tracks, albums and artist data, with history and reversibility.

I've only work on the backend part, and there are of course big challenges in term of UX/UI, but I did not hit half the crap I was expecting.

- As a funkwhale user, you can visit an artist / album / track page and suggest a change (new cover, fix a typo, change the track license…)- If the resource is not located on your instance, this suggestion is forwarded to the remote instance- The owner of the resource (first uploader or artist account, or instance admin…) can approve or reject the suggestion- Once approved, the modification is broadcasted over federation

- Accounts with the "library" permission will always have it- First uploaders of an album/track/artist will have the permission as well unless- Someone claimed the resource, in which case, that account will replace the first uploader as the owner of the resource

The claiming feature itself is not implemented yet but will be useful for creators that join the network and need to take ownership of their work that was already uploaded by other people.

If we reach that, while bringing other planned features to the project (federated user interactions and comments, podcast support, live audio streaming), I believe Funkwhale will be competitive enough as a platform to seriously attract creators and users that currently live on mainstream platforms.

There is still _a lot_ of things to do before all of that even work and is nicely integrated, but it makes me happy to see the progress.

We don't have to wait years to benefit from this. Each feature can be implemented separately, and will progressively bring more value to the whole platform until the universe implode under the critical mass of Funkwhale accounts :D