twitter-tweet IV issue explained

Here's the issue:

https://instantview.telegram.org/contest/pysnnoticias.com/template7/issue2/

The next template in the list has this problem too.

The problem

This site uses <blockquote> with "twitter-tweet" class to display a tweet's content, but does not (at least sometimes) specify the link to a tweet.

This does not break the target page, because a tweet's content is in place and can be displayed. The actual embedding is a JavaScript enhancement. Content is always here, it's jut it can be post-processed by Twitter's JS library if a link to the source tweet is present. If it's not, the original <blockquote> content will be shown. This is how it's intended to work, and it's what's happening on the target website:

The creator's template generates an error and refuses to display the page. What it should do is to replicate the original behavior i. e. show the content.

Relevance

This case is quite common for this website. In fact, I've googled up a number of pages with tweets by "twitter" keyword, and all of them have the same tweet formatting:

1. http://pysnnoticias.com/oficial-sevilla-presta-avanzado-al-levante/
2. http://pysnnoticias.com/twitter-prueba-caracteristica-que-destaca-tweets-de-su-mejor-amigo/
3. http://pysnnoticias.com/twitter-se-va-a-terminar-el-dashboard-su-aplicacion-para-negocios/
4. http://pysnnoticias.com/no-twitter-no-va-a-borrar-la-cuenta-de-donald-trump/
5. http://pysnnoticias.com/twitter-va-a-separar-dms-recibidas-por-desconocidos/

None of them work with the creator's template:

1. https://goo.gl/B9M4Je
2. https://goo.gl/8afuiq
3. https://goo.gl/b1kzvf
4. https://goo.gl/KSW2Tn
5. https://goo.gl/cwgHdF

They do not work with the next template too:

1. https://goo.gl/d6bduk
2. https://goo.gl/NzWrJ9
3. https://goo.gl/kNYzfE
4. https://goo.gl/U1ahjQ
5. https://goo.gl/zUZg39

And do work with mine:

1. https://goo.gl/oCRq4T
2. https://goo.gl/78TJzD
3. https://goo.gl/uBdU3H
4. https://goo.gl/LCAg7U
5. https://goo.gl/Mh2c2a

So, these pages can and should be supported, because it's possible to replicate the exact behavior of the source page, and my solution does it without any loss of content.