[Request] A Script to Disable "Session Has Timed Out"


#1

Requesting a script that would disable the “session has timed out” feature of Wanikani reviews.


#2

I’m pretty sure that’s their for a reason… Your browser needs to communicate your review progress with the server… So when the connection times out, something needs to be done about it.

Perhaps there’s a solution around this, but in the development of the site…

I very rarely see this, except when on a very dodgy connection.


#3

Ahhhh

You are probably right actually. I didn’t think of that.


#4

It’s a good point though! Not sure if something could be done about this from a user experience or technical point of view… It can be annoying with a bad connection :slight_smile:


#5

It happens to me a lot. It shouldn’t need to keep a connection open, http is mostly stateless.


#6

Try this: http://files.ruipinheiro.eu/wanikani_scripts/Wanikani_Never_Idle/

I ended up doing this script for personal use little time before I retired from the site, and then never ended up releasing it. Does exactly what you requested. At the time, it worked. Maybe it still works now?


#7

Thanks man I’ll give it a shot and get back to you.


#8

At the very least the script needs to be updated to @include https://whatever.

I idled a review for ~10 minutes without timing out and then answered it and it seemed to work correctly.


#9

This script didn’t seem to work for me, but I made a similar one that does (it just deletes the hook in the DOM)
https://greasyfork.org/en/scripts/8818-wk-no-idle

no guarantees express or implied.


#10

One time the session timed out screen came up and I hit enter because I thought that would refresh the page, but instead it submitted an incorrect (halfway typed) answer. Fun stuff.


#11
Ethan said... This script didn't seem to work for me, but I made a similar one that does (it just deletes the hook in the DOM)
https://greasyfork.org/en/scripts/8818-wk-no-idle

no guarantees express or implied.
 I can't install it directly because I get an error (however I copied the script and was able to add it from clipboard manually)

"Could not parse script:
Ignoring @match pattern http*://www.wanikani.com/review/session because:
Error: @match: Could not parse the pattern"

I wonder why that's the case.

This actually brings me to another point I'd like to make. I've noticed people use the "*" in space of the "s" for https. I realize the reason for this, as WK has been finicky in the past about whether or not it decides to be secure or not. However, I have two things about this usage

1) I have gotten quite familiar with regex and realize the importance of making your code as efficient as possible. Since the only alternative people want to be there would be "s", why not use "https?", that way if the s is there, it takes it, and if it's not there, it also takes it.

2) Perhaps more importantly, I have tried to force http by typing it in that way, but it redirects me to https, which leads me to believe this has been addressed on the server, forcing the users to stay https. Can anyone else confirm this? If that's the case, then we no longer have to concern ourselves with the possibility of a link being http.

#12
Darcinon said... One time the session timed out screen came up and I hit enter because I thought that would refresh the page, but instead it submitted an incorrect (halfway typed) answer. Fun stuff.
 Yeah, that's the thing. When a session has timed out, you can still, technically, finish your review session. At one point, I kept timing out so much that I just ignored it and continued my session, only refreshing the page when I finished. Haha I'm glad that most of the server issues *knock on wood* have been fixed for the most part now.