That's a solution that better fits open source Twitter web services. For an open source desktop client like Spaz it certainly doesn't work.
On Tue, Jun 30, 2009 at 16:37, DWRoelands <duane.roela...@gmail.com> wrote: > > Wait, the solution is that every -user- of an open-source Twitter > client would have to register for their own set of -consumer- keys? > > That's not what you meant, is it? > > On Jun 30, 4:39 pm, Alex Payne <a...@twitter.com> wrote: > > The simplest solution is that every deployment of the tool will have to > > register for their own OAuth credentials. This isn't ideal. I'd inquire > over > > athttp://groups.google.com/group/oauth > > > > On Tue, Jun 30, 2009 at 06:04, DWRoelands <duane.roela...@gmail.com> > wrote: > > > > > This is really an excellent question. > > > > > If we're developing an open-source Twitter client, how are we supposed > > > to handle the consumer_key and consumer_key_secret? > > > > > On Jun 29, 7:58 pm, Support <supp...@yourhead.com> wrote: > > > > 2. Obfuscation of the application's registered "key" and "secret." > > > > Are there any best practices? What about an open source project? > > > > -- > > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
