Using the oEmbed API there’s an html attribute returned, I see there’s an old discussion proposing using this returned html but it ends up leaning towards the current solution.
I understand the current approach is cleaner and safer, so it makes sense to keep it on core.
Not something I really need currently, but if I happen to need it, a custom plugin for using this “official” Instagram embedding – enforcing a fixed height and fallbacking to the core solution – would be feasible? Can I have another Onebox engine with the same matches_regexp or should I try monkey patching Onebox::Engine::InstagramOnebox?
Thanks.