On 12/5/05, Jeff Licquia <[EMAIL PROTECTED]> wrote: > > Iris (Psi, Kopete) doesn't seem to use the hash at all. I was unable to > find other examples of avatar handling in client source.
The Pedrito build of Psi _does_ cache images, you would have to check the patches applied there to make sure. > The JEP should probably be clearer on this point. I have a bone to pick with 'base64' encoding. Some implementations create a newline after every 64 characters, others don't. Across different platforms, these newlines will differ: \n (*nix) vs \r\n (win32) vs \r (mac). As an absolute minimum _if_ the hash is computed using the base64 encoded data, the newlines must be removed. All this confusion is removed if the hash is computed on the raw image data. Also it's far simpler to compute the hash on the raw data using _any_ tool. (i.e. openssl, sha1sum, etc) -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Mon Dec 5 17:29:27 2005 From: [EMAIL PROTECTED] (Pedro Melo) Date: Mon Dec 5 17:29:43 2005 Subject: [py-transports] PyMSN-t avtar hash In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Hi Another solution for this, would be to treat the hash as an opaque value. That means that the client should store the image and the hash that was used. This way, it doesn't matter how the hash was generated. Best regards, On Dec 5, 2005, at 2:59 PM, Norman Rasmussen wrote: > On 12/5/05, Jeff Licquia <[EMAIL PROTECTED]> wrote: >> >> Iris (Psi, Kopete) doesn't seem to use the hash at all. I was >> unable to >> find other examples of avatar handling in client source. > > The Pedrito build of Psi _does_ cache images, you would have to check > the patches applied there to make sure. > >> The JEP should probably be clearer on this point. > > I have a bone to pick with 'base64' encoding. Some implementations > create a newline after every 64 characters, others don't. Across > different platforms, these newlines will differ: \n (*nix) vs \r\n > (win32) vs \r (mac). As an absolute minimum _if_ the hash is computed > using the base64 encoded data, the newlines must be removed. > > All this confusion is removed if the hash is computed on the raw image > data. Also it's far simpler to compute the hash on the raw data using > _any_ tool. (i.e. openssl, sha1sum, etc) > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports -- HIId: Pedro Melo SMTP: [EMAIL PROTECTED] XMPP: [EMAIL PROTECTED]
