Search results

"It's the Guam way. I imagine" "This is how they'd wear a shirt in Guam, I guess. I don't actually know, I'm just making assumptions cos it's hot there."

Seems it might be related to the addition of AbortController. Need a dev to wake up and confirm though. In the mean time you need to update your browser to a version that supports it if able. Always the Apple devices that break first :x

@nonamethanks I know it's not an attack. But if we don't say something when people are waaaaaaaaaaay wrong about our spending/needs it will become internet fact and I'll be reading about on Reddit in a month as 100% proven, verified, totally genuine fact. And yes, you don't know anything. You...

@nonamethanks You're the one is keeps bringing up storage and bandwidth like it has some relevance on CPU/RAM usage for the scale we need. How does a 6TB NVME server help us with processing so many requests? I can tell you 100% for sure it will be dwarfed by the CPU/RAM availability we have on...

@nonamethanks Okay. Compared. So they do 377TB in a month. We do a several PB a month. Not even on the same scale. We dwarf their traffic. Which makes total sense when you consider how many images a chapter contains, how many chapters are hit every minute, versus people opening a few images...

@nonamethanks That's clearly a 24TB HDD archive/storage server. Our servers are expensive because we NEED to pay for lots of cores/threads, lots of RAM and NVME storage for all the processing, caching and moving data around without it crippling the site. You can't do that on cheap ass archive...

Best chapter.

Appreciate the effort, but this has no relevance to us. Path has nothing to do with our hosting. You're making incorrect assumptions or believing way too much stuff from second hand sources. Our servers have plenty of capacity and available bandwidth - and we have more coming next week to give...

@Banacond It's not a bug. You have two accounts with almost the same name. One with loads of follows, and this one with a few.

PM me the IP you are trying.

@Jordick DB issues don't affect your inability to read on an older device. I'm no expert, but there's probably something in the code that isn't usable on older IOS or the out of date browser available on that OS. Maybe @teasday to take a look and see, but as far as I know none of us even own an...

@Jordick No. Seems like the most common cause of issues right now is people using outdated ipads. I guess things tend to break when you are using an ipad 1 or 2 released around 10 years ago. Are you one of those people?

@Darkstar961 Working fine. Try clear your mangadex cookies and cache.

@mangamerchant Awesome idea. If bandwidth was the issue.

@Beddo @__TheOne__ @GrizonII @MTHLily @Croa @ayushk222 @Pegasus1751 @Safety_Dance @Oranos2115 @kimochi123 @Look4Diversion @z3c9 @Ken-Oh @LordPants @tornadix99 @zyraxeer @Kaedox @DeProgrammer @snailyman @Kaizeel @B0undarybreaker @gayasswitch @Z2 It's a weird cache issue from DDG. It updates as...

@whoamiagain No one has. It's a weird cache issue from DDG. It updates as soon as you perform any action on site. You are not actually on their account.

@nobile The rate limits are set so that no actual human would hit them. If you are just reading manga on the site it will make not a single iota of difference to you - unless you happen to open a crap load of tabs at once from a bookmark folder for some reason. They only really affect automated...

Continued growth of site over the last month - often over 20,000 concurrent users - has pushed the old DB slaves to, and past, their limits. During those times we've seen peaks on MD@​H of 1400MB/s (11.2Gb/s)! Splitting off the API onto its own server hasn't had as much of an impact as we had...

@Inori Not right now, but once we move all chapters to md@h, then yes. It is currently the default for old chapters. The current reader DOES load all images at the start (for old chapters), it just does them in order so that pages don't pop up in weird order like they did on legacy if the page...

@Filthy_Hobbits Not sure what you mean. Pinch zoom works perfectly for me over images in all display modes. Might be browser related. Typically most issues exist in terrible Apple products :x