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.

Sign up for GitHub

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

Jump to bottom

Being in a matrix room bridged to Telegram then enabling puppeting doesn't bridge you if you didn't join the Telegram side #205

Closed
turt2live opened this issue Aug 8, 2018 · 3 comments
Closed

Being in a matrix room bridged to Telegram then enabling puppeting doesn't bridge you if you didn't join the Telegram side #205

turt2live opened this issue Aug 8, 2018 · 3 comments
Labels
bug: defect Something isn't working and it never has worked
Milestone
0.5.0

Comments

@turt2live
Copy link
Contributor

  1. Join a matrix room that is bridged to Telegram
  2. Don't be in the Telegram room
  3. Puppet your Telegram account
  4. Speak in the matrix room - messages will not be bridged
@tulir
Copy link
Member

tulir commented Aug 8, 2018

Three potential solutions:

  • Make the Telegram user join the Telegram chats (potentially unwanted, not always possible)
  • Kick the Matrix user from the portals if they're not in the respective Telegram chat
  • Use the same portal list that is used for users who logged in with a bot (potentially unreliable, but should work fairly well for real users. Probably the best solution)

@tulir tulir added the bug: unclassified Something isn't working and it may or may not have worked in the past label Aug 8, 2018
@tulir tulir added this to the 0.4.0 milestone Aug 8, 2018
@turt2live
Copy link
Contributor Author

turt2live commented Aug 8, 2018 •
edited
Loading

or a 4th option: use the relaybot (if configured) as a fallback

edit: I think this is your option 3 actually.

@tulir tulir modified the milestones: 0.4.0, soon™ Nov 5, 2018
@tulir tulir added bug: defect Something isn't working and it never has worked and removed bug: unclassified Something isn't working and it may or may not have worked in the past labels Dec 20, 2018
@tulir
Copy link
Member

tulir commented Feb 12, 2019

This should be fixed in f8e429f (option 3)

@tulir tulir closed this as completed Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug: defect Something isn't working and it never has worked
Milestone
0.5.0
Development

No branches or pull requests
2 participants
@turt2live @tulir