[twitter-dev] problem in adding follow in twitter from my tool

[kiran kumar]

Hi,
 I getting problem is,i like to add bulk of followers but i not
that all followers adding.I worked on php by using cURL functions.and
i use add follower by using 
http://twitter.com/friendships/create.xml?screen_name="follower's
username".plz help to solve my problem.

  Thank u,

[twitter-dev] Re: Accessing twitter.com on Windows CE devices (not Windows Mobile)

[Andrew Badera]

If you're writing custom code, simply set the user-agent header yourself.

If you're stuck in IE6 for WinCE, and it's just you, I think there are
registry settings you can hack.

If you have wider distribution, you might be out of luck. I think this
issue has been raised previously however. A fix from Twitter would be
nice.

∞ 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 Wed, Oct 7, 2009 at 8:01 PM, NaileBrotte  wrote:
>
> Hi,
> I'm working on a device running Windows CE 6.0 / IE6 (not Windows
> Mobile 6), and when accessing www.twitter.com, I'm redirected to
> m.twitter.com (because the User Agent says "Windows CE"). The problem
> is that IE6 doesn't handle the login page that is being sent by the
> server because it's  marked as "application/xhtml+xml" which IE
> doesn't handle and just offers for download.
>
> Is there a way to access the standard page? Or browse a fixed URL that
> wouldn't redirect to the mobile page?
> There must be a few devices like that with that same problem.
>
> Maybe the parsing of the User Agent could be made a bit more specific
> about what has to be identified as a mobile.
>
> Thanks in advance.
> NB.
>
>
> wget -U "Windows CE" www.twitter.com
>
> --2009-10-08 11:46:33--  http://www.twitter.com/
> Resolving www.twitter.com... 168.143.161.20
> Connecting to www.twitter.com|168.143.161.20|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://twitter.com/ [following]
> --2009-10-08 11:46:33--  http://twitter.com/
> Resolving twitter.com... 168.143.161.20
> Reusing existing connection to www.twitter.com:80.
> HTTP request sent, awaiting response... 302 Found
> Cookie coming from twitter.com attempted to set domain to
> m.twitter.com
> Location: http://twitter.com/login [following]
> --2009-10-08 11:46:34--  http://twitter.com/login
> Reusing existing connection to www.twitter.com:80.
> HTTP request sent, awaiting response... 200 OK
> Length: 3404 (3.3K) [application/xhtml+xml]
> Saving to: `login'
>
>     0K ...                                                   100%
> 24.6K=0.1s
>
> 2009-10-08 11:46:34 (24.6 KB/s) - `login' saved [3404/3404]
>
>
>
>
> wget -U "Windows" www.twitter.com
>
> --2009-10-08 11:46:15--  http://www.twitter.com/
> Resolving www.twitter.com... 168.143.162.116
> Connecting to www.twitter.com|168.143.162.116|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://twitter.com/ [following]
> --2009-10-08 11:46:15--  http://twitter.com/
> Resolving twitter.com... 168.143.162.116
> Reusing existing connection to www.twitter.com:80.
> HTTP request sent, awaiting response... 200 OK
> Length: 21063 (21K) [text/html]
> Saving to: `index.html'
>
>     0K .. ..                                 100%
> 54.8K=0.4s
>
> 2009-10-08 11:46:21 (54.8 KB/s) - `index.html' saved [21063/21063]
>
>

[twitter-dev] Re: whitelisting process?

[Chad Etzel]

Hi Edwin,

The process can take up to a week, but it is usually sooner than that.
However, it seems like everyone and their brother now thinks they need
whitelisting for their use-case, so the number of applications per day
has been growing dramatically.

We'll get to it, have no fear.

-Chad

On Wed, Oct 7, 2009 at 7:43 PM, Edwin Khodabakchian
 wrote:
>
> Does anyone know how long it usually takes for the twitter team to
> approve or request a whitelisting (http://twitter.com/help/
> request_whitelisting) request?
>
> We are in the process of launching a new service and this is one of
> the last dependencies we are trying to resolve so any insight into the
> process would be very much appreciated.
>
> Thank you,
> Edwin
>
> ---
> http://www.feedly.com
>

[twitter-dev] Re: Case is wrong in GeoRSS

[stevenic]

no worries... it is a bit confusing... as I said I'm looking for both
in my code so either is ok.  But others are probably looking for
georss:Point so you may just want to send a notification when you
change it...

On Oct 7, 10:08 am, Raffi Krikorian  wrote:
> hi steve.
>
> you're right!  we should be using georss:point and not georss:Point!  
> the confusing thing is that in JSON, the type attribute of the  
> geometry object is "Point" and not "point".
>
> we'll ship a fix for that.  thanks!
>
>
>
>
>
>
>
> > You're currently sending Geo Tags as:
>
> >            http://www.georss.org/georss";>
> >                37.78029 -122.39697
> >            
>
> > But according to the schema for GeoRSS-Simple Point should be
> > lowercased:
>
> >      http://www.georss.org/simple
>
> > as in:
>
> >            http://www.georss.org/georss";>
> >                37.78029 -122.39697
> >            
>
> > The original example you posted to the form had the correct case but
> > what you actually rolled out is different.  Was there a reason for the
> > switch?
>
> > I've updated my code to look for uppercase Point for now...
>
> > -steve
>
> --
> Raffi Krikorian
> Twitter Platform Team
> ra...@twitter.com | @raffi- Hide quoted text -
>
> - Show quoted text -

[twitter-dev] Problem with Twitter show_user request

[ArnieLapinig]

Hello,

Hello,

Just started developing a Twitter app... I'm using a php script with
CURL to issue a show_user request. The twitter_id in the request comes
from the response from a search method, which returns xml data.
I use the twitter_id in show.xml to get the user's location info.
But I'm getting this response:

Warning: file_get_contents(
  /users/show.xml?user_id=4667006333
Not found  ) [function.file-get-contents]:
failed to open stream: No such file or directory.

Does Twitter still allow Basic Authorization? Do I have to register an
app with Twitter in order to get a valid response when using the REST
API?

Thanks for helping out...

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[thomas cavanaugh]

your hunch appears right;;there is an undisclosed network(s) problem that so
far the powers to be are "reluctant?? to publish

On Wed, Oct 7, 2009 at 11:11 PM, Panu Tangchalermkul wrote:

>
> Thanks for all the follow up, guys. I tested this scenario on several
> machine in my home after I posted the above question, and it's weird
> that ALL experiencing the same thing.
>
> I tested it on 1 Windows XP PC, 1 Windows XP laptop, 1 Windows XP
> virtual machine. On both Firefox and IE.
>
> Now I can't think of anything but a network problem, but how is it
> possible?
>
>
> On Oct 8, 5:17 am, stephane  wrote:
> > The problem I usually (systematically in fact) encounter is that if
> > 1 / I start a oauth process (go to the oauth login page on twitter)
> > from a 3rd party app (say "myoauthapp")
> > 2 / I don't click neither "accept" nor "deny" and just close the
> > window (or tab),
> > -> when I sign-in on twitter, instead of being forwarded to my
> > home_timeline, I'm brought to the Oauth accept page for the 3rd party
> > app "myoauthapp".
> >
> > I think this (buggy) behavior has already been reported on this group
> > several weeks ago
> >
> > Stephane
> > @sphilipakishttp://twazzup.com
>  >
> > On Oct 7, 9:59 pm, Michael Steuer  wrote:
> >
> > > I¹m not angry. This is however a mailing list about Twitter
> development, and
> > > Panu is posing what seems like a legitimate question relating to
> Twitter
> > > development. Sending SPAM as original messages as one thing and would
> be
> > > ignored by everyone, sending spam in response to legitimate
> > > questions/threads is another, and probably especially frustrating for
> the
> > > person trying to get an answer to a question, in this case Panu.
> >
> > > Anyway, just my 2 cents.
> >
> > > Panu ­ I tried to reproduce that issue on my machine, but wasn¹t able
> too.
> > > Perhaps someone else can weigh in with a response that¹s not about disk
> > > defragmentation ;)
> >
> > > On 10/7/09 12:39 PM, "JDG"  wrote:
> >
> > > > it didn't waste a ms of my time. it only wasted your time by
> responding. why
> > > > do people get so angry about things they see on the internet? it's
> the easiest
> > > > thing on the planet to ignore.
> >
> > > > On Wed, Oct 7, 2009 at 13:17, Michael Steuer 
> wrote:
> > > >> Is this a joke? Why waste 100s of people¹s time?!
> >
> > > >> On 10/7/09 10:10 AM, "thomas cavanaugh"  > > >>  > wrote:
> >
> > > >>> windows 98 and above 1 reboot 2 open"computer" go to storage drives
> click on
> > > >>> properities.,  click on defrag or clear button defrag or clear
> NONESSENTIALS
> > > >>> FROM THAT DRIVE.,reboot again  if this doesnt  solve the problem
> consult
> > > >>> microsoft especially if it is windows vista operating system .there
> is an
> > > >>> internal "conflict" between downloaded soft ware on your unit
> probably
> > > >>> conflicting security programs.,, be patient let me know how you
> make out
> > > >>> t.
> >
> > > >>> On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul <
> pan...@gmail.com
> > > >>>  > wrote:
> >
> > >  I have tested this on 2 Twitter OAuth demo site,
> >
> > > http://twitteroauth.appspot.com/
> > > http://fourmargins.com/labs/twitter_oauth/
> >
> > >  by using Firefox 3.5 and Internet Explorer 8 on Windows Vista
> 32bit
> >
> > >  Every time after I ignore (close without any action on the page)
> > >  Twitter OAuth application authorization page (the page that has
> Allow
> > >  and Deny button), I cannot load any page that using Twitter OAuth
> API
> > >  including Twitter own login system.
> >
> > >  To describe in step-by-step, I open one of the above OAuth demo
> > >  website, click on the link that will give the application an
> access to
> > >  my twitter account, a browser redirect me to twitter page that
> require
> > >  me to choose Allow or Deny, I choose to ignore it and close that
> page.
> > >  Then I regret my action and try to open it again, I have
> encountered
> > >  "The connection was reset" on Firefox 3.5 and "Internet Explorer
> > >  cannot display the webpage" on IE, after I have clicked the same
> link.
> >
> > >  I don't know why but it seems "deleting all cookies" is an only
> > >  resolution. This is reproducible every times on my machine.
> >
> > >  OAuth BUG?
>

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[Panu Tangchalermkul]

Thanks for all the follow up, guys. I tested this scenario on several
machine in my home after I posted the above question, and it's weird
that ALL experiencing the same thing.

I tested it on 1 Windows XP PC, 1 Windows XP laptop, 1 Windows XP
virtual machine. On both Firefox and IE.

Now I can't think of anything but a network problem, but how is it
possible?


On Oct 8, 5:17 am, stephane  wrote:
> The problem I usually (systematically in fact) encounter is that if
> 1 / I start a oauth process (go to the oauth login page on twitter)
> from a 3rd party app (say "myoauthapp")
> 2 / I don't click neither "accept" nor "deny" and just close the
> window (or tab),
> -> when I sign-in on twitter, instead of being forwarded to my
> home_timeline, I'm brought to the Oauth accept page for the 3rd party
> app "myoauthapp".
>
> I think this (buggy) behavior has already been reported on this group
> several weeks ago
>
> Stephane
> @sphilipakishttp://twazzup.com
>
> On Oct 7, 9:59 pm, Michael Steuer  wrote:
>
> > I¹m not angry. This is however a mailing list about Twitter development, and
> > Panu is posing what seems like a legitimate question relating to Twitter
> > development. Sending SPAM as original messages as one thing and would be
> > ignored by everyone, sending spam in response to legitimate
> > questions/threads is another, and probably especially frustrating for the
> > person trying to get an answer to a question, in this case Panu.
>
> > Anyway, just my 2 cents.
>
> > Panu ­ I tried to reproduce that issue on my machine, but wasn¹t able too.
> > Perhaps someone else can weigh in with a response that¹s not about disk
> > defragmentation ;)
>
> > On 10/7/09 12:39 PM, "JDG"  wrote:
>
> > > it didn't waste a ms of my time. it only wasted your time by responding. 
> > > why
> > > do people get so angry about things they see on the internet? it's the 
> > > easiest
> > > thing on the planet to ignore.
>
> > > On Wed, Oct 7, 2009 at 13:17, Michael Steuer  wrote:
> > >> Is this a joke? Why waste 100s of people¹s time?!
>
> > >> On 10/7/09 10:10 AM, "thomas cavanaugh"  > >>  > wrote:
>
> > >>> windows 98 and above 1 reboot 2 open"computer" go to storage drives 
> > >>> click on
> > >>> properities.,  click on defrag or clear button defrag or clear 
> > >>> NONESSENTIALS
> > >>> FROM THAT DRIVE.,reboot again  if this doesnt  solve the problem consult
> > >>> microsoft especially if it is windows vista operating system .there is 
> > >>> an
> > >>> internal "conflict" between downloaded soft ware on your unit  probably
> > >>> conflicting security programs.,, be patient let me know how you make 
> > >>> out  
> > >>> t.
>
> > >>> On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul  > >>>  > wrote:
>
> >  I have tested this on 2 Twitter OAuth demo site,
>
> > http://twitteroauth.appspot.com/
> > http://fourmargins.com/labs/twitter_oauth/
>
> >  by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit
>
> >  Every time after I ignore (close without any action on the page)
> >  Twitter OAuth application authorization page (the page that has Allow
> >  and Deny button), I cannot load any page that using Twitter OAuth API
> >  including Twitter own login system.
>
> >  To describe in step-by-step, I open one of the above OAuth demo
> >  website, click on the link that will give the application an access to
> >  my twitter account, a browser redirect me to twitter page that require
> >  me to choose Allow or Deny, I choose to ignore it and close that page.
> >  Then I regret my action and try to open it again, I have encountered
> >  "The connection was reset" on Firefox 3.5 and "Internet Explorer
> >  cannot display the webpage" on IE, after I have clicked the same link.
>
> >  I don't know why but it seems "deleting all cookies" is an only
> >  resolution. This is reproducible every times on my machine.
>
> >  OAuth BUG?

[twitter-dev] Re: Updates to the retweet API payload

[Zaudio]

We use JSON thoughout... as JSON and also parsing to db fields... I
love that JSON converts directly to OO but then again what works
for one app, may hinder others... no ideal solution.

I suspect that things will stay as they are anyway... so your our app
lose on this one and will just have to do more during our to db
parsing operations ...

Simon

On Oct 7, 7:52 am, Marco Kaiser  wrote:
> Well, you're not making use of JSON as JSON, and instead use "brute-force"
> methods to extract parts of it... I think it's a bit unfair to request that
> change to be made, as it would complicate things for everyone doing "real"
> JSON-to-OO mapping. Just my 2c.
>
> And no, retweet_status is perfectly valid - it's the property name in a
> status model, and it is assigned a status data model. Just a nested object.
> You don't have to name a member "status" just because it is a Status data
> type...
>
> Marco
>
> 2009/10/7 Zaudio 
>
>
>
>
>
> > Sure, I'll justify this mroe...
>
> > One of our apps receives updates via the Streaming API and the various
> > REST api methods (mentions, user timelines, friends/home timelines).
> > We collect data as JSON as it's to date been faster and mor compact
> > than alternatives... we can also then go on to use this directly
> > client side in Jscript if we wish...
> > We are caching all updates of interest in a db... thus parse them for
> > the required data fields before storing them there. Currently the
> > parser has to pull out the user node, and is then left with the root
> > status node it is then simple to parse the separated nodes for all
> > fields pertinant to the current operation.
> > We make quick checks initially to determine the relevance of the
> > message to the app's cached stream we want to check things like
> > JUST created_at for the status (and not user) and then check the text
> > property for certain markers.
> > It is easy to find these efficiently in a JSON string without parsing
> > the entire thing to objects as things stand... so we save a lot of
> > server cpu cycles. It's fastest to this from the inner node
> > outwards... this is where the 'wasted' cpu cycles are coming in here
> > with the change for retweeted_status
> > Status's of interest only have the further fields parsed that we want
> > for out db copy...
>
> > for example.. say you want to quickly check the id of the status to
> > confirm if you have it in you db already or not... currently we just
> > excluded the user node, and thent he id is in the remainder without
> > conflict.
>
> > Now add retweeted_status with it's user subnode
>
> > To now get the id of the root status without parsing the entire string
> > to objects... we pull it apart again from the inner node outwards...
> > we now need to exclude the retweeted_status user subnode... this no
> > longer has a unique start tag/definition... as there are TWO identical
> > start tags in the string so we do a lot more work to ensure we get
> > the retweeted_status and it's user node that we would if it had an
> > alternative start tag.
> > If it were instead retweeted_user, then we could extract that directly
> > and easily, exclude it, then exclude the surrounding retweeted_status
> > tag... and we've got the retweeted_status node separated... then we
> > can procede as we do now with the rest... and if necessary use the
> > retweeted_status as well.
>
> > Hope that makes sense
> > I agree that keeping it as user also makes good object sense... but
> > then the retweeted_status is not 'status' anymore... and it is a
> > status I'm suggesting soemthing similar for it's inner node..
>
> > Simon (Zaudio)
>
> > On Oct 6, 12:01 pm, Marco Kaiser  wrote:
> > > No, please don't change that to retweeted_user ... the data structure
> > > included as the retweeted status is a status, and that data structure has
> > a
> > > user property. That's a very clear object model, and should map very well
> > to
> > > JSON, as it's nested, not at the same level as the main user the retweet
> > is
> > > received from. So by doing that change, you'd break the data model for a
> > > status, in that there are two version that need to be taken care of.
>
> > > Or can you explain in more depth why this would cause problems with
> > > reasonable JSON parsers that map strings to objects?
>
> > > 2009/10/6 Zaudio 
>
> > > > Another significant thought... could you 'please' consider changing
> > > > the name of the  node INSIDE the retweeted_status node to say
> > > >  ?
>
> > > > Thius will make JSON parsing way simpler... especially if the goal is
> > > > to extract the retweeted_status when present; or do things like
> > > > quickly find the date of the tweet... I alreayd have to contend with a
> > > > created_at field in the user and status nodes... now that could double
> > > > up... so owuld appreciate an easier to find retweeted user node for
> > > > JSON parsability
>
> > > > Thanks
>
> > > > Simon (Zaudio)
>
> > > > On Oct 4, 8:16 a

[twitter-dev] Accessing twitter.com on Windows CE devices (not Windows Mobile)

[NaileBrotte]

Hi,
I'm working on a device running Windows CE 6.0 / IE6 (not Windows
Mobile 6), and when accessing www.twitter.com, I'm redirected to
m.twitter.com (because the User Agent says "Windows CE"). The problem
is that IE6 doesn't handle the login page that is being sent by the
server because it's  marked as "application/xhtml+xml" which IE
doesn't handle and just offers for download.

Is there a way to access the standard page? Or browse a fixed URL that
wouldn't redirect to the mobile page?
There must be a few devices like that with that same problem.

Maybe the parsing of the User Agent could be made a bit more specific
about what has to be identified as a mobile.

Thanks in advance.
NB.


wget -U "Windows CE" www.twitter.com

--2009-10-08 11:46:33--  http://www.twitter.com/
Resolving www.twitter.com... 168.143.161.20
Connecting to www.twitter.com|168.143.161.20|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://twitter.com/ [following]
--2009-10-08 11:46:33--  http://twitter.com/
Resolving twitter.com... 168.143.161.20
Reusing existing connection to www.twitter.com:80.
HTTP request sent, awaiting response... 302 Found
Cookie coming from twitter.com attempted to set domain to
m.twitter.com
Location: http://twitter.com/login [following]
--2009-10-08 11:46:34--  http://twitter.com/login
Reusing existing connection to www.twitter.com:80.
HTTP request sent, awaiting response... 200 OK
Length: 3404 (3.3K) [application/xhtml+xml]
Saving to: `login'

 0K ...   100%
24.6K=0.1s

2009-10-08 11:46:34 (24.6 KB/s) - `login' saved [3404/3404]




wget -U "Windows" www.twitter.com

--2009-10-08 11:46:15--  http://www.twitter.com/
Resolving www.twitter.com... 168.143.162.116
Connecting to www.twitter.com|168.143.162.116|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://twitter.com/ [following]
--2009-10-08 11:46:15--  http://twitter.com/
Resolving twitter.com... 168.143.162.116
Reusing existing connection to www.twitter.com:80.
HTTP request sent, awaiting response... 200 OK
Length: 21063 (21K) [text/html]
Saving to: `index.html'

 0K .. .. 100%
54.8K=0.4s

2009-10-08 11:46:21 (54.8 KB/s) - `index.html' saved [21063/21063]

[twitter-dev] whitelisting process?

[Edwin Khodabakchian]

Does anyone know how long it usually takes for the twitter team to
approve or request a whitelisting (http://twitter.com/help/
request_whitelisting) request?

We are in the process of launching a new service and this is one of
the last dependencies we are trying to resolve so any insight into the
process would be very much appreciated.

Thank you,
Edwin

---
http://www.feedly.com

[twitter-dev] At Symbol (@) in Twitter Search

[Nick]

The at symbol (@) does not seem to work when searching tweets.  When
the @ symbol is alone (surrounded by nothing or whitespace) in a
search, the search returns 0 English results.  Sometimes languages
that use non-ascii characters seem to be found.  However, when the @
is followed by at least 1 alphanumeric character, the query seems to
work fine.

I found this by searching for "@ the diner downtown", and I was
getting back 0 results, but at least 1 results should have been
returned, because that's what I tweeted.  This probably affects
searches for mentions too, because you can't just search for "@".

I've used the web site and the search API:
http://twitter.com/#search?q=%40
http://search.twitter.com/search.atom?q=%40

Has anyone gotten a query to work with @ standing alone?  This there a
different way to perform the same search?

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[stephane]

The problem I usually (systematically in fact) encounter is that if
1 / I start a oauth process (go to the oauth login page on twitter)
from a 3rd party app (say "myoauthapp")
2 / I don't click neither "accept" nor "deny" and just close the
window (or tab),
-> when I sign-in on twitter, instead of being forwarded to my
home_timeline, I'm brought to the Oauth accept page for the 3rd party
app "myoauthapp".

I think this (buggy) behavior has already been reported on this group
several weeks ago

Stephane
@sphilipakis
http://twazzup.com

On Oct 7, 9:59 pm, Michael Steuer  wrote:
> I¹m not angry. This is however a mailing list about Twitter development, and
> Panu is posing what seems like a legitimate question relating to Twitter
> development. Sending SPAM as original messages as one thing and would be
> ignored by everyone, sending spam in response to legitimate
> questions/threads is another, and probably especially frustrating for the
> person trying to get an answer to a question, in this case Panu.
>
> Anyway, just my 2 cents.
>
> Panu ­ I tried to reproduce that issue on my machine, but wasn¹t able too.
> Perhaps someone else can weigh in with a response that¹s not about disk
> defragmentation ;)
>
> On 10/7/09 12:39 PM, "JDG"  wrote:
>
> > it didn't waste a ms of my time. it only wasted your time by responding. why
> > do people get so angry about things they see on the internet? it's the 
> > easiest
> > thing on the planet to ignore.
>
> > On Wed, Oct 7, 2009 at 13:17, Michael Steuer  wrote:
> >> Is this a joke? Why waste 100s of people¹s time?!
>
> >> On 10/7/09 10:10 AM, "thomas cavanaugh"  >>  > wrote:
>
> >>> windows 98 and above 1 reboot 2 open"computer" go to storage drives click 
> >>> on
> >>> properities.,  click on defrag or clear button defrag or clear 
> >>> NONESSENTIALS
> >>> FROM THAT DRIVE.,reboot again  if this doesnt  solve the problem consult
> >>> microsoft especially if it is windows vista operating system .there is an
> >>> internal "conflict" between downloaded soft ware on your unit  probably
> >>> conflicting security programs.,, be patient let me know how you make out  
> >>> t.
>
> >>> On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul  >>>  > wrote:
>
>  I have tested this on 2 Twitter OAuth demo site,
>
> http://twitteroauth.appspot.com/
> http://fourmargins.com/labs/twitter_oauth/
>
>  by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit
>
>  Every time after I ignore (close without any action on the page)
>  Twitter OAuth application authorization page (the page that has Allow
>  and Deny button), I cannot load any page that using Twitter OAuth API
>  including Twitter own login system.
>
>  To describe in step-by-step, I open one of the above OAuth demo
>  website, click on the link that will give the application an access to
>  my twitter account, a browser redirect me to twitter page that require
>  me to choose Allow or Deny, I choose to ignore it and close that page.
>  Then I regret my action and try to open it again, I have encountered
>  "The connection was reset" on Firefox 3.5 and "Internet Explorer
>  cannot display the webpage" on IE, after I have clicked the same link.
>
>  I don't know why but it seems "deleting all cookies" is an only
>  resolution. This is reproducible every times on my machine.
>
>  OAuth BUG?

[twitter-dev] Re: Streaming API Rate Limit Question

[John Kalucki]

Yes to two different accounts for sampling and filtering.

You can filter by keyword (track) and userid (follow) on the same
connection. Their limits don't interfere with each other. We encourage
this behavior, as our cost is somewhat vaguely aligned with the number
of connections and the rate of connections.

The only downside is that you can't, currently, get elevated access
for both on the same connection. We can bump track, which leaves
follow at the default level, or we can bump follow, but track is at
the default level. If this becomes and issue, we'll create some hybrid
access levels.

The default level is currently pretty generous, most applications
don't need anything more.

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Oct 7, 2:04 pm, Damon C  wrote:
> I've got a quick question on the rate limiting of the streaming API.
> The documentation states the following:
>
> "Each account may create only one standing connection to the Streaming
> API."
>
> Does this mean that I have to use two separate accounts if I want to
> connect to both statuses/sample and statuses/filter?
>
> Similarly, do I have to use separate accounts if I want to access both
> the track and follow predicates of the filter stream?
>
> I'm assuming the answer is yes, but I just wanted to verify.
>
> Thanks,
>
> dpc

[twitter-dev] Streaming API Rate Limit Question

[Damon C]

I've got a quick question on the rate limiting of the streaming API.
The documentation states the following:

"Each account may create only one standing connection to the Streaming
API."

Does this mean that I have to use two separate accounts if I want to
connect to both statuses/sample and statuses/filter?

Similarly, do I have to use separate accounts if I want to access both
the track and follow predicates of the filter stream?

I'm assuming the answer is yes, but I just wanted to verify.

Thanks,

dpc

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[Michael Steuer]

I¹m not angry. This is however a mailing list about Twitter development, and
Panu is posing what seems like a legitimate question relating to Twitter
development. Sending SPAM as original messages as one thing and would be
ignored by everyone, sending spam in response to legitimate
questions/threads is another, and probably especially frustrating for the
person trying to get an answer to a question, in this case Panu.

Anyway, just my 2 cents.

Panu ­ I tried to reproduce that issue on my machine, but wasn¹t able too.
Perhaps someone else can weigh in with a response that¹s not about disk
defragmentation ;)


On 10/7/09 12:39 PM, "JDG"  wrote:

> it didn't waste a ms of my time. it only wasted your time by responding. why
> do people get so angry about things they see on the internet? it's the easiest
> thing on the planet to ignore.
> 
> On Wed, Oct 7, 2009 at 13:17, Michael Steuer  wrote:
>> Is this a joke? Why waste 100s of people¹s time?!
>> 
>> 
>> 
>> On 10/7/09 10:10 AM, "thomas cavanaugh" >  > wrote:
>> 
>>> windows 98 and above 1 reboot 2 open"computer" go to storage drives click on
>>> properities.,  click on defrag or clear button defrag or clear NONESSENTIALS
>>> FROM THAT DRIVE.,reboot again  if this doesnt  solve the problem consult
>>> microsoft especially if it is windows vista operating system .there is an
>>> internal "conflict" between downloaded soft ware on your unit  probably
>>> conflicting security programs.,, be patient let me know how you make out  
>>> t.
>>> 
>>> On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul >>  > wrote:
 
 I have tested this on 2 Twitter OAuth demo site,
 
 http://twitteroauth.appspot.com/
 http://fourmargins.com/labs/twitter_oauth/
 
 by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit
 
 Every time after I ignore (close without any action on the page)
 Twitter OAuth application authorization page (the page that has Allow
 and Deny button), I cannot load any page that using Twitter OAuth API
 including Twitter own login system.
 
 To describe in step-by-step, I open one of the above OAuth demo
 website, click on the link that will give the application an access to
 my twitter account, a browser redirect me to twitter page that require
 me to choose Allow or Deny, I choose to ignore it and close that page.
 Then I regret my action and try to open it again, I have encountered
 "The connection was reset" on Firefox 3.5 and "Internet Explorer
 cannot display the webpage" on IE, after I have clicked the same link.
 
 I don't know why but it seems "deleting all cookies" is an only
 resolution. This is reproducible every times on my machine.
 
 OAuth BUG?
>>> 
>>> 
> 
> 

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[JDG]

it didn't waste a ms of my time. it only wasted your time by responding. why
do people get so angry about things they see on the internet? it's the
easiest thing on the planet to ignore.

On Wed, Oct 7, 2009 at 13:17, Michael Steuer  wrote:

>  Is this a joke? Why waste 100s of people’s time?!
>
>
>
> On 10/7/09 10:10 AM, "thomas cavanaugh"  wrote:
>
> windows 98 and above 1 reboot 2 open"computer" go to storage drives click
> on properities.,  click on defrag or clear button defrag or clear
> NONESSENTIALS FROM THAT DRIVE.,reboot again  if this doesnt  solve the
> problem consult microsoft especially if it is windows vista operating system
> .there is an internal "conflict" between downloaded soft ware on your unit
> probably conflicting security programs.,, be patient let me know how you
> make out   t.
>
> On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul 
> wrote:
>
>
> I have tested this on 2 Twitter OAuth demo site,
>
> http://twitteroauth.appspot.com/
> http://fourmargins.com/labs/twitter_oauth/
>
> by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit
>
> Every time after I ignore (close without any action on the page)
> Twitter OAuth application authorization page (the page that has Allow
> and Deny button), I cannot load any page that using Twitter OAuth API
> including Twitter own login system.
>
> To describe in step-by-step, I open one of the above OAuth demo
> website, click on the link that will give the application an access to
> my twitter account, a browser redirect me to twitter page that require
> me to choose Allow or Deny, I choose to ignore it and close that page.
> Then I regret my action and try to open it again, I have encountered
> "The connection was reset" on Firefox 3.5 and "Internet Explorer
> cannot display the webpage" on IE, after I have clicked the same link.
>
> I don't know why but it seems "deleting all cookies" is an only
> resolution. This is reproducible every times on my machine.
>
> OAuth BUG?
>
>
>
>


-- 
Internets. Serious business.

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[Michael Steuer]

Is this a joke? Why waste 100s of people¹s time?!


On 10/7/09 10:10 AM, "thomas cavanaugh"  wrote:

> windows 98 and above 1 reboot 2 open"computer" go to storage drives click on
> properities.,  click on defrag or clear button defrag or clear NONESSENTIALS
> FROM THAT DRIVE.,reboot again  if this doesnt  solve the problem consult
> microsoft especially if it is windows vista operating system .there is an
> internal "conflict" between downloaded soft ware on your unit  probably
> conflicting security programs.,, be patient let me know how you make out   t.
> 
> On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul  wrote:
>> 
>> I have tested this on 2 Twitter OAuth demo site,
>> 
>> http://twitteroauth.appspot.com/
>> http://fourmargins.com/labs/twitter_oauth/
>> 
>> by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit
>> 
>> Every time after I ignore (close without any action on the page)
>> Twitter OAuth application authorization page (the page that has Allow
>> and Deny button), I cannot load any page that using Twitter OAuth API
>> including Twitter own login system.
>> 
>> To describe in step-by-step, I open one of the above OAuth demo
>> website, click on the link that will give the application an access to
>> my twitter account, a browser redirect me to twitter page that require
>> me to choose Allow or Deny, I choose to ignore it and close that page.
>> Then I regret my action and try to open it again, I have encountered
>> "The connection was reset" on Firefox 3.5 and "Internet Explorer
>> cannot display the webpage" on IE, after I have clicked the same link.
>> 
>> I don't know why but it seems "deleting all cookies" is an only
>> resolution. This is reproducible every times on my machine.
>> 
>> OAuth BUG?
> 
> 

[twitter-dev] twitter.com/followers/befriend_all ?

[Rick Yazwinski]

I see comments via google about having a bot call this regularily to
make sure your bot follows anyone following the bot... makes sense
(rather than getting all friends and all followers and issuing
seperate friend requests), however I see no reference to it on the
twitter api site.

Is this legit?

When I call it it just redirects to my home page.

Rick...

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

[thomas cavanaugh]

windows 98 and above 1 reboot 2 open"computer" go to storage drives click on
properities.,  click on defrag or clear button defrag or clear NONESSENTIALS
FROM THAT DRIVE.,reboot again  if this doesnt  solve the problem consult
microsoft especially if it is windows vista operating system .there is an
internal "conflict" between downloaded soft ware on your unit  probably
conflicting security programs.,, be patient let me know how you make out
t.

On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul wrote:

>
> I have tested this on 2 Twitter OAuth demo site,
>
> http://twitteroauth.appspot.com/
> http://fourmargins.com/labs/twitter_oauth/
>
> by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit
>
> Every time after I ignore (close without any action on the page)
> Twitter OAuth application authorization page (the page that has Allow
> and Deny button), I cannot load any page that using Twitter OAuth API
> including Twitter own login system.
>
> To describe in step-by-step, I open one of the above OAuth demo
> website, click on the link that will give the application an access to
> my twitter account, a browser redirect me to twitter page that require
> me to choose Allow or Deny, I choose to ignore it and close that page.
> Then I regret my action and try to open it again, I have encountered
> "The connection was reset" on Firefox 3.5 and "Internet Explorer
> cannot display the webpage" on IE, after I have clicked the same link.
>
> I don't know why but it seems "deleting all cookies" is an only
> resolution. This is reproducible every times on my machine.
>
> OAuth BUG?
>

[twitter-dev] Re: API for marking tweets seen

[Josh Roesslein]

Yes that would be a nice feature to have. A simple true/false value in
the status payload marking it read/unread
would do just fine. Also having an API endpoint to toggle this would
also be nice for marking statuses as unread/read.

Josh

On Wed, Oct 7, 2009 at 6:32 AM, Theyagarajan S  wrote:
> Hello,
>
> As someone who uses tweetdeck,web and my mobile client i would think if
> there was  a way an app would know if the tweet was already seen by a
> user.One way i could think of is knowing/storing the least tweet (by
> timestamp) that was fetched by user with API/web, and any app that user will
> first fetch the last seen tweet time and request only tweet stream after the
> time.
>
> Has anyone else felt the need for this?
>
> Thanks
> Taggy
>



-- 
Josh

[twitter-dev] Re: Search API Rate limiting - App Engine (again)

[Josh Roesslein]

Twitter should really in this case either white list all GAE IPs (I'm
sure an email to Google could get all IPs they use) or allow charging
API requests to an authenticated account rather than by IP (much like
the REST API does). This way each GAE application would just set up a
twitter account and each gets its own 150 request per hour.

Josh

[twitter-dev] Re: API for marking tweets seen

[Sean P.]

I agree. I use multiple clients throughout the day and the ability to
know where I left off is a huge plus so that I don't have to
"memorize" what the last tweet I read was (especially if its been a
while). Although it would be a bit difficult and can turn into a
nightmare for the website. For example, with email, we must list all
our email and if we have a lot of people emailing us (this is
equivalent to people we follow), we end up with a backlog that we must
go through and mark everything read by hand (or select all then mark
as read). It can make things a little overwhelming, unless they are
automatically marked as read once you log out (fetch only those since
the last login).

On Oct 7, 4:32 am, Theyagarajan S  wrote:
> Hello,
>
> As someone who uses tweetdeck,web and my mobile client i would think if
> there was  a way an app would know if the tweet was already seen by a
> user.One way i could think of is knowing/storing the least tweet (by
> timestamp) that was fetched by user with API/web, and any app that user will
> first fetch the last seen tweet time and request only tweet stream after the
> time.
>
> Has anyone else felt the need for this?
>
> Thanks
> Taggy

[twitter-dev] Re: Search API Rate limiting - App Engine (again)

[Aid]

I am also facing this issue.  I'm only making a couple of requests
from GAE (about 3-4) and none of them are getting through,   I keep
getting the following using Twitter4J

Twitter Exception while retrieving status
twitter4j.TwitterException: 400:The request was invalid.  An
accompanying error message will explain why. This is the status code
will be returned during rate limiting.


  /statuses/show/2.xml
  Rate limit exceeded. Clients may not make more than 150
requests per hour.



On Oct 6, 7:13 pm, Paul Kinlan  wrote:
> Hi Chad,
>
> I am sorry but that doesn't even help in the slightest.
>
> You are essentially saying that we shouldn't develop on the App
> Engine, since would now have to also buy a proxy.  Which is completely
> unfeasible and defeats the purpose of why people are using the app
> engine.
>
> I understand that this might also be an App Engine issue - for
> instance they could have reduced the number of IP addresses they pool
> from to make external requests.
>
> This is a very noticeable change inratelimiting in the last few
> weeks.  For instance I could run roughly 2 searches a second, then all
> of a sudden I would be lucky to run 2 every 15 seconds.  User-Agent
> strings were supposed to allievate this issue.  There are more than
> enough pieces of meta data on an App Engine request that Identify the
> exact application that is making the requests - I guess it is too much
> effort to take these into account.
>
> I am in the fortunate position that allowed me to set up a nginx proxy
> quickly, but I suspect a lot of other people couldn't do that.
>
> I hope something can be sorted for the large number of GAE based
> Twitter apps.
>
> Paul Kinlan
>
> On 6 Oct 2009, at 17:50, Chad Etzel  wrote:
>
>
>
> > Hi All,
>
> > GAE sites are problematic for the Twitter/Search API because the IPs
> > making outgoing requests are fluid and cannot as such be easily
> > allowed for access. Also, since most IPs are shared, other
> > applications on the same IPs making requests mean that fewer requests
> > per app get through.
>
> > One work around would be to spin up a server in EC2 or Rackspace Cloud
> > or something and use it as a proxy for your requests. That way you
> > have a dedicated IP that will have its full share of resources talking
> > with the Twitter servers.
>
> > HTH,
> > -Chad
>
> > On Tue, Oct 6, 2009 at 12:45 PM, Martin Omander
> >  wrote:
>
> >> Same here; my app runs on Google App Engine and 40% of the requests
> >> to
> >> the Twitter Search API get the 503 error message indicatingrate
> >> limiting.
>
> >> Is there anything we as app authors can do on our side to alleviate
> >> the problem?
>
> >> /Martin
>
> >> On Oct 5, 1:53 pm, Paul Kinlan  wrote:
> >>> I am pretty sure there are custom headers on the App Engine that
> >>> indicate
> >>> the application that is sending the request.
>
> >>> 2009/10/5 elkelk 
>
>  Hi all,
>
>  I am having the same issue.  I have tried setting a custom user-
>  agent,
>  but this doesn't seem to affect the fact that twitter is limiting
>  based on I.P. address.  I'm only making about 5 searches an hour
>  and
>  80% of them are failing on app engine due to a 503ratelimit.
>  Twitter needs to determine a better way to let cloud clients access
>  their search API.  It seems like they have really started blocking
>  search requests in the last week or so.
>
>  If anyone has any idea about how to better identify my app engine
>  app
>  please let let me know.
>
>  On Oct 5, 2:59 am, steel  wrote:
> > Hi. I have this problem too.
> > My application does two request per hour and it get "ratelimit".
> > What is wrong? I think it is twitter's problems
>
> > On 1 окт, 01:45, Paul Kinlan  wrote:
>
> >> Hi Guys,
> >> I have an app on the App engine using the search API and it is
> >> getting
> >> heavilyratelimited again this past couple of days.
>
> >> I know that we are on a shared set of IP addresses and someone
> >> else
>  could be
> >> hammering the system, but it seems to run for weeks without
> >> seeing the
> rate
> >>limitbeing hit and then all of a sudden only about 60% of the
> >> searches
> >> I perform will beratelimited.  This seems to occur every two
> >> months
>  or so.
>
> >> Has something changed recently?
>
> >> Paul

[twitter-dev] Re: Case is wrong in GeoRSS

[Raffi Krikorian]

hi steve.

you're right!  we should be using georss:point and not georss:Point!   
the confusing thing is that in JSON, the type attribute of the  
geometry object is "Point" and not "point".


we'll ship a fix for that.  thanks!



You're currently sending Geo Tags as:

   http://www.georss.org/georss";>
   37.78029 -122.39697
   

But according to the schema for GeoRSS-Simple Point should be
lowercased:

 http://www.georss.org/simple

as in:

   http://www.georss.org/georss";>
   37.78029 -122.39697
   

The original example you posted to the form had the correct case but
what you actually rolled out is different.  Was there a reason for the
switch?

