« first day (301 days earlier)      last day (3519 days later) » 

3:30 AM
[ SmokeDetector ] Offensive title detected: Is “Whore” archaic in Australian English? on ell.stackexchange.com
 
3:54 AM
[ SmokeDetector ] All-caps title: TIME SERIES/PANEL ANALYSIS on stats.stackexchange.com
 
 
8 hours later…
11:55 AM
[ SmokeDetector ] All-caps title: WRITE THE ANSWERS USING C++ on programmers.stackexchange.com
 
12:32 PM
[ SmokeDetector ] All-caps title: TAMIL PHONETIC TYPING on askubuntu.com
[ SmokeDetector ] All-caps title: HTTP ERROR 503 SERVICE_UNAVAILABLE on stackoverflow.com
 
 
1 hour later…
1:48 PM
[ SmokeDetector ] All-caps title: PAST PERFECT OR PAST SIMPLE on ell.stackexchange.com
 
 
1 hour later…
 
5 hours later…
!!/stappit
 
[ SmokeDetector ] SmokeDetector started at rev 2cf9309 (@Undo)
 
@Undo ... that didn't work.
@Undo @ProgramFOX Proposing a new feature: instead of stappit, add !!/block {time} & !!/unblock. !!/block blocks Smokey for {time} minutes, and !!/unblock makes it post again.
 
8:27 PM
@Undo issues had to go bye-bye for a bit.
 
Huh?
 
Troll decided to troll our GH issues page.
 
... wonderful
 
ikr? :P
 
I didn't even know you could kill issues.
 
8:32 PM
It's in the settings page.
Everything should come back when it gets reenabled.
 
Yeah, it did.
I'm going to ask him to identify himself on SE, don't see anything inherently harmful in the first one.
 
@Undo Sure, however, I asked in the Tavern who's account it was -- no response.
The only places I posted that issue were here & the Tavern.
 
meh, if they keep it up I'll contact GitHub and see what they can do. Killing issues isn't a long-term solution.
 
I know.
 
I'm surprised that as owners we can't baleet issues.
 
8:42 PM
We should feature-request it.
 
how?
There isn't a meta.GitHub is there?
 
I think there's a GH repo.
Ooor... maybe not.
> For questions, bug reports, or feature requests, please email support@github.com.
Anyway, what do you think of github.com/Charcoal-SE/SmokeDetector/issues/16, @Undo?
 
we could probably do it, but it would almost certainly be easier just to make the autorunner recognize when it kills itself.
!!/stappit
~~stappit
 
I'm not sure how you would differentiate between them.
Oh, right, SD isn't in this room anymore.
 
@hichris123 exit codes, probably.
 
8:50 PM
!!/stappit
 
@hichris123 wait what?
Ohhhhh
 
@Undo I kinda suspended it, and I don't think it liked that... :P
 
:D
 
[ SmokeDetector ] SmokeDetector started at rev 2cf9309 (@Undo)
 
Hiya Smokey!
~~stappit
 
8:52 PM
!!/stappit
... give it a minute...
 
I killed it, want to test something
 
@Undo Only reason why I wouldn't do it that way is because then you'd have to manually restart it.
 
that's okay
a block would be better, but I don't plan on dying anytime soon.
 
[ SmokeDetector ] SmokeDetector started at rev 2cf9309 (@Undo)
 
test
It shouldn't take a minute
it's nearly instantaneous. (I'm logging new chat messages it sees)
!!/stappit
 
8:55 PM
[ SmokeDetector ] SmokeDetector started at rev 2cf9309 (@Undo)
 
aha
 
hmm?
 
so yeah, stappit works. Autostart script also works :P
goes to read about exit codes
If you want to work on a block thing, that'd be great. I don't really have time to.
 
Hmm, alright.
After I finish my homework. :P
 
[ SmokeDetector ] SmokeDetector started at rev 2cf9309 (@Undo)
 
9:01 PM
hi smokey
!!/stappit
 
Goodbye, cruel world
[ SmokeDetector ] SmokeDetector started at rev 2cf9309 (@Undo)
 
so close.
bah
 
