@Kilimanjaro If you have to keep setting them back, you must be wiping your cache or local files constantly. Don't do that. As mentioned, the reader settings are local so that they won't interfere with reading on multiple devices, and we have absolutely no plans to change that.
@alexsilener That's a caching issue on the api.mangadex.org server, not a problem with the API per se. Working on it.
As for the login issues (for @0TheWatcher0 as well), my best guess is that the script rejects the session cookie for security reasons and invalidates the session. Changing the...
If the quality of a chapter looks indistinguishable from a troll release to the staff, it's treated as a troll release. We're not mind readers, we can't know people's intentions. What we do know is how a release looks like.
And this one looks like absolute trash jesus fucking christ you can't...
No, we don't want to prevent guests from reading H, literally the only reason the switch is hidden from them is to avoid getting blacklisted in placed like Indonesia. If a guest has the url, we're perfectly fine with them being able to read it.
In short, no. BzzBzz is completely right in the previous post. We'd be rolling in money if we could solve this issue.
Not to mention there's some inherent irony in worrying about scanlations being stolen when the raws had to come from somewhere, somehow.
@Teddy Not really the thread to be discussing this, but do you mean there should be like a warning alert in the reader (similar to the spoiler gap warning) when the chapter is H and the user doesn't have H visible? Guess I could try doing that, now that I think about it.
@Ivegotnolife I don't know about polished, but tachiyomi and paperback using the api.mangadex.org server is certainly helping the webserver to not choke as bad as it used to