Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AMP pages displaying your own domain

webmasters.googleblog.com

Post reply on HN
Print view View original

11–20 of 340 posts

Re: AMP pages displaying your own domain

#11

Post by 48309248302 »

This 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 JavaScript disabled.

Also, the feature only works on Google Chrome and possibly Edge, which gives another point to the article below.

https://www.zdnet.com/article/former-mozilla-exec-google-has...

AMP is a fundamentally bad idea that needs to disappear.

Edit: Mozilla has marked Signed HTTP Exchanges as harmful.

https://mozilla.github.io/standards-positions/

Re: AMP pages displaying your own domain

#12

Post by 48309248302 »

ganeshkrishnan wrote: post #8
iandanforth wrote: post #2

I feel like Google is pushing AMP and components too hard. I've started to balk at the idea of using them even for explorations.

AMP is like Brussels Sprouts. If it's forced on you when you are young, you will grow up hating it.

Brussels sprouts are good for you. AMP is more like medical experiments performed on you during an alien abduction.

Re: AMP pages displaying your own domain

#16

Post by chii »

48309248302 wrote: post #11

This 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?

Re: AMP pages displaying your own domain

#18

Post by Lammy »

ganeshkrishnan wrote: post #6
RHSeeger wrote: post #4

Earlier quoted context omitted.

The other half actively despise it.

"Your website has been banned for illegal activity and all content has been deleted. The suspension is immediate and indefinite. Please consider using another Internet" Also, their algorithms mistook live streaming of Notre Dame fires as 9/11 incident. How can live stream be a past incident? https://abcnews.go.com/Business/youtube-mistakenly-flags-not...

You are confusing the term “live stream” to mean something actually happening at that moment in the real world. All a “live” stream actually is to Youtube or FB or any other streaming service is just incoming RTMP packets. Youtube matches incoming streams against their ContentID database just as they do for normal uploads. I would bet that the same thing would have happened if the same footage were uploaded normally after the fact. People will use unlisted streams to broadcast pirated content otherwise. I faced a similarly false claim once where me playing Super Mario World on a real life SNES was falsely matched to some major label song, and since it was my third strike (all false) my account got banned from being able to use Youtube Live entirely. In the end I’m kind of glad that happened because it led to me developing my own minimal self-hosted stream site for small friends-only streams, including things Youtube would give legit claims for. My tiny VPS wouldn’t stand up to thousands or probably even dozens of simultaneous viewers like Youtube or the other big names can, but that doesn’t matter at all for me.

Re: AMP pages displaying your own domain

#19

Post by 48309248302 »

chii wrote: post #16
48309248302 wrote: post #11

This 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?

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 doing with IE in the old days.

4) I don't publish on Github pages, but if I did, I would still have a choice over which servers I put the sites on.

5) There shouldn't be a single company (or few companies) that dictates how we publish online.

6) Shame on the people who are splitting the web with this fake-opensource technology. There's even a Google engineer over here referring to the Web like it's a Google product. https://news.ycombinator.com/item?id=19631136

Re: AMP pages displaying your own domain

#20

Post by stephenr »

notatoad wrote: post #9
skilled wrote: post #3

I wonder if Google is self-aware to the fact that majority of webmasters don't give a shit about AMP.

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.

Post reply on HN