Backtype isnt cutting it.

[David]

I have been using the custom shortner for a while now, and I am pretty
frustrated with the integration on my own site. Tweetmeme doesn't
fully support awe.sm and most of the time URLs don't shorten using my
URL. Your solution was to use backtype.

Well Backtype sucks-
-its interface with Twitter isn't as good and it just doesn't bring
the traffic or shares that tweetmeme does
-It doesn't report all retweets, where tweetmeme seems to

I see the benefits of the custom shortner URL for each share, but
honestly it would be much more valuable to work with the tweetmeme
ecosystem consistently. I would gladly trade the first feature for
the second.


Are you guys stopping work on awe.sm? I believe in this product, it
is a wonderful, richer product than bitly.pro and I hope you aren't.
The lack of updates and the poor reliability has me believing
otherwise though...

[Michael Montano]

Hi David,

Can you email me at m...@backtype.com - we index every tweet so it should be simple to get to the bottom of your problem w/ some more details.

Thanks,
Mike

--
You received this message because you are subscribed to the Google Groups "awesm-api" group.
To post to this group, send email to awes...@googlegroups.com.
To unsubscribe from this group, send email to awesm-api+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/awesm-api?hl=en.



Sent via BlackBerry from T-Mobile

[Jonathan Strauss]

Thanks Mike for chiming in on the BackType-specific issue. FWIW, I generally find BackType to be pretty comprehensive in my usage.

And David, thanks for your feedback. Our goal with tools integrations is to provide the broadest set of options for all the use-cases that matter to our customers. However, this does require integration work on their part which is beyond our control. In the case of Tweetmeme, we have had ongoing discussions with them about proper awe.sm integration but respect the fact that they have had other priorities thus far.

For what it's worth, I personally prefer the BackType Tweetcount button for my sites as it doesn't require the visitor to OAuth before tweeting. But our goal is to deliver you the ability to work with whatever tool you choose, and so we will continue to pursue proper Tweetmeme integration along with the other new tools options we hope to bring you soon.

And we are still here working harder on awe.sm than ever (despite outwards appearances). We're a small team (there's only 3 of us full-time right now, though you can help us find a 4th: http://awe.sm/56APM), and we made a decision several months back to build an entirely new system from the ground-up. The good news is that this system will be more reliable and performant, have better APIs, and have a brand new GUI that will deliver you the full value of our unique link per share approach. The bad news is that delivering this new system has required us to forgo all but the most crucial work on the legacy system.

We had hoped to have already unveiled the new system to existing users like you, but it is taking longer than planned. However, you should start to see improvements in days not weeks. We really appreciate your patience, and hope you'll find it was worth the wait once you have had a chance to use the result.

Best,
-jonathan

--
Jonathan Strauss, Co-Founder
http://snowballfactory.com

We're hiring a back-end engineer! http://awe.sm/56APM

Campaign tracking for social media - http://awe.sm
A smarter way to update Facebook from Twitter - http://tweetpo.st
Sharecount button for Facebook - http://www.fbshare.me