Live data from Hacker News

Google May Be Stealing Mobile Traffic

alexkras.com

141–150 of 261 posts

Re: Google May Be Stealing Mobile Traffic

#141

I don't (and never will) use AMP and I feel that it is patently unfair to penalize pages for not using some non-standard tech. Google should index the web fairly, not make use of their tech a factor. Webpage speed is a fair measure (and I really wouldn't know what I could do to make my pages any faster, AMP will not make a measurable difference). I would expect an un-biased search engine to rate pages with and withou…

In my opinion, the problem is that your version of unbiased doesn't add much value to a user (and is actually biased for the website-owners). For example, SourceForge started adding a lot of misleading 'Download' buttons all over their page, and they might ask the same thing about 'an unbiased ranking' (Google's always been criticized for being the 'Web Police'). As a user however, I'd want Sourceforge's rankings go…

The best solution to combat bloat is less bloat, not faster ways to deliver bloat (all that will do is increase the budget for bloat).

Re: Google May Be Stealing Mobile Traffic

#142
post #95

Earlier quoted context omitted.

Well other than being riddled with security holes. It has its place, but never use it on user-submitted images.

While that may have been true in 2014, today it's hard to find an exploitable bug affecting a major image format parser in ImageMagick. Assuming you aren't using unsanitized user-provided parameters on the command line with it, it should be fine unless your attacker is very motivated.

There was an RCE vulnerability this year: https://imagetragick.com/

Re: Google May Be Stealing Mobile Traffic

#143
post #20

> Consider adding a link at the top of your AMP page, giving user an option to visit the original post Why should they want to read the post again? The only viable option is to have links to other posts on your site, or maybe a link to the comments. By the way, what's the purpose of the bar at the top? The back button of the browser already does that, even on mobile. About analytics: I don't know if those accesses do…

> Why should they want to read the post again

Or if they want to copy paste an url to email (perhaps that's too advanced a feature...), it looks like a "let me google that for you" site, not what they're actually sending. Yay.

Re: Google May Be Stealing Mobile Traffic

#144
post #138

"I hope I am not being too hard on Google." -- no, the author is being very, very nice. Google has a strong business interest in users never going to other sites. Between AMP & voice search, the future is going to be very rough for businesses that rely on free search traffic. In practical business terms I would strongly suggest website owners build ultra-light versions of their sites. If you have international aspira…

How do you suggest publishers who are dependent on traffic from Google cope with AMP in the short-term? It seems like there is no way to compete with AMP-enabled content on Google ranking except by adopting AMP.

Re: Google May Be Stealing Mobile Traffic

#145
post #81

Earlier quoted context omitted.

I said "techies like me". Thats not extrapolating anything. Obviously much less experienced techies still need to look up how many sides a square has at least twice a day.

> I said "techies like me" A data point of one isn't particularly descriptive.

While i'll take the compliment that you think i am that unique.

I'm pretty sure I'm not.

Re: Google May Be Stealing Mobile Traffic

#146

I don't (and never will) use AMP and I feel that it is patently unfair to penalize pages for not using some non-standard tech. Google should index the web fairly, not make use of their tech a factor. Webpage speed is a fair measure (and I really wouldn't know what I could do to make my pages any faster, AMP will not make a measurable difference). I would expect an un-biased search engine to rate pages with and withou…

Does anyone know how to disable AMP?

Re: Google May Be Stealing Mobile Traffic

#147

Earlier quoted context omitted.

That's your experience. In my experience, AMP pages are horrible and I avoid clicking on those.

Why don't you like them as a user? They load extremely quickly and you can scroll through the different AMP pages by simply swiping left or right.

The scrolling is messed up and I cannot share the original link easily. And non amp pages load just as fast if I just disable js.

Re: Google May Be Stealing Mobile Traffic

#148

Earlier quoted context omitted.

> I would expect an un-biased search engine to rate pages with and without AMP equal Well there's your problem :-). Google isn't an unbiased search engine, they're a commercial entity with a financial interest in feeding you particular search results. They're absolutely going to be biased in the results they provide you.

They also have near-monopoly status on search, so they must not be anticompetitive.

But it will take years for the government to do anything about it.

Longer, perhaps, if Hillary is elected with Eric Schmidt's help.[1]

1: http://qz.com/520652/groundwork-eric-schmidt-startup-working...

Re: Google May Be Stealing Mobile Traffic

#149
post #42

Earlier quoted context omitted.

To be fair, as a user... I absolutely love AMP. (That being said, I dislike it as a content provider and as someone worried Google has too much power)

Yep, in the short-term it's a good thing for users because it means they can access the content they are looking for more quickly in a consistent format. In the long run, it might be bad for users, as it could result in media producing less valuable content, and one big company having more control over distribution.

But content isn't really valuable anyway. If there's less of it, then I'll make breakfast a few minutes earlier - that's all.

Re: Google May Be Stealing Mobile Traffic

#150

Earlier quoted context omitted.

It would be amazing if every website were designed like Wikipedia. With the exception of MediaViewer, Wikipedia is one of the best-designed websites out there. It's light, content-prominent, progressively enhanced, HTTPS-only. Even their mobile site is pretty good (though basically all mobile experiences are bad nowadays). What exactly is wrong with Wikipedia's design?

Wikipedia's mobile site is fantastic, IMO. I really wish all mobile sites were like Wikipedia's. The pain of browsing the web on mobile would go away completely.

I think it's mostly OK. A lot of my problems with mobile would be alleviated if I could get a browser to reflow text on demand. It used to be you could set your zoom level, double tap and the page would reflow to the new zoom level. This doesn't seem possible now, so I'm always scrolling side to side if I want to be zoomed in a bit more.

I have a few other minor problems about how Wikipedia's mobile page handles without Javascript enabled, but one big thing is that there's a minimum zoom level set. I can zoom in, but I can't zoom out, which means if I want more text per line, there's nothing to be done. This again feeds in to the lack of reflow in mobile browsers. I have no idea why this feature went away, but it completely ruined the mobile web for me.

Post reply on HN