Skip to content
This repository has been archived by the owner on May 14, 2023. It is now read-only.

Hack Matrix support into Telegram or Signal clients #360

Open
ludwigbald opened this issue May 28, 2020 · 8 comments
Open

Hack Matrix support into Telegram or Signal clients #360

ludwigbald opened this issue May 28, 2020 · 8 comments

Comments

@ludwigbald
Copy link

They are open source and have a good interface.

@homebeach
Copy link

Why not just use multiprotocol client like Pidgin?

@ludwigbald
Copy link
Author

ludwigbald commented May 31, 2020 via email

@kiliankoe
Copy link

kiliankoe commented May 31, 2020

Pidgin is great for what it is, but also quite old. Afaik the idea here is not to revive the classic multiprotocol clients like Pidgin, Gajim, Trillian, Adium, etc, but to basically take over a modern UX and basically clamp Matrix behind it :P

@homebeach
Copy link

@ludwigbald
Copy link
Author

ludwigbald commented Jun 18, 2020

@homebeach : My point was not to bridge Matrix and Telegram with this. I only want to steal the mature UX for a native Matrix client!

@ludwigbald
Copy link
Author

Also an option: mattermost and rocket.chat

  1. steal the UX and make it a matrix client.
  2. convince them to switch out the default backend to matrix.
  3. millions of new matrix users.

@kiliankoe
Copy link

convince them to switch out the default backend to matrix.

I remember the days when Facebook and Google Chat were based on XMPP and federated publicly...

@LiGoldragon

This comment was marked as abuse.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants