Link to tracks that aren’t on Funkwhale

petitminion

@Sporiff is this closed ? https://pad.funkwhale.audio/VyGBZFb4T5G57q-99pApGQ

petitminion

I added the hide attribute and the source attribute to the spec, so admins can hide a link and the frontend can know were it come from

petitminion

the api probably lack some logic to handle the moderation, I propose to create a list of banned link only editable by the admins. This way if a link is banned even if a user tries to add it again, it will no be allowed, avoiding moderation work.
this is a comes has a complement of admin being hable to edit links

Maybe hide and ban could follow the same logic : the moderator could ban musicbrainz links like any other link instead of hiding them.

Sporiff

petitminion the api probably lack some logic to handle the moderation, I propose to create a list of banned link only editable by the admins. This way if a link is banned even if a user tries to add it again, it will no be allowed, avoiding moderation work.

A denylist is definitely a good idea!

Maybe hide and ban could follow the same logic : the moderator could ban musicbrainz links like any other link instead of hiding them.

I see this mechanism working as follows:

The admin would maintain a denylist of links (e.g. if the admin doesn't want any Wikipedia URLs to appear, they can add it to the denylist and any URLs matching the pattern will not be allowed/will be removed from content. This removes the entry from the database completely, ensuring it's not visible to API responses
The admin can hide specific links from MB if they don't find them relevant or just don't want them to show up. This is different in that it only impacts the specific target (e.g. the album/artist that the admin is editing) and is just there to stop the MB fetch task adding the link each time. This only hides the link visually, and it will still be available in the API response (with a hidden attribute)

Of course, the admin could denylist a specific link that they really don't want appearing in the API response, but that's their choice.

petitminion

Sporiff what is the interest of having both approach ? why not only have a denlist to avoid useless moderation option ?
To have a synced mb table, a tasks would just have to add the hiden atributre to the mb link if a mb link is added to the denlist. The api should not return hiden links (useless explicitly asked to). And that's it. What do you think ?

Sporiff

petitminion It may not be necessary. The only thing I can think of is the following:

There is a link against an artist in MusicBrainz. We pull this link in when we create the artist
The admin of the server doesn't want this link to appear against this specific artist, so they hide it. This means that it isn't displayed against this specific artist even if it's updated
The same link is also present on another artist. The admin does want it to appear here, so they leave it in place.

If we only had a denylist, this wouldn't work. The link would be present on the denylist and so would not appear on any content.

The difference, I think, is between content organization and anti-abuse. The denylist would be an anti-abuse feature, while hiding would be a content organization feature. However, this is probably an edge case, and the denylist is by far the more important mechanism. Maybe we should start with that and just have the link hiding feature be a future feature idea.

petitminion

Sporiff If we only had a denylist, this wouldn’t work. The link would be present on the denylist and so would not appear on any content.

Indeed..

Sporiff Maybe we should start with that and just have the link hiding feature be a future feature idea.

I agree with that o/

petitminion

So about the denlist, it should be accessible in the moderation section I suppose ? We can also keep this frontend design for later and only provide it through the django admin panel

I'm gonna start coding the backend api endpoints for this feature

Sporiff

petitminion I think it's important that this is easily accessible for end users, so as soon as possible we need to expose it in the application itself to ensure that admins can easily control this. The Django admin panel is fine while we're still developing the feature, but we can't reasonably expect admins to keep using it for day-to-day stuff.

petitminion

Sporiff @mjourdan this means we need another design here 🙂

gcrk

@petitminion I don't think we need this for now, we have widgets that should be used and if I remember correctly there is already a design pending for the admin settings, but they would only get picked up when Kasper is doing the reimplementation of the settings page.

petitminion

gcrk okey thx for lettings me know 🙂 Could be great if all the team could have access to the design through penpot directly ? I don't have access to anything in my penpot account :s What do you think @mjourdan ?

gcrk

petitminion You are editor of the group, so you should have access unless you created a new account.

petitminion

I propose to start implementing the backend following the actual spec. And to create a new spec about the moderation denlist.

« Previous Page