A Guest Post by David Cleland from TotalApps.

In 2006 I proudly started my first blog, DigMo! It was technology, it was creativity, it was music and it was education. Despite it being a bit of blog soup I was pleased at how quick the site grew but within a few years it reached a critical point beyond which I really couldn't get the traffic to grow. The site was frankly far too general to appeal to a specific community.

The site had a massive 80% bounce rate and taking advice from reading the great advice on this site I decided to take stock and critically re-evaluate the future of DigMo!

As a result I decided to split the site and create two separate niche blogs, DigMo! To focus on educational technology and I launched a new site, TotalApps, to focus on Mac and iPhone App reviews. The thought of starting from zero scared me and I looked at ways to get the site up and running quickly.

I decided the best way to draw attention to the blog was to offer regular site competitions. Finding companies willing to sponsor prizes was actually much easier than I initially expected. I tend to target companies whose product I have reviewed and especially if the review has been popular with readers.

With blog authors being urged to declare any products they are able to keep once a review is published what better way to retain your creditability but by passing the review samples on to your readers as a competition prize ? It seems to me like a logical benefit that will add value to your site and grow the community.

The Mistakes

I think it is best to share my mistakes with the Problogger readers and the initial competitions I ran simply required visitors to leave a comment on a post. This didn't grow the site and managed to result in a massive 70% bounce rate i.e. the users came, entered, and left knowing we would email them if they had won.

The Successes

I decided if I was going to make competitions really work they needed to be of benefit not only to the visitor but also the site and thus I needed to limit entry to RSS subscribers (both email and reader)

The solution was simple and surprisingly successful and will basically work for anyone running a Wordpress blog even with a custom theme.

Setting the competition up takes a tiny bit of code adjusting but nothing too difficult.

The Concept

The competition works by placing a code at the bottom of blog posts that will only appear when the entry is read in an RSS reader, i.e. it does not appear on site.

To do this I used a known solution that was pointed out to me by fellow blogger Thaya Kareeson.

There are a few versions of this idea around but this solution works brilliantly on TotalApps. As I haven't come across any plug-ins that can run competitions this bit of code fiddling is the ideal solution for now.

Getting Started

Open the functions.php file in your current theme folder (I would back this up before adding the code just to be on the safe side).

Paste the following code into the text :

function contest_post_filter($content) {
if ( is_feed() )
return $content.'TotalApps Competition Code (Please note it is case sensitive) : a12221s';
else
return $content;
}
add_filter('the_content','contest_post_filter');
function contest_comment_filter($comment_text) {
return str_replace('a12221s', '[code hidden]', $comment_text);
}
add_filter('get_comment_text','contest_comment_filter');

There are two lines you need to change - 1. the line that says TotalApps Competition Code and 5 lines down the code is repeated (a1221s).

I recently ran a competition where visitors could win a copy of Screenflow 2.0. The following screenshot shows the bottom of the post as it appeared in the browser.

. and this is how it looked in the RSS reader. You should note your RSS Feed must be the full article view (i.e. not just the abstract) for the code to appear.

When the competition closes as I generally ask the sponsor to select a number between 1 and the number of comments and then contact the lucky winners using the email address in the comment.

When a competition closes you can either comment out the code in functions.php by adding /* before the code and */ after or alternatively is simply change the text to "No competition at present"

Offering a reason to sign up to the RSS feed resulted in the number of TotalApps RSS subscribers growing in one month to double the number of readers DigMo! had after 3 years.

Tips :

• Know what your readers want and try and target prizes appropriately.
• Make sure you link to your RSS and RSS by Email Feeds in the post to make it as easy for visitors to subscribe as possible.
• Make sure you make the rules clear and post the winner's name publicly on site.
• Where possible have the competition sponsors look after the postage. This not only saves you time and hassle but it is also assures the sponsor the competition is above board.
• Don't run competitions for more than a week as most of the comments tend to happen in the first week after that it dries up quickly.

I have to say I am certainly no expert in coding or blogging but am really excited to find a solution that really works for managing the competitions and I am equally as excited to see the number of subscribers grow.

There may even be better solutions out there and if you know of any I would be keen to hear them.

David Cleland is a teacher based in Ireland who runs three successful blogs (TotalApps, FlixelPix and Digmo.co.uk)

Post from: Blog Tips at ProBlogger.

How To Run Subscriber-Only Competitions on Your Blog

Share This

By Senior Editor Kris Smith (@croncast)

