[twitter-dev] Re: Access level changed to Read, Write AND Direct Message but still can't access DMs!

[twittme_mobi]

The same problem here - i am not sure if the api guys are aware of the
consequences every change they make...

On Jul 12, 1:33 am, Mr Blog  wrote:
> I have the same problem.
>
> On the App settings it is set to:
>
> "Read, Write and Accessdirectmessages"
>
> But when users authenticate with OAuth, it's telling users:
>
> This application will not be able to:
> Access yourdirectmessages.
>
> How do we fix this?
>
> On Jul 4, 5:38 pm, "alexre...@gmail.com"  wrote:
>
>
>
>
>
>
>
> > Most of my apps require read access forDirectMessages, but they're
> > only reading from one account.  Many users DM to one account and I
> > need access to that one account to grab all the DMs (which no longer
> > works as of June 30th).
>
> > I changed the Access Level of all my apps to Read, Write andDirect
> > Message, but it doesn't seem that the change has taken place, or I'm
> > missing something, somewhere in terms of what I need to do?
>
> > When I try and re-authorize an account I see the following on the
> > Twitter / Authorize screen:
>
> > This application will not be able to:
> > Access yourdirectmessages.
> > See your Twitter password.
>
> > What else do I need to do?  I have confirmed that the application
> > settings on Twitter do say, Read, Write andDirectMessagesfor my app
> > but I can only use "my access token" (for the Twitter handle
> > associated with the app) to accessdirectmessages, anytime I try and
> > re-authorize any account through my actual app, I see:
>
> > This application will not be able to:
> > Access yourdirectmessages.
> > See your Twitter password.
>
> > ... which isn't inline with how I setup the settings.  Any help would
> > be greatly appreciated.  I'm really hoping I'm missing something small
> > here.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: friendship/incoming , then what?

[twittme_mobi]

wow!

strange why would i display those then?!
twitter is popular because the api is open and not because of API
restrictionthat's why twitter has
some advantages over facebookrestricting is not the best choice i
think...

On Jun 10, 11:01 am, Rich  wrote:
> According to the API guys, send them to Twitter.com.  For some reason
> they don't want us to have an API that allows us to accept or reject
> friend requests
>
> On Jun 10, 10:02 am, twittme_mobi  wrote:> Hello,
>
> > it seems like i can get a list of everyone that want's to follow me
> > using
> > friendship/incoming
>
> > Then how can I actually allow them to follow me...e.g. to accept that
> > request?
>
> > thanks.

[twitter-dev] friendship/incoming , then what?

[twittme_mobi]

Hello,

it seems like i can get a list of everyone that want's to follow me
using
friendship/incoming

Then how can I actually allow them to follow me...e.g. to accept that
request?

thanks.

[twitter-dev] Re: Mobile OAuth Summary

[twittme_mobi]

Hi All,

I still think that it is reasonable to think about this.
Is there anyone from twitter doing something about it?

Thanks.

On May 4, 9:25 am, twittme_mobi  wrote:
> Hello Raffi,
>
> Could you please, get back to us on this?
> Do you have any plans on resolving that issue?
> Is there any show stopper?
> What are we doing with this?!
>
> Thanks.
>
> On Apr 29, 12:07 pm, Raffi Krikorian  wrote:
>
> > hi.
>
> > i'll follow up on this - do you have a notion of what browsers, what phones,
> > etc. your users are coming from
>
> > On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi 
> > wrote:
>
> > > Hello,
>
> > > I migrated mymobileweb site toOAuth.
> > > Now, I have a lot of users complaining that theOAuthpage of twitter
> > > is not
> > >mobilefriendly.Some of them are getting just a blank screen or just
> > > cannot open it.
>
> > > My honest question is - this is being discussed many times but where
> > > are we with this?
> > > Are all those users really suppose to get such a bad user experience?
> > > Why would you need a javascript
> > > on a login page?Is it so hard to create such page just formobile
> > > browsers?
>
> > > Is anybody handling this - I mean it is an obvious problem that we
> > > have for more than a year already.
>
> > > Any comments on this are highly appreciated.
>
> > --
> > Raffi Krikorian
> > Twitter Platform Teamhttp://twitter.com/raffi

[twitter-dev] Re: Mobile OAuth Summary

[twittme_mobi]

Hello Raffi,

Could you please, get back to us on this?
Do you have any plans on resolving that issue?
Is there any show stopper?
What are we doing with this?!

Thanks.


On Apr 29, 12:07 pm, Raffi Krikorian  wrote:
> hi.
>
> i'll follow up on this - do you have a notion of what browsers, what phones,
> etc. your users are coming from
>
> On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi wrote:
>
>
>
> > Hello,
>
> > I migrated my mobile web site to OAuth.
> > Now, I have a lot of users complaining that the OAuth page of twitter
> > is not
> > mobile friendly.Some of them are getting just a blank screen or just
> > cannot open it.
>
> > My honest question is - this is being discussed many times but where
> > are we with this?
> > Are all those users really suppose to get such a bad user experience?
> > Why would you need a javascript
> > on a login page?Is it so hard to create such page just for mobile
> > browsers?
>
> > Is anybody handling this - I mean it is an obvious problem that we
> > have for more than a year already.
>
> > Any comments on this are highly appreciated.
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

[twitter-dev] Re: Mobile OAuth Summary

[twittme_mobi]

Hello,

I would agree with bob.hitching - let's take a general approach.
It is obvous that the OAuth twitter login page is not mobile optimized
so, rather than going and asking everyone
what phone you have and then trying to fix it for that phone - why
don't you just follow the best practice for mobile xhtml - basicaly
that would mean no javascript, no html tables...using just simple set
of the well known html - div,form elements,br :) it is really
easy and i do not see why you guys are taking no action - there is
already a lot of users using this just because they would not like to
install an app
on their phone.

Please consider this seriosly and we are all here to help!



On Apr 29, 12:07 pm, Raffi Krikorian  wrote:
> hi.
>
> i'll follow up on this - do you have a notion of what browsers, what phones,
> etc. your users are coming from
>
> On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi wrote:
>
>
>
>
>
> > Hello,
>
> > I migrated my mobile web site to OAuth.
> > Now, I have a lot of users complaining that the OAuth page of twitter
> > is not
> > mobile friendly.Some of them are getting just a blank screen or just
> > cannot open it.
>
> > My honest question is - this is being discussed many times but where
> > are we with this?
> > Are all those users really suppose to get such a bad user experience?
> > Why would you need a javascript
> > on a login page?Is it so hard to create such page just for mobile
> > browsers?
>
> > Is anybody handling this - I mean it is an obvious problem that we
> > have for more than a year already.
>
> > Any comments on this are highly appreciated.
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

[twitter-dev] Mobile OAuth Summary

[twittme_mobi]

Hello,

I migrated my mobile web site to OAuth.
Now, I have a lot of users complaining that the OAuth page of twitter
is not
mobile friendly.Some of them are getting just a blank screen or just
cannot open it.

My honest question is - this is being discussed many times but where
are we with this?
Are all those users really suppose to get such a bad user experience?
Why would you need a javascript
on a login page?Is it so hard to create such page just for mobile
browsers?

Is anybody handling this - I mean it is an obvious problem that we
have for more than a year already.

Any comments on this are highly appreciated.

[twitter-dev] OAuth create favorite fails

[twittme_mobi]

Hello,

I am moving my twitter app to OAUTH.
I am fine with most of the URLs/use case but I have problem with
favorites/create and favorites/destroy/

For example, If I login with OAuth , i could view the friends timelen,
check for
existing block and follows between users but when I try to create a
favorite, I would get
as a response:

{"request":"/1/favorites/create/9623635886.json","error":"Incorrect
signature"}Array ( [request] => /1/favorites/create/9623635886.json
[error] => Incorrect signature )  OAUTH

Any help is highly appreciated.

thanks.

[twitter-dev] Re: cannot edit registered application

[twittme_mobi]

Thanks Brian,

I wrote an e-mail and I will keep you all informed about the
development.
Note that, I have another account - johny_edu , with existing
application ,
and I cannot edit an existing application with it.

Thanks.

On Jan 20, 10:55 pm, Brian Sutorius  wrote:
> This may be an issue with your account. Please write to
> a...@twitter.com from the email address associated with your Twitter
> account and we can look into it.
>
> Thanks,
> Brian
>
> On Jan 20, 10:25 am, twittme_mobi  wrote:
>
> > Hello Abraham,
>
> > Thanks for your reply.I tried  that and it is not working,
> > but there another problem even more annoying - I tried to create new
> > application and
> > I am getting Unable to register this application. Check your
> > registration settings.
> > It does not say if the captcha is wrong or if by chance the callback
> > url is not valid ori do not know...
> > It just pull out this message out of nowhere without obvious reason.
>
> > I am a bit worried about this since I am trying to migrate my mobile
> > twitter site to OAuth , but I cannot event start doing it.
>
> > Any help is appreciated.
>
> > On Jan 20, 2:11 am, Abraham Williams <4bra...@gmail.com> wrote:
>
> > > I've been getting some fail whales while viewing my application pages but
> > > not when editing them.
>
> > > Tryhttp://twitter.com/oauth_clients/edit/27insteadofhttp://twitter.com/o...
>
> > > Abraham
>
> > > On Tue, Jan 19, 2010 at 09:32, twittme_mobi  
> > > wrote:
> > > > Hello,
>
> > > > every time i try to edit my application settings , i would get Unable
> > > > to register this application. Check your registration settings.
>
> > > > Isn't it supposed to point me to the exact value that might be
> > > > wrong.If i new what is it i wouldn't put wrong value in the first
> > > > place.
>
> > > > Is this page working at all.I really think that this basic auth
> > > > deprecation in june is a very bad idea
>
> > > --
> > > Abraham Williams | Moved to Seattle | May cause email delays
> > > Project | Intersect |http://intersect.labs.poseurtech.com
> > > Hacker |http://abrah.am|http://twitter.com/abraham
> > > This email is: [ ] shareable [x] ask first [ ] private.
> > > Sent from Seattle, WA, United States

[twitter-dev] Re: cannot edit registered application

[twittme_mobi]

Hello Abraham,

Thanks for your reply.I tried  that and it is not working,
but there another problem even more annoying - I tried to create new
application and
I am getting Unable to register this application. Check your
registration settings.
It does not say if the captcha is wrong or if by chance the callback
url is not valid ori do not know...
It just pull out this message out of nowhere without obvious reason.

I am a bit worried about this since I am trying to migrate my mobile
twitter site to OAuth , but I cannot event start doing it.

Any help is appreciated.

On Jan 20, 2:11 am, Abraham Williams <4bra...@gmail.com> wrote:
> I've been getting some fail whales while viewing my application pages but
> not when editing them.
>
> Tryhttp://twitter.com/oauth_clients/edit/27instead 
> ofhttp://twitter.com/oauth_clients/details/27
>
> Abraham
>
> On Tue, Jan 19, 2010 at 09:32, twittme_mobi  wrote:
> > Hello,
>
> > every time i try to edit my application settings , i would get Unable
> > to register this application. Check your registration settings.
>
> > Isn't it supposed to point me to the exact value that might be
> > wrong.If i new what is it i wouldn't put wrong value in the first
> > place.
>
> > Is this page working at all.I really think that this basic auth
> > deprecation in june is a very bad idea
>
> --
> Abraham Williams | Moved to Seattle | May cause email delays
> Project | Intersect |http://intersect.labs.poseurtech.com
> Hacker |http://abrah.am|http://twitter.com/abraham
> This email is: [ ] shareable [x] ask first [ ] private.
> Sent from Seattle, WA, United States

[twitter-dev] cannot edit registered application

[twittme_mobi]

Hello,

every time i try to edit my application settings , i would get Unable
to register this application. Check your registration settings.

Isn't it supposed to point me to the exact value that might be
wrong.If i new what is it i wouldn't put wrong value in the first
place.

Is this page working at all.I really think that this basic auth
deprecation in june is a very bad idea

[twitter-dev] Re: Basic Auth Deprecation in June

[twittme_mobi]

Hello,

Thanks for your reply!
Couldn't I just save the access token in a database and use it later?

Thanks.

On Jan 14, 1:31 am, Cameron Kaiser  wrote:
> > Regarding Basic Auth Deprecation is June - would it be possible using
> > OAuth to automate
> > some users posts - for example - there are some applications that can
> > automate a post in the future.
>
> > Could that still work in future?
>
> There is going to be a browserless API, and that might serve such a
> purpose.
>
> --
>  personal:http://www.cameronkaiser.com/--
>   Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com
> -- FORTUNE: You have a magnetic personality. Avoid iron-based alloys. 
> -

[twitter-dev] Basic Auth Deprecation in June

[twittme_mobi]

Hello ,

Regarding Basic Auth Deprecation is June - would it be possible using
OAuth to automate
some users posts - for example - there are some applications that can
automate a post in the future.

Could that still work in future?

Thanks.

[twitter-dev] Re: block exists problem

[twittme_mobi]

Hello,

I tested it with curl and it seems to work fine...probably it is a bug
in my lib...
Thanks!

On Dec 27, 9:40 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Are you still having this issue?
>
> I just tried both:
>
> http://twitter.com/blocks/blocking/ids.jsonhttp://twitter.com/blocks/blocking/ids.xml
>
> and they worked fine.
>
> Abraham
>
> On Thu, Dec 24, 2009 at 14:59, twittme_mobi  wrote:
> > Hello,
>
> > I am trying to execute the following API url:
> >http://twitter.com/blocks/blocking/ids.json
>
> > every time I hit this, I get : "Not Found".
>
> > I also tried with the xml format, I used users who should have blocked
> > ids.
> > Any idea is appreciated.
>
> > Thanks.
>
> --
> Abraham Williams | Awesome Lists |http://awesomeli.st
> Project | Intersect |http://intersect.labs.poseurtech.com
> Hacker |http://abrah.am|http://twitter.com/abraham
> This email is: [ ] shareable [x] ask first [ ] private.
> Sent from Madison, WI, United States

[twitter-dev] block exists problem

[twittme_mobi]

Hello,

I am trying to execute the following API url:
http://twitter.com/blocks/blocking/ids.json

every time I hit this, I get : "Not Found".

I also tried with the xml format, I used users who should have blocked
ids.
Any idea is appreciated.

Thanks.

[twitter-dev] Re: retweets vs mentions

[twittme_mobi]

So basically statuses/retweet results are included in statuses/
mention ?


On Nov 17, 4:21 pm, Josh Roesslein  wrote:
> Mentions are any tweets that contain @yourscreenname in the tweet.
> Retweets are tweets that repeat a previously posted tweet (kind of
> like email forwarding).
>
>
>
> On Tue, Nov 17, 2009 at 7:08 AM, Rich  wrote:
>
> > Mentions are anyone who replies or mentions or retweets you, retweets
> > are exactly that, just retweets?
>
> > On Nov 17, 10:15 am, twittme_mobi  wrote:
> >> Hi all,
>
> >> I wondered if we already could start using the retweet API methods -
> >> for example statuses/retweet.
> >> Currently statuses/mentions also returns retweets , so what is the
> >> difference between thos and how
> >> should they be organized in an application implementing this
> >> functionality/
>
> >> Thanks.- Hide quoted text -
>
> - Show quoted text -

[twitter-dev] retweets vs mentions

[twittme_mobi]

Hi all,

I wondered if we already could start using the retweet API methods -
for example statuses/retweet.
Currently statuses/mentions also returns retweets , so what is the
difference between thos and how
should they be organized in an application implementing this
functionality/

Thanks.

[twitter-dev] waiting for whitelisting

[twittme_mobi]

Hello,

Sorry for posting this again. but I have problems with my mobile
twitter site, which is
in production since 4 months now and alreay widely used.The problem is
that my hosting company changed my outgoing IP without notifying me
and now i reach the time limit and the users are complaining.It is
very annoying so i would kindly ask the twitter guys to have a look.
My new IP is 99.198.100.139 for http://twittme.mobi  and i would like
to have it whitelisted.

Thanks.

[twitter-dev] Re: White listing rejected - no reason

[twittme_mobi]

Hi Chad,

I already submitted whitelisting request since my hosting company
changed my outgoing IP address without
notifying me which is very annoying since i can already see some
errors comming from most active users.
My new IP is 99.198.100.139 . Could you please take a look or should I
send a mail?

Thanks!

On Oct 30, 12:58 am, Chad Etzel  wrote:
> Email your username to a...@twitter.com and we can look up the reason and
> help you figure things out.
> -Chad
>
> On Thu, Oct 29, 2009 at 7:50 PM, Arnaldo de Moraes Pereira <
>
>
>
> eggh...@gmail.com> wrote:
> > Hello,
>
> > I've submitted my application to be on the white list, but this request has
> > been rejected, without a reason.
>
> > For some weeks now, I've been receiving 400 Bad Request http responses
> > frequently and didn't reach the rate limit, not once (
> >http://apiwiki.twitter.com/Rate-limitingsays the app would receive 503 if
> > the rate limit was reached). I just can't fetch fresh updates (just old,
> > delayed ones), can't get directions here to understand why this is happening
> > and now I can't be white listed.
>
> > I'd ask for an answer and a direction here, but since that seems hard to
> > get: may please somebody tell me anything useful about this situation?
>
> > Thanks,
>
> > --
> > Arnaldo M Pereira- Hide quoted text -
>
> - Show quoted text -

[twitter-dev] Re: Twitter icons

[twittme_mobi]

Hi,

Is it ok to use the logo in our apps, someone would say that we
are misleading users that we are actually twitter branches or so...

On Oct 14, 10:12 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Here is Twitters logo:https://twitter.com/about#download_logo
> Abraham
>
> On Wed, Oct 14, 2009 at 11:02, John Meyre  wrote:
>
> > I don't know if I got that information here or somewhere else, but somebody
> > pointed out a location where I could get some Twitter icons.
>
> --
> Abraham Williams | Community Evangelist |http://web608.org
> Hacker 
> |http://abrah.am|http://twitter.com/abrahamhttp://web608.org/geeks/abraham/blogs/2009/10/03/win-google-wave-invite
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States

[twitter-dev] rate limit error on status/show only

[twittme_mobi]

Hi All,

I am hitting the following url:
/statuses/show/4843243649.xml

And i get:
Rate limit exceeded. Clients may not make more than 150 requests per
hour.

Note that before and after that i can hit any other url without
problems with the same user - so i am
logged in my application and everything works fine until i hit this
url, after i get the error i could continue
with other functionality with no problemsstrange huh?

Thanks.

[twitter-dev] Mentions included in replies?

[twittme_mobi]

Hi All,

why do we need mentions included in the result of  statuses/
replies.xml since we have a separate method
for mentions.Now the result is that they appear as replies without
populating the in_reply_to_status_id.

Thanks.

[twitter-dev] Re: Mobile oAuth

[twittme_mobi]

Hi Jim,

any news on that?How close are you to address this?

Thanks.

On Sep 7, 9:54 am, "jim.renkel"  wrote:
> I've opened a feature request for this in the issues database:
>
> http://code.google.com/p/twitter-api/issues/detail?id=1011
>
> If you like this idea and / or think it's a good thing, please
> indicate your support both here and in the issues forum.
>
> If you don't like it and / or don't think it's so hot, I'd like to
> hear that too.
>
> Thank you in advance.
>
> Jim Renkel
>
> On Sep 5, 4:42 am, twittme_mobi  wrote:
>
> > Jim,
>
> > Thanks for the broad summary,
> > I fully agree with you.
> > There should be some mechanism formobiledevices with
> > less resources forOAuth.
>
> > Regarding the source parameter of the Application, it is very
> > important with regards of e-marketing of the application itself.
>
> > Greetings!
>
> > On Sep 5, 2:08 am, "Jim Renkel"  wrote:
>
> > >OAuthis great, in certain circumstances. In others, it's not so great.
>
> > > Circumstances for which it is great include:
> > > -   consumer web sites; and
> > > -   consumer client applications that have access to a reasonable
> > > browser on
> > >     the client device
> > > in both cases with the qualification that the authorization pages of the
> > > service provider are in a language (e.g., English, Japanese, etc.) that
> > > is the same as that used by the consumer.
>
> > > In these circumstances,OAuthas defined by the specifications and
> > > implemented by twitter works very well.
>
> > > Circumstances for which it is not so great include:
> > > -   consumer client applications that do not have access to a reasonable
> > >     browser on the client device; and
> > > -   consumer client applications and web sites that are in languages for
> > >     which service authorization pages in those languages are not
> > > available.
>
> > > In these circumstances,OAuthas defined by the specifications and
> > > implemented by twitter does not work so well.
>
> > > Currently, in circumstances whereOAuthdoes not work very well, twitter
> > > client applications and web-sites can resort to Basic Authentication.
>
> > > The drawbacks to this are obvious:
> > > -   the user must give their twitter password to the client;
> > > -   at some point twitter will no longer support Basic Authentication;
> > > and
> > > -   the source of tweets created by these clients is "API" rather than
> > > the
> > >     client's name.
>
> > > Pooh pooh the last drawback if you will, but to some it is important.
>
> > > Now, the fact of the matter is that some users are perfectly comfortable
> > > in giving their twitter passwords to client applications and web-sites,
> > > even where those clients supportOAuth.
>
> > > I don't think these users should be penalized and forced to useOAuth
> > > if'n and when'n twitter drops support for Basic Authentication.
>
> > > And if'n and when'n twitter drops support for Basic Authentication,
> > > client applications and web-sites that now only support Basic
> > > Authentication will be forced to supportOAuth. Myself, I don't think
> > > that's an unreasonable requirement, but others may differ.
>
> > > And I don't think these creators should have to forgo having their
> > > client's name as the source of tweets their clients create, now or ever,
> > > just because their users chose to trust them to use Basic
> > > Authentication.
>
> > > So I propose the following enhancement to twitter'sOAuth
> > > implementation:
>
> > > Allow a userID and password to be included as optional parameters of an
> > >oauth/access_token request. If supplied and authentic, they would cause
> > > a valid access token to be returned without the user having visited the
> > > authorize URL and approved the access.
>
> > > Alternately, the userID and password could be optional on an
> > >oauth/request_token request, in which case, if supplied and authentic,
> > > the request would return a valid access token, rather than a request
> > > token, again without the user having visited the authorize URL and
> > > approved the access. The advantage to this alternative is it reduces by
> > > one the number of API calls needed.
>
> > > I believe either of these alterna

[twitter-dev] Re: OAuth + Mobile nightmare

[twittme_mobi]

Hi all,

any update on this?it is still not clear when mobile applications
could migrate ot
OAuth and how long we could use basic auth?

Thanks!

On Sep 4, 3:36 pm, twittme_mobi  wrote:
> in addition to storing the access token somewhere , wouldn't it be
> better
> if twitter delivermobilefriendly version of the oauth pages?
>
> On Aug 19, 12:14 am, JDG  wrote:
>
> > That's what you should be doing. There's no reason to get a new Access Token
> > every time. Per the OAuth spec, you should probably code your app to handle
> > an expired token gracefully. The spec states that tokens MAY expire --
> > Twitter currently does not expire theirs, though. However, that doesn't mean
> > that they couldn't in the future.
>
> > 2009/8/18 André Arruda 
>
> > > I'm thinking about storing the access token in the phone so the user won't
> > > have to go
> > > through all the auth process everytime the program is opened.
>
> > > I hope i won't find any new "surprises" by doing this.
>
> > > 2009/8/18 Otávio Ribeiro 
>
> > > no.. just the same problem.
>
> > >> On Mon, Aug 17, 2009 at 3:09 PM, AArruda  wrote:
>
> > >>> I've been developing a Java/MIDP Twitter client for the past two
> > >>> months, and i still need a couple more months to publish a beta
> > >>> version. A few days ago i found out that the update source (app name)
> > >>> is no longer customizable unless the client uses OAuth for
> > >>> authentication, which means that any update sent through my client is
> > >>> shown as "from API" instead of my app's name.
>
> > >>> I understand that OAuth is important for many security reasons, but it
> > >>> still has important issues withmobileapplications, forcing the user
> > >>> to open a page through amobiledevice, writing down the PIN,
> > >>> switching back to the app and logging in again is just hell. Not to
> > >>> mention the smartphones that don't support programs running in the
> > >>> background.
>
> > >>> The current API's methods shouldn't be restricted to OAuth unless
> > >>> these issues are solved first. We, developers andmobileusers, would
> > >>> be thankful.
>
> > >>> Is anyone using any other solution for OAuth andmobiledevices, if
> > >>> there is any?
>
> > --
> > Internets. Serious business.

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

Hi Tomas, you are absolutely right but i am
considering caching in a different task that  i am doing..

Thanks!

On Oct 7, 12:36 pm, Thomas Hübner  wrote:
> If you unfollow or follow or block you get an user xml back from Api -
> is it to difficult to remove or add the returned id manually from ID
> List/Array? We talk about runtime? This saves a lot of expensive Api
> calls (to load the id's on start and manage them within your code
> then)
>
> On 6 Okt., 23:35, twittme_mobi  wrote:
>
> > Hi Tomas,
>
> > I just checked the social graph functions.The point is that if i make
> > unfollow
> > and then get all the id's of users that i follow - the user id that i
> > unfollowed would be still there - e.g.
> > this methods are not updated in real time.
>
> > Could you all comment on this?Is that a bug?
>
> > On Oct 6, 11:47 am, twittme_mobi  wrote:
>
> > > Hi Tomas,
>
> > > Thanks for the colaboration!
> > > I do not handle all the users at the same time, i just ment that
> > > storing session data for all currently logged-in users could take some
> > > memory
> > > resources but in general i agree with you...some caching along
> > > with a proper implementation should not harm :)
>
> > > Thanks!
>
> > > On Oct 5, 1:27 pm, Thomas Hübner  wrote:
>
> > > > I only can talk for .NET - A Dictionary(of Long, Boolean) with 5000
> > > > Id's needs around 500 Ticks If I request the Method .ContainsKey. I
> > > > don't think that an API Request with parsing xml can be faster.
> > > > Additional you nail the server with unneeded requests which are
> > > > "expensive" (rate limits) too
>
> > > > I don't know your Applicaton but you'll handle all accounts at the
> > > > same time? Normaly if an user authenticates the first calls could be
> > > > to request the ID Lists and store them during this users sessiontime.
> > > > If a user leaves you can free this memory.
>
> > > > On 5 Okt., 12:03, twittme_mobi  wrote:
>
> > > > > Hi Tomas, another question to collaborate,
> > > > > do you think that is faster to find the ID in array by iterating it
> > > > > rather that searching for a string in the XML
> > > > > with some well known search function
>
> > > > > On Oct 5, 10:54 am, twittme_mobi  wrote:
>
> > > > > > Hi Tomas,
>
> > > > > > Thanks for the clarification.
> > > > > > One question - if you have many users, you will need to load all the
> > > > > > IDs
> > > > > > for All the users in the memory - isn't that too heavy?some of the
> > > > > > users have 10+ followers.
>
> > > > > > Thanks.
>
> > > > > > On Oct 4, 6:26 pm, Thomas Hübner  wrote:
>
> > > > > > > the problem is that a friendship exist is an "expensive" API Call 
> > > > > > > (of
> > > > > > > 150 possible per hr) I do not know what kind of Application you 
> > > > > > > plan but
> > > > > > > for my client App I load the ID's of followers with one API call 
> > > > > > > and
> > > > > > > keep this list in memory. If a status become loaded I compare the
> > > > > > > icluded UserID with the list and switch the menues depending on
> > > > > > > containing this ID or not. This is much faster then request the 
> > > > > > > API each
> > > > > > > time.
>
> > > > > > > Only situation which is not working for are search calls because 
> > > > > > > the
> > > > > > > delivered result (ATOM) does not contain any userID which is a 
> > > > > > > fail
>
> > > > > > > twittme_mobi schrieb:
>
> > > > > > > > Hi Tomas,
>
> > > > > > > > thanks for the reply!
> > > > > > > > the social graph methods are too heavy for such a simple 
> > > > > > > > operation.
> > > > > > > > I have to check if user is followed every time that a profile is
> > > > > > > > visited so
> > > > > > > > i would now where to put "Follow" or "Unfollow" button.It is not
> > > > > > > > reasonable
> > > > > > > > t

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

That's exactly the case, Thanks!

On Oct 6, 11:52 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Check out:http://apiwiki.twitter.com/Twitter-REST-API-Method:-friendships-show
>
> On Sat, Oct 3, 2009 at 04:46, twittme_mobi  wrote:
>
> > Hi guys, i tried friendship/exists but it throws an
> > error when the user is protected.How should i accomplish this task
> > with the API?
>
> --
> Abraham Williams | Community Evangelist |http://web608.org
> Hacker |http://abrah.am|http://twitter.com/abraham
> Project |http://fireeagle.labs.poseurtech.com
> This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

Hi Tomas,

I just checked the social graph functions.The point is that if i make
unfollow
and then get all the id's of users that i follow - the user id that i
unfollowed would be still there - e.g.
this methods are not updated in real time.

Could you all comment on this?Is that a bug?

On Oct 6, 11:47 am, twittme_mobi  wrote:
> Hi Tomas,
>
> Thanks for the colaboration!
> I do not handle all the users at the same time, i just ment that
> storing session data for all currently logged-in users could take some
> memory
> resources but in general i agree with you...some caching along
> with a proper implementation should not harm :)
>
> Thanks!
>
> On Oct 5, 1:27 pm, Thomas Hübner  wrote:
>
> > I only can talk for .NET - A Dictionary(of Long, Boolean) with 5000
> > Id's needs around 500 Ticks If I request the Method .ContainsKey. I
> > don't think that an API Request with parsing xml can be faster.
> > Additional you nail the server with unneeded requests which are
> > "expensive" (rate limits) too
>
> > I don't know your Applicaton but you'll handle all accounts at the
> > same time? Normaly if an user authenticates the first calls could be
> > to request the ID Lists and store them during this users sessiontime.
> > If a user leaves you can free this memory.
>
> > On 5 Okt., 12:03, twittme_mobi  wrote:
>
> > > Hi Tomas, another question to collaborate,
> > > do you think that is faster to find the ID in array by iterating it
> > > rather that searching for a string in the XML
> > > with some well known search function
>
> > > On Oct 5, 10:54 am, twittme_mobi  wrote:
>
> > > > Hi Tomas,
>
> > > > Thanks for the clarification.
> > > > One question - if you have many users, you will need to load all the
> > > > IDs
> > > > for All the users in the memory - isn't that too heavy?some of the
> > > > users have 10+ followers.
>
> > > > Thanks.
>
> > > > On Oct 4, 6:26 pm, Thomas Hübner  wrote:
>
> > > > > the problem is that a friendship exist is an "expensive" API Call (of
> > > > > 150 possible per hr) I do not know what kind of Application you plan 
> > > > > but
> > > > > for my client App I load the ID's of followers with one API call and
> > > > > keep this list in memory. If a status become loaded I compare the
> > > > > icluded UserID with the list and switch the menues depending on
> > > > > containing this ID or not. This is much faster then request the API 
> > > > > each
> > > > > time.
>
> > > > > Only situation which is not working for are search calls because the
> > > > > delivered result (ATOM) does not contain any userID which is a fail
>
> > > > > twittme_mobi schrieb:
>
> > > > > > Hi Tomas,
>
> > > > > > thanks for the reply!
> > > > > > the social graph methods are too heavy for such a simple operation.
> > > > > > I have to check if user is followed every time that a profile is
> > > > > > visited so
> > > > > > i would now where to put "Follow" or "Unfollow" button.It is not
> > > > > > reasonable
> > > > > > to execute the social graph methods every time, because sometimes
> > > > > > users might
> > > > > > have thousands of followers.Isn't it the friendship/exists method 
> > > > > > that
> > > > > > needs to be fixed,
> > > > > > after all, it is just for checking if user is followed or not..
>
> > > > > > Thanks!Your opinion is welcome!
>
> > > > > > On Oct 3, 2:20 pm, Thomas Hübner  wrote:
> > > > > >> you have the social graph methods which deliver ID's. 
> > > > > >> Unfortunately the
> > > > > >> same API call for screennames is missed - so you never can make
> > > > > >> comparings with search API results because there is no userID in.
>
> > > > > >> friends/ids
> > > > > >> followers/ids
>
> > > > > >> cheers,
> > > > > >> Thomas
>
> > > > > >> twittme_mobi schrieb:
>
> > > > > >>> Hi guys, i tried friendship/exists but it throws an
> > > > > >>> error when the user is protected.How should i accomplish this task
> > > > > >>> with the API?
>
> > > > > >>  signature.asc
> > > > > >> < 1KViewDownload
>
> > > > >  signature.asc
> > > > > < 1KViewDownload

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

Hi Tomas,

Thanks for the colaboration!
I do not handle all the users at the same time, i just ment that
storing session data for all currently logged-in users could take some
memory
resources but in general i agree with you...some caching along
with a proper implementation should not harm :)

Thanks!

On Oct 5, 1:27 pm, Thomas Hübner  wrote:
> I only can talk for .NET - A Dictionary(of Long, Boolean) with 5000
> Id's needs around 500 Ticks If I request the Method .ContainsKey. I
> don't think that an API Request with parsing xml can be faster.
> Additional you nail the server with unneeded requests which are
> "expensive" (rate limits) too
>
> I don't know your Applicaton but you'll handle all accounts at the
> same time? Normaly if an user authenticates the first calls could be
> to request the ID Lists and store them during this users sessiontime.
> If a user leaves you can free this memory.
>
> On 5 Okt., 12:03, twittme_mobi  wrote:
>
> > Hi Tomas, another question to collaborate,
> > do you think that is faster to find the ID in array by iterating it
> > rather that searching for a string in the XML
> > with some well known search function
>
> > On Oct 5, 10:54 am, twittme_mobi  wrote:
>
> > > Hi Tomas,
>
> > > Thanks for the clarification.
> > > One question - if you have many users, you will need to load all the
> > > IDs
> > > for All the users in the memory - isn't that too heavy?some of the
> > > users have 10+ followers.
>
> > > Thanks.
>
> > > On Oct 4, 6:26 pm, Thomas Hübner  wrote:
>
> > > > the problem is that a friendship exist is an "expensive" API Call (of
> > > > 150 possible per hr) I do not know what kind of Application you plan but
> > > > for my client App I load the ID's of followers with one API call and
> > > > keep this list in memory. If a status become loaded I compare the
> > > > icluded UserID with the list and switch the menues depending on
> > > > containing this ID or not. This is much faster then request the API each
> > > > time.
>
> > > > Only situation which is not working for are search calls because the
> > > > delivered result (ATOM) does not contain any userID which is a fail
>
> > > > twittme_mobi schrieb:
>
> > > > > Hi Tomas,
>
> > > > > thanks for the reply!
> > > > > the social graph methods are too heavy for such a simple operation.
> > > > > I have to check if user is followed every time that a profile is
> > > > > visited so
> > > > > i would now where to put "Follow" or "Unfollow" button.It is not
> > > > > reasonable
> > > > > to execute the social graph methods every time, because sometimes
> > > > > users might
> > > > > have thousands of followers.Isn't it the friendship/exists method that
> > > > > needs to be fixed,
> > > > > after all, it is just for checking if user is followed or not..
>
> > > > > Thanks!Your opinion is welcome!
>
> > > > > On Oct 3, 2:20 pm, Thomas Hübner  wrote:
> > > > >> you have the social graph methods which deliver ID's. Unfortunately 
> > > > >> the
> > > > >> same API call for screennames is missed - so you never can make
> > > > >> comparings with search API results because there is no userID in.
>
> > > > >> friends/ids
> > > > >> followers/ids
>
> > > > >> cheers,
> > > > >> Thomas
>
> > > > >> twittme_mobi schrieb:
>
> > > > >>> Hi guys, i tried friendship/exists but it throws an
> > > > >>> error when the user is protected.How should i accomplish this task
> > > > >>> with the API?
>
> > > > >>  signature.asc
> > > > >> < 1KViewDownload
>
> > > >  signature.asc
> > > > < 1KViewDownload

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

Hi Tomas, another question to collaborate,
do you think that is faster to find the ID in array by iterating it
rather that searching for a string in the XML
with some well known search function

On Oct 5, 10:54 am, twittme_mobi  wrote:
> Hi Tomas,
>
> Thanks for the clarification.
> One question - if you have many users, you will need to load all the
> IDs
> for All the users in the memory - isn't that too heavy?some of the
> users have 10+ followers.
>
> Thanks.
>
> On Oct 4, 6:26 pm, Thomas Hübner  wrote:
>
> > the problem is that a friendship exist is an "expensive" API Call (of
> > 150 possible per hr) I do not know what kind of Application you plan but
> > for my client App I load the ID's of followers with one API call and
> > keep this list in memory. If a status become loaded I compare the
> > icluded UserID with the list and switch the menues depending on
> > containing this ID or not. This is much faster then request the API each
> > time.
>
> > Only situation which is not working for are search calls because the
> > delivered result (ATOM) does not contain any userID which is a fail
>
> > twittme_mobi schrieb:
>
> > > Hi Tomas,
>
> > > thanks for the reply!
> > > the social graph methods are too heavy for such a simple operation.
> > > I have to check if user is followed every time that a profile is
> > > visited so
> > > i would now where to put "Follow" or "Unfollow" button.It is not
> > > reasonable
> > > to execute the social graph methods every time, because sometimes
> > > users might
> > > have thousands of followers.Isn't it the friendship/exists method that
> > > needs to be fixed,
> > > after all, it is just for checking if user is followed or not..
>
> > > Thanks!Your opinion is welcome!
>
> > > On Oct 3, 2:20 pm, Thomas Hübner  wrote:
> > >> you have the social graph methods which deliver ID's. Unfortunately the
> > >> same API call for screennames is missed - so you never can make
> > >> comparings with search API results because there is no userID in.
>
> > >> friends/ids
> > >> followers/ids
>
> > >> cheers,
> > >> Thomas
>
> > >> twittme_mobi schrieb:
>
> > >>> Hi guys, i tried friendship/exists but it throws an
> > >>> error when the user is protected.How should i accomplish this task
> > >>> with the API?
>
> > >>  signature.asc
> > >> < 1KViewDownload
>
> >  signature.asc
> > < 1KViewDownload

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

Hi Tomas,

Thanks for the clarification.
One question - if you have many users, you will need to load all the
IDs
for All the users in the memory - isn't that too heavy?some of the
users have 10+ followers.

Thanks.

On Oct 4, 6:26 pm, Thomas Hübner  wrote:
> the problem is that a friendship exist is an "expensive" API Call (of
> 150 possible per hr) I do not know what kind of Application you plan but
> for my client App I load the ID's of followers with one API call and
> keep this list in memory. If a status become loaded I compare the
> icluded UserID with the list and switch the menues depending on
> containing this ID or not. This is much faster then request the API each
> time.
>
> Only situation which is not working for are search calls because the
> delivered result (ATOM) does not contain any userID which is a fail
>
> twittme_mobi schrieb:
>
> > Hi Tomas,
>
> > thanks for the reply!
> > the social graph methods are too heavy for such a simple operation.
> > I have to check if user is followed every time that a profile is
> > visited so
> > i would now where to put "Follow" or "Unfollow" button.It is not
> > reasonable
> > to execute the social graph methods every time, because sometimes
> > users might
> > have thousands of followers.Isn't it the friendship/exists method that
> > needs to be fixed,
> > after all, it is just for checking if user is followed or not..
>
> > Thanks!Your opinion is welcome!
>
> > On Oct 3, 2:20 pm, Thomas Hübner  wrote:
> >> you have the social graph methods which deliver ID's. Unfortunately the
> >> same API call for screennames is missed - so you never can make
> >> comparings with search API results because there is no userID in.
>
> >> friends/ids
> >> followers/ids
>
> >> cheers,
> >> Thomas
>
> >> twittme_mobi schrieb:
>
> >>> Hi guys, i tried friendship/exists but it throws an
> >>> error when the user is protected.How should i accomplish this task
> >>> with the API?
>
> >>  signature.asc
> >> < 1KViewDownload
>
>
>
>  signature.asc
> < 1KViewDownload

[twitter-dev] Re: How to check if user is followed?

[twittme_mobi]

Hi Tomas,

thanks for the reply!
the social graph methods are too heavy for such a simple operation.
I have to check if user is followed every time that a profile is
visited so
i would now where to put "Follow" or "Unfollow" button.It is not
reasonable
to execute the social graph methods every time, because sometimes
users might
have thousands of followers.Isn't it the friendship/exists method that
needs to be fixed,
after all, it is just for checking if user is followed or not..

Thanks!Your opinion is welcome!

On Oct 3, 2:20 pm, Thomas Hübner  wrote:
> you have the social graph methods which deliver ID's. Unfortunately the
> same API call for screennames is missed - so you never can make
> comparings with search API results because there is no userID in.
>
> friends/ids
> followers/ids
>
> cheers,
> Thomas
>
> twittme_mobi schrieb:
>
> > Hi guys, i tried friendship/exists but it throws an
> > error when the user is protected.How should i accomplish this task
> > with the API?
>
>
>
>  signature.asc
> < 1KViewDownload

[twitter-dev] How to check if user is followed?

[twittme_mobi]

Hi guys, i tried friendship/exists but it throws an
error when the user is protected.How should i accomplish this task
with the API?

[twitter-dev] Re: Private user's 'following' information: why am I denied access via API but can get through Twitter.com?

[twittme_mobi]

So..should we open a new defect for friendships/exists  - since it
thows an
error if user is privated and i still need just to check if one user
is following another...

On Oct 1, 2:18 am, Dusty  wrote:
> I've noticed this issue with the social graph methods as well.
>
> I can see who's following a protected user via the website. 
> ex:http://twitter.com/msmosso/followers
>
> But you can't get this data from the API anymore. ex: curl -u
> username:passwordhttp://twitter.com/friends/ids/msmosso.xml
>
> This is a recent change. Maybe 2 weeks ago this happened.
>
> I wonder if I should expect the behavior to go back like it was, or if
> I should start asking protected account holder to authenticate if they
> want to see their Friend Or Follow page. Any ideas?
>
> Dusty
>
> On Sep 30, 4:46 pm, Raffi Krikorian  wrote:
>
> > sorry - i guess i'm confused.  we're speaking about the friendships/
> > exists endpoint?  that changelong refers to statuses/friends, statuses/
> > followers, friends/ids, and followers/ids.  sorry for the confusion.
>
> > i would suggest creating a ticket on the google code tracker and star  
> > it if you're interested in it.  that way somebody can take care of it.
>
> > thanks!
>
> > > Yes, this is still the case. I thought for sure Tweet Thief was  
> > > missing something obvious, but when I went and tried it, he is 100%  
> > > correct!
>
> > > I agree with him that this is a serious bug that needs to be fixed.
>
> > > Jim Renkel
>
> > > -Original Message-
> > > From: twitter-development-talk@googlegroups.com 
> > > [mailto:twitter-development-talk@googlegroups.com
> > > ] On Behalf Of Raffi Krikorian
> > > Sent: Wednesday, September 30, 2009 14:12
> > > To: twitter-development-talk@googlegroups.com
> > > Subject: [twitter-dev] Re: Private user's 'following' information:  
> > > why am I denied access via API but can get through Twitter.com?
>
> > > is this actually the case?
>
> > >http://apiwiki.twitter.com/REST+API+Changelog
>
> > > on the 15th of september, this issue may have been cleared up.
>
> > >> This is an annoying inconsistency with the Twitter API.
>
> > >> If you do an authenticated call to view a user's friends/followers,
> > >> and that user is either blocking the authenticated user or is  
> > >> private,
> > >> you will not be able to view their friends/followers.  You will get
> > >> "not authorized" error.  However, if on Twitter.com, you login and  
> > >> try
> > >> to do the same thing, you CAN do this.
>
> > >> The solution in the API is to make UNauthenticated calls and you will
> > >> be able to view friends/followers without issue.
>
> > >> On Sep 3, 12:37 am, Tweet Thief  wrote:
> > >>> Summary Question: "If a user is 'private' on Twitter, why can I see
> > >>> their followers on Twitter.com (IFF I log in) but not through the
> > >>> API?"
>
> > >>> Details:
>
> > >>> For example, I went tohttp://twitter.com/just_me_hi/followers/and
> > >>> can see all of her followers, despite the fact that she is "private"
>
> > >>> (Note: I can see them on twitter.com while logged in even when I am
> > >>> fairly certain that she blocked me before going private.)
>
> > >>> curl -D - -s -u user:pass
> > >>> "http://twitter.com/friendships/exists.xml?user_a=just_me_hi&user_b=tw
> > >>> ..."
>
> > >>> Results in:
>
> > >>> HTTP/1.1 403 Forbidden
> > >>> Status: 403 Forbidden
> > >>> (irrelevant headers edited)
>
> > >>> 
> > >>> 
> > >>>  /friendships/exists.xml?
> > >>> user_a=just_me_hi&user_b=tweetthief
> > >>>  You do not have permission to retrieve following status for
> > >>> both specified users.
> > >>> 
>
> > >>> PLEASE NOTE: I tried the same API access from another account I am
> > >>> 99.% sure she did NOT block, and it still gives me this
> > >>> "permission error" so it does NOT appear to have anything to do with
> > >>> whether or not this account is "blocked" and everything to do with
> > >>> the
> > >>> fact that the account is marked "private"…
>
> > >>> I don't understand why the API gives me less access to information
> > >>> than the website.
>
> > >>> T.T.
>
> > >>> ps: @just_me_hi appears to have gone private after I (and others)
> > >>> called her out for plagiarism in violation of the Twitter TOS. You
> > >>> can
> > >>> see the chain of events here:
>
> > >>>http://tweetthief.tumblr.com/tagged/justmehi/chrono
>
> > >>> --http://tweetthief.tumblr.com
> > >>> Shining a light on users who plagiarize on Twitter
>
> > --
> > Raffi Krikorian
> > Twitter Platform Team
> > ra...@twitter.com | @raffi

[twitter-dev] cannot delete own status

[twittme_mobi]

Hi all,

my twitter app has the functionality to delete own statuses , using
statuses/destroy...
only that i can find in the logs a lot of errors stating:

No status found with that ID.

Here are some status IDs: 4470190247, 4470445033,4470418659

any help is appreciated...thanks.

[twitter-dev] Re: Private user's 'following' information: why am I denied access via API but can get through Twitter.com?

[twittme_mobi]

So...if user is protected and i am not following him, nor he is
following mecan i still
use friendship/show?

Basically i am trying to check in my application whether user is
followed or not by the logged-in user
How could i do that if friendship/exists is throwing an error in case
of protected user?

On Sep 3, 10:41 pm, TjL  wrote:
> On Thu, Sep 3, 2009 at 3:37 AM, Tweet Thief wrote:
> > curl -D - -s -u user:pass
> > "http://twitter.com/friendships/exists.xml?user_a=just_me_hi&user_b=tw...";
>
> Try the (new?) friendship/show:
>
> http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friendships-show
>
> curl -D - -s --netrc
> "http://twitter.com/friendships/show.xml?target_screen_name=tweetthief...";
>
> (you can avoid putting your username and password on the commandline
> if you use ~/.netrc)
>
> I was just looking at it for a little script I use that mimics doesfollow.com
>
> The advantage seems to be that you get both "directions" (does a
> follow b and does b follow a) in one API call, which makes a lot of
> sense.
>
> Dunno how long it's been there, but it's new to me… and it's one of my
> favorite new features in a long time, minor though it is.
>
> TjL

[twitter-dev] Re: Protect My Tweets feature and effect on replies to tweets

[twittme_mobi]

I am having such problems - in my twitter app,I am sending the search
results to the screen,
then someone is trying to re-tweet a status so status_id is passed to
my
re-tweet script so that text could be extracted and re-tweeted.Then i
have the following error:

"Sorry, you are not authorized to see this status"

If that's a normal behaviour then how can i extract just the text of
the statusshould i pass the whole text via
HTTP GET to my re-tweet script?

The problem is that i am

On Sep 30, 2:03 am, JDG  wrote:
> How are you getting the replies? From the streaming or search APIs, yes,
> it's to be expected. If you're getting it from your timeline, you have to
> follow that user.
>
>
>
> On Tue, Sep 29, 2009 at 13:32, kprobe  wrote:
>
> > I run a game called Tweet_Words via a server app which tweets out
> > clues every minute. People reply to @Tweet-Words with their guesses
> > just fine to play the game. However, I just found out that if a user
> > has Protect My Tweets activated, then replies to @Tweet_Words are
> > being ignored.
>
> > The user turned off the feature and played the game just fine.
>
> > Furthermore, if @Tweet_Words becomes a follower of the person, then
> > the person can reactive the Protect My Tweets feature and continue to
> > play.
>
> > Question: is this the normal behaviour of Twitter to totally ignore
> > tweets sent out by protected people?
>
> --
> Internets. Serious business.

[twitter-dev] Re: whitelisting of IP for application - does it applies for all users

[twittme_mobi]

Hi Chad,

You were right!Thanks for the hint.The point is:

1)I am moving to another hosting account and my new IP address is
69.175.24.45 ,
but just for accepting the client connections.I have an outband IP -
probably NAT server or
some GATEWAY with IP address of 69.175.29.34.

2) I already asked for whitelisting of  69.175.24.45 and it was
approved.Then I understood that i need
whitelisting for 69.175.29.34 and also asked for that but it was
rejected with no stated reason.

3)Probably your whitelisting team decided that this is not a
production system but note that it is
exactly regarding production migration, so i will really need
69.175.29.34  whitelisted so i can point
my current production domain to the new hosting account.

I know that this is a bit confusing but could you kindly help me to
resolve this issue.
I already sent another whitelisting request...i hope you will approve
it.

Note that, i will let you now when migration finish so you can delete
the IP addresses that i do not longer need.
Thanks!

On Sep 18, 11:21 pm, Chad Etzel  wrote:
> Hello,
>
> Are you absolutely sure that outgoing requests from your server are
> coming from the same IP you whitelisted? You will see an increased
> rate-limit on your personal account because that is the account you
> used to apply for whitelisting, so it will always have an increased
> limit no matter what IP it is using. Many hosting providers perform
> outgoing requests through a different IP (usually in some sort of NAT
> configuration).
>
> If you run
> curlhttp://jazzychad.net/iponly.php
> from your server do you get back the same IP?
>
> -Chad
>
> On Fri, Sep 18, 2009 at 8:03 AM, twittme_mobi  wrote:
>
> > Hi,
>
> > I have my ip whitelisted so it should get 2 request per hour.
> > The point is that when i login in with my username to my twitter
> > application hosted on the specified IP - i get all the 2 requests
> > per hourbut if i login with a different user name - i get only
> > 150.
>
> > My question is - shouldn't it apply for all the users using this IP ?
> > Isn't it that the purpose of the whitelisting?
> > My application will work fine only for my username?
>
> > You can find a test version of the app at -http://69.175.24.45
>
> > Thanks.

[twitter-dev] Re: Alert: "Twitpocalypse II" coming Friday, September 11th - make sure you can handle large status IDs!

[twittme_mobi]

Hopefully with php and no database i should not worry about this...

On Sep 21, 2:45 pm, Martin Dufort  wrote:
> Ryan: Is this still scheduled for today or tomorrow ?
>
> Thanks
> Martin Dufortwww.wherecloud.com
>
> On Sep 11, 3:00 pm, Ryan Sarver  wrote:
>
> > Hwee-Boon,
>
> > That is definitely part of the plan and hence why we are aiming for
> > that Monday / Tuesday. We know what a strain it can be to push stuff
> > out at the end of the week.
>
> > Best, Ryan
>
> > On Fri, Sep 11, 2009 at 10:27 AM, Hwee-Boon Yar  wrote:
>
> > > One suggestion: similar to API changes, it seems more appropriate that
> > > if you want to force it, to do it earlier in the week, starting
> > > Monday, rather than Friday. That leaves enough resources and hands to
> > > stock up water and non-perishable goods rather than on a Friday.
>
> > > --
> > > Hwee-Boon
>
> > > On Sep 12, 12:27 am, Ryan Sarver  wrote:
> > >> To give everyone an update --
>
> > >> We have been able to work with our operations team to delay the forced
> > >> update until around September 21st or 22nd (over a week away). Since
> > >> thistwitpocalypseis based on the tweet count, it is impossible to
> > >> predict exactly when it will happen and therefore we can only make
> > >> projections based on current usage and possible spikes. With that
> > >> being said, it *could* happen as early as Sept 16th (Wednesday), so
> > >> please start updating your applications now to handle the change. We
> > >> will be able to give you better estimates as the event moves closer
> > >> and we will be sure to update the list when we know the exact time of
> > >> the update.
>
> > >> Let us know if you have any questions and be sure to stock up on water
> > >> and non-perishable goods :)
>
> > >> Ryan
>
> > >> On Thu, Sep 10, 2009 at 9:10 AM, Ivan Kirigin 
> > >> wrote:
>
> > >> > Call me crazy, but I store any data from a 3rd party in strings.
> > >> > Typically, I used a text blob to store some serialized object (like
> > >> > json or a python pickle) which maximizes flexibility. For the tweet
> > >> > id, I think I used 64 chars.
>
> > >> > In about 10 years, after I've cleared all the other higher priority
> > >> > and more impactful optimizations, I might think about dealing with
> > >> > this again.
>
> > >> > Ivan
> > >> >http://kirigin.com
>
> > >> > On Sep 10, 5:48 am, JDG  wrote:
> > >> >> and if they are, just store the twos complement of the ID in the DB 
> > >> >> and do
> > >> >> the math when you retrieve if it's negative. :)
>
> > >> >> On Thu, Sep 10, 2009 at 00:12, Rob Ashton  
> > >> >> wrote:
> > >> >> >  I've always just stored as 64bit integers, I'd assumed that 32bit
> > >> >> > wouldn't be enough.
>
> > >> >> > Now, if it goes above 64bit then I'm screwed, because neither my 
> > >> >> > language
> > >> >> > or database have built in support for that! :P
>
> > >> >> >  *From:* JDG 
> > >> >> > *Sent:* Thursday, September 10, 2009 4:21 AM
> > >> >> > *To:* twitter-development-talk@googlegroups.com
> > >> >> > *Subject:* [twitter-dev] Re: Alert: "TwitpocalypseII" coming Friday,
> > >> >> > September 11th - make sure you can handle large status IDs!
>
> > >> >> > if you were on signed32 you'd have had a problem a long time ago. 
> > >> >> > not quite
> > >> >> > sure why people haven't just taken to treating/storing as strings 
> > >> >> > -- sure
> > >> >> > there's a bit more overhead mem/storage-wise, but you don't have to 
> > >> >> > change
> > >> >> > your code every few months.
>
> > >> >> > On Wed, Sep 9, 2009 at 16:45, Joseph Cheek  wrote:
>
> > >> >> >> Twitter is in league with Al Qaida!  You heard it first here, 
> > >> >> >> folks!
>
> > >> >> >> Ok, seriously, this message I wrote wasn't worth the electrons it 
> > >> >> >> took
> > >> >> >> to transmit it...  let's see if I can increase the s2n ratio:
>
> > >> >> >> 4294967296, that an unsigned 32-bit int?  ok, fair enough.  i know 
> > >> >> >> some
> > >> >> >> of my apps use signed 64bit ints, but i'm not sure about the db... 
> > >> >> >> will
> > >> >> >> need to check... might be signed32...
>
> > >> >> >> Joseph Cheek
> > >> >> >> jos...@cheek.com,www.cheek.com
> > >> >> >> twitter:http://twitter.com/cheekdotcom
>
> > >> >> >> Nicholas Moline wrote:
> > >> >> >> > And nobody thought about the significance of accelerating 
> > >> >> >> > anything
> > >> >> >> > called a *pocolypse to be on the anniversary of a date that 
> > >> >> >> > thousands
> > >> >> >> > died in a terrorist attack Tactful Twitter... Real Tactful
>
> > >> >> >> > On Wed, Sep 9, 2009 at 1:00 PM, Alex Payne  > >> >> >> > > wrote:
>
> > >> >> >> >     Sorry, an error in phrasing. It was previously mentioned 
> > >> >> >> > that this
> > >> >> >> >     change was pending. We had not previously announced a date 
> > >> >> >> > for the
> > >> >> >> >     change.
>
> > >> >> >> >     Normally, we prefer to provide more advance notice where 
> > >> >> >> > possible,
> > >> >> >> but
> >

