Okay hear me out. Frequently I do just a few words here and there between tasks while working. After a certain timeout, it forgets any words that are half-complete and still in-progress, and I have to redo them.
You would think that redoing a few words is no big deal, right? Well actually it is. The problem is that the half of the word that I did earlier, I remember it perfectly, even if the first time around I missed it, because I just did it 2 hours ago. This has resulted in me burning words I donât actually know at all. This issue is directly impeding my learning.
I tried to get around this by blocking the timeout window with ABP, but this doesnât really solve the problem, the words still come back again. Itâs only 10 words or less that need to be saved either in cookies or in a database entry associated with my account, and I know for a fact there is nothing technically infeasible about this. There is more data in my user profile than this.
On mobile Iâm fine because I use Flaming Durtles which doesnât have this issue, it remembers my status no matter how long itâs been, and I can do words in smaller sets. Itâs only on web on desktop that this is a problem. Iâm desperate enough to solve this problem that Iâve considered building my own extension or even my own client using the API to get around it. But it feels like something that should be solved directly by Wanikani. Nobody enjoys or prefers the current timeout experience where progress is lost and needs to be repeated. Iâd like to see this fixed, if possible.
I have but normally I have to stop reviewing at a momentâs notice to resume my work or whatever Iâm doing, so I donât have time to complete those remaining items. Even just completing 10 items can take me a few minutes especially if some of them are difficult.
One thing I have been doing that kind of sort of works is to always hit the âend sessionâ button immediately when I start a session. Then I can do them in little sets of 10 and hope that I can wrap up more quickly. But I still often get interrupted too quickly. I really just want more flexibility than this.
I have the exact same problem for the exact same reason as @chiaracoetzee, and while I do use the wrap up button often, even more often, Iâll task switch thinking Iâll come back to reviews in a few minutes, only to get absorbed into the task I switched to, to come back to WK 20 minutes later and the session has timed out.
Usually donât suggest this since it goes against the WaniKani method of randomized reviews, but your use case clearly isnât compatible with how their default system works. What you can do is use a userscript (or smartphone app feature) to order your reviews such that you get reading and meaning back-to-back, meaning that you finish item reviews for each item before moving on to the next item.
This is the one I use: [Userscript]: Reorder Ultimate 2 [newest] since I too sometimes forget my open review session and it messes up the unfinished reviews when I come back. It has a â1x1 modeâ checkbox that does that for you.
Not really an ideal solution but I intentionally mark some wrong. Like you said, theyâre fresh in your memory because you just got them wrong 2 hours ago. I agree with that and in the same way - I remember I got them wrong, so Iâll intentionally mark them wrong again.
Iâve tried the reorder script with the back-to-back method and itâs⊠okay. In some ways better since I canât really see a word without wanting to think about both the meaning and the reading. My only frustration is that it randomly reorders the items and overrides Wanikaniâs own ordering method, but thatâs not a huge deal. Iâll try that again for a while and see how it goes.
It seems that the timeout message time to display is lot shorter than the actual session time. An ASP website hosted on IIS (for example) has a default session time of 20 minutes, but you can raise it in the config. Without knowing how this site is configured i canât tell what the actual session time is here, but I seems longer than 20 mins.
My main grievance is that you might answer 40 questions but have only locked out three items. If thereâs 15 reviews at 6am then 10 at 7 then 10 at 8 etc by the time you come on at 10 the second half of the item might be seperated by 50 other questions. I wish they stayed in their bundles, and the first 30 questions would be all from the 6am lot, rather than at 10 itâs now all mixed in together.
P.s sorry crap typing, on phone, i hate this keyboard but the other one put the capital letters and i fail wanikani reviews if the first character is katakana.
Can someone explain to me why this is a problem and why OP ends up burning words he doesnât know?
I also use the wrap up feature and 98% I am able to finish my 10 word review session. But sometimes things happen and I need to leave my session to do something else and it times out. But how is doing some words again going to make me burn then without knowing them?
OP reviews the meaning of a word, gets it wrong, checks the answer to see what the word means, remembers the meaning, then the review session times out. Which means, WK doesnât remember that the meaning was answered wrong.
OP then starts a new session, sees the word again, answers right because they double-checked the correct meaning a few hours ago, and the word is burned, even though OP actually got it wrong a few hours ago. But because of the timeout, WK didnât register the wrong answer and the item wasnât knocked down in the SRS.
Ohhh that. Got it. This is what I do when I ârage quitâ if I mistype something (I use mobile) and I get it wrong.
I quit and start again because I knew the word Lol (only do if if itâs the only word Iâve gotten wrong in the review session though). I see now that the same thing happens with time outs.
Thankfully I always (barring some emergency which rarely happens) finish my sessions but I do agree ir sucks.
I think so. When you get the meaning or reading correct usually you already know the other one as well. And even if you donât, seeing both back to back first is the same as having it random. I wish they could fix this
Presumably the sessions require memory/storage on the backend to keep track of partially complete items. Ending the session and flushing that data saves WK money. Iâd guess that they are using an in memory cache like redis, or something similar, to track this and they have to flush users from that cache relatively regularly or they have to buy a larger cache instance, or again, something similar.
Transitioning this approach to a persistent database, thereby eliminating the need to flush an in memory cache, as the OP suggests would likely induce other costs.
At the end of the day, itâs probably a money issue. Thatâs really the only explanation. That said, it is still too short.
Itâs definitely stored in your browser cache. If you make too many mistakes you can change device or dump your cache and start again, and wanikani will never know. Itâs all local until you click the button to wrap up the session.
Well we pay money Lol. They need to make space within each userâs database and cache the items there. Once the session is done they can then flush it.
This way, thereâs no need for in memory caching.
Kidding of course. Maintaining servers is tough and it is expensive.
