Telegram API

JerryMungo

Honorary Master
Joined
Jul 18, 2008
Messages
37,522
Reaction score
6,275
So I was thinking of building a SignalR based chat interface for an app we're developing, but then someone told me to look at Telegram... you know, open source and all that good stuff...
Well it looks like it's a PITA for various reasons including:

1) It's not really possible to seperate the rest of Telegram from your app - it effectively just becomes an embedded telegram interface in your web app... so users could be left feeling like you have access to their chats and contacts etc.
2) Users need to login to your app as well as Telegram (with their phones) - an auth code is sent to the mobile telegram app, so they have to be telegram users and have to open the app to use your web app 'interface'.

Some googling confirmed it...
https://yalantis.com/blog/whats-wrong-telegram-open-api/

Unless I'm missing something, it's not really suitable for your own custom and hosted app?
 
Look at Google's Firebase - it does support XMPP as well as push notifications - so a perfect use-case for native apps (as well as browser integration) - Cloud messaging, notifications, crash reporting etc are all free.
 
Look at Google's Firebase - it does support XMPP as well as push notifications - so a perfect use-case for native apps (as well as browser integration) - Cloud messaging, notifications, crash reporting etc are all free.

Cool, will take a look, though integration with MVC seems dead simple with SignalR so I'm likely to go that route.
https://docs.microsoft.com/en-us/as...started/tutorial-getting-started-with-signalr
I'm a little wary of being tied down to a platform - rather host it ourselves but may consider it if all things considered it's simpler.
 
So I was thinking of building a SignalR based chat interface for an app we're developing, but then someone told me to look at Telegram... you know, open source and all that good stuff...
Well it looks like it's a PITA for various reasons including:

1) It's not really possible to seperate the rest of Telegram from your app - it effectively just becomes an embedded telegram interface in your web app... so users could be left feeling like you have access to their chats and contacts etc.
2) Users need to login to your app as well as Telegram (with their phones) - an auth code is sent to the mobile telegram app, so they have to be telegram users and have to open the app to use your web app 'interface'.

Some googling confirmed it...
https://yalantis.com/blog/whats-wrong-telegram-open-api/

Unless I'm missing something, it's not really suitable for your own custom and hosted app?

Use Plus = it runs on top of telegram and tabs your chats. Individuals, groups, Supergroups, bots etc. There is also an Administration tool so that you can even mute all the members in a channel except for the mods - or just one member. Gives you really nice control over your groups and broadcast channels
 
Except I want an App I can use to collect data in the field from mobile workers.
 
Top
Sign up to the MyBroadband newsletter
X