gpt-emacs-macro VS oxipng

I wrote a quick integration to the GPT-3 API to Emacs [0]. Although it's a very simple implementation, it's made many small things I would've previously done manually much quicker (ie - one-off calls to convert a hyperlink in X format to markdown; abbreviate first names of author lists of papers; convert some "text message speak" messages into a paragraph).

[0] https://github.com/samrawal/gpt-emacs-macro

I made something similar for emacs and it unlocks what I think of as “semantic macros” — being able to interface with GPT-3 for actions that are a tiny complexity level above what I usually use kbd macros for (like smart capitalization) easily become possible to automate!

Screenshot - https://twitter.com/samarthrawal/status/1591527892386734081

Code - https://github.com/samrawal/gpt-emacs-macro

Thanks! It's available here -- https://github.com/samrawal/gpt-emacs-macro

I have had good experiences with https://github.com/shssoichiro/oxipng . Although, I suspect this wouldn't give you nearly enough space savings as jpg.

If you do want the file as a PNG (for transparency and a common format that's well supported), but don't want it so huge, consider something like oxipng. https://github.com/shssoichiro/oxipng

oxipng, pngquant and svgcleaner — optimizing images

I wonder how `pngcrush` compares to `oxipng` (https://github.com/shssoichiro/oxipng).

Personally, I use `oxipng` if I want lossless compression. However, most of the time, I use `pngquant` instead, since it gives significant size reduction even at `99%` (I can't even distinguish between the original and reduced image).

    pngquant --quality=99 --ext=.png --force file.png

Depending on your workflow it might make sense to export PNGs directly from Affinity and then reduce their size with a utility like Oxipng, which uses all your cores to find the best algorithm for each particular image.

Assuming your frames are PNG files, you could use a lossless optimizer like optipng to try if their size can be reduced. I prefer oxipng, which is faster and multithreaded, and seems to have more active development.

Not sure what extensions of images you use, but if they’re PNG you could use oxipng: https://github.com/shssoichiro/oxipng