JerryMungo
Honorary Master
- Joined
- Jul 18, 2008
- Messages
- 37,520
- 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?
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?