Re:Fight back against Google AMP (2018)
by Ajedi32 on Wednesday December 04, 2019 @01:28PM
(#21705276)
The standard is brand new, and AMP was the motivating factor for its creation, so obviously the majority of existing use cases are AMP-related. That doesn't mean you couldn't go and implement a non-AMP use case in your own production site today.
Re:Fight back against Google AMP (2018)
by dane-pgp on Wednesday December 04, 2019 @03:47PM
(#21706733)
One interesting use case for SXG is to allow decentralised and offline websites, since the site's data can be tied to a key/certificate/domain without having to be downloaded from a specific server. As an example, the IPFS project is already trialling the technology:
Re:Fight back against Google AMP (2018)
by buboard on Wednesday December 04, 2019 @06:13PM
(#21708216)
tying it to a domain name (which is the typical use of the URL) breaks the web though. i could understand if the key is used to show that the origin is a twitter account handle or something, but breaking the semantics of the domain by signing the content doesn't make any functional sense. Other than putting lipstick on a pig (AMP) of course
Or maybe you have some notable examples of SXG being used in a production non-AMP scenario?