[twitter-dev] Re: A few updates about the permission model change

[Aaron Rankin]

Hi Matt,

We missed the bit about having to use oauth/authorize and were going
through oauth/authenticate. Via oauth/authorize it's working properly.


Aaron

On Jun 23, 6:57 pm, Matt Harris  wrote:
> Hi Aaron,
>
> I have't been able to reproduce this issue so could you email me details of
> the app and captures of the requests and responses. Then I can investigate
> further.
>
> Thanks,
> @themattharris <https://twitter.com/intent/follow?screen_name=themattharris>
> Developer Advocate, Twitter
>
> On Wed, Jun 22, 2011 at 12:57 PM, Aaron Rankin 
> wrote:
>
>
>
>
>
>
>
> > Hi Matt / Twitter,
>
> > We're not seeing the Direct Message permission setting ever take
> > effect. In our application profile, it says that we're set to request
> > read, write and DM, and we've saved this several times successfully.
> > However, both the X-Access-Level header and the oauth/authorize page
> > list that we don't have DM access (and for the former, on accounts for
> > which we've re-authorized).
>
> > Aaron
>
> > On Jun 13, 7:56 pm, Matt Harris  wrote:
> > > Hey everyone,
>
> > > A number of updates were made to the Direct Message methods and OAuth
> > > screens at the end of last week. Here's what went out:
>
> > > * force_login is now supported onhttps://api.twitter.com/oauth/authorize
> > > * the OAuth screens now support a feature phone tier of handsets and
> > render
> > > them in a simpler format
> > > * the language on all the screens is standardized to say "direct message"
> > > * there is a "Return to App" URL on the Deny and Cancel screens that
> > > redirects the user to the oauth_callback url with a 'denied' parameter
> > > instead of oauth_token.
>
> > > This next parameter isn't needed by everybody but we will be adding
> > > screen_name support to the authorize and authenticate pages in the next
> > few
> > > days. If you want to add this to your code ready for when we release the
> > > feature you can, but please know the screen_name parameter will be
> > ignored
> > > unless you also provide the force_login parameter. The screen_name
> > parameter
> > > pre-fills the username field of the OAuth screen when force_login is
> > true.
> > > The user is still able to edit the field, even if it is prefilled.
>
> > > Lastly, these are the main points discussed in previous emails and
> > Tweets:
> > > * The new permission level will be enforced on 30th June.
> > > * If you don't need to read or delete direct messages you do not need to
> > > update the permission level of your application.
> > > * Read/Write applications will still be able to send direct messages,
> > even
> > > after the enforcement date.
> > > * Existing oauth_tokens will not be invalidated, even if the application
> > > permission level is altered.
> > > * You can find out the current permission level of an oauth_token by
> > > inspecting the headers of an authenticated request to the API. Look for
> > > the X-Access-Level header.
>
> > > Best,
> > > @themattharris <
> >https://twitter.com/intent/follow?screen_name=themattharris>
> > > Developer Advocate, Twitter
>
> > --
> > 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 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: A few updates about the permission model change

[Aaron Rankin]

Hi Matt / Twitter,

We're not seeing the Direct Message permission setting ever take
effect. In our application profile, it says that we're set to request
read, write and DM, and we've saved this several times successfully.
However, both the X-Access-Level header and the oauth/authorize page
list that we don't have DM access (and for the former, on accounts for
which we've re-authorized).


Aaron


On Jun 13, 7:56 pm, Matt Harris  wrote:
> Hey everyone,
>
> A number of updates were made to the Direct Message methods and OAuth
> screens at the end of last week. Here's what went out:
>
> * force_login is now supported onhttps://api.twitter.com/oauth/authorize
> * the OAuth screens now support a feature phone tier of handsets and render
> them in a simpler format
> * the language on all the screens is standardized to say "direct message"
> * there is a "Return to App" URL on the Deny and Cancel screens that
> redirects the user to the oauth_callback url with a 'denied' parameter
> instead of oauth_token.
>
> This next parameter isn't needed by everybody but we will be adding
> screen_name support to the authorize and authenticate pages in the next few
> days. If you want to add this to your code ready for when we release the
> feature you can, but please know the screen_name parameter will be ignored
> unless you also provide the force_login parameter. The screen_name parameter
> pre-fills the username field of the OAuth screen when force_login is true.
> The user is still able to edit the field, even if it is prefilled.
>
> Lastly, these are the main points discussed in previous emails and Tweets:
> * The new permission level will be enforced on 30th June.
> * If you don't need to read or delete direct messages you do not need to
> update the permission level of your application.
> * Read/Write applications will still be able to send direct messages, even
> after the enforcement date.
> * Existing oauth_tokens will not be invalidated, even if the application
> permission level is altered.
> * You can find out the current permission level of an oauth_token by
> inspecting the headers of an authenticated request to the API. Look for
> the X-Access-Level header.
>
> Best,
> @themattharris 
> Developer Advocate, Twitter

-- 
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] Oauth authorize isn't working consistently

[Aaron Rankin]

I'm posting in case Twitter is unaware. The authorize page/process is
regularly returning no tokens. It is working some of the time. Our
users have reported this since Wednesday.

Aaron Rankin
Sprout Social

-- 
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] Search API OR queries returning wrong results

[Aaron Rankin]

Searches using OR where the result type is "recent" are returning
wrong results. For example, if I search for (ipad kid), I see results
from a minute ago. If I search for (ipad backseat), the most recent
tweet is about 5 hours ago. Then, if I search (ipad kid) OR (ipad
backseat), only the (ipad backseat) results are returned.


Aaaron

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

[twitter-dev] Missing @mention in the API

[Aaron Rankin]

Hi,

I'm wondering if the Search API, REST API and Site Streams may be
missing @mentions. This tweet (http://twitter.com/#!/AddisonWesley/
status/50587789309390848) exists on http://twitter.com/AddisonWesley,
but isn't present in the REST API or Search, as a mention of @rufusd,
and we think didn't come through Site Streams. I at first assumed it
had been deleted, but then why would it be still in the sender's feed?


Aaron

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

[twitter-dev] Sporadically missing oauth tokens after oauth/authorize

[Aaron Rankin]

Taylor/Twitter,

Sporadically, I'm seeing oauth tokens not returned after the authorize
step. I haven't seen the "woah there" reported much recently, but is
this a new issue?


Thanks,
Aaron

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

[twitter-dev] Seeing many "Woah there" errors on oauth/authenticate

[Aaron Rankin]

Our users are reporting many sporadic "Woah there" errors on the oauth/
authenticate page, where the error says the token info was already
used. We're forwarding our users to that page immediately after we get
the token info. Is this a problem with our oauth logic (we're using
Twitter Async / EpiTwitter) or is it an API issue?


Thanks,
Aaron

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

[twitter-dev] Local searches on Search API not working

[Aaron Rankin]

I'm consistently getting no results for a variety of Search API
queries using the geocode parameter. For example:

http://search.twitter.com/search.json?q=beer&rpp=100&page=1&geocode=41.938682556152344,-87.6544189453125,100mi&result_type=recent

http://search.twitter.com/search.json?q=tuesday&rpp=100&page=1&geocode=41.938682556152344,-87.6544189453125,100mi&result_type=recent


This is with 100 miles of Chicago. We all know that someone who's
geocoded will tweet about either beer or tuesday, near Chicago
(especially the former). I've tried other locations as well.

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

[twitter-dev] Direct Message endpoints returning HTTP 502 constantly

[Aaron Rankin]

Is this expected due to capacity or other infrastructure problems? Or,
am I doing something wrong?


Thanks,
Aaron

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

[twitter-dev] Re: statuses/mentions missing tweets

[Aaron Rankin]

Fair enough, though it hasn't corrected itself yet and I'm seeing it
on every user I test against so this feels like a systemic problem.
Our application caches all historical mentions of our users. How are
we to know when the API gives us valid results or not?

On Nov 8, 11:28 am, Taylor Singletary 
wrote:
> There are times when the cache is not warm with more recent tweets. These
> times will pass and there's really not much you can do from an API
> perspective when this condition is happening to a particular user's
> timelines. The data is just inaccessible to the API at the moment.
>
> Taylor
>
> On Sun, Nov 7, 2010 at 1:41 PM, Aaron Rankin wrote:
>
>
>
>
>
>
>
> > I'm seeing errors with this endpoint. A request for the last 200
> > mentions of @aaronrankin returns 29 mentions that were created between
> > February and now, with many missing. Per my own cache of tweets, there
> > were 200 mentions of @aaronrankin between September 3rd and today.
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

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

[twitter-dev] statuses/mentions missing tweets

[Aaron Rankin]

I'm seeing errors with this endpoint. A request for the last 200
mentions of @aaronrankin returns 29 mentions that were created between
February and now, with many missing. Per my own cache of tweets, there
were 200 mentions of @aaronrankin between September 3rd and today.

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

[twitter-dev] Re: statuses/retweets_of_me returning statuses that haven't been retweeted

[Aaron Rankin]

Taylor,

Is there an ETA on this feature? Or are there plans to include info
about distinct retweet actions on a given tweet? Just knowing that a
tweet was retweeted isn't too useful w/o additional API calls IMO.


Thanks,
Aaron

On Oct 6, 4:16 pm, Taylor Singletary 
wrote:
> The retweet_count and retweeted fields are not yet 100% functional.
>
> Taylor
>
> On Wed, Oct 6, 2010 at 2:01 PM, Aaron Rankin wrote:
>
>
>
>
>
>
>
> > I'm seeing a lot of statuses coming back from statuses/retweets_of_me
> > with "retweet_count" set to 0 or null and "retweeted" set to false.
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

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

[twitter-dev] statuses/retweets_of_me returning statuses that haven't been retweeted

[Aaron Rankin]

I'm seeing a lot of statuses coming back from statuses/retweets_of_me
with "retweet_count" set to 0 or null and "retweeted" set to false.

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

[twitter-dev] 401s from http://stream.twitter.com/statuses/filter

[Aaron Rankin]

I'm seeing plenty of 401s returned from the 
http://stream.twitter.com/statuses/filter
endpoint. This is still supporting basic auth, correct?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Bad characters in statuses/home_timeline JSON

[Aaron Rankin]

In some tweets, I'm seeing non-UTF8 characters being returned which
breaks the JSON. I notice it after "contributors_enabled" in the user
object.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Streaming API OAuth explanation?

[Aaron Rankin]

Hi,

Is there an ETA for enabling oauth on stream.twitter.com?


Thanks,
Aaron

On May 13, 1:11 pm, John Kalucki  wrote:
> OAuthis not enabled on stream.twitter.com. You can try on
> chirpstream.twitter.com.
>
> On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers  
> wrote:
> > I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
> > but I like to do things myself to learn.
>
> > Anyhow I am trying to accesshttp://stream.twitter.com/1/statuses/sample.xml
> > and I keep getting 401.
>
> > I have verified pretty much every parameter, and used the tool on
> >http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
> > to verify my signature is correct. I used twurl to obtain the user
> > access tokens to my account.
>
> > After doing some reading I'm no longer convinced that thestreaming
> > server even supportsoauth.
>
> > can you fill me in on the current status of stream.twitter.com and
> >oauth?
>
> > thanks!
> > Lucas
>
> > On Apr 20, 11:02 pm, Jonathon Hill  wrote:
> >> Thanks Taylor for the very detailed and helpful response!
>
> >> Jonathon
>
> >> On Apr 20, 1:17 pm, Taylor Singletary 
> >> wrote:
>
> >> > Hi Jonathon,
>
> >> > ForStreamingAPI access that isn't from the perspective of a user's
> >> > account, you would use two-leggedOAuthto establish authentication instead
> >> > of basic auth.
>
> >> > A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have
> >> > a specific resource you are trying to access, you have some parameters 
> >> > you
> >> > want to pass to that resource, and you have anOAuthconsumer key andOAuth
> >> > consumer secret. Which is unlike three-leggedOAuthwhere you also have
> >> > oauth_tokens representing either a user/access_token or a request token 
> >> > in
> >> > addition to the rest.
>
> >> > But the rules remain the same. You take all theOAuthparameters and the
> >> > parameters you are sending to the resource, organize them, build a 
> >> > signature
> >> > base string, then sign that with your consumer secret and send the 
> >> > request
> >> > on to Twitter properly signed. The only difference is that there is no
> >> > oauth_token and oauth_token_secret getting involved in the mix.
>
> >> > This is essentially what a two-legged request to thestreamingAPI would
> >> > look like:
>
> >> > Signature Base String
> >> > GET&http%3A%2F%2Fstream.twitter.com
> >> > %2F1%2Fstatuses%2Fsample.json&oauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0
>
> >> > Signature
> >> > Xi5jfuw2XqtU5KpNX9ZCtTptJS0=
>
> >> > Authorization Header
> >> >OAuthoauth_nonce="SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8",
> >> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1271783743",
> >> > oauth_consumer_key="ri8JxYK2zzwSV5xIUfNNvQ",
> >> > oauth_signature="Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D", oauth_version="1.0"
>
> >> > Taylor Singletary
> >> > Developer Advocate, Twitterhttp://twitter.com/episod
>
> >> > On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill  
> >> > wrote:
> >> > > One thing I meant to find out @chirp last week--what willoauthlook
> >> > > like for theStreamingAPI? I'm having a hard time visualizing how
> >> > > that will work.
>
> >> > > Thanks,
>
> >> > > Jonathon Hill
> >> > > @compwright
> >> > > Company52
> >> > >http://company52.com
>
> >> > > --
> >> > > Subscription settings:
> >> > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

[twitter-dev] Re: Slow response to twitter updates for a third party app

[Aaron Rankin]

FWIW, our application has been experiencing these same issues for
several weeks now. I've seen repeated overcapacity errors being
returned (the "too many tweets" HTML page) on both GET and POST
requests. I don't have specifics on likely times of the day, though US
Central nighttime seems much less likely than weekly business hours.
Our servers are located in Dallas, TX.

Let me know if there's anything else that would be helpful for me to
provide.

Thanks,
Aaron
Sprout Social

On May 12, 9:54 am, John Kalucki  wrote:
> It's probably on our end. I'll post some advice.
>
>
>
> On Wed, May 12, 2010 at 12:24 AM, Tjaap  wrote:
> > John,
> > can you already tell us something about the latency issue?
>
> > Is it your opinion that the many connect failures I am seeing are
> > something on my end? Or could that be correlated with the timeouts?
>
> > Thanks,
> > Jaap

[twitter-dev] /statuses/friends requiring auth for non-protected user

[Aaron Rankin]

I'm seeing /statuses/friends require authentication for multiple non-
protected users. Meanwhile, /statuses/followers is returning statuses
for the same users.

{"request":"/1/statuses/friends.json","error":"This method requires
authentication."}


-- 
Subscription settings: 
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

[twitter-dev] Re: Upcoming changes to the way status IDs are sequenced

[Aaron Rankin]

Taylor,

We too rely heavily on the sequential, increasing nature of standard
tweet and DM IDs. Are both are in scope here?

While it is straightforward to can change code to sort and compare on
dates, this will be a major undertaking for our application. I suspect
many other applications are in the same situation. This will be a
major impact to the community of existing applications.

I hope the Twitter technical team recognizes the pain this will cause
and has weighed all possible scaling alternatives.



Aaron

--
Sprout Social

On Mar 26, 3:41 pm, Taylor Singletary 
wrote:
> Hi Developers,
>
> It's no secret that Twitter is growing exponentially. The tweets keep coming
> with ever increasing velocity, thanks in large part to your great
> applications.
>
> Twitter has adapted to the increasing number of tweets in ways that have
> affected you in the past: We moved from 32 bit unsigned integers to 64-bit
> unsigned integers for status IDs some time ago. You all weathered that storm
> with ease. The tweetapoclypse was averted, and the tweets kept flowing.
>
> Now we're reaching the scalability limit of our current tweet ID generation
> scheme. Unlike the previous tweet ID migrations, the solution to the current
> issue is significantly different. However, in most cases the new approach we
> will take will not result in any noticeable differences to you the developer
> or your users.
>
> We are planning to replace our current sequential tweet ID generation
> routine with a simple, more scalable solution. IDs will still be 64-bit
> unsigned integers. However, this new solution is no longer guaranteed to
> generate sequential IDs.  Instead IDs will be derived based on time: the
> most significant bits being sourced from a timestamp and the least
> significant bits will be effectively random.
>
> Please don't depend on the exact format of the ID. As our infrastructure
> needs evolve, we might need to tweak the generation algorithm again.
>
> If you've been trying to divine meaning from status IDs aside from their
> role as a primary key, you won't be able to anymore. Likewise for usage of
> IDs in mathematical operations -- for instance, subtracting two status IDs
> to determine the number of tweets in between will no longer be possible.
>
> For the majority of applications we think this scheme switch will be a
> non-event. Before implementing these changes, we'd like to know if your
> applications currently depend on the sequential nature of IDs. Do you depend
> on the density of the tweet sequence being constant?  Are you trying to
> analyze the IDs as anything other than opaque, ordered identifiers? Aside
> for guaranteed sequential tweet ID ordering, what APIs can we provide you to
> accomplish your goals?
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: API speed is kicking ass lately...

[Aaron Rankin]

Yeah, in talking w/ @raffi on the API team, I learned that simply by
using the api.twitter.com URL when calling REST methods instead of the
legacy format of using just twitter.com, you're using a separate and
better hardware base. Hence, the chance for faster speeds. The
twitter.com REST methods share the same hardware as the twitter.com
website.

On Jan 15, 2:03 am, PJB  wrote:
> Woo hoo... something must have changed... for at least the past 24
> hours, I am noticing incredible performance from API calls.  Seems to
> be at least 40% faster than earlier in the week.

[twitter-dev] Search API suddenly stopped returning results for the same query

[Aaron Rankin]

Is anyone else seeing the Search API not returning results that it had
been returning recently? For example, this query returned results
consistently this morning and then recently stopped:

http://search.twitter.com/search.json...@aaronrankin&page=1&rpp=100&since_id=7452902654

It works without the since_id. And, I'm not having a rate limiting
issue.

[twitter-dev] Re: Private list statuses are missing many tweets

[Aaron Rankin]

Marcel,

My screenname is aaronrankin and the list is called sprout-social-
contacts.


Thanks,
Aaron

On Jan 5, 12:57 pm, Marcel Molina  wrote:
> Could you tell me your screen name and I'll pass your issue along to the
> team that maintains the list backend.
>
> On Mon, Jan 4, 2010 at 6:03 PM, Aaron Rankin  wrote:
> > I have a private list and both on twitter.com and via GET list /
> > statuses, many tweets are missing. I confirmed this behavior by
> > comparing the most recent tweets of several users to their public
> > timelines.
>
> --
> Marcel Molina
> Twitter Platform Teamhttp://twitter.com/noradio

[twitter-dev] Private list statuses are missing many tweets

[Aaron Rankin]

I have a private list and both on twitter.com and via GET list /
statuses, many tweets are missing. I confirmed this behavior by
comparing the most recent tweets of several users to their public
timelines.

[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)

[Aaron Rankin]

Does authenticate actually "authorize" the app to perform operations
on behalf of the user? My understanding is the user must first
"authorize" the app and then the app can send them through
"authenticate" in the future as a login check. If the user never
approves the app in an "authorize" operation, I don't think the app
has the right to perform and twitter operations on behalf of the user.

On Dec 29, 1:44 pm, Andy Freeman  wrote:
> > Nice =>https://twitter.com/oauth/authenticate?force_login=true?{signed
> > args} this stuff is working very well for me;) Thank you for your
> > hint.
>
> While that "works", I think that it shouldn't.
>
> (1) I don't think that it's a legal url because it has two '?'s.
> (2) force_login=true isn't part of the signed arguments so it should
> be rejected.  (The whole point of signing is to block man-in-the-
> middle attacks that alter arguments.)
>
> I haven't tried including force_login=true in the signed arguments.
> Are you saying that it doesn't work?  If so, I'd say that that's a
> bug, as is the above.
>
> Thanks,
> -andy
>
> On Dec 28, 9:41 pm, el moro  wrote:
>
> > Nice =>https://twitter.com/oauth/authenticate?force_login=true?{signed
> > args} this stuff is working very well for me;) Thank you for your
> > hint.
>
> > Axel
>
> > On 29 Dez., 03:21, Andy Freeman  wrote:
>
> > > > The difference (to my understanding) is that Authenticate does not
> > > > authorize the app.
>
> > > Huh?
>
> > > Whether I use authorize or authenticate, my app can tweet etc on the
> > > user's behalf.
>
> > > What, exactly, do you think that authenticate and authorize do?  I
> > > think that both can give my application a token that I can use to take
> > > actions on the user's behalf.  I think that both do some sort of login
> > > or check before doing so.
>
> > > The difference that I see is in how twitter presents its questions
> > > regarding the account that is allowing my application to do its thing.
>
> > > That, and the bit that authenticate leaves folks logged in to twitter.
>
> > > On Dec 28, 5:27 pm, Justyn  wrote:
>
> > > > The difference (to my understanding) is that Authenticate does not
> > > > authorize the app. We need to have the app authorized but want to give
> > > > the user the chance to choose which account to login with (and
> > > > Authorize).
>
> > > > Ideally, twitter state would not be effected, and user could authorize
> > > > an app with desired account (regardless of session) without clicking
> > > > "sign out".
>
> > > > Justyn
>
> > > > On Dec 28, 5:36 pm, Abraham Williams <4bra...@gmail.com> wrote:
>
> > > > > That is true. Authenticate currently leaves the user logged in.
>
> > > > > I would prefer that get fixed rather then adding force_login to 
> > > > > authorize as
> > > > > I view leaving users logged in as a security risk. Apparently Twitter 
> > > > > does
> > > > > not:
>
> > > > >http://code.google.com/p/twitter-api/issues/detail?id=1070
>
> > > > > On Mon, Dec 28, 2009 at 17:13, Andy Freeman  
> > > > > wrote:
> > > > > > > Then use authenticate. It accomplishes the same effect of 
> > > > > > > authorize.
>
> > > > > > Does it?  My notes say that authenticate leaves the user logged into
> > > > > > twitter if they weren't before and that authorize doesn't.
>
> > > > > > For my purposes, I'd like to force the user to specify their twitter
> > > > > > account and password even if they're already logged in and not 
> > > > > > change
> > > > > > their login state (as far as twitter is concerned) at all.
>
> > > > > > I can imagine folks who'd like to allow users to quickly authorize 
> > > > > > the
> > > > > > use of the logged in account (if any)
>
> > > > > > I can't imagine anyone who'd want to change the user's logged in
> > > > > > state.
>
> > > > > > On Dec 27, 6:08 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > > > > > > Then use authenticate. It accomplishes the same effect of 
> > > > > > > authorize.
>
> > > > > > > On Sun, Dec 27, 2009 at 17:42, Justyn  
> > > > > > > wrote:
> > > > > > > > Thanks Abraham - I understand this is the current limitation, 
> > > > > > > > however
> > > > > > > > I think there is a need for the foce_login to be available with 
> > > > > > > > the
> > > > > > > > authorize function. The authorize landing page is confusing to 
> > > > > > > > users
> > > > > > > > who want to sign-in with an account that is different from their
> > > > > > > > latest session. The "sign-out" option is not obvious to users. 
> > > > > > > > This is
> > > > > > > > based on user feedback, and I don't think we're the only ones 
> > > > > > > > having
> > > > > > > > this issue.
>
> > > > > > > > On Dec 27, 3:39 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > > > > > > > > force_login=true only works onhttps://
> > > > > > twitter.com/oauth/authenticatenot
> > > > > > > > > onhttps://twitter.com/oauth/authorize.
>
> > > > > > > > > On Sat, Dec 26, 2009 at 23:23, el moro 
> > > > > > > > > 
> > > > > > > > wrote:
> > > 

