The JSON response has all dashes replaced by spaces wherever the URL occurs which breaks widget generation.
For example the following oembed URL:
https://publish.twitter.com/oembed?url=https%3A%2F%2Ftwitter.com%2Fguardiannews%2Flists%2Fguardian-editorial-accounts
Returns:
{"url":"https:\/\/twitter.com\/guardiannews\/lists\/Guardian editorial accounts","title":"Guardian editorial accounts","html":"<a class=\"twitter-timeline\" href=\"https:\/\/twitter.com\/guardiannews\/lists\/Guardian editorial accounts\">A Twitter List by guardiannews<\/a>\n<script async src=\"\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>","width":null,"height":null,"type":"rich","cache_age":"3153600000","provider_name":"Twitter","provider_url":"https:\/\/twitter.com","version":"1.0"}
Note the href for the list has been changed to “https://twitter.com/guardiannews/lists/Guardian editorial accounts”, dashes replaced by spaces.
Widgets.js then reports:
Timeline for list for screen_name: guardiannews with slug: Guardian not found
as it’s not parsing the slug properly with the dashes missing.
Cheers.