9:16 PM
we need stappit in the tavern.
Anyone have perms in there?
Maybe give it to Bart..
 
Nope, stappit doesn't work in the Tavern.
^ thoughts, @Seth?
 
@hichris123 that needs fixing.
@hichris123 Looks good to me.
 
Alright, I'll work on fixes to these after homework.
 
@Seth no, they can come in here.
stappit would kill the bot period, the command only works in here.
 
9:31 PM
hm.
I suppose.
>
time.sleep(secs)

Suspend execution for the given number of seconds. The argument may be a floating point number to indicate a more precise sleep time. The actual suspension time may be less than that requested because any caught signal will terminate the sleep() following execution of that signal’s catching routine. Also, the suspension time may be longer than requested by an arbitrary amount because of the scheduling of other activity in the system.
might do it right there. (maybe)
 
Hmm, interesting idea. Though it would have to be on that thread...
 
I am such a terrible programmer :(
 
10:09 PM
@Undo still around?
Anyway, when you are, can you please pull this?
Oh, hiya @AnnonomusPenguin!
 
@hichris123 Hi!
Oy wat's new?
 
Why did you lock conversation?
 
'cause trolls
 
You should add a time limit to it so they can't stop it for 200000 minutes :P
 
10:15 PM
Unlocked.
@AnnonomusPenguin Planning on doing that, only implemented blocking with no time so far.
@AnnonomusPenguin Any thoughts on how you could make a timer count down, then do something, but at the same time be listening for messages?
 
@hichris123 I'd just store the UNIX-like timestamp (seconds since Unix-epox or whatever its called) and then compare that to the current time and the ban length
 
@AnnonomusPenguin But how? You could get the start time, compare it to the current... but wouldn't a while loop lock up the thread?
 
@hichris123 you wouldn't use a while loop :P
 
... what would you use then?
 
10:29 PM
@AnnonomusPenguin still here?
 
@hichris123 Not the prettiest but it works
The chart I mean
Makes sense?
 
hmmm... yeah, makes sense.
 
Any issues with it?
 
Instead of offloading the checking of messages to another thread, what would you think of just offloading the timer to another thread?
 
That is all one thread
That's just the call stack
I need to go. Be back in a little while
 
10:32 PM
cya.
@AnnonomusPenguin How would you keep track of time, though?
This is what I have so far, btw: github.com/Charcoal-SE/SmokeDetector/commit/…
 
@hichris123 simple. You don't use a timer
You store the time the ban ends. If the current time > the ban end time, then the ban is over. Otherwise, it is active
 
[ SmokeDetector ] All-caps title: GREY SCREEN WITH SPINNING WHEEL.HELP on apple.stackexchange.com
 
You don't realize how much you over-complicate things until you work with limited resources on a humble AVR chip that needs to do thousands of floating point operations a second (it really hurts).
Been there, done that, you don't need a timer :P
@hichris123 ^^^
Let me finish the code... also you should make the array of user IDs that are allowed into one string so it is easy to kick Undo out adaptable.
 
10:51 PM
@AnnonomusPenguin Sorry to be stupid, but... how?
In other news: I've gotten two upvotes on a CW answer on the behalf of the OP. :P stackoverflow.com/questions/21580011/…
@AnnonomusPenguin good idea
 
@hichris123 I'm cloning it now
 
@AnnonomusPenguin smart.
 
Pull request right now
Did you see the commit already? :P
 
merged.
@AnnonomusPenguin yup, I just looked at your profile and saw '4 secs ago'. :P
 
Cool!
Oy @Doorknob
 
11:04 PM
Oy!
 
@AnnonomusPenguin here's my thought: allow a custom time up to 4 hours. If that is not specified or it's greater than 4 hours, default to 15 min.
 
@hichris123 4 hours? Then you can easily make a bot to do that with it hard to be noticed except with server logs.
 
Oy @Doorknob.
 
Oh wait only trusted users can do that, right?
 
yeah.
 
11:05 PM
Nevermind
sigh me needs coffee
 
Wow: it's been this long and this was the first commit for a Charcoal project? Wow, I need to catch up.
 
yup. ;)
@AnnonomusPenguin What would I cast the string to in order to add it to gmtime()?
 
