Peter Saint-Andre wrote:
Zenon Kuder jr. wrote:Actually the idea (I talked with Pavel by IM a bit) is that client a) either uses hash, checks the incoming data and caches per hashor b) doesn't know the hash or hash wasn't used or doesn't support hashes and then caches per JID and per the unique string.I hope I got it right and clear :-).Yes, that seems good.
We might even want to harmonize BoB with User Avatar (XEP-0084). There we have:
<metadata xmlns='urn:xmpp:avatar:metadata'>
<info bytes='size-of-image-data-in-bytes'
height='image-height-in-pixels'
id='SHA-1-hash-of-image-data'
type='content-type-of-image-data'
url='HTTP-URL-for-image-data'
width='image-width-in-pixels'/>
</metadata>
So hashes of user avatar images could be compared against BoB data, too
(without changing XEP-0084, unless we want to add a 'cid' attribute there).
/psa
smime.p7s
Description: S/MIME Cryptographic Signature
