On 2 March 2010 14:11, hcarvalhoalves <hcarvalhoal...@gmail.com> wrote:
> Sorry, I just saw Twitpic's documentation now [1]. > > What I can say, is that their implementation is a joke. > It's not that simple. Twitpic is usually used by 3rd party programs - not directly. So for example with Tweetdeck, if they wanted to integrate Twitpic I would have to use oauth to allow tweetdeck and then oauth again with twitpic and every other service. In other words, a horrible user experience - the same would apply to websites. There isn't a way to pass around tokens between services as its authenticated against their secret key. So you need to authenticate each of them individually or use the passwords. Anyway, basically you should at least store encrypted passwords as you can't store a hash. Something like this would help; http://www.djangosnippets.org/snippets/1095/. It isn't ideal but its better than plain text. I believe that snippet (or a variation of) is used in Pinax - so you may want to look there to see how they did it. It was discussed at the sprints at EuroDjangoCon, Prague last year. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
