Anyone else being drip-fed gradings? 
I’ll finish a book, get a handful gradings available immediately, and then after a couple days of my grading page saying there’s nothing left to grade, the grading button will show up again and feed me a couple more (and not always from my most recent books).
2 Likes
FWIW this can happen in normal operations too. If you have a book which doesn’t have enough books within 5 levels of it, it can hang out at that level without being able to offer more gradings.
Then, if it changes level, it can bump up into a range where you have a book to compare to.
Not sure that’s happening here, just noting~
7 Likes
Good to know! That might be the case for some of them that I’ve noticed going up or down a level recently, but because most of the books I’ve read are books that only I have read and graded, not a lot of change usually happens in the levels of my books haha. It’s felt random whenever it happens, but I’ll keep an eye out going forward for if the books involved might have been pushed into a different bracket.
4 Likes
Duplicate series:
and this looks like it should be included in the series:
6 Likes
Voting for feature buttons on the forum has a bug? Navigating between threads stays 投票 and 投票済み, even if I haven’t voted yet. (If I click the button showing the wrong state, it will say エラー.)
Only refreshing the website (F5) will show the correct state.
1 Like
I can’t reproduce the error. Maybe is now fixed and was a weird cache issue or is still happening?
I am still seeing it. Firefox for Windows and Firefox for Android.
Reproduction steps:
- Go to a Natively > Product Requests thread
- Choose a suggested thread at the bottom with a different voting status.
- Refresh with F5 or pull down on Android.
- Pressing Back (Alt+Left) also results in the same problem.
1 Like
Granted I’m using a Firefox fork (Librewolf 147.0.2-1) and Linux, but I can’t reproduce.
Leave here the version of your browser for @brandon or one of the team to check it out and see if they can reproduce.
Also for @brandon can I suggest role tags so we can tag the team instead of individuals so we don’t overload just one of you with the recent incorporations?
4 Likes
Another set of duplicates, with Solo leveling, both the manga and webnovel.
A simple duplicate for the manga, one with the series (나 혼자만 레벨업 | L27), and the other one is just one standalone volume (https://learnnatively.com/book/f087dc07a9/).
As for the webnovel, it’s actually been published with two different editions, with volumes split differently. The light cover edition has with 14 volumes, while the dark cover edition only has 8. And somehow, when the series were created, something went wrong along the way so it pulled from the other edition, twice too. So there’s a standalone volume 1 나 혼자만 레벨업 | L27, a series with volume 14 and then the 8 volumes from the other edition 나 혼자만 레벨 업 시리즈 | L30, and then volumes 14 and 2 from the first edition, and all 8 from the second 나 혼자만 레벨 업 시리즈 | L28.
And if you have to keep just one of the two editions, I’d suggest the one with 14 volumes as it’s available through Ridibooks, otherwise the other one is limited to Yes24. (I’m also looking forward to finally being able to track the rest of this series, as I’m currently at volume 4/14)
6 Likes
Just noticed the About Us page is out of date now, both about learners of which languages the site is for and how many members are on the team. Maybe this is an excuse to update the Blog, too? So there’s some sort of announcement about recent developments for users who don’t check the forums.
12 Likes
I think I found another set of duplicates:
3 Likes
Small Product Announcement
Hey everyone! Just wanted to update you all on our progress.
Recent activities
- Onboarding @mathew & @nikoru (note @mathew is using his real name now
) - Developing all the processes for our collaboration
- Brain dumps from me to them on how things work, where to go next
Code Releases
- First just want to say, everyone has already become a code contributor even if it may not be visible yet
- @nikoru - rebuilding our frontend infrastructure, improving testing & enforcing typing to make it leaner, quicker, less buggy and easier to iterate on. This overhaul will take a while and is not yet visible, but we will hopefully begin rolling out switchovers page by page.
- @mathew - fixed some issues with generating CDJapan links. Has been diving into our backend and fixing multiple things up.
- Me - I’ve been focused on centralizing our book addition & syncing processes and continue to make them more robust and error free.
What’s next
We’re mostly continuing our current activities of wrangling infrastructure, squashing bugs and getting @nikoru & @mathew more familiar with the codebase.
Things have been going great - bringing on partners was certainly the best decision i’ve made in years 
While the next while is simply focused on bugs and improving our infrastructure, I think you all will be thrilled when we get to real feature roll out later this year 
And with regards to all the duplicates you all are posting, thank you! Our major priorities continue to be TMDB syncing issues (like @ceique posted and TMDB season splitting) and these book data issues.
We got irons in the fire, hopefully these all get cleaned up soon! We’ll let you know when we do~~
42 Likes
Awesome, thank you guys so much! Code fixes and streamlining and testing aren’t glamorous, but it’s what holds the site together.
18 Likes
Just created ひぐらしのなく頃に 鬼曝し編 1 | L24?? as a series, but only got first book imported, even though it is a series on amazon (and I’m sure I marked it as one)
I had the same issue in 病月 1 | L22 though that one was not a series in amazon either.
please fix them so I can read them without getting upset that I can’t mark them on natively 
4 Likes
It looks like it got populated
Normally, it can take up to 30 minutes. On very rare occasion (<5%), it will take a day. Beyond that there’s an issue.
As for the series not on amazon.. yeah, that’s not going to autopopulate. Will be addressing soon
6 Likes
oh my bad, in my experience so far it had auto populated almost instantly before, so I assumed it was not going to happen.
2 Likes
I was wondering if there was a conceptual/backend issue with being able to track rereads. I know Goodreads supports it but I’m not a huge fan of the way they do it, but they do do it… if I think about it from a (layman’s) database management perspective, though, it seems kind of daunting.
7 Likes
This is one of the most upvoted features, I absolutely agree! After our infrastructure work we’ll be trying to pick off some of the most upvoted features like this.
And it’s definitely doable, but you’re right it will be some work. When we get to it there will a conversation, i’ll be sure to ping you!
10 Likes
And I guess on that note, @brandon, a quick question for you: does infrastructure work include fixing bugs? Or is it purely a drive to improve robustness? No sweat if it’s one or the other, I was just curious.
5 Likes
The focus is on improving infrastructure.. but we’re doing that because we’re encountering a lot of bugs, which we believe will be fixed via infrastructure. We’ll also do some targeted bug fixes, but the focus is infrastructure. 
For example, we’re seeing a lot of data errors right now, both in books & in tv shows. I could go one by one and fix all of these things right now.. but instead i’m spending the time building out a better input system for how we create books & book series. And today I recently released a data management admin with full rollback capabilities, laying the basis for a non techical ‘librarian’ role which could fully manage our data issues easily, both tv, movie & book issues.
WRT frontend bugs, @nikoru is rolling out a much better system which hopefully should make bugs much less common. @mathew is doing some targeted error work right now and other supplementary activities to those efforts.
So yes, bugs should be resolved and our intent is to make site operations way smoother and resilient before moving onto exciting new features.
19 Likes
