« first day (1815 days earlier)      last day (2008 days later) » 

6:00 PM
@ArtOfCode True, for collecting data for something like this (if it was possible to get deleted question data), i.e. where you're not trying for it to be human-interactive, it's quite reasonable to use a much slower request rate, particularly if you're trying not to impact other things (even just overall load on the SE API servers).
 
Point is moot since we can't actually use the API for this purpose, but 2 hours isn't actually that bad given that we wouldn't need to use the data right away anyway
 
[ SmokeDetector | MS ] Shortened url in answer (56): How to check if a list exists in Python ✏️ by a deleted user on stackoverflow.com
fp- by Erik the Outgolfer
 
@SmokeDetector Nope, points to the real docs.
 
6:18 PM
Why did the edit bump the previous revision? For this one:
15 mins ago, by SmokeDetector
[ SmokeDetector | MS ] Shortened url in answer (56): How to check if a list exists in Python ✏️ by a deleted user on stackoverflow.com
Shouldn't Smokey have seen the current revision, and used that rather than revision n-1 ?
 
it was edited after Smokey saw it
 
@ArtOfCode True (both points). As has been mentioned, it looks like both the creation and deletion dates are available from PostsWithDeleted in SEDE, or using one of the data dumps.
 
(and pretty sure because it did, btw)
 
SEDE it is... the data dumps are terrible for automation
 
Is there any convenient way to programmatically query SEDE, or do we need to scrape the page for results?
 
6:23 PM
@EriktheOutgolfer There was a new answer 4 minutes before the edit
 
that sounds irrelevant
it wasn't caught anyway
 
No, because it was the new answer that caused Smokey to scan the whole post.
 
yeah, still before the edit
it might've also been an edit to the question, or any of the answers
 
@Makyen You can get CSV results from SEDE queries
 
@CalvT Ah, that's the badger I think
 
6:26 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Security Package by Davidwestcoast on security.SE
 
I was wondering why the report pre-timed the edit, but assumed it was because my system clock was off
 
fp- by Erik the Outgolfer
 
I forgot the activity elsewhere could trigger a scan of associated content
 
I'm guessing it got reported in SOCVR first, and gunr2171 saw it and edited before it got reported here
 
[ SmokeDetector | MS ] Potentially bad keyword in title (1): Where to buy Kratom in Bonn? by docp on travel.SE (@JoErNanO)
 
6:28 PM
How asychronous are reports? Would we get a notification here 5 minutes after SOCVR?
 
It's the message rate limiter
 
the large delays are usually suffered by the Taverners :P
 
@EriktheOutgolfer They have a system delay if I recall correctly
@bertieb The message rate limiter is per domain, so as smokey only reports to SOCVR, there's practically no limit. However all chat.se messages go through the same limiter, which causes the delay
All the site specific rooms etc
 
Smokey only reports to SOCVR?
 
eh?
 
6:33 PM
@bertieb On chat.so right?
 
Oh, I see now
 
Yeah sorry it wasn't clear
 
No problem :)
I'm a bit confused at times by the relationships
Ever since I joined the Chearcoal Team, all the SE-wide emails come from "Stack Overflow"
 
@ArtOfCode Thanks. Obviously, I should investigate more prior to asking.
 
@bertieb no, SOBotics too
 
6:35 PM
Something something something, trilogy site
 
Oh true, I forgot about that one. However 2 rooms is a lot less than the rooms on chat.se
 
@EriktheOutgolfer @CalvT I didn't even know the SO rooms were hosted on a separate domain
shrug
 
most of them
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, repeated url at end of long post (101): Can I apply for a transit visa in Oman? by Vicky on travel.SE (@JoErNanO)
 
And I'm not sure why they are either
I'm not over in that direction that often :P
 
6:36 PM
there is a stackoverflow.com host here in chat.SE too
 
tpu- by bertieb
 
@bertieb There's chat.stackexchange.com, chat.stackoverflow.com, and chat.meta.stackexchange.com
 
But whyyyyyy :P
I mean...
(Okay, architecture, load-separating, separation etc but still)
 
There's 22 rooms on chat.se that Smokey reports to
 
@bertieb not sure about that either... I suspect it might be on purpose not for servers' sake, but for rep from other sites not to count
 
