element-hq/element-call

Steps to reproduce Running element call in standalone mode hooked up to Continuwuity Start a new room as an anonymous user Copy the invite link and open in a new browser Outcome What did you expect? Joining the room works successfully What happened instead? An error occurs: and the logs show This is due to a conditional in element call that is supposed to assume the room's join_rule === public if it's not present, however the check is implemented incorrectly in certain cases: In this room summary response, the join_rule is not present. According to the spec for room summaries, join_rule missing should be interpreted as public. When Ruma (and by extension, Continuwuity) renders the json response for a room summary, it excludes the value if it's public - which complies with the spec. In order to fix this, I can simply: diff --git a/src/room/useLoadGroupCall.ts b/src/room/useLoadGroupCall.ts index 2cd0d40b..8a7617d8 100644 --- a/src/room/useLoadGroupCall.ts +++ b/src/room/useLoadGrou

Summary The default branch already hardened .github/workflows/blocked.yaml, .github/workflows/changelog-label.yml against the issue(s) below, but 4 release branches still carry it. This proposes the same, minimal, scanner-verified fix for each. What's flagged (by zizmor) unpinned-uses — actions referenced by mutable tag/branch instead of a pinned commit SHA Already resolved on the default branch in: cc8ab0a cf0cb2e Affected release branches (4) release-v0.9.0 (still present as of HEAD 4644fc89) release-v0.11.1 (still present as of HEAD b5f526f9) release-v0.11.0 (still present as of HEAD 6e9b837f) release-v0.8.0 (still present as of HEAD a2df8fae) Suggested per-branch patches Each diff below was checked locally with zizmor and actionlint: the flagged finding(s) are cleared on the affected construct and no new lint or security findings are introduced. (Whitespace is normalized; only security-relevant lines change.) release-v0.9.0 — unpinned-uses File .github/workflows/blocked.

Your use case What would you like to do? Review + update the reverse proxy snippets of the self hosting doc. Why would you like to do it? The snippets include the /sfu/get endpoint but not the /get_token endpoint. I believe /sfu/get is being depreciated in favor of /get_token. The snippets could have minor changes made to improve clarity. The Caddy snippet at least would have clearer context if it included the opening/closing lines of the block for the domain, and I don't believe adding that and /get_token would add excess clutter or make it a denser read for people reading through. How would you like to achieve it? I'm happy to make a PR for the Caddy changes as that's what I use (It'd be small enough I would have just done that instead of the issue but contributing.md says do the issue so why not), but ideally people familiar with and well versed in using nginx and haproxy would do a pass on those snippets to make sure they're clear and up-to-date as well. Have you considered any a

Potential solutions: The WidgetApi instance should be created in the matrix-js-sdk (maybe) Reexport all of the widget api through the matrix-js-sdk so EC does not depend on the matrix-widget-api directly use a peerDependencies depency to get warnings if versions dont match.

Your use case What would you like to do? Remind everyone of the passing time. Why would you like to do it? For professional meetings timekeeping is very important. How would you like to achieve it? Add another reaction with sound that is like an alarm clock, timer, etc. Have you considered any alternatives? Unfortunately, the ideal solution of everyone being disciplined is not always feasible. Additional context No response