Like you, I've been a member and user of PayPal's service for years. They were early to the game and grew accordingly with a product that made buying online drop dead easy. With an exit to eBay they were integrated into a powerful money minting machine.

They also joined a culture of apathy and disdain for those that help them line their pockets developers.

Like their acquirer, PayPal continued to build a mediocre developer community, foster it with partial code samples, limited information and limited support. Now in kindness to PayPal they did begin providing better support a few years ago and are pretty good when it comes to engaging developers on the message boards offering solutions a problem that has plagued eBay for years.

Visit any eBay developer board and you'll find replies that focus on posting in the wrong thread topic instead of offering a solution. It shows the developers that they aren't a priority.

I was looking forward to the release of the brand spanking new PayPal X Developer Network. Hoping that my previous experience wouldn't hold true and that there would be a renewed focus on the developers that are integrating the PayPal gateways and API's into their platforms. But they let me down.

The new developer community site is plagued with broken links, the same old code samples and forums that stopped loading threads on October 28. The intention is there but the execution is hit and miss.

I can forgive them this time, though. Because it appears that their intention is to focus fully on their API implementations and integrate the legacy products like IPN and PDT into a more standardized solution.

Which will help PayPal as it moves toward working with developers to create a wider range of solutions like mobile and in application micro-payments.

Something else of note with the new PayPal X Developer Network is the improved site IA. Thank you to the person(s) that restructured the information and worked with the UI person(s) to highlight what developers want most . . . documentation.

DISCLOSURE OF MATERIAL CONNECTION: http://cmp.ly/0

PayPal X Developer Network Same as it Always Was is a post from: TechStartups.com

By Senior Editor Kris Smith

Startups, it's time to begin shortening and tracking your own URL's. Taking control of your data is the simplest way of measuring your engagement online next to direct conversations with users. Look at it like taking a survey without asking a single question.

So what?

There is a wealth of data to be collected from that shortened URL that can help you make your product(s) better. Take for instance if your job is to write blog posts and then tweet about them. If you're tracking the data yourself you can measure the most active click-through times and tweet then. Another example might be your desire to track other click-throughs and track the geo-location of your biggest fans.

Other great information to get from this one-click survey is what site did they use to click-through, also known in the biz as referrer and what some might call the holy grail of necessary data for digital product development, user-agent. For when you need to know the application or platform, such as mobile, to better your products. So that's so what.

So how?

There are a couple of ways to get it done. If you want the data and tracking that I described above without having to parse your log files you can use the code samples that I will add below. If you simply are looking for a way to brand your URL shortener and use it on Twitter, then you can follow the discussion and directions in this forum thread for using .htacess on Apache [http://www.webmasterworld.com/forum92/2545.htm].

For those of you ready to get it on with a kick start and build on top of it, here we go. I should mention that this is for those on a LAMP box. Not sure what LAMP means? This isn't for you then. If you do and are on another platform, feel free to follow along for the concepts.

First Get a short URL

The best choice doing this the right way is to figure out something that comes close to your regular URL. Say your site is goldfishbowlpirate.com and you found that gbp.me was available. Then you would snatch it up and your short URL's would look like http://gbp.me/1234. Make sure you host the account on a LAMP server.

Second Edit the .htaccess file

Simple copy and past job into your .htaccess file will get you on the road to tracking your click-throughs like a champ.

code: RewriteEngine On
RewriteBase /
RewriteRule ^[0-9] /

Third MySQL table

You'll need to setup a couple of tables: one to store the URL's that need to be redirected and one to store the click-through data.

The base table

CREATE TABLE IF NOT EXISTS `url_base` (
`url_id` int(11) NOT NULL auto_increment,
`url_key` varchar(6) NOT NULL default '',
`url_value` varchar(255) NOT NULL default '',
`bookmarklet` tinyint(1) NOT NULL default '0',
`user_host` varchar(255) NOT NULL default '',
`create_time` timestamp NOT NULL default CURRENT_TIMESTAMP,
PRIMARY KEY  (`url_id`),
KEY `url_key` (`url_key`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1;

The clicks table

CREATE TABLE IF NOT EXISTS `url_clicks` (
`hit_id` int(11) NOT NULL auto_increment,
`url_id` int(11) NOT NULL default '0',
`hit_host` varchar(255) NOT NULL default '',
`hit_time` timestamp NOT NULL default CURRENT_TIMESTAMP,
`hit_referer` varchar(255) NOT NULL default '',
`hit_agent` varchar(255) NOT NULL default '',
PRIMARY KEY  (`hit_id`),
KEY `hit_agent` (`hit_agent`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1;

Fourth Code it up

This is where the magic truly happens. We need code to create shortened URL's, handle the redirects by looking up the shortened URL in the url_base table and track the click-through in the url_clicks table.

I've created a zip file that has all the necessary files in it and the SQL above for download. Also Included in the zip are the .htaccess file and four PHP scripts.

1. config.php A configuration file
2. index.php To act as the index incase there is an error with the redirect
3. makeit.php To make shortened URL's. It can be called by other programs like an API
4. makeit_b.php To make shortened URL's for a Bookmarklet for easy testing and copy and paste. To use the Bookmarklet simply right-click on your bookmarks toolbar and paste the code below into the Location' section. Make sure to swap out yourshorturl' with your own!javascript:(function(){var%20a=window,b=document,c=decodeURIComponent,d=a.open('http://yourshorturl/makeit_b.php?url='+c(b.location),"bkmk_popup","left="+((a.screenX||a.screenLeft)+10)+",top="+((a.screenY||a.screenTop)+10)+",height=145px,width=200px,resizable=1,alwaysRaised=1");a.setTimeout(function(){d.focus()},300)})();

Now that you've got all the code you need to begin shortening and tracking your own URL's you can take a look at a sample of a very simple admin page. I've been using this system of shortening for nearly two years for all of my Twitter URL's.

A special thanks to Mike Marusin for writing the first version of this code for his own personal URL shortener back in 2007.

DISCLOSURE OF MATERIAL CONNECTION: http://cmp.ly/4

Post from: TechStartups.com

Tweet This Post

Eater.com is counting down the days until New York Times restaurant critic and "baby bulimic" Frank Bruni files his last review for the Paper of Record, going so far as to speculate who would succeed Bruni and prognosticating the odds of some favorites.

Names added to that list yesterday included one local writer: the ludicrously prolific Michael Nagrant of Hungry Mag, Serious Eats, New City and just about any paper or website that publishes a byline. Owning to all sorts of biases here as both a colleague and friend, if the Times really wanted to make a splash in naming Bruni's heir apparent few food critics have the resume of Nagrant; one that includes collaborating on a Beard Award-winning cookbook; a critic whose voice is constantly evolving; a entertaining and engaging writer equally comfortable in traditional and new media; one whose personal code of food journalism ethics is downright Orthodox Catholic in the age of the Yelp! Elite Squad.

I contacted Nagrant about his name popping up. He responded by saying that he's sent Times "Dining In/Dining Out" Editor Trish Hall samples of his work in the past two months for her consideration. Nagrant replied, "The New York Times food critic position is one of the most important jobs in American food writing. Whether it's (Ruth) Reichl or Bruni or (William) Grimes et al, as a writer I've looked to those who've held that chair and always tried to write to that standard. The NYT critic spot is very much a goal of mine." As to wanting to take the job in these uncertain times for print journalism, Nagrant said, "In these tough times for print journalism where some would rather be the next food TV star or own a restaurant, I want to write. I don't want to be rich or famous. I only want to sustain myself, practice the craft and get better everyday. I want nothing more as a writer and I'm willing to give everything I am if the honor came my way."

Nagrant acknowledged Eater's speculation yesterday with (natch) twitter updates, paraphrasing Groucho Marx and even providing a headshot so the Times doesn't have to.

After a full week of testing/documentation, I'm finally finished with IT Helper 1.0! I shouldn't say finally; it's been only 4 weeks since I introduced the project. I started out knowing nothing about Intel AMT (or even C#!) and managed to teach myself everything I needed to know to develop a working management console. More importantly, I used only the resources provided through the Manageability Developer Community. So there's no excuse! If I can do it, anyone can. Now go develop your own management console! Just kidding...

Developing for Intel AMT isn't easy. While 4 weeks may seem like a short time, keep in mind that I don't eat or sleep (I work 24 hours a day). That's 4 weeks * 7 days * 24 hours = 672 hours! I'm joking again. But developing a management console really does take time. Here's some quick advice on working faster:

• Understand the basic concepts. This is the best advice I can give. Know what you're doing before you start doing.
  • Check out my first and second blog posts for a good introduction to Intel AMT.
• Sign up for ISPP. The Intel Software Partner Program allows you to create a Project Plan based on the use cases and features you'd like to implement. Know where you're going before you start going.
• Take advantage of your resources. Read the documentation in the SDK. There are also plenty of samples that implement the same features that you're trying to implement. Don't try reinventing the wheel.
• ASK QUESTIONS! Use the forums and blogs to ask questions about the things that you don't understand. I wasted so much time trying to figure things out for myself. Asking questions almost always gave me the answer I was looking for. Uh, just ask questions...

Within the next few weeks, I'll talk about some of the obstacles that I faced during development along with some more advice. You'll soon be able to download IT Helper 1.0 and try it out for yourself. I wanted to have it available by today, but I still have to work out some minor details before releasing it publicly. Thanks for reading and remember to check for updates regularly.

Google Wave, the search giant's incredibly ambitious new Email/IM hybrid that was announced in May, is quickly picking up steam. As of last week the service was open to around 6,000 developers (most of whom had attended conferences like I/O), and Google is planning to send out an additional 20,000 invites over the next month. It looks like a big batch of them just went out, as we've received a number of tips about new invitations, and Twitter is currently abuzz with excited developers thrilled to finally get in on the action.

One other piece of news that will be very interesting to non-developers eagerly waiting to try out the service: Google is planning to release Wave to 100,000 users beginning on September 30th, using the service's main wave.google.com hub rather than the developer site (we can likely expect a Gmail-like limited invitation system). By this time we can likely expect there to be a rich variety of Wave widgets the site already boasts plenty of them, including a RickRoll widget and more practical things like a weather forecast but you can't try them out without a Developer Sandbox account.

Thanks to Noah Hendrix for the tip.

Crunch Network: MobileCrunch Mobile Gadgets and Applications, Delivered Daily.

Reader recently launched liking (and a bunch of other features). One of the nice things about liking is that it's completely public*. It would therefore make sense to be pretty liberal with liking data, and in fact Reader does try to expose liking in our feeds. If you look at my shared items feed you will see a bunch of entries like:

<gr:likingUser>00298835408679692061</gr:likingUser>
<gr:likingUser>11558879684172144796</gr:likingUser>
<gr:likingUser>07538649935038400809</gr:likingUser>
<gr:likingUser>09776139491686191852</gr:likingUser>
<gr:likingUser>02408713980432217881</gr:likingUser>
<gr:likingUser>05429296530037195610</gr:likingUser>

These are the users that have liked. Users are represented by their IDs, which you can use to generate Reader shared page URLs. More interestingly, you can plug these into the Social Graph API to see who these users are.

Liking information isn't just limited to Reader shared item feeds. If you use Reader's view of a feed, for example The Big Picture's, you can see the <gr:likingUser> elements there too. This means that as a publisher you can extract this information and see which of your items Reader users find interesting.

For now liking information that is included inline in the feed is limited to 100 users, mainly for performance reasons. That number may go up (or down) as we see how this feature is used.

* I've seen some wondering what the difference between liking, sharing and starring is. To some degree that's up to each user, but one nice thing about liking is that it has less baggage associated with it. We learned that if we try to redefine existing behaviors (like sharing) users get upset.

Kevin Maney eulogizes: Motorola, once one of the great American companies, appears to be in a death cycle. Its stock is at a five-year low, its market share is sinking like a phone thrown overboard, and its product line seems to be behind the times. Analysts are dropping support for Motorola, the company's debt ratings are going through the floor, and it can't recruit top talent.

It all adds up to a sad scenario that seems destined to end with Motorola going the way of one-time icons like RCA, Westinghouse, and U.S. Steel. If Carl Icahn thought booting Ed Zander from the CEO job was going to fix anything, he was clearly mistaken.

On Glassdoor.com, the input from Motorola employees is brutal. Some samples:

From a senior project coordinator -- "There are probably too many downsides to express in this reveiw. There is high stress level due to the fact that no one knows from day to day if they will have a job even if they are a top performing employee."

From a software engineer: "Motorola is huge into cost cutting right now. It seems that cost cutting is our actual product. It makes me wonder that if we are so bent on cutting costs then are we going to say no to the right projects that will help make money in the end?"

From a senior quality engineer: "Please force out these dinosaur managers who have no grasp of technology! According to reports, our current CEO does not even use email. The previous CEO, Ed Zander, let the company become a laughingstock with its RAZR phones."

From an anonymous employee: "Tough times for the company have lead to a stressful work environment with employees and resources stretched very thin. Lost the creative edge from years past. Poor middle management in general. Very few managers are truly decisive leaders - they are unwilling to take any chances and risks and prefer to follow the herd."

CEO Greg Brown has one of the lowest internal approval ratings of any CEO reviewed on Glassdoor, at 19%. Employee satisfaction runs at a low 2.7 on a scale of 1 to 5. Unless something radical happens, Motorola's days of being a great company are done.