Add ML classifier to reject spam events #735
Open
+216
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Flip label - 1 is legit, 0 is spam
flip bit - 1 is legit, 0 is spam
flip bit - 1 is legit, 0 is spam
flip bit - 1 is legit, 0 is spam
flip bit - 1 is legit, 0 is spam
|
@jc00ke most of what you're looking for is now here I think - I ran most tests successfully locally, but was running into some chrome version mismatch on selenium tests that were failing. I think they were mostly unrelated, but can't be sure, so you may want to try locally too - yak shaving the version mismatch is something I can do, but will take a bit longer and I wanted to get the code here first so you can check it out. LMK what you think! |
jc00ke
requested changes
Jul 19, 2023
|
@jc00ke any chance to pull this? |
|
What ever happened to this PR? I came here after noticing that a few events in San Francisco have been posted to Calagator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As referenced in my other message, here's an implementation where we can use a classifier to reject spam events. The one thing I don't love is that this requires HTTP requests during an HTTP request, but no way to get around that without putting some other job logic into calagator afaict