3 ms·
This looks like legit, no-nonsense gets-the-job-done code that gets updated every time some jerk find a new way to be a jerk to others. It isn't great, but at l
by ridaj 5y ago
This looks like legit, no-nonsense gets-the-job-done code that gets updated every time some jerk find a new way to be a jerk to others. It isn't great, but at least not over-engineered, and I'm not sure if Twitch account sign-up volumes and abuse are at the point where they should staff a project to do this more robustly / scalably
- OskarS 5y agoExactly what I think. This is the kind of code that doesn't have a platonic ideal, it has to get updated with time and experience and reports. There is no "non-hacky" way to do this, you just have to look at the reports that are coming in and keep adding rules that are relevant.
- tonfreed 5y agoYou say that there's no "non-hacky" way, but... https://www.youtube.com/watch?v=bJ5ppf0po3k https://www.youtube.com/watch?v=bJ5ppf0po3k He made a filter that did analysis of the pronunciation of the messages that were being sent. His breakdown of it starts at around 13:30
- ridaj 5y agoWell there are some significantly less hacky / more scalable ways to do this. This looks at the edge of maintainability, but if the lists were 10x as long and people constantly stepped on each other's toes causing outages while making updates, a bit of project investment probably wouldn't be a bad idea.
- baud147258 5y agoit's missing a few slurs, I'm not sure it gets updated (or it's a filter elsewhere which gets updated)
- notjustanymike 5y agoThere are portions of my codebase that are intentionally "dumb" code. They contain cascading rules controlling what UI elements are visible that can be challenging to reason about. So I wrote it so simple that anyone can read it. I see the same here. It's not clever, but no one has any doubt what words are being checked.