<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>CostPerNews - Latest Comments in TwitPwr vs Bit.ly: No Contest</title><link>http://costpernews.disqus.com/</link><description>The Leading Performance Marketing Blog!</description><atom:link href="https://costpernews.disqus.com/twitpwr_vs_bitly_no_contest/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 05 Jul 2009 17:31:15 -0000</lastBuildDate><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-12179453</link><description>&lt;p&gt;Great! a new design! I'm looking for the improvement of this beta. just make a good move. I'm looking forward for your next post, so keep on posting!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">boston moving help</dc:creator><pubDate>Sun, 05 Jul 2009 17:31:15 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-8714617</link><description>&lt;p&gt;The frames are used to drive more traffic and followers to the person who tweeted the link.&lt;/p&gt;&lt;p&gt;The top bar links to the profile of the person, and we have a referral link which gives them more "twitpwr juice" when those they refer sign up for the service.  The more twitpwr ranking you have, the more users see your profile and follow you on Twitter.&lt;/p&gt;&lt;p&gt;So users get more followers and exposure for all the links they create in the system.. And every URL gets its own profile page which generates passive traffic as well as helps build organic rankings.&lt;/p&gt;&lt;p&gt;The frame is key to helping every user/site owner get more traffic.&lt;/p&gt;&lt;p&gt;In response to amerkwr's comment.   Every link that gets submitted gets its own profile page so you're getting backlinks throughout our site every time a link is submitted.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dan</dc:creator><pubDate>Sun, 26 Apr 2009 20:17:33 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-8179234</link><description>&lt;p&gt;Both are cool. I like &lt;a href="http://Ow.ly" rel="nofollow noopener" target="_blank" title="Ow.ly"&gt;Ow.ly&lt;/a&gt; personally because &lt;a href="http://Ow.ly" rel="nofollow noopener" target="_blank" title="Ow.ly"&gt;Ow.ly&lt;/a&gt; integrates smoothly with Hootsuite. I think Twitter Power reaches out to the more obsessive tweeter than other twitter platforms. Kudos to Joel for such an interesting product!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tarik Pierce</dc:creator><pubDate>Tue, 14 Apr 2009 05:00:43 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-7904925</link><description>&lt;p&gt;Good post. Another deal-breaker for me is the redirection. &lt;a href="http://Bit.ly" rel="nofollow noopener" target="_blank" title="Bit.ly"&gt;Bit.ly&lt;/a&gt; uses 301 Permenant redirects, while TwitPwr doesn't use any redirects, just framing.&lt;/p&gt;&lt;p&gt;This means that when I use &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;, Google indexes my pages and gives backlink credit to my original site, while when using TwitPwr, TwitPwr gets all the credit.&lt;/p&gt;&lt;p&gt;I looked around, and this article speaks about 301/302 redirections and SEO:&lt;br&gt;&lt;a href="http://news.stepforth.com/blog/2008/01/redirects-permanent-301-vs-temporary.php" rel="nofollow noopener" target="_blank" title="http://news.stepforth.com/blog/2008/01/redirects-permanent-301-vs-temporary.php"&gt;http://news.stepforth.com/b...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Another point for &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Amer K</dc:creator><pubDate>Mon, 06 Apr 2009 10:51:27 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-7743769</link><description>&lt;p&gt;sweet, i heart frames, can we get some blink back too?&lt;/p&gt;&lt;p&gt;Really though, frames? Isnt it 2009? Wasn't it pretty well determined that frames are antithetical to the purpose of the WWW about 10 years ago or so?&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">halfacat</dc:creator><pubDate>Thu, 02 Apr 2009 11:08:52 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-6850197</link><description>&lt;p&gt;twitpwr gets you indexed pages that interlinked with keyword links to your profile and the site you are linking to...it also builds a ton of associated content to make those links more valuable. You need to take a look at the entire system before you make a judgement...or get someone to look at it that is qualified from an SEO and traffic standpoint to understand what is happening behind the scenes. Twitpwr drives traffic and followers...nothing else does.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jason</dc:creator><pubDate>Tue, 03 Mar 2009 17:42:57 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-6070360</link><description>&lt;p&gt;TwitPWR added an "X" to fix that issue.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Spider Dog</dc:creator><pubDate>Sat, 07 Feb 2009 13:39:15 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-4483456</link><description>&lt;p&gt;Haven't had a chance to listen to Geekcast yet - looking forward to it today on the drive up to Santa Fe.&lt;/p&gt;&lt;p&gt;One of my pet peeves is when people throw out a half baked product, call it a "beta" and expect people to do their testing for them. That's not what a beta version is supposed to be. Betas are supposed to be handled in-house. Products are supposed to be finished before releasing them to the public. Alpha &amp;gt; Beta &amp;gt; Gold, and if your users find problems, you issue patches or updates. If your product relies on real-world testing, that's fine - but explain that instead of just slapping a 'beta' label on it and using that label as an excuse for the product's shortcomings.&lt;/p&gt;&lt;p&gt;20% of the functionality is on the site? That's not even half-baked, that's fifth-baked - and the functionality that is being talked about for future implementation is basic stuff that should have been in before the service went public. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DMC</dc:creator><pubDate>Thu, 18 Dec 2008 12:01:31 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-4482824</link><description>&lt;p&gt;That's basically what I said on GeekCast yesterday, Daniel:&lt;/p&gt;&lt;p&gt;&lt;a href="http://bit.ly/lhge" rel="nofollow noopener" target="_blank" title="http://bit.ly/lhge"&gt;http://bit.ly/lhge&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I participate in a ton of beta and alpha testings since I'm a chronic early adapter and understand the basics of many coding languages.&lt;/p&gt;&lt;p&gt;This sort of dismissive response towards people kicking the tires of the service is not only trite, but makes me definitely not want to use the service in the future when it "comes out of beta."&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sam Harrelson</dc:creator><pubDate>Thu, 18 Dec 2008 11:27:51 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-4476191</link><description>&lt;p&gt;This comes across as "it's beta, so don't complain or point out any shortcomings" to me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DMC</dc:creator><pubDate>Thu, 18 Dec 2008 01:37:06 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-4462595</link><description>&lt;p&gt;Sounds good, I'll be looking for the improvements.  Consider this part of my beta testing :)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sam Harrelson</dc:creator><pubDate>Wed, 17 Dec 2008 13:16:57 -0000</pubDate></item><item><title>Re: TwitPwr vs Bit.ly: No Contest</title><link>http://www.costpernews.com/archives/twitpwr-vs-bitly-no-contest/#comment-4462504</link><description>&lt;p&gt;TwitPwr is in Beta.  More features, new design and a top frame close button are being rolled out very shortly.  The top frame close button will be live today as will user profile pages with the user's created links.&lt;/p&gt;&lt;p&gt;You are currently seeing about 20% of TwitPwr functionality on the site.&lt;/p&gt;&lt;p&gt;We haven't disclosed a lot of the features yet, because of competition in the market place.&lt;/p&gt;&lt;p&gt;Didn't Jim Kukral mention that we were in beta on your Geekcast? &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DanNickerson</dc:creator><pubDate>Wed, 17 Dec 2008 13:13:57 -0000</pubDate></item></channel></rss>