Sorry, I stepped out for a bit. I think you're still writing the message with charcoal-colored glasses. You have to consider what it will mean to someone who is unfamiliar with all of the technical details and nuances of your system.
Or, perhaps more importantly, what it should mean.
> Charcoal project members cast <spam/abusive> flags on this post, but at least one subsequent reviewer isn't confident that's the right decision. Please review and undelete the post if necessary; see <info page> for more details.
^ @CodyGray that's the current wording; where do you think that falls down?
That's a big improvement. I guess I missed the final version.
Only quibble might be whether it matters that they were Charcoal project members. On the one hand, it isn't relevant and having that at the very beginning could throw people unfamiliar with the Charcoal project for a loop. On the other hand, it only takes once to become familiar enough with Charcoal for it not to be a stumbling block in the future.
Aye. I think it's probably better to err on the side of too much detail now, having cut it down some; if mods don't care that it was Charcoal, that's fine, but if they do then the info and links are there.
I don't think the fact that it's an automated flag is especially important. On the other hand, it's only one or two words you're adding in to the message, and I agree that most mods are not going to go digging through the profile to see that.
It's only important that it's an automated flag if you aren't making clear what the moderator is supposed to do in response to the flag. Since that's been largely addressed, the person who is raising it diminshes in importance.
You have to be careful when pointing out that things are automatic, because then the question for the reviewer becomes, "So...what am I supposed to do?"
@ArtOfCode If you can do so, it looks like the Redis server needs to be rebooted. I'm not sure if rebooting the Redis server is something that only Undo can do. Just clicking the "reboot" button doesn't appear to have solved the problem.
I agree that rebooting the Redis server really isn't something we want to be doing on a regular basis. Unfortunately, the current situation is that it's been necessary multiple times recently. Maybe have a process that monitors Redis for OOM and kills/restarts it?
That would also work. :-; I was under the impression that the logging it was providing was beneficial (along with the other stuff that was previously working (mostly)).
Should be back now, cc @thesecretmaster I shut Redis logging off for now, getting the OOM command error on every page. Looks like a memory limit on redis-logging isn't behaving right, killing requests instead of evicting oldest records.
If it really just needs more memory, it should be possible to create a file and use the file as swap space. While that's significantly slower than having actual RAM, it should be able to provide up to about an additional 6GB of virtual memory in a basic EC2 instance.
Expensive in $, or slow? I'd expect that it's not great wrt. speed, but it's better than running out of memory, if you need it. Obviously, it's significantly preferable to keep everything within the available RAM, but it's an option, if needed.
Yep. Mostly because we know the other Redis instance (on the same server) is going to grow, so we don't want logging to crowd it out in the near future
Post 1: Could not find data for this post in the API. It may already have been deleted. Post 2: Already recently reported [ [MS](https://m.erwaysoftware.com/posts/uid/academia/124999) ] Post 3: Already recently reported [ [MS](https://m.erwaysoftware.com/posts/uid/crafts/5909) ] Post 4: Already recently reported [ [MS](https://metasmoke.erwaysoftware.com/post/159723) ] Post 5: Could not find data for this post in the API. It may already have been deleted.
Post 1: Could not find data for this post in the API. It may already have been deleted. Post 2: Could not find data for this post in the API. It may already have been deleted. Post 3: Looks like spam but not reported: Post is bumped by community ♦️ Post 4: Looks like spam but not reported: Post is bumped by community ♦️ Post 5: Could not find data for this post in the API. It may already have been deleted.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +5 more (695): evaherbalist.com/cial-rx/ by vhnluuqq on askubuntu.com
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +5 more (788): evaherbalist.com/cial-rx/ by vhnluuqq on drupal.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body, +1 more (394): Careful steps while devouring Keto Life by Asolotorow on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body, pattern-matching website in body, +3 more (591): Keto Life Guarantee by waplzmjaiida on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (393): How To Sell Zephrofel by user133372 on graphicdesign.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (888): evaherbalist.com/cial-rx/ by pejsdiohk on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body, +1 more (394): What Is KETO LIFE and by PdfdAdgf on superuser.com
[ 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 product name in body, +3 more (594): behind the purgative is to build by user998650 on superuser.com
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link following arrow in body, +3 more (788): healthytalkz.com/seratopical-cream/ by mirzawook on apple.SE
@SmokeDetector For those curious, bisect says "Matched by (?:facebook|whatsapp|email|yahoo|twitter|skype|paypal|website|server|credit|account).{0,12}hack(?:er|ing)s?(?<!serversforhackers)(?#orig in blacklist 2018-09-08; 10TP/11FP to 2019-01-10; moved to watchlist) on line 7579 of watched_keywords.txt"
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad keyword in answer (179): Life size image in Photoshop by user133383 on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, potentially bad ip for hostname in body, +3 more (563): Keto Life Canada by user133383 on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, potentially bad asn for hostname in body (393): How Does It Luxe ClaireRX Works? by LuxeclaireRX on askubuntu.com
How is this answer a spam (or rude, or abusive)?
Screenshot for non 10K users:
Deleted screen:
Expanded View:
