[twitter-dev] Re: Get friends' screen names instead of friends' ids?
Abraham, I noticed you added this discussion into that issue, so hopefully that will keep adding some visibility to that issue. It seems like this is a pretty popular request that keeps coming up on this list, yet the issue has a status of Won't Fix. Twitter dev team, is there anyway that you guys can reconsider this issue? The last time you guys evaluated it was back in February and I would image that the demand for a call like this has increased since then. On Jul 22, 7:32 am, Abraham Williams 4bra...@gmail.com wrote: Nope.http://code.google.com/p/twitter-api/issues/detail?id=265 On Wed, Jul 22, 2009 at 05:14, link2caro tran.minhq...@link2caro.comwrote: Hi, I would like to know if there is any way to get friends' screen names instead of friends' ids? Thank you in advance. P/S: sorry if this post is duplicate, I cannot find my last post. -- 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. Sent from Madison, WI, United States
[twitter-dev] Re: When to use page parameter for followers/ids
I asked the same thing just a few days ago, I even created a suggestion ticket for it but the suggestion got closed: http://code.google.com/p/twitter-api/issues/detail?id=831#c0 I do think this needs to be addressed but it sounds like its not a priority. On Jul 20, 10:10 am, Jesse Stay jesses...@gmail.com wrote: Something appears to have changed recently, perhaps a quicker timeout, or maybe Twitter's just getting overloaded, I can't tell. The solution isn't optimal though. I can't seem to get followers/ids without a page parameter to work with anyone above 100,000 followers. I have to resort to the page parameter in that case, and I'm still not sure if 100,000 followers is the actual number to tell you the truth. (100,000 followers really isn't that much compared to some of the larger users on Twitter) Somehow we need a better way to tell when we should resort to the page parameter, and when we shouldn't. When we should, it would be optimal if we could increase the results per page to closer to that limit. As of the moment, it takes 20 requests just to get all the followers of someone with 100,000 followers. Not only that, but the results returned are often inaccurate, or certain pages don't return anything at all. Getting the list of followers for someone with that many followers has become completely unreliable, and those users are starting to notice (across many apps). Ideally, it would be nice if we could get the single followers/ids method without page parameters to work for every user on Twitter (maybe more compression, perhaps returning as a binary object we can parse back into text, or whatever works). If that's not possible, is there a way Twitter can bump up in priority getting the page calls fixed, and perhaps with many more followers per page? Ideally, the max per page ought to be the maximum number of followers allowed before the page parameter is called. As of the moment, that call is almost useless. Jesse
[twitter-dev] Re: Tool that shows who is using specific tags?
Do you mean something like this? http://hashtags.org/ On Jul 19, 11:09 am, Nick Arnett nick.arn...@gmail.com wrote: I've searched a bit, but it's hard to write a good query for this one - anybody know of a tool that will show a list of users who have used a specific tag? It would be simple and I'll write it myself if need be. All it has to do is search for the tag and then compile and present a list of unique users. This occurred to me because I was thinking I'd like to see who is attending the Community Leadership Summit, but I don't want to have to page through all the results and manually assemble a list. It would be extra cool if there were a tool that did this for Twitter and blogs together. Anybody know of something like this? Nick
[twitter-dev] friends/ids Limits
Has anyone come up with a good number where a call to the social graph methods returns a 403? I have made calls that return over 30,000 ids, but I am curious what the limit is. Also, the general idea is that if you have someone that has a large following, you would then implement paging. Why is it that paging returns results 5000 records at a time? Is there a way to return more per page? Thanks Kevin
[twitter-dev] Re: Design of Invite Twitter friends
I had a similar question last night and found this thread that offered some insight into the most efficient way to do something like this. Here is the thread that discusses the best approach to get details on all of the friends or followers of a user: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8e255670186b52b3/54602c14899f42ff?lnk=gstq=list+friends# On Jul 9, 12:20 pm, chachra sumit.chac...@gmail.com wrote: Hi, I'm trying to design a invite twitter friends feature (similar to the invite facebook friends concept). Sadly its not drop some code, like Facebook is... I'll have to develop from scratch. Wondering whats the most scalable way of doing this? Details: #1 By friends of course means followers since I can direct message them #2 The graph API call returns ID's, I would have to make $n api calls to get details on each of the $n id's right? Getting the users name, picture etc. ? #3 Then when the user selects users to invite, and presses submit then I'll have to make $m direct message calls ($m $n)? Sounds like a lot of API calls to achieve something really simple. anyone have ways of doing this nicely? I would love to eliminate calls in #2 if possible. Cheers! Sumit
[twitter-dev] Re: stopping bit.ly automatic shortening of urls
I am curious if there has ever been an official response from twitter on why some simple HTML has not been allowed in a tweet? If we were able to use an anchor tag, and the HTML did not count against the 140 character limit, then the need for a URL shortener service would not be needed. On Jul 8, 10:27 am, sull sullele...@gmail.com wrote: ironically, my example urls are shortened here ;) On Jul 8, 12:20 pm, sull sullele...@gmail.com wrote: this is a topic of interest to me for a long while. been meaning to start a thread. i'm often bothered by the automatic shortening of urls when in fact the url does not need to be shortened. in these cases, i of course do not want to hide the real url by using a forced 3rd party service like bit.ly. i have use cases where all that is posted is a url. and the url includes a long detailed description of the link. this, in my opinion, is smart as the only object to maintain is the url itself which provides a hyperlink and a short message combined. sometimes, these use cases are using natural language vanity urls to form short sentences. ie.http://john.tot.al.ly/wiped-out-on-this-huge-wave-in-hawaii-at-the-Su... the other annoying thing that is related to the twitter UI is how long urls are cut-off//trimmed even if they dont need to be. the above example would be destroyed because it would result in something like: http://john.tot.al.ly/wip actually, i'm not certain if that is still the case as it seems to me that every url is shortened with bit.ly now. i grok the value in tracking urls and bit.ly may be bought by twitter at some point and this notion of url tracking will be fully integrated but the debate about url shortners in general how they can break the natural web, are vulnerable to massive broken links and simply thr cryptic format itself that hides the true location are all to be considered and continued to be debated. at the very least, 3rd party developers should get an override toggle. that is something i think we all need to start demanding. and yes, an official doc explaining the current and future impementations of url shortening on twitter is definitely needed now. http://plea.se/twitter-dont-shorten-this-url-with-bitly-since-it-does... http://twitter.com/sull/status/2534470050 @sull On Jul 8, 4:50 am, Swaroop rh.swar...@gmail.com wrote: However, if you paste in a link that is less than 30 characters, we'll post it in its entirety. If it's longer than 30 characters, we'll convert it to a shorter URL. Source:http://help.twitter.com/portal
[twitter-dev] Whitelist Limits
From what I can tell, the white list limits are 20,000 calls per hour. I am curious if any app out there has come close to hitting that limit yet, and if so could you provide some usage details about your application? I am trying to make a decision about creating a single user desktop app vs a multi user web app. I really want to create it as a web app, but I am concerned about the long term viability of the white list limit.
