« first day (3776 days earlier)      last day (340 days later) » 

!!/watch iptolocation\.io
@Mast see my PR#10452 :)
@Vickel Oops.
21:24
!!/reject 10452 "Watch is good, but someone didn't notice the PR and forced the watch manually. Unfortunately this means the PR must be rejected."
@Mast I hit an error while trying to run that command; run !!/errorlogs for details.
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): How to retrieve WETH sent from Trust Wallet to binance.us wallet‭ by Jason Denney‭ on stackoverflow.com
@Mast Closed pull request #10452.
@SmokeDetector Yea, yea...
I'm human, unlike you.
But thanks for the reminder smokey.
21:35
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
@Vickel Thanks for reminding me, merging PRs which are already watched tend to cause issues so it's important we stay on top of things like this.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title (3): Where to buy authentic Patek Philippe in NYC?‭ by mark paul‭ on worldbuilding.SE
no problem for me, now the spam is locked
21:51
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How do I set initial value for ngx-intl-tel-input‭ by Reda El khechabi‭ on stackoverflow.com
!!/watch diamondsourcenyc\.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Trying to use react-player throws a Hydration error‭ by zahid zahid husssain‭ on stackoverflow.com
teward/Thoth: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 5ca9384c4d (SmokeDetector: Auto watch of diamondsourcenyc\.com by Mast) (running on teward/Thoth, Python 3.10.12)
Restart: API quota is 86462.
22:31
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): I am having a 500 server error on my script withdrawal page‭ by Crypto-talk‭ on stackoverflow.com
@Makyen Thanks, duly noted. I think I must have read "we’re not aiming to catch plagiarism" and automatically read the following tp as fp. But given that plagiarism isn't a target, why use tp unless the post is spammy/abusive? Could that not potentially confuse the algorithms that are trying to determine what is spam?
I've changed my feedback on the subject post.
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Backing up an Electrum wallet‭ by hannah‭ on bitcoin.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to send error from spring to react js‭ by user23691895‭ on stackoverflow.com
22:52
tpu- feedback received on [MS] Backing up an Electrum wallet‭
@SmokeDetector Needs edit by >2k user
At this point, I'm tempted to flag as r/a
@Nick Yes, that's possible. It goes back to the difference between the initial target of feedback being if there should be a system block on the content vs. what should be red flagged.
!!/blacklist-number- +1(323)9101605
@Makyen A normalized version, {{'13239101605'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 1(323) 9 1 0 1 6 0 5 to determine which entries on the number lists match that pattern, which would tell you: Matched by +1(323)9101605 on line 4174 of watched_numbers.txt: 13239101605 found normalized; 3239101605 found normalized
23:34
@Makyen Before my time I suspect... anyway, I'll use tp in future unless the guidance changes.
Thoughts on this MS report? /cc @Fastnlight. Why is it tpu...? I also see that the user account is gone (mod nuked, presumably). While the surrounding text is clearly abusive and violates the CoC, it's arguably salvageable.
@cocomac I voted tpu because although it could be salvaged, the abusive part is more than 50% of the content and it is directed at a specific person, not just swearing in general.
@cocomac I sent an R/A, because that was I think it is...
@cocomac I'd say it's too far gone, personally.
IOW: I'd be comfortable blocking that at the system level.
Fair enough. I'd agree that it should be blocked at the system-level and meets the R/A bar. I'm not convinced it is unrepairable (meaning tp), but... due to the abuse, I see why it could be tpu anyways.
23:45
@cocomac just one post with a nice collection like moron, lackies, STFU, d0uch3baggery, you sound like a tw@t

« first day (3776 days earlier)      last day (340 days later) »