"Secret" API calls? C'mon, if Tweetie for iPhone does have this capability, someone's going to reverse it out of there soon enough. Someone who cares enough to do it, anyway.
Not offering a public API isn't exactly an "unfair advantage" - it merely raises the bar. Now, if Twitter punishes app developers for using the same techniques that Tweetie or other official Twitter apps use ... then it's a different story. On 5/19/10 10:44 AM, Dewald Pretorius wrote: > I have not yet seen the new Twitter iPhone client, but if this is true > then it's exactly what we developers feared would happen, namely > Twitter competing with developers and using secret API calls to offer > features that external developers cannot offer. It's really not a good > move, folks, because once you open that barn door, the horses just > keep bolting, and you undermine an already shaky trust in the > intentions of Twitter towards developers. I know this was not decided > or done by Ryan's group, but someone in your group should do some > serious advocacy here, because you're the ones who want us to trust > you and continue to work with you in a non-combative environment. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)