home_timeline also includes both.
For user retweeted status i would just check if(status[i].retweeted_status
!= null and status[i].user.screen_name == currentuser)
But the problem comes when you have friends redundant status i.e
status[i].retweeted_status != null and status[i].user.screen_name !=
Thank you for the due dilligence (lol)... Resolved finally ... it was
a problem with percent encode and utf 8 encode of text (status), i
used huevuniverse to check
every step and finally was solved ... still some chararacter are
strange (latin characters), but it is working enough well ...
you
http://twitter.com/apps - Click on the App - Edit - Delete-Button
It's so simple. ;-)
Greetings from Germany
Lukas
I'm working on a twitter client and I want to take advantage of the
new official retweet. I just want to get the same thing like twitter
web retweeted by you. But the api doesn't contain any information
for whether a status is retweeted by me. So how can I get to know
this?
Thanks.
is this possible in any way that one twitter conversation will contain
only one tweet ? I am trying to show the twitter conversation chain in
my application. but sometimes it happens that the conversation chain
contains only one tweet. Now my understanding is that if a
conversation contains only
is this possible in any way that one twitter conversation will contain
only one tweet ? I am trying to show the twitter conversation chain in
my application. but sometimes it happens that the conversation chain
contains only one tweet. Now my understanding is that if a
conversation contains
I'm working on a twitter client and I want to take advantage of the
new official retweet. I just want to get the same thing like twitter
web retweeted by you. But the api doesn't contain any information
for whether a status is retweeted by me. So how can I get to know
this?
Native retweets are a new type of tweet, and do not show up as mentions. You
can cobble together an approximation using search, retweets_of_me, and
retweets that will get close, but I don't think you can be 100% sure to
catch all of them.
-- ivey
On Sat, Jan 2, 2010 at 5:35 PM, gstarsf
There is already an enhancement request for this:
http://code.google.com/p/twitter-api/issues/detail?id=1218
On Jan 4, 10:12 am, Michael Ivey michael.i...@gmail.com wrote:
Native retweets are a new type of tweet, and do not show up as mentions. You
can cobble together an approximation using
I am getting a 200 status message but no results for these two
accounts, in both atom and json, and they both definitely have tweets:
http://search.twitter.com/search.atom?q=from:lindsaylohan
http://search.twitter.com/search.atom?q=from:chucktodd
I don't want to postulate, but I wonder if there's
I've noticed that this is not always the case.
If I retweet an older tweet it shows up as a new tweet in
home_timeline. But if I retweet a tweet on the first page, call
home_timeline, it doesn't contain the retweet (only visible under
retweeted_by_me). Same occurrance happens on twitter.com but
Hello everyone!
I sure hope you can help. I am developing a web based app that
searches for location based tweets using the search API with json
results. I provide the longitude latitude via my own local database on
my server. Presently I'm limited to just the US and Canada but I'm
thinking I
done
On Jan 3, 4:06 pm, Mark McBride mmcbr...@twitter.com wrote:
John, can you open an issue on the code
tracker?http://code.google.com/p/twitter-api/issues
---Mark
http://twitter.com/mccv
On Sun, Jan 3, 2010 at 1:17 PM, John munz...@gmail.com wrote:
another thing i've noticed is
This is an issue we're currently working to resolve. Both of the
users you mentioned should be showing up in search results now.
---Mark
http://twitter.com/mccv
On Mon, Jan 4, 2010 at 10:37 AM, Ben magnetbo...@gmail.com wrote:
I am getting a 200 status message but no results for these
Anyone who can help me out here?
On 2 jan, 19:28, bnonews michaelvpop...@gmail.com wrote:
Hi,
In November I requested (from account @BreakingNews) to whitelist IP
208.74.120.146 so we no longer have rate limits. That IP belongs
towww.bnonews.com. Until now we stayed well below the rate
I have a private list and both on twitter.com and via GET list /
statuses, many tweets are missing. I confirmed this behavior by
comparing the most recent tweets of several users to their public
timelines.
Dewald, it should be noted that, of course, not all 200 request responses
are created equal and just because pulling down a response body with
hundreds of thousands of ids succeeds, it doesn't mean it doesn't cause a
substantial strain on our system. We want to make developing against the API
as
I think that's like asking someone: why do you eat food? But don't say
because it tastes good or nourishes you, because we already know
that! ;)
You guys presumably set the 5000 ids per cursor limit by analyzing
your user base and noting that one could still obtain the social graph
for the vast
I'm just now noticing this (I agree - why was this being announced over the
holidays???) - this will make it near impossible to process large users.
This is a *huge* change that just about kills any of the larger services
processing very large amounts of social graph data. Please reconsider
Ditto PJB :-)
On Mon, Jan 4, 2010 at 8:12 PM, PJB pjbmancun...@gmail.com wrote:
I think that's like asking someone: why do you eat food? But don't say
because it tastes good or nourishes you, because we already know
that! ;)
You guys presumably set the 5000 ids per cursor limit by
In my account, there's no list named 'design':
http://twitter.com/shortyawards/design
results in a 404 page
When I try to create one with that name, I get numbers appended to it:
curl -u .. -dname=design http://api.twitter.comtyawards/lists.xml
?xml version=1.0 encoding=UTF-8?
list
Some quick benchmarks...
Grabbed entire social graph for ~250 users, where each user has a
number of friends/followers between 0 and 80,000. I randomly used
both the cursor and cursor-less API methods.
5000 ids
cursor: 0.72 avg seconds
cursorless: 0.51 avg seconds
5000 to 10,000 ids
cursor:
The backend datastore returns following blocks in constant time,
regardless of the cursor depth. When I test a user with 100k+
followers via twitter.com using a ruby script, I see each cursored
block return in between 1.3 and 2.0 seconds, n=46, avg 1.59 seconds,
median 1.47 sec, stddev of .377,
Also, how do we get a business relationship set up? I've been asking for
that for years now.
Jesse
On Mon, Jan 4, 2010 at 10:16 PM, Jesse Stay jesses...@gmail.com wrote:
John, how are things going on the real-time social graph APIs? That would
solve a lot of things for me surrounding this.
On Jan 4, 8:58 pm, John Kalucki j...@twitter.com wrote:
at the moment). So, it seems that we're returning the data over home
DSL at between 2,500 and 4,000 ids per second, which seems like a
perfectly reasonable rate and variance.
It's certainly not reasonable to expect it to take 10+
Hi ,
Thanks for your reply.But actually i am talking about the
conversation thread returned by the twitter .I am using this url to get the
conversation thread as xml.
http://search.twitter.com/search/thread/statusid
Is there any scenario when twitter will return only one message in this
Ryan Sarver announced that we're going to provide an agreement
framework for Tweet data at Le Web last month. Until all that
licensing machinery is working well, we probably won't put any effort
into syndicating the social graph. At this point, social graph
syndication appears to be totally
I am frequently hitting rate limit. i know it happens when you do
more
than 150 search API call in a hour
int a[] =twitter.getFriendsIDs(xyz).getIDs();
int b[][] = new int[a.length][]
for(int i=0;ia.length;i++)
b[i] = twitter.getFriendsIDs(a[i]).getIDs();
now the problem is a.length = 148 , that
The existing APIs stopped providing accurate data about a year ago
and degraded substantially over a period of just a few months. Now the
only data store for social graph data requires cursors to access
complete sets. Pagination is just not possible with the same latency
at this scale without an
As noted in this thread, the fact that cursor-less methods for friends/
followers ids will be deprecated was newly announced on December 22.
In fact, the API documentation still clearly indicates that cursors
are optional, and that their absence will return a complete social
graph. E.g.:
~300,000 ids in 15 seconds:
$ time curl http://twitter.com/followers/ids.xml?screen_name=dougw /
dev/null
% Total% Received % Xferd Average Speed TimeTime
Time Current
Dload Upload Total Spent
Left Speed
100 5545k 100 5545k0 0 346k
Again, ditto PJB - just making sure the Twitter devs don't think PJB is
alone in this. I'm sure Dewald and many other developers, including those
unaware of this (is it even on the status blog?) agree. I'm also seeing
similar results to PJB in my benchmarks. cursor-less is much, much faster.
At
32 matches
Mail list logo
