Search results

Now that some time has passed, I'll leave a semi-official response to this. This rule has worked well so far. Ultimately, the goal is to avoid any potential issues from hosting chapters with links to sites that monetise their translations without the publisher's approval. This is also a step...

Hmm, I'm not sure how this can happen. My understanding of this is that the ID of a created thread is attached to the title page. So, if the title is modified the thread won't be recreated. This also makes the thread intangible if the title page is deleted (the same concept applies to chapter...

Hey, I'm just here to confirm that this issue has been on our issue tracker for some time. Sadly there haven't been any updates for a while.

Hi, just for the record, this is a known issue. The last update on this was that it was deemed "difficult to fix".

Hey, apologies for the very very late response (I raised this issue to the devs some weeks ago). Due to the way the settings work at the moment, there isn't an easy way to fix this. This is because most settings are currently stored in your browser's localstorage. This means that the site...

Yesterday we pushed a new update to address this suggestion, here's the new wording.

Hey, I went ahead and approved your chapters. Sorry for these delays.

Hi, I forgot to update this thread, sorry. I asked the developers, but unfortunately I can't share the script because of the way it changes how the reader behaves. If this bothers you, try using a Chromium browser instead. I was told that this can be fixed however, but it's not a trivial fix.

Hi, as many have previously mentioned, this would fundamentally go against our core mission and will expose us to significant legal risks.

Thanks for the report, this is now on our issue tracker.

The fix for this issue was implemented on the main site a few days ago. Thank you for the report.

There was an issue with the settings schema that produced a reset of all settings, this is now fixed. Thanks for the report.

Sorry, I was just able to replicate the bug, so the recording is no longer needed. I was also able to confirm this bug also happens on both Chromium and Firefox. This is now on our issue tracker.

Hey, for anyone still experiencing this bug, please provide a link to the title where the Read button is unavailable.

Hi. Sorry for the late reply, can you please post a recording for this bug alongside more info such as: Browser (and version). Operating system (and version).

Closing this thread as not a bug. We mainly post up-to-date information about potential downtimes via Discord for anyone interested.

We pushed a rules update to the excessive profiteering rule to address some of these situations. You can find more info about it here.

Hi. The 14th of May update enables this feature for everyone on the main site:

Hi everyone! We're rolling out two updates today: one highly requested enhancement and one important rules clarification. You can now once again tailor your reading experience by filtering out content you don't want to see across the site. To set it up, go to Settings -> Blocks -> Tag Filters...

Unfortunately, I don't have an update on this issue, but it's still being worked on. Our reader is one of the most complicated piece of software and it's quite difficult to tinker with it. As for a temporary workaround, I'll ask around if it's ok to share the script someone created internally...