The new update is looking good! One thing I noticed though, and honestly I don't remember if the page was there before or not, is that a user we've banned from our leaderboard shows up in the streams page. He's not banned site-wide, just from our community, so it makes sense, but would it be possible to get a blacklist feature for the streams page?

He should be fine just to stream. I don’t really see the problem with it.

The issue isn't him streaming, or even his stream being shown on speedrun.com. The issue is his stream being promoted on the page of a game he's been banned from.

Depending on what they’ve been banned for, you could probably message site staff to ban him from the site.

Would per-community ban lists solve this? Here's the rough idea:

• You'd be able to exclude user(s) from your community.
• It would prevent them from taking any actions (submitting runs, etc) or appearing in places like the Streams page.

That seems like a good idea - maybe

@SkittlesCat I mean, it's not any harder to abuse than rejecting (or just outright ignoring) every run that person submits. Ideally the ban reasons would be documented in some way that site staff can see, and moderators would be able to answer any follow up questions about them from site staff in case any issues arise. Abuse would be handled the same way as any other abuse of moderator privileges, I imagine.

@Camcorder I think that would work if it's only for the game/community in question. If I ban someone from the "Mobility" community, they should still be able to submit runs to any other game, and their stream should show up unless they're running Mobility.

@Camcorder A per-community ban list would be perfect!

@Camcorder I think that would work if it's only for the game/community in question. If I ban someone from the "Mobility" community, they should still be able to submit runs to any other game, and their stream should show up unless they're running Mobility.

Yeah that's exactly it - we already have site-wide bans, this would be community specific. There's a few issues to work through, but we'll add this to the list!