In reply to Nollind Whachell.

This is a post about Automattic's block experiments, so we're getting a bit off-topic from that discussion. The embedding system also doesn't really have anything to do with blocks. The embed-related blocks are merely a wrapper over the existing oEmbed system.

Honestly, I don't think this is a widely-needed feature. It was tough to turn up many results when searching for similar requests. For the average user, WordPress covers a vast array of providers that will cover their needs. If there's an oEmbed provider missing from the core list, there is likely a plugin out there that will cover it.

I'm not 100% up to speed on how Twitter, Facebook, etc. handle embeds, but believe it is a much different type of system that takes a snapshot of a URL and caches the data (image, title, description) on their servers. That seems more like the type of thing that would fall more squarely within plugin territory.

Embeds, as we know them in WordPress, should never happen unless the site owner explicitly allows them through something like oEmbed. A big part of this is because such embeds use resources from the third-party website.

The embed system is one of my weak spots in development knowledge, so I hope I described that correctly.