Skip to main content

Yahoo! Publisher Network Beta to Close April 30, 2010

I received this email today regarding Yahoo Publisher Network to get axe! Here's the original email from Yahoo.

Dear Publisher,

Yahoo! continuously evaluates and prioritizes our products and services, in alignment with business goals and our continued commitment to deliver the best consumer and advertiser experiences. After conducting an extensive review of the Yahoo! Publisher Network beta program, we have decided to close the program effective April 30, 2010. We expect to deliver final publisher payments for the month ending April 30, 2010 to publishers no later than May 31, 2010. All publishers eligible for 1099s for the 2010 tax year will have those mailed by January 31, 2011.

Because our content will no longer be delivered to your ad unit spaces after April 30, 2010, we recommend removing all YPN ad code from your pages by that date.

For the opportunity to continue earning revenue, we suggest using Chitika, a leading advertising network that syndicates Yahoo! Content Match and Sponsored Search ads. Chitika has set up a special process for YPNO beta publishers to participate in its platform. Click here for more information.

We thank you for your participation in the Yahoo! Publisher Network beta. If you have any questions regarding this announcement, please contact our Support Team at (866) 785-2636, Monday through Friday from 7:00 a.m. to 5:00 p.m. PDT. 
Sincerely,

Your Partners at Yahoo!
The cool think about Chitika is you can use the ads with Adsense campaign. I will take a look and try Chitika ads in KING.NET News Portal site. We'll see if they can bring additional income.

Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​
http://buddypress.org/ - Wordpress (Open Source and Free)http://elgg.org/ - (Open Source and Free)Commercial Social Networks software
http://www.socialengine.com/ ($299 Stand Alone, $29/mo Cloud)http://www.jomsocial.com/ (run with Joomla, need to know CMS)http://www.boonex.com/ (very expensive, $399 for Standard)http://www.anahitapolis.com/http://www.oxwall.org/http://sharetronix.com/http://www.moosocial.com/http://www.jcow.net/http://phpdolphin.comhttp://www.grou.ps (from free to Commercial, I left my networks and they are selling it http://www.phpfox.com/ (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company)http://www.ning.com (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at johnsmith@king.net (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at marysmith@king.net.
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here:
http://www.whaddya.com/2011/09/windows-needs-your-credentials.html