Telegram GitHub Issue "Workroom" #25
Comments
|
/start |
Tips:
|
# No linked pull requests to close |
|
/start |
![UbiquiBot[dev]](https://avatars.githubusercontent.com/in/257883?s=40&u=1eea9b595c7c8aa1f9dd80751aa25f169024431e&v=4){kind=avatar}
Tips:
|
Tips:
|
# No linked pull requests to close |
|
@jordan-ae the deadline is at 2024-08-16T12:35:35.674Z |
|
/start |
! Skipping '/start' because the issue is already assigned. |
|
@0x4007 I encountered a blocker with the Telegram integration plugin. Initially, the plan was to create a bot using BotFather, similar to our previous Telegram bot. However, according to Telegram's latest documentation, bots are unable to create Telegram channels—only human users can do this, likely to prevent spamming. To work around this limitation, I opted to use the gram-js library, which allows us to create channels via a Telegram app associated with an existing user account. The challenge here is that Telegram requires a phone number for authentication and sends a code that must be manually entered to pass 2FA. Fortunately, this authentication process only needs to be done once. After the first successful authentication, a session string is generated. This session string remains valid indefinitely unless explicitly revoked, so we won’t need to re-authenticate in the future. Given this requirement, we'll probably have to create a dedicated Telegram user for Ubiquity, which will be used to power the plugin. I've made some progress and have successfully managed to create a Telegram channel when a task starts and close/delete the channel when the task is completed. I'm submitting a PR with the current state of the implementation asap. |
|
https://t.me/UbiquityOS is ready to be used. |
|
QA: ubq-testing/telegram-bot#4 (comment) It is not based on https://github.com/ubiquity/ubiquibot-telegram at all and uses the |
|
Perhaps there is an opportunity to use Telegram apps to solve this problem somehow. |
That's essentially what I have been trying I'm sure as the MTProto API is for clients and apps as far as I understand it while the or do you mean mini apps? |
|
0x4007 via telegram:
So a new issue is created and after a price label is applied the bot creates a workroom, which is it's own telegram group chat and it posts a link to it. At this point no one is in it so the core team member(s) assigning the labels and creating the task should be required to join the workroom immediately so there is at least one person in it in the event a contributor joins it. So they'd effectively be the 'knowledge base' for that task via telegram pretty much? Should our telegram bot also be invited into the chat directly too? We'll need to create db entry for each chat that we create and have the plugin event run on If we kick everyone from the chat once the issue is complete and then the issue is reopened should we post a new chatroom link or the same link for the original chat? Should we standardize workroom titles with a prefix/format or just use the raw task title? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
|
@0x4007 can this be assigned to me and reward generated please. As far as I can tell I have met and achieved the spec, provided ample QA, docs and tutorials to properly setup and install this plugin. |
|
@gentlementlegen i understand theres been more set up required i presume i should assign both of you |
|
I spent quite some time on the setup because it is complex and @Keyrxng didn't have enough access to the configuration or the Cloudflare, but to be honest I didn't code anything in here. |
|
And I spent almost as much writing docs, recording tutorials and trying to assist in the setup process. Sorry and thanks @gentlementlegen, I'm just as glad as you that it's behind us now lmao. |
|
@Keyrxng the deadline is at Thu, Oct 31, 11:50 PM UTC |
! Failed to run comment evaluation. Relevance / Comment length mismatch! |
|
Not the first time this error pops up, I wonder if it is just OpenAI not returning the proper JSON response or the logic being flawed. |
! Failed to run comment evaluation. Relevance / Comment length mismatch! |
@gentlementlegen You need to implement a fix |
+ Evaluating results. Please wait... |
|
Note This output has been truncated due to the comment length limit.
|
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Task | 1 | 600 |
| Issue | Comment | 6 | 14.13975 |
| Review | Comment | 68 | 0 |
[ 220.122 WXDAI ]
@0x4007
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Specification | 1 | 79.11 |
| Issue | Comment | 5 | 6.417 |
| Review | Comment | 44 | 134.595 |
[ 103.803 WXDAI ]
@gentlementlegen
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Comment | 2 | 6.471 |
| Review | Comment | 20 | 97.332 |
I've never seen a summary posted are you sure this is implemented to spec? |
P.S:
Apprecaite if you could fix this for me also, cheers. |
I realize that some projects require collaboration, and our team has a natural tendency to direct message each other. The problem with this approach is that the collaborative research in direct messages is not auditable. The conversation that occurred would be useful for future reference to post a summary to the completed task.
It would be nice if as soon as a task is started, the bot can post a link to a freshly generated telegram chat room that acts as a collaborative "work room" to solve that particular task
Once the task is closed as complete, we can use ChatGPT to summarize the essential details from the telegram group chat and post it to the GitHub issue as a conversation summary for future reference
Inventing the telegram integration will probably take some time so I'll set this to a week.
It would be nice to get automatically kicked from the chat when the task is completed so that our telegrams don't get cluttered with these.
The text was updated successfully, but these errors were encountered: