The current implementation of join requests makes it unnecessarily complex. You need to create a special link just to enable join request. And then you face permission clashes—one link to allow joining, another link requires admin approval to join. And then you also face issues related to leaking of links that allow joining to people.
Why not just have a toggle in permissions section: members can join without requiring approval ☑
Group admin can just toggle this permission any number of times depending on whether one wants to allow people to join with approval or without approval.
The problem is, that legacy client versions can't handle this "waiting for permission" process and would just fail without a helpful message.
So the devs need to make all clients capable to handle it first and wait a few month before allowing admins to enable the feature described above (except for testing in beta versions of course). So it is ensured, that at least most clients meanwhile have updated to a version, that can handle this.
It is a similar impediment like telegram had, when migrating ids from 32 to 64 bits.
Daniel
These scammers attack multiple "nearby chats" simultaneously. Pre-approval by an admin would stop that
I saw many geo located groups, having up to 3000 scam accounts inside, even pinging each other. Most users have left the group and admins gave up, but did not delete them.
@inquisitive So your suggestion is basically to bridge the gap between Telegram as an easy-to-use and an advanced Plattform.
As Rear-Tiger mentioned, there are several points to consider while implementing such a feature. Apart from that, being able to use join requests alongside normal join links is useful in many cases - i.e. if you have users that are joining from different (trusted & not trusted) locations.
From my own experience: It seems that Telegram integrated version checks & the ability to display messages from the server in the app - to be able to tell users with outdated applications **why** it is that they cannot login, for example.
» Toggle Join Requests in Permissions - Section « As I said - this will not work well - just because you cannot scale it! (It breaks the possibilities you get with the feature to have **multiple join links** in the first place.)
But I have an idea: Your idea could work fine for regular groups - because they are private, technically different from Supergroups & Channels - an they are **not** for large scale communities.
PLEASE NOTE: -» a regular group has a »name« & »picture« -» a group that has a »description« or »username« is a supergroup -» a group created through the official apps is a regular group -» a regular group gets converted automatically to a supergroup as soon as you change certain settings applying to supergroups -» some custom clients allow you to directly create a supergroup
Log in here to report bugs or suggest features. Please enter your phone number in the international format and we will send a confirmation message to your account via Telegram.
The problem is, that legacy client versions can't handle this "waiting for permission" process and would just fail without a helpful message.
So the devs need to make all clients capable to handle it first and wait a few month before allowing admins to enable the feature described above (except for testing in beta versions of course).
So it is ensured, that at least most clients meanwhile have updated to a version, that can handle this.
It is a similar impediment like telegram had, when migrating ids from 32 to 64 bits.
Pre-approval by an admin would stop that
As Rear-Tiger mentioned, there are several points to consider while implementing such a feature. Apart from that, being able to use join requests alongside normal join links is useful in many cases - i.e. if you have users that are joining from different (trusted & not trusted) locations.
From my own experience: It seems that Telegram integrated version checks & the ability to display messages from the server in the app - to be able to tell users with outdated applications **why** it is that they cannot login, for example.
» Toggle Join Requests in Permissions - Section «
As I said - this will not work well - just because you cannot scale it! (It breaks the possibilities you get with the feature to have **multiple join links** in the first place.)
But I have an idea:
Your idea could work fine for regular groups - because they are private, technically different from Supergroups & Channels - an they are **not** for large scale communities.
PLEASE NOTE:
-» a regular group has a »name« & »picture«
-» a group that has a »description« or »username« is a supergroup
-» a group created through the official apps is a regular group
-» a regular group gets converted automatically to a supergroup as soon as you change certain settings applying to supergroups
-» some custom clients allow you to directly create a supergroup