[twitter-dev] Statuses Followers and Statuses Friends not returning correct order

[Aaron Rankin]

Both of these methods are documented as returning people in the order
that the followed or were followed, starting with the most recent.
But, they aren't ordering them this way, and instead are ordering them
in some distinguishable manner.

[twitter-dev] Re: Search calls ever moving into REST API?

[Aaron Rankin]

John,

My key issue is that my application is hosted on shared
infrastructure. In addition to mine, other applications are hitting
the Search API from a common IP address. If there is a way to identify
my traffic from others', and only rate limit it if it's responsible,
that would solve it.

I am using a (hopefully) unique and meaningful user-agent.

Thanks,
Aaron

On Sep 23, 11:20 am, John Kalucki  wrote:
> TheSearchAPIis served from a totally different infrastructure 
> thanapi.twitter.com. As such, it has limits that are tuned to protecting a
> very different back-end. Even ifSearchwas served through theapi.twitter.com 
> stack, the policies would still be driven by the back-
> end.
>
> If you are hittingsearchAPIlimits, there's a good chance there is a
> better way to service your application. If you share your use case,
> perhaps we can point out a better way to get the same results?
>
> -John Kaluckihttp://twitter.com/jkalucki
> Services, Twitter Inc.
>
> On Sep 23, 8:41 am, Aaron Rankin  wrote:
>
> > I've seen talk of movingSearchAPIcalls into theRESTAPIfor a
> > while now. Twitter, are there any plans or dates that you can discuss
> > yet? Is this still planned at all?
>
> > This will be very useful to my application because ofREST'saccount-
> > based rate limiting. I'm constantly beingSearchrate limited because
> > I'm on Rackspace Cloud, sharing the same IP as other Twitter apps.

