Lately the scan sizes have gotten pretty out of hand, IMO. I dont know why you'd need scans that huge on a desktop but its definitely murder on mobile devices. Even on wifi each page loads at what seems like dial-up speeds and that can't be good for your bandwidth to serve such huge files that, lets face it, 90% of users are going to look at for a few seconds and click next.

Anyway, thats my long-winded way of asking if we can improve this - maybe keep the gargantuan resolution files to the chapter downloads, or have the resize button pull a smaller version of the file instead of DLing the whole thing and having the browser do the resize?

Are there some releases in particular that you're having issues with?

Lately the scan sizes have gotten pretty out of hand, IMO. I dont know why you'd need scans that huge on a desktop but its definitely murder on mobile devices. Even on wifi each page loads at what seems like dial-up speeds and that can't be good for your bandwidth to serve such huge files that, lets face it, 90% of users are going to look at for a few seconds and click next.

Anyway, thats my long-winded way of asking if we can improve this - maybe keep the gargantuan resolution files to the chapter downloads, or have the resize button pull a smaller version of the file instead of DLing the whole thing and having the browser do the resize?

Are there some releases in particular that you're having issues with?

For me almost every manga on the site started to load significantly slower in the last month, though it's gotten a little better this week. In particular, each page of 1 x 1/2 chapter 7 takes several minutes to finish loading. This is on desktop with fast Wi-Fi.

last edited at Mar 28, 2018 12:17AM

It seems to be most everything I've looked at, but for specific examples:

https://dynasty-scans.com/chapters/the_reason_that_turns_red
https://dynasty-scans.com/chapters/panzer_titten
https://dynasty-scans.com/chapters/koisato
https://dynasty-scans.com/chapters/lewd_drawings_in_spring_scenery

To add a bit more input, I tested the examples above. Instant loading on everything except "KOISATO", where there was a slight delay of a few seconds the first time I went through the pages (but instant loading the second time I went through it). "1 x ½" loads fine as well. Could this be a regional thing? I am in Europe. I myself have had periods when things loaded slowly, sometimes significantly so (though nothing as drastic as what themusicman is experiencing with "1 x ½"), but I have not come across it for some months now.

last edited at Mar 29, 2018 6:32PM

It's most likely an isp specific issue. I only tested with 1 x ½ but I had no issues loading them at all compared to other chapters on the site when I commonly have issues myself due to my isp being total trash.

Lately the scan sizes have gotten pretty out of hand, IMO. I dont know why you'd need scans that huge on a desktop but its definitely murder on mobile devices. Even on wifi each page loads at what seems like dial-up speeds and that can't be good for your bandwidth to serve such huge files that, lets face it, 90% of users are going to look at for a few seconds and click next.

Anyway, thats my long-winded way of asking if we can improve this - maybe keep the gargantuan resolution files to the chapter downloads, or have the resize button pull a smaller version of the file instead of DLing the whole thing and having the browser do the resize?

Are there some releases in particular that you're having issues with?

For me almost every manga on the site started to load significantly slower in the last month, though it's gotten a little better this week. In particular, each page of 1 x 1/2 chapter 7 takes several minutes to finish loading. This is on desktop with fast Wi-Fi.

I'm with you guys on this. Pages have been loading painfully slow for me. I read on my phone, though I use Wi-Fi to so. My speed is around 30mbps on average, so I think that's more than enough to load a page quickly, right? I'm curious who's your ISP? I've got AT&T... Maybe, it's throttling...?

I'm in the US, I have AT&T gigabit for my desktop/wifi connections and Verizon for 4G LTE on an iPhone 7. Both experience the same issue.

And regardless of whether the current files load fast enough for some, isn't the question of whether the site should be serving up such huge files to phones worth exploring? Again, the "resized" version is just the full version downloaded and fit to screen by the browser. Some of those images are as large as 5 MB each. It just seems silly to have to download the massive full file to show on a very small screen for just a second. Most people don't have unlimited phone data, and I'm sure the cost adds up for the bandwidth to serve them too.

ghost posted:

I'm with you guys on this. Pages have been loading painfully slow for me. I read on my phone, though I use Wi-Fi to so. My speed is around 30mbps on average, so I think that's more than enough to load a page quickly, right? I'm curious who's your ISP? I've got AT&T... Maybe, it's throttling...?

Speed means nothing if there's a local routing issue. 30mbps would be more than enough so long as the servers your connection is routed through and Dynasty itself are performing fine. American ISPs cut corners wherever they feel they an get away with it though and those routing servers are one of those places so it's not uncommon for there to be issues for some people loading things at times.

And my personal experience on the site recently convinces me it's probably not the site's server because while I frequently do have issues loading things on the site at a reasonable speed, that hasn't been the case recently including chapters given as an example.

