This update contains many small changes that are purely technical and shouldn't have any visible effect, and it adds support for Facebook "pfbid" URLs. If you do not care about or use Facebook, you can stop reading there.
Concerning Facebook, it has come to my attention that they have recently started obfuscating their URLs, encrypting them with an unspecified algorithm that generates a different value every time. According to Facebook's public announcement, this change was effected to deter what they call "unauthorized scraping" and is meant to "protect people’s privacy". Cynics will be quick to remark that Facebook's business is based on monetizing its users' information, and that change just happens to interfere with Firefox's query parameter stripping, a privacy-enhancing feature that had been released just a few weeks prior, casting doubt on whether encrypting a URL's identifier is meant to protect users or optimize Facebook's money maker. Facebook/Meta denied via a spokeperson that this has anything to do with blocking privacy features.
Starting with this version, embedding content using Facebook "pfbid" URLs is now supported. The add-on will attempt to revert the encrypted value to its canonical ID whenever possible.
Starting with this update, pages scraped via this add-on are saved to the internal-data://temp, which is usually located at the root of your forum in the internal_data/temp directory. The filenames will appear as s9e.xxxx.html.gz where xxxx is a string of 32 alphanumeric characters. The files are automatically removed by XenForo after a few days.
In most cases it will not make any difference. In some rare cases, it may slightly speed up embedding links from unreliable sources that require scraping.
A number of improvements have been made to the lazy loader. The goal is to generally improve efficiency and make dynamically-sized embeds such as tweets as nondisruptive as possible.
The size of dynamically-sized embeds (e.g. tweets) is cached locally in the browser. This will improve the user experience on repeat viewing or when the same embed is shown multiple times on a page.
Visible embeds are loaded as soon as possible. Previously, the lazy loader waited a tiny fraction of time (32 ms) before checking for visible embeds while the page is loading. Combined with the aforementioned caching, it can reduce and even eliminate Cumulative Layout Shift.
The visibility of all embeds in collapsed quotes is now checked to determine whether they should be loaded. Previously this only applied to regular-sized embeds such as YouTube videos, and has now been extended to all embeds. This means that an embedded tweet in a collapsed quote is not loaded unless it is at least partially visible.