Search results

Nah we have unions

API hits for guests are pretty much cached at ddos-guard. The majority of the content we serve never even hits our servers.

The OP

You've somehow found the most uncacheable feature I've heard so far: something that depends on the user, their language filtering settings, their read chapters as well as the number of available chapters in specific languages in any given title. We could implement this, but nobody could read...

Good news: people suck at giving things proper ratings. You can assume the ratings are always wrong and won't be a spoiler in any way.

Generally speaking we're not going to make any big changes to the design of the current site, that's what we're rewriting the site for. BBCode in manga descriptions is currently kind of an unavoidable evil, and I'm not completely sure we want to actually keep it as a possibility once the more...

Since the suggestion is essentially "make the site more user-friendly and its customizability more obvious and accessible" I'll just say that that is one of the design goals of v5 This particular suggestion itself however, especially as it relates to the current iteration of the site, I don't...

Sure, but by the law of equivalent exchange we'll ban you from the site

Not today FBI

api server bad wait until we fix

@DrMuhammad @Thelonewolf If it's just questions about why is the MangaDex extension for Tachiyomi not working properly, the answer is indeed that our api server caching is messed up and will lead to some inconsistencies between Tachiyomi and the website. There's nothing else I can say about it...

In short: Do not ask or talk about Tachiyomi here. I have no fucking clue.

@RhiobeT Not an option currently. @Yvyuw Caching troubles, I assume. @Grumpyfelo I don't know how that relates at all to what I just said there. I was talking about CORS there, it has nothing to do with Tachi, using a VPN or the API needing to be fixed in any way. For the information of...

lol

Yes As for getting into the field, I'm currently earning more with an intern salary than any other job I've ever had. Just live in a better country lol.

Hmm

We currently serve static pages everywhere except the reader, so "pulling down to update" would just mean refreshing the entire page. I don't have an iPhone so I dunno how their PWA's look, but you'd get the same effect just pressing the refresh page button. Assuming it's there somewhere.

With the setup we have currently, this is not really doable without severely stressing the database servers. Seeing how we're already struggling keeping them up, this'll have to wait until v5 at the earliest, if then.

That's what it means, yes. Obviously we don't want other sites just directly acting as a frontend for our data. They'll have to go through some effort ripping us off at least. What you should realize is that CORS is specifically just a commonly implemented web browser security feature designed...

fair