Knocking

[nadonomy]

[Mikaela]

Has there been any movement regarding supporting knocking? It's mentioned in the 1.2 spec announcement and I think it has been in spec since 1.1.

Platform specific issues:

• Implement Knocking on Element Android element-android#3875
• Implement Knocking on Element iOS element-ios#4731
• Implement Knocking on Element Web element-web#18655

[hex-m]

The upcoming Synapse 1.54 raises the default room version to 9. Newly created rooms on most servers will probably support knocking soon.

[Mikaela]

@daniellekirkwood What is the missing information? The spec? https://spec.matrix.org/latest/client-server-api/#knocking-on-rooms

[Mikaela]

Room version 9 is currently the default in spec and room version 10 introduced knock_restricted allowing merging knocking with restricted join rules.

There is a proposal to make 10 the new default matrix-org/matrix-spec-proposals#3904

Has there been any movement in Elements to support either? I would like at least the ability to see which rooms can join directly as per with "restricted " join rule, while I consider it as disservice for "knocking" to result the radio button just disappearing in room settings.

[Mikaela]

With the current Matrix spec version being 1.7 and current default room version being 10, which features knock_restricted as another join rule utilising knocking, I would like to ask again what the X-Needs-Info in the labels means? Does @nadonomy personally need to link to the spec as per the label description?

This issue is blocked awaiting information from the reporter

[mpeter50]

@daniellekirkwood Aftrer 3 years, we still do not know what information do you need. Does that mean no more information is needed?

I just recently found a room, #nheko:nheko.im, that I and other people cannot join, because apparently it can only be joined by knocking. Should I open a bug report for that?
Other clients have already implemented this feature.

[hex-m]

Knocking is a labs feature of element-web (ask to join) and seems to be implemented in element-x-ios and element-x-android.

[ara4n]

So I had someone asking about knocking yesterday and got nerdsniped into seeing what the remaining work might be. This resulted in:

• MSC4506 to define how to push admins when someone knocks on their rooms
• Rewriting MSC4233 to transparently remember which server a user knocked by

Synapse impls:

• Push relevant users if there's a knock on a room (MSC4506) synapse#19955
• Implement MSC4233: Remembering which server a user knocked through synapse#19956 (fixes Rescinding or declining a room join request over federation is not implemented synapse#18030)
• Reflect out-of-band leaves in MSC4222 state_after on sync synapse#19957
• Auto-join rooms when a knock is accepted synapse#19958 (fixes Auto-join rooms when knock accepted synapse#16307)
• Make sure calling /context on an out-of-band membership event doesn't 500 synapse#19959
• Don't 500 /sync when an always-included event has no state synapse#19960

Ruma draft of MSC4506: https://gist.github.com/ara4n/a8d8dae8d49bca976c847768f2330754

Client impls:

• Display pushes for knocks (MSC4506) element-x-ios#5874
• Advance the join room screen if we're autojoined by the server element-x-ios#5875 (fixes Auto-join rooms when knock accepted synapse#16307)
• Display push notifications for knocks element-x-android#7207
• Render an invite that arrives as a timeline member event as an invite push element-x-android#7208 (fixes Auto-join rooms when knock accepted synapse#16307)
• Render knock membership events in notifications element-web#34268

[hex-m]

Will knocking be compatible with e2ee history sharing?