Thanks. Fixed that by shortening long urls.
But fixed it better by now doing an url check before storing it. So the page needs to actually exist. And if it does, I believe the urls should be short enough in the first place (as per the format google uses).
Thanks for the explanation, but I did know how png works and differs from jpg
Though I did not know that LFS (or I guess directx) will load png just fine if you give it the jpg extension.
We'll see about all this when Scawen makes some time to do the skin download updates.
I like the idea of converting skins to dds on the server and gzipping them. The filesize is about the same as jpg then (even for 2048) but without lossy compression. It also has the added bonus that the LFS client doesn't have to do any conversions, leading to faster skin downloading / processing.
Degats' suggestion to store everything as gzipped dds actually would work very well. Even for 2048 skins. So I'm discussing this with Scawen to see what we can do. Then there wouldn't be any lossy compression at all and you could upload skins even as png for example.
Ah, that's because the thumbnails are now stored with double dimensions. Will fix tonight.
I'm now allowing that character again.
The full set of allowed skin file name characters has been limited though. There were some annoying characters being used previously.
Currently accepted characters are a-z A-Z 0-9 ._-# SPACE
I don't think LFS can make use of png files at the moment, so png uploads (and in particular downloads) will not be possible. Unless I'd convert them to jpg on the server, but then what's the point of uploading in png in the first place
Just make sure you don't use too much compression on your jpg files. Imo the quality is totally acceptable then for this purpose.