Protected channels #2052
Replies: 4 comments
-
This feature would require a lot of time to implement and in most cases one could just set a password on the channel and archive the same. |
Beta Was this translation helpful? Give feedback.
-
It is not flexible, and i already started implementing this feature. Passwords are not so good. If we have some meeting room, and someone threw out a password, we will need to change it and notify to all members of this channel. We should eliminate this. |
Beta Was this translation helpful? Give feedback.
-
@beqabeqa473 what would happen to the public servers and creating a temp channel with a passwor? then everyone is allowed to join because the username is same for everyone in the public servers. |
Beta Was this translation helpful? Give feedback.
-
I don't care for that.
…On 10/24/23, Amir Mahdi ***@***.***> wrote:
@beqabeqa473 what would happen to the public servers and creating a temp
channel with a passwor? then everyone is allowed to join because the
username is same for everyone in the public servers.
--
Reply to this email directly or view it on GitHub:
#2052 (comment)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
--
with best regards Beqa Gozalishvili
Tell: +995593454005
Email: ***@***.***
Web: https://gozaltech.org
Skype: beqabeqa473
Telegram: https://t.me/gozaltech
facebook: https://facebook.com/gozaltech
twitter: https://twitter.com/beqabeqa473
Instagram: https://instagram.com/beqa.gozalishvili
|
Beta Was this translation helpful? Give feedback.
-
Description
It would be good to have the following feature:
Protected channels.
it should be working as follows:
in every channel, a new section, allowed_users should be created, which tells server to make decision to allow or deny user joins.
Also, a flag should be added in channel structure to identify if this channel is protected. Note, that protected flag is already exists, we need to discover another name for that.
Three commands, allowUser, denyUser and getUserAccessList should be added in the protocol:
allowUser: accepts channelId and userName and adds an user to the channels allowed_users section.
denyUser: accepts channelId and userName and removes an user from a channel allowed_users section.
getUserAccessList: accepts channelId and lists all allowed_users.
three corresponding events should be added:
userAllowed, userDenied and allowedUser.
It would be great to hear your opinion and suggestions @bear101
Application
Beta Was this translation helpful? Give feedback.
All reactions