- I agree output should be more of a service and we should support more rich embedding via whatever the host server supports ( not what the local client ) supports.
- Timed Media handler does not jump though too many hoops for embedding per-say... because it separates embedding representation ( html5 video tags ) from player interface ( mwEmbed player ). But it certainly would be helpful to fix up media Handling so that you could embed videos from commons on your local wiki without having to keep an up-to-date copy of TMH.
- For example adaptive streaming should start being supported in html5 browsers. Would be nice if the embedding service included the code to do this ( instead of having to update your extension )
- In terms of output api formats, we should also think about open graph xml ( as well as oEmbed api entry point ) Open graph would support embedding into everyone's 'favorite' social network.
Sounds good overall... and good to hear that TMH is less hoop-jumpy. :) Sounds like we should be able to embed (hah) MwEmbed into the embedded iframe to handle the player logic and otherwise make that pretty straightforward for ForeignAPIRepo and oEmbed clients. :D
For Facebook/OpenGraph I'm a bit unclear on whether we'll be able to trigger a direct media player per the stuff on https://developers.facebook.com/docs/opengraph/#types but we can get to the details later! I'll throw a bugzilla entry in to stash more notes on later.