You can also take a look at one of my apps that pulls out a lot of
this data for any (public) Twitter user.
http://tweetstats.com/graphs/dacort shows my activity since I joined
Twitter and can be broken down by month.
I'd be very interested in hearing your conclusions, feel free to let
me know
Nope, not possible. Streaming API tokenizes on space and punctuation.
So you'll have to come up with the variants and provide those.
Damon
On Oct 10, 6:28 am, D. Smith emai...@sharedlog.com wrote:
For example I want is to search for words that have 'truck' in it and
want to get all tweets that
Just wanted to chime in that the documentation is, indeed, pretty
confusing. I'd suggest the description paragraph beginning with
something like:
This parameter is only available to Firehose, Retweet, Link, Birddog
and Shadow clients.
I assume the recommended approach to not missing data on
I built TweepSearch.com to do this.
Example:
http://tweepsearch.com/search?query=name:joe+location:montrealcommit=Do+Your+Thing!
Your milage may vary - the site is definitely slow at the moment and
somewhat out-of-date.
Damon
On Jul 13, 2:28 pm, PhilGo20 gauvin.phili...@gmail.com wrote:
+1 on this, I'd like to know the answer as well.
Damon/@dacort
On Jun 8, 4:43 pm, Jim Gilliam j...@gilliam.com wrote:
Will we be able to get matches on the original URL through the streaming
API?
For example, I'm tracking act so I can match tweets that link to
'http://act.ly'. Will I
I heard somewhere that the list count is supposed to be included in
the user object at some point, although I can't remember where I heard
that/what the timeline was.
Until then, best solution appears to be (I hate to say it) scraping
the website. Otherwise, the API calls could get out of hand
Saw this as well right around 3pm PST. Not sure if newlines were
coming through or not, traffic graph shows a small amount of traffic
coming in as opposed to 0 so possibly.
On Apr 1, 3:46 pm, Chad Etzel jazzyc...@gmail.com wrote:
Hi all,
I am using the filter stream, and twice in the last 24
Curious why you're using a varchar field for protected as opposed to
tinyint(1)/boolean? I don't see a verified field either, not sure if
that's necessary for FoF.
Other than that, most of my stuff is pretty similar although I'm not
quite as discerning on the lengths of the fields. I usually just
Hi folks,
I'm Damon Cortesi (@dacort) and have been addicted to building Twitter
apps for the past two years now. I wrote my first Twitter app in 2007.
It was a perl script that downloaded your tweets and inserted them
into an iWork Numbers template to graph your timeline and top
replies[1]. That
Hey John,
+1 on experiencing that issue this morning. Let me know if there's any
way I can help.
dpc
On Feb 22, 10:51 am, John Kalucki j...@twitter.com wrote:
A number of developers have reported abandoned connection issues on the
Streaming API starting, perhaps, about two weeks ago. The
Your assumption is correct. You'll have to do your own parsing.
On Feb 2, 12:52 pm, Ronald ronald.bradf...@gmail.com wrote:
I'm presently migrating some of my code base to the Streaming API, and
I have a question regarding the filter/track syntax.
Currently I run multiple searches on
at the documentation and the filtering.
-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.
On Sun, Jan 10, 2010 at 12:17 PM, Damon C d.lifehac...@gmail.com wrote:
OK, so it looks like I misunderstood the docs, as it relates to the
punctuation.
I understood this:
Terms are exact-matched
This question is directed towards John, but happy to hear how other
folks do it as well.
I've got a couple questions regarding the tokenizing process on the
streaming API. This would be remedied pretty easily with an example
from Twitter as to their tokenizing process/regexp as I'm slightly
it won't. And I'm still
wondering what exactly Twitter defines as punctuation.
dpc
On Jan 10, 11:44 am, Damon C d.lifehac...@gmail.com wrote:
This question is directed towards John, but happy to hear how other
folks do it as well.
I've got a couple questions regarding the tokenizing process
I've got a quick question on the rate limiting of the streaming API.
The documentation states the following:
Each account may create only one standing connection to the Streaming
API.
Does this mean that I have to use two separate accounts if I want to
connect to both statuses/sample and
Just had an odd occurrence over on TweetStats. There's a user
(@dillaweezer) whose account was created in Apr 2009, but he somehow
has one tweet from Oct. 2008. Any idea how/why this happened?
User id: 36811640
created_at: Thu Apr 30 23:31:53 + 2009
Status id: 3439822377
created_at: Sat Oct
Hi,
Working on OAuth'ing some of my apps today and noticed that the
authenticate (vs. authorize) feature appears to have been disabled
since some time last night?
Was just curious if there was an updated status about this?
Thanks,
Damon
--
Damon P. Cortesi
Security Guy, Twitter Apps
Blog:
I've seen this from time-to-time before, but could never really pin it
down to specific users or timeframes.
In any case, I frequently see inconsistencies between the data in XML
and JSON representations. The example I came across last night was
with the ActiveRainMaker account. The caches have
Dan,
You can use the Gnip notification feeds to obtain some of this
information. For example, their data provides the user that is being
replied to and I use this to create the Top 10 @replies on
http://tweetstats.com/twitter_stats
dpc
On Feb 7, 4:10 pm, Dan slightlyoffb...@gmail.com wrote:
Naveen,
If you follow the protected person on Twitter (and they allow it), you
can then fetch their updates by logging in with that account.
This is one way to make it work w/o requesting their username and
password. :)
On Feb 2, 8:52 am, Naveen naveen.s.sax...@gmail.com wrote:
I have some
:
Maybe we've made a terrible omission in our documentation, but the
count parameter is for limiting downwards, not upwards. If you only
want 5 statuses in a timeline rather than 20, count is a-okay. But it
isn't meant for pushing up the number of statuses returned.
Damon C wrote:
Twitter-folk
This can also be retrieved using any valid Twitter account. One thing
to note, however, is that the relationship data in these queries is
not always accurate (or existent). There's an open ticket for this:
http://code.google.com/p/twitter-api/issues/detail?id=234
This is the main reason that I
Not at this time, but it is in the future plans. (unless Twitter
scoops me and releases their own bio search in the near future. ;))
On Jan 23, 9:47 pm, Bill bill.kid...@gmail.com wrote:
Very cool. Does tweepsearch have an API?
Bill
On Jan 23, 10:06 am, Damon C d.lifehac...@gmail.com wrote
.
Besides that, really nice job.
Best regards,
Fábio Silva.
On Sat, Jan 24, 2009 at 2:47 AM, Bill bill.kid...@gmail.com wrote:
Very cool. Does tweepsearch have an API?
Bill
On Jan 23, 10:06 am, Damon C d.lifehac...@gmail.com wrote:
Hi Bill,
I've actually put up a site recently
Hi Bill,
I've actually put up a site recently that can do this. The initial
goal was to limit to your followers, but it can search any indexed
profile as well.
It's at http://tweepsearch.com
I expect Twitter to come out with a profile search at some point, but
until then...I'll keep this
The only reply I can think of for this is HOT!
I just spent the past couple weeks building a service to search ones
followers (http://tweepsearch.com) and I still feel bad about pounding
the API. This will make it _much_ easier.
Thanks for making this change!
dpc
On Jan 22, 2:46 pm, Alex
Assuming you guys are aware, but just in case. Seems a change to the
API (to remedy the privacy leak, I'm assuming) is now causing Twitter
badges on blogs to request API auth.
On Jan 6, 12:20 am, Chris Heilmann chris.heilm...@gmail.com wrote:
I find this to be particularly concerning from a privacy point of
view.
You can retrieve enough information about a user to even replicate
their home page. This could be particularly damaging from a phishing
point of
Hi Alex,
Thanks for the updates - one of the things I noticed is that the
archive API method was marked as wontfix. I was wondering what this
means for the future of accessing our Twitter history?
Is this just something where we won't be able to export it in one
shot, but still have access to
29 matches
Mail list logo
