Depending on how long it stays in maintenance, it could be anywhere from 18-36+ months before the end of service. In the meantime, let's hope that nothing breaks too badly. But to be honest, based on how support has worked for the last 5+ years, the site seems to have been in maintenance for a while now.
You guys are all wrong. Let's not dabble in unsubstantiated conspiracy theories and wild speculation. If you look at the facts, it's very simple, really: MTurk will stop working exactly 7 days after the last person does a James Billings HIT. As long as we find a new victim every week and sacrifice them to James Billings, the site will stay online.
Also check this out: https://docs.aws.amazon.com/general/latest/gr/service-lifecycle.html MTurk is now in Maintenance stage, not in Sunset stage. So it could last for years, and it would eventually transition to Sunset stage, which should, on average, based on that page, give us another 12 months of MTurk. They also announce the end of support date once a service enters Sunset (here).
Also, they usually give more time before sending a service into maintenance, but due to all the issues the platform has been having lately, my guess is that they did the bare minimum to avoid an onboarding spike and keep server load manageable for the maintenance phase.
oh haha i remember them. They blocked me a few years ago. It was good when I had it . Once mturk finally shuts down, will this forum still work?
no no, this is good. it reduces the odds of the "mass illogical and unprovoked suspensions" upgrade by at least 3000%
Code: // ==UserScript== // @name Hide MTurk Banner // @namespace http://tampermonkey.net/ // @version 1.0 // @description Hides the yellow Amazon Mechanical Turk warning banner // @match https://worker.mturk.com/* // @grant none // ==/UserScript== (function() { 'use strict'; const hideBanner = () => { const divs = document.querySelectorAll('div'); divs.forEach(div => { // Checks for the specific text and ensures it's targeting the banner, not the whole page wrapper if (div.textContent.includes('Amazon Mechanical Turk is no longer accepting new customers') && div.textContent.length < 500) { div.style.display = 'none'; } }); }; // Run on initial load hideBanner(); // Catch it just in case the banner loads slightly after the rest of the page setTimeout(hideBanner, 1000); })(); just incase anyone gets tired of that banner, sure someone can make a better script
Code: // ==UserScript== // @name Nuke MTurk Banner // @namespace http://tampermonkey.net/ // @version 1.0 // @description Hides the yellow Amazon Mechanical Turk warning banner // @match https://worker.mturk.com/* // @grant GM_addStyle // ==/UserScript== GM_addStyle(`#maintenance_banner { display: none !important; }`);
Hold up, added one line. Use this, this will eliminate that tiny fraction of a second the banner shows up when you refresh the page: Code: // ==UserScript== // @name Nuke MTurk Banner // @namespace http://tampermonkey.net/ // @version 1.0 // @description Hides the yellow Amazon Mechanical Turk warning banner // @match https://worker.mturk.com/* // @run-at document-start // @grant GM_addStyle // ==/UserScript== GM_addStyle(`#maintenance_banner { display: none !important; }`);
It's hilarious how what is very likely the last ever "new feature" they've added to MTurk is a friggin' giant obnoxious banner at the top of every page that you can't even dismiss. Just one final "fuck you" to all of us.
most likely everyone who turks is asleep, but if theres anyone on who knows how to do stuff on mts catcher, please let me know.
i was trying to find out if you could limit the amount of hits from a batch that are grabbed, say 5 instead off the full 25 queue, @AlexZ already told me you cant. QBC finally full broke on me and getting a hold of CT is probably not going to happen, so now im very sad and trying to limp through VRAPI.
i was trying to find out if you could limit the amount of hits from a batch that are grabbed, say 5 instead off the full 25 queue, @AlexZ already told me you cant. QBC finally full broke on me and getting a hold of CT is probably not going to happen, so now im very sad and trying to limp through VRAPI.
