03/16 - Fork it Over Friday!

Title: To trust or not to trust?(~ 2 minutes) | Accept Requester: Maayan Katzir [A1YTYP1IG4ZUHK] Contact TV: [Hrly: $14.35] [Pay: 4.63] [Fast: null] [Comm: null] [Rej: 0] [ToS: 0] [Blk: 0] TO: [Pay: 4.54] [Fast: 5.00] [Comm: 5.00] [Fair: 5.00] [Reviews: 13] [ToS: 0] TO2: [Hrly: ---] [Pen: ---] [Res: ---] [Rec: ---] [Rej: 0] [ToS: 0] [Brk: 0] Reward: $0.50 Duration: 1 hour Available: 1 Description: Making trust and mistrust decisions as quickly and accurately as possible and get an additional bonus (~2$ - ~4$) depending on your performance in a ~25 minutes experiment Requirements: Total approved HITs GreaterThanOrEqualTo 100; Exc: [201169047-79000] DoesNotExist; HIT approval rate (%) GreaterThanOrEqualTo 95; Location In US

HIT exported from Mturk Suite v2.1.17​

 

I woke up just in time to watch all my Brian Z's expire.

 

Did anyone do the bullying messages? I can't get this google form to accept any format

 

So sleepy.

Good morning.

 

Currently, our team is working on fixing the submission mode on Google Forms and the HIT you were working on is currently closed. PLEASE SAVE YOUR ANSWERS! We will republish this HIT in a bit and you could paste them in again. Again, sorry for the inconvenience.

 

Scott Weathers [A317VTHPKTYI24] Take a Research Survey(~ 8 minutes) - $0.80 | PANDA

[36N0GER6UXHO05CMZ15WND91L65JGR]​

Fair

Unrated

Unrated

$9.14 / hour
00:05:15 / completion time

​

Pros:

Cons:
The pages on this survey were loading very slowly. It could have gone much faster if not for that. In case anyone was wondering excessive sighing and eye rolling does not made the pages load faster.

To read Scott Weathers's full profile check out TurkerView!​

 

Title: Social Psychology Study - 50 cents reward(~ 4 minutes) | Accept Requester: Bastian Jaeger [A2P7AUX7K3P5MU] Contact TV: [Hrly: $11.61] [Pay: 3.50] [Fast: null] [Comm: null] [Rej: 0] [ToS: 0] [Blk: 0] TO: [Pay: 3.60] [Fast: 5.00] [Comm: 5.00] [Fair: 5.00] [Reviews: 10] [ToS: 0] TO2: [Hrly: $30.00] [Pen: ---] [Res: ---] [Rec: 100% of 1] [Rej: 0] [ToS: 0] [Brk: 0] Reward: $0.50 Duration: 25 minutes Available: 1 Description: This is a study on hiring decisions. Requirements: Total approved HITs GreaterThanOrEqualTo 100; Exc: [2077829-77151] DoesNotExist; HIT approval rate (%) GreaterThanOrEqualTo 90; Location In US

HIT exported from Mturk Suite v2.1.17​

 

Good morning

 

I kept getting please use the correct format or whatever got annoyed and returned it to early for the crap especially when my que is full

 

Thanks. Where did you see that?

I ended up just coping them all to a pastebin and messaging her the link. Then I checked TO to see if there was an email address posted for her and saw she went on a rejection spree a while back...

 

Empty queue, finally

 

I feel loved now.

 

I messaged her because I was losing my mind. It was making the writing task much easier with the frustration I was feeling trying to do the HIT.

 

Yeah I'd much prefer TO used in that way than TV. No offense, but I doubt anyone knows the intentions of that Requester unless they replied back to a message and were just like "oh yeah, I thought that was a neat trick to fool people not paying attention into giving me free data, MWAHAHAHA" - which.. I suspect didn't happen.

Most timer issues are just human error, then get fixed, and then people using TV will do the work while people using TO will skip it. Which is the nice benefit of splitting forum posts & permanent Requester data. A "hey, this timer is borked don't do the HIT until the Req fixes it" alerts people of the immediate problem w/o having to permanently neg-rep the Requester for something that is most easily attributed to an understandable fork up / misunderstanding.

Can you earnestly tell me this isn't a pretty confusing set of questions to have back-to-back?


I'm sure you can parse which does which, but can you imagine some brand new Requester looking at those two things? I know when I first logged in (and granted the wording was a bit different) I thought the time allotment was the (~X minutes) guesstimate I'd seen on most HITs & expiration was the.. well, time to expire. Its not exactly perfectly clear which "help" line actually matches which question either given the copious amount of white space between... everything. Its pretty easy to make the same mistake even now.. and, IME, 90% of the Requesters I've seen making it go back and fix it.

Are Requesters who tell you to do the survey, get your code, then accept the hit & submit it scamming workers with their advice? No, they just don't know shit about the platform. But if you followed their instructions you'd submit more free data than the Requester would ever even know what to do with.