Developer PSA: labs.j-novel.club is your new friend!

pcj

@Bruhtek said in Developer PSA: labs.j-novel.club is your new friend!:

Still looking for a way to sort the results

sorting is easy to do client side.

Bruhtek

@pcj Then I would have to get all the series before sorting them, it is technically viable, but a way to get them already sorted to keep requests small (using pagination) would be even better

pcj

@Bruhtek True that. I didn't think about pagination, but if that's involved you definitely want a server side sort.

chocolatkey

@Bruhtek Added jnovel.bruhtek.com to the CORS exceptions, definitely nicer than proxying user data through your CORS proxy (please don't). It also includes localhost, 127.0.0.1 and dev.j-novel.club (nonexistent host you can map yourself) if you want to develop locally.

I thought I had documented sorting before, but here's the whole proto message for series querying:

/**
 * Search query for series
 */
message SeriesQuery {
    string query = 1; // Search query
    Series.Type type = 2; // The type of series to include

    Sorting sort = 3; // How to sort the series
    enum Sorting {
        NEWEST = 0; // Sort by created, descending
        OLDEST = 1; // Sort by created, ascending
        AZ = 2; // Sort by title, ascending
        ZA = 3; // Sort by title, descending
    }

    bool only_follows = 4;
    bool only_catchups = 5;
}

xellon

Hello, I'd like https://xellon.github.io to be included in CORS list. I'm making a pre-pub reader at https://xellon.github.io/pages/j-novel for my kindle paperwhite which has a very basic browser.

redmasq

Hello,
Just in case it is needed. I wrote a script that snags all of my purchases very quick (epub). It's just a low-quality quickie, just in case it comes in handy, I've posted it here. No guarantees and such.

https://github.com/redmasq/jnc_swagger/tree/main/examples

I'm probably going to schedule it as a weekly job myself, so as to capture any errata and such. I'll suggest not to use the -forceAll unless necessary since it does cause it to download everything again, which could be hard on J-Novel Club's servers (I'm sure my testing was annoying).

I was having problems with an earlier version of FBReader. I found that repackaging the epub file fixes the issue. The script does this, but it is off by default since the files downloaded works perfectly fine in Calibre and such, and in the latest FBReader (probably was a zip handling issue).

I done it in Powershell since I run Windows for my main desktop, but if bash (Linux), zsh (OSX), or python (whatever) is needed, it's a simple exercise to convert it. For the shell script versions, I need web request and JSON support, so I would probably use something like jq and curl, but they are installed easily through pacman, yum, apt, or brew.

Happy Reading.

chocolatkey

I'll update this post with the v2 changes after the migration is fully complete. In the meantime, here's a bonus about the new image CDN:

https://cdn.j-novel.club/pub/img/{height}/{format}/{path...}

height:	120,240,360,480,600,720,840,960,1080,1200
format:	webp,avif,jpg
Full example URL: https://cdn.j-novel.club/pub/img/240/webp/01J/9/V/J9BYFSR8F77KXWT87AZR7.jpg

Many of the images behind this CDN (e.g. covers) are currently low-resolution, so the bigger heights won't result in any change. The images will eventually be replaced by high-quality equivalents.

TAAPAye

@chocolatkey said in Developer PSA: labs.j-novel.club is your new friend!:

I'll update this post with the v2 cha

So I completely misinterpreted this statement.

I noticed the site changed last week when all my scripts broke. I saw in the forms there were known issue being worked on and thought the above messaged indicated that the api itself was down and that an update would be posted when it was back online. So I thought I would just be patience and wait.

...Then it occurred to me to replace v1 with v2 in all the api calls.

yzh4rjdzob6

It amuses me that w/ the change to v2, serie is still a thing. This is a typo for series, yes? Or, perhaps, a reference to an elf mage?

https://labs.j-novel.club/app/v2/parts/{{part slug}}/serie

https://labs.j-novel.club/app/v2/parts/disowned-but-not-disheartened-life-is-good-with-overpowered-magic-volume-1-part-1/serie?format=json

Gamen

@yzh4rjdzob6 Probably not a typo. Possibly a concession to some library that needed distinction between the singular and plural, maybe just because. I know I find zero plurals aggravating when I want to name both a findFirstX and findManyX method just by using -s instead of being that explicit... (anime and manga are another two annoying examples that would go the other way, tacking on a bad -s to make them plural)

admin

@Gamen Indeed this was a choice I made 8 years ago when developing JNC myself. Yes, it would have been possible in the framework I was using to have Series be the model and series be an instance of that model but I felt that would make the code less readable and more prone to errrors and I'd rather have it clear "singlar" word for it that the poor English language doesn't have, so made a convention to call a single series a "serie".

talisein

I just realized my aoab monitor has been failing to login since Oct 10th with a 504. Has the login protobuf changed by chance? I don't think it was ever documented and I forget how I figured it out. I know its on me to fix but I thought I would ask..

Ah, I missed the v2 change..

Malloc

This post is deleted!

Malloc

Has https://labs.j-novel.club/embed/{part_id}/data.xhtml been disabled? I am now only getting the error "(404) Not Found" from it

When I inspect the web's part reader I see they are getting the data from blob:https://labs.j-novel.club/{Some unknown token} which doesn't look like a part id at all.

Also https://labs.j-novel.club/app/v1/me/library?format=json which I use to determine what volumes I own is returning "(503) Server Unavailable" and when change v1 to v2 as an earlier post indicated I get "(401) Unauthorized".

Gamen

@Malloc I see https://labs.j-novel.club/embed/v2/PRT-2VPLKJA/data.xhtml for the latest tearmoon part, so everything looks fine to me. I assume the old (MongoDB?) ObjectIds, which have been termed legacyId in the data for a while now, were replaced with these new ids.