-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telegram Bot V2 #1
Comments
Now that #2 is merged this spec can be expanded on and the features that are required to be ported over should be listed here. It's unclear to me what features are wanted in this new version compared to V1. All other aspects of my initial spec have been met. @rndquu @gentlementlegen @0x4007 rfc, thank you. |
What is your question? |
What features exactly from V1 need ported over? All of them as they exist in V1 or |
Nobody knows as well as you. List every feature in "v1" and write a proposal for what to add in "v2" |
This plugin is designed to process events from both Telegram and GitHub, enabling it to respond flexibly and making it more scalable than a configuration limited to handling Telegram events and kernel interactions alone.
The system will function as the 'kernel' for Telegram, intended for use potentially within just our organization or alongside partners, depending on the final design.
All essential logic from Version 1 (V1) will be refactored to be compatible with the new Version 2 (V2) kernel. Initially, it will incorporate the functionality specified in ubiquity-os/plugins-wishlist#25.
It aims to provide a robust foundation that can be expanded with additional features. Comprehensive documentation will be developed to facilitate rapid onboarding, ensuring a seamless transition to align with the capabilities of V1.
/ask
via V1 features #17The text was updated successfully, but these errors were encountered: