4 ms·
I was under the impression that those kinds of tricks already happen with today's technology. Advertisers will put the advertised price in a hotlinked image se
by cbhl 8y ago
I was under the impression that those kinds of tricks already happen with today's technology.
Advertisers will put the advertised price in a hotlinked image served from a server, and they will both (1) use the image being fetched as a proxy for the email being downloaded/opened/read, and (2) change the contents of the served image after-the-fact. ("Save this email and open it every day this week for a new deal" and other horrors.)
Alphabet's Code of Conduct can be found at https://abc.xyz/investor/other/google-code-of-conduct/ https://abc.xyz/investor/other/google-code-of-conduct/ . I'm pretty sure "all our users" is intended to include advertisers and rightsholders (like music labels, movie companies).
- ocdtrekkie 8y agoThe AMP Project actually maintains it's own code of conduct, which is what was being referred to in my comment: https://github.com/ampproject/amphtml/blob/master/CODE_OF_CONDUCT.md https://github.com/ampproject/amphtml/blob/master/CODE_OF_CO... I don't have any inherently issue with CoCs, though I find it irritating when threat of "enforcing the CoC" is used as a method to silence legitimate, reasoned criticisms.
- Bartweiss 8y agoI'm curious what the implied violation was, if only for the benefit of other people thinking about CoCs. The "What We Believe" section certainly has lots of open-ended language; it's quite easy to declare any unwelcome criticism 'unconstructive', or any dissenting views 'tactless'. But the "Don't" section is quite a bit more concrete, and mostly wouldn't apply. Was the implication that "this is a fundamentally bad idea" counts as "derailing" or "unstructured critique"?
- simpss 8y agohere's what he's referencing: https://github.com/ampproject/amphtml/issues/13457 https://github.com/ampproject/amphtml/issues/13457 https://github.com/ampproject/amphtml/issues/13597 https://github.com/ampproject/amphtml/issues/13597 and the resulting(check the timestamps): https://github.com/ampproject/amphtml/issues/13603 https://github.com/ampproject/amphtml/issues/13603
- dmitriid 8y agoOnly that process never materialised.
- simpss 8y agotrue, I initially missed the final response & only noticed it now when I linked the discussions. It is a bit disappointing and follows the common "wait until it cools down & give a non-response" pattern. But it's actually more than I expected. A response like this shows that they really were in a bit of a blinder there for a sec :)