Search results

Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience. History state will now be updated at most at a 100ms interval because apparently Safari doesn't like changing it at sanic speeds.

@Soveregin Okay, the search works on at least the latest version of Edge for me. @Nolonar Not that it's particularly important to do right now, but you're probably right about the radio button stuff, I'll think about rewriting that. Same with redirects from the server side, might probably be a...

Preventing selections between two of the chip inputs is a bit of a pain, so for now I went with an easier way and just ignore excluded tags that are also already included. That's all in the search frontend though, so you could still access an url directly if you want to specifically break your...

@Keryx Hey, sorry this took a while. I added a thing that makes the history.replaceState happen at most once every 100ms. That's still so low that 100 times per 30 seconds might happen if you're quickly scrolling up and down for 10 seconds straight, but I also wrapped it in a block that should...

Before this turns into a conspiracy theory, I will say that I have zero evidence to confirm this accusation, but Kettle and Inari most certainly did share an IP address a day or two ago. Incidentally, they no longer do.

Ah, not automatically. Deleting a chapter initially just moves it to a recycle bin from where it can be restored should we be asked to, which happens occasionally.

Shounen and Shoujo aren't tags, they're demographics. I'm guessing dropbox doesn't want you to hotlink.

They're gone, fam. The only secret clubs on this website are for staff.

Having the images as png is making them kinda massive, especially since they're not optimized with pngout (could shave off 2~3MB of each image), but the quality is much better than with the earlier jpg soups, so thank you for that.

@Nolonar The js on the site overall is a complete mess because of how Holo wrote things in the early days. I haven't had the interest to go over the entire thing fixing everything yet. Also, getting rid of jQuery completely is something I plan to do, so the stuff I've written explicitly avoids...

Well, we do have the history (even though it only stores the last 10 distinct manga) and since you mentioned followed manga you can presumably also just check your follows for recent read stuff, right? Are you talking about something more specific, somehow?

Sorry, I know it's not amazing but I do want to make it better! That includes writing a new separate, more basic version that mimics Legacy but works better and hopefully also without js.

For what it's worth, no matter what happens to the forums, I don't think anybody in the staff is interested in changing the linear post order. At least by default. Optional stuff, if it ever becomes applicable, will be optional.

Sounds to me like people who would get blocked often would see it as a badge of honor rather than a mark of shame.

Planned but can't do without significant changes to how read markers work

Bumping this to remind myself to implement it

Unfortunately with the way this currently works, we can't. Completed doesn't in actual fact add read markers but removes all of them (in order to minimize rows), and simply treating the read icons as if you've read them by default. However, the planned read marker update - whenever that comes...

Should be fixed now along with the other db-related problems

Yeah this is a known (I believe cache-related) bug with manga that have a LOT of chapters in all languages. Will be fixed with the new API.

Please split these images up into somewhat shorter ones and don't use such insane compression. The jpg artifacting with these releases is seriously terrible.