[Script] Worker.mturk Overwatch Script

@Ethraiel Hello, I'm having an issue where every time I load OW, an instance of TO is attached to a previous HIT.

Spoiler: Example of issue. Using latest Chrome build and TO extension.

 

Im gonna start working backward here and answer the last question first, or attempt to anyway. I would try changing the script running order so that overwatch is after TO... let me know if that helps

edit @RicanGuy86 i kept repeating the word "extention" in my head and realized you cant do what i mentioned with the extension(to my knowledge), i'll have to spend some time playing around with it because i've been using kads TO script for a while now. I'll let you know if i can figure something out.

 

when you're on the page can you open up the console (ctrl+shift+j) and tell me what you see? or take a screenshot?

 

This will be added, the length is important so I'll have to fix that. you'd think amazon would keep it to no more than 2 possible lengths but i guess not thanks for the info.

 

Sorry I got this working now, well it was working Sunday anyway. I believe the problem was with my computer not the script

 

im assuming "error handling" is still checked? if you have the time open up OW then the console (ctrl+shift+j) then log yourself out on another page, then tell me what you see please

 

Thanks so much. I've been using the TO extension for a while now, and I don't think it's something I need when using something like OW. I think I may just remove it being that there are other ways to obtain TO info.

Thank, again.

 

Ha, I just saw your reply and the next thing I tried to add to OW had a length of 12.
IPSoft AWS Account (AG5D2IURXS69)

 

Thanks

 

Still gonna do some experiments, shouldn't expect people to have to uninstall any TO script or extension... thanks for letting me know what was happening

 

I had error handling unchecked. Would you like the results with or without it checked?

 

If you have it unchecked the script will not check that you're logged in (among other things)... check the box and try to log out, you should be alerted

 

Keeps telling me I'm logged out. Logged in and out several times, any ideas?

 

There've been some issues with the captcha loggin, at least it was messing with me a bit yesterday. Im writing another update, and kad helped me find a new (better) way to track the logged status so im gonna try to get that out as soon as i can.
(also you can turn off error handling in the settings and those failures should be silent, you might want to watch the console as you run it like that at first)

 

Didn't do anything outside of logging off and closing all Chrome windows. Seems to be working again. Will keep an eye on the issue and report if it happens again.

Thanks, this is a fine piece of work!

 

I get this when getting PREs on the worker.com site.

 

I am grateful for this script, but I think I may not fully understand how it operates.
Example:
Right now, ROC-NLP-RESEARCH hits are up. I can see them on worker.mturk.com. I have three queries which, I think, should be triggering a response from OW: two search strings "roc" and "ROC-NLP-RESEARCH". The third is the actual requester ID. I don't always have these three, I am just trying to get a response from OW.

OW should be alerting me that those hits are there, but it is not. I don't understand why it is not. The script is working, as it just alerted me to CR's a few minutes ago and the last scrape time is updating. But, why is it not seeing that one requester? Should "Search All" be the first thing I hit when I open OW? Is it keeping data between sessions?

Thanks

 

Yes using search all when you start is the best way to quickly search through all HITs you qualify for, the ROCs should pop up no matter what page they're on, as OW just searches the "latest HITs" page. It also normally(not search all) includes HITs you dont qual for which means HITs can be pushed from that first page fairly quickly.

 

So there seems to be a reoccurring issue of the TTS dying on overwatch until you reboot (actually you might be able to completely kill chrome but I have an SSD so I just reboot).

Is that a known issue for you? It sucks when TTS dies

 

I havent had that happen, but i am away from my computer fairly often and might've just not noticed. Does it happen after a specific amount of time? Have you opened up your console to see if there are any errors when you notice it doing that? that might be helpful (though might not )