I am still a little unclear if we will be able to determine the correct
since_id to pass to the api by always looking for the largest tweet id we have
seen.
It seems if two messages are posted at very close to same time, they may not be
sequential since the bottom bits will be randomly generat
type of information is valuable to
the user, but user objects (not ids) would be required to create a UI
for someone to view and then interact with such requests.
--Naveen Ayyagari
@knight9
@SocialScope
On Apr 13, 7:32 pm, Dana Contreras wrote:
> We've deployed two new methods for re
feel free to tear apart my assumptions
or if there is some security risk I am not considering with this type
of implementation?
--Naveen Ayyagari
@knight9
@SocialScope
On Apr 13, 9:06 pm, Raffi Krikorian wrote:
> > Is there API endpoints planned to accept/reject incoming and cancel
&g
This is great.
I love the twurl interface at http://dev.twitter.com/console
Just a thought/suggestion, a link to the documentation when a method
is chosen from the drop down list. Its not critical, i can look it up;
it would just be a nice extra to save me a few extra clicks.
--Naveen Ayyagari
We see the same huge latency and timeouts as well (our timeouts are
also at 30 seconds).
We running out of a US data center on multiple machines, we see this
issue on all if our servers.
I agree with @tjaap, would like to hear twitters reaction as well.
On May 7, 6:02 pm, Tjaap wrote:
> I'm se
, 2010 at 12:08 AM, Naveen Ayyagari
> wrote:
>
>
>
> > We see the same huge latency and timeouts as well (our timeouts are
> > also at 30 seconds).
>
> > We running out of a US data center on multiple machines, we see this
> > issue on all if our servers
+1 on the additional parameter to optionally request the data. Every
byte counts for mobile device battery life and download time.
--Naveen Ayyagari
@knight9
On May 13, 8:13 pm, Dewald Pretorius wrote:
> Raffi,
>
> This is all good, but can you please make the inclusion in the tweet
search.twitter.com website.
http://dl.dropbox.com/u/27113/search_wierdness.jpg
I have seen this strange behavior via the api as well and it is a bit
confusing.
--Naveen Ayyagari
SocialScope
@knight9
Hello,
Hoping we can get post on status.twitter.com about @replies not
showing up... We have been getting a lot of reports that they are
missing, and a quick twitter search seems to indicate it is not
limited to our application.
http://search.twitter.com/search?had_popular=true&q=replies&resu
ucki wrote:
> > > The mentions timelines were updating with additional latency, perhaps a
> > few
> > > minutes, for about a day, but they were updating. They should be updating
> > in
> > > near real time now.
>
> > > -John Kaluckihttp:/
I would love to participate in any conversation related to push
services as well meet other developers out there. Count me in, I
should be able to make it work any day that week.
Naveen Ayyagari
Ubiquitous Systems
On May 21, 2009, at 5:18 PM, Alex Payne wrote:
>
> Hi all,
>
I have a user who posts a lot of messages and is reporting that his
messages are not posting from our app. After some investigation when
the user posts on twitter.com he receives a message something to the
effect "too much twittering for the hour"...
The API does not report any error message
Chris ,
We implemented something like this "network status" using the
rate_limit_status call (for the IP), while some of the numbers are
sometimes wonky with this api right now we poll this every 5 minutes
and set a flag to enable or disable all twitter requests from the
server dep
Sometimes the rate_limit_status call is not returning a 302 to
redirect, or the rate_limit_status xml, but HTML with a meta refresh
in it (which curl doesnt understand to follow redirect/retry).
Its not huge problem for us, but it can affect some throttling code
people may or may not be imp
t; Hmm, it shouldn't be spitting back HTML. How often are you seeing
>> this?
>> -Chad
>>
>>
>>
>> On Sat, Aug 8, 2009 at 1:02 PM, Naveen Ayyagari
>> wrote:
>>
>>> Sometimes the rate_limit_status call is not returning a 302 to
>>&
1. OAuth rarely works - I tried a number of your apps and it seems
to work 1 out of 6-7 times. As a note, it worked better with Safari,
but not every time.
-Not applicable
2. 302 redirect
- not sure anymore since our code has been updated to follow them
automatically.
3. Genera
Most calls seem to be working much better for us.
in response to the rate_limit_status call, I get HTML back
occasionally.. looks like the fail whale page and 502 twitter over
capacity..
Got this one about 10 min ago.
08-09-09 19:40:15rate_limit_status response(502): PUBLIC "-//W3C//DTD X
Just wanted to report that we are back up and running for the most
part as well, BUT quite a number of our servers are still experiencing
some BlackOut periods where twitter fails to respond and connections
time out. They seem to last about 5-10 minutes each. We are running
quite a few s
catcalls,
I would like to know what open source software you have contributed
and where they are located. I need to know to avoid using your work at
all costs.
Many open source software projects have dependencies, this DLL has a
dependency on Log4Net, the solution is simple, download and
+1 on this.
I think the ReTweet concept is more complex than the model in the
Retweet API described. While twitter has always been a keep it simple
service, I think you will find many users wont use this new
functionality if they can't use it the way they do currently (with
additional c
A quick google search shows how to use the Embeded Safari browser to
change the user-agent.
If you change the user-agent to something a desktop would use, it
should work for you.
Realize though that this will then give the desktop presentation of
the website, which may not be ideal..
h
I am seeing this issue as well. Users are reporting it very frequently
now...
At first I thought it was a bug in the client, but it happens every
time I try to delete a status right now, and it has become one of the
highest reported bugs in out app.
Twitter reports 400 with the JSON bel
+1 also can not connect to twitter api from any of our servers.
On Oct 18, 2009, at 10:32 AM, Mark Ng wrote:
+1 can't connect from slicehost.com (I believe in St. Louis).
2009/10/18 Michael Ivey :
Further info I've collected:
Can't connect from:
AT&T DSL in South Alabama
AT&T iPhone networ
+1 agreed
On Oct 23, 2009, at 7:20 PM, Dewald Pretorius wrote:
Instead of all of us having to do fancy tap-dances, the proper
solution is for Twitter to issue an error response when a sent tweet
is rejected for whatever reason.
Dewald
On Oct 23, 7:58 pm, AJ Chen wrote:
then, comparing the
Thanks for the quick response. I guess I was confused.
On Oct 28, 2009, at 8:53 PM, Marcel Molina wrote:
The cursors are for lists of lists and lists of users followed
by/following lists. The statuses timeline for a given list takes all
the same options you'd expect to manage status timelines.
I have seen these in our users logs as well. I wasn't sure if it was
twitter or a mobile gateway they were using.
On Oct 29, 2009, at 11:41 AM, hima wrote:
Hi
I am trying to collect users data from twitter, like the number of
followers, number of tweets, the time the user' account is alive
+1
Is there no way to view the lists that a user is subscribed to? As a
client, it seems kind of silly that we can't allow the user to view a
list that they already subscribe to with out them having to go find
the list again. Kind of a big hole, because that means we will have to
cache a
+1 I was wondering this as well.
On Oct 30, 2009, at 2:23 PM, Jim Gilliam wrote:
I assume lists_count must be coming to the user payload, but haven't
heard anyone mention it.
Jim
I agree, friday is a poor time to make planned changes to the API...
On Nov 13, 2009, at 11:58 PM, Jesse Stay wrote:
> I've already implemented this, but for future sanity, can you guys avoid
> doing these major updates on Fridays when we're all not focusing as much on
> work? That way if th
Not that I am advocating any change because I prefer the way it works now.
But this has been a point of confusion for some of our users as well.
The issue stems from when a user uses xAuth to authenticate, they understand it
as they have used their password so if they change the app should no lo
30 matches
Mail list logo