Services, API keys, tests, etc.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, So I've got two Services packages that are pretty much ready to go. Services_Facebook is a ground up fully functional interface to all of the Facebook endpoints (it even supports photo uploads, which *ahem* Facebook's own doesn't). Services_Flickr is a package I coded over a year ago and my lazy ass just never finished. Now, both of these services have both public'ish API keys and secrets. The problem I have is publicly exposing my API keys and secrets via my package's tests. With Facebook it's minimized because you have to add the Services_Facebook PEAR application to your profile (I've created a junk account specifically for the tests), but Flickr is a bit more open I think, though you'd need to give the package access to your Flickr account before write operations could happen. I suppose I could create a junk Flickr account and do the same thing I did with Facebook ... Thoughts? - --Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG8HO/h0MUGpYY9OQRAhoOAKDIOnZcfFul3BQXWfgM0kYhw2wEsACeMju2 2Oc8pviy71viKh/vOoqmoyg= =ibm0 -----END PGP SIGNATURE-----