-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Allow anonymous use of the chat [$250] #604
Comments
What does "Registration Required" set to false do? I have not seen any effect? |
👍 I am considering switching away from Slack and this is one of the main features I am looking for (being able to access and read the public channels without registration). |
This needs to be an option for each channel. If the creator wants it, the channel can be read for unregistred users. |
Or written to. I would really like that it can be like: user comes, sees channels (maybe flagged as such), and can read them, and can write an reply. And if the are not logged in, they have also to fill in the name in the status bar (which stays stored locally). |
Bump:
|
@mitar Registration Required is not used at this time. |
Heh, a setting which does nothing. ;-) OK, this is good, then it can be used for this particular purpose. So I would suggest that we make it so:
I would say that concept of private and public channels should be for some other ticket/task. |
for sure agree with @AdrianoCahete this needs to be maybe global to allow it. But needs to be a per channel setting. |
But if I want to have all channels public, I do not want to enable per channel it every time. I think that per channel permissions can be added later. Because those are two pretty different use cases still. |
Maybe we could use a Meteor package which automatically creates an account for every user, and then just use permissions to do the rest. And allowing users to change the username and set password would then allow them to register the account once they decide to do so. There are packages like:
Not sure which one is good. |
I've used I think you should just rely on admin settings to force user registration or not. |
I agree. A user per guest is a bit too much over head just to let them see the channel. |
Yes, and then you have a registration-looking form which converts that guest user to a normal user. It sets username and password and e-mail, for example. It can look to the user the same as current registration form.
I would like not just seeing the channels, but also posting. So posting without having to be registered (you just pick the name when you want to post). |
IMHO
|
+1 to @rodrigok |
Again, I think there are two features here and I think both should be supported:
I see that some people like the feature of anonymous reading, but I would also need anonymous writing. |
@mitar anonymous write is possible, but we can't provide consistency and is much hard to prevent flooding. |
For anonymous reading, you wouldn't need an account. Anonymous usernames might be pre or post pended with (Anon) or (Temp) or something as well, so users know they aren't registered (per server setting?). Those sound like good ideas? |
+1 |
@ShaRose Might as well just use a normal session. Binding to an IP is generally a bad idea. Think public access. More then one user in a library / coffee shop? I've been in situations where I went to a sight and I was suddenly logged in as someone else ;) |
+1 This is why I was proposing autocreation of accounts for each guest when you are in "no registration required" mode. |
Per room or general access options (radio - choose one):
Other options
|
fwiw, if this is critical to anyone, riot chat allows world-readable channels already: https://chat.tomesh.net/#/directory |
Where can I define, which public channels are listed in the left column when arriving anonymously at the start page? Currently I see "undefined" only and directory does not allow to search (which is okay for users, but it should list public channels). |
@rasos Make the channel/rrom default and it will be showed there |
@lunitic tnx, but where do I set a channel room to become default? Can't find it in any menu. We're on RC 0.62. I only can set it as favorite which is a per user setting. |
If you set them as "default" channels, I think they will show up
automatically.
…On Mon, Apr 23, 2018 at 5:07 AM, Roland ***@***.***> wrote:
Where can I define, which public channels are listed in the left column
when arriving anonymously at the start page? Currently I see "undefined"
only and directory does not allow to search (which is okay for users, but
it should list public channels).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL_pYhDmCLmGEQSoJNmbdGXo_ut6SHd4ks5trZnjgaJpZM4F0Lwk>
.
|
Hi there |
…0fbf9d [Upstream Catchup] Merge RC:master to develop_pwa
Adding to what @leonardorocc0 is reporting: I have allowed anonymous write on my instance (3.14.0). I have disabled finding public channels via the directory or spotlight search for This mislead me to almost configure a security hole simply because I thought that if I disable finding public channels via spotlight on Is there any possibility to disable the spotlight results of public channels for anonymous users without a username? |
So currently, Rocket.Chat is a very much a Slack clone. But my main issue with Slack is that it is not open enough. So I would like an option to make Rocket.Chat more open. What I mean by that is that is that users can come and start reading what is happening on public channels without registration. So when a not-logged in user would open root address, they would get to the normal main screen, with all channels listed and so on. When they would open a channel, they could see what is happening there, but the message input box would be grayed out and a message to register/login to post would be there.
There is a $250 open bounty on this issue. Add to the bounty at Bountysource.
The text was updated successfully, but these errors were encountered: