-
MattJ
What spec are Movim/Monocles following for comments?
-
singpolyma
What are other people doing about this problem: <presence from muc/NICK><x xmlns=vcard-temp:x:update><photo>HASH</photo></x></presence> <iq GET VCARD TEMP /> <iq type="result"><vCard xmlns="vcard-temp"><PHOTO><TYPE>image/jpeg</TYPE></PHOTO></vCard></iq> so since I didn't get a photo, next time I get their presence they still claim they have one, and give me the hash for it, but I still don't have anything matching that hash so I fetch again... and again... and again...
-
singpolyma
I really wish whatever server is doing this would stop, but in lieu of that...
-
moparisthebest
cache the negative response for some time?
-
moparisthebest
or maybe forever...
-
singpolyma
forever would be a problem I think. but maybe "until next app start" or something yeah
-
moparisthebest
in theory next upload to fix it should upload correctly *then* set the new hash
-
moparisthebest
but yea... relying on clearly broken thing to do the right thing feels sketchy lol
-
singpolyma
I don't think the hash is wrong. I'm currently chasing it down but I think it's permissions related
-
singpolyma
yup, confirmed.
-
singpolyma
if avatar in prosody is set to "contacts only" then prosody always injects the hash to presence, but strips only the binary from the vcard-temp
-
singpolyma
if I fetch the same vcard-temp from a contact or a non-contact (including of course via a muc) it acts differently
-
singpolyma
which seems correct on the fetch side. but then I get this hash...
-
jjj333_p (any pronouns)
could that be wrong behavior on the prosody side?
-
singpolyma
IMHO yes it is
-
singpolyma
if I wouldn't allow the target jid to see the photo, then I shouldn't tell it about the photo hash in presence
-
singpolyma
IMHO
-
singpolyma
but maybe that's hard I dunno