[LEAPSECS] private smear goes public

[Christopher Hoover]

I'm not speaking for Google (and have no specific knowledge) ...

I think the forcing factor was cloud computing not ad networks.


On Fri, Dec 2, 2016 at 1:00 AM, Poul-Henning Kamp <phk at phk.freebsd.dk>
wrote:

> --------
> In message <58407DE7.1030905 at edlmax.com>, Brooks Harris writes:
>
> > As I read it I think Google's intention is to publish their method and
> > algorithm in the hopes others may follow it. It would be better if
> > everybody did it the same way, but it will remain to be seen if others
> > will choose to follow the example.
>
> No.
>
> Googles *problem* is that they decided to smear internally, but provide
> tons if APIs for the rest of the world.
>
> The most valuable of these APIs, in terms of money, from Googles
> point of view, is the on-line, real-time bidding for ad-space in
> front of your eyes [1]
>
> Google running on private time up to half a second different from the
> rest of the world doesn't work in that scenario, so either Google
> had to drop their smear ... or make the consumers of their APIs
> use their smear too.
>
> Guess what happened...
>
> Poul-Henning
>
> [1] Ever wondered what "google tag manager" is about ?
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> _______________________________________________
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
> https://pairlist6.pair.net/mailman/listinfo/leapsecs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20161202/804d2449/attachment.html>