2 comments

[ 2.3 ms ] story [ 13.2 ms ] thread
I'm a big fan of embedly and will continue to use them, this is a bit aggravating though. I think it's important to lay the blame with the party responsible here - twitter; for their increasingly developer hostile attitude.

Why the hell does it matter to them how I acquire the embed code? I'm still using the same damn code, all this does is make my life harder.

Twitter cannot call this oEmbed. Their API documentation is lying.