telegram
pantalaimon
Our great sponsors
| telegram | pantalaimon | |
|---|---|---|
| 3 | 3 | |
| 1,224 | 272 | |
| 3.9% | 1.8% | |
| 8.3 | 1.8 | |
| 11 days ago | 8 months ago | |
| Python | Python | |
| GNU Affero General Public License v3.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
telegram
-
Matrix 2.0: How we’re making Matrix go voom
It's supported, e.g. mautrix-telegram uses it: https://github.com/mautrix/telegram/blob/master/ROADMAP.md
- Selfhosted application for joining chat services?
-
[mautrix-telegram] What is the database I need to configure? Is that homeserver.db?
I'm trying to configure the mautrix-telegram bridge on my homeserver and I'm not sure what the database they are referring to in line 39 is (https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml). The only thing I can imagine it being is homeserver.db on my Synapse server but I have no idea if it is supposed to be sqlite or postgres.
pantalaimon
-
Matrix 2.0: How we’re making Matrix go voom
Well, if you want end-to-end encryption, then obviously that's going to be hard to write from scratch(!) - especially if you want it to be secure. However, we make it trivial to get up and running by piping your client through a proxy like Pantalaimon (https://github.com/matrix-org/pantalaimon/) which takes your normal traffic and makes it E2EE.
Not sure which "any of the other tablestakes features" you have in mind... obviously if you want loads of features, then you're going to have to write a whole bunch of code to implement them in your client, or build on an existing SDK like matrix-bot-sdk, matrix-rust-sdk, matrix-js-sdk etc. Not sure that's a disadvantage of Matrix though(!)
-
IETF should keep XMPP as IM standard, instead of Matrix
I've tried to set up some Matrix projects. The Client-Server API is easy to work with, but as soon as encryption is involved, things start getting messy. Many libraries have a hard time working right with E2EE enabled, because suddenly you need to keep track of all manner of things that aren't always documented well.
I tried to hack E2EE in by using Pantalaimon [0] but running that on a server with the necessary management capabilities is very tricky and doesn't do cross signing, so I've come to the conclusion that it's effectively useless for my use cases.
Every now and then I check back on the current state of E2EE in libraries and it does seem to be improving. Hopefully the entire process becomes easier next time I get the time to work on my proof of concept code.
-
Threema says it's Open Source Now. Should I use it?
It takes a bit more configuration, but possible via pantalaimon
What are some alternatives?
tg-index - Python web app to index telegram chats and serve its files for download over HTTP.
threema-android - Threema App for Android.
facebook - A Matrix-Facebook Messenger puppeting bridge
serialipedia - The encyclopaedia of serialization formats
python - A Python 3 asyncio Matrix framework.
umurmur - Minimalistic Murmur
cryptg - Official Telethon extension to provide much faster cryptography for Telegram API requests.
protocol - The schemas for the Harmony protocol
TeleServ - Telegram to IRC bridge in Python, that makes Telegram users appear as IRC users by linking as an IRC network server.
matrix-hookshot - A bridge between Matrix and multiple project management services, such as GitHub, GitLab and JIRA.
franz - Franz is a free messaging app for services like WhatsApp, Slack, Messenger and many more.
matrix.org - matrix.org public website