31–40 of 188 posts
This is really idiotic. What are they trying to do? Make sure that all the top users flock to App.net or somewhere else?
Considering that I don't know a single real-life person that is on app.net, I wouldn't consider it an alternative to anything.
*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
While that may be true, Twitter has a lot of its popularity and mechanics to thank for from the third party apps.
Think of hashtags and slashtags: http://gigaom.com/2010/04/30/the-short-and-illustrious-histo...
Even the verb 'to tweet' and the bird imagery allegedly came from outside of Twitter.
If it weren't for Loren Brichter's app Tweetie, I probably wouldn't have even bothered with using Twitter.
This is really idiotic. What are they trying to do? Make sure that all the top users flock to App.net or somewhere else?
No, they're making sure users flock to twitter.com instead. And it's been effective, since I use the web interface instead of Tweetbot now!
If my salary depended on the Twitter API right now I'd be scared shitless.
Unless you work for Twitter, I'd say you're right, and rightly so. Don't depend on someone else's API, how many times must history repeat itself before this message sinks in.
A better strategy is to trust somebody (/an API) until they give you good reasons not to. Admittedly, twitter seems to have broken that trust. I personally would't use them as a platform, unless the benefits clearly outweigh the risks of them haphazardly cutting me off.
Earlier quoted context omitted.
I've had a bot blocked by Myspace when I resorted to that. They started redirecting all my requests to " http://google.com ". And I was just working on an old Thinkpad running Ubuntu server in my dorm room, so I have to think blocking me was an automated response. I'm sure Twitter knows how to block crawlers, especially ones that they're actually aware of.
I'm sure Twitter would block bots doing unuserlike things. But isn't the point of a Twitter client to do userlike things?
Although, it still kills the advertising cash cow.
It's so sad to watch such a lively lovely service remove the fun by destroying the values that made it great. Meanwhile we are sitting here saying "charge us money, you fools", and they are deaf to us. Twitter: your online site is usability hell, your own clients are dated and painful. Above all we have one question: why? Why are you intent on this path of foolishness based on placing customers and developers last?
But I suppose they'd just wind up getting sued.
*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
> "If you wrote a client that exposed twitter to new markets or something that added value to Twitter" That's exactly what happened here. Twitter does not currently have a native Win8 client, and a native client has always been a value-add for Twitter's users - many people prefer to have an always-on Twitter widget on their machine that pushes messages to them, over a browser window they have to poll. I haven't used…
Very good summary by Marco. It's really annoying when these companies have secret policies that have to be discovered rather than are clearly stated. It just wastes people's time to try to discover the policy, having to do costly time consuming experiments to find out what the policy is as if this was an unknown branch of particle physics.