and
Authentication is secondary. So its not a question of comparing it
with Basic Auth over HTTPS.
These are just my thoughts.
Srikanth
On Tue, Aug 11, 2009 at 2:46 AM, Bradley S. O'Hearne brad.ohea...@gmail.com
wrote:
All,
I don't want to kick this subject to death
much to offer for desktop
apps.The debate goes on.
Sooner or later twitter is going to remove basic auth support. We
have no choice but to move on.
On Tue, Aug 11, 2009 at 8:27 PM, Bradley S. O'Hearne brad.ohea...@gmail.com
wrote:
Srikanth,
Thank you for your thoughts -- good ones
, at 12:58 PM, JDG wrote:
Why would it be hosted in your app? Why can't you open Safari?
On Tue, Aug 11, 2009 at 13:29, Bradley S. O'Hearne brad.ohea...@gmail.com
wrote:
Srikanth,
By third party i meant some one like 'TwitViewer' (some one who
would pay and register their app in appstore
Christopher,
It is good to see that someone understands the bigger picture here.
This conversation suffers from a presumption of a specific use-case
(web application communicating with Twitter), and a particular
presumption of trust, or lack thereof. The particular comments such as:
All,
Just a question along the same lines as Dmitriy's, and forwarding no
opinion one way or the other -- but I'm curious, as security
discussions often end up being debates about one particular facet of a
security scheme while not considering the big picture. What is the
breach that
Hello all,
I am trying to post a URL to a Twitter status that has a @ character
in it. The problem is probably obvious -- anyone know how to prevent
Twitter from interpreting the @ as a username?
Thanks,
Brad
. It's better for your customers
(security) and it's better for you because your customers can use your
application with peace of mind.
If YOU wouldn't hand over YOUR Twitter credentials to a stranger, it's
silly to expect your users to do so.
On Jul 30, 11:40 am, Bradley S. O'Hearne brad.ohea
