| It's probably best for me to provide an example. We create three URLs for each media asset. For [1], [2], and [3] you can click our icon in the top right corner: - A link to the asset itself (just the JPEG or whatever with embedded ID) [0] - A link to a preview with twitter card, facebook open graph, etc support suitable for sharing (and re-sharing) on social media [1] - A link to an iframe embed for use wherever else [2] For an asset where the user has configured the metadata to be hidden our verification API doesn't return anything other than the checksum to validate against [3]. Users can update the returned metadata at any time or hiding of the extended metadata and it's updated dynamically and instantly - everywhere. So this way producers and consumers of content don't need to have a dedicated consumption implementation (but it could certainly be branded or white labeled to the content producer). Currently the client is just our javascript but we're working on mobile and browser extensions that can run anywhere against the raw asset link provided in [0]. [0] https://share.tovera.com/assets/c65b0658ab6e4d89963b1e0a319a... [1] https://share.tovera.com/preview/c65b0658ab6e4d89963b1e0a319... [2] https://share.tovera.com/embed/c65b0658ab6e4d89963b1e0a319a1... [3] https://share.tovera.com/preview/e51de3d34bfe47d7bc25fb8f252... |