dab isn't a word in English. It's a word that has many meanings in memetic, it could mean a certain kind of arm gesture, taking drugs, or as a word to mean anything you want it to mean at that time. It's an abuse of the language.
I found a cool public spam dataset dt.fee.unicamp.br/~tiago/smsspamcollection A strategy for improving smokey is to go through the dataset and make sure Smokey can classify it correctly.
@EricLeschinski SMS spam is quite far from the spam we see here, Smokey probably can't classify any of it correctly and updating it to do that would not bring any value for the task it's doing
Recently, I came across this question which is marked as duplicate of another question, but I don't see it.
Here is a screenshot.
We don't see the link to the duplicate question at the top of the question like this one here.
Is this a bug or something I am not aware of?
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +2 more: Test Troxin is works? by jujulidas on askubuntu.com
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +2 more: x4up.org/nugenix-side-effects/ by szkvvptwb on askubuntu.com
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +2 more: x4up.org/nugenix-side-effects/ by rajeshpadh on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in title, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title: Side Effects Of zeus muscle Capsules: by jeenjeq on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, repeated URL at end of long post: Abella Mayfair Review by Judtpatel on meta.SE
@AJ That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; use !!/watch-force if you really want to do that.
File "/usr/lib/python3.4/site-packages/sh.py", line 792, in wait
self.handle_command_exit_code(exit_code)
File "/usr/lib/python3.4/site-packages/sh.py", line 815, in handle_command_exit_code
raise exc
ValueError: Expecting value: line 1 column 1 (char 0)
2017-11-23 05:24:00.360058 UTC
File "/home/dragonlord/SmokeDetector/chatcommunicate.py", line 189, in watcher
message_id=message_id)
File "/home/dragonlord/SmokeDetector/chatcommunicate.py", line 258, in handle_commands
return subcmds[second_part_lower](**subcommand_parameters)
ok so I'm not sure what the heck is going on there, I was just testing to see if some bug was NG-exclusive but apparently I found something else in the process lol
if has_already_been_posted(post_data.site, post_data.post_id, post_data.title) and not is_false_positive(
(post_data.post_id, post_data.site)):
# Don't re-report if the post wasn't marked as a false positive. If it was marked as a false positive,
# this re-report might be attempting to correct that/fix a mistake/etc.
if GlobalVars.metasmoke_key is not None:
se_link = to_protocol_relative(post_data.post_url)
ms_link = "https://m.erwaysoftware.com/posts/by-url?url={}".format(se_link)
vs
if has_already_been_posted(post_data.site, post_data.post_id, post_data.title) and not is_false_positive(
(post_data.post_id, post_data.site)):
# Don't re-report if the post wasn't marked as a false positive. If it was marked as a false positive,
# this re-report might be attempting to correct that/fix a mistake/etc.
if GlobalVars.metasmoke_key is not None:
se_link = parsing.to_protocol_relative(post_data.post_url)
ms_link = "https://m.erwaysoftware.com/posts/by-url?url={}".format(se_link)
I have no recollection of fixing that, maybe angus did it
either way that parsing.to_protocol_relative is very obviously wrong
Recently, I came across this question which is marked as duplicate of another question, but I don't see it.
Here is a screenshot.
We don't see the link to the duplicate question at the top of the question like this one here.
Is this a bug or something I am not aware of?
