Alex introduced a limit (15/hr ) to verify_credentials – even
authentic calls. But IIRC, this was later removed, looks like it's
back.
If an API is untrusted, it must be treated as entirely untrusted. You
should be adding defensive heuristics between the untrusted API
results and your application. If a given fetch seems bad, then queue
the results and don't act on them until otherwise corroborated,
perhaps by some quorum of subse
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 c
Twitter removed that functionality just recently. Any application that
used if before it was removed is still allowed to use it.
On Oct 5, 2009, at 12:07 AM, Vincent Nguyen wrote:
> We knew is to change "from" on tweets, we must use Oauth!
> But i see desktop client such as tweetdeck, twitter
We knew is to change "from" on tweets, we must use Oauth!
But i see desktop client such as tweetdeck, twitterfox,...
don't use Oauth and they still have "from twitterfox",..
how does that happens?
AndrewI don't think you can do that. If that would have been the case, they
would have never put any restrictions.
Yogesh
On Sun, Oct 4, 2009 at 3:43 PM, Josh Roesslein wrote:
>
> Andrew,
>
> I'd email a...@twitter.com about getting whitelisted. If they deny it
> then maybe just do a little bit
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
Thomas, again, that number may be different from one minute to another, and
I've also found it gets cached differently. I want to know the number of
friends/followers at the time the snapshot was taken for the set I'm paging
through. I want to know the number Twitter expects to be in that specifi
Andrew,
I'd email a...@twitter.com about getting whitelisted. If they deny it
then maybe just do a little bit at a time
until you have processed all your username -> ids.
Josh
On Sun, Oct 4, 2009 at 3:40 PM, Andrew McCloud wrote:
>
> I don't thin you understood my question. I have a list of us
I don't thin you understood my question. I have a list of usernames
that i need to convert to ids. These usernames are not friends of my
account.
On Oct 3, 11:18 pm, Thomas Hübner wrote:
> you can
> usehttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0f...
> together with the
requests for friends/ids with cursor=-1 parameter via API (through
Yahoo Pipe) returns empty set
The same request for .xml data right from browser returns correct
data.
requests for friends/ids return 400 Bad request via API (through Yahoo
Pipe).
The same request for .xml data right from browser returns correct
data.
E.g.:
http://www.twitter.com/friends/ids/abava.xml - always work from
browser
and the same request does not work via API (through Yahoo pipe)
We've
the Number of ID's is the number of followers
you also can call
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
first. Within the result you have
1031
293
however - you have to do an additional API call if you don't trust the
pagewise calls
Jesse Stay schrieb:
> Thomas, I
John, because no offense, but frankly I don't trust the Twitter API. I've
been burned too many times by things that were "supposed to work", code
pushed into production that wasn't tested properly, etc. that I know better
to do all I can to account for Twitter's mistakes. There's no telling if at
Thomas, I don't see where it gives you the expected number of users.
Originally I thought Alex said that was going to be part of it, but not
seeing it in the docs. I only see ids, next_cursor, and previous_cursor.
On Sun, Oct 4, 2009 at 8:36 AM, Thomas Hübner wrote:
> You can use the socialGraph
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 t
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 tim
You can use the socialGraph method before:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids
If you have this you have the expected number of users.
Jesse Stay schrieb:
> I was wondering if it might be possible to include, at least in the
> first page, but if it's easier it
Curious -- why isn't the end of list indicator a reliable enough
indication? "Iterate until" seems simple and reliable.
Can you request the denormalized count via the API before you begin?
(Not familiar enough with the API, but the back-end store offers this
for all sorts of purposes.) You'd hav
Retweet is 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 chan
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 prud
Ah - okay. I was looking in the wrong spot. Haven't looked those up in
awhile.
Jesse
On Sun, Oct 4, 2009 at 2:12 AM, Rich wrote:
>
> statuses/friends and statuses/followers are there for me
>
> On Oct 4, 9:10 am, Jesse Stay wrote:
> > I noticed that the "friends" and "followers" methods aren'
Hi,
When searching using geocod, max_id, pagination and since (I included
them all since I don't know which is/may be causing the problem) I get
duplicate results and/or deleted tweets.
For example:
This search returns several duplicates of the same tweet but with
different IDs:
http://search.t
I was wondering if it might be possible to include, at least in the first
page, but if it's easier it could be on all pages, either a total expected
number of followers/friends, or a total expected number of returned pages
when the cursor parameter is provided for friends/ids and followers/ids? I'm
The Geo tag is only populated firstly if the user posting the tweet
has opted in via Twitter's website (which hasn't been enabled yet) and
secondly Geo data was submitted with that tweet
On Oct 4, 4:41 am, Patrick wrote:
> I have been reading about the Twitter Geo stuff - it all sounds
> excitin
statuses/friends and statuses/followers are there for me
On Oct 4, 9:10 am, Jesse Stay wrote:
> I noticed that the "friends" and "followers" methods aren't on the docs any
> more here:http://apiwiki.twitter.com/Twitter-API-Documentation
>
> Did I miss the memo that these were being deprecated? W
I noticed that the "friends" and "followers" methods aren't on the docs any
more here:
http://apiwiki.twitter.com/Twitter-API-Documentation
Did I miss the memo that these were being deprecated? Why aren't they in the
docs?
Thanks,
Jesse
27 matches
Mail list logo
