Well I don't like that.. does anybody here think about user
experience? What is a rock solid security model good for, when nobody
uses it because it's just cumbersome? As always in life, trade offs
need to be made. I could design a black box where nothing would ever
get in or out, but this box
My Desktop Client is also depending on since_id right now in order to
display the user all new tweets since he logged out. Also without
since_id and max_id it's not really possible to implemente a more
link at the bottom.
Personally, for my needs it would be enough if since_id and max_id
would be
Hi,
the developer wiki mentions that the source parameter is no longer
recommended, because using oauth, twitter can already know the source
of messages.
However, there are a few use case scenario's that are limited if
source is only available through oauth.
Oauth is all about delegated
)
Besides; all the examples you mention are for delegated
authentication; it would be weird to have a headless system that is
working as a service implement an oauth scheme.
greetings,
Ivo
On Sep 14, 12:09 pm, Andrew Badera and...@badera.us wrote:
With all the freely available examples, and all
