No, there's really not a good solution for open source developers. :(
On Jul 10, 3:57 pm, Cameron Kaiser spec...@floodgap.com wrote:
After reading that thread, it seems there is no good solution :(
That is also my conclusion.
--
Duane Roelands duane.roela...@gmail.com writes:
No, there's really not a good solution for open source developers. :(
If there really isn't a good solution for open source developers, there
isn't a good solution for *any* developers unless you're running through
a private proxy (and even that
No, there's really not a good solution for open source developers. :(
If there really isn't a good solution for open source developers, there
isn't a good solution for *any* developers unless you're running through
a private proxy (and even that has problems).
I think that the PIN
It's different from basic auth in the way that oauth was primarily designed
to be different -- the app need not know your password (thus preventing a
rogue app from stealing it) and it need not send it over the wire with every
request (thus preventing a rogue entity from monitoring and trapping it
There was just a long thread discussing these sorts of security issues.
The thread title is Security Best Practices and is at
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/45550d6cebf86051#
- h
On Fri, Jul 10, 2009 at 10:05, Grant Emsley grant.ems...@gmail.com
After reading that thread, it seems there is no good solution :(
On Jul 10, 1:17 pm, Howard Siegel hsie...@gmail.com wrote:
There was just a long thread discussing these sorts of security issues.
The thread title is Security Best Practices and is at
After reading that thread, it seems there is no good solution :(
That is also my conclusion.
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- 1-GHz Pentium-III + Java + XSLT ==
