You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dont think it's a bug. It was probably designed that way to prevent "Too many requests" error.
Hmm .. but if that were the only case, dev should've just make the chapter list fetching list slower, no? Or better yet, give a toggle settings to users whether they want paged or or single list. Well, I'm not a dev, so i can't say for sure
The dev probably wanted to get the plugin running soon. I have also noticed that scrolling too far in the latest section also leads to the 429 error. So, I'm not sure if the site is strict regarding scraping or it could be solved using a little delay
The dev probably wanted to get the plugin running soon. I have also noticed that scrolling too far in the latest section also leads to the 429 error. So, I'm not sure if the site is strict regarding scraping or it could be solved using a little delay
Ok, i went and checked that too. I noticed that novels are appearing far faster than other plugins i use, in those other plugins, when scrolling, it'd take 2/3sec for more novels to appear but this one is giving them instantly. No wonder site blocking it. Chapter list might be solved with lil delay too
Idk if changing the layout to continuous is a "fix" in this case. The 429 error on novel page is an issue that needs to be fixed but I'm not sure about changing the chapter layout. I'm working on something else right now so I will not be able to fix it for now
Idk if changing the layout to continuous is a "fix" in this case. The 429 error on novel page is an issue that needs to be fixed but I'm not sure about changing the chapter layout. I'm working on something else right now so I will not be able to fix it for now
Also there is an annoying update popup that doesn't goes away when i try updating this plugin it says no update found, and i don't use this novel, but this kind of page wise formatting i don't like, i think one single format page fetching will be better than always have to change pages and find chapters randomly.
Ranobes does a very aggressive rate limiting. Decreasing 429 for novel fetching is possible but when I attempted to do the continuous chapter toggle, 429 is very persistent anything that has more that 10 pages (~250 chapters) either takes a very long time or gets rate limited even with a delay of 1.2 seconds between each request. This same delay works fine for fetching novels. If we increase the delay to something like 2 seconds Novels like Shadow Slave (~3000 chapters) would take ~240 seconds just waiting which makes it very much not worth it. Also it may also lead to getting IP blocked by Ranobes. So, idk how to implement it.
Activity
D3ICIDE commentedon Jul 27, 2026
I dont think it's a bug. It was probably designed that way to prevent "Too many requests" error.
MonomoySama commentedon Jul 27, 2026
Hmm .. but if that were the only case, dev should've just make the chapter list fetching list slower, no? Or better yet, give a toggle settings to users whether they want paged or or single list. Well, I'm not a dev, so i can't say for sure
D3ICIDE commentedon Jul 27, 2026
The dev probably wanted to get the plugin running soon. I have also noticed that scrolling too far in the latest section also leads to the 429 error. So, I'm not sure if the site is strict regarding scraping or it could be solved using a little delay
MonomoySama commentedon Jul 27, 2026
Ok, i went and checked that too. I noticed that novels are appearing far faster than other plugins i use, in those other plugins, when scrolling, it'd take 2/3sec for more novels to appear but this one is giving them instantly. No wonder site blocking it. Chapter list might be solved with lil delay too
MonomoySama commentedon Jul 27, 2026
@D3ICIDE are you perhaps gonna try fixing this one?
D3ICIDE commentedon Jul 27, 2026
Idk if changing the layout to continuous is a "fix" in this case. The 429 error on novel page is an issue that needs to be fixed but I'm not sure about changing the chapter layout. I'm working on something else right now so I will not be able to fix it for now
torkita commentedon Jul 29, 2026
Also there is an annoying update popup that doesn't goes away when i try updating this plugin it says no update found, and i don't use this novel, but this kind of page wise formatting i don't like, i think one single format page fetching will be better than always have to change pages and find chapters randomly.
D3ICIDE commentedon Aug 25, 2026
Ranobes does a very aggressive rate limiting. Decreasing 429 for novel fetching is possible but when I attempted to do the continuous chapter toggle, 429 is very persistent anything that has more that 10 pages (~250 chapters) either takes a very long time or gets rate limited even with a delay of 1.2 seconds between each request. This same delay works fine for fetching novels. If we increase the delay to something like 2 seconds Novels like Shadow Slave (~3000 chapters) would take ~240 seconds just waiting which makes it very much not worth it. Also it may also lead to getting IP blocked by Ranobes. So, idk how to implement it.