Search results

2020-11-18 - Fixed chapter list pagination by using the p parameter returning results from the wrong offset - Fixed chapter views being incremented even when the chapter was unavailable to the user

@Mr_Detective @rkkn Oh, I was assuming you were talking about stuff that doesn't have text to translate. Never mind then. I don't know what this would be called or how the kind of works we're talking about would be defined, so unless there's a proper definition, there's not really anything to...

Absolutely not, that's pointless duplicate data potentially thousands of times over. Especially with how long group names can get. As long as the site itself is still using v1, I won't give it a deadline. Would be cool if we could it by 2021-01-01 I guess, that's a nice date.

They should be reported because this isn't an image gallery site

I don't think we need notifications to let dozens of angry people know when to start talking shit about a group

Bruh

I guess I could have documented that better. But yes, it's intentional that the chapter lists don't return the necessary page information and that you need to actually fetch it from the /chapter endpoint, hence why the index uses "partial information" when referring to incomplete chapter entities.

Goddamnit, I didn't notice that the relation/tags/followtype responses are objects instead of arrays. This is what I get for testing on Firefox, I guess. I'm just going to keep them as they are since it doesn't really affect anything. Sorry about the inconsistency.

@Carbonated That's the idea, yeah.

@nonindustrial Duly noted, I'd like to include something like that as well. I'm still going to have to figure out what I can get away with when it comes to optimizing queries without breaking the damn site.

And yes I'll be marking the date in my local time so no jokes about the updates being in the future allowed

2020-11-10 - [Breaking] Changed the { id: "name" } groups map in chapter listings to an array of simple group entities[ { id, name } ] so that it's in line with the rest of the api - [Breaking] Moved the read parameter in POST /user/{id}/marker from the query to the body - Fixed lastChapter...

Well, I kind of fucked this announcement up. I should've expected I was going to make breaking changes to v2 still and said it was like a release candidate or something. I'm sorry about this. There's two breaking changes I'd like to make: the simple group entities with chapters lists and the...

Duly noted. We're planning on updating the frontpage in the fairly near future either way, so let's just hope this bug magically disappears lol.

@SqueakBeans Let's just say that we're not willingly making running this site harder for ourselves.

Well no, the manga was on a break last week (unless you mean it took an entire week for the author to write that lol) And will be next week too, if you missed the tiny print

@Daxar This is just built with the existing PHP backend we have. At this point, setting up proper tooling would basically be more effort than just quickly editing a little controller.

True, this one was light on redrawing and typesetting compared to the last few chapters. Alpha's translation taking a bit longer than usual aside, this was the easiest chapter in a while.

Sometime during Saturday hopefully. That's the plan, but it's pretty much going to have all the same problems as the current search. Unless I do some heavy rewriting, which I... don't think I will. We'll see.

Yeah, fixed.