Recent content by cardboard_mf

A super late update, but an update none-the-less! Personal API Clients token resolution methods are now supported by MD# v1.1.0! You can fetch access tokens for your personal API clients with 2 different methods; either via Configuration or Manual specification. Configuration: You will need to...

Re-upload? Probably uploaded the wrong chapter, content seems the same as chapter 28.

Aye, we hit a year of operation for the reverse image search database. It went live (in beta) 2022-12-11 00:40:04 EST so it’s a year and day old at this point. There are currently 4,277,044 images indexed with over 3.7TB of image metadata, signatures, and files stored. my next major update to...

Another slightly breaking change in v1.0.18 that was released today. It was brought to my attention that when the API returned an error code (non 2xx status code), the library would throw an exception and subsequently hide the returned error body. This has been fixed and now the library will...

I have added a notice at the top of the main readme on the GitHub Does that work?

In other news, I just checked the database... There are 3,040,128 unique manga pages indexed so far equating to 2.6TB of data processed by the indexing service with roughly 98% up time since December 28th 2022. That's 9,846 manga processed with 111,176 chapters. A further breakdown of the...

I've added an alert on the old version of the search that redirects to the new site (kinda half assed it though): I'll look into the Yandex API as another fallback as long as it doesn't cost too much. Thanks for the suggestions! I'm also in the process of re-writing the backend of the whole...

If you're receiving sporadic 400 Bad Request responses from the API, try updating to the latest version! I believe I've fixed the issue. I've also added the ability to override the User-Agent sent on all API requests via the library, you can specify it anywhere that you specify tokens or API...

Ah, yeah, I've mostly stopped updating the manga portion of https://cba.index-0.com/manga You should probably use the new site: https://manga.index-0.com/reverse I think the new site still has the same bug as it's to do with how the routing for importing and then going to the manga's page...

Not sure if anyone is using this library, but if you updated to the latest version of the nuget package (1.0.15), there is semi-breaking change: If you use the dependency injection extension method .AddMangaDex(), you will need to also chain .AddJson() and .AddCardboardHttp() as these packages...

I'm not sure what you're asking to be more detailed. I also don't know what you mean by "which chapter direction the image is in"? If you want to see what chapter a page belongs to on either of the websites you can click the "Link:" section: Or if you're talking about the bot, you can click...

Extreme TL;DR: I have a database of "image signatures" that I compare uploaded images against. The comparison returns a "normalized distance" between the two signatures and anything below a certain threshold is considered a duplicate. I scrape mangadex to generate these image signatures. Not so...

Because google lens doesn't have any recent releases since MangaDex isn't scrape-able by google robots. Where as my service has any English release already indexed within 30 seconds* of the manga being released. Also some of the less popular manga don't show up on lens at all. Also, lens...

I recently released an update for this service that also adds in Saucenao results if it cannot find anything on either my database or google lens. It tends to be pretty unreliable, but it is better than nothing. As of today there are 1,292,845 english manga pages in my reverse image search...

I released a decently massive update to the MD#, most of it is just documentation comments to make development easier, but there are a few useful tools in there as well. Specifically, the new pagination utility will take most of the guess work out of getting all results from MD's paginated...