Replies: 2 comments
|
Best word of advise if anyone is test... do a backup... I lost a day's worth of data by messing with this with no backup. Now I don't know what affect we will have when we upgrade to the newer version. |
|
Just sharing some thought, as I have looked at other similar projects. The channel is self has a limitation of 50 admins. For a bot to work or added it needs to be added as an admin. Can we allocate a pool of bots to a specific channel and rotate as needed? We don't need to have the same bots for all channels. Is there any way to cap the usage of a specific bot to avoid the unnecessary flag to get it banned? When a bot is banned, is there a way to auto retire them? Also for optimization is there a way to measure how a bot perform over time? Not all bots are the same, some are fast some are really slow. Some bots are good for specific files, some aren't. Its prob due to the data center location and where files are held. These are ideas only, I am not a programmer however I might fork it and test program this via vibe coding. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Due to the way telegram works, there are limitations on how many admins you can have in a channel. For a bot to be in the channel it needs to be an admin.
The number set by telegram is 50 admin capped. You can't have more.
The bot rotation that we have in telegram is good and not good. How it is at the moment the more you have the more memory it consume. This does not necessarily mean you get more performance either.
I find that anything more than 10 usually leads to lower performance.
Teldrive have an API that allows you to script to add bots. This is great to rotate the bots. However when we use the remove bot API. It removes it from teldrive but leave it in the channel as admin.
This leads to an issue of too many admins.
I think the algorithm could be improved to help and clean up properly. This leaves room for new bots to be added.
The reason why I want to rotate the bot is to spread activities to avoid getting flagged.
So far the bot rotation algorithm could be improved.
I tried to fork the code to help write a different algorithm. But it seems the new code changes the db, and I don't have another instant to try to help.
What I find currently is if a bot is banned the logs is spammed but the app doesn't notify or do any to manage the issue.
Bots removal doesn't clean the room bot remains.
The add and remove is a bit temperamental, it a bot is still valid it doesn't add. I think this is fixed in the new code. I did try a compile to test but this pretty much corrupted my db.
These are not bugged, so just open a conversation here for feedback and hopefully help to improve it.
All reactions