# Wanikani Dashboard Update **URL:** \ **Category:** Announcements\ **Created:** [July 22, 2024, 10:41pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667 "2024-07-22T22:41:27Z")\ **Posts on this page:** 20\ **Page:** 4
**Author:** ![RobertaB](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/wanikanicommunity/original/3X/f/d/fd4c154120954695f788402f3bcf4e616499bc2d.png) [@RobertaB](https://community.wanikani.com/u/RobertaB)\ **Post date:** [July 23, 2024, 4:51pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/61 "2024-07-23T16:51:12Z")
I did notice the same exact thing, on mobile it is smaller. Edit: also the font for the Recent lesson and Burned items left is smaller 🤷. ---
**Author:** ![tofugu-scott](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tofugu-scott/32/565166_2.png) [@tofugu-scott](https://community.wanikani.com/u/tofugu-scott)\ **Post date:** [July 23, 2024, 5:12pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/62 "2024-07-23T17:12:10Z")
> [@Hubbit200](#): > > is there a reason why this wasn’t released onto the preview site a couple of days ago considering you knew it would break so many scripts? This would have left a fairly significant code change going stale on its own branch in our version control while we waited for code that we don’t manage or have control over to be updated. I have seen some authors aren’t able to fix their scripts until August. > [@Hubbit200](#): > > I understand you provide no official support for scripts And you answered the other part of the question, however this change has been a long time coming and I did tell people this back in [March 2023](https://community.wanikani.com/t/updates-to-lessons-reviews-and-extra-study/60912/28) TBH as soon as this hit production it was always going to break scripts regardless of how much time people had to fix their scripts before hand. ---
**Author:** ![tofugu-scott](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tofugu-scott/32/565166_2.png) [@tofugu-scott](https://community.wanikani.com/u/tofugu-scott)\ **Post date:** [July 23, 2024, 5:21pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/63 "2024-07-23T17:21:04Z")
> [@iustin](#): > > Just curious, jQuery I understand, but the rest are a bit surprising. For my curiosity, what tech stack is now used? > [@araigoshi](#): > > [Turbo Frames](https://turbo.hotwired.dev/handbook/frames) (not to be confused with turbo links). It’s a bit of a niche choice but seems similar enough to htmx which has been getting some fanfare the last couple of years. We use Ruby and Rails. Turbo is part of [hotwire](https://hotwired.dev) which is a Rails default. This change meant we could remove Node completely from our app also. For us this is huge, and has resulted in much faster build and deployment times but also reduced our code surface area significantly. ---
**Author:** ![drydenxenvik](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/wanikanicommunity/original/3X/f/d/fd4c154120954695f788402f3bcf4e616499bc2d.png) [@drydenxenvik](https://community.wanikani.com/u/drydenxenvik)\ **Post date:** [July 23, 2024, 6:08pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/64 "2024-07-23T18:08:00Z")
FYI, Odd behavior seen consistently (Edge + Chrome, no scripts installed). When completing reviews, going back to the main page first loads the previous view showing the reviews to tackle from before, followed by what looks like a full page refresh to update the reviews that were completed. (note: gif is looped, the dashboard only does this once after returning from reviews) ![dashboard glitch](https://global.discourse-cdn.com/wanikanicommunity/original/4X/2/4/2/24268bb082244f1b2ea8a55b441ad3faa35acee9.gif) ---
**Author:** ![tofugu-scott](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tofugu-scott/32/565166_2.png) [@tofugu-scott](https://community.wanikani.com/u/tofugu-scott)\ **Post date:** [July 23, 2024, 7:10pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/65 "2024-07-23T19:10:41Z")
Thanks for the screenshot. This has been noted. ---
**Author:** ![Hubbit200](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/hubbit200/32/510283_2.png) [@Hubbit200](https://community.wanikani.com/u/Hubbit200)\ **Post date:** [July 23, 2024, 8:04pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/66 "2024-07-23T20:04:26Z")
> [@tofugu-scott](#): > > TBH as soon as this hit production it was always going to break scripts regardless of how much time people had to fix their scripts before hand. I do understand your point of view - but I also still think it would have been nice to have it on preview for just a few days: it would have allowed popular and actively maintained scripts to be updated or at least have workarounds be posted even if not _every single_ script was updated. And I’m sure a couple of days could be managed from the version control side, as has been done before. Or if that were still too much to ask - at the _very least_ a post like this one but posted maybe a couple of days ago to warn script authors it was going to happen so we could be more prepared (and e.g. even have fixes ready to go for things like switching to using turbo on the dashboard!). That would have been zero extra effort and would only have served to helpfully give warning to everyone who puts many hours into helping improve your product. You did mention you were working on switching to turbo etc. a few months ago, but for all we knew that could be happening a month ago, today, or next year! (or never, as evidenced by the reviews API endpoint 😉 ) I’m sorry if I come across overly hostile - it’s just the lack of understanding towards script authors/users frustrates me a lot when you have such an active and large scripting community. ---
**Author:** ![iustin](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/iustin/32/297575_2.png) [@iustin](https://community.wanikani.com/u/iustin)\ **Post date:** [July 23, 2024, 8:26pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/67 "2024-07-23T20:26:07Z")
> [@tofugu-scott](#): > > > [@araigoshi](#): > > > > [Turbo Frames](https://turbo.hotwired.dev/handbook/frames) (not to be confused with turbo links). It’s a bit of a niche choice but seems similar enough to htmx which has been getting some fanfare the last couple of years. > > We use Ruby and Rails. Turbo is part of [hotwire](https://hotwired.dev) which is a Rails default. This change meant we could remove Node completely from our app also. For us this is huge, and has resulted in much faster build and deployment times but also reduced our code surface area significantly. Thanks both! A bit far from my backend stack (I mean, on a personal level, not work-work), but interesting. I’ll have to read in more detail - the ability to remove a lot of the usual frontend stack is appealing indeed. ---
**Author:** ![RobertaB](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/wanikanicommunity/original/3X/f/d/fd4c154120954695f788402f3bcf4e616499bc2d.png) [@RobertaB](https://community.wanikani.com/u/RobertaB)\ **Post date:** [July 23, 2024, 9:36pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/68 "2024-07-23T21:36:05Z")
Similar things on mobile devices as well. Chrome on Android, no scripts installed. When scrolling up to the review section, the whole screen kind of shakes. ---
**Author:** ![tofugu-scott](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tofugu-scott/32/565166_2.png) [@tofugu-scott](https://community.wanikani.com/u/tofugu-scott)\ **Post date:** [July 23, 2024, 10:12pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/69 "2024-07-23T22:12:44Z")
> [@Hubbit200](#): > > it would have allowed popular and actively maintained scripts I would say double-check would fall into that category and I know rfindley has said that they dont have time until august. > [@Hubbit200](#): > > Or if that were still too much to ask - at the _very least_ a post like this one but posted maybe a couple of days ago to warn script authors it was going to happen Just so you know I / we thought about and discussed this. My POV was that if I wrote a post saying it was coming that wouldn’t be all that helpful because you wouldn’t know what may or may not break. > [@Hubbit200](#): > > and e.g. even have fixes ready to go for things like switching to using turbo on the dashboard This was mentioned last year in the post I linked previously. THis change was always coming, and a year is more than enough notice IMO. > [@Hubbit200](#): > > (or never, as evidenced by the reviews API endpoint 😉 ) I hear you on this and I still read that post but don’t respond because I feel I am damned if I do and damned if I don’t. Not an easy place to be. My stance on “I will report back on that when I have the actual answer” still stands. > [@Hubbit200](#): > > I’m sorry if I come across overly hostile - it’s just the lack of understanding towards script authors/users frustrates me a lot when you have such an active and large scripting community. I do understand your frustration, which is why I always try to get people to think about scripts as their own responsibility. If I wrote a script for any web application for my own personal use and it broke, I wouldn’t expect the web app owner to know about my personal script nor cater to it. I think it would be unfair of me to expect the web app to manage any of my own personal code when it is not under their control. Scripts are great if you can fix them yourself, which is how they should be “marketed”. I know this isn’t the situation we are in, but I am sure as you can see it is hard from both sides at the moment. If it is any conciliation this did end quite a long and large transitional code change and we have settled (for now) on using a mostly standard Rails stack. ---
**Author:** ![tofugu-scott](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tofugu-scott/32/565166_2.png) [@tofugu-scott](https://community.wanikani.com/u/tofugu-scott)\ **Post date:** [July 23, 2024, 10:14pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/70 "2024-07-23T22:14:15Z")
I have just deployed a fix for the screen shake when you scroll. ---
**Author:** ![Hubbit200](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/hubbit200/32/510283_2.png) [@Hubbit200](https://community.wanikani.com/u/Hubbit200)\ **Post date:** [July 23, 2024, 11:09pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/71 "2024-07-23T23:09:23Z")
I appreciate the detailed response! And I apologise for taking up your time 🙂 > [@tofugu-scott](#): > > I would say double-check would fall into that category and I know rfindley has said that they dont have time until august. For sure - but there’s also many scripts that are being actively updated / have already been updated, and would have benefited from having a couple of days on preview to save some stress and to avoid users having their experience messed up. > [@tofugu-scott](#): > > This was mentioned last year in the post I linked previously. THis change was always coming, and a year is more than enough notice IMO. Fair. I think my issue was it was almost too much notice, as a future thing that could happen in months and months I (and I’m sure others) didn’t really prepare in the same way as if there’d been a post saying “in three days time, this will break if you don’t have an update ready”. But yes, I do appreciate you having provided that original post. > [@tofugu-scott](#): > > I hear you on this and I still read that post but don’t respond because I feel I am damned if I do and damned if I don’t. Not an easy place to be. My stance on “I will report back on that when I have the actual answer” still stands. I don’t envy your situation 😅 I do wish though very occasional updates could be provided even if just to say that e.g. it’s still under consideration, or that it’ll likely take a year or two, etc. It would make it seem less like an “abandon and ignore all feedback” situation from WK… > [@tofugu-scott](#): > > I do understand your frustration, which is why I always try to get people to think about scripts as their own responsibility […] Scripts are great if you can fix them yourself, which is how they should be “marketed”. I know this isn’t the situation we are in, but I am sure as you can see it is hard from both sides at the moment. I do understand your point of view. I think the issue is that there’s quite a lot of people using scripts (a much higher percentage than the average website) and a large community has been created around it, with many incredible scripts. This can then be used to argue (by other users - WK doesn’t seem to have taken a stance on it) that features you can get with scripts don’t need to be implemented into WK even as an option (e.g. dark mode, heatmap, double-check, pitch info, custom items, etc.). Which is an issue, as scripts are inherently unstable if support isn’t provided (which as you rightly say is difficult). It’s an impossible situation - I just wish a better middle ground could be found. I do like WK a lot, but it can feel a lot like “big corporation that doesn’t listen to its users” sometimes, when I originally got the impression it was more than that. In any case, congrats on cleaning up the code so much - as a dev myself I know it’s always very satisfying to get old code cleaned up and improved (oh and also your gradual move to more CSS variables is greatly appreciated, it makes dark mode styles a bit easier to maintain). And I do appreciate the time you take to respond here on the forum, that is already a step up from most companies 😉 ---
**Author:** ![superelf94](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/superelf94/32/775220_2.png) [@superelf94](https://community.wanikani.com/u/superelf94)\ **Post date:** [July 23, 2024, 11:34pm UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/72 "2024-07-23T23:34:30Z")
Let me start with I have no idea about code so it could just be my internet’s strict enforcement of security and authorization interfering with it but just in case here’s the loadout that I got after I tried to open gravatar. ![キャプチャ](https://global.discourse-cdn.com/wanikanicommunity/original/4X/1/d/7/1d70d3f7582d679362f87683056ec43d7e517789.jpeg) I guess in the end it’s not the biggest of problems but it was quite a shock when I noticed that it had basically disappeared suddenly. Knowing that it does still exist, just invisible I can get used to though. ---
**Author:** ![tofugu-scott](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tofugu-scott/32/565166_2.png) [@tofugu-scott](https://community.wanikani.com/u/tofugu-scott)\ **Post date:** [July 24, 2024, 12:13am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/73 "2024-07-24T00:13:59Z")
It would appear that your browser / computer has outdated certificates or you have cached expired certificates. if you do an internet search for `NET::ERR_CERT_AUTHORITY_INVALID` you might find a solution to your problem. ---
**Author:** ![superelf94](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/superelf94/32/775220_2.png) [@superelf94](https://community.wanikani.com/u/superelf94)\ **Post date:** [July 24, 2024, 12:40am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/74 "2024-07-24T00:40:42Z")
Thank you for the help, I did what I am able to do on my work computer as far as clearing the cache, but I can’t disable the security protocols which would allow me to try and change more. I think for now on this computer I’ll just be a white circle 🙃 ---
**Author:** ![ctmf](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/ctmf/32/183394_2.png) [@ctmf](https://community.wanikani.com/u/ctmf)\ **Post date:** [July 24, 2024, 1:17am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/75 "2024-07-24T01:17:27Z")
> [@tofugu-scott](#): > > I removed about 167,000 lines of code Come on now, minified code only counts as one line. 😃 ---
**Author:** ![ctmf](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/ctmf/32/183394_2.png) [@ctmf](https://community.wanikani.com/u/ctmf)\ **Post date:** [July 24, 2024, 2:08am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/76 "2024-07-24T02:08:38Z")
> **Summary** > > So it did break, as promised 😃 , and I did fix it. But now I’ve got a weird thing I’m not sure is or isn’t related to the update and maybe I’m an idiot, but while we’re here, someone might know: > > So now my script… doesn’t work the first time the page is loaded in a while, but it does if I hit the refresh button a couple of times. I think maybe wkof (which it depends on) isn’t fully loading first? Because once when it seemed to NOT work I tried checking the value of wkof.user, which was undefined. But then when I manually typed wkof.include(‘ItemData’) in the console and _then_ wkof.user, it suddenly started working again (and so did my script on refresh). But wkof.ready(‘ItemData’).then… is (and has always been) in the script. Kind of scratching my head why it doesn’t always work now. Never mind, the script is running and can dump output to the console, I just must have screwed up the display code. Weird that it works sometimes, though. ---
**Author:** ![durteloni](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/durteloni/32/682461_2.png) [@durteloni](https://community.wanikani.com/u/durteloni)\ **Post date:** [July 24, 2024, 2:10am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/77 "2024-07-24T02:10:13Z")
Since you mentioned that you use Tsurukame, I believe that if you click on the Upcoming review chart on that app, it will show the information you need in list form. In my case, it shows that the current review includes 11 items that reached master level. ---
**Author:** ![amagi](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/amagi/32/705881_2.png) [@amagi](https://community.wanikani.com/u/amagi)\ **Post date:** [July 24, 2024, 3:10am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/78 "2024-07-24T03:10:31Z")
Perfect that helped. Honestly it confused me at first but your post had me take a closer look and I can understand it now. Yes, this is the feature I was looking for. ---
**Author:** ![Cookie316](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/wanikanicommunity/original/3X/f/d/fd4c154120954695f788402f3bcf4e616499bc2d.png) [@Cookie316](https://community.wanikani.com/u/Cookie316)\ **Post date:** [July 24, 2024, 5:29am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/79 "2024-07-24T05:29:44Z")
> [@tofugu-scott](#): > > I hear you on this and I still read that post but don’t respond because I feel I am damned if I do and damned if I don’t. Not an easy place to be. My stance on “I will report back on that when I have the actual answer” still stands. Just wanted to reply to this (since the Reviews endpoint is a big deal to me). You’re not damned if you do, damned if you don’t. Every complaint in that thread revolves around the fact that it’s been ignored for a year straight - so I can’t wrap my mind around why you’d think ignoring it even more is somehow a better solution than just… Responding… Nobody is demanding “the actual answer” - all we want is some transparency and communication and to stop being ignored. Even if it’s just a small update about what’s being done and what progress is being made, that is _way_ better than straight up silence. People are, totally understandably, going to assume you abandoned the whole issue when you ignore them for an entire year straight. And that is, totally understandably, going to make them frustrated. So to see you now complaining about them in another thread, acting like there’s nothing you could possibly do to please them and they just _want_ to be annoyed… Doesn’t seem super cool to me. If it’s out of your control - say so, and people will stop blaming it on you. If it’s within your control, then tell us what you’re doing to resolve it. If you’ve made some headway towards a solution, tell us and we’ll be thankful. If you haven’t made any headway towards a solution, then don’t be surprised when people are annoyed. You have a lot of options to make things a whole lot better. You don’t have to feel like the whole situation is helpless. And that being said - I don’t blame the situation on you personally. I don’t fully understand how Tofugu management is structured or what role you play in getting this solved, so please don’t take any of this personally. I’m not annoyed with you - I’m only annoyed with the situation as a whole. (and as of now I have no reason to assume it’s your fault) ---
**Author:** ![superelf94](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/superelf94/32/775220_2.png) [@superelf94](https://community.wanikani.com/u/superelf94)\ **Post date:** [July 24, 2024, 6:48am UTC](https://community.wanikani.com/t/wanikani-dashboard-update/66667/80 "2024-07-24T06:48:15Z")
> [@Cookie316](#): > > Every complaint in that thread revolves around the fact that it’s been ignored for a year straight - so I can’t wrap my mind around why you’d think ignoring it even more is somehow a better solution than just… Responding… I mean I think this counts as a response… > [@tofugu-scott](#): > > My stance on “I will report back on that when I have the actual answer” still stands. Idk personally, but, I figure to make something as big of an announcement on something that is so highly sought after would need to be handled delicately and properly. One person on the team saying _anything_ here in the community threads, which could possibly be mistaken as “purposefully hiding answers/announcements in the comments” could be a (worst case scenario) fireable offense. Just because Scott happens to respond in the community more than others, he’s not alone and wanikani isn’t just run by one person. And what is being requested isn’t what every single person wants anyway. Many people have other priorities on what they want done faster than other things. I have a feeling that the only thing that Scott could say is “we hear you” (which he has) but it wouldn’t be/ apparently isn’t enough for a lot of people here. Maybe there is no timeline, or is dependent upon several other things going through which might surprisingly go quicker than others, or maybe it takes so long. Therefore giving any answer that hasn’t been approved, would be worse, but it also looks worse to just not say anything. > [@Petition to make popular third party add-ons an integrated feature](https://community.wanikani.com/t/petition-to-make-popular-third-party-add-ons-an-integrated-feature/66671/30): > > The development team is larger than just me. > [@Cookie316](#): > > And that being said - I don’t blame the situation on you personally. I don’t fully understand how Tofugu management is structured or what role you play in getting this solved, so please don’t take any of this personally. I’m not annoyed with you - I’m only annoyed with the situation as a whole. (and as of now I have no reason to assume it’s your fault) I can understand frustrations, but it definitely feels like this is being aimed at the mods who comment or post, and Scott is the one who responds the most. Especially with a lot of "you"s being thrown around in not just your post but many others. The mods at wanikani are humans too. And so are we. [Previous page](https://community.wanikani.com/t/wanikani-dashboard-update/66667.md?page=3) [Next page](https://community.wanikani.com/t/wanikani-dashboard-update/66667.md?page=5)