@Miz All times are either listed in your time zone or US Central time.

After reading the all comments I decided to post it on Licensing Suggestion and hope for the best.

https://forums.j-novel.club/topic/9183/light-novel-the-shut-in-lady-is-an-understanding-sacred-beast-caretaker

There is no fan translation (At least I didn't find it, when I searched), because there is no WebNovel version, there is only the Light Novel version.

I also put the manga version on the Licensing Suggestion on the Forum:

https://forums.j-novel.club/topic/9184/manga-the-shut-in-lady-is-an-understanding-sacred-beast-caretaker

Sorry, should have mentioned that is in not something that will be measured in weeks.

Volume 1 won’t be out until July. I suggest checking sometime after at least Volume 1 is out. This way you are not checking all the time.

That being said, we don’t have the date it will be listed either. The listings are handled by our print distributor, not us directly. Even if we said it will be released in X. They will still take their own time to put the listing up.

We make the connection link on our site because it would be a lot more work to individually put the link when a listing goes live.

More debugging information. This is from Firefox 137.0.2-1 as installed on my linux (Debian, PopOS) laptop.

First, I tried disabling cache and clearing site data, but unlike @Anaxim's experience this didn't help on my instance.

Second, I wanted to clarify that the problem with the manga reader on Firefox is strictly limited to loading the chapter. Once loaded, I can move from page to page without problems. That is, I can turn on privacy.resistFingerPrinting once the chapter is loaded and the reader works fine going from page to page.

Third, by switching the privacy.resistFingerPrinting on and of during load, I've isolated this error:

Uncaught Error: Permission denied to access property "type"
NextJS 5
Learn more
framework-717b5372727d76c7.js:25:92626
NextJS 4
forEach self-hosted:157
D NextJS
sendSyncMessage moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/nscl/common/SyncMessage.js:564
refetch moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:126
fetchLikeNoTomorrow moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:144
fetchPolicy moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:95
fetchPolicy moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:85>

The "learn more" link says, among other things, that :

"There was attempt to access an object for which you have no permission. This is likely an <iframe> element loaded from a different domain for which you violated the same-origin policy."

Thanks again, @chocolatkey , for your efforts. Hope this helps...

Any troubleshooting of this would likely include your account data and the forum isn't a good place for that. You'll probably get better help with this if you email support@j-novel.club about it.

@LokiTheBookReader Thank you for letting us know. We will look into this and push an update within the next few days.

@pcj THANK YOU!
I have been so confused and frustrated. And of course it's something simple but not where I thought to check.

The latest issue of Wild Last Boss nailed the chapter title and a speech bubble with this artifact.

Image clip

This has been fixed! Sorry about that!

@myskaros Thanks, seems to be fixed.

My Tiny Senpai turned out to have been internal miscommunications; it wasn't actually ready for posting this week, so they've pushed this release only back a week; the following section should release on the existing schedule.

So no one got My Tiny Senpai this time around, no matter how you access the site.

@linksbrawler Oh, it's because of cronet. In the latest update that's out, we switched to using a better-performing networking library (cronet), but it seems that only works when Google Play services are available on the device. It should be possible to implement a fallback, I'll look into doing that for the next update.

Hi, just want to let you and anyone else who has had issues with the novel reader's performance affecting your battery life: we do have things in the works to vastly improve the novel reader, but I can't make any promises as to when that will go live. I can say it will probably be past Q2 this year.
Same goes for the manga reader, although I don't think it's as much of a battery hog.

@vorduran Took too long to figure out how to reach a person, but he was eventually able to push it through (finally). I still think their system is broken if that is literally the only way to access updated files instead of it happening automatically.