Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

[share-link] Enhanced share links -- passwords & time limits #86

Closed
chuyskywalker opened this Issue Jan 23, 2013 · 11 comments

Comments

Projects
None yet
8 participants

I want to share links to documents with a few people, but I don't want the documents to be made available forever and for anyone who happens to get the link. So, this request (could be broken into two requests) would cover:

  1. Add support for creating share links that expire after X amount of time
  2. Add support for creating share links that requires a password for access

And, of course, ensure that you can both password protect AND time limit a link.

Owner

freeplant commented Jan 23, 2013

We will add the time limit first.

@ghost ghost assigned xiez Feb 4, 2013

usrflo commented Jan 26, 2014

Is there any news about this feature request ?

FireROR commented Sep 11, 2014

Any updates? I think this is very useful function.

Owner

lins05 commented Sep 11, 2014

Check https://seacloud.cc/group/3/wiki/server-changelog/ and search for
"Password protection for sharing links".

On Thu, Sep 11, 2014 at 9:22 AM, FireROR notifications@github.com wrote:

Any updates? I think this is very useful function.


Reply to this email directly or view it on GitHub
#86 (comment).

FireROR commented Sep 11, 2014

Password is good. But auto-expire will be better, and I thought freeplant says time limit first?

Owner

lins05 commented Sep 11, 2014

They're both implemented.

On Thu, Sep 11, 2014 at 10:00 AM, FireROR notifications@github.com wrote:

Password is good. But auto-expire will be better, and I thought freeplant
says time limit first?


Reply to this email directly or view it on GitHub
#86 (comment).

FireROR commented Sep 11, 2014

Ok. I did see the Expiring time for sharing links from 3.1.0. Would you please let me know where to setup?

On the share file page, there is only Download Link and Private Share, and Password protection and generate bottom. Maybe I am looking at the wrong place...

Owner

lins05 commented Sep 11, 2014

Ah, sorry for this confusion. I forgot to say that auto expiration for
shared links is only included in seafile pro server.

On Thu, Sep 11, 2014 at 10:15 AM, FireROR notifications@github.com wrote:

Ok. I did see the Expiring time for sharing links from 3.1.0. Would you
please let me know where to setup?

On the share file page, there is only Download Link and Private Share, and
Password protection and generate bottom. Maybe I am looking at the wrong
place...


Reply to this email directly or view it on GitHub
#86 (comment).

FireROR commented Sep 11, 2014

LOL. Ok then... Thanks.

tehXor commented Sep 18, 2014

I also was wondering where the expire time for new links is as I saw it in the changelog from 3.1.0. But when I get this thread correctly this now is a paid only feature.
This is really a pity. When I implemented Seafile as "friends and family" storage solution I found the difference between the community and pro edition very reasonable as pro seemed to difere in the way that it offers support and features which are only needed for company setups.
But this now is feature which I'm sure every private user would also love to have and so it now feels a little like the project moves in way where new comfort features for everybody are kept back to generate more revenue. I'm not really accusing someone for wanting to make money (we all gotta live from something) and the feature pack provided by the CE still is great so at the moment there still is no reason for me to move to another project. But I'm just writing this as sort of feedback and also in the hope that this 'new' trend doesn't get to extreme in the future so I'm not forced to change (because I guess I really don't like the way i.e. OwnCloud is doing things) ;-)
Cheers!

Contributor

shoeper commented Sep 18, 2014

@tehXor I think a bit like you do but I think living without expire time is ok for private usage. We can also simply delete the share later by hand.

@freeplant freeplant closed this Aug 22, 2015

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