@ArtOfCode Hmmm... Having it happen automatically feels game-able. For instance, getting it in one sitting would be easy (once you have reviewer), without requiring you to do anything other than go through SD reports which already have 2+ feedbacks and just submit the same feedback without thinking about it.
@ArtOfCode The combo of being able to get it w/o actually needing to even try to think about what feedback to give was the point. Having a human in the auth loop implied that they had at least seen the person demonstrating some level of thinking and responsibility. OTOH, I haven't looked at what the different auth levels are and what they get to do, so it may not be something that matters.
@ArtOfCode I think 60 is kinda low. What about 60 and 5 (?) must be the first feedback on a post? I personally won't consider myself a core member here, but I just stop by and send feedbacks/flag every so often.
@quartata If that's the use/criteria, it sounds like it's just a gauge as to the person's ability to be contacted via chat to remove autoflags. So, some auto-determination would be a good thing. Perhaps the time-frame should be reduced (e.g. to auto exclude someone when they go on vacation, and include them when they return).
@Makyen core is intended to be what it says on the team - "is a core member of the team" in that they've made non-trivial continuing contributions to what we do
@ArtOfCode That's what I generally thought the intent was, which is why I was concerned about auto-inclusion/exclusion based on a single criteria, which would be gamed by some people.
@Makyen eh, if people game it we slap 'em on the wrist and tell 'em to not do that. That enforcement strategy has worked for us so far for other things
@WELZ You can install either Greasemonkey or Violentmonkey in Firefox for Android. (I haven't actually tried using them, but both are available and installable).
