Looks like the Great Firewall or something like it is preventing you from completely loading www.skritter.com because it is hosted on Google App Engine, which is periodically blocked. Try instead our mirror:

legacy.skritter.cn

This might also be caused by an internet filter, such as SafeEyes. If you have such a filter installed, try adding appspot.com to the list of allowed domains.

Does stroke strictness get weaker

夏普本   April 29th, 2013 3:15a.m.

I have noticed that words I have correctly written before, I am given considerably more wrong strokes before its marked incorrect or even so so. I would really like an option like stroke order strictness which would allow for automatic incorrect marking if any strokes were incorrect. At the moment it seems like it depends on how many strokes are in a character, so characters with 10+ strokes you can make loads of mistakes. Changing every word to wrong when skritter thinks I got it correct (even though I needed 2 or 3 attempts to get the first stroke) is quite tiresome.

nick   April 29th, 2013 3:59p.m.

We don't adjust the incorrect stroke threshold based on whether you learned the character before or not, just the number of strokes in the character.

If we were too strict about incorrect strokes, then we would frustratingly mark it as incorrect whenever a recognition problem occurred. I know on the iOS app we went through a lot of tuning until most users were satisfied with the thresholds, and I'd be loathe to retune it or offer an extra option that wouldn't be useful to most users. Is this on iOS, or on the web?

夏普本   April 29th, 2013 5:23p.m.

I don't know why you need extra attempts to write a character containing more strokes. If I know the character completely I never have any problem writing it, all the strokes are recognised with no problem. I get the feeling that if you write a stroke slightly out of position, this is not counted as one of your "allowed" mistakes? I don't really mind this, but so many characters I can make completely the wrong initial stroke and it gives me several chances.

I just feel that the recognition works very well and I very rarely come across a time when I feel I wrote the stroke correctly and it was not recognised, but I'm constantly finding characters that I can't write without seeing the first stroke, or making a couple of guesses at the first stroke and are being marked completely correct.

It feels like each character has 1 or 2 extra lives and I'd just like some way off not having them. If I genuinely thought I had written it correctly then i could still manually mark it as correct, but I hardly ever need to do that, yet I have to constantly manually mark them wrong because in real life I don't have these extra lives.

This is on iOS.

nick   April 29th, 2013 6:48p.m.

Hmm; I personally make recognition mistakes frequently enough, and I designed the thing, but maybe I'm biased towards poor fingermanship. Others' thoughts?

lindaepl   April 30th, 2013 9:00a.m.

Have you tried turning on raw squigs?

夏普本   April 30th, 2013 9:53a.m.

Yea I use raw squigs already.

lechuan   April 30th, 2013 10:03a.m.

I dragged the Stroke Order Strictness setting all the way to the right. I also use raw squigs.

Currently I tend to manually mark a character wrong (because I drew the wrong stroke oce or twice), more often than I manually mark a character right (because it failed to recognize a stroke I was drawing).

If there was an extra slider for Stroke Accuracy, I'd probably bump that up as well.

Frank Pereny   April 30th, 2013 2:58p.m.

I think I will crank up the stroke order as well, although I rarely have trouble with stroke order.

On a side note - does this affect any of the "cheats"?

I know many of you are guilty as I am writing 了 in a single stroke, 口 in 2 strokes, or the 辶 as a nice big squiggle.

Laspimon   May 1st, 2013 6:22a.m.

Now we are touching upon recognition errors, I just wanted to note (in case others have the same problem):
The last stroke of 走 in radical position (e.g. 趋) registers very poorly foor me, and has always done so.

Frank Pereny   May 1st, 2013 9:24a.m.

For Skritter purposes I write that stroke as a 横 and it recognizes it every time.

Hugh723   June 24th, 2013 7:17p.m.

I agree with the OP and have made anorher post about it before finding this one. Any hints needed to complete the word and it should be marked as wrong such as it would be in the real world or on a test.

Although this setting was likely by design to keep some users happy, there must be a strictness setting for users like us who are more strict on ourselves.

This forum is now read only. Please go to Skritter Discourse Forum instead to start a new conversation!