EntitityCapabilities payload is not added to outgoing presence when presence have 'to' address
Issue #132
closed
Is there any reason why it should not be added to directed presence?
Comments (4)
-
repo owner -
reporter In case of ExternalComponent, presences are always have to address and this EntityCapsManager can not be used to attach capabilities when presences are generated on ExternalComponent side
-
repo owner - changed status to resolved
Add EntityCapabilities extension to every outbound presence
Don't omit if presence has a 'to' attribute.
Fixes issue
#132→ <<cset 2adf0f58b86b>>
-
repo owner - changed status to closed
Fixed with 0.8.0
- Log in to comment
Good question. This change dates back to 2014 (5abc5f1).
I think the reason was, that Caps as well as Avatar Updates (XEP-0153) and Last Activitiy (XEP-0256) were included in Presences, which are used to join/leave a MUC room, which I considered undesirable.
We could also check for the MUC extension in the presence, but this means we need the MUC dependencies/classes available in EntityCapsManager, which is currently not the case.