@Undo there used to be a pii leak on dev. Now there isn't. That's a known bug, reported it a while back
At one point using the original™ HTML manip for private betas trick I was able to break into dev and it assigned me a different user somehow (unregistered account). I could see the email address and whatnot. But iirc that got fixed, or at least Shog did something to remove the PII. I told Oded about the possible PII leak of the bug chris just discovered, but I don't think there is a leak there since it didn't get fixed.
There was a time when one could roam around on dev without getting destroyed :p
Darkness. An app that lets you categorize close reviews with extra kewords. Like "easy", "not sure", "domain knowledge required", etc. Then others can go through them.
The current close process is a bit jerky because the workflow for easy closes and li-shall-have-to-read-through-the-entire-thing closes are different. This might be slowing things down
Basically, something to help expedite the close vote reviews would be nice.
(Darkness because it's dark when you close a room :P)
Oh, @ManishEarth, I figured out how to use PhantomJS to track the most recent questions coming in. I'm applying Doorknob's spam-checker to them. Now I just need to figure out how to post them to the Tavern, and I'm done.
I'm currently looking up how to connect phantom and python :P
I'm thinking something like we run the Phantom code from within Python, and the phantom code prints the site, postid, and title in a predictable form when it finds spam. Then we somehow detect these printings from Python and send them to the spam room.
r@server1:~/ChatExchange$ python test.py
Traceback (most recent call last):
File "test.py", line 1, in <module>
from ChatBrowser import *
File "/home/parker/ChatExchange/ChatBrowser.py", line 3, in <module>
from BeautifulSoup import *
ImportError: No module named BeautifulSoup
@Undo btw, all that os.environ crap in test.py is so that the script can remember passwords for me. Just for testing, all it does is take the stuff from environment variables and use it instead of prompting
Currently, the sendMessage() and postSomething()/getSomething() (sends a GET/POST request with in-built fkey management) are the three methods that you need. If you're going to run it for a long time, run updateFkey() every now and then
For ease of use, you can set the ChatExchangeU and ChatExchangeP environment variables to your credentials so that you don't have to enter them every time
@Undo I don't see where the part comes in with detecting bad kewords... I just see 'JAVA - Bad keyword': function(el, qTitle) { return /\d{10}|jquery|java/i.test(qTitle) },. Is it different from Doorknob's?
if 'seek' in 'those who seek shall find':
print('Success!')
but keep in mind that this matches a sequence of characters, not necessarily a whole word - for example, 'word' in 'swordsmith' is True. If you only want to match whole words, you ought to use regular expressions:
import re
def f...
@Undo Will that work ^? It seems like it just needs to be phrases, and not whole words, so that should work...
if 'seek' in 'those who seek shall find':
print('Success!')
but keep in mind that this matches a sequence of characters, not necessarily a whole word - for example, 'word' in 'swordsmith' is True. If you only want to match whole words, you ought to use regular expressions:
import re
def f...