Skip to main content

Tell-a-Friend widget from Socialtwist

Tell-a-Friend is free and simple to use widget from Socialtwist, just copy and paste. No integration or coding.

Tell-a-Friend widget help Users share content across IM and Email without leaving the site. It synchs with their IM, email in the context of the content they're sharing without those tedious pop-up forms that require manual input. Tell-a-Friend widget is one of the best word-of-mouth marketing tool in existence. 

image

Tell-a-Friend widget is completely free and hosted by Amazon EC2, so you know it's scalable. For corporate users a paid service is available with additional options like Widget UI skin matching your site, Custom context wiring and Activity database at your control.

Tell-a-Friend widget can be used at Product Pages to replaces the traditional "Email a friend" link to spread the word on products/brands/sites. Search Results, News Items, Blog Posts - word-of-mouth is the best way to direct traffic to your blogs, Get the word out - make time sensitive announcements contests, events and offers to spread the word instantly.

Video Tour:

Installation Instructions: http://tellafriend.socialtwist.com/wizard/html/instructions/blogger.html
http://tellafriend.socialtwist.com/wizard/html/instructions/website.html
http://tellafriend.socialtwist.com/wizard/html/instructions/wordpress.html
http://tellafriend.socialtwist.com/wizard/html/instructions/textpattern.html

Comments

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog ...

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...