@EriktheOutgolfer Reporting NAA has no value. A single NAA/VLQ flag will put the post in the review queue. The only thing that additional NAA/VLQ flags do is increase the number of "Looks OK" review responses required in review for the post to exit the review queue (increased 1 "Looks OK" for each additional flag). Thus, additional flags are basically useless. If you want something that actually helps remove the post, then you need someone to go to the review queue, find the review, and act on it.
Thus, as far as flags go, having a single person flag the post is basically just as good as having several. Given that NAA flags are not automatically raised through the tools most people use to review SD reports, it's even more worthless to report such answers to SD.
@Makyen it's just that feeling: "we, uh, managed to catch only one of two NAAs on the same question by the same user", then you want to pop it like bubblewrap :P
Traceback (most recent call last):
File "/home/ubuntu/charcoal/SmokeDetector/tasks.py", line 37, in f
func(*args, **kwargs)
File "/home/ubuntu/charcoal/SmokeDetector/metasmoke.py", line 82, in check_last_pingtime
"forcing SmokeDetector restart to reset all sockets.", f=True)
File "/home/ubuntu/charcoal/SmokeDetector/helpers.py", line 56, in log
log_file(log_level, *args)
File "/home/ubuntu/charcoal/SmokeDetector/helpers.py", line 66, in log_file
if levels[log_level][0] < Helpers.min_log_level:
@iBug I am aware of 6 admins: thesecretmaster, tripleee, angussidney, Andy, ArtOfCode, Undo. None of them are currently in this room. Other users in this room might be able to help you.
@gparyani apparently I just created a new MS account and it requires human activation. I guess it'll be there next time I need it. If somebody who has access wants to mark it as a false positive, feel free.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, +2 more: intimidate faced by prisath on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +3 more: Regal Keto So how did I do it you by user10337020 on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +2 more: Verutum RX Rather opt for cheaper by liralopa on askubuntu.com
@iBug There’s no real reason the theme should be separate. You should be able to copy all the theme files into the website repo (making sure to add a link to the old repo in the commit for blame purposes) and have Art archive (rather than delete) the theme repo.
[ SmokeDetector | MS ] Url-only title, link at end of body, pattern-matching product name in body, pattern-matching website in body, pattern-matching website in title, +3 more: mummydiet.org/supreme-test-x-boost/ by jbgwrkom on askubuntu.com
The idea was to use it for multiple websites, but that never worked out and now it’s just difficult to edit the site since things are in two different repos.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, +4 more: Regal Keto when deciding on a diet by ossesapup on ham.SE
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, link at end of body, potentially bad ns for domain in body, +1 more: livesmartt.com/paltrox-rx/ by yobik on askubuntu.com
Yes; it can cause Smokey to get rate-limited, which is a big enough annoyance already. That, and that Smokey isn't a toy; it's a serious bot for helping to detect spam.
If anyone’s interested in contributing to my in-development UI for Helios (It currently offers read-only access, but I’d like to get write access set up at least for notifications), ask and I’ll get you a join link.
There’s a backend I created (maybe we should merge it with the actual Helios server cc @Andy) that uses SE auth to allow users to connect to Helios.
Currently it only supports creating notifications, but it would be fairly easy to add notification deletion. (users can only modify their notifications)
We’d need a way to check MS for privileges to allow (un-) watching/blacklisting.
