No I’m not affiliated (call me crazy 
)
2 Likes
It means the API is not overcoming vimeo’s bot checks. They might be able to resolve this if you email them.
2 Likes
It turns out that this site also uses a plugin onebox assistant?
I very much doubt it
1 Like
But then its mean that black screen on vimeo previews, not cause of plugin onebox assitant!
In my post here, without onebox assistant, I see the same black screen as on my forum, instead of normal preview.
OneBox Assistant is meant to help solve these problems, not make them worse 
But it relies on the 3rd party API crawling that site. (embed.rocks)
Onebox Assistant is merely wiring up the results returned from the API instead of going directly.
If you cannot get a successful result on their website, then it is unlikely to help.
You need a response from embed.rocks.
3 Likes
Robert, my English is pretty bad, and this probably creates additional difficulties in understanding between us.
I also apologize to the moderators, because I have already created many messages that do not bring anything useful. I think it would be right to delete them…
However, I still want to clarify my thought. The most important thing at this moment is that: on this forum, meta.discourse.org, the link I inserted to the video from the vimeo resource is also displayed incorrectly. Theres no preview. And this surprised me. In other words, as I understand it, if this forum does not use this plugin, but the preview is still displayed incorrectly, then I initially thought incorrectly that the problem was in onebox assistant. The problem is in somewhere else. May be problem in OneBox itself?
Just tell me, link in this post is showing correctly for you? Is it with thumbnail or it just blackscreen?
No problem. Let’s walk through this again.
In a vanilla Discourse, to create a onebox preview, a Discourse server must be able to see and retrieve the “og” tagged data in the target page meta information. This is essentially a crawl.
To achieve this the target web server and its gatekeepers must not block this crawl.
It appears that meta is not permitted to see that page by its gatekeepers.
This is why you would consider using this plugin in the first place.
This plugin uses an API to return the target page instead of crawling directly.
This takes advantage of activities and management that the API provider does to significantly increase the chances of being allowed to see the content (e.g. using a farm of servers with high reputation IP addresses from which to launch the crawl, or possibly even faking a view as if it came from the desktop).
Unfortunately in this case, it appears even embed.rocks does not have rights to crawl that page and therefore in this case this plugin is not helpful.
However, if you raise this issue to embed.rocks support teams attention they may be able to work out ways in which to resolve this blockage.
In general this plugin should be useful as it should provide a better onebox previewing experience than a vanilla Discourse without it, though of course you have to pay the API provider.
Note, other things might be going wrong here, for example the target page might not have a good thumbnail.
However, you can use Facebook’s debug tool to explore the data and I believe it looks good:
Which points to the issue being with embed.rocks atm.
On a side note, the rise of Generative AI may be making content platforms much more careful about who can see their content for fear of their content ending up in someone’s model for free.
I hope that’s clear.
3 Likes
Robert, thanks a lot. Now i see. Without plugin meta.discourse.org can’t get thumbnails from vimeo also. With plugin it can be achieved, but at this time API is broken for vimeo.
Thanks again!
1 Like