I've updated my code to look for uppercase Point for now...

-steve


--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi

[twitter-dev] Ignoring OAuth application authorization page once causes following pages not be able to load up

[Panu Tangchalermkul]

I have tested this on 2 Twitter OAuth demo site,

http://twitteroauth.appspot.com/
http://fourmargins.com/labs/twitter_oauth/

by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit

Every time after I ignore (close without any action on the page)
Twitter OAuth application authorization page (the page that has Allow
and Deny button), I cannot load any page that using Twitter OAuth API
including Twitter own login system.

To describe in step-by-step, I open one of the above OAuth demo
website, click on the link that will give the application an access to
my twitter account, a browser redirect me to twitter page that require
me to choose Allow or Deny, I choose to ignore it and close that page.
Then I regret my action and try to open it again, I have encountered
"The connection was reset" on Firefox 3.5 and "Internet Explorer
cannot display the webpage" on IE, after I have clicked the same link.

I don't know why but it seems "deleting all cookies" is an only
resolution. This is reproducible every times on my machine.

OAuth BUG?

[twitter-dev] How to update the "What are you doing?" section.

[mariadanmark]

Hi
I have, on several trys, not been able to update my "What are you
doing?" section.
Does anyone have an idea why?
Thanks
Therese

[twitter-dev] Re: Twitter, Please Explain How Cursors Work

[John Kalucki]

First you have to assume no changes to the set. Users with any
significant following will see constant churn. Factoring out natural
churn then:

Ideally, the results are the same. Practically, the results are the
same. In a very few corner cases they are not. For the next several
weeks, for edges that were created over ~2 weeks ago, there will be,
very very rarely, issues with cursor jitter: In theory and in practice
there will be some over-delivery -- the last userid, or so, in a block
may be duplicated in the first rows a subsequent block. In theory
there might be similar under-delivery, but we haven't found an actual
case of under-delivery yet. You may need to deduplicate your results
if your app is very sensitive to duplication. In any case, new edges
no longer suffer from this jitter, and we're going to repair the whole
graph in a few weeks. I think this will require several megawatthours
of computation.

Your first two statements are correct. I don't understand your third
statement. But I think it is a false assertion. Could you briefly
restate?

An aside: There may be some signal in the cursors. Especially in the
most significant bytes. They're references into the edge-creation-time
index after all. I don't know how much obfuscation there is,
especially in the lsb's, but the cursors ideally should be treated as
opaque tokens. While unlikely, we may change their format at some time
in the future. And then various acts of daring do could break.

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.

On Oct 7, 6:57 am, Jeffrey Greenberg 
wrote:
> John,Please clarify this scenario. If one makes a complete set of calls
> starting from cursor -1 unto the end at one moment, and then another set of
> the same calls later is there any invariance?  If so what?
>
> From the statements above I understand:
> - always 5000 followers are returned (if the user has more than 5000, and
> the last call will have less)
> - the order is the same: it's the time order that users followed this
> account
>
> And thus:
> - there is no correlation in the API between a particular cursor and a set
> of returned values (followers)
>
> Is that it?
>
> On Tue, Oct 6, 2009 at 4:12 PM, John Kalucki  wrote:
>
> > I described, in some detail, the reasons for cursors here:
>
> >http://groups.google.com/group/twitter-development-talk/msg/badfb7b60...
>
> > If the details are uninteresting, the high-level summary is this: The
> > paged API was designed in a previous era. Paging is simply too
> > expensive and totally impractical to provide with the current
> > following counts. Also the QoS had deteriorated to the point where
> > some doubted that anyone was seriously using the methods. Paging is
> > going away and paging is not coming back.
>
> > The cursored approach allows us to continue to provide access to the
> > social graph via the REST API. As a benefit, QoS has been dramatically
> > improved and data quality is now pretty close to perfect.
>
> > If the implementation details and invariants described are confusing,
> > then stick to the well worn part of the path: Request the first block
> > with a cursor of -1. Keep requesting forward until you get a cursor of
> > 0.
>
> > -John Kalucki
> >http://twitter.com/jkalucki
> > Services, Twitter Inc.
>
> > On Oct 6, 11:06 am, Jesse Stay  wrote:
> > > I said the same thing in the last thread about this - still no clue what
> > > Twitter is doing with cursors and how it is any different than the
> > previous
> > > paging methods.
> > > Jesse
>
> > > On Tue, Oct 6, 2009 at 10:22 AM, Dewald Pretorius 
> > wrote:
>
> > > > Thanks John. However, I will be the first to put up my hand and say
> > > > that I have no clue what you said.
>
> > > > Can someone please translate John's answer into easy to understand
> > > > language, with specific relation to the questions I asked?
>
> > > > Dewald
>
> > > > On Oct 5, 1:17 am, John Kalucki  wrote:
> > > > > I haven't looked at all the parts of the system, so there's some
> > > > > chance that I'm missing something.
>
> > > > > The method returns the followers in the reverse chronological order
> > of
> > > > > edge creation. Cursor A will have the most recent 5,000 edges, by
> > > > > creation time, B the next most recent 5,000, etc. The last cursor
> > will
> > > > > have the oldest edges.
>
> > > > > Each cursor points to some arbitrary edge. If you go back and
> > retrieve
> > > > > cursor B, you should receive N edges created just before the edge-
> > > > > pointed-to-by-B was created. I don't recall if N is always 5000,
> > > > > generally 5000 or if it's at most 5000. This detail shouldn't matter,
> > > > > other than, on occasion, you'll make an extra API call.
>
> > > > > In any case, retrieving cursor B will never return edges created
> > after
> > > > > the edge-pointed-to-by-B was created. All edges returned by cursor B
> > > > > will be no-newer-than, and generally older than, than the
> > edge-pointed-
> > > > > to-by-B.
>

[twitter-dev] Re: Twitter, Please Explain How Cursors Work

[Jeffrey Greenberg]

John,Please clarify this scenario. If one makes a complete set of calls
starting from cursor -1 unto the end at one moment, and then another set of
the same calls later is there any invariance?  If so what?

>From the statements above I understand:
- always 5000 followers are returned (if the user has more than 5000, and
the last call will have less)
- the order is the same: it's the time order that users followed this
account

And thus:
- there is no correlation in the API between a particular cursor and a set
of returned values (followers)

Is that it?


On Tue, Oct 6, 2009 at 4:12 PM, John Kalucki  wrote:

>
> I described, in some detail, the reasons for cursors here:
>
> http://groups.google.com/group/twitter-development-talk/msg/badfb7b6074aab10
>
> If the details are uninteresting, the high-level summary is this: The
> paged API was designed in a previous era. Paging is simply too
> expensive and totally impractical to provide with the current
> following counts. Also the QoS had deteriorated to the point where
> some doubted that anyone was seriously using the methods. Paging is
> going away and paging is not coming back.
>
> The cursored approach allows us to continue to provide access to the
> social graph via the REST API. As a benefit, QoS has been dramatically
> improved and data quality is now pretty close to perfect.
>
> If the implementation details and invariants described are confusing,
> then stick to the well worn part of the path: Request the first block
> with a cursor of -1. Keep requesting forward until you get a cursor of
> 0.
>
> -John Kalucki
> http://twitter.com/jkalucki
> Services, Twitter Inc.
>
> On Oct 6, 11:06 am, Jesse Stay  wrote:
> > I said the same thing in the last thread about this - still no clue what
> > Twitter is doing with cursors and how it is any different than the
> previous
> > paging methods.
> > Jesse
> >
> > On Tue, Oct 6, 2009 at 10:22 AM, Dewald Pretorius 
> wrote:
> >
> > > Thanks John. However, I will be the first to put up my hand and say
> > > that I have no clue what you said.
> >
> > > Can someone please translate John's answer into easy to understand
> > > language, with specific relation to the questions I asked?
> >
> > > Dewald
> >
> > > On Oct 5, 1:17 am, John Kalucki  wrote:
> > > > I haven't looked at all the parts of the system, so there's some
> > > > chance that I'm missing something.
> >
> > > > The method returns the followers in the reverse chronological order
> of
> > > > edge creation. Cursor A will have the most recent 5,000 edges, by
> > > > creation time, B the next most recent 5,000, etc. The last cursor
> will
> > > > have the oldest edges.
> >
> > > > Each cursor points to some arbitrary edge. If you go back and
> retrieve
> > > > cursor B, you should receive N edges created just before the edge-
> > > > pointed-to-by-B was created. I don't recall if N is always 5000,
> > > > generally 5000 or if it's at most 5000. This detail shouldn't matter,
> > > > other than, on occasion, you'll make an extra API call.
> >
> > > > In any case, retrieving cursor B will never return edges created
> after
> > > > the edge-pointed-to-by-B was created. All edges returned by cursor B
> > > > will be no-newer-than, and generally older than, than the
> edge-pointed-
> > > > to-by-B.
> >
> > > > So, all future sets returned by cursor B are always disjoint from the
> > > > set originally returned by cursor A. In your example, if you
> refetched
> > > > both A and B, the result sets wouldn't be disjoint as there are no
> > > > longer 5,000 edges between cursor A and cursor B.
> >
> > > > I think this, in part answers your question. ?
> >
> > > > -John Kaluckihttp://twitter.com/jkalucki
> > > > Services, Twitter Inc.
> >
> > > > On Oct 4, 6:10 pm, Dewald Pretorius  wrote:
> >
> > > > > For discussion purposes, let's assume I am cursoring through a very
> > > > > volatile followers list of @veryvolatile. We have the following
> > > > > cursors:
> >
> > > > > A = 5,000
> > > > > B = 5,000
> > > > > C = 5,000
> >
> > > > > I retrieve Cursor A and process it. Next I retrieve Cursor B and
> > > > > process it. Then I retrieve Cursor C and process it.
> >
> > > > > While I am processing Cursor C, 200 of the people who were in
> Cursor A
> > > > > unfollow @veryvolatile, and 400 of the people who were in Cursor B
> > > > > unfollow @veryvolatile.
> >
> > > > > What do I get when I go back from C to B? Do I now get 4,600 ids in
> > > > > the list?
> >
> > > > > Or, do I get 5,000 in B, which now includes a subset of 400 ids
> that
> > > > > were previously in Cursor A?
> >
> > > > > Dewald
>

