If any Html-asset that wasn't supposed to be a part of the graph expansion query somehow gets into the graph, hyperlink will treat it as a valid page that needs all its non-page dependencies checked.
The open graph link responds with an Html asset, which then becomes a first-level citizen in the graph.
When hyperlink is running with the --internal switch, https://vimeo.com/49026951 get checked as part of the run as if you had called hyperlink directly on that URL.
If hyperlink is running with the --recursive switch activated, having https://vimeo.com/49026951 in the graph will result in a complete traversal of the entirety of https://vimeo.com
This case is equally relevant where no cross-domain jump is happening. Running hyperlink non-recursive should fo course also never result in another page being expanded upon, even if it was local
If any Html-asset that wasn't supposed to be a part of the graph expansion query somehow gets into the graph, hyperlink will treat it as a valid page that needs all its non-page dependencies checked.
Case in point:
The open graph link responds with an
Htmlasset, which then becomes a first-level citizen in the graph.When hyperlink is running with the
--internalswitch, https://vimeo.com/49026951 get checked as part of the run as if you had called hyperlink directly on that URL.If hyperlink is running with the
--recursiveswitch activated, having https://vimeo.com/49026951 in the graph will result in a complete traversal of the entirety of https://vimeo.comThis case is equally relevant where no cross-domain jump is happening. Running hyperlink non-recursive should fo course also never result in another page being expanded upon, even if it was local