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

Alternative model of bridging #30

Open
lingnand opened this issue Jan 10, 2020 · 1 comment
Open

Alternative model of bridging #30

lingnand opened this issue Jan 10, 2020 · 1 comment
Labels
currently not in TODOs Feature will be created later ... maybe enhancement New feature or request

Comments

@lingnand
Copy link

It seems to me that another way of modelling the bridge could be:

  • each email address is represented as a matrix user
  • each message thread is an email thread with the correspondent
  • for emails going out to multiple addresses, it becomes a room with multiple users

This is closer to the 'simple puppeted bridging' explained in the matrix doc and in my opinion a more intuitive way of interaction for the end user.

Did you ever consider this model instead of the more bot-like model your project is using?

P.S. I'm very new to matrix so could be missing something obvious.

@JojiiOfficial
Copy link
Owner

Yes I considered this. When I started this project I was new to matrix too and wanted to learn GOlang. Using the bot sdk was easier at this time so I decided to use this instead of the appservice API. Switching to the appservice API would lead to a complete redesign of the bridge (a lot of work). I don't have time for that at the moment, maybe I'll do these huge change later.

@JojiiOfficial JojiiOfficial added currently not in TODOs Feature will be created later ... maybe enhancement New feature or request labels Jan 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
currently not in TODOs Feature will be created later ... maybe enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants