Yahoo-based parking companies made the switch to Bing this month. Domain owners saw stat delays on TrafficZ, Parked, SmartName and WhyPark as these changes took place. U.S. and Canadian ads are now coming from Microsoft's Bing service rather than Yahoo. Bing also uses Greenwich Mean Time (GMT or UTC) for their reporting, so these services have had to standardize on this - making the month of October a few hours shorter than it would otherwise be.
"Since 100% of the traffic is at Bing, our numbers are down quite a bit. But we don't know what is going on either. I have talked to other parking companies and people who have direct feeds with Yahoo and they are seeing the same issues on their side."Domain owners have also noted stats and reporting delays. Bing is said to be sending the numbers to Yahoo and Yahoo is sending them to the parking companies. This is a new role for the people at Bing, and they may be just working the kinks out. Yahoo and Bing are supposed to be continuing to give companies the same share of total revenue that they did before, but some are skeptical about this. Apparently singular and plural search terms can sometimes pay very differently on Bing. Parked reportedly is planning to implement systems to automatically display ads for the better search term - singular or plural.
Kudos to Donny Simonton of Parked for keeping everyone up-to-date on this change. SmartName also sent everyone an email letting them know about the change, but not in the blow-by-blow manner that Donny covered this change.
Many websites, like eNom, use SSL for their login process. Once you are logged-in, however, they send you a cookie with your account settings in a manner that is insecure. Hackers have always been able to read this cookie, but now 300,000 other people who have downloaded the FireSheep plugin can also do this.
The fix - Don't use unsecured wifi hotspots. Steve Gibson, well known PC security analyst is on record recommending that Starbucks secure all of their hotspots and just require people to login with the password "Starbucks." That's all it would take. The destination website itself, such as eNom, should also stop sending an unsecured cookie. Like banks, they could simply encrypt everything. That is the best fix - and all domain registrars need to set up full https encryption across their sites as soon as possible