6:39 PM
@bertieb There are 3 rooms on chat.SO in which SD reports.
 
@Makyen And growing with each reply :P
I've got one room, one room... two rooms, two rooms!... three! Three rooms on chat.SO; going once, going twice...
 
not sure if chat.SO is subject to the same rate limits as chat.SE and chat.meta.SE, though
 
@EriktheOutgolfer As good an explanation as any :)
 
yeah, although it doesn't explain why the heck it's on an entirely separate server
and thus I also have to set the "quicker notifications" setting for all three servers!
 
I 'unno
I still wanna know why my emails come from SO now :P
There's probably a Meta about it
 
6:44 PM
@EriktheOutgolfer Yeah it is - it's the same software underneath
 
@bertieb rebranding
 
@CalvT but it's another server
 
!!/watch musafirevisa\.com
 
@EriktheOutgolfer Aren't all three separate servers?
 
6:45 PM
@CalvT I think so
 
@WELZ Ah, unrelated to joining a Team then?
 
SE is often substituted for SO nowadays...
 
Nope, they are switching their brand back to SO (because of teams and $) (this is all my opinion)
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, repeated url at end of long post, blacklisted user (170): Oman Visa for Russian Women by Vicky on travel.SE (@JoErNanO)
tpu- by K.Dᴀᴠɪs
 
All I know is that they are all totally separate from the main site, because when they did the freeze awhile back chat still worked
 
6:46 PM
not sure... I think it might even be that SO and SE are really two companies, one being a subsidiary of the other (although not sure which is which)
 
Ok thanks
 
@NobodyNada In case you are not aware, NobodyNada/Raspberry Pi last pinged MS 15 hours ago.
 
@Makyen it ran out of disk space. Fixed; thanks
 
np. I just happened to notice.
@ArtOfCode I suspect you're aware, but just in case you're not: ArtOfCode/TRINITY last pinged MS 2 days ago.
 
@bertieb I'm pretty sure it's just for historical reasons (cc @EriktheOutgolfer)
 
6:57 PM
chat was invented after SE, no?
(pretty sure chat was invented somewhere in 2010, while SE 1.0 existed prior to that)
yay, speculation
 
Restart: API quota is 19676.
 
!!/location
 
@EriktheOutgolfer teward/Solar Flare
@EriktheOutgolfer NobodyNada/Raspberry Pi
 
!!/standby rasp
 
[ SmokeDetector ] SmokeDetector started in standby mode at rev 9da4f89 (𝐢𝐁𝐮𝐠 ♦: Update .gitattributes) (running on NobodyNada/Raspberry Pi)
 
6:59 PM
@Henders Just in case you're not aware, Henders/EC2 last pinged MS 6 days ago.
 
@NobodyNada Fair enough!
 
@EriktheOutgolfer Based on this, it looks like there was originally chat.SO, chat.MSO, chat.SU, and chat.SF
Then they merged chat.SU and chat.SF with chat.SE when launching SE 2.0. They decided chat.SO should be left alone since it's huge, and chat.MSO should be left alone since it wasn't clear whether it belonged with SO or SE.
 
except that chat.meta.stackoverflow.com redirects to chat.meta.SE
 
If NobodyNada/Raspberry Pi comes out of standby again, it would be a good idea to !!/pull. The commit it's on is one that's know to have more issues (e.g. with excessive memory consumption) than latter commits. This might be a reason why it wasn't pinging MS.
 
hm, maybe we can do that now, but, eh, eh, eh...
 
7:07 PM
@Makyen Thanks; I'll pull right now.
 
NobodyNada/Raspberry Pi received failover signal.
 
!!/pull
 
!!/test textnow.vip
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-11: textnow.vip
Body - Position 0-11: textnow.vip
Username - Position 0-11: textnow.vip
 
um, where is NobodyNada/Raspberry Pi?
 
7:08 PM
Pulling
 
!!/test bluestacks.vip
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-14: bluestacks.vip
Body - Position 0-14: bluestacks.vip
Username - Position 0-14: bluestacks.vip
[ SmokeDetector ] SmokeDetector started at rev 5d8cde5 (SmokeDetector: Auto watch of musafirevisa\.com by K.Dᴀᴠɪs --autopull) (running on NobodyNada/Raspberry Pi, Python 3.5.3)
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-14: bluestacks.vip
Body - Position 0-14: bluestacks.vip
Username - Position 0-14: bluestacks.vip
 
