Use the spritzer to sample tweets, but you only need to sample
follower_count data per user over time.
On May 26, 9:33 am, Ryan Bell wrote:
> Peter,
>
> I appreciate the suggestion, but am looking to provide the
> functionality naively in our client as we may end up competing with
> their service
If you spent 45 minutes browsing discussions about Dean Collins, then
you studied how spammers caused a made-for-spammers app to get banned.
If you prevent people from using your app in an abusive way, you won't
end up like Dean Collins.
I want to share with the group:
http://sagistech.blogspot.com/2010/03/parsing-twitter-json-comparing-c.html
The author compares different .NET JSON parsers, and determines that
Gapi.NET is the fastest at parsing Twitter JSON.
I'm using Gapi.NET for statuses/sample.json now, and it really is fast
Try a Plurk Client!
even ever logging in to
> Twitter.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
>
>
>
> On Fri, Mar 26, 2010 at 12:38 AM, mcfnord wrote:
> > I'd love a list of id's for active accounts and another list of id's
> >
I keep wondering if we can discuss data. We're all driving data API's
and some of us must save the data as we gather it. I'm gathering the
social graph (which accounts read which accounts). I'm sure many
people gather many datatypes and metrics. It makes some everybody-wins
sense to me to trade or
I think I know the answer to this question (YES), but I wanna clarify:
Everywhere in the docs that I see curl followed by credentials,
if the topic includes REST, that's an API that I will not be using
curl for,
because curl doesn't use oauth, so it cannot authenticate.
i'll certainly know in 30 d
I'm gonna poke some gentle fun at you here. I'm spidering the whole
social graph. I'm 25% done with my first pass. I will need two passes
to accomplish my goal. I hope to be done sometime in 2011.
You can limit your service to the vast majority of people who have far
fewer than one million followe
Hi, Abraham, and everyone.
I'm crawling twitter. (But who isn't, right?) Us social graph geeks
have our own advantages, and our own set of challenges.
For example, I would not want to manage the vastness of tweet volumes.
But I do get neck-deep in social graph data. Which means I crawl with
this:
I'd love a list of id's for active accounts and another list of id's
for inactive ones, by some sensible criteria of activity. Publishing
this is in twitter.com's interest, admittedly for that large first and
second crawl. I'm calling this for everyone:
http://twitter.com/friends/ids.xml/?user_id=
I'm storing integer arrays, a feature of PostgreSQL.
On Aug 15, 1:36 pm, Kevin Mesiab wrote:
> Your implementation here has much to do with how you intend to use the
> social graph.
>
> Are you simply caching, or do you intend to identify metrics by
> analyzing the shape of the relationships ove
This incident bounced around in my head today. I think Twitter does
not like the essential nature of this application, to contact members
of its userbase. I would like to know what users of the premium
Twitter Butler product included in their messages. I am designing a
mass-contact model now, and
12 matches
Mail list logo
