search

matrix-org / matrix-spec

The Matrix protocol specification
Apache License 2.0
178 stars 94 forks source link

Specify how inclusive appservices interact #288

Open turt2live opened 6 years ago

turt2live commented 6 years ago

Another question: if a join event for a room alias that should be forwarded to an app service comes in, and more than one app service's namespace matches it, should we GET /rooms/{roomAlias} on both app services, potentially creating two rooms? Because with the way things are currently set up, and alias namespaces aren't marked as exclusive, this could happen. API ref: https://matrix.org/docs/spec/application_service/unstable.html#get-rooms-roomalias

From @anoadragon453 in #dendrite-dev ( https://matrix.to/#/!FyQrGcOoVamcLcvdob:matrix.org/$15270053065148KAOsF:amorgan.xyz )

Related issue: https://github.com/matrix-org/matrix-doc/issues/559

anoadragon453 commented 6 years ago

In this case, we may want to require room and alias namespaces be exclusive?

turt2live commented 1 year ago

In this case, we may want to require room and alias namespaces be exclusive?

4 years late, but we can't if we also expect the users namespace to only be local: exclusivity on all rooms sounds... bad.