[twitter-dev] Re: Updates to the retweet API payload

[Marco Kaiser]

Well, you're not making use of JSON as JSON, and instead use "brute-force"
methods to extract parts of it... I think it's a bit unfair to request that
change to be made, as it would complicate things for everyone doing "real"
JSON-to-OO mapping. Just my 2c.

And no, retweet_status is perfectly valid - it's the property name in a
status model, and it is assigned a status data model. Just a nested object.
You don't have to name a member "status" just because it is a Status data
type...

Marco

2009/10/7 Zaudio 

>
> Sure, I'll justify this mroe...
>
> One of our apps receives updates via the Streaming API and the various
> REST api methods (mentions, user timelines, friends/home timelines).
> We collect data as JSON as it's to date been faster and mor compact
> than alternatives... we can also then go on to use this directly
> client side in Jscript if we wish...
> We are caching all updates of interest in a db... thus parse them for
> the required data fields before storing them there. Currently the
> parser has to pull out the user node, and is then left with the root
> status node it is then simple to parse the separated nodes for all
> fields pertinant to the current operation.
> We make quick checks initially to determine the relevance of the
> message to the app's cached stream we want to check things like
> JUST created_at for the status (and not user) and then check the text
> property for certain markers.
> It is easy to find these efficiently in a JSON string without parsing
> the entire thing to objects as things stand... so we save a lot of
> server cpu cycles. It's fastest to this from the inner node
> outwards... this is where the 'wasted' cpu cycles are coming in here
> with the change for retweeted_status
> Status's of interest only have the further fields parsed that we want
> for out db copy...
>
> for example.. say you want to quickly check the id of the status to
> confirm if you have it in you db already or not... currently we just
> excluded the user node, and thent he id is in the remainder without
> conflict.
>
> Now add retweeted_status with it's user subnode
>
> To now get the id of the root status without parsing the entire string
> to objects... we pull it apart again from the inner node outwards...
> we now need to exclude the retweeted_status user subnode... this no
> longer has a unique start tag/definition... as there are TWO identical
> start tags in the string so we do a lot more work to ensure we get
> the retweeted_status and it's user node that we would if it had an
> alternative start tag.
> If it were instead retweeted_user, then we could extract that directly
> and easily, exclude it, then exclude the surrounding retweeted_status
> tag... and we've got the retweeted_status node separated... then we
> can procede as we do now with the rest... and if necessary use the
> retweeted_status as well.
>
> Hope that makes sense
> I agree that keeping it as user also makes good object sense... but
> then the retweeted_status is not 'status' anymore... and it is a
> status I'm suggesting soemthing similar for it's inner node..
>
> Simon (Zaudio)
>
>
> On Oct 6, 12:01 pm, Marco Kaiser  wrote:
> > No, please don't change that to retweeted_user ... the data structure
> > included as the retweeted status is a status, and that data structure has
> a
> > user property. That's a very clear object model, and should map very well
> to
> > JSON, as it's nested, not at the same level as the main user the retweet
> is
> > received from. So by doing that change, you'd break the data model for a
> > status, in that there are two version that need to be taken care of.
> >
> > Or can you explain in more depth why this would cause problems with
> > reasonable JSON parsers that map strings to objects?
> >
> > 2009/10/6 Zaudio 
> >
> >
> >
> > > Another significant thought... could you 'please' consider changing
> > > the name of the  node INSIDE the retweeted_status node to say
> > >  ?
> >
> > > Thius will make JSON parsing way simpler... especially if the goal is
> > > to extract the retweeted_status when present; or do things like
> > > quickly find the date of the tweet... I alreayd have to contend with a
> > > created_at field in the user and status nodes... now that could double
> > > up... so owuld appreciate an easier to find retweeted user node for
> > > JSON parsability
> >
> > > Thanks
> >
> > > Simon (Zaudio)
> >
> > > On Oct 4, 8:16 am, John Kalucki  wrote:
> > > > Retweetis an invasive feature with many deep dependency paths. Firm
> > > > dates would be useful, but they aren't possible in this particular
> > > > situation. This makes planning for downstream folks difficult.
> >
> > > > I'd be ready for the slight possibility of low-volume retweets
> mid-to-
> > > > late week, with a high chance the following week, and perhaps a near-
> > > > unity chance of low-volume retweets the week after that. So, for
> > > > critical code, any time now. As for full-roll-out, 

[twitter-dev] Re: Updates to the retweet API payload

[Zaudio]

Sure, I'll justify this mroe...

One of our apps receives updates via the Streaming API and the various
REST api methods (mentions, user timelines, friends/home timelines).
We collect data as JSON as it's to date been faster and mor compact
than alternatives... we can also then go on to use this directly
client side in Jscript if we wish...
We are caching all updates of interest in a db... thus parse them for
the required data fields before storing them there. Currently the
parser has to pull out the user node, and is then left with the root
status node it is then simple to parse the separated nodes for all
fields pertinant to the current operation.
We make quick checks initially to determine the relevance of the
message to the app's cached stream we want to check things like
JUST created_at for the status (and not user) and then check the text
property for certain markers.
It is easy to find these efficiently in a JSON string without parsing
the entire thing to objects as things stand... so we save a lot of
server cpu cycles. It's fastest to this from the inner node
outwards... this is where the 'wasted' cpu cycles are coming in here
with the change for retweeted_status
Status's of interest only have the further fields parsed that we want
for out db copy...

for example.. say you want to quickly check the id of the status to
confirm if you have it in you db already or not... currently we just
excluded the user node, and thent he id is in the remainder without
conflict.

Now add retweeted_status with it's user subnode

To now get the id of the root status without parsing the entire string
to objects... we pull it apart again from the inner node outwards...
we now need to exclude the retweeted_status user subnode... this no
longer has a unique start tag/definition... as there are TWO identical
start tags in the string so we do a lot more work to ensure we get
the retweeted_status and it's user node that we would if it had an
alternative start tag.
If it were instead retweeted_user, then we could extract that directly
and easily, exclude it, then exclude the surrounding retweeted_status
tag... and we've got the retweeted_status node separated... then we
can procede as we do now with the rest... and if necessary use the
retweeted_status as well.

Hope that makes sense
I agree that keeping it as user also makes good object sense... but
then the retweeted_status is not 'status' anymore... and it is a
status I'm suggesting soemthing similar for it's inner node..

Simon (Zaudio)


