[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +5 more (691): how to use Keto Max XR by telinorjek on meta.SE (@Ollie)
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, blacklisted website in answer, potentially bad keyword in answer (267): get a contact phone number crash by Navin on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (91): Playing Facebook Games by sonam on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in link text in answer, link at beginning of answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, +1 more (119): Stack Exchange login hangs on Windows 10 Mobile? by sonam on stackapps.com
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
FIRE version 1.4.0 (now 1.4.1): (GitHub) (install): lots of changes, including better rendering of reported posts and why data; better responsiveness; move & resize the popups; click to lock open/position of why data, so you can copy out of it or click some links; etc.
9
AIM version 0.28: (GitHub) (install). Add additional rooms; show ignore feedback; various improvements; Prevent the queue of MS WebSocket messages from growing without bound.
6
My intent is that this version of FIRE is an intermediate version. The plan is that an additional version will be released moderately soon, but there's more work for me to do to make that happen. Basically, with this release, the differences between the released version and my development went from this to this, with white indicating portions which are identical.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@Makyen Nice job with the new FIRE version! I do like the reason weight on the side of each report; it's definitely easier than going through MS and will help when setting my autoflagging preferences.
You can hover over it for the why data (which is now nicely formatted and everything) and clicking the username now takes you to their profile, which is something I've wanted for awhile
@Ollie You can put the window.dispatchEvent(new CustomEvent('fire-popup-appeared')); line on L2492, in the handleReportImages function, and FIRE Additional Functionality should work properly.
@Spevacus Hmmm... I wasn't consciously aware that it used events to detect that. Ironically, I did add events which FIRE now fires when the popup is opening, opened, closing, and closed, so that something could detect those happening.
