Re: [twitter-dev] friends/ids JSON API
Yes, this will be supported also. We should have the support rolling out very early this week. It will be triggered via a query parameter: stringify_ids=true This will apply to the following: - friends/ids.json - followers/ids.json - blocks/blocking/ids.json - friendships/no_retweets/ids.json - statuses/:status_id/retweeted_by/ids.json Thanks, Taylor On Tue, Oct 26, 2010 at 2:24 AM, Alex B wrote: > Will this be updating to the snowflake id strs workaround? Currently > it delivers ints in an array. > > I'd like to propose a flag on all JSON API calls (? > ids_as_strings=true) to deliver ids as strings instead of ints. This > could apply to the cursor problem we saw earlier. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends/ids and followers/ids not working in oauth
Instead of the console, if you are running some type of linux or unix [unix on osx/mac - terminal], just write a simple function to display results. i just have a function to grab a file or array and just use php to print_r(jsonfilehereorarray); On Oct 25, 2010, at 10:23 AM, Taylor Singletary wrote: The console on dev.twitter.com is unreliable. I recommend using Apigee's great Twitter console instead http://app.apigee.com/console/twitter http://app.apigee.com/console/twitter#apimet=http%3A//api.twitter.com/1/friends/ids.json%3Fuser_id%3D1497__apiidx__%3Dnull__apisecure__%3Dtrue__apiprovider__%3Dtwitter for a good example. We're working on showing our current bug-ridden console who's boss. Taylor On Mon, Oct 25, 2010 at 1:28 AM, jlezard wrote: Hello, If you use the console to call the method friends/ids (like http://api.twitter.com/1/friends/ids.json?user_id=12345 ) it no longer returns a nicely formated json, in fact it returns something completly wrong like 4 ids for someone who has 250 friends I was heavily relying on this method for my app, is there going to be a fix to this ? Thanks a lot Note: I can still get the friend ids with basic auth but then the limit is 150 which is not sufficient. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends/ids and followers/ids not working in oauth
there is a current ticket on ids, also did you notice the newer id_str
versus id, use that -
and don't use the console it's limiting.
$parameters = array("screen_name" => "BARACKOBAMA", "cursor" =>
$cursor);
$method = "followers/ids";
$followers = $this->connection->get($method, $parameters);
Max return of 5000 ids minus suspended users. More than 5000, paginate
with next_cursor_str and start with "cursor" always being "-1" the
first page, this will be eventually deprecated and automatic in all
requests as pagination cursor being "-1" [it's a string]
- Slate
On Oct 25, 2010, at 4:28 AM, jlezard wrote:
Hello,
If you use the console to call the method friends/ids (like
http://api.twitter.com/1/friends/ids.json?user_id=12345
) it no longer returns a nicely formated json, in fact it returns
something completly wrong like 4 ids for someone who has 250
friends
I was heavily relying on this method for my app, is there going to be
a fix to this ?
Thanks a lot
Note: I can still get the friend ids with basic auth but then the
limit is 150 which is not sufficient.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends/ids and followers/ids not working in oauth
The console on dev.twitter.com is unreliable. I recommend using Apigee's great Twitter console instead http://app.apigee.com/console/twitter http://app.apigee.com/console/twitter#apimet=http%3A//api.twitter.com/1/friends/ids.json%3Fuser_id%3D1497__apiidx__%3Dnull__apisecure__%3Dtrue__apiprovider__%3Dtwitterfor a good example. We're working on showing our current bug-ridden console who's boss. Taylor On Mon, Oct 25, 2010 at 1:28 AM, jlezard wrote: > Hello, > > If you use the console to call the method friends/ids (like > http://api.twitter.com/1/friends/ids.json?user_id=12345 > ) it no longer returns a nicely formated json, in fact it returns > something completly wrong like 4 ids for someone who has 250 > friends > > I was heavily relying on this method for my app, is there going to be > a fix to this ? > > > Thanks a lot > > > > Note: I can still get the friend ids with basic auth but then the > limit is 150 which is not sufficient. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends list in Site Stream
Yes, my program is making hundreds of connections to *Site* Stream and receiving updates for tens of thousands of users. -- @N On Wed, Oct 20, 2010 at 12:08 PM, Tom van der Woerdt wrote: > Your programs? Are you sure you don't mean User Streams? > > Tom > > > On 10/20/10 8:53 PM, Naoki Hiroshima wrote: >> Ok, maybe it's trivial in terms of the size of data sent from the >> server. But it seems taking a long time to receive all of those lists, >> and be ready to get status updates. >> If allowed, I'd like my programs to receive status updates as soon as >> they get connected. >> >> -- @N >> >> >> >> On Wed, Oct 20, 2010 at 9:20 AM, John Kalucki wrote: >>> This amount of data is trivial compared to the total amount of data sent >>> over Site Streams. The friends list per user is roughly the size of a tweet >>> or two. We have to weigh the cost of maintaining the feature vs. the >>> bandwidth and CPU savings. Unless the savings is significant, generally the >>> optimal solution is to let the client discard unneeded data. >>> -John >>> >>> >>> >>> On Tue, Oct 19, 2010 at 5:16 PM, N wrote: Hi there, I've been playing with Site Stream for a bit, and I have a request. When a client connects to the server, it returns a series of the friend list for each users. Can you make this optional? Receiving a lot of friends data for thousands of users is a quite bit of trafic and wasteful unless it's really needed. I'd be very happy if I wouldn't have to receive it when I don't need. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk >>> >>> -- >>> Twitter developer documentation and resources: http://dev.twitter.com/doc >>> API updates via Twitter: http://twitter.com/twitterapi >>> Issues/Enhancements Tracker: >>> http://code.google.com/p/twitter-api/issues/list >>> Change your membership to this group: >>> http://groups.google.com/group/twitter-development-talk >>> >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends list in Site Stream
Your programs? Are you sure you don't mean User Streams? Tom On 10/20/10 8:53 PM, Naoki Hiroshima wrote: > Ok, maybe it's trivial in terms of the size of data sent from the > server. But it seems taking a long time to receive all of those lists, > and be ready to get status updates. > If allowed, I'd like my programs to receive status updates as soon as > they get connected. > > -- @N > > > > On Wed, Oct 20, 2010 at 9:20 AM, John Kalucki wrote: >> This amount of data is trivial compared to the total amount of data sent >> over Site Streams. The friends list per user is roughly the size of a tweet >> or two. We have to weigh the cost of maintaining the feature vs. the >> bandwidth and CPU savings. Unless the savings is significant, generally the >> optimal solution is to let the client discard unneeded data. >> -John >> >> >> >> On Tue, Oct 19, 2010 at 5:16 PM, N wrote: >>> >>> Hi there, >>> >>> I've been playing with Site Stream for a bit, and I have a request. >>> >>> When a client connects to the server, it returns a series of the >>> friend list for each users. Can you make this optional? Receiving a >>> lot of friends data for thousands of users is a quite bit of trafic >>> and wasteful unless it's really needed. I'd be very happy if I >>> wouldn't have to receive it when I don't need. >>> >>> -- >>> Twitter developer documentation and resources: http://dev.twitter.com/doc >>> API updates via Twitter: http://twitter.com/twitterapi >>> Issues/Enhancements Tracker: >>> http://code.google.com/p/twitter-api/issues/list >>> Change your membership to this group: >>> http://groups.google.com/group/twitter-development-talk >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends list in Site Stream
Ok, maybe it's trivial in terms of the size of data sent from the server. But it seems taking a long time to receive all of those lists, and be ready to get status updates. If allowed, I'd like my programs to receive status updates as soon as they get connected. -- @N On Wed, Oct 20, 2010 at 9:20 AM, John Kalucki wrote: > This amount of data is trivial compared to the total amount of data sent > over Site Streams. The friends list per user is roughly the size of a tweet > or two. We have to weigh the cost of maintaining the feature vs. the > bandwidth and CPU savings. Unless the savings is significant, generally the > optimal solution is to let the client discard unneeded data. > -John > > > > On Tue, Oct 19, 2010 at 5:16 PM, N wrote: >> >> Hi there, >> >> I've been playing with Site Stream for a bit, and I have a request. >> >> When a client connects to the server, it returns a series of the >> friend list for each users. Can you make this optional? Receiving a >> lot of friends data for thousands of users is a quite bit of trafic >> and wasteful unless it's really needed. I'd be very happy if I >> wouldn't have to receive it when I don't need. >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends list in Site Stream
This amount of data is trivial compared to the total amount of data sent over Site Streams. The friends list per user is roughly the size of a tweet or two. We have to weigh the cost of maintaining the feature vs. the bandwidth and CPU savings. Unless the savings is significant, generally the optimal solution is to let the client discard unneeded data. -John On Tue, Oct 19, 2010 at 5:16 PM, N wrote: > Hi there, > > I've been playing with Site Stream for a bit, and I have a request. > > When a client connects to the server, it returns a series of the > friend list for each users. Can you make this optional? Receiving a > lot of friends data for thousands of users is a quite bit of trafic > and wasteful unless it's really needed. I'd be very happy if I > wouldn't have to receive it when I don't need. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends/ids requires authentication now?
Hi UncleYa, We have some lingering issues from the basic auth shut off that result in the occasional, incorrect error like this when being rate limited. Hope to have those all cleaned up soon. Part of your post suggests you may have been getting a different kind of error when you application was accessing these methods.. do you know what errors you were receiving? You should be prepared for a few different kinds of exceptions when accessing any resources.. Taylor On Thu, Sep 16, 2010 at 5:24 AM, UncleYa wrote: > Hello. Today I was testing my web-application that uses "friends/ids" > API function. First several times all was correct. But later > application stopped working. That isn't rate limiting. And, when I > call this function through browser (entering something like this > "http://api.twitter.com/1/friends/ids/uncleyaru.xml";) it returns > "Basic authentication is not supported". > Will this function be rate limited or it's temporary? Thank you. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Friends
Hey,
I'm not sure which library you are using here, could you explain the
language you are using and a link to the library so we can help debug.
Thanks,
Matt
On Thu, Aug 26, 2010 at 2:23 PM, garyz wrote:
> Is anyone else having problem with TwitterOauth and friends?
>
> I'm trying to create friends with:
>
> ret = @client.friend("twittername")
>
> And the response I get is a null ret and "test" shows up on the
> console.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Friends and followers
Probably a naming mistake made early on that would have been too much effort to change later on. Clearly though, mutual following indicates "Friends" more that the unidirectional follow does. In my system, we say "following" and "friends" like you suggest. A bit confusing, but I think easier than coming up with a new word for mutual following. You can see it here: http://madison.imby.info/p/Philip.Crawford On Tue, May 25, 2010 at 10:43 PM, Miles Parker wrote: > This question is sort of pedantic, but I'm wondering why the API > refers to "friends" instead of "followers". The API say's that > "friends" == "following", but I understand (e.g. see this nice little > article > http://andrewchenblog.com/2009/03/16/friends-versus-followers-twitters-elegant-design-for-grouping-contacts/) > that "friends" are mutual followers, that is: > > 1. I follow you (following) -> > 2. You follow me (follower) <- > 3. We follow each other (friends) <-> > 4. Nada ø > > So would it be correct to substitute "following" for "friends" WRT to > API? To keep it straight on my side, I'm going to have to come up with > a word that means "friends" in the sense of 3 above. > -- imby - in my back yard An Experiment in Local Professional Networking http://madison.imby.info/p/Philip.Crawford
Re: [twitter-dev] Friends and followers
Twitter has evolved quite a bit over the last 4 years. It's not always possible to evolve the API at the same pace. I wouldn't say that mutual followers are friends. They're just mutual followers. On Tue, May 25, 2010 at 7:43 PM, Miles Parker wrote: > This question is sort of pedantic, but I'm wondering why the API > refers to "friends" instead of "followers". The API say's that > "friends" == "following", but I understand (e.g. see this nice little > article > http://andrewchenblog.com/2009/03/16/friends-versus-followers-twitters-elegant-design-for-grouping-contacts/ > ) > that "friends" are mutual followers, that is: > > 1. I follow you (following)-> > 2. You follow me (follower) <- > 3. We follow each other (friends)<-> > 4. Nada ø > > So would it be correct to substitute "following" for "friends" WRT to > API? To keep it straight on my side, I'm going to have to come up with > a word that means "friends" in the sense of 3 above. >
Re: [twitter-dev] friends/ids missing cursor information with oAuth?
Hi Andrew, I just did a few ad hoc tests and was able to get the fields to show up in JSON and XML responses, both with OAuth and using Basic Auth. Is it possible that when the value is zero to JSON key/pair, your implementation might be hiding the result from you in some way? Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Mon, Apr 26, 2010 at 11:47 PM, Andrew Horn wrote: > Hi all > > I've been working with the friends/ids endpoint and it seems that the > next_cursor and previous_cursor are missing from the json response if > oAuth is used to authenticate. The cursors are present using simple > auth. > > Is anyone else seeing this, or am I missing something? > > Thanks in advance, > Andrew Horn > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