Just did a tracert to see. The only hiccup is at the end somewhere in France, looks like:

2 216 ms 3 ms 128 ms 99-137-156-1.lightspeed.cicril.sbcglobal.net [99
.137.156.1]
3 2 ms 1 ms 1 ms 71.151.37.126
4 3 ms 2 ms 2 ms 71.145.64.224
5 5 ms 3 ms 3 ms 12.83.43.29
6 5 ms 3 ms 3 ms cgcil403igs.ip.att.net [12.122.133.33]
7 4 ms 4 ms 3 ms chi-b21-link.telia.net [213.248.87.253]
8 40 ms 39 ms 39 ms nyk-bb4-link.telia.net [62.115.137.58]
9 35 ms 33 ms 31 ms nyk-b2-link.telia.net [62.115.137.99]
10 27 ms 26 ms 27 ms be100-154.nwk-5-a9.nj.us [192.99.146.38]
11 96 ms * 96 ms be100-1298.ldn-5-a9.uk.eu [192.99.146.132]
12 104 ms * 101 ms be103.gra-g2-nc5.fr.eu [213.251.128.64]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 101 ms 101 ms * ip208.ip-188-165-37.eu [188.165.37.208]
18 100 ms 100 ms 101 ms ip208.ip-188-165-37.eu [188.165.37.208]

Trace complete.

Tamahime posted:

Just did a tracert to see. The only hiccup is at the end somewhere in France, looks like:

Trace complete.

This is exactly how my tracerts look when I'm having issues too, albeit with local servers instead of French ones. And when that happens it's definitely an isp issue and not a Dynasty issue.

Are there any mirrors for dynasty? It just got blocked yesterday here in Russia (ironically, on the same day as Telegram).

My Internet is also trash in my region, so the files being smaller would help me greatly since sometimes I'm several minutes waiting for the loading.

My Internet is also trash in my region, so the files being smaller would help me greatly since sometimes I'm several minutes waiting for the loading.

Any specific releases you're having issues with?

There needs to be some way to report stupid bullshit to Nezchan or DPF or someone. A button that sends them an email or otherwise lets them know that someone is being a ween and they might wanna take a look.

This troll here, for example.

There needs to be some way to report stupid bullshit to Nezchan or DPF or someone. A button that sends them an email or otherwise lets them know that someone is being a ween and they might wanna take a look.

This troll here, for example.

There is IRC, and Discord, with Discord being your best bet. The trolling in question has already been brought up to dpf's attention, so there is nothing more to do but wait.

I was wondering if maybe Gyaru could be a tag?
Also, it would be kinda useful if you could search specifically search for oneshots and/or short stories (in number of chapters).

last edited at Apr 19, 2018 2:44PM

(Sorry for the double post, just wanted to bump the thread)
I think Oppai loli could be a tag too.

Edit: Not saying Oppai loli and Gyaru should be tags, I just think they could be useful. If people disagree I understand. lol

last edited at Apr 24, 2018 3:07PM

(Sorry for the double post, just wanted to bump the thread)
I think Oppai loli could be a tag too.

Hestia

(Sorry for the double post, just wanted to bump the thread)
I think Oppai loli could be a tag too.

Hestia

Kurumi Oonuma/Oonuma Kurumi/Kurumi Ohnuma/Ohnuma Kurumi too.

last edited at Apr 24, 2018 3:08PM

Can we have more than 5 options for Blacklist tag?

angel tag

So you tag Jeanne alter both as Jeanne Alter and Avenger depending on which one was suggested/you remember? And we have both:
https://dynasty-scans.com/pairings/brynhildr_x_jeanne_alter/images
and
https://dynasty-scans.com/pairings/avenger_x_brynhildr/images
tags for the same paring.
Give us the damn names if you can't keep track of the tags.

(Whoops didn't realize I somehow posted it in the wrong thread)

Suggestion #1:
Don't threaten users with bans for repeatedly requesting accurate tags that are, for no clear reason, rejected.
(Examples: 'rape' tag being rejected despite abundant rape in the specified media, 'polyamory' tag being rejected despite the content being explicitly polyamorous, and the removal of a 'yuri' tag from a pairing with a non-gendered/non-binary character being rejected despite that tag being intended exclusively for woman/woman pairings on Dynasty.)

Suggestion #2:
Some means of direct messaging users, so that things like this can actually be discussed without resorting to either off-topic exchanges, dedicated forum topics, or suggestions like this.

last edited at May 15, 2018 10:38AM

Don't threaten users with bans for repeatedly requesting accurate tags that are, for no clear reason, rejected.

My suggestion is to let it go, love. Maybe someone else in the future will have success where you failed. I've had accurate tag suggestions rejected that were changed at a later point (and I'm definitely not alone in this).

Ay, you were warned. Banned.