Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Currently cannot fully capture oembed of tweets on oembed.link #189

Open
despens opened this issue Sep 18, 2023 · 1 comment
Open

Currently cannot fully capture oembed of tweets on oembed.link #189

despens opened this issue Sep 18, 2023 · 1 comment

Comments

@despens
Copy link

despens commented Sep 18, 2023

oembedded tweets are currently not captured, it looks like the embedding scripts can only partially execute in the archiveweb.page desktop app v0.11.2

Example:

https://oembed.link/https://twitter.com/GIFmodel/status/1239234426825052161

image

image

@ikreymer
Copy link
Member

ikreymer commented Oct 7, 2023

Yes, unfortunately seems like this may have been an issue for a while, in the app, but should work fine in the extension.

I think culprit is that it somehow is unable to fetch the js payload:

Target Attached: iframe  21CFFF920BA5F9E93C2D52074FBEB246
Target Attached: iframe https://platform.twitter.com/widgets/widget_iframe.34999e64cd909e9be3bbd826bafcd2c4.html?origin=https%3A%2F%2Foembed.link B02224DF13052BBB4413B0958FD56018
no buffer for: https://platform.twitter.com/embed/embed.runtime.134756fb68200110af56.js 200 88147.4 Network.getResponseBody
[Error: No resource with given identifier found]
no buffer for: https://platform.twitter.com/embed/embed.9449.143d97ea3ade6f4824dc.js 200 88147.5 Network.getResponseBody
[Error: No resource with given identifier found]

Will need further investigation :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants