Something like that. Ideally, what I would do is configure the app so that if the consumerkeys (both secret and non) are not present, the user is directed to a screen to input those for themselves (with maybe a helpful link to get them in the first place).



On Jan 18, 2010, at 9:46 AM, Raffi Krikorian wrote:

that's precisely what i would do - author your code to read from a
configuration file that contains the keys. don't distribute that
configuration file, but, instead, distribute a README or an example
configuration file that the end user would fill in.

On Mon, Jan 18, 2010 at 9:43 AM, John Meyer <john.l.me...@gmail.com
<mailto:john.l.me...@gmail.com>> wrote:

    On 1/18/2010 1:19 AM, Ryan McCue wrote:

        Hey guys,

        I'm looking to integrate Twitter posting into an application I'm
        developing. The catch to this is that because it's open
        source, and
        programmed in PHP, I'd have to distribute the secret key with it.

        What's the best way to go about this? I've fallen back onto the
        ordinary basic auth API for now.

        Thanks,
        Ryan.



    Technically, you don't. All opensource requires is that you
    distribute the source code, not the individual data. So you could
    specify that the secret key is in a particular file and then other
    users could insert their own secret key.




--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi


Reply via email to