caching is the best answer i have found
On Fri, Sep 4, 2009 at 9:01 PM, dizidglasw...@gmail.com wrote:
Hi,
When i request friends (or followers) from the Twitter API i want to
get the screen_name's based on the id's.
I use users/show for this, inputting the id and getting back de
I gave it a shot, but I'm still getting the same result. I tried a few
accounts from a few ips, and also a new account from a new ip and I
always get the 401 on the second connect.
If it helps, I tried another api call repeatedly that requires auth
(http://twitter.com/statuses/mentions.json) and
Do you have any code examples for this? So you basically maintain a
local db of id-to- screen_names? Do you get all of a user's friend/
follower id's and then look up their screen names with individual API
calls? What do you do when a user has more relationships than the API
limit will
Jim,
Thanks for the broad summary,
I fully agree with you.
There should be some mechanism for mobile devices with
less resources for OAuth.
Regarding the source parameter of the Application, it is very
important with regards of e-marketing of the application itself.
Greetings!
On Sep 5, 2:08
Is there any way that you can make an option to adjust the position of
the background image? It seems more natural for me to have my personal
image in the bottom right corner and not the top left. Thank you very
much.
Hi All,
I get the following error message for some invocations of:
account/rate_limit_status.xml
I found this in the logs of my application.It happens about 20 times a
day but it is
still annoying.Most of the time it works fine, so i guess it is due to
high load or something
any idea?
Hello,
sometimes users login with their e-mail,
while my app is expecting username.
the user can login with no problems but later on, the app
is using the e-mail instead of login/screen name.
s there any way to get user id/screen_name from e-mail.
how can one overcome this problem?
Thanks!
You should be able to use:
http://apiwiki.twitter.com/Twitter-REST-API-Method:-account
verify_credentialshttp://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0verify_credentials
to
get the user_id/screen_name.
Abraham
On Sat, Sep 5, 2009 at 05:20, twittme_mobi nlupa...@googlemail.com
John,
Just so we know, is this 5,000 thing going to be fixed over the
weekend, or will we have to wait until Tuesday?
Dewald
On Sep 5, 12:35 am, John Kalucki jkalu...@gmail.com wrote:
We're aware of the problem with the following API not returning more
than 5,000 followers. Apparently this
Thanks for your replies, I will try to explain my question better:
My goal is to backup my friends (e.g. the people i follow) in a .cvs
file.
I first do an API call to get all friends, like this cfhttp
url=http://twitter.com/friends/ids.json?screen_name=#tu#;
method=get result=output /
This
There's probably a defect in the last version of the server, or maybe
there's an inconsistent auth database that's tripping things up. I
tried to reproduce this numerous ways last night, and I think I saw
this issue once, but I wasn't sure. If there's a defect, it's subtle.
Please reproduce in
Hi,
I'm writing a twitter service which only uses API methods not
requiring authentication.
I'd like to bind the service to the user's twitter name though. In
order to verify the user's identity, I could have them sign in with
OAuth (seems a little overkill though because I won't be using any
hi Ryan,
any update on this issue ?
Using Twitter4J, and what I've been seeing is last night,
getFollowersIDs(), including suspended. This AM, the filtering of
suspended accounts seems to be working again.
On the other hand, getFollowersStatuses() doesn't seem to be
filtering out the suspended accounts.
pg
On Sep 5, 7:36 am,
Thanks to the efforts of many working late into a Friday night, we
deployed a fix for this issue starting at about 11pm PDT. The fix was
verified as working in production at about 12:05am PDT.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sep 5, 5:36 am, Dewald Pretorius
Awesome. Thanks John, and also to everyone who made this happen.
Dewald
On Sep 5, 10:55 am, John Kalucki jkalu...@gmail.com wrote:
Thanks to the efforts of many working late into a Friday night, we
deployed a fix for this issue starting at about 11pm PDT. The fix was
verified as working in
Hello
I am seeing right now (14:45 UTC) discrepancy between the list of my
followers as reported by my home page at Twitter.com (which is
correct) and the list reported by the API - which seems to be several
days old (it includes several followers that I blocked recently).
Is anyone else seeing
The ideal solution is for Twitter to change the system and
allow each account to have only one screen name, all the
time, forever, with no changes. Then a separate id value
is not required because all account identification will be
done by the original screen name.
REST and SEARCH would
All the time. I have given up on expecting consistency between summary
numbers and the actual detail data.
Twitter has to do so much data replication for performance reasons, I
think it's extremely tough to keep everything in sync.
It's like the discrepancies in search results and site rankings
Dear All,
I am a newbie in a matter of a Twitter-API. I'm currently doing a
research about importance of a User in twitter based on his/her social
network graph.
As a first step, I would like to analyze the Top Users in twitter
(user with the most followers).
I saw from the API-DOC that
John, thanks for spending time on this. Any chance we can get a lift on the
follow limits for a temporary time so I can catch up a few users that were
affected by this? Or, if you want to do it on a per-user basis I can send
you the names of the users.
Jesse
On Sat, Sep 5, 2009 at 7:55 AM,
I know there's been a ton of request for a followers/screen_names API,
or a friends/screen_names one for that matter. Right now the only way
of getting all of a user's followers is with http://twitter.com/followers/ids.xml
and that only renders the id's. There's no efficient way of getting
You've just made a perfect argument for my suggestion that
Twitter use ONLY unchangeable screen names (no more ids) for
the whole system.
:)
Owkaye
I know there's been a ton of request for a
followers/screen_names API, or a friends/screen_names one
for that matter. Right now the only way
The friend/follower counts are TOTALLY off. Why can't new features be
introduced without breaking critical existing features? When will
this be fixed. Many of us rely on these counts for accurate f/f
counts!
On Sep 4, 8:49 pm, John Kalucki jkalu...@gmail.com wrote:
The 5k limit is a bug.
Again, I can't stress this enough - when bugs like this are introduced, it
is imperative that follow limits are also removed temporarily (or on a
case-by-case basis) so we can make this up to our users. I've already had
to issue refunds to a couple due to this. If you need me to send you the
Jesse,
Last night when this thing hit I actually immediately thought about
you and wondered how it impacted you.
I'm now thanking my lucky stars that I don't do mass unfollow. I do
have the unfollow those who unfollow me feature, but I have limited
it to a maximum of 10 unfollows every 8 hours,
I find if you take it as the rule and not the exception it's much easier to
plan. Seems that way lately with Twitter. :-)
FWIW, I know you hate hearing this, but Facebook's API pushes changes into a
beta staging environment every Tuesday, notifies developers of the changes
as they update it, and
Fortunately it only affected a couple users, but I'd like to make it up to
them. BTW, this didn't affect the mass unfollow feature you saw Scoble and
others using (that would have worked fine). This affected the unfollow
those who unfollow me feature. We have safety valves in place as well, but
I would have built in something like doing an array diff before doing
any unfollow, and if the diff is 10%+ of the old followers list, then
just bail and do nothing.
Even the mass unfollow would not have worked, if the API returned only
5,000 friends instead of the full list, correct?
Dewald
I've tried and tried for several MONTHS through all channels I can
find, to get Twitter to fix this issue, but all I've gotten are
automated mssages, and dropped problem tickets. I get Direct Messages
that are shown to be from MYSELF, but I didn't send them. They are
coming from a blog called
On Sat, Sep 5, 2009 at 3:38 PM, John Kaluckijkalu...@gmail.com wrote:
There's probably a defect in the last version of the server, or maybe
there's an inconsistent auth database that's tripping things up. I
tried to reproduce this numerous ways last night, and I think I saw
this issue once,
Change your Twitter password immediately.
That can only happen if some rogue service has your password and sends
DMs on your account.
Changing your password should stop them dead in their tracks.
Dewald
On Sep 5, 12:02 pm, amylou61 aleach6...@gmail.com wrote:
I've tried and tried for several
The fix to last nights 5000 limit to friends/ids, followers/ids now
returns with approximately 1-5% duplicates.
For example:
User1:
followers: 32795
unique followers: 32428
User2:
friends: 32350
unique friends: 32046
User3:
followers: 19243
unique followers: 19045
NEITHER of these figures
I've disabled all our following scripts until we hear back from Twitter on
this. Can I pay to get a 24/7 support number I can call for stuff like this?
Jesse
On Sat, Sep 5, 2009 at 1:38 PM, PJB pjbmancun...@gmail.com wrote:
The fix to last nights 5000 limit to friends/ids, followers/ids now
I think changeable screen_names are a big problem even outside the
api, for links for example : twitter accounts are linked everywhere
with uri http://twitter.com/screen_name so it may cause 404 if the
user changes his/her screen_name, or worst if someone else takes it,
it will link to the wrong
35 matches
Mail list logo
