Search results

I came here to laugh at you

@alexsilener That's a caching issue on the api.mangadex.org server, not a problem with the API per se. Working on it. As for the login issues (for @0TheWatcher0 as well), my best guess is that the script rejects the session cookie for security reasons and invalidates the session. Changing the...

If the quality of a chapter looks indistinguishable from a troll release to the staff, it's treated as a troll release. We're not mind readers, we can't know people's intentions. What we do know is how a release looks like. And this one looks like absolute trash jesus fucking christ you can't...

Yes I should probably add line clamping to it so that, say, only 4 lines max will show.

No, we don't want to prevent guests from reading H, literally the only reason the switch is hidden from them is to avoid getting blacklisted in placed like Indonesia. If a guest has the url, we're perfectly fine with them being able to read it.

In short, no. BzzBzz is completely right in the previous post. We'd be rolling in money if we could solve this issue. Not to mention there's some inherent irony in worrying about scanlations being stolen when the raws had to come from somewhere, somehow.

@Teddy Not really the thread to be discussing this, but do you mean there should be like a warning alert in the reader (similar to the spoiler gap warning) when the chapter is H and the user doesn't have H visible? Guess I could try doing that, now that I think about it.

Inside the reader, in the reader settings.

@Ivegotnolife Yeah that's all you

@Ivegotnolife I don't know about polished, but tachiyomi and paperback using the api.mangadex.org server is certainly helping the webserver to not choke as bad as it used to

@Halo Yeah I'm stress testing the jinx

A few server errors going on, but actually not at a rate that's out of the ordinary. I guess the API server is doing good work.

It's a naive solution. It's pretty easy to imagine a situation where it would cause unwanted side effects, such as when a group has quietly dropped a series and another one picks it up. Blocking a group-manga combination would be more robust, but that's a bit nightmarish to maintain in both the...

Took me a while to realize what this problem was about, but with some help I found out that for some reason the reader doesn't allow you to pinch zoom while the page is scrolling. I didn't even know this was an issue before just now. I'll look into fixing this, I have some ideas as to what's...

I'd love to move to a gay leftist DDoS provider if we could, but alas.

@NoNume Are you talking about the "detailed" list view option? A manga could have like dozens of tags possibly, so obviously there's no way to fit them all in. We could I guess fit some, I guess, but how would we decide which tags to show and which not without manual selection?

@UseYourName Can you upload a screenshot of your reader settings? I have no idea what would possibly be going wrong. edit: Wait no, I got it. It's a problem with fit to width and no resize specifically. That was dumb of me.

Our warning systems need improving, that's for sure, but we definitely don't want per-chapter tags. Too many groups will be either unwilling to maintain their own or overly enthusiastic with them. I can already see it leading to situations where two groups have translated the same chapter, and...

I didn't think it was necessary to mention, since that information is clearly available. No, it's not and it will not be. I don't understand why you would need to see our implementation, since it's the responses you need to concern yourself with regardless. Seeing how we wrote the API won't...

@UseYourName That can't be right. What OS? It's working perfectly fine with col-auto on Windows.