Ugh, Twitter. Yes.

The worst thing about Twitter's manglesome reencoding is that most of the time it makes files -larger- than before. Not larger in terms of resolution, but larger in file size, especially in video length .gifs.

I had a twenty-minute redraw cycle once that had maybe thirty thousand frames. Because it was a recreation stack, though, only a few pixels changed per frame and so the LICEcap (which is fantastic for this kind of thing, I should add) recording was only 613kB. Twitter being Twitter, though, decided that the dimensions were not what it liked, so it tried to "compress" it. I had to close the window after ten minutes. The way it does it, the result would probably have been at least thirty megabytes.



I am extremely careful to give Twitter exactly the dimensions it wants now, to try and sidestep that as much as possible. It still does some outright moronic things, though, like compressing anything that does not have at least one transparent pixel in it, which, of course, turns pixel art into artefacty mush. >:1

AND the resulting file is larger than the original.



I wish they had at least put in a thing that checks that kind of thing, like "Hey, I compressed it! Is it smaller? No? FINE I WILL JUST DISPLAY YOUR GRUBBY OLD FILE UNMOLESTED THEN SEE IF I CARE D:<"

No dice. u_u



Other than that, though, I have seen APNGs on a few Pokemon databases, so it turns up here and there. Unfortunately rarely, though. It would be nice if that changed. u_u;

I have tried to make pixel animations in .mp4 and it has been a nightmare every time, without exception[ because I can only afford freeware and freeware answers to nobody].