@hichris123 Do you just mean how I got the gmtime() + 900?
It returns the number of seconds (UTC time) since the Unix Epox (Jan/1/1970)
 
@AnnonomusPenguin Well, I'd be taking a substring of ev to add to gmtime(). Would I just cast that substring to an int?
 
11:19 PM
Yes, it is an integer. I'm not sure about the type of integer, but it seems like that doesn't matter in python
So, if you got the string "/!! block 15" you would take the substring "15" and convert to the int 15 and add that value to gmtime() and assign that to whatever the variable is called (I can't remember)
@hichris ^
 
hmm, okay.
That doesn't seem to work: ideone.com/yBtjfS.
@AnnonomusPenguin ^
 
Wait, do we just want time @AnnonomusPenguin?
 
yeah
Ooh, time.time
 
yeah.
 
11:26 PM
Did you just fork it?
 
Hmm?
 
On Ideone?
 
Oh, I just edited it directly.
 
@hichris123 which forks it
 
ah.
 
11:27 PM
I saw that when I refreshed the page :)
So that works now, replace that function and try it again in the main code.
 
yup, gimme a sec.
 
11:44 PM
@hichris123 It's been way more than a second! :P
 
Yup, because I fail at Python.
@AnnonomusPenguin ^ look good?
yup, I think that works.
 
@hichris123 me more
That looks good
 
ok, I'm committing.
 
This is a big commitment!
 
[ SmokeDetector ] SmokeDetector started at rev 859a7ad (@Undo)
 
11:51 PM
oh, hiya @Undo.
Right on time.
 
that's on the blocking branch.
 
@Undo go pull again. ;P
 
... okay :P
 
11:51 PM
@Undo heh, I read that as "thread" at first and was confused
 
@AnnonomusPenguin ^^
 
Skeet-like move!
 
[ SmokeDetector ] SmokeDetector started at rev c6485eb (@Undo)
 
@Undo I did me first Charcoal commit
 
!!/block
 
11:52 PM
blocked
 
@AnnonomusPenguin but charcoal isn't a thing any more.
 
!!/unblock
 
@Undo I meant Charcoal-SE (the user)
 
... where are you?
!!/block
 
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/ubuntu/SmokeDetector/ChatExchange/chatexchange/browser.py", line 597, in _runner
    self.on_activity(json.loads(a))
  File "/home/ubuntu/SmokeDetector/ChatExchange/chatexchange/rooms.py", line 67, in on_activity
    event_callback(event, self._client)
  File "ws.py", line 88, in watcher
it's still running, but that happened. Looks like it killed the thread.
 
11:53 PM
oh, duh.
Pushed a fix.
 
@AnnonomusPenguin oh, yay!
 
[ SmokeDetector ] SmokeDetector started at rev dd19c8e (@Undo)
 
!!/block
 
blocked
 
!!/unblock
:(
 
11:55 PM
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/ubuntu/SmokeDetector/ChatExchange/chatexchange/browser.py", line 597, in _runner
    self.on_activity(json.loads(a))
  File "/home/ubuntu/SmokeDetector/ChatExchange/chatexchange/rooms.py", line 67, in on_activity
    event_callback(event, self._client)
 
wut.
Oh, I did that wrong... shakes fist
 
;)
 
pushed
 
[ SmokeDetector ] SmokeDetector started at rev 1236180 (@Undo)
 
!!/block
 
11:56 PM
blocked
 
Oooh an all-number short commit
 
!!/unblock
 
unblocked
 
yayz!
 
:D
@Undo yup
@Undo Do you think we should add the time it's going to block for or no?
 
11:58 PM
meh, might as well. Except that might give the troll a way to set a 'come-back-in-x-minutes-to-troll-more' alarm.
!!/block
 
blocked
 
!!/unblock
 
unblocked
 
@Undo That was my problem with it...
 
I'm gonna test it, this might be a little spammy.
:D
 
11:59 PM
heh, okay.
 

« first day (301 days earlier)      last day (3519 days later) »