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
It seems that we are talking about two categories of applications.
1.) As in the subject of this thread, open-source CMS or other multi-
user, membership or blogging systems. This type of system usually has
some facility for the admin user/webmaster to change settings such as
admin email address,
oops. really, I had thought this through but got carried away with the
'transparent installation' idea.
During the installation, the user would authenticate (via the software
provider or directly with twitter?) - and then be delivered the
credentials. Sorry.
On Aug 31, 10:58 am, Ken
I think the issue is really that it is not a very elegant solution and
is outside the realm of a standard non-technical persons experience.
The whole idea of having the end-user register a pre-built app as
their own is cumbersome. That said it is the only real solution to the
dilemma. It is the
On Aug 18, 4:22 am, Ken k...@cimas.ch 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
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 from
Still no solution:
http://groups.google.com/group/twitter-development-talk/msg/58b4b54d41b3ce4f
After that initial message, it is apparently still not available...
I've released my module by explaining in the readme how webmasters can
add their own application and obtain the consumer public and
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 exactly hard to do. You just
Sorry for the confusion. I mean web application developers. There are
quit a number of open-source web apps for twitter. Besides standalone
apps, there are also, add-ons for all the various CMS solutions out
there, written in PHP, Perl, etc.
On Jul 27, 2:02 pm, M. Edward (Ed) Borasky
On Tue, Jul 27, 2010 at 17:02, M. Edward (Ed) Borasky
zn...@borasky-research.net 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
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
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
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
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
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
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
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
17 matches
Mail list logo
