-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to add NSFW reporting to tracks. #1
Comments
I'm not sure I understand what you meant. Could this be rephrased to be clearer ? |
As I understand it, when someone uploads a track to the site, sometimes we'll forget to flag it as NSFW. We need a mechanism on the site where a listener can flag a track as potentially NSFW, so it can be reviewed by an admin and flag the track accordingly, recreating any shows which would be affected by the change. |
Correct. |
Understood. Thanks. |
But also because longer term, I want to be able to run 8 hour "background music" streams that people can consume at workplaces or social events, that the user can choose to be SFW, etc. |
Sorry, I wanted this to be referenced in this issue. |
I'm working on this, got it almost working, but I think there's a bug in PDO, or maybe it's just my code.. I'll see that later :-) |
Ok, the bug above is fixed. Waiting on #53 to be merged before I submit a PR for this. |
Merged. |
Fixed issue #1 : Need to add NSFW reporting to tracks
This is fixed by #54 so it can be closed. |
Fix malformed NotAPICall message
Ultimately, we all make mistakes, and sometimes a track is uploaded without being marked as being unsafe for work or family listening. On the main site, doing this marks a track as being family-unsafe should flag it for moderators to review. When a moderator reviews the track, it should remove all the moderation flags, then once the moderator has marked the track as unsafe it should remove the track bumpers as well as setting the isNSFW flag on the track.
This should also be able to be changed without it being flagged first.
The text was updated successfully, but these errors were encountered: