@mattj My first impressions:
It works great *when* it works.
I'm not sure if I maybe just misconfigured it, but it only works if I send a custom presence to the transport using Gajim (Conversations doesn't allow me to do that - it doesn't even allow me to add the transport as a contact).
But as soon as the Gajim resource disconnects, all my telegram contacts are displayed as offline again in conversations.

@mattj But when I use Gajim and send a manual presence, then it works really well.
Telegram users aren't aware that they talk to a user on an XMPP client at all. Only sending files results in the telegram end receiving a link that points to the XMPP HTTP upload service instead of for example an inline image.

@povoq I stopped using it. As I am also using the official app on multiple devices, it annoyed me that the transport "stole notifications" from the real apps.

@povoq I conclusion I can say that it only makes sense to use the transport if you are forced to communicate with people via telegram but don't want to use their app at all. In that case it works "good enough".

The documentation unfortunately is not great and it takes some tinkering to get it to work properly.

@povoq Oh and I could work around the issue above by configuring zhabogram to stay online when devices disconnect.

@Vanitasvitae :xmpp: Hmm, I see. I guess since I want to stop using the official app, I should give it a try then.
How much server resources did it need? Ruby makes me a bit cautious as other software written in Ruby is quite a memory hogg.

@povoq I'd say it doesn't consume much, though I haven't payed attention to it either.

Basically it's just a simple CLI based telegram client with XMPP bindings :D

@Vanitasvitae :xmpp: Would be awesome if you could write a short tutorial about it if you can get it working well :)
Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.