Not allowing typing questions

[Zyme]

I never did any userscripts but in this case i will really try it, because I really don’T want to use memrise at the moment and get words right (and repeat them again when it is way too late) just because I saw them. Thanks

[fillipka]

@08ovij

// ==UserScript==// @name Memrise All Typing // @namespace cooljingle (Aaron Miles) · GitHub @description All typing / no multiple choice when doing Memrise typing courses// @match http://www.memrise.com/course//garden/// @match http://www.memrise.com/garden/review/*// @version 0.1.2// @updateURL https://github.com/cooljingle/memrise-all-typing/raw/master/Memrise_All_Typing.user.js// @downloadURL https://github.com/cooljingle/memrise-all-typing/raw/master/Memrise_All_Typing.user.js// @grant none// ==/UserScript==

$(document).ready(function() {

//*****************************************************************************************************************************
//MEMRISE ALL TYPING
//-----------------------------------------------------------------------------------------------------------------------------
//This userscript prevents multiple choice from occuring in typing courses, replacing it with a typing prompt.
//You can configure the extent to which this happens by setting these values to true/false:
// INCLUDE_REVIEWS: suppresses multiple choice when reviewing an item which hasn’t been watered for a while.
// INCLUDE_MISTAKE_REVIEWS: suppresses multiple choice on items that reoccur after getting them wrong earlier in the session.
// INCLUDE_LEARNING: suppresses multiple choice on new items you are learning.
//*****************************************************************************************************************************

var INCLUDE_REVIEWS = true;
var INCLUDE_MISTAKE_REVIEWS = false;
var INCLUDE_LEARNING = false;

MEMRISE.garden.boxes.load = (function() {
var cached_function = MEMRISE.garden.boxes.load;
return function() {
if (INCLUDE_REVIEWS) {
enableAllTypingReviews();
}
if (INCLUDE_MISTAKE_REVIEWS) {
enableAllTypingMistakeReviews();
}
if (INCLUDE_LEARNING) {
enableAllTypingLearning();
}

    return cached_function.apply(this, arguments);
};

}());

function enableAllTypingReviews() {
MEMRISE.garden.session.box_factory.is_lowest_rung = function() {
return false;
};

MEMRISE.garden.session.box_factory.isTypingDisabled = function(e) {
    return false;
};

}

function enableAllTypingMistakeReviews() {
MEMRISE.garden.boxes.add_next = (function() {
var cached_function = MEMRISE.garden.boxes.add_next;
return function() {
makeMaybeTyping(arguments[0]);
return cached_function.apply(this, arguments);
};
}());
}

function enableAllTypingLearning() {
MEMRISE.garden.session.box_factory.make = (function() {
var cached_function = MEMRISE.garden.session.box_factory.make;
return function() {
var result = cached_function.apply(this, arguments);
if (arguments[0].learn_session_level) {
makeMaybeTyping(result);
}
return result;
};
}());
}

function makeMaybeTyping(box) {
if (box.template === “multiple_choice”) {
var boxCopy = jQuery.extend({}, box);
box.template = MEMRISE.garden.session.box_factory.makeMaybeTyping(boxCopy).template;
}
}

});

wow, thank you for this fix. love ya

[Ora9]

The thing you are referring to in your Croatian course is a known problem for hidden sentences. If you have a hidden single word, it should work fine. However, if you have two words or more, just don’t make it hidden and it should be accepted. (I know it’s not ideal, but I hope it still helps.)

Other than that, can’t wait for some official Memrise representative to tell us what’s going on. If it’s a bug, no problem, just tell us that you’re working on it and we’ll be patient. If it’s a feature that you’re testing… well, you can see that many people don’t like it (myself included), so please make it optional, so everyone could use the version they like better.

[xvg11]

…which would be okay for the app. But why the web?

I can’t imagine what their plan could be or what they’re thinking either. It’s just another in a series damaging changes that nobody wants.

[xvg11]

The thing you are referring to in your Croatian course is a known problem for hidden sentences.

Just for the record, that’s not my Croatian course, but another user’s who was reporting a problem with hidden alts not working suddenly with strict typing. But I’ve seen the same problem in courses I’m taking, where it seems to happen with single words too, and appears related to the presence of commas or parenthesis in the answers.

Other than that, can’t wait for some official Memrise representative to tell us what’s going on. If it’s a bug, no problem, just tell us that you’re working on it and we’ll be patient.

The problem is that they were caught deceiving us intentionally before, and have destroyed their own credibility and made it reasonable for us to doubt everything they say. Who would believe them now if they said it was just a bug? There is a principle in law called “falsus in uno, falsus in omnibus,” which means “false in one thing, false in everything,” and, it now applies to Memrise.

[DW7 (Meminence, Rank 15 &)]

These two posts are related:

Typed answers requested when NOT set up

and

Multiple Choice tests appearing seemingly randomly. CoolJingle’s “All Typing” userscript disabled

For information this is what @MemriseMatty replied with : We are aware of some changes that have arisen, which have affected some courses on Memrise, and hope to have more information on this soon. We have a team who will be posting an update on the community forum outlining the current situation regarding typing tests / tapping tests.

[xvg11]

Don’t forget us Memrise! Tell us what is going on, and what you will do to fix it.

