LotusGuild/cinny
3
0
Fork 0
Code Issues 27 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Room invite links and QR codes use matrix.to, which can't open Lotus Chat #285

New Issue
Closed
opened 2026-10-04 19:50:21 -04:00 by jared · 1 comment
jared commented 2026-10-04 19:50:21 -04:00
Owner
Copy Link
Copy Source

What happens
These all produce https://matrix.to/#/!room…?via=…:

  • Room Settings → General → Share Room (link and "Download QR"): src/app/features/common-settings/general/RoomShareInvite.tsx:42.
  • The Invite dialog's Copy Link and QR Code: src/app/components/invite-user-prompt/InviteUserPrompt.tsx:81.
  • Space "Copy Link": src/app/pages/client/sidebar/SpaceTabs.tsx:142, src/app/pages/client/space/Space.tsx:127.

The #130 work documents that matrix.to cannot be pointed at this deployment: its Cinny adapter is hard-coded to app.cinny.in, and web-instance[] only works for Element. So a friend scanning the room's QR or clicking the invite link is offered Element or app.cinny.in, not chat.lotusguild.org.

Fix: use getLotusRoomPermalink(useLotusShareBase(), …) (already used by "Copy Lotus Link", and correct on desktop via webAppUrl) for these share and QR paths. Optionally keep a secondary "Copy matrix.to link" for people on other clients.

Last touched by a4615439 (2026-09-12, via-server resolver).

Acceptance criteria: the QR decodes to https://chat.lotusguild.org/home/!room…?viaServers=…, and a logged-out visitor lands on login and then the room.

Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny 30e2dbcd, cinny-desktop 8f67ec7, element-call 3b0050e8.

**What happens** These all produce `https://matrix.to/#/!room…?via=…`: - Room Settings → General → **Share Room** (link and "Download QR"): src/app/features/common-settings/general/RoomShareInvite.tsx:42. - The **Invite** dialog's Copy Link and QR Code: src/app/components/invite-user-prompt/InviteUserPrompt.tsx:81. - Space "Copy Link": src/app/pages/client/sidebar/SpaceTabs.tsx:142, src/app/pages/client/space/Space.tsx:127. The #130 work documents that matrix.to **cannot** be pointed at this deployment: its Cinny adapter is hard-coded to app.cinny.in, and `web-instance[]` only works for Element. So a friend scanning the room's QR or clicking the invite link is offered Element or app.cinny.in, **not chat.lotusguild.org**. **Fix:** use `getLotusRoomPermalink(useLotusShareBase(), …)` (already used by "Copy Lotus Link", and correct on desktop via `webAppUrl`) for these share and QR paths. Optionally keep a secondary "Copy matrix.to link" for people on other clients. **Last touched by** a4615439 (2026-09-12, via-server resolver). **Acceptance criteria:** the QR decodes to `https://chat.lotusguild.org/home/!room…?viaServers=…`, and a logged-out visitor lands on login and then the room. --- _Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny `30e2dbcd`, cinny-desktop `8f67ec7`, element-call `3b0050e8`._
jared added the priority: mediumuxarea: navigation labels 2026-10-04 19:50:21 -04:00
jared commented 2026-10-04 20:17:06 -04:00
Author
Owner
Copy Link
Copy Source

Decision (Jared, 2026-10-04): switch the Share Room link and QR, the Invite dialog link and QR, and the space Copy Link to Lotus links (getLotusRoomPermalink + useLotusShareBase). Keep a secondary "Copy matrix.to link" for people on other clients.

**Decision (Jared, 2026-10-04):** switch the Share Room link and QR, the Invite dialog link and QR, and the space Copy Link to Lotus links (`getLotusRoomPermalink` + `useLotusShareBase`). Keep a secondary "Copy matrix.to link" for people on other clients.
jared closed this issue 2026-10-17 23:50:19 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
a11y
Accessibility: keyboard, screen reader, contrast, motion
 area: appearance
Client area: appearance
 area: auth-session
Client area: auth-session
 area: build-ci
Client area: build-ci
 area: calls
Client area: calls
 area: desktop
Client area: desktop
 area: media
Client area: media
 area: messaging
Client area: messaging
 area: mobile
Client area: mobile
 area: moderation
Client area: moderation
 area: navigation
Client area: navigation
 area: notifications
Client area: notifications
 area: settings
Client area: settings
 area: threads
Client area: threads
 bug
Something is not working
 dependencies
Third-party package versions and advisories
 docs
README / LOTUS_* docs wrong or missing
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 needs-human-review
performance
Re-render storms, leaks, heavy work on hot paths
 planning
priority: critical
Data loss, security hole, or crash on a main path
 priority: high
Broken feature or serious usability problem
 priority: low
Minor issue or polish
 priority: medium
Wrong behaviour in an edge case or notable degradation
 qa
Manual QA: shipped, needs a human in a real environment
 question
More information is needed
 research
security
XSS, unsafe URLs, data leaks, auth/session
 tech-debt
Code health, dead code, fragile patterns
 ux
Usability or visual inconsistency
 wontfix
This won't be fixed
No labels area: navigation priority: medium ux
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
cole (Cole Keller) jared (Jared Vititoe) nathan (Nathan Vititoe)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#285