On Oct 6, 12:01 pm, Marco Kaiser  wrote:
> No, please don't change that to retweeted_user ... the data structure
> included as the retweeted status is a status, and that data structure has a
> user property. That's a very clear object model, and should map very well to
> JSON, as it's nested, not at the same level as the main user the retweet is
> received from. So by doing that change, you'd break the data model for a
> status, in that there are two version that need to be taken care of.
>
> Or can you explain in more depth why this would cause problems with
> reasonable JSON parsers that map strings to objects?
>
> 2009/10/6 Zaudio 
>
>
>
> > Another significant thought... could you 'please' consider changing
> > the name of the  node INSIDE the retweeted_status node to say
> >  ?
>
> > Thius will make JSON parsing way simpler... especially if the goal is
> > to extract the retweeted_status when present; or do things like
> > quickly find the date of the tweet... I alreayd have to contend with a
> > created_at field in the user and status nodes... now that could double
> > up... so owuld appreciate an easier to find retweeted user node for
> > JSON parsability
>
> > Thanks
>
> > Simon (Zaudio)
>
> > On Oct 4, 8:16 am, John Kalucki  wrote:
> > > Retweetis an invasive feature with many deep dependency paths. Firm
> > > dates would be useful, but they aren't possible in this particular
> > > situation. This makes planning for downstream folks difficult.
>
> > > I'd be ready for the slight possibility of low-volume retweets mid-to-
> > > late week, with a high chance the following week, and perhaps a near-
> > > unity chance of low-volume retweets the week after that. So, for
> > > critical code, any time now. As for full-roll-out, that would be even
> > > more of a guessing game.
>
> > > -John Kaluckihttp://twitter.com/jkalucki
> > > Services, Twitter Inc.
>
> > > On Oct 4, 6:43 am, Zaudio  wrote:
>
> > > > Hey John,
>
> > > > Thanks for that... can you put an earliest date on 'very soon' please
> > > > - just so I know how long we've got?
>
> > > > Thanks
>
> > > > Simon (Zaudio)
>
> > > > On Oct 3, 8:15 pm, John Kalucki  wrote:
>
> > > > > There are plans to filter retweets from various resource, see the
> > > > > documentation. However, it would be most prudent to assume that
> > > > > retweets will eventually show up everywhere, and handle them
> > > > > appropriately, or at least tolerate them wherever they are 

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

No, that's for both the generation of the signature and the request.  I just
tested it.  If the parameters are not in the correct order, the request will
fail with a "401 Unauthorized" error.  In my test, I put the timestamp
before the nonce.  The request failed.  If I put the parameters in order,
the request is successful.

On Wed, Oct 7, 2009 at 8:14 AM, JDG  wrote:

> That's simply for generating the signature base string. it does not matter
> when you're actually sending the parameters.
>
>
> On Wed, Oct 7, 2009 at 05:33, ryan alford  wrote:
>
>> Here is the documentation on ordering the parameters...
>> http://oauth.net/core/1.0#anchor14
>>
>> Section 9.1.1
>>
>> Parameters are sorted by name, using lexicographical byte value ordering.
>> If two or more parameters share the same name, they are sorted by their
>> value.
>>
>> This is excluding the oauth_signature parameter.
>>
>> Ryan
>>  
>>
>> On Wed, Oct 7, 2009 at 6:11 AM, ryan alford wrote:
>>
>>> Yes, the order does matter. All parameters need to be in order except
>>> for the signature. The signature should be last and should have been
>>> generated with all of the parameters in the correct order.
>>>
>>>
>>>
>>> On Oct 7, 2009, at 12:10 AM, jmathai  wrote:
>>>
>>> >
>>> > The order of parameters shouldn't matter.  What library are you using
>>> > to generate the url?
>>> >
>>> > On Oct 6, 8:51 pm, ryan alford  wrote:
>>> >> The signature needs to be at the end of the URL, not sorted with the
>>> >> other parameters.
>>> >>
>>> >> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>>> >>
>>> >>
>>> >>
>>> >>> I am trying to run a sample app
>>> >>> but i am getting 401 error during request_token phase.
>>> >>
>>> >>> Failed to validate oauth signature and token
>>> >>
>>> >>> this is what i am accessing:
>>> >>
>>> >>>
>>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
>>> >>> ...
>>> >>
>>> >>> What's problem this sentence
>>> >>> Anybody help me plz..
>>>
>>
>>
>
>
> --
> Internets. Serious business.
>

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[JDG]

That's simply for generating the signature base string. it does not matter
when you're actually sending the parameters.

On Wed, Oct 7, 2009 at 05:33, ryan alford  wrote:

> Here is the documentation on ordering the parameters...
> http://oauth.net/core/1.0#anchor14
>
> Section 9.1.1
>
> Parameters are sorted by name, using lexicographical byte value ordering.
> If two or more parameters share the same name, they are sorted by their
> value.
>
> This is excluding the oauth_signature parameter.
>
> Ryan
>  
>
> On Wed, Oct 7, 2009 at 6:11 AM, ryan alford wrote:
>
>> Yes, the order does matter. All parameters need to be in order except
>> for the signature. The signature should be last and should have been
>> generated with all of the parameters in the correct order.
>>
>>
>>
>> On Oct 7, 2009, at 12:10 AM, jmathai  wrote:
>>
>> >
>> > The order of parameters shouldn't matter.  What library are you using
>> > to generate the url?
>> >
>> > On Oct 6, 8:51 pm, ryan alford  wrote:
>> >> The signature needs to be at the end of the URL, not sorted with the
>> >> other parameters.
>> >>
>> >> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>> >>
>> >>
>> >>
>> >>> I am trying to run a sample app
>> >>> but i am getting 401 error during request_token phase.
>> >>
>> >>> Failed to validate oauth signature and token
>> >>
>> >>> this is what i am accessing:
>> >>
>> >>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
>> >>> ...
>> >>
>> >>> What's problem this sentence
>> >>> Anybody help me plz..
>>
>
>


-- 
Internets. Serious business.

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

Here is the documentation on ordering the parameters...
http://oauth.net/core/1.0#anchor14

Section 9.1.1

Parameters are sorted by name, using lexicographical byte value ordering. If
two or more parameters share the same name, they are sorted by their value.

This is excluding the oauth_signature parameter.

Ryan


On Wed, Oct 7, 2009 at 6:11 AM, ryan alford  wrote:

> Yes, the order does matter. All parameters need to be in order except
> for the signature. The signature should be last and should have been
> generated with all of the parameters in the correct order.
>
>
>
> On Oct 7, 2009, at 12:10 AM, jmathai  wrote:
>
> >
> > The order of parameters shouldn't matter.  What library are you using
> > to generate the url?
> >
> > On Oct 6, 8:51 pm, ryan alford  wrote:
> >> The signature needs to be at the end of the URL, not sorted with the
> >> other parameters.
> >>
> >> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
> >>
> >>
> >>
> >>> I am trying to run a sample app
> >>> but i am getting 401 error during request_token phase.
> >>
> >>> Failed to validate oauth signature and token
> >>
> >>> this is what i am accessing:
> >>
> >>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
> >>> ...
> >>
> >>> What's problem this sentence
> >>> Anybody help me plz..
>

[twitter-dev] API for marking tweets seen

[Theyagarajan S]

Hello,

As someone who uses tweetdeck,web and my mobile client i would think if
there was  a way an app would know if the tweet was already seen by a
user.One way i could think of is knowing/storing the least tweet (by
timestamp) that was fetched by user with API/web, and any app that user will
first fetch the last seen tweet time and request only tweet stream after the
time.

Has anyone else felt the need for this?

Thanks
Taggy

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

[Thomas Hübner]

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
> > > > > > > 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: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

Yes, the order does matter. All parameters need to be in order except
for the signature. The signature should be last and should have been
generated with all of the parameters in the correct order.



On Oct 7, 2009, at 12:10 AM, jmathai  wrote:

>
> The order of parameters shouldn't matter.  What library are you using
> to generate the url?
>
> On Oct 6, 8:51 pm, ryan alford  wrote:
>> The signature needs to be at the end of the URL, not sorted with the
>> other parameters.
>>
>> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>>
>>
>>
>>> I am trying to run a sample app
>>> but i am getting 401 error during request_token phase.
>>
>>> Failed to validate oauth signature and token
>>
>>> this is what i am accessing:
>>
>>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
>>> ...
>>
>>> What's problem this sentence
>>> Anybody help me plz..

[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.