Skip to content
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

Spam Classification #2991

Closed
wants to merge 1 commit into from
Closed

Spam Classification #2991

wants to merge 1 commit into from

Conversation

ewdurbin
Copy link
Member

Pursuant #2982

@ewdurbin
Copy link
Member Author

@di @dstufft thoughts on the modeling thus far?

release_version = Column(Text, nullable=False)
source = Column(report_source, nullable=False)
reporter_user_id = Column(UUID, nullable=True)
result = Column(Boolean, nullable=False)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supposed to be some metric for "spaminess"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

negative. in initial research of akismet and smythe the response to a classification request is a boolean. True/False or verdict:BLOCK/verdict:ALLOW (which can be trivially modeled as a Boolean)

@di
Copy link
Member

di commented Feb 20, 2018

Seems to make sense, this would capture both results from automated services and user-generated reports, and we could aggregate them for every project. I like that the analyze_upload task is asynchronous as well.

@ewdurbin
Copy link
Member Author

dope, I'll continue fleshing this out tonight.

@ewdurbin ewdurbin closed this Apr 24, 2018
@dstufft dstufft deleted the spam_classification branch November 28, 2018 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants