最近の検索
検索オプション
For that purpose, it is convenient if the original server (content holder) has signed the content with server's private key so that the ogp clients can cache the key and verify the data received from the third-party server.
This will require servers to work with less power, because ogp data will be (usually) dynamically generated, but servers' private keys can be completely static.
Additionally, this mechanism will be good for oEmbed, because oEmbed data *should* be generated dynamically.
There is another option: use distributed filesystem (e.g. IPFS) instead of signing every content manually ;-)