[twitter-dev] whitelisting of IP for application - does it applies for all users

[twittme_mobi]

Hi,

I have my ip whitelisted so it should get 2 request per hour.
The point is that when i login in with my username to my twitter
application hosted on the specified IP - i get all the 2 requests
per hourbut if i login with a different user name - i get only
150.

My question is - shouldn't it apply for all the users using this IP ?
Isn't it that the purpose of the whitelisting?
My application will work fine only for my username?

You can find a test version of the app at - http://69.175.24.45

Thanks.

[twitter-dev] Re: Source parameter only available through oauth - misses a use case

[twittme_mobi]

Ok, but againplease make OAuth pages at twitter mobile friendly so
that the mobile web sites can use it!

On Sep 15, 11:28 am, Duane Roelands  wrote:
> It's an incentive to move to OAuth.
>
> Twitter has made their intentions clear about Basic Auth: They want it
> to go away.  By restricting the "source" parameter to OAuth requests,
> they give developers an incentive to move forward.
>
> On Sep 15, 4:20 am, Emrah  wrote:
>
> > I totally agree... Ivo, I got the same answers for a pretty similar
> > question some months ago...
> > I do not see the link between the source parameter and how the
> > authentication is made...
>
> > Cheers!
>
> > Ivo wrote:
> > > Hi,
>
> > > short answer: oauth is for delegated authentication; I'm using direct
> > > authentication of my own account. Both are valid use cases, so in my
> > > opinion the source parameter should continue to work for the second
> > > use case (I can't find a good reason to only support it for delegated
> > > authentication)
>
> > > Besides; all the examples you mention are for delegated
> > > authentication; it would be weird to have a headless system that is
> > > working as a service implement an oauth scheme.
>
> > > greetings,
> > > Ivo
>
> > > On Sep 14, 12:09 pm, Andrew Badera  wrote:
>
> > >> With all the freely available examples, and all the freely available
> > >> documentation and support available through oauth.net, what's stopping
> > >> you from cranking out an OAuth client implementation in <2 hours?
>
> > >> OAuth helps prevent, or at least make obvious for the time being,
> > >> spammers. HTTP Basic Auth has no value here.
>
> > >> ∞ Andy Badera
> > >> ∞ +1 518-641-1280
> > >> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> > >> ∞ Google me:http://www.google.com/search?q=andrew%20badera
>
> > >> On Mon, Sep 14, 2009 at 1:48 AM, Ivo  wrote:
>
> > >>> Hi,
>
> > >>> the developer wiki mentions that the source parameter is no longer
> > >>> recommended, because using oauth, twitter can already know the source
> > >>> of messages.
>
> > >>> However, there are a few use case scenario's that are limited if
> > >>> source is only available through oauth.
>
> > >>> Oauth is all about delegated authentication. It's about the user
> > >>> granting access to his resources to a service.
>
> > >>> There are services out there that do not use the user's credentials at
> > >>> all, but use their own account. E.g. I built flackr.net, and it logs
> > >>> in with its own @flackr account to follow its own timeline and
> > >>> aggregate news on a website. I don't need user's credentials at all
> > >>> for that. The Flackr backend is autonomous and runs on a server that
> > >>> has no web frontend, it just fetches data and processes it. It does
> > >>> send out tweets when it has aggregated something interesting.
>
> > >>> If I were to use oauth in this scenario I would have to build in full
> > >>> oauth support in my backend script, only to login once with my own
> > >>> account to grant myself access.  Since this is not about delegated
> > >>> access, I don't need oauth and can authenticate against twitter
> > >>> directly.
>
> > >>> This is a perfectly good use case scenario, and the source parameter
> > >>> would have to stay in order to support this use case scenario while
> > >>> still providing a different source.

[twitter-dev] Re: email used as login causing problems

[twittme_mobi]

Hi All,

any update on that?
How are you handling e-mail logins?

Regards.

On Sep 6, 5:06 pm, twittme_mobi  wrote:
> Hello Abraham,
>
> currently this method is returning empty response e.g. "".
> If it returns empty response - my application knows that this is
> sicessfulllogin,
> otherwise - it prints the error.The docs regarding this should be
> updated.
>
> Greetings!
>
> On Sep 5, 12:27 pm, Abraham Williams <4bra...@gmail.com> wrote:
>
> > You should be able to 
> > use:http://apiwiki.twitter.com/Twitter-REST-API-Method:-account
> > verify_credentials<http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0veri...>
> > to
> > get the user_id/screen_name.
> > Abraham
>
> > On Sat, Sep 5, 2009 at 05:20, twittme_mobi  wrote:
>
> > > Hello,
>
> > > sometimes usersloginwith theire-mail,
> > > while my app is expecting username.
> > > the user canloginwith no problems but later on, the app
> > > is using thee-mailinstead oflogin/screen name.
>
> > > s there any way to get user id/screen_name frome-mail.
> > > how can one overcome this problem?
>
> > > Thanks!
>
> > --
> > Abraham Williams | Community Evangelist |http://web608.org
> > Hacker |http://abrah.am|http://twitter.com/abraham
> > Project |http://fireeagle.labs.poseurtech.com
> > Thisemailis: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: 200 "errors"

[twittme_mobi]

it happens even more often now...

On Sep 9, 3:50 am, Jonathan Smith  wrote:
> This happens to me when I do json get requests as well.
> It happens very inconsistently during a normal session, but I can
> almost always reproduce it if I let the client sit for a while and
> then try.
>
> Is almost as if the server can't authenticate the request fast enough
> and throws back an empty html page by default.
>
> On Sep 7, 10:48 am, Rich  wrote:
>
>
>
>
>
> > Can we please hear something from someone at Twitter about this, it's
> > becoming unusable with constant XML errors
>
> > On Sep 7, 4:51 am, Naveen A  wrote:
>
> > > We are seeing this HTML META REFRESH as well from our clients. We are
> > > a mobile application and seeing this issue more and more frequently to
> > > the point that application is not functioning properly, its hard for
> > > use to provide any specific ip data as the carriers are most likely
> > > proxying the requests from the device.
>
> > > It is not limited to a specific api call either, it is a systemic
> > > issue across a wide range of calls we make.
>
> > > There was a ticket related to the issue in the bug tracker for search,
> > > but it has been closed and I think it should be re-opened as it is
> > > still a problemhttp://code.google.com/p/twitter-api/issues/detail?id=968
>
> > > Any feedback would be appreciated.
>
> > > On Sep 6, 3:01 pm, Rich  wrote:
>
> > > > Yeah it's happening to me again, same as my previous email, except the
> > > > time stamp will be around 2 minutes ago
>
> > > > On Sep 6, 4:05 pm, twittme_mobi  wrote:
>
> > > > > Hi Ryan,
>
> > > > > I am getting the same error - i can found it in the logs of my app
> > > > > every day - at least 20 times.
>
> > > > > 1. The IP of the machine making requests to the Twitter API. If you're
> > > > > behind NAT, please be sure to send us your *external* IP.
>
> > > > > --->
> > > > > Name:    twittme.mobi
> > > > > Address:  67.222.129.154
>
> > > > > 2. The IP address of the machine you're contacting in the Twitter
> > > > > cluster. You can find this on UNIX machines via the "host" or
> > > > > "nslookup" commands, and on Windows machines via the "nslookup"
> > > > > command.
>
> > > > > --->
> > > > > Name:    twitter.com
> > > > > Address:  128.121.146.100
>
> > > > > 3. The Twitter API URL (method) you're requesting and any other
> > > > > details about the request (GET vs. POST, parameters, headers, etc.).
>
> > > > > --->
> > > > > 'account/rate_limit_status.xml'
>
> > > > > 4. Your host operating system, browser (including version), relevant
> > > > > cookies, and any other pertinent information about your environment.
>
> > > > > --->
> > > > > Linux, mobile browser,firefox, no cookies used.
>
> > > > > 5. What kind of network connection you have and from which provider,
> > > > > and what kind of network connectivity devices you're using.
>
> > > > > --->
> > > > > devices are mostly mobile..probably using mobile connections or
> > > > > wireless.
>
> > > > > Thanks!
>
> > > > > On Sep 5, 2:54 pm, Alex  wrote:
>
> > > > > > hi Ryan,
> > > > > > any update on this issue ?

[twitter-dev] Re: email used as login causing problems

[twittme_mobi]

Hello Abraham,

currently this method is returning empty response e.g. "".
If it returns empty response - my application knows that this is
sicessfull login,
otherwise - it prints the error.The docs regarding this should be
updated.

Greetings!

On Sep 5, 12:27 pm, Abraham Williams <4bra...@gmail.com> wrote:
> You should be able to 
> use:http://apiwiki.twitter.com/Twitter-REST-API-Method:-account
> verify_credentials<http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0veri...>
> to
> get the user_id/screen_name.
> Abraham
>
> On Sat, Sep 5, 2009 at 05:20, twittme_mobi  wrote:
>
> > Hello,
>
> > sometimes users login with their e-mail,
> > while my app is expecting username.
> > the user can login with no problems but later on, the app
> > is using the e-mail instead of login/screen name.
>
> > s there any way to get user id/screen_name from e-mail.
> > how can one overcome this problem?
>
> > Thanks!
>
> --
> Abraham Williams | Community Evangelist |http://web608.org
> Hacker |http://abrah.am|http://twitter.com/abraham
> Project |http://fireeagle.labs.poseurtech.com
> This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: 200 "errors"

