Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web+riot registerProtocolHandler #4940

Closed
lukebarnard1 opened this issue Aug 30, 2017 · 6 comments
Closed

web+riot registerProtocolHandler #4940

lukebarnard1 opened this issue Aug 30, 2017 · 6 comments

Comments

@lukebarnard1
Copy link
Contributor

This would be required were we to want a better matrix.to experience. matrix.to would also need modifying so as to point to web+riot://#/room/!bla/$bla instead of https://riot.im/app.

@lampholder
Copy link
Member

I don't understand this I'm afraid - does this mean matrix.to riot links could open in existing riot instances rather than starting a new instance? If so 👍 👍 👍 👍 👍 👍 👍 😄

@lukebarnard1
Copy link
Contributor Author

lukebarnard1 commented Sep 17, 2017

Yep, that's exactly it. Although I wonder if we should do web+matrix instead? As a general way to swap to a matrix web-based client? Probably not that much to gain from web+matrix and so web+riot is probably sufficient.

@aaronraimist
Copy link
Collaborator

Is this fixed by matrix-org/matrix-react-sdk#2272?

@turt2live
Copy link
Member

Not entirely. That PR makes it easier to navigate links but doesn't solve the problem outlined here

@bkil
Copy link

bkil commented May 30, 2023

Duplicate/superseded by #16875

@t3chguy
Copy link
Member

t3chguy commented Nov 27, 2024

Closing in favour of #16875

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants