Search results

Your shard allocation stays the same, which means that over time, the number of writes should reduce once you've cached a lot of chapters in your shards. 1. Your client is assigned a number of shards to cache, which is random. The higher your allocated quota, the more shards you are assigned...

what on earth is happening in this thread

😁

We've added 4 more devs to the v5 backend team, so while it's still Soon(TM), it's not as far away as, say, 1 month ago.

Yes, the requirements will be dropping soon.

When you experience problems, check the image url to see if it's a ddosguard problem or a md@h problem.

Common sense applies, and in your example, provided the group is long dead, there won't be any problems. It's not like you're claiming credit for yourself - you intend to credit the group.

There are no per page limits. There is only the 100MB chapter limit. A valid reason for splitting is to get around the 100MB limit, only if you have exhausted other options to reduce the filesize, such as optimising with pingo, resizing so it's not 5000x10000 etc

@AbyssalMonkey Thanks for letting us know. MD@H has been around for a few weeks only, it's still in its infancy. H@H has had years of development, so of course they are going to be ahead of us, lol. Rest assured that the option to switch it off will remain until all of these problems have been...

Link these chapters so we can check

Turns out the guy who recommended VeePN to us on the forums turned out to be a spambot lmao. https://mangadex.org/thread/246332/1/#post_2123332 Goodbye, VeePN...

@potatoesriceandbread It is the default bootstrap theme, which is commonly used on many websites.

38 pages, wow

@remlei Let us know which node is giving you these errors, by looking at the URL of the images.

We have no plans on rejecting anyone willing to run a client, but we are limited by the number of certificates we can generate right now. EU nodes are a low priority at the moment, AS and NA are higher priority.

Mods don't know the storyline of every title. If it looks like a spoiler, and someone reports it, it will most likely be marked as such. You'd have to make it clear it was your prediction rather than presenting it as fact, I guess.

You would have to ask HakuNeko to implement it on their end. There is the option to switch it on and off on the reader, but I don't know how HakuNeko does it.

@knabber They are not assigned to new clients automatically. Ix takes a look at the pending clients and picks high cache/high bw ones in regions needing them the most, e.g. AS.

Users will be assigned clients based on closest region. Clients with higher bandwidth will get more requests.

Or people can slow down their reading!