Slashdot Mirror

← Back to Stories (view on slashdot.org)

Defining Clicks and Click Fraud

Posted by ryuzaki0 on from the now-define-what-the-definition-of-'the'-is dept.

abb_road writes "Google, Microsoft and Yahoo have banded together and created the Click Measurement Group, with the goal of creating a standard definition for a 'click'. The group will have some access to the three companies' click data, although the access won't be unlimited. The move comes in response to advertisers who claim that click fraud is costing them almost $1 billion dollars a year, and who have hit Google and Yahoo with lawsuits alleging negligence in fighting click fraud."

2 of 78 comments (clear)

  1. Re:Dupe? by aztracker1 · · Score: 0, Offtopic

    Honestly I find it kind of funny they can get together on click fraud (which can seriously cost them money), but can't come together on a good solution for SPAM, or even the psuedo anonymity (SPF). I know that SPF isn't an antispam solution, it's a partial authentication solution.. but strong SPF requirements by MSN/Hotmail, Yahoo, GMail and AOL would force everyone to start sending email from where it belongs... IMHO it would be nice if email was required to come from an MX server for a given domain.. yeah, using SMTP Submit port (587) and SMTP authentication is *SO* hard.. :/

    I know I've gone off topic, it just kinda irks me they can work together on this, but not spam.

    --
    Michael J. Ryan - tracker1.info
  2. Re:Dupe? by CustomDesigned · · Score: 0, Offtopic
    yeah, using SMTP Submit port (587) and SMTP authentication is *SO* hard.. :/

    Having wasted many days on this, if your customer uses Outlook, it *is* hard. Those that I could convince to run Thunderbird had it up and running out of the box first time. Outlook is a nightmare. It is a chinese puzzle. It does not support normal SASL (providing only NT passwords). It only supports STARTTLS (so it can use LOGIN passwords) on port 25. Whenever you change the SMTP port, it resets the IMAP settings to defaults. Many versions do not support SMTPS on any port either. The customers in question will not upgrade Outlook, much less switch to some other client. I have 2 customers with an Outlook version that seems to be completely unworkable for SMTP AUTH. Of course, stupid firewalls that the customer doesn't know about can interfere with "non standard" ports like 465 (smtps) also.