!!/standby rasp
(pull is done)
 
👍
 
7:12 PM
!!/test inro.in
 
> Would not be caught as a post, title or username.
 
can we watch that inro.in domain? Not as confirmed spam domain but as potential spam domain?
 
never been caught, it seems
 
!!/watch inro\.in
 
7:15 PM
hmm...
 
@rene Watched keywords: anything is game, but be prepared to have it removed if circumstances require it.
 
for example, blacklisting is such a circumstance ;-P
 
@CalvT thx
 
@EriktheOutgolfer All joking aside, I think the primary issue being thought about there was the possibility of something that was watched producing excessive FP. :-)
In this case, the desired pattern is relatively simple, but long enough such that it's unlikely to generate FP. It also has no current hits on SE. Thus, the indicators are that it's unlikely to generate large quantities of FP.
 
@Makyen heh, it's a joke :P
 
7:24 PM
:-)
 
and then, Mak tried to cover up that he missed the joke...
(we all miss jokes)
 
No jokes allowed under the CoC ruling ...
 
not sure... pretty sure you mean jokes that might offend somebody if taken seriously
 
I'm already offended ...
 
[ SmokeDetector ] SmokeDetector started at rev fc221fd (SmokeDetector: Auto watch of inro\.in by Makyen --autopull) (running on teward/Solar Flare, Python 3.6.5)
Restart: API quota is 17683.
 
7:34 PM
@EriktheOutgolfer Actually, I was trying to make a joke out of missing the joke, but maybe that was missed. Or, maybe I missed the joke about the joke about missing the joke, or was that the joke about the joke about the joke about missing the joke. :-)
 
@Makyen in my experience, meta-jokes are null
also, you can't make a joke about something you don't know
if you miss something, you don't know it
also, if you still attempt to do that, it's then that you might actually offend people
 
[ SmokeDetector | MS ] Few unique characters in body (93): Removed Post - N/A ✏️ by Antonio Gaspari on stackoverflow.com
tp- by Erik the Outgolfer
[ SmokeDetector | MS ] Few unique characters in body, mostly dots in body, mostly dots in title (208): a.................a...........................a ✏️ by HanMah on stackoverflow.com
tp- by Erik the Outgolfer
 
!!/test-a downloader.vip
 
> Blacklisted website in answer
----------
Body - Position 0-14: downloader.vip
 
7:53 PM
@EriktheOutgolfer I'm not sure if you've switched from banter to being serious about the possibility that someone (you???) might have been offended by our previous exchange in the comment I'm replying to and your prior couple of comments. If you're offended, I apologize. It certainly wasn't my intent to offend.
 
@Makyen definitely not offended :P I was talking about the cons of meta-jokes and "tough luck" jokes over there :P
o_o
 
[ SmokeDetector | MS ] Username similar to website in answer (51): Is there any way to connect to the elastic search cluster using the rest client? by Tech Gabs on stackoverflow.com
 
8:20 PM
[ SmokeDetector | MS ] Bad keyword with email in body (66): Nikah and divorce by Shoclynn Williams on islam.SE
fp- by Erik the Outgolfer
 
@SmokeDetector More on-topic over Law.SE...
 
8:41 PM
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): scam with blockchain by devfar on bitcoin.SE
fp- by NobodyNada
 
I don't understand why people leave their legit emails in an unobscured way in a public website.
Well, I say unobscured way but I really mean at all
 
[ SmokeDetector | MS ] No whitespace in title (64): DirectoryNotFoundException by Vpanda on stackoverflow.com
fp- by K.Dᴀᴠɪs
 
how have I not discovered Infinifactory before now
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Car possession being threatened by Co-signer by Gainz on money.SE
 
9:14 PM
@ArtOfCode whispers Factoriooooooooooo
 
@bertieb Oh I've discovered that one alright :P
 
!!/watch myjawab\.com
 
