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

Ability to disable direct messages #665

Closed
kosciak9 opened this issue Oct 5, 2021 · 2 comments · Fixed by #892
Closed

Ability to disable direct messages #665

kosciak9 opened this issue Oct 5, 2021 · 2 comments · Fixed by #892

Comments

@kosciak9
Copy link

kosciak9 commented Oct 5, 2021

Hello,

At our server we have bridge to external group (TG) where other members of our project reside. I wanted for our users to be double puppeteer-ed (it's cleaner), so I asked them to login. Unfortunately, it's generating a lot of noise with their direct messages. Is there a way to keep double puppeteering and lose direct messages? I've been looking for solution for quite a long time and found nothing (filters don't matter for direct messages).

I could maybe try to look into code and prepare a PR, but I'm not sure how you want to proceed here.

Thanks in advance

@kosciak9
Copy link
Author

kosciak9 commented Oct 5, 2021

Possibly - just disable recreating chats that were closed when new message arrives in those chats. I keep on deleting direct messages, they're forgotten - and then recreated shortly afterwards.

@Ultrawipf
Copy link

Would be very nice to change per user during the login if they only want to only act in manually bridged channels or receive their whole telegram activity with private messages. Or disable auto generated channels completely and only use manual bridging.

Maybe i am missing something but i haven't seen an option yet to be logged in and not get spammed by telegram events in matrix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants