Stuart.. thanks a lot.. got it. specially that twitpic example.. :)
On Apr 28, 7:15 pm, Stuart <stut...@gmail.com> wrote: > I think you're not understanding that there's a definite line between > Twitter itself and the applications we build that use the API. No > application you build is ever like to "become part of Twitter". > > If your application needs to store any data you need to provide that > as part of your application - this is what TwitPic does so why should > you be any different? > > While I don't work for Twitter [yet ;-)] I can pretty much guarantee > that they won't ever endorse your application in the way you seem to > think they will. > > As for what you should do now I suggest you read the API docs very > carefully, understand exactly where the line is between Twitter and > your application, then start designing/coding it. You don't need to > talk to Twitter before using the API to build an application. Once > it's built I'm sure Doug and they guys will be happy to take a look > and make suggestions but that's likely to be as far as their > involvement ever gets. > > Hope that clears things up for you. > > -Stuart > > --http://stut.net/projects/twitter > > 2009/4/28 guru <badshaah.k...@gmail.com>: > > > > > Thanks Andrew for the link.. I am going to check it for my > > requirement.. > > > @Matt.. > > > Thats true. Here is an example which explains everything about my need > > and the application.. > > > Not My Type Application : > > Suppose there is an application called TwittShareUpdates which > > provides daily share updates for some company. Individual user will > > download/Add it for there use using Twitter credentials. One user's > > application information will not be shared by other user, obvious in > > this case. There is no need to store data also in this case. > > > My Type Application (Just an example) > > Suppose there is an application called TwittAlbum in which you store > > photos and that will be viewed and commented by other users. You can > > also view other users photo and can put comment on it. > > > Now you see, TwittAlbum is different from TwittShareUpdates as > > TwittAlbum will take space and this application should be considered > > an independent application. In fact it should be part of Twitter. > > Whereas TwittShareUpdates should be considered as independent > > application provided by third party. > > > TwittAlbum will need some space and every Twitter user will know about > > this feature "Album feature provided by Twitter" (suppose this feature > > is not present right now). TwittShareUpdate will be added/downloaded > > individually by only those users who need it personally whereas > > TwittAlbum will be considered as integral part of Twitter. Whether you > > use it or not, it will remain there as a feature provided by Twitter > > for its users. > > > So.. my application is like TwittAlbum. I want to develop it for > > mobile as well as for desktop also using Java. I had gone through that > > API link earlier also and still checking it. Thanks again for it. > > > So.. any more suggestions? what to do now? regarding space and what > > are the processes to take initiative for send details to twitter > > management team regarding this so that they can evaluate it? > > > sorry for long message but thought lets explain it in better way so > > that nobody will keep guessing.. > > > Thanks again in advance.. > > > Guru. > > > On Apr 28, 1:10 am, Matt Sanford <m...@twitter.com> wrote: > >> Hi there, > > >> From your description it sounds like you do need some storage of > >> your own to keep information like this. > > >> Thanks; > >> – Matt Sanford / @mzsanford > >> Twitter Dev > > >> On Apr 27, 2009, at 12:49 PM, guru wrote: > > >> > @Matt.. what if my mobile application need to store some data provided > >> > by user for other users.. where this will be stored?? and also.. this > >> > application will not be used by only one user.. this is a feature > >> > which will be shared amongst users.. this is for twitter itself and > >> > will be used by all users.. both format will be available.. mobile as > >> > well as desktop.. its a software (till now only concept) which will be > >> > developed by me, maintained by me.. but will be used by twitter people > >> > as an integrated software of twitter.. > > >> > can u suggest me something?? its really a good idea.. do i need to > >> > create my own webspace?? > > >> > On Apr 27, 8:16 pm, guru <badshaah.k...@gmail.com> wrote: > >> >> please read "twitter" at the place of "tutor" .. extremely sorry for > >> >> this.. > > >> >> On Apr 27, 7:13 pm, guru <badshaah.k...@gmail.com> wrote: > > >> >>> Hi All, > > >> >>> I want to develop a new mobile application for twitter. But I have > >> >>> few > >> >>> questions. Please help me as I am new for twitter and this forum. > > >> >>> 1. If tutor users will use my mobile application, then some space is > >> >>> required to store data of my application. does twitter provide space > >> >>> to us to store data related for the user which will be generated > >> >>> by my > >> >>> application? > >> >>> if provides, then which type of space? any database facility? > > >> >>> 2. To whom I will contact after developing this mobile application? > > >> >>> 3. As this is a mobile application, so can u please suggest me that > >> >>> what tools I should use? > > >> >>> thanks in advance.. please reply as soon as possible.- Hide quoted > >> >>> text - > > >> >> - Show quoted text -