@ArtOfCode Sweet 👍
I don't know why I feel the need to whisper it, but I do that a fair it it seems
Group chat from the other day :P
(not the person's real name, so no pii)
 
!!/watch tamilrockers\.cl
 
9:16 PM
 
9:28 PM
naa by bertieb
[ SmokeDetector | MS ] Bad pattern in url answer (69): cosmos db graph api how to check if exist and update edge? by Seb on stackoverflow.com
 
9:46 PM
[ SmokeDetector | MS ] Potentially bad keyword in username (1): Ideas for creating a "Drain / Siphon" magic spell ✏️ by openInvent on sound.SE
 
10:06 PM
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (30): View C++ output in terminal when executing Qt application (macOS) by ds3284 on stackoverflow.com
fp- by K.Dᴀᴠɪs
 
10:20 PM
[ SmokeDetector | MS ] Misleading link (12): Restore BIP44 HD wallet by user89294 on bitcoin.SE
fp- by Erik the Outgolfer
[ SmokeDetector | MS ] Potentially bad keyword in username (1): I want to see all my exchange linked deleted questions? by openInvent on meta.SE
fp- by Makyen
 
@SmokeDetector ig-
 
10:58 PM
!!/test musafirevisa.com
 
> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-16: musafirevisa.com
Title - musafirevisa.com NS suspicious ns59.domaincontrol.com.,ns60.domaincontrol.com.
Body - Position 0-16: musafirevisa.com
Body - musafirevisa.com NS suspicious ns59.domaincontrol.com.,ns60.domaincontrol.com.
Username - Position 0-16: musafirevisa.com
 
!!/test bandgap.co.uk
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username, potentially problematic ns configuration in body, potentially problematic ns configuration in title
----------
Title - Position 0-13: bandgap.co.uk
Title - Suspicious nameservers: all IP addresses for bandgap.co.uk are in set {'213.175.200.222'}
Body - Position 0-13: bandgap.co.uk
Body - Suspicious nameservers: all IP addresses for bandgap.co.uk are in set {'213.175.200.222'}
Username - Position 0-13: bandgap.co.uk
 
!!/test office-setup.co
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username, potentially problematic ns configuration in body, potentially problematic ns configuration in title
----------
Title - Position 0-15: office-setup.co
Title - Suspicious nameservers: all IP addresses for office-setup.co are in set {'162.215.252.26'}
Body - Position 0-15: office-setup.co
Body - Suspicious nameservers: all IP addresses for office-setup.co are in set {'162.215.252.26'}
Username - Position 0-15: office-setup.co
 
11:00 PM
!!/test office-account.com
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-18: office-account.com
Body - Position 0-18: office-account.com
Username - Position 0-18: office-account.com
 
!!/test my-norton.net
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-13: my-norton.net
Body - Position 0-13: my-norton.net
Username - Position 0-13: my-norton.net
 
!!/test nortonkeyactivation.com
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-23: nortonkeyactivation.com
Body - Position 0-23: nortonkeyactivation.com
Username - Position 0-23: nortonkeyactivation.com
 
11:00 PM
!!/test kudoflow.com
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-12: kudoflow.com
Body - Position 0-12: kudoflow.com
Username - Position 0-12: kudoflow.com
 
!!/test hotelsafes.com
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 0-14: hotelsafes.com
Body - Position 0-14: hotelsafes.com
Username - Position 0-14: hotelsafes.com
[ SmokeDetector | MS ] Potentially bad keyword in username (1): Feature Request: See deleted posts by openInvent on meta.SE
fp- by Tetsuya Yamamoto
[ SmokeDetector | MS ] Manually reported answer (94): Java Mouse Click Dispatch Event by Atakan.P on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in username (1): How to use hexdump to show charaters in different presentations at the same time by openInvent on stackoverflow.com
fp- by ByteCommander
tpu- by ByteCommander on Java Mouse Click Dispatch Event [MS]
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (162): What does it mean to laugh like the letter k? by schniter on literature.SE (@Mithrandir)
tpu- by K.Dᴀᴠɪs
 
11:42 PM
@K.Dᴀᴠɪs I do, sorta
 
Well have fun with your spam-filled inbox asking for teh codez
 
gime moar
 

« first day (1815 days earlier)      last day (2008 days later) »