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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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
