martin
11 Noviembre, 2025 06:49
13
De acuerdo, creo que tengo una solución aquí, deberíamos usar oEmbed para estas cosas de YouTube en su lugar:
main ← issue/youtube-oneboxes
opened 06:39AM - 11 Nov 25 UTC
We currently rely on Open Graph data to render YouTube oneboxes.
However, YouTu… be does not always give us a response with the Open Graph
data necessary, leading to empty preview HTML like this that shows
as a broken image in the composer:
```
<img src="" width="480" height="360" title=" - YouTube" style="aspect-ratio: 480 / 360;">
```
In addition, our old method of parsing YouTube script tags for JSON
which contains information for the video, introduced in
https://github.com/discourse/onebox/commit/4d669d2b710483281df1b99ff1140acdada11286,
seems to no longer work reliably, possibly due to changes in YouTube's
JS structure.
To fix this, we switch to using YouTube's oEmbed endpoint which gives us
all the metadata we need for oneboxes in JSON format, including title, author,
thumbnail URL, and video dimensions. This approach is more robust and less likely to break
due to changes in YouTube's page structure.
c.f. https://meta.discourse.org/t/youtube-uris-fail-to-render-thumbnails-when-oneboxed/387673
No lo creo, parece que son 2 cosas:
Algún tipo de limitación de velocidad/redirección de IP extraña, porque a veces para diferentes sitios en nuestro hosting el enlace OP funciona
Este código ya no funciona, porque el JSON que esperamos ya no está allí discourse/lib/onebox/engine/youtube_onebox.rb at e144ec07c8c17ad0f73427524bccc10c074d5a19 · discourse/discourse · GitHub
En general, la URL de oEmbed parece más segura, para el video OP es https://www.youtube.com/oembed?url=https://youtube.com/shorts/Cs3sTnLO6EE&format=json y obtienes este tipo de respuesta:
2 Me gusta
