@double-beep SD does, for some reason, but it doesn't appear to be the fault of the AF userscript. The issue is that SD is reporting the post twice when it's both reported through the MS API and scanned normally. It's unclear why that's happening, as SD is supposed to prevent reporting a post twice within a short period. I need to take a more detailed look at the code to determine why it's happening. I did look a bit, but only determined that it's not the MS API forcing the report.
At the moment, I'm thinking it might be a concurrency issue, but I haven't really looked into that possibility, yet.
@Spevacus That pattern looks like it's already caught by Bad phone number in answer and Bad phone number in body Append -force to the command if you really want to add this pattern.
:59714169 That pattern looks like it's already caught by Bad phone number in answer and Bad phone number in body Append -force to the command if you really want to add this pattern.
@Dharman When you hover over the FIRE button??? The release version of FIRE doesn't add a tooltip to the FIRE button and it's not a link, so your browser shouldn't be trying to display a URL. I'm a bit confused.
@Dharman Is what you're seeing a tooltip, or is it a toastr message (similar to what you described as the blue popup)? If it's a toastr message, what color is it?
@Dharman OK. Thanks. Those are toastr messages. That helps narrow it down, somewhat, but I'm definitely not seeing that issue. What other userscripts are you running which might mess with the chat message contents?
