Live data from Hacker News

Without Warning, Twitter Kills StatTweets

statsheet.com

11–20 of 39 posts

Re: Without Warning, Twitter Kills StatTweets

#11
post #2

As a side note this is reason I've always believed building an business/app of any importance on-top of another site is just crazy. You're at their mercy and there's nothing you can ever do to stop them shutting you out.

At the same time, that site might be creating business opportunities that wouldn't otherwise exist.

And almost any business will be dependant, to some extent, on others. It's a question of how many of your dependencies are irreplaceable, and how likely they are to shut you out.

See for example http://en.gentoo-wiki.com/outage-10-08.html - they went down and lost all their data because the hosting company had a fight with the people who owned the building where the servers were kept. (Including backups, which made the host irreplaceable - with offsite backups, that wouldn't have been the case.)

Building on a site like twitter might increase the risk of being cut off on a whim, but it probably decreases the risk of competitors.

Re: Without Warning, Twitter Kills StatTweets

#12
Twitter is very open with how they like and don't like their system to be used. They are the most open company I can think of with their API. I can guarantee this wouldn't come as a surprise to the service maker. This is coming from someone who makes an application that heavily uses twitter.

Re: Without Warning, Twitter Kills StatTweets

#15
post #9

Earlier quoted context omitted.

Because an account is some precious commodity?

If it weren't, would we be having this discussion? Seems that you want it both ways, depending on whether you're discussing Twitter's obligations to you or your obligations to Twitter.

Account is a precious commodity, account name generally not, unless the intent is to squat.

Re: Without Warning, Twitter Kills StatTweets

#19
post #10
post #2

As a side note this is reason I've always believed building an business/app of any importance on-top of another site is just crazy. You're at their mercy and there's nothing you can ever do to stop them shutting you out.

Every business is built on other businesses. In the 1800s if you wanted distribution you had to play ball with the railroad barons. This is just the 21st century equivalent. Likewise, if you're building a destination website you're dependent on Google, email spam lists (don't get blacklisted!), browser vendors (MSFT and ESPN once conspired to make espn.com for IE-only), and even ISPs (see: Net Neutrality). The risks…

There is a difference between those early dependence and Twitter. Twitter is still young, it's uncertain, and worst it's future is really unpredictable because it doesn't even have a business model to generate revenue yet.

Building on top of a business is sensible when you are depending on something that's been there for a while, know it's dependable and have a reputation. This twitter does not have.

If the same service as Twitter was provided by Google, Amazon or even Microsoft, you know it's backed by something solid.

Re: Without Warning, Twitter Kills StatTweets

#20
post #2

As a side note this is reason I've always believed building an business/app of any importance on-top of another site is just crazy. You're at their mercy and there's nothing you can ever do to stop them shutting you out.

I agree. That's what sucks about our dependency on Google too. Most Internet businesses are dependent on them and they can decide to remove you from the index as quickly as Twitter disabled the StatTweet accounts. Twitter effectively removed me from their index.

There is a difference between depending on Google and depending on Twitter.

Google is a multi faceted business, they have a good revenue model, have money, and are a proven company. Depending on them isn't crazy.

What's crazy is depending on Twitter, it's new, still have no solid revenue model to make money and sustain, in simple it's a single egg in the basket.

Post reply on HN