> I think it's far better developer/business practice to design
> *proprietary* applications that are secure and register them with Twitter
> using xAuth.
As has been said time and time again, "proprietary" is not a solution
for this, as any non-hosted app using OAuth can have the keys
extracted f
On Aug 18, 4:22 am, Ken wrote:
I am new to this thread having seen it over the past few weeks and
wondered what all the fuss was about.
The solution by MindcrimeNL above seems optimal, why is it a
workaround?
Do developers not really want their users to register their own
Twitter app? It's not
On Tue, Jul 27, 2010 at 17:02, M. Edward (Ed) Borasky
wrote:
> 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),
Is this scheme available for all open source applications to test, or
is TTYtter the only one using it at the moment?
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb
"A mathematician is a device for turning coffee into theorems." - Paul Erdos
Quoting Cameron Kai
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),
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
dev.twitter.com-- there are also better solutions than this
rudimentary one that we simply
can't implement yet. We're also concerned with releasing (and
> 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 requi
I too have been developing open source Twitter applications. I'm using
Perl though, not PHP. I am about to release all of my code that
operates *unauthenticated* in open source form, but I am strongly
leaning now towards *not* providing open source solutions for
authenticated access to the