[twitter-dev] Search calls ever moving into REST API?

[Aaron Rankin]

I've seen talk of moving Search API calls into the REST API for a
while now. Twitter, are there any plans or dates that you can discuss
yet? Is this still planned at all?

This will be very useful to my application because of REST's account-
based rate limiting. I'm constantly being Search rate limited because
I'm on Rackspace Cloud, sharing the same IP as other Twitter apps.

[twitter-dev] Re: How to list followers, including icons and usernames?

[Aaron Rankin]

It looks like status/followers gets you part of the way there. First,
some questions for Twitter:

1) Does status/followers return statuses for distinct users? E.g., if
one of my followers has changed their status twice in the past minute,
will this method return the latest or both?
2) For every follower, will this definitely return the last status for
each, even if they've been idle for some time?

Since this returns statuses in batches of 100, to get all data for all
followers, you'll still to run a query for every 100 (including the
remainder at the end). At least in the JSON, status/followers doesn't
tell you how many followers there are. To know the number of queries
(pages of 100) to fetch, you also need to query followers/ids. It's
clearly better than 1 query per follower + 1 call to follower/ids for
the main user in question.

Is this the best way to get information for each follower of a given
user?


Thanks,
Aaron

On Jun 28, 12:41 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Check out this 
> method:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0f...
>
>
>
> On Sun, Jun 28, 2009 at 12:26, Bemmu wrote:
>
> > I'm wanting to do a friend selector that looks something like the
> > selector on Facebook, where the user sees a list of their followers'
> > names and icons, and can select some of them. Right now the only way I
> > can think of is first getting all IDs of followers from "/followers/
> > ids", and then calling "/users/show.json?user_id=" for each. Seems
> > expensive and slow.
>
> > What's the right way to do this? I see some apps have follower
> > selectors, but I don't know if they screen scrape "http://twitter.com/
> > followers/1401881", or do as I just described and simply not work for
> > people with too many followers.
>
> > My dream API method would allow sorting by name or follower count,
> > something like this:
>
> > Query: "/followers/list.json?sort=follower_count&page=1&per_page=1000"
> > Response:
> > [
> >  { 'id' : 12345, 'icon' : 'http://...somethingjpg', 'username' :
> > 'a' },
> >  { 'id' : 67890, 'icon' : 'http://...somethingjpg', 'username' :
> > 'b' },
> >  ...
> > ]
>
> > Since many users will probably have thousands of followers, I thought
> > I could ease the
>
> --
> 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.