The Parchment Proxy was originally created because of cross-origin restrictions. It's now used when a website doesn't add CORS headers.
A website like the IF Archive does have CORS headers, but it doesn't compress storyfiles. This is likely the case for lots of other websites too. So I'm wondering if it would be better to just use the proxy for everything? It can make quite a difference: for something like Cragne Manor it brings 8.6MB down to 2.8MB.
I've talked to the IF Archive people, and they might start compressing storyfiles at some time in the future. When that happens we could add the archive domain to a list which don't use the proxy. (This is already the case for files on unbox.ifarchive.org.)
The Parchment Proxy was originally created because of cross-origin restrictions. It's now used when a website doesn't add CORS headers.
A website like the IF Archive does have CORS headers, but it doesn't compress storyfiles. This is likely the case for lots of other websites too. So I'm wondering if it would be better to just use the proxy for everything? It can make quite a difference: for something like Cragne Manor it brings 8.6MB down to 2.8MB.
I've talked to the IF Archive people, and they might start compressing storyfiles at some time in the future. When that happens we could add the archive domain to a list which don't use the proxy. (This is already the case for files on unbox.ifarchive.org.)