Nginx and the Image format wars.

NGINX - Image Wars

We’ve talked about the videos, we’ve talked about the images. Now we talk about the web-server, Nginx.

In this entry we’re going to get crazy technical with how we deploy all of these new image formats that are being introduced in what feels like the “The Great Video/Image War” to finally put GIFs, JPEGs, PNGs, and MP4s to bed. But instead we’re going to talk about a section that seems skipped a lot. How to actually implement these new formats? Because if we do a review on an image format, and it’s good. Then as bloggers it would be hypocritical to not apply these formats to our site. It however opens up questions. How do we maintain the security of our readers while at the same time giving them the very best image as the lowest bandwidth conceivable? To which thankfully since we have a VPS a lot of the encoding is handled via CRON. While a lot of the deciding factors of which browser gets served what is all in the hands of NGINX web daemon.

Read on if you want to know more.

Read more

Make WordPress default to WebM first. MP4 and OGV last!

WebM default WordPress video title.

WordPress does not want to default to WebM out of the box.

Since I did a blog about WebP minus well do one about WebM. As some of you may know that I run a hybrid video/regular blog we use WebM because it’s the latest and greatest. Back when I was running with the Angular theme that included its own version of MediaPlayer.js and all was good because the WebM files were being referenced first and foremost. That changed when I reverted back to a more standard WordPress theme that relied on the out-of-the-box MediaPlayer.js which is totally fine except for one problem.

Default WordPress HTML5 video player grabs MP4’s first. Not WebM.

Read more