You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
When processing a 3PID invite, the HS currently looks up the 3PID on the IS using v1/lookup.
MSC2134 has defined a v2/lookup API that supports using hashed addresses. (More discussion is needed to decide whether the HS should use hash alg none and continue to send plain text for this case or instead actually hash the value from HS to IS.)
Since the intention is to remove the v1 IS API down the road, we'll want to do this migration to cover all usages of v1.
The text was updated successfully, but these errors were encountered:
We believe this is code path is unused by Riot today, as it does the lookup itself, but it seems still important for other client where we don't know how they handle 3PID invites.
When processing a 3PID invite, the HS currently looks up the 3PID on the IS using
v1/lookup
.MSC2134 has defined a
v2/lookup
API that supports using hashed addresses. (More discussion is needed to decide whether the HS should use hash algnone
and continue to send plain text for this case or instead actually hash the value from HS to IS.)Since the intention is to remove the v1 IS API down the road, we'll want to do this migration to cover all usages of v1.
The text was updated successfully, but these errors were encountered: