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

Removing the "naa" feedback #483

Closed
double-fault opened this issue Jan 25, 2017 · 11 comments
Closed

Removing the "naa" feedback #483

double-fault opened this issue Jan 25, 2017 · 11 comments
Labels
type: feedback wanted "Closed as too opinion-based."

Comments

@double-fault
Copy link
Member

Smokey was created to classify spam, not LQP. The "naa" feedback serves no purpose IMO in Smokey. It has caused confusion many times, and I do not see the reason for this feedback type to be there anymore.

Relevant discussion in chat: http://chat.stackexchange.com/transcript/message/35002373#35002373 (read below that).

@Cerbrus
Copy link
Member

Cerbrus commented Jan 25, 2017

👍
Whether something answers a question or not is irrelevant, when determining if said post is spam.

@ArtOfCode-
Copy link
Member

I'm unsure. I think I was one of the proponents for adding it what must be a year or more ago now - and there must have been a good reason for that. I'd like to find out what that is before we just remove it.

@teward
Copy link
Member

teward commented Jan 25, 2017

NAA has been implemented for at least a year, now. My guess is to track cases where a filter catches half-positives that are not spam, but are still "valid detections". (That is to say, something posted that matches the filter but isn't a tpu- worthy case) @Undo1 would know more about this...

@Undo1
Copy link
Member

Undo1 commented Jan 25, 2017

It serves to identify posts that aren't spam, but that we'd still be happy if they were blocked before being posted.

For example, there's a big difference between a group of posts that are 99% tp / 1% fp, compared to a group that is 99% tp / 0.95% naa / 0.05% fp. The latter is much more representative of the potential for Real Damage if one of our metrics was allowed to integrate with the system (or was given extra flag weight).

@teward
Copy link
Member

teward commented Jan 25, 2017

Tracking these metrics is a good thing. I'm going to vote against removal of the "naa" feedback.

@Cerbrus
Copy link
Member

Cerbrus commented Jan 26, 2017

That makes sense @Undo1.
While this still applies:

Whether something answers a question or not is irrelevant, when determining if said post is spam.

I understand it can be desirable to track some types of not-spam.

@double-fault
Copy link
Member Author

@Undo1 if that is the reason for having the NAA feedback, shouldn't we have a similar one for questions too?

@angussidney
Copy link
Member

Alternatively rename it to Low Quality (or use a similar name), then it can be associated with questions too. Then we can add NAA as an alias for it.

FDSC could then bind NAA and VLQ in answers (and possibly delete?) to the LQ feedback along with VLQ and off-topic flags/closevotes for questions.

@angussidney angussidney added the type: feedback wanted "Closed as too opinion-based." label Jan 27, 2017
@Undo1
Copy link
Member

Undo1 commented Jan 27, 2017

Torn on that one. On one hand, there have been a few (small number, from what I've seen) of situations where this would be useful.

On the other, I could make a fairly strong argument that it's an order of magnitude easier for us to accurately gauge whether an answer should have been posted than whether a question should have been posted. Some (many) sites have really weird rules around questions, and only a few have those around answers (sorry, SR and HR...)

@ArtOfCode-
Copy link
Member

Hey, at least we have mods from SR and HR around to make a call :)

@double-fault
Copy link
Member Author

heh, fair enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feedback wanted "Closed as too opinion-based."
Development

No branches or pull requests

6 participants