01/07 - Sublime Sunday!

Right?! That’s what I always say!

 

I was talking about the cat hair on black.

 

Yes, mine shows $0 - even though I've done work.

 

TV is down for major change to the way reviews get submitted
Also change server structure a bit so I can make a staging/dev version & not have to take it down for changes like this in the future.. though I think it still wont work with a huge rewrite to parts of linking so probs wont get used anyway now that I'm thinking about it

 

Sorry, I just know what my cat does with socks.

 

Great, thanks!! Wanted to make sure before bugging Kad.

@Kadauchi you may want to look into the Projected Earnings This Week (it's showing $0.00) on HIT Tracker. (I apologize if it's a known issue) Thanks a bunch!

 

Title: Survey about academic study ( 30 Secs ) | AcceptA Requester: Mclaren [A2YM12VE7K9G37] Contact TV: No Reviews TO: No Reviews TO2: No Reviews Reward: $0.25 Duration: 10 minutes Available: 1 Description: Give us your opinion about our survey Requirements: Total approved HITs LessThan 10000; Location EqualTo IN

These India only hits man.

 

So this wont be included on this roll-out, and I'll repost it again when more folks are around, but most likely future rejection reports will work like this:

• 1 week after a rejection has been reported an e-mail and/or notification will be generated for a user to come back and "confirm" the rejection.
  • If the user comes & confirms (or marks as overturned) - great, all is well & TV is getting accurate data.
  • If a user does not come back and confirm/overturn the rejection within 1 week (so 2 weeks from original report), the rejection mark will be left on the Reqs account (since we don't know if it was/was not overturned) but their account will be disabled from future access.

This is the only way I can think of to avoid the TO mass requester page destruction is to systemically weed out people who refuse to keep that kind of data up to date and accurate. I feel like a week is more than enough time for a Requester to figure out & overturn rejections while balancing the sporadic nature of Turking (ie, a user may legitimately disappear within a months time). So long as alerts are generated well (leaning towards e-mail, but I may do it straight up from TVJS so if you're logged into mTurk you're getting an alert to keep your shit updated) I don't see this as unfair, I don't want Requester accounts permanently brutalized unless they're legitimately crappy Reqs.

Any suggestions/improvements on this would be appreciated since I know its kinda heavy-handed :S

 

TurkerViewJS Updated to v6.0.0

CHANGELOG for v6.0.0: Introduced more server-side validation of data. You'll need to upgrade to 6.0.0 in order to leave reviews now, unfortunately this wont be obvious when attempting to leave reviews from the outdated version so please pass along the word. Rating communication now requires a comment, as does rating pay & hourly too far apart.

To review/install the full script check out TurkerView!​

 

I asked this the other day and never got an answer- but, with my computer blue screens and crashing over the last few months, and losing everything over and over- now that I think it's fixed and I am setting everything up again- isn't there someplace in the TV script that I am supposed to put my TH user name?

 

Nope, no need. For the purposes it needs to verify your TH/TV identity it checks with the websites themselves to see who you are, so as long as you're logged in to both there is no need to put your credentials into the userscript (which, in hindsight, was a terrible idea haha)

 

On the MTS hitfinder- for name and match on the include list- do I put the name of the requester, or RID, HIT name or GID or what in the name area or does it matter?

 

click that little star on the far left of the hit that you want to block and it will bring a box to let you block it.

 

or include

 

I am trying to add Requesters I want to include who have not posted today and it says "Nickname" and "what to match"- was wondering what to put in the what to match slot.