https://github.com/joolfe/telegram-broker
Testing telegram API with a real use case
https://github.com/joolfe/telegram-broker
Last synced: about 1 year ago
JSON representation
Testing telegram API with a real use case
- Host: GitHub
- URL: https://github.com/joolfe/telegram-broker
- Owner: joolfe
- Created: 2019-03-28T18:14:17.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2019-04-05T07:50:39.000Z (about 7 years ago)
- Last Synced: 2025-02-06T09:35:04.661Z (over 1 year ago)
- Language: JavaScript
- Size: 2.16 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# telegram-broker
Testing telegram API with a real use case.
See the /docs folder for more info, this repo is going to be explained step by step in the doc.
# Ideas/Todo
- Explain about developer API here https://tjhorner.com/webogram/#/im?p=u777000_4233751068855082337 and also about the explorer of the layers and methods?
- Externalize the configuration to a file and load at startup or use some npm library for this.
- We should decide if we should do some kind of pooling or we can subcribe to channel changes.
- Look for a way to get just recent messages, i mean, we are not interested in old message, some kind of date filter?
- We probabily need to store in somewhere the activity log so we can look for a good way to see this.
- Some UI interface will be needed.
- Documentations about user guide.