fp- by doppelgreener on [How can i call a service phone number with a hash in android? [android 3.0.1] marshmellow](//stackoverflow.com/questions/50588459) [MS]
1. hit channels#get_email_address, copy email address 2. paste into Channels signup box 3. MS receives email, parses join link 4. hit channels#show_link, click link
@ArtOfCode >The following is your email address to use with Channels. Copy and paste it into the box at stackoverflow.com/c/charcoal/join. - says it on the page you linked
Unofficial results: Winners are Bohemian, Taryn, and Mick MacCallum.
OpenSTV version 1.7 (OpenSTV.org)
Suggested donation for using OpenSTV for an election is $50. Please go to
OpenSTV.org/donate to donate via PayPal, Google Checkout, or
Amazon Payments.
Certified election reports are also available. Please go to
openstv.org/certified-reports for more information.
Loading ballots from file votes.blt.
Ballot file contains 10 candidates and 21359 ballots.
No candidates have withdrawn.
Ballot file contains 21359 non-empty ballots.
@SmokeDetector While this was repairable, 66% of the answer was inappropriate content. I'm OK with a system level block on this specific content. However, that it was autoflagged (and I was one of the autoflaggers) concerns me that something that's somewhat less would still be autoflagged/blocked. I don't think the flagging was wrong, but I do feel it's an edge case which might be too close to the edge for us to autoflag.
@SmokeDetector Just info: Red flags on this were disputed.
@Undo Yep, that's a good thing. That part of the system is working correctly. How we've currently set things should be something we watch. We've adjusted detections to better catch the trolling that we've been seeing. I know that I've adjusted my autoflagging criteria to be better able to flag that trolling. Others may have done so too. I'm just concerned, and have been concerned, that we might lean too far in that direction for the "normal" level of repairable posts.
It's not something that's an actual demonstrable problem at this time, just something that we should keep an eye on.
@ByteCommander If you felt this was repairable, which is the action you took, then the appropriate feedback is fp. Another time, if you feel that editing is the correct resolution (repairable), then please provide fp feedback, preferably prior to making the edit. This will give people the earliest notice that the automatic flags they've placed and/or the manual flags they may have raised might be invalid/invalidated. This will give them the most notice to evaluate it themselves, or to reevaluate.
@Makyen Added [a-z_]*(?:1_)?800[\W_]*805[\W_]*7863[a-z_] to watchlist
[ SmokeDetector ] SmokeDetector started at [rev 76e1388 (SmokeDetector: Auto watch of [a-z_]*(?:1_)?800[\W_]*805[\W_]*7863[a-z_]* by Makyen --autopull*)](//github.com/Charcoal-SE/SmokeDetector/commit/76e1388) (running on teward/Solar Flare)
@Makyen That pattern looks like it's already caught by Bad ns for domain in answer and Bad ns for domain in body; append -force if you really want to do that.
@Makyen Added shopzoro\.us to watchlist
CI on 84d0d7f succeeded. Message contains 'autopull', pulling...
@SmokeDetector This is an example of something where I our feedback, or at least guidance, feels inadequate. While I feel there's something that could be rescued from this question (i.e. it's potentially repairable, thus FP), I feel it's sufficiently offensive such that I would be fine with a system level block (i.e. TP). I have have flagged it as rude/offensive, because, to me, this is over the line of what should be repaired/saved vs. where the user should have some consequences.
