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 th
So, I after spending the day looking through documentation,
developer's discussion and testing various OAuth code bits, it is my
understanding that there is no secure OAuth solution for open-source
PHP developers. But, the August 16th deadline is still looming. And I
have to be able to integrate, t
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
So, I think the solution has to be that the user downloads my app,
installs it on their site, then registers my app as their own app with
dev.twitter. After which, they will receive their own key & secret
pair. They will then input their key & secret pair into my app which
is living on their site,
o "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) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb
>
> "A mathematici
al threat in exposing them to customers.
> - You can let them use the new Twitter extension for open source
> twitter clients - although I am not sure whether it's ready yet.
>
> Tom
>
> On Aug 1, 1:49 am, Michael Babcock wrote:
>
> > So, I think the solution has to be
ining in the readme how webmasters can
> > add their own application and obtain the consumer public and secret
> > key for their application and giving them an option to enter them in
> > the module.
> > I'm not really happy about this workaround... It just sucks...
>
&
Well, as a testimony to this less than elegant solution (IMHO), I have
rolled out my app (a PHP add-on for a popular CMS) with the the
customer_key and customer_secret fields blank in a settings type
control panel (db storage). I was very clear to provide a thorough
walk through of the dev.twitter.
