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.

"Some Kanji in this list will not be studied"

weirdesky   May 5th, 2012 12:39p.m.

So I get this error every time I add a new list of words with rare kanji. However I have "Study all kanji in lists" and "Study rare kanji" checked off. For example, if you take a look at my words, if we go to "~様", it will say this is added, but it won't have a "prev" time, and the "next" time will always be 10 hours. Has anyone else encountered this problem?

I'm also reviewing almost entirely on the mobile application, so there be a problem with communication somehow as well.

Edit: Since I'm mentioning the iOS app, you guys have some not-Japanese kanji in here. Like under lists, the kanji you have down there for "My Lists" I've never seen before (especially with those two boxes), and the kanji over published too. Also, the kanji over Study and Account in Settings.

scott   May 7th, 2012 1:24p.m.

The message that some kanji won't be studied is only referring to kanji that by default are not added to the words; it has nothing to do with rare kanji. It has no effect on your studies though; when you study the lists they'll add properly. I just need to have it check the user settings before giving that warning. Will add that to the to do.

I'm not seeing this with '~様'. When I look at the word in your account, it says studied 11 hours ago (I guess it came up since then? On the mobile app or the site?).

The images were created for Chinese. We haven't gotten around to making icons for Japanese yet, but don't worry, we will before it's released!

weirdesky   May 7th, 2012 11:45p.m.

Oh, oops. The problem kanji is actually just "様". My bad. That one is perpetually due in 10 hours. I already know it, but I'm worried that that'll happen with a kanji I don't already know.

As for the kanji for the mobile app, that makes sense. Some of that may be tricky to find kanji for, though, because the Japanese use katakana for a lot of those concepts. :/

Another thing about the mobile app: there tend to be discrepencies in due counts between the mobile app and the web app (generally not by more than 10), even when I do a hard reset of the app (closing it in the switcher and reopening it), and occasionally there are words that seem to add themselves, but only the web app. In order to see them on the mobile app, I must first review them on the web app. Currently, the prefix 長~ is waiting to be reviewed for the first time on the web app, but has yet to appear on the mobile app.

scott   May 8th, 2012 1:55p.m.

Looking at 様, you're actually studying three items related to it: the component and two of the words (よう and さま). You keep studying the component, and that pushes the two words back, because they're the same base and the system tries to spread those out when giving you reviews. Have you been overpracticing the component 様 at all?

What you say about 長~ is more troubling though. It sounds like it simply got missed on a sync somehow and so the app doesn't see it. That really needs to be rock solid to make sure everything makes it to the app; if the sync misses something it won't see it until that item changes again (by studying it on the site for example), otherwise the app will never get it. Will look into it. I assume the discrepancy goes away if you clear all your local data and download anew, though?

weirdesky   May 9th, 2012 10:06p.m.

Oh, I didn't know that it would push back the introduction of a character like that if I had been practicing it a lot. I haven't been intentionally practicing it more than everything else, but those words are all really basic, so they showed up at the beginning of the JLPT 4 list, and I went through the entirety of it in a day.

I currently have about... 600 reviews stacked up. When I clear them up, I'll take a look at the web app, see if it's still there. If it is, I'll clear my local data and reinstall to check.

Another thing I've noticed that I think is related to this: I recently put in a stroke order correction for 匿. There was a problem with the strokes on the 右 inside there. I got an email back from George telling me they've been fixed. However, later, I ended up practicing that kanji on the mobile app, and it had the incorrect stroke order. However, when I tried it out on the main site (via scratchpad), it had the right stroke order. I think this is kind of related to the problem I have with new cards being stuck in limbo in web app land.

scott   May 11th, 2012 4:41p.m.

General data that applies to everyone like for vocab definitions, stroke orders, and decomps is actually updated with a slightly separate system than your user-specific data like how well you know something, or your custom definitions. That system is somewhat slower for those, being not as time-sensitive, but I'll add some code to try and figure out what's going on with those updates.

weirdesky   May 12th, 2012 1:09a.m.

So the problem got a lot worse. As far as I could tell, when I tried to add words to the mobile app, it added them to the web-app netherland instead. It built up over 200 new words in the web app only. This problem persisted through multiple resets of the application.
So I reinstalled from my computer. Sure enough, the problem went away, like you expected. 260 new words woooooooo (don't worry, they're all easy XD).

weirdesky   May 12th, 2012 1:10a.m.

Also, the Rare kanji switch for me defaults to off, even though it's on on the web app.

scott   May 13th, 2012 10:06p.m.

Hmm, and this was giving you grief after you had installed the latest update, 0.9.8? Or were you on an older version before by any chance? Also, next time you might try clearing local data (in the account settings view) rather than reinstalling the whole app.

I think there's a general bug with the settings. Nick can reproduce it but so far I haven't been able to. We're on the case!

I'll see if I can reproduce this loss of words in any way.

weirdesky   May 14th, 2012 4:19p.m.

Yeah, I actually got this particular problem immediately after installing 9.8 . If I have a big build up of words in the web app again, I'll just try that instead. Sounds a lot easier.

The problem's still happening, I think. It looks like I currently have a build up of 30 new words in the web app (or at least that's the difference in the two numbers, 554 and 584, with a new word that I've never seen at the front of the queue in web app and not the mobile app)

scott   May 14th, 2012 5:11p.m.

I'm working on a system to try and figure out where these discrepancies are coming from. We've got to make sure the syncing is just right. I'll let you know when that's set up.

weirdesky   May 14th, 2012 8:12p.m.

Sounds good.

weirdesky   May 14th, 2012 8:29p.m.

Secondary question: Why is this thread not being bumped by our posts?

nick   May 14th, 2012 11:58p.m.

Do you have the forum sort set to "Created" and not "Updated"?

weirdesky   May 15th, 2012 12:57a.m.

Hooooo didn't know that you could do that. Glad you told me how to fix that. It was getting awfully irritating to go searching for this thread XD

scott   May 15th, 2012 2:20a.m.

You can also click the checkbox in the upper right corner to get replies.

I was able to reproduce the bug where items weren't syncing to the app. Will work on getting the bug out tomorrow.

weirdesky   May 15th, 2012 3:20p.m.

Oh wow so many features in this forum I didn't know about XD It's great you reproduced the bug though. Was there something special you had to do to produce it? I'm curious what I was doing that brought it on. I'm assuming this wasn't a problem everyone was having.

scott   May 16th, 2012 1:55p.m.

Figured it out yesterday. It had to do with the system I built to handle people who have used multiple devices. The server is most efficient at picking up changes when you've only ever used one device, the way it indexes the changes, but once you add on a second device, it switches to another slightly more complicated system, and that system had the bug. It was mainly happening when you added a new word. The fix will go out with the next build.

I found a handful of other bugs while fixing this one too. Gotta get rid of all these soon!

weirdesky   May 16th, 2012 2:02p.m.

Alrighty. I'm looking forward to it.

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