On Aug 17, 6:27 am, Chris Babcock <[email protected]> wrote: > When you know your code is going to be seen you either avoid doing > stupid things like hard coding credentials or you learn fast that > configuration data is not code. Fair enough. So how do you do it? How do I distribute a desktop or mobile device application - open source or closed - that uses my OAuth credentials in such a way as to protect my credentials from being discovered? Seriously, how do you do that?
- [twitter-dev] Re: Open Auth Jesse Stay
- [twitter-dev] Re: Open Auth Josh Roesslein
- [twitter-dev] Re: Open Auth sausman
- [twitter-dev] Re: Open Auth Kevin Mesiab
- [twitter-dev] Re: Open Auth Peter Denton
- [twitter-dev] Re: Open Auth Nicole Simon
- [twitter-dev] Re: Open Auth Andrew Badera
- [twitter-dev] Re: Open Auth Jason Martin
- Absurd Misunderstanding of Open Anything (Was:... Chris Babcock
- Re: Absurd Misunderstanding of Open Anythi... Duane Roelands
- Re: Absurd Misunderstanding of Open Anythi... Bill Kocik
- Re: Absurd Misunderstanding of Open A... Chris Babcock
- Re: Absurd Misunderstanding of Op... JDG
- Re: Absurd Misunderstanding of Op... Joseph Cheek
- Re: Absurd Misunderstanding of Op... Cameron Kaiser
- Re: Absurd Misunderstanding of Open Anythi... Joseph Cheek
- Re: Absurd Misunderstanding of Open A... srikanth reddy
- Re: Absurd Misunderstanding of Op... Chris Babcock
- Re: Absurd Misunderstanding of Op... srikanth reddy
- Re: Absurd Misunderstanding of Op... Chris Babcock
- Re: Absurd Misunderstanding of Op... srikanth reddy
