@ByteCommander [Weights are automatically managed by MS based on the true positives/false positives, and the amount caught, on a scale of 0 - 100 true positive count, if more than 20 posts caught ](github.com/Charcoal-SE/metasmoke/blob/…)
Most of the recent posts seem to be around 150 on weight and 3 reasons. Using max rep 1 and setting 3 reasons, it is possible to create a flagging condition for the posts. Should at least help with some auto-flagging
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +5 more: healthflyup.com/luna-trim/ by cinuredd on askubuntu.com
room topic changed to Charcoal HQ: Where diamonds are made, smoke is detected, and we break things by developing on production. 90k true positives and counting. Handy links: charcoal-se.org, github.com/Charcoal-SE, charcoal-se.org/blaze, metasmoke.erwaysoftware.com [best-bad-practices] [corn-for-horse] [crazed-maniacs] [dev-on-prod] [everything-is-broken] [panic-driven-development] [plastic-knives] [programmatic-crowbars] [roadkill-pasta]
@Undo Yeah.. I could probably have articulated that a bit better. When I said 'actions', I was really thinking 'actions like that'. Responsibly reporting a site to whomever is relevant, of course, is not an issue.
I'll edit it to reflect that, since it's up on the starboard. If you're all uncomfortable with it being there - there's been a few people who have disagreed here - I'm happy to have the stars removed, as well.
@K.Dᴀᴠɪs Added m[au]st[eu]rbat(?:e|io?ng?) to watchlist
[ SmokeDetector ] SmokeDetector started at [rev 80424ca (SmokeDetector: Auto watch of m[au]st[eu]rbat(?:e|io?ng?) by K.Dᴀᴠɪs --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/80424ca) (running on teward/Solar Flare)
@K.Dᴀᴠɪs FIRE's user-perceived response time will depend on what you've done with your mouse. FIRE pre-fetches data for the post once you mouse-over the FIRE button. Thus, if you've waited a short time between moving the mouse over the FIRE button, then it's likely that FIRE has already made the requests which it has to wait for prior to displaying the popup.
Given the nature of SOBotics, it's more likely that you are moving your mouse pointer around the chat page in order to click on other bot's reports, just happening to go over FIRE buttons. Thus, it's more likely that the user-percieved performance of FIRE is better in SOBotics. Beyond that perception issue, no, there's no reason that FIRE is actually more responsive in SOBotics than here.
You can do an interactive rebase of the commit where the file appeared first, and change it manually there. Or there's some filter-branch command that should do it automatically which I never used
In Linux, or any other form of unix, os.execl and friends are a good choice for this -- you just need to re-exec sys.executable with the same parameters it was executed with last time (sys.argv, more or less) or any variant thereof if you need to inform your next incarnation that it's actually a ...
If the method in that answer (there's an alternative given for Windows, but I think you'd also need to start a different file because NTFS doesn't allow overwriting an open file) doesn't work, one can still manually restart there.
windows can surely have a program restart itself, otherwise programs like Chrome wouldn't be able to offer a "click this button to restart the program for an update" option
it's probably that the main process gets another one started up, exits, then the other process takes care of making the update happen, then restarts the original process from its updated source.
mohd.roslan***strong text***
