Thanks. I also encourage in not following the mentioned implementation, and not only because they have problems with deleted files (interesting) but also because that solution is verticalized on Wikimedia Commons, and nowadays a "modern" embedder system should probably just use the OEmbed protocol that is quite flexible and would support out of the box an incredible amount of websites, potentially including Wikimedia Commons, with relatively few amount of code, than supporting every single website in the universe.

So, in an ideal world it seems we could have both these resolved:

1. Mediawiki should support OEmbed (existing task ✨ https://phabricator.wikimedia.org/T364479 )
2. Phorge should support OEmbed (missing task - I will open)

There are still data protection concerns in embedding things with OEmbed, but an allow-list of OEmbed-embeddable domains could be designed, for example to only activate Wikimedia Commons.

There is still a cache concern for OEmbed support in Phorge, since people may use Phorge as proxy to DOS other websites or similar things, so the above config is really needed and more....

So, given the fact that the majority of popular websites already support the OEmbed protocol, I think that the current blocking task is this:

https://phabricator.wikimedia.org/T364479 - add OEmbed support to Wikimedia Commons.

But don't expect to see this implemented also in Phorge in less than 5 years lol. We are not WordPress.