201–210 of 340 posts
Earlier quoted context omitted.
Brussels sprouts are good for you. AMP is more like medical experiments performed on you during an alien abduction.
What's up with this extreme hatred for AMP? I personally love AMP.
Type "amp sucks" into a search engine to find out more.
Remember the talk about how the Chrome team was going to "rethink" the navbar, and what domain and site identity really mean? And people were a little worried about this? Turns out people were right to be suspicious. This is hot garbage. You can no longer ask a user "What URL does your navbar say you're at?". It is no longer a source of truth. They will actively be lied to.
But what does it mean that you are on a particular URL? For a long time already it's not being connecter to a particular physical server. Now it's the next step - to be completely decoupled from the server and just mean content instead.
Earlier quoted context omitted.
The CDN is you, for all intents and purposes. It's your agent in the back and forth, as much as your hosting provider would be. A third-party cache isn't. I don't mind that you can sign and verify content, that's fine and useful. I'm just not a fan of changing the address bar's meaning.
But what I'm saying is that the meaning that you ascribe to the address bar is incorrect -- it already only tells you who published the content, not who you are actually connected to. What I'm saying is that this does not change the meaning of what's in the URL bar. It's the same as before. It tells you who published the content originally.
No, it tells you the origin of the document. If you are the creator, and you choose to put your content on server X it will tell you "I've got this from server X". Whether that server is a reverse proxy or a shared webhost or a dedicated server in a DC or a raspberry pi running on your desk doesn't matter - it's the designated original that you, the owner of example.org chose.
That's what it always meant, and it changes when you do a redirect, and it shows you the current URL even if there is a canonical header of http-equiv. I can put a reverse proxy on my host and proxy example.com to example.org - the address bar tells you that you're reading example.com, not example.org, as it should, because you're connected to me, not to example.org.
Earlier quoted context omitted.
next month they'll also style it like your browser's native address bar for a better user experience and intoduce a w3c standard API for hiding the real address bar. /s?
They already had the braindead idea of hiding parts of the URL like "www." or "m." so it's not that unrealistic unfortunately.
This is such a strange reaction from HN. The AMP cache URLs have been a top 3 complaint about AMP here. "I can't copy-paste URLs, it's hard for users to understand which site they are on, it looks like the content is provided by Google rather than the real provider", etc. Now there's a solution that preserves the preloading and validation benefits of AMP caches but maintains the original URLs, in a way that's cryptog…
* does not show all comments, often ones I am actually looking for
* does not let me collapse comment sections
* uses the default white background theme which burns my retinas if I am looking at my phone in a dark environment
* shows overlay ads for the Reddit app that cover about 40% of the screen for no goddamn reason
* requires 2-3 separate actions to get to the original page
Yet I cannot find a browser extension or setting to tell AMP to fuck off. Honestly AMP might be what finally gets me to switch search engines after many years of using Google.
Earlier quoted context omitted.
AMP allows Google to see exactly how you interact with every page on the internet. Just from the text of the pages you visit they can build a profile around you. What your interests are, how much of an article you're likely to finish, whether you're the type of person to highlight text as you read, etc. Unless you live on an island with a poor satellite connection AMP is useless as anything more than a corporate user…
AMP documents don't share user data with Google, which can be trivially seen by inspecting the network events that the page generates. If the publisher chooses, they can send logging to Google Analytics, but this is not part of AMP. The typical argument otherwise is that the AMP javascript is loaded from Google's cache, however these javascript resources allow for a very long cache lifetime (1yr if the page came from…
They might not now, but could ‘t Google start creating unique URLs on each page, allowing them to track you that way?
Earlier quoted context omitted.
> And you're also back to the situation where you can't preload the content in a controlled manner or privacy-preserving manner... A few people have pointed out the privacy-preserving aspect of AMP. I'm not sure I get how that's the case. Is this referring to the fact that the page is not being pre-loaded from the content owner's own webserver? The main privacy violators on the internet are Google and Facebook. How i…
Good question. If you make a search query, but have not clicked on any results, you have a privacy expectation that the web servers of the search results you have not clicked on will not know you performed this query, your ip address, cookie, etc. For example, if you search for [headache] and then close the window, mayoclinic.com knowing that you made this query would probably be a surprising result. With naive prelo…
At its root, I think my objections to AMP boil down to a few things:
On a technical level:
1. It's buggy and weird on iOS.
2. I'm not convinced I care about a few seconds of loading time enough to justify the added complexity of making this kind of prefetching possible. Additionally, this seems like a stop-gap that will be rendered unnecessary by increasingly wide pipes for data.
On a philosophical level:
3. It gives Google way too much power over content.
4. I want the option to turn it off completely because of points [1] and [3], and because I fundamentally want to feel in control of my internet experience.
Edit: The point about SXG making AMP URLs less likely to get copy/pasted to other mediums is a key benefit I hadn't considered and will likely make avoiding AMP outside of Google search easier.
I can’t believe there is no way to opt out of AMP as the end user. The UX is so terrible. Often times I will search for something and have a Reddit result come back. When I tap the link, I get the AMP page which: * does not show all comments, often ones I am actually looking for * does not let me collapse comment sections * uses the default white background theme which burns my retinas if I am looking at my phone in…
Earlier quoted context omitted.
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 mor…
There is a difference between the web publisher controlling that abstraction and a web publisher that has been strong armed into one abstraction or another.