There are plenty of open source *library* developers, and plenty of applications that use open source libraries, but not all that many open source full applications. The only ones I can think of at the moment are Gwibber (Gnome), Choqok (KDE), mine (Social Media Analytics Research Toolkit), Spaz, get2gnow, and ttytter. IMHO Choqok and Gwibber are lame - I use CoTweet or on my desktop and, Twitter, Twidroid, Seesmic, Touiteur and Peep on my HTC Verizon Droid Incredible.

The Twitter piece of Social Media Analytics Research Toolkit is at the moment read only, and as I noted earlier the main reason I even looked at oAuth was to get the 1500 (read) API calls per hour. Given the small number of users I have at the moment, it wouldn't be all that difficult to "upgrade" them to oAuth and 350 calls per hour one at a time by hand - all that would be required is to license that piece of code separately. ;-)
M. Edward (Ed) Borasky

"A mathematician is a device for turning coffee into theorems." - Paul Erdos

Quoting Michael Babcock <>:

Correct me if I am wrong, but doesn't Twitter risk loosing a large
percentage of their third party open-source developers, by not having
a solid solution for the required OAuth security changes in time for
the deadline?

I can only guess, but, I would think that the open-source segment
would count for quite a large number of independent developers, all
eager to build for and promote the Twitter vision.


On Jul 27, 8:59 am, Taylor Singletary <>
Hi Folks,

There are a few hold ups to rolling this out more widely, the most pressing
being that we are currently unable to serve SSL content on there are also better solutions than this
rudimentary one that we simply
can't implement yet. We're also concerned with releasing (and supporting) a
solution widely that we'll soon want to deprecate.


On Tue, Jul 27, 2010 at 8:53 AM, Cameron Kaiser <>wrote:

> > I have the same question. I need to add Twitter OAuth to my widely
> > distributed PHP based open-source CMS add-on. All the documentation
> > says never ever distribute your consumer secret, which I understand
> > why this would be a bad idea. Yet all of the documentation/examples I
> > have found require that the consumer secret be hard-coded into the
> > source.

> > The closes thing I have found, that doesn't require the consumer
> > secret embedded in the source, is a description of how it might work,

> > But, I cannot find any docs/examples where this scenario has actually
> > been implemented.

> It does exist. While I can't speak for Twitter and whatever internal issues
> are slowing up its rollout, TTYtter has been a test bed for the key
> exchange
> for some time now. Most of the users have found the process painless. You
> can
> see how a sample workflow works in the documentation, or try it yourself.
> The
> app itself is open Perl.


> I'm sure Taylor will comment on what will be happening to roll it out to
> more
> potential consumers.

> --
> ------------------------------------ personal:
>  Cameron Kaiser * Floodgap Systems **
> -- People are weird. -- Law & Order SVU
> ---------------------------------------

Reply via email to