its great when i can watch youtube videos or work on stuff, see a spam post pop up on my other monitor, then i can just spam flag and tpu it and go back to what im doing
its amazing how little work i have to do to ruin spammers work. Makyen, Thomas, and the rest of those that have developed Charcoal and the surrounding tools have done amazing work.
@lyxαl i have auto flagging enabled, but im not sure if my flags have ever been used for that. maybe when im asleep. but FIRE can flag for me, so i only have to go to the site if i need to create an account
@Dragonrage you can go to metasmoke.erwaysoftware.com/flagging and then click x flags used today on the top right and it will bring you to a list of all auto flags used from your acccount
@Dragonrage I'm unsure exactly what you're asking for. Could you describe what you'd like to see a bit more clearly?
Currently, if you highlight something in the FIRE popup and then alt-click on it, the text will be copied into the input box. Alt-click also works without needing to highlight on links in the FIRE popup to copy the URL to the input box. These can save quite a bit of time/effort on creating messages for watching/blacklisting.
I've owed, for quite some time, to break out two additional userscripts form my personal modifications. One which takes lines in the input box and translates them to watch or blacklist commands (mostly). The other allows sending multiple lines of input in the input box as multiple messages, rather than as a single message. Part of that is also to have a dynamic height on the input box and a user-set baseline size.
It's unclear when I'll release those two, but both are on the list of things I should get to the point of releasing, rather than have them just in my own modifications.
@Makyen ah, i didnt know about the alt click, i mustve missed that in the documentation. mainly i was thinking something like the domain section when there is a link detected, just for phone numbers. basically if a phone number was detected it would have a little section at the bottom with a button to send the watch or blacklist command for it.
@Dragonrage There's some documentation about the alt-click feature in the README.md.
The lists which I think you're mentioning are part of FIRE Additional Functionality, so it's more likely to get done with changes to that userscript. I'm not adverse to having something in FIRE, but there's nothing currently.
@Nick The pattern contains an invisible U+202D whitespace character. The pattern starts with whitespace. Append -force to the command word(s) if you really want to add the pattern you provided.
@Nick The pattern contains an invisible U+202D whitespace character. Append -force to the command word(s) if you really want to add the pattern you provided.
SD jumped in the middle. i was hoping to have my message immediately following yours so whichever of the two read your message would also see mine and kill them as well
@NisseEngström Please provide an adequate reason for rejection (at least 20 characters long) so the user can learn from their mistakes. Use -force to force the reject
@NisseEngström 'https://stackoverflow.com/questions/65681138/does-mockrestserviceserver-support-mutual-tls-and-if-so-how-to-configure-it' is not caught by a blacklist or watchlist item.
@Dragonrage The !!/blacklist command has been deprecated. Please use !!/blacklist-website, !!/blacklist-username, !!/blacklist-keyword, or perhaps !!/watch-keyword. Remember to escape dots in URLs using \.
That describes so many spammers. It's inconvenient, too, because it's so much easier to detect when they actually remember to include any information whatsoever about the thing they're hawking...
@NisseEngström Yeah, although usually those have the good sense to not have the spammy text in the initial revision. Probably what they were gonna do, though.
@cigien 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 word(s) if you really want to add the pattern you provided.
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 08:02:26 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/278256?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=scifi.stackexchange.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 08:02:41 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/776590?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=physics.stackexchange.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 08:02:55 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/1174981?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=ru.stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 08:03:09 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/119769?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=money.stackexchange.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 08:03:23 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/72438?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=mechanics.stackexchange.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 08:03:38 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/4754727;4754706?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=math.stackexchange.com
@Dragonrage The watches and blacklists are different. For watches, the fp rate isn't really a concern. We'd like to avoid a very high number of fp, of course, but the goal of the watchlist is to not let any spam slip through the cracks, and some fp is to be expected. For blacklists, however, we want to have a very low fp rate, so the watches I suggested would be very unlikely to be blacklisted.
@cigien fair enough. feel free to watch whichever you think would be most appropriate. my guess is custom suits would be more likely to be spam, but just a guess
We can watch both. They each have less than 10 fp on SE (at least, but there might be more since we can't do regex searches on SE), so it shouldn't be an issue. OTOH, e.g., best[\W_]*+suits has >2k hits on SE, so watching that wouldn't be a good idea.
@SmokeDetector This has 13/0 tp/fp on MS, so it should catch stuff. custom[\W_]*+suits has 3/1 tp/fp though, and all tp would be caught by this pattern, so not much point in watching it.
@Dragonrage Sorry, I was referring to SE search stackexchange.com/search?q=%22best+suits%22. The MS search is going to be biased towards tp, so for figuring out the potential fp rate, an SE search is useful.
