Re: Twitter support broken in Pino
2010/9/10 Bill Nottingham nott...@redhat.com: Bill Nottingham (nott...@redhat.com) said: The other option would be to switch to gwibber (which has been un-desktop-couched in Fedora 14, so it theoretically won't bring in nearly as much to the live image. So, actual testing - building a livecd with gwibber instead of pino brings in the following packages: PyXML 4185378 python-sexy 61194 python-oauth 50819 python-imaging 1381510 python-distutils-extra 133515 mx 6599955 libsexy 102616 gwibber 2367779 Resulting live image was 704MB. Note that not all of these appear to *actually* be required by gwibber - bug 632621 filed. Bill -- Hi all, I'll update pino to the latest snapshot for F14+ soon which already add support for oauth. Regards, Chen Lei -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Twitter support broken in Pino
Bill Nottingham (nott...@redhat.com) said: The other option would be to switch to gwibber (which has been un-desktop-couched in Fedora 14, so it theoretically won't bring in nearly as much to the live image. So, actual testing - building a livecd with gwibber instead of pino brings in the following packages: PyXML 4185378 python-sexy 61194 python-oauth50819 python-imaging 1381510 python-distutils-extra 133515 mx 6599955 libsexy 102616 gwibber 2367779 Resulting live image was 704MB. Note that not all of these appear to *actually* be required by gwibber - bug 632621 filed. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Twitter support broken in Pino
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
Re: Twitter support broken in Pino
Gianluca Sforna (gia...@gmail.com) said: 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 The other option would be to switch to gwibber (which has been un-desktop-couched in Fedora 14, so it theoretically won't bring in nearly as much to the live image. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Twitter support broken in Pino
On Fri, Sep 3, 2010 at 6:27 PM, Bill Nottingham nott...@redhat.com wrote: The other option would be to switch to gwibber (which has been un-desktop-couched in Fedora 14, so it theoretically won't bring in nearly as much to the live image. Certainly that's a better option than shipping F14 with a non functional twitter client. -- 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
