[fr0stG]

Quote:

Originally Posted by niCe But it's better than nothing, isn't it? I feel this is reasonable compromise.

Maybe the better approach would be to educate people on how to properly compress things and use a CDN for model delivery. CloudFlare can be used, and it's completely free.

https://www.youtube.com/watch?v=W3JulhlNmSk

533 models in 30 seconds using HTTP/1.1. It could be even faster if it supported sending a ZIP with all of them rather than downloading them one by one. But obviously that could have some security considerations. The arguably better thing to do would be to add HTTP2 support for parallel requests.

The argument that custom downloads worsens the user experience is ridiculous. Sure, it adds a little more wait, but the benefit from having custom models more than makes up for that. In turn, the custom models improve UI/UX as well.

So just some ideas:
- Keep custom models, but enforce HTTP downloads at the minimum
- Add HTTP/2 or QUIC support
- Create a post/wiki article about how to use CDN's, GZIP compression, so on.
- Support sending models via a compressed/archive file to the client (potential security considerations, though)
- Create/implement a server-side minifier for models so that even when people add uncompressed behemoths, the server will still be able to serve them efficiently. Or alternatively, create a script/batch file to mass-minify models so that they can be uploaded/exported.