[twittme_mobi]

Hi Ryan,

I am getting the same error - i can found it in the logs of my app
every day - at least 20 times.

1. The IP of the machine making requests to the Twitter API. If you're
behind NAT, please be sure to send us your *external* IP.

--->
Name:twittme.mobi
Address:  67.222.129.154

2. The IP address of the machine you're contacting in the Twitter
cluster. You can find this on UNIX machines via the "host" or
"nslookup" commands, and on Windows machines via the "nslookup"
command.

--->
Name:twitter.com
Address:  128.121.146.100

3. The Twitter API URL (method) you're requesting and any other
details about the request (GET vs. POST, parameters, headers, etc.).

--->
'account/rate_limit_status.xml'

4. Your host operating system, browser (including version), relevant
cookies, and any other pertinent information about your environment.

--->
Linux, mobile browser,firefox, no cookies used.

5. What kind of network connection you have and from which provider,
and what kind of network connectivity devices you're using.

--->
devices are mostly mobile..probably using mobile connections or
wireless.

Thanks!


On Sep 5, 2:54 pm, Alex  wrote:
> hi Ryan,
> any update on this issue ?

[twitter-dev] email used as login causing problems

[twittme_mobi]

Hello,

sometimes users login with their e-mail,
while my app is expecting username.
the user can login with no problems but later on, the app
is using the e-mail instead of login/screen name.

s there any way to get user id/screen_name from e-mail.
how can one overcome this problem?

Thanks!

[twitter-dev] Error "invalid body" when invoking get rate limit

[twittme_mobi]

Hi All,

I get the following error message for some invocations of:
account/rate_limit_status.xml

I found this in the logs of my application.It happens about 20 times a
day but it is
still annoying.Most of the time it works fine, so i guess it is due to
high load or something
any idea?

Greeting!

[twitter-dev] Re: Mobile oAuth

[twittme_mobi]

Jim,

Thanks for the broad summary,
I fully agree with you.
There should be some mechanism for mobile devices with
less resources for OAuth.

Regarding the source parameter of the Application, it is very
important with regards of e-marketing of the application itself.

Greetings!

On Sep 5, 2:08 am, "Jim Renkel"  wrote:
> OAuth is great, in certain circumstances. In others, it's not so great.
>
> Circumstances for which it is great include:
> -   consumer web sites; and
> -   consumer client applications that have access to a reasonable
> browser on
>     the client device
> in both cases with the qualification that the authorization pages of the
> service provider are in a language (e.g., English, Japanese, etc.) that
> is the same as that used by the consumer.
>
> In these circumstances, OAuth as defined by the specifications and
> implemented by twitter works very well.
>
> Circumstances for which it is not so great include:
> -   consumer client applications that do not have access to a reasonable
>     browser on the client device; and
> -   consumer client applications and web sites that are in languages for
>     which service authorization pages in those languages are not
> available.
>
> In these circumstances, OAuth as defined by the specifications and
> implemented by twitter does not work so well.
>
> Currently, in circumstances where OAuth does not work very well, twitter
> client applications and web-sites can resort to Basic Authentication.
>
> The drawbacks to this are obvious:
> -   the user must give their twitter password to the client;
> -   at some point twitter will no longer support Basic Authentication;
> and
> -   the source of tweets created by these clients is "API" rather than
> the
>     client's name.
>
> Pooh pooh the last drawback if you will, but to some it is important.
>
> Now, the fact of the matter is that some users are perfectly comfortable
> in giving their twitter passwords to client applications and web-sites,
> even where those clients support OAuth.
>
> I don't think these users should be penalized and forced to use OAuth
> if'n and when'n twitter drops support for Basic Authentication.
>
> And if'n and when'n twitter drops support for Basic Authentication,
> client applications and web-sites that now only support Basic
> Authentication will be forced to support OAuth. Myself, I don't think
> that's an unreasonable requirement, but others may differ.
>
> And I don't think these creators should have to forgo having their
> client's name as the source of tweets their clients create, now or ever,
> just because their users chose to trust them to use Basic
> Authentication.
>
> So I propose the following enhancement to twitter's OAuth
> implementation:
>
> Allow a userID and password to be included as optional parameters of an
> oauth/access_token request. If supplied and authentic, they would cause
> a valid access token to be returned without the user having visited the
> authorize URL and approved the access.
>
> Alternately, the userID and password could be optional on an
> oauth/request_token request, in which case, if supplied and authentic,
> the request would return a valid access token, rather than a request
> token, again without the user having visited the authorize URL and
> approved the access. The advantage to this alternative is it reduces by
> one the number of API calls needed.
>
> I believe either of these alternatives is a viable solution for the
> circumstances where the existing OAuth implementation does not work so
> great.
>
> Comments expected and welcome.
>
> Jim Renkel
>
> -Original Message-
> From: twitter-development-talk@googlegroups.com
>
> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of
> twittme_mobi
> Sent: Friday, September 04, 2009 08:39
> To: Twitter Development Talk
> Subject: [twitter-dev] Re: Mobile oAuth
>
> I am also interested in mobile oath solution.
> twitter guys should think of something before deprecating basic auth
>
> On Aug 20, 8:01 am, Cameron Kaiser  wrote:
> > > I have a mobile based twitter client in the field and have
> implemented
> > > oAuth for this client. Some of the devices are either very low
> memory
> > > or have primitive browsers that dont support the rendering of the
> > > 'allow' / 'deny' access page (http://twitter.com/oauth/authorize). I
> > > have tried the obvioushttp://m.twitter.com/oauth/authorizebutthis
> > > seems to serve the same standard webage.
>
> > > So Im looking for nat previous info or plans of a lightweight
> > > implementation of oAuth access page for twitter.
>
> > I'm also particularly interested in such a page, especially one a text
> > browser could access such as Lynx or w3m.
>
> > --
> > 
> personal:http://www.cameronkaiser.com/--
> >   Cameron Kaiser * Floodgap Systems *www.floodgap.com*
> ckai...@floodgap.com
> > -- Adore, v.: To venerate expectantly. -- Ambrose Bierce
> --

[twitter-dev] Whitelist domain name instead of IP

[twittme_mobi]

My IP is already whitelisted but is it possible to whitelist the
domain, because my app will be in trouble if they change my IP from
the hosting center?

[twitter-dev] Re: OAuth + Mobile nightmare

[twittme_mobi]

in addition to storing the access token somewhere , wouldn't it be
better
if twitter deliver mobile friendly version of the oauth pages?

On Aug 19, 12:14 am, JDG  wrote:
> That's what you should be doing. There's no reason to get a new Access Token
> every time. Per the OAuth spec, you should probably code your app to handle
> an expired token gracefully. The spec states that tokens MAY expire --
> Twitter currently does not expire theirs, though. However, that doesn't mean
> that they couldn't in the future.
>
> 2009/8/18 André Arruda 
>
>
>
> > I'm thinking about storing the access token in the phone so the user won't
> > have to go
> > through all the auth process everytime the program is opened.
>
> > I hope i won't find any new "surprises" by doing this.
>
> > 2009/8/18 Otávio Ribeiro 
>
> > no.. just the same problem.
>
> >> On Mon, Aug 17, 2009 at 3:09 PM, AArruda  wrote:
>
> >>> I've been developing a Java/MIDP Twitter client for the past two
> >>> months, and i still need a couple more months to publish a beta
> >>> version. A few days ago i found out that the update source (app name)
> >>> is no longer customizable unless the client uses OAuth for
> >>> authentication, which means that any update sent through my client is
> >>> shown as "from API" instead of my app's name.
>
> >>> I understand that OAuth is important for many security reasons, but it
> >>> still has important issues with mobile applications, forcing the user
> >>> to open a page through a mobile device, writing down the PIN,
> >>> switching back to the app and logging in again is just hell. Not to
> >>> mention the smartphones that don't support programs running in the
> >>> background.
>
> >>> The current API's methods shouldn't be restricted to OAuth unless
> >>> these issues are solved first. We, developers and mobile users, would
> >>> be thankful.
>
> >>> Is anyone using any other solution for OAuth and mobile devices, if
> >>> there is any?
>
> --
> Internets. Serious business.

[twitter-dev] Re: Mobile oAuth

[twittme_mobi]

I am also interested in mobile oath solution.
twitter guys should think of something before deprecating basic auth

On Aug 20, 8:01 am, Cameron Kaiser  wrote:
> > I have a mobile based twitter client in the field and have implemented
> > oAuth for this client. Some of the devices are either very low memory
> > or have primitive browsers that dont support the rendering of the
> > 'allow' / 'deny' access page (http://twitter.com/oauth/authorize). I
> > have tried the obvioushttp://m.twitter.com/oauth/authorizebut this
> > seems to serve the same standard webage.
>
> > So Im looking for nat previous info or plans of a lightweight
> > implementation of oAuth access page for twitter.
>
> I'm also particularly interested in such a page, especially one a text
> browser could access such as Lynx or w3m.
>
> --
>  personal:http://www.cameronkaiser.com/--
>   Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com
> -- Adore, v.: To venerate expectantly. -- Ambrose Bierce 
> --