@VictorVosMottor For vandalism like that, we typically mark it was tp- or v. We don't want to blacklist the user as they typically won't go on to vandalize their posts again once warned.
@VictorVosMottor Blacklist Managers (read about these here) are users who can add to and remove from the watchlist and blacklist lists for websites and other such keywords. The user blacklist is just a list of users that will automatically have their posts reported through SmokeDetector when scanned.
We can add to the Watchlist and Blacklist ourselves by using !!/watch (regex) too, but our additions are made in the form of a Pull Request, which a blacklist manager must review and approve/reject.
[ SmokeDetector | MS ] Link at end of answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer, username similar to website in answer (127): adding textarea to wordpress options-general.php by WP Flips on stackoverflow.com
@double-beep Because I went through the list of feedbacks which were duplicated and cleared all the duplicates. In other words, on every post where a user had more than one feedback, I deleted enough of them so that each user has only one feedback per post. The significant majority of them were straight duplicate feedbacks which were created within 0 seconds of each other.
@Mast No. I also removed ones where the user had given more than one non-identical feedback. On each of those, I evaluated which feedback was either A) the one which appeared more likely the user intended to be their final feedback (i.e. their most recent), or, in a small number of cases, which was more appropriate for the post.
We never really quantified what "exceptional contribution" means in terms of earning stickers... but whatever it is, I'm pretty sure 18,655 reviews qualifies :P
!!/bisect asus.com/Motherboards/P8Z77V_LX/</a>; ) with a very small empty slot labelled "PCIEX1_1", plus a few longer PCI Express 3.0 slots empty. I think I also have a spare SATA 6Gb/s slot...</p><p>COuld anyone ghelp me out - What's the fastest slot to use please, and wny recommendations on a decent fast SSD to buy please ?</p><p>Thanks!J</p>
@Mast 'a> ) with a very small empty slot labelled "PCIEX1_1", plus a few longer PCI Express 3.0 slots empty. I think I also have a spare SATA 6Gb/s slot...</p><p>COuld anyone ghelp me out - What\'s the fastest slot to use please, and wny recommendations on a decent fast SSD to buy' is not caught by a blacklist or watchlist item.
@Mast Matched by (?:buy\b(?<!<\/?code>.*?)(?!.*?<\/?code>)(?:[^b]|b(?!uy\b)|\wb){0,400}?<\/?a(?=(?: [^>]*|)>)[ >]\W*|a>(?<=<\/a>)(?<!<\/?code>.*?)(?!.*?<\/?code>)(?:[^>]|>(?<!<\/a>)){0,400}?\bbuy)(?#buy before, in, or after a link within 400 characters without code; when watched, was 3077/2878/194/14 minus 12/2/10/0: 2018-12-14T21:43Z, or so) on line 7044 of watched_keywords.txt
I disabled the feedback buttons for FIRE on chat.Meta quite a while ago. I'm now looking to re-enable them. I'm relatively sure I've even uninstalled and reinstalled the script since then. Does anyone know how I can reenable the feedback buttons there?
@thesecretmaster New feedback from a user currently replaces any feedback which was given in the last 24 hours. If the old feedback is more than 24 hours old, then it's not replaced, but the new feedback is added. As far as I know, that was done so there's a record of the old "locked" feedback. However, it would be better, IMO, for the old, >24 hours old, "locked" feedback to be automatically "cleared" (i.e. leaving a record) when a new feedback is given.
I don't recall a situation where it's been desirable to not clear that old feedback.
However, the significant majority of the duplicated feedback was actual duplicates, which were placed within, at most, a second or two, mostly in 0 seconds. IME, this happens when either a userscript sends more than one feedback very rapidly, or when the user double-clicks on the feedback button on MS. I assume that in such cases, MS has two threads which are applying the feedback and the check for a duplicate is made prior to the new feedback being placed. Thus, there's a timing issue.
The real fix is to have MS perform a check after the feedback is added. In that check, it should be that if there is more than one feedback from the user, then only the most recent should be retained, and any additional feedback from the user on the post within the last 24 hours silently deleted and any feedback from the user on the post which is older than 24 hours being marked as "cleared".
The JavaScript should be changed such that it doesn't allow the user to double-click, but that's a band-aid, rather than a real fix. [The JS to do this is written/in testing, as it's still useful (and applied to more elements), even if a real MS solution is implemented for feedback.]
@Mithical To clear the configuration of FIRE you can do:
You can enter the following in the console to wipe FIRE's localStorage values and start over: localStorage.removeItem('fire-user-data'); localStorage.removeItem('fire-user-sites'); localStorage.removeItem('fire-sites');
Sorry for the multiple pings. Just appending the onebox to the monologue made it look a lot like it was part of the earlier information, even though it was a reply to something else.
@Mast These are easy to spot in the "why" data. If the captured text begins and ends with "buy" and a part of an <a> or </a> then it's almost always that regex.
The Barbequeue has been completed. All items have been reviewed. We are completely caught up. Starting with over 25,000 reviews, the Barbequeue has been completed in 13 days.
Time to shout out some power players: @Rubiksmoose is the undisputed review queue king, having given 18,655 feedbacks over the course of the event. That's... Insane, honestly. Runner up is @double-beep with 6,369, followed by @DanielWiddis with 2,440 - an impressive feat for someone who only joined a few weeks ago.
13
Here's a screenshot of the standings for the non-Core folks.
@double-beep Personally, I find the GraphiQL interface to be much better. I don't have a problem with removing the link to the GraphQL interface. My comment on your PR is mostly a procedural/organizational issue.
@Mast Which highlights just how much work almost 19k feedbacks is for one person and how huge the 37,062 feedbacks contributed during the Barbequeue are. Great job. Thank you, and everyone, for all the hard work
I collected some URLs, then POSTed https://sites.google.com/site/site_name/system/services/gateway/?service=ReportAbuse&j2anofwd=true&jot.xtok=someString and most of them were deleted
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, potentially bad keyword in body, repeating characters in body (263): Como fazer tal coisa assim ✏️ by User on pt.stackoverflow.com
