« first day (3914 days earlier)      last day (202 days later) » 

17:00
fp feedback received on [MS] Calculate Frame by Frame VMAF‭
!!/blacklist-number +39 351 222 3051
@SmokeDetector tpu- No affiliation disclosed.
Cow
Cow
@Vickel hahaha
Cow
Cow
@GeneralGrievance confused now, tpu because it's disclosed?
@Cow Because there wasn't any. There still isn't.
Cow
Cow
@GeneralGrievance ok I think I understand now
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to murder efficiently as an assassin?‭ by Sparky‭ on gaming.SE
Cow
Cow
@DavidPostill undisclosed affiliated in the last link: superuser.com/a/1851378/1878868
@SmokeDetector tp-
17:18
I don't know why this guy doesn't just say "from my website" instead of "the following website"...
Cow
Cow
yeah that's pretty weird
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad asn for hostname in title (2): Promote Your Ads Free: Adult, Escorts, Dating & Hookup Opportunities! - XposeHub.com‭ by ads_postify‭ on meta.SE
!!/watch- xposehub\.com
17:25
PR#12505 ("Vickel: Watch xposehub\.com") opened by SmokeDetector
!!/approve 12505
!!/watch- xposehub(?!\.com)
PR#12506 ("Vickel: Watch xposehub(?!\.com)") opened by SmokeDetector
17:27
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Vairt Real Estate Investment In The USA?‭ by Vairt Real EState‭ on meta.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Vairt Real Estate Investment In The USA?‭ by Vairt Real EState‭ on meta.SE
[ SmokeDetector | MS ] Potentially bad keyword in body, blacklisted user (73): Vairt Real Estate Investment In The USA?‭ by Vairt Real EState‭ on meta.SE
Cow
Cow
????
rofl
Oops?
[ SmokeDetector | MS ] Manually reported answer (batch report: post 1 out of 4) (93): How to create custom API for company and customer creation in Magento 2‭ by Shivani Nayyar‭ on magento.SE
[ SmokeDetector | MS ] Manually reported answer (batch report: post 2 out of 4) (93): Magento2: How to create custom API to get all product details of specific category?‭ by Shivani Nayyar‭ on magento.SE
[ SmokeDetector | MS ] Manually reported answer (batch report: post 3 out of 4) (93): Install Facebook Pixel Tracking‭ by Shivani Nayyar‭ on magento.SE
[ SmokeDetector | MS ] Manually reported answer (batch report: post 4 out of 4) (93): How to install Google TAG Manager (GTM) to Magento 1.9.2 without extension?‭ by Shivani Nayyar‭ on magento.SE
17:28
@cocomac I tried flagging+reporting it from AdvancedFlagging but I was getting a connection error. Seems the report did go through, after all
You also reported it in the room. And smokey was apparently a bit slow - it also picked it up. For a total of 3 reports.
Cow
Cow
@VLAZ all reported by you roflmao
It's dropped at least one of my commands today as well.
Cow
Cow
@SmokeDetector k
17:31
@Cow Huh? Yeah, seems so in FIRE. But the 3 MS reports are attributed differently 1. by me 2. by cocomac 3. by Smokey
Cow
Cow
@VLAZ loool
glitch in the matrix
I did !!/report on the post, so the one by me makes sense, although ideally the SD one would have been first...
@Cow No, it's a feature. So nobody feels left behind.
Cow
Cow
@VLAZ that's smart, family edition
17:34
!!/approve 12506
!!/blacklist-website- vairt\.com
PR#12507 ("Vickel: Blacklist vairt\.com") opened by SmokeDetector
now 5,0,0
Keep in mind, that doesn't count all the Discussion posts they've made.
Cow
Cow
17:38
more like 30:0:0
:D
Cow
Cow
17:55
moo
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Prayer to attain a religious guru or guide?‭ by a deleted user on hinduism.SE
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (160): Photographing human iris without reflections‭ by Hallumbrina Arrbrump‭ on photo.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): How to Make Vertical Slick Slider to Show Next Slide's Bottom Part Only‭ by Nuriddin Gulamov‭ on stackoverflow.com
18:10
!!/approve 12507
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body, potentially bad keyword in title (96): spiritual talismans and magic rings ✆"+256740608727 fiji new zealand‭ by azaan Bilal‭ on stackoverflow.com
!!/blacklist-number +256740608727
@JeffSchaller A normalized version, {{'256740608727'}}, 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 256740608727 to determine which entries on the number lists match that pattern, which would tell you: Matched by +256740608727 on line 3620 of watched_numbers.txt: 256740608727 found normalized
Cow
Cow
18:13
sdc watch- SPIRITUAL[\W_]*+TALISMAN[\W_]*+RINGS
PR#12508 ("Cow: Watch SPIRITUAL[\W_]*+TALISMAN[\W_]*+RINGS") opened by SmokeDetector
Interesting set of contributors there...
Cow
Cow
hm?
18:15
!!/approve 12508
@Cow Same 2 people doing those q&a's.
Cow
Cow
hmm
Hmmmm
sock puppet?
that's weird
!!/watch paradox[\W]*+recovery[\W]*+wizard
@Vickel You don't have blacklist manager privileges, but I've created PR#12509 for you.
18:27
PR#12509 ("Vickel: Watch paradox[\W]*+recovery[\W]*+wizard") opened by SmokeDetector
!!/approve 12509
18:41
[ SmokeDetector | MS ] Manually reported answer (93): redirect to page#about using symfony&twig‭ by odardila‭ on stackoverflow.com
!!/watch- tumaquinaya\.com
PR#12510 ("Vickel: Watch tumaquinaya\.com") opened by SmokeDetector
^ bulldozers :)
!!/watch- tumaquinaya(?!\.com)
PR#12511 ("Vickel: Watch tumaquinaya(?!\.com)") opened by SmokeDetector
18:47
[ SmokeDetector | MS ] Pattern-matching website in body, potentially bad keyword in body (96): Fake or legit trading platoforms?‭ by Terrance‭ on ethereum.SE
!!/approve 12510
!!/approve 12511
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Comment demander poliment à une femme ✏️‭ by LPH‭ on french.SE
teward/Cerberus: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 1e3e87ebb8 (SmokeDetector: Merge pull request #12511 from Charcoal-SE/auto-blacklist-1722883553) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 98710.
19:07
[ SmokeDetector | MS ] Blacklisted user (72): How to solve GB Whatsapp banned issue?‭ by farhan ali‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to connect GB Whatsapp with Pc?‭ by farhan ali‭ on superuser.com
19:54
tpu- feedback received on [MS] How to connect GB Whatsapp with Pc?‭
Cow
Cow
@SmokeDetector user deleted their user m.erwaysoftware.com/posts/uid/stackoverflow/78836073 and created a new to start posting spam again
I'm off to bed
o/
20:08
[ SmokeDetector | MS ] Offensive body detected, offensive title detected (103): Here's another piece of shit LaTeX‭ by M.G.Poirot‭ on tex.SE
@SmokeDetector tpu-
20:22
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Finding minimum value of function that returns 1‭ by Faruk Ibrahimovic‭ on quantumcomputing.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, username similar to website in answer (75): Problem with Send email - APP WP Mail SMTP by WPForm - Wordpress‭ by Al-Fatima Quran Academy‭ on stackoverflow.com
@SmokeDetector naa-
[ SmokeDetector | MS ] Link at beginning of body, potentially bad ip for hostname in body (47): What design software was used to create rashguards like these?‭ by eric priest‭ on graphicdesign.SE
Makyen/EC2-linux: Executing automatic scheduled reboot.
!!/watch- rashyhub\.com
21:15
@SmokeDetector Not sure. Could be legitimate.
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)
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (160): Raspberry Pi Camera Module, Time Lapse Photography‭ by Hallumbrina Arrbrump‭ on raspberrypi.SE
21:48
@SmokeDetector tpu-
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (160): Can photography or film have its own new type of aura?‭ by Hallumbrina Arrbrump‭ on philosophy.SE
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (160): How is a multi-angle scene filmed?‭ by Hallumbrina Arrbrump‭ on video.SE
@SmokeDetector tpu-
!!/watch- modyedge\.com
22:37
!!/watch (?-i:^Hallumbrina Arrbrump$)
@Fastnlight User is not blacklisted (26647247 on stackoverflow.com).
!!/watch- grandnewswire\.com
PR#12512 ("Fastnlight: Watch grandnewswire\.com") opened by SmokeDetector
Actually, is 8/0/0, with no other SE users by that name
!!/blacklist-keyword (?-i:^Hallumbrina Arrbrump$)
!!/approve 12512
@JeffSchaller I'm pretty sure there's a username blacklist (!!/blacklist-username [regex]), which is only tested against usernames and has no bookending (\b)
22:45
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on 678d40a by SmokeDetector in the master branch
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on 678d40a by SmokeDetector in the master branch
Looks like a blacklister needs to run !!/unwatch (?-i:^Hallumbrina Arrbrump$) to fix that issue
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Javascript How to get first three characters of a string‭ by frances cannolly‭ on stackoverflow.com
!!/watch- Cyberpoint[\W_]*+Recovery
PR#12513 ("Fastnlight: Watch Cyberpoint[\W_]*+Recovery") opened by SmokeDetector
!!/bisect cyber point recovery (.) com
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.12): failure on a5bfbf5 by SmokeDetector in the auto-blacklist-1722898161 branch for PR #12513
@Fastnlight Matched by c[\W_]*+y[\W_]*+b[\W_]*+e[\W_]*+r[\W_]*+p[\W_]*+o[\W_]*+i[\W_]*+n[\W_]*+t[\W_]*+r[\W_]*+e[\W_]*+c[\W_]*+o[\W_]*+v[\W_]*+e[\W_]*+r[\W_]*+y[\W_]*+(?:d[\W_]*+o[\W_]*+t[\W_]*+)?c[\W_]*+o[\W_]*+m(?# obfuscated cyberpointrecovery.com) on line 64457 of watched_keywords.txt
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.8): failure on a5bfbf5 by SmokeDetector in the auto-blacklist-1722898161 branch for PR #12513
22:55
!!/blacklist-keyword- c[\W_]*+y[\W_]*+b[\W_]*+e[\W_]*+r[\W_]*+p[\W_]*+o[\W_]*+i[\W_]*+n[\W_]*+t[\W_]*+r[\W_]*+e[\W_]*+c[\W_]*+o[\W_]*+v[\W_]*+e[\W_]*+r[\W_]*+y[\W_]*+(?:d[\W_]*+o[\W_]*+t[\W_]*+)?c[\W_]*+o[\W_]*+m(?# obfuscated cyberpointrecovery.com)
PR#12514 ("Fastnlight: Blacklist c[\W_]*+y[\W_]*+b[\W_]*+e[\W_]*+r[\W_]*+p[\W_]*+o[\W_]*+i[\W_]*+n[\W_]*+t[\W_]*+r[\W_]*+e[\W_]*+c[\W_]*+o[\W_]*+v[\W_]*+e[\W_]*+r[\W_]*+y[\W_]*+(?:d[\W_]*+o[\W_]*+t[\W_]*+)?c[\W_]*+o[\W_]*+m(?# obfuscated cyberpointrecovery.com)") opened by SmokeDetector
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.8): failure on cd29d57 by SmokeDetector in the auto-blacklist-1722898523 branch for PR #12514
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.12): failure on cd29d57 by SmokeDetector in the auto-blacklist-1722898523 branch for PR #12514
Looks like all builds will fail until the (now blacklisted) watch is removed. Here's the command for blacklisters: !!/unwatch (?-i:^Hallumbrina Arrbrump$)
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Brightness options in Ubuntu 12.04 desktop missing ✏️‭ by Harsh Thakar‭ on askubuntu.com
!!/watch-number 00201040581277
@Vickel You don't have blacklist manager privileges, but I've created PR#12515 for you.
PR#12515 ("Vickel: Watch 00201040581277") opened by SmokeDetector
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.8): failure on c9f6e53 by SmokeDetector in the auto-blacklist-1722901694 branch for PR #12515
@Fastnlight looks like you're right
23:53
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.12): failure on c9f6e53 by SmokeDetector in the auto-blacklist-1722901694 branch for PR #12515
I would fork the repo, remove it, and make a PR, but it's much easier for a blacklister to run a simply command
Looks like that was my fault? Fixing first...
!!/unwatch (?-i:^Hallumbrina Arrbrump$)
@JeffSchaller No, SD (for some reason) didn't remove the watch you created when you blacklisted the username
Right! I assumed it would, so... that's odd. Thank you for teeing up the fix!
23:56
Wait, it did?
Maybe PR's got crossed up and it was re-merged?
Yes, that's it
So it's your fault! :)
Looks like it resolved conflicts by simply rebasing the PR. It should have (imo) merged it instead

« first day (3914 days earlier)      last day (202 days later) »