I think it’s clear that they are ignoring us deliberately, based on orders from the top. A company as small as Memrise doesn’t ignore its users for more than a week by accident. They’ve been told to ignore our extremely numerous pings, and say nothing. I’ve also noticed that even the “language specialists” have given us the same stock answer as before with the “comma change”, “I’ll pass it on to the team,” when they respond to complaints in the official course forums that are somehow related to this change.

[xvg11]

We are aware of some changes that have arisen, which have affected some courses on Memrise, and hope to have more information on this soon.

That’s a classic delay and deflection response. Notice the use of the passive voice, “have arisen.”

We know that changes don’t “arise” by themselves. Someone changed things deliberately. They don’t have to “hope to have more information soon”, because they know right now exactly what they’ve done, and why. Nor do they need a “team who will post an update,” but just need to tell us the truth. I suspect that what they mean to say is that they find ignoring us is no longer tenable, so they have to formulate a way to spin this, and come up with a plausible sugar-coated response.

[abudabuman]

For information this is what @MemriseMatty replied with : We are aware of some changes that have arisen, which have affected some courses on Memrise, and hope to have more information on this soon. We have a team who will be posting an update on the community forum outlining the current situation regarding typing tests / tapping tests.

This is fine.
I think we should all be grateful this website has been around for as long as it has and not have unrealistic demands beyond that - this is not a “business” in the normal sense whereas we as customers can threaten to defect to the competitors or just leave - this is a “Startup” whose “Exit” is overdue. It’s a fruit that haven’t been sold beyond it’s ripeness time.

In other words, these people are a small group of super capable young entrepreneurs who were hoping to have the website and especially the app sold by now, a.k.a make an “EXIT” (like other platforms such as “WAYS”, “FACEBOOK” ect.).

Apparently that hasn’t happened thus far and they are stuck with this beautiful white elephant. I don’t think any of them planned on being attached to this thing as a steady job for so long.

Just to put things in perspective - I have contacted the Memrise team at around the time this “bug” came about asking about paying membership options: I coincidentally earned my Memimence badge and with it a 50% off offer. I just wanted to ask how I can pay since I couldn’t find the link once I clicked the screen.
I haven’t heard from them even after two emails basically saying I want to give them money.

Usually in a proper established happily running business they have a tech team, customer retention team and an even more dedicated and eager team (which unlike the others in some places works 24 hrs) for recruiting customers and following leads.

Apparently they were only concerned with acquiring customers at the beginning in order to have an attractive number to show potential buyers (of this startup). Now acquiring or retention of existing customers is only a liability to them.

So, as for me… I will definitely not become a paying memeber after this revelation and I will at the same time not keep any ill feelings towards these people only gratitude and hope it keeps on living with the minimum maintenance they put into it + be grateful for a capable smart community of users who come up with fixes such as the javascript one above

[alanh]

Interesting! I just got this one as a typing test in Spanish (Spain) 4: “¿tu hija quiere una educación?”

I was so surprised, I made a typing mistake in my answer and then got presented with it as a MC!

Anyone else getting typing tests (longer than 15 characters) now?

[Foorgol]

Hi alanh,
yes same here. I testet a phrases’ course just now. Behaviour seems to be back to normal (typing required even with long sentences). Hope it stays that way.

[xvg11]

I just compared their code again, and they made exactly one change; they removed the check that disabled typing answers longer than 15 characters.

[alanh]

Sounds like a conscious decision to put things back as they were, then. As Foorgol says, “hope it stays that way” now!

[allayr]

This is amazing! Thanks so much in taking the time to fix this. It is such a great help on your behalf.
Many many thanks for your kindness and generosity!

[Geil]

I wonder what may of prompted them to make the change to begin with? Perhaps they were getting feedback from users about getting answers wrong with a simple typo like hitting s instead of d because they are right next to each other on the keyboard etc… It can’t be that hard to write an algorithm that detects a range of typos and ignores it rather than fine tuning every sentence in the creation options.

[xvg11]

Yes, it was definitely a conscious decision, because changes don’t just “arise” in the code by themselves, contrary to what they would have us believe. They obviously have a plan, had meetings about it, and then sent out instructions to the developers and coders to implement their plan.

Why they’ve chosen to backtrack on this change, and once again not to be forthcoming with us, is a question that remains to be answered. But I don’t think that they’ve abandoned their plans altogether, but rather made a temporary tactical retreat.

[Zyme]

such an algorithm is probably impossible, because it would need to be able to decide whether it was a typo or a grammatical error. Often it is intended to be precise with the order of two letters or the accent, because it can change the meaning totally. And that’s true for every language. And to decide if it was just a typo that needs to be auto corrected or if the user just got it wrong is impossible for an algorithm. Only the user itself can know that.

So it is not just about making the mistake correct, it is about finding out if the user also knows what would have been correct.

But on-topic: Let’s hope it stays this way and it wasn’t just a first test that will be repeated or worse even implemented for some reason.

[ThomasMunro90]

Thanks so much!

[flamantrose]

For me, typing tests for more than 15-16 characters is currently back to normal. Without any extra script.

Hope that it stays that way!

[Ora9]

Everything back to normal here too, and nobody has been complaining that they still have the problem - so I guess we can conclude that it’s been fixed. Great!