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

Uploaded files list, either an option on the right hand pane or thru history option? #760

Closed
Megatronic79 opened this issue Sep 11, 2015 · 11 comments

Comments

@Megatronic79
Copy link

Would be good if you can see a list of all files uploaded to a channel, it could be available thru the history option and maybe searchable? Useful to find specific drawings\documents when the channel content is high.

@Megatronic79
Copy link
Author

same goes for URL links added to the channels ( Much like the Hip Chat client has?)

@rockneverdies55
Copy link

+1

Definitely a good idea.

@Sing-Li
Copy link
Member

Sing-Li commented Sep 11, 2015

Hmmm... our uploaded files are externally accessible without authentication. Need to think hard b4 proceeding with this one, we don't want every Rocket.Chat hoster to inadvertently become a free XBMC video host.

@Megatronic79
Copy link
Author

Yeah sure, could we have the option to have some channels that require authentication to follow the URL to the document? was the reason they are publically available for sharing?

if so maybe we could lock all documents to internally authenticated users and have the option to send out a link via email and set a pass code to acces? keeps everything under control?

Much like OwnCloud's share option?

@graywolf336
Copy link
Contributor

@Sing-Li #724 is an issue I created about uploads not being protected at all, which is an issue for me as I don't want any files to be made publically accessible unless they are explicitly marked as public downloads.

@Megatronic79
Copy link
Author

So we should mark this ticket as depends on #724

@geekgonecrazy
Copy link
Contributor

This is definitely planned. But I agree we should for sure finish #724 to prevent abuse.

@marceloschmidt
Copy link
Member

Related to #308

@gmsecrieru
Copy link
Contributor

Closing this based on #955

@Megatronic79
Copy link
Author

Yep tested that earlier looks good!

Should focus on the #724 for the public facing instances.

@gmsecrieru
Copy link
Contributor

👍

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

No branches or pull requests

7 participants