If you are using Twitter with pino you probably noticed it stopped
working on September, 1, duly reported in
https://bugzilla.redhat.com/show_bug.cgi?id=629192

This was due to twitter forcing oauth authentication on all API
consumers, as explained by the gwibber author on ars technica:
http://arstechnica.com/security/guides/2010/09/twitter-a-case-study-on-how-to-do-oauth-wrong.ars

Now, one interesting sentence from the article is:
"""
Most FOSS client developers have simply chosen to embed their keys in
their source code with the hope that Twitter won't notice. I was about
to give up on Gwibber, but Canonical intervened on my behalf (special
thanks to Ken VanDine) and negotiated a compromise with Twitter that
will allow Gwibber to continue using the service.
"""

So I'm wondering if we can lobby the same exception for pino, which is
the default client we ship in the desktop spin

Thoughts?

-- 
Gianluca Sforna

http://morefedora.blogspot.com
http://identi.ca/giallu - http://twitter.com/giallu
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to