Getty Images now uses HTTPS to retrieve an image's dimensions.
Gfycat is now HD by default.
Added support for more Medium URLs.
Support for Clyp.it has been added.
All phrases used in the add-on's options and footer are now translatable.
Added support for Castos. Thanks to Ask Andy About Clothes for sponsoring this addition.
Stitcher has been updated to support their shortlink URLs.
Vimeo has been updated and remains functionally the same.

Starting with this update, the release version of add-on will be tested on XenForo 2.2.
The lazy loader has been updated to load visible elements more aggressively. In previous versions, the lazy loader would wait up to 3 seconds for the rest of the page to completely load before displaying embedded content. Starting with this update, visible (on-screen) elements are loaded immediately and will compete for resources with the rest of the page. This will prevent slow resources such as ads and large images from delaying embedded content.
The add-on's CSS has been updated to correctly handle long titles.
The oEmbed logic has been updated to limit the number of concurrent fetches to prevent resource exhaustion. The number of fetches is limited to 1 per page, with a maximum of 3 concurrent fetches across processes.

This is a recommended update if you use the click-to-load feature with oEmbed enabled.
Added a new option to replace the YouTube player with a lightweight placeholder. The placeholder is a single image with no text that loads and starts the YouTube player when clicked.

Updated Audiomack and Twitch. Note that the new Twitch embed only works on HTTPS sites that are served on port 443 at the moment. Hopefully Twitch will relax those restrictions.

Obsolete workarounds for the Vimeo and YouTube embeds have been removed.
This is the same workaround as this previous update.

If Vimeo videos don't load on Safari because of Domain Level Privacy, check the "Use the default Vimeo embed" option. Otherwise, don't.
This revision fixes a CSS injection issue in some of the templates.

The CSS issue was reported by ThemeHouse's Jake B.