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

Add option for disable chat in public shares #2284

Open
Ivansss opened this issue Oct 8, 2019 · 12 comments
Open

Add option for disable chat in public shares #2284

Ivansss opened this issue Oct 8, 2019 · 12 comments
Labels
1. to develop enhancement feature: chat 💬 Chat and system messages feature: talk-sidebar ⬅️ Sidebar integration of Talk into other apps like sharing and documents
Milestone

Comments

@Ivansss
Copy link
Member

Ivansss commented Oct 8, 2019

Related with #2280
Apart from the global options in #2283, it would be nice to have an option to disable chat in public shares for a specific file.
This option will be available only for the file owner and enabled by default.
If the file owner disables this option, only internal users/shares will be able to use the chat attached to this file and the chat will not appear in public shares.

Screenshot 2019-10-08 at 16 35 23

@nickvergessen
@nextcloud/designers ideas?

@Ivansss Ivansss added 0. Needs triage enhancement feature: chat 💬 Chat and system messages feature: talk-sidebar ⬅️ Sidebar integration of Talk into other apps like sharing and documents labels Oct 8, 2019
@jancborchardt
Copy link
Member

Since it is related to how you share, the option needs to be in the menu of the Share link instead:
nextcloud/server#12178

With the mockup by @juliushaertl on hiding the advanced settings, we can put it in there. :)

@Ivansss
Copy link
Member Author

Ivansss commented Oct 8, 2019

@jancborchardt we thought about adding it to the "share link" menu too :)
But the problem is that the chat is not share related but file related.
In other words, there is just one chat per file, not one chat per share.
That way, all the sharees use the same chat for collaboration.
So this option should be outside of the "share link" menu.

@danxuliu
Copy link
Member

danxuliu commented Oct 9, 2019

It could still be added to the Sharing tab outside all shares, but I think that it will be strange.

But there was an additional reason to add it to the Chat tab, which is not touching the server code for this. As far as I know right now apps can not extend the Sharing tab, so the option would need to be added in the server itself, and I would like to avoid as much as possible to add app specific code to the server (yes, the Password protect by Talk option is hardcoded in the server, but in that case there was no other way around it ;-) ).

Also, another phrasing (which I think is better) that we came up for the option was Enable public conversations (instead of Enable chat in public shares).

@Ivansss
Copy link
Member Author

Ivansss commented Oct 9, 2019

Also, another phrasing (which I think is better) that we came up for the option was Enable public conversations (instead of Enable chat in public shares).

I know that we came up with "Enable public conversations" 😄 , but then I thought that this wording might be hard to relate with the chat shown in public shares.

Another idea could be "Enable chat in shared links"? So we use a similar term as in Files.
Screenshot 2019-10-09 at 09 27 26

@nickvergessen
Copy link
Member

@jancborchardt

With the mockup by juliushaertl on hiding the advanced settings, we can put it in there

I think it is somewhat weird to have it in there, if it manages all shares for the same file. And I can almost guarantee that there will be a request to manage them individually and that will be a pain to oversight and manage in the backends...

@jancborchardt
Copy link
Member

I think it is somewhat weird to have it in there, if it manages all shares for the same file.

No, the menu exists for every share link individually, including mail shares (and we could even have it in the shares with people on the same instance).

So you could e.g. send a link to one group which makes the chat visible and actionable, and to another who only sees the file itself.

@Ivansss And yes, it should simply be called "Enable chat". Links are not "public" per se, so we should not call it that or people think it will be made public on some list. ;)

@nickvergessen
Copy link
Member

The share table has no support for this, so it will become a mess. Exactly why I think we should stick to the global setting for now. The details for this minor change is just too much effort at the moment

@jancborchardt
Copy link
Member

@ma12-co @jenniferpiperek do you understand this, and/or do you have a proposal here? :)

@marcoambrosini
Copy link
Member

marcoambrosini commented Oct 10, 2019

I think it's reasonable to have a global setting for this. Per share setting would be Ideal for the current UI, since this would be the only global setting from what I see. Do we have any other global (per shared file and not per share) setting?

As per the busy popover, I think we could also explore a horizontal navigation flow similar to the color picker one, something like:

IMG_20191010_082613

@tigernero79
Copy link

I saw that talk 7.0.1 update was released which should include the ability to disable chat in the URL of the file sharing but I can't find how to do it is the option?

@nickvergessen nickvergessen added this to the 💔 Backlog milestone Nov 14, 2019
@nickvergessen
Copy link
Member

I saw that talk 7.0.1 update was released which should include the ability to disable chat in the URL of the file sharing but I can't find how to do it is the option?

It's in the admin settings, visit index.php/settings/admin/talk on your instance as an admin

@tigernero79
Copy link

thanks, but option came out only with such 7.0.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop enhancement feature: chat 💬 Chat and system messages feature: talk-sidebar ⬅️ Sidebar integration of Talk into other apps like sharing and documents
Projects
None yet
Development

No branches or pull requests

6 participants