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

Ways to find posts which were *not* autoflagged #51

Closed
2 of 3 tasks
tripleee opened this issue Dec 29, 2016 · 6 comments
Closed
2 of 3 tasks

Ways to find posts which were *not* autoflagged #51

tripleee opened this issue Dec 29, 2016 · 6 comments
Labels
status: planned We like the idea and might get around to it at some point. type: feature request Requests for a new feature.

Comments

@tripleee
Copy link
Member

tripleee commented Dec 29, 2016

The new autoflagging functionality is awesome, but in order to make it even more awesome, we need some way to find the posts which were still not autoflagged, so that we can analyze them and figure out additional heuristics we could put in the system in order to catch similar posts in the future.

I'm vague on what exactly would be useful, and only posting the use case at this point. I can think of some ways which should hopefully be reasonably straightforward, by order of (my limited perception of) apparent complexity.

  • Similar to the flagged log https://metasmoke.erwaysoftware.com/flagging/logs display a timeline of just the posts which were not flagged
  • Throughout the system, expose the flag weight in places where currently we display a summary (title, site, timestamp, user, feedback icons, etc) -- this overlaps with issue Reason weight in flagging logs #50 to some extent
  • Expose the flag weight in the search form as a searchable field
@ArtOfCode- ArtOfCode- added the type: feature request Requests for a new feature. label Dec 29, 2016
@ArtOfCode-
Copy link
Member

ArtOfCode- commented Dec 29, 2016

Point 2: 084d6ad

@tripleee
Copy link
Member Author

tripleee commented Jan 2, 2017

Point 3 was requested again: http://chat.stackexchange.com/transcript/message/34498185#34498185

@tripleee
Copy link
Member Author

Would it make more sense to close this and reopen #53?

@Undo1
Copy link
Member

Undo1 commented Apr 25, 2017

No, this one works. It's on my radar, just need to find time to do it.

@ArtOfCode- ArtOfCode- reopened this Aug 16, 2017
@ArtOfCode- ArtOfCode- added the hacktoberfest HF issues label. Outside of HF, also consider using type: up-for-grabs. label Oct 2, 2017
@thesecretmaster thesecretmaster removed the hacktoberfest HF issues label. Outside of HF, also consider using type: up-for-grabs. label Jun 19, 2018
@thesecretmaster
Copy link
Member

Unless flag weight became a field in posts, I really think this is too expensive to be possible.

@tripleee
Copy link
Member Author

Blazer delivers this and much more. Thanks for providing it!

Sent with GitHawk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: planned We like the idea and might get around to it at some point. type: feature request Requests for a new feature.
Development

No branches or pull requests

4 participants