Dev, ++ Show more
Tfw you implement something quite complicated and things apparently work as expected (until they crash and burn of course)
Dev, ++ Show more
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.
Dev, ++ Show more
It would work like this:
- 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
Dev, ++ Show more
While quite complicated, I believe this is needed, to have auditability of the changes (what value was changed, by who, when, why), and make the reviewing/reverting process easy to deal with.
Dev, ++ Show more
As for the approval permission:
- 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.
Dev, ++ Show more
This is an important step to improve the overall quality of the audio metadata available on the network, and make the service more attractive to content creators.
Dev, ++ Show more
And once we have resource claiming, the road is paved for supporting tips: You're a creator, you claim your profile, add a link to your Patreon or whatever, and voilà!
Of course, for the contribution part we'll want something structured, so we can suggest users what creators to tip based on their habits/settings.
But that specific part will not be develop inside Funkwhale itself and will likely happen as a separate standard to be reusable by other projets.
Dev, ++ Show more
And I love the fact this is incremental change.
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
re: Dev, ++ Show more
mastodon.eliotberriot.com is one server in the network
Dev, ++ Show more
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.