@SmokeDetector The linked page is, supposedly, an example of having subscriptions, which the OP wants to know if such are supported. I see nothing on the linked page about subscriptions. I do see a page which is clearly promotional, using various common tricks/techniques for hard selling and tricking people into purchasing (e.g. preventing navigation away from the page). This is spam, IMO.
@Makyen That pattern looks like it's already caught by Pattern-matching website in body, Potentially problematic ns configuration in answer, Pattern-matching website in answer, Potentially problematic ns configuration in body, Bad keyword in answer, and Bad keyword in body; append -force if you really want to do that.
WARNING: Could not copy key review_queue/3/unreviewed. cleanups/review_queue/3/unreviewed exists? false | review_queue/3/unreviewed exists? false
Error performing CleanRedisJob (Job ID: aceec9cf-92fa-4838-accb-c7b8b7406e1e) from Async(default) in 2699502.96ms: Redis::CommandError (ERR no such key):
/var/railsapps/metasmoke/shared/bundle/ruby/2.5.0/gems/redis-3.3.5/lib/redis/client.rb:121:in `call'
/var/railsapps/metasmoke/shared/bundle/ruby/2.5.0/gems/redis-3.3.5/lib/redis.rb:571:in `block in rename'
Redis::CommandError (MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.)
sort of an answer, but guy's advertising for his own Youtube channel, apparently. scifi.stackexchange.com/a/201895/98028 known spammer, or just a "please don't advertise your stuff" comment, edit out this part and let it be deleted through VLQ? (as it's... really VLQ.)
Oh, right. metasmoke generates presigned, expiring links to dumps 'cause they're huge and I want a good way to shut off access fast if some idiots tries to run my AWS bill up by downloading it a bunch.
@thesecretmaster Doable. If you get commands to dump to a file on the local filesystem, I can hook the rest up. Maybe make a GH issue, otherwise I'll forget.
MS has new changes to speed up a few slow routes (see end of message). If things aren't populating correctly (i.e. missing feedbacks), ping @thesecretmaster. This effects /reasons, /reasons/<id>, /posts, and /search_fast
@Shree That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Undo Thanks. It ... didn't do what I needed it to.
Also, re: redis bugs, currently feedbacks aren't populating correctly to the post lists in a few places. I'm aware, and will get to it tomorrow morning.
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +1 more (494): wellnesstrials.org/retinol-md-ca/ by user130936 on graphicdesign.SE
Also @Undo / @ArtOfCode I'm aware that I've just introduced some new stuff into the codebase, so if either of you have questions or want me to document anything or want a general outline of what's changed, let me know.
@thesecretmaster Is /fast_search a different route than just /search? Is it linked from somewhere, or do we need to type it manually? Hmmm... Typing it manually doesn't work, but the rails routing error page indicates that it understands /search_fast, which does go to a search page.
@Makyen 1) I lied, it's /search_fast not /fast_search, 2) It isn't linked from anywhere because eventually I'll just rip out /search and replace it 3) The page looks the same as /search, but it will be faster (once I un-break it)
@thesecretmaster It appears slightly different. It has "case sensitive" checkboxes. Would you entertain requests for additional functionality in search?
This post looks to me like a spammer who forgotten to include a link (the end of the post is "please call or CLICK HERE".) I am a bit torn between "off-topic" and "spam" flag.
@Makyen Sure! The case_sensitive stuff was out of necessity -- PCRE is naturally case-sensitive, and so I had to prepend (?i) for case insensitivity, and I figured I might as well make it a check box.
@MartinSleziak why would anyone post that if it wasn't to promote the service they are promoting? it's out-and-out spam, the fact that it's incompetent doesn't change things
Fair point. I am bit careful with spam flags - since from what I've told they are also used for some algorithms that Stack Exchange users for spam detections.
@Shree That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@TetsuyaYamamoto No such command 'watch-accesscontrols\.com\.au'.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-11: f2style.com Username - Position 0-11: f2style.com Body - Position 0-11: f2style.com
@Mithrandir I concluded the exact opposite, and the response just says check out this shop -- there is no indication that they actually carry the requested products
[ 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, +1 more (589): garcinia-pro-zona/ by Debragree on wordpress.SE
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@SmokeDetector If a search on the shop's site resulted in finding the product requested, I'd agree that it was FP. But, I've tried searching on the linked site for the products requested in both the question this is answering and the question for the user's previous answer and found nothing. IMO, that makes both of this user's answers which have been reported by SD unsolicited and thus spam.
[ 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, +4 more (690): Praltrix dischem south africa by user369305 on meta.SE
1) By default, wrap the regex in (?s:), as that matches how . is interpreted in SD's watches and blacklists, checking entries/potential entries for those is a significant use of searching; might as well have that as a checkbox too, default applied.
2) Checkbox, default applied, for regexes to be bookended with \b. This will match the behavior in the watchlist and keyword blacklist. Maybe a "watchlist & keyword blacklist" checkbox.
3) Dates: allow the user to specify a range of dates to match. When adding a regex or making a change to a regex it's quite helpful to look at just posts after the regex was added, as it's no longer just looking at those posts that were otherwise caught. This is something that I look at by hand, but it takes considerable time.
4) Allow criteria to be selected to be OR instead of AND. This allows duplicating watchlist and keyword blacklist in Title, Body, and Username without needing to run 3 separate searches.
5) A second match criteria for Title, Body, Username, and Why. (I'm 95% interested in Body.) This allows much easier construction of a search that is "match A, but not match B". This can be quite useful for looking at criteria used in detections that are not just a single regex.
6) (more work) have available additional report data, an alternate report, or highlighted, that shows what matched the criteria (I mostly care what matched regexes). This is particularly helpful for adjusting regexes. It can be used to determine additional criteria that to be used to improve %TP. Currently, I do this by manually scanning through the search results.
I tried to do #6 with the JS Data Explorer, but managed to crash MS. I haven't retried no that we have a reboot button available, but I probably should.
I know that's quite a bit. Sorry about that. I've been intending to see about working on them and/or making some GitHub issues as Requests for Enhancements.
