Marked wrong for lack of niqqud
I was on mobile so it's kinda hard to report properly when niqqud cause problems on listening exercises, but I think this is the first time I've not just been marked as a typo, but actually wrong. Unless I'm seriously missing something here!
I'm on an iPad, and I literally don't have the means to write most of the niqqud or a dagesh or whatever that dot on the ש is called. I don't mind particularly being told I have typos for not using them, but it's a bit depressing to get marked wrong for it. Unless I'm going completely mad (possible!) the vowels and the dot on the ש are the only thing I can see that Duolingo would mark wrong here.
Hm... Maybe because ישנה could also mean 'sleeping' (feminine)? Still this is a pretty silly error and I'm sure the Hebrew team will fix it when they can :)
It's a known issue with the audio exercises, the team are trying to get Duolingo to fix this.
A known issue: the system sees רואֶה as being a different word to רואה, and in type what you hear exercises, it only accepts exactly what is said, not any best answer alternatives. We hope that the Duolingo developers can implement a rule which ignores nikud, or that they find some other workaround. In this case, I assume that the sheer number of nikud markings on the word mean that instead of being one "letter" out and having a "typo", it tells you you are several out and have a wrong answer. The only thing we can do here is disable audio exercises for this word, which we have done, but another Duolingo bug means that our disables don't seem to work!
Ahhh that explains it. I did wonder, with all those nikkud, if Duolingo was just overwhelmed! That was my best guess. I think it's the first time Duolingo has outright told me I'm wrong on an audio exercise (I mean, besides when I just plain made an actual error) instead of just telling me I have a typo.
"our disables don't seem to work"
Well... that's helpful 8o D'OH.
Thanks at least for the reassurance it wasn't just me... I did a double take at the screen when I got the message I'd got it wrong, and was paranoid I'd made some obvious error I was somehow managing to miss completely...