Skip to content
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

Broadcast channels #9556

Closed
3 of 4 tasks
sampaiodiego opened this issue Jan 30, 2018 · 5 comments · Fixed by #9950
Closed
3 of 4 tasks

Broadcast channels #9556

sampaiodiego opened this issue Jan 30, 2018 · 5 comments · Fixed by #9950

Comments

@sampaiodiego
Copy link
Member

sampaiodiego commented Jan 30, 2018

The idea is to have a new option on create channel page called "Broadcast Channel", having it toggled on will disable "read only" toggle.

Only owners will have permission to write on this channel.

Every message on this channel will have an action button called "Reply" that once hit will redirection the user to direct room with the sender with clicked message auto-filled as a reply on the text box.

  • Apply options on create channel and edit channel

  • Insert button 'reply' on each message

  • Open room by reply

  • block user list to normal users

@kb0304
Copy link
Contributor

kb0304 commented Feb 3, 2018

Hi @sampaiodiego ,
I would like to work on this feature. Could you please assign it to me.

@sampaiodiego
Copy link
Member Author

sampaiodiego commented Apr 12, 2018

oops.. PR was not merged yet. reopening

@sampaiodiego sampaiodiego reopened this Apr 12, 2018
@rodrigok rodrigok added this to the 0.64.0 milestone Apr 21, 2018
@adrianovieira
Copy link

I'm trying to use this...

But if we set a channel as read only and broadcast one that reply' button' appears to be useless.

So, you it would "hide" that button, wouldn't it?

@sampaiodiego
Copy link
Member Author

looks like we have an issue. the button is intended to work. can you please open an issue describing it please @adrianovieira ?

@adrianovieira
Copy link

adrianovieira commented Jun 5, 2020

Ok! But before that I'll perform an update of our instance (which is 3.0). After that I will open anew issue if the problem still there.

Thanks, by your quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants