Seems like a reasonable idea. The content server says "here, you hold this for me", and the address bar only shows who originally signed it.
One could imagine replacing the serving layer with something like BitTorrent or IPFS.
AMP pages displaying your own domain
21–30 of 340 posts
Re: AMP pages displaying your own domain
#22Semi-related, I think Web Packages and Signed Exchanges could have some usefulness outside of Google's caches. One of their spec examples was for verifiable web page archives.
Another idea it could be used for a wifi "drop box" (drop station?) when there's no internet connection around. That isn't uncommon at some popular spots up river into the woods in the US.
The idea is that as people enter the area, they can update the drop station automatically for things like news or public posts with whatever they've cached recently.
I'm pretty sure I read about this idea before the spec was drafted but I couldn't find or remember the site, something like vehicle-transported data.
Re: AMP pages displaying your own domain
#23Does nothing for publishers' needs for deeper control and analytics. Just a "feel good" gesture that results in additional complexity for everyone involved. Google is not the only company in the world that knows how to load a page efficiently.
Re: AMP pages displaying your own domain
#24Earlier quoted context omitted.
I wonder if any webmasters are self aware that their users like amp
Users like pages that load quickly, which amp is not a requirement for. Amp is designed to tighten googles grip on the web, nothing more.
No it isn't. It's designed to make the user experience better on sites that frequently host Google ads (and also often contain a ton of bloat, 3rd party js, poorly constructed DOMs, awful CSS, etc).
The only way Google could proactively "solve" this problem was by creating a "standard", and then also offering to absorb end user traffic for sites that adopted the standard. FWIW, AMP is an open standard not solely owned or contributed to by Google.
Re: AMP pages displaying your own domain
#25Earlier quoted context omitted.
> I don't want my content restricted or hosted in Google's cache. how is this different than using your own domain, but pointing it to a github.io page? Or using medium, but with your own domain (but still being served from medium's servers)? Is it just google you're adverse to, or the entire idea of someone else hosting your content?
1) I want full control over my servers and to not be penalized in search engines for not hosting my sites on Google. Where are the server-side logs? 2) I want full control over how I publish my sites with real web standards. AMP is not a web standard, it's a Google format that they are strong-arming people into using. 3) Mozilla considers Signed HTTP Exchanges harmful. This technology is as bad as what Microsoft was…
As per point 6, I wouldn’t take what was said there as a statement from Google, or potentially even an employee of Google. They did it as a throwaway .. anybody wishing to kick the hornets nest could have posted that, employee or not.
Re: AMP pages displaying your own domain
#26Earlier quoted context omitted.
I wonder if any webmasters are self aware that their users like amp
Users like pages that load quickly, which amp is not a requirement for. Amp is designed to tighten googles grip on the web, nothing more.
I partly agree with this. If you run a WordPress blog, then EasyEngine [1] and OpenLiteSpeed [2] can really boost your site performance.
The performance will be greatly affected if you run some cancerous theme with endless JavaScript calls. But both of the mentioned "engines" have changed the way I see blogging with WordPress.
Best of all, this is accessible to your average user as well. DigitalOcean can spin you up an OLS instance in a minute or so...
Re: AMP pages displaying your own domain
#27With the peerweb.com platform I will be providing a free-for-non-commercial-use polyfill for Signed HTTP Exchanges which can be used for distributed p2p content offloading.
Peerweb helps sites automatically offload all resources (including streaming ugc video) to a decentralized p2p network.
ETA: ~1yr
Re: AMP pages displaying your own domain
#28This sounds terrible. Does it mean that browsers will begin lying to users and say that the users are visiting the website's server when they are really visiting a restricted version of the website that is hosted in Google's cache? I don't want my content restricted or hosted in Google's cache. AMP doesn't load in a privacy sensitive way. It's on Google's servers and it takes many seconds to load if you have JavaScri…
> I don't want my content restricted or hosted in Google's cache. how is this different than using your own domain, but pointing it to a github.io page? Or using medium, but with your own domain (but still being served from medium's servers)? Is it just google you're adverse to, or the entire idea of someone else hosting your content?
That's a good point! Domain owners can host their websites wherever they like, and yes that includes Google's cloud.
If they go through a content network like Cloudflare, you can't even tell who's hosting the site by looking at the IP address.
It drives home the point that websites are abstractions that have no necessary relationship to any particular physical hardware. Network tools may or may not tell you a bit more about the source, depending on if there are any leaks in the abstraction.
Re: AMP pages displaying your own domain
#29Earlier quoted context omitted.
1) I want full control over my servers and to not be penalized in search engines for not hosting my sites on Google. Where are the server-side logs? 2) I want full control over how I publish my sites with real web standards. AMP is not a web standard, it's a Google format that they are strong-arming people into using. 3) Mozilla considers Signed HTTP Exchanges harmful. This technology is as bad as what Microsoft was…
As per point 6, I wouldn’t take what was said there as a statement from Google, or potentially even an employee of Google. They did it as a throwaway .. anybody wishing to kick the hornets nest could have posted that, employee or not.
It's not written like someone trying to kick a hornet's nest. It's written like someone who has been conditioned inside of a culture that has begun to view the Web as a Google product on some level.
Re: AMP pages displaying your own domain
#30Let’s hope AMP, like most google products, is shut down within the next 2-3 years
Amen!