Hey, this is mainly towards @Kadauchi since you're developing MTS, but if anyone can help, please do. I've had this problem for a while now on FF where the HITFinder tab crashes 2-3times a day. I've had this issue in the past, a FF update fixed it, and then a subsequent update broke it again and it's been broken for a couple months now. I disabled every other extensions (had to live without an adblock for hours!!) except tampermonkey, and the crashes still happen. When I reload the tab, every extension is broken (except MTS), meaning I have to disable/enable them all (like, MTS doesn't show the colored row after the crash, meaning TVJS in TM doesn't work). Also has a funny unintended effect of reloading the same scripts multiple times on page I don't reload. Spoiler: Funny effect Anyway, I figured the problem is definitely how MTS and Firefox behave together, but I don't know how to read FF crash pages, so I don't understand what the problem could be nor what I could do to fix the problem. Would anyone happen to know something that could help me fix this?
The key is to stop using a shit browser run by a shit org and use.. a decent browser run by a shit org in Chrome, thanks.
It sounds like CT is helping kad with this as well or something anyways. Hopefully they figure it out
I prefer to have a semblance of privacy from our overlord... Also, I hate chrome and much prefer firefox (and have been using FF for like 15y, so old habits die hard).
Firefox is probably a better browser but less people use it among the mturk community at least so less support. Brave is still unironically good and @DarkChild still uses it I think. (chromium based)
More like I'm a monkey who can paste things.. FF says innerHTML is unsafe and inefficient.. and says to use.. jQuery to fix it Not making that up, btw https://developer.mozilla.org/en-US...Safely_inserting_external_content_into_a_page
Hmm, extra weird. Let's see if you can reproduce it when the test build comes out for v3 but I'm guessing the large majority of existing bugs will be fixed and a whole new set will appear.
Any approximate ETA for v3? (I hate that question myself, so sorry for asking it; just looking for a ballpark between weeks/months/years)
Sometime in May for the first test build which should only need a week or two of testing before it gets pushed is the plan. I'm wrapping up HIT exporting now which leaves HF/HC/HT. That sounds like a lot but it'll definitely be less work than getting all the MTurk DOM interactions done (MTS scripts, TVJS).
Maybe MTS has been taken off the extension store because it keeps crashing on my PC and they see it as a bad extension