-
Notifications
You must be signed in to change notification settings - Fork 294
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
There are no more supergroup groups. #426
Comments
That is going to stay there until the API is updated to abstract the differences between normal groups and supergroups. Underneath, Telegram still handles them separately. With Telegram 5.2 the conversion just happens automatically on some events, but the reasons why GroupButler doesn't work in normal groups are still valid Edit: I got your point. Maybe that string is a bit confusing now, yes |
I thought I removed these 🤔 And yeah, telegram really needs to update their bot api so we can handle these cases better. |
This Issue is preventing me to add the Bot to any new group. Is there a workarround?
I thought the were no more "normal groups" and "super groups" |
@lasmaty07 Toggling Group Type (private/public) or Chat history visibility should be enough to trigger the conversion it seems. |
I have been able to add Group Butler finally! As said in this thread, now all the groups are "Supergroups", but @GroupButler_bot says the following in a normal group; > Hello everyone! But, to solve this you must to convert your group from Private to Public. After this, the bot will work! > Hello everyone! Now, you can convert your group to Private again, the bot will continue working after that. :D |
This is misinformation. Supergroups (called "megagroups" in the API) still exist. They are just converted more seamlessly, like when you make the group public (and then send a message), as you said. |
There is a public or private group.
GroupButler/lua/groupbutler/main.lua
Line 153 in 637a77d
The text was updated successfully, but these errors were encountered: