Enhancement - Revoke public link

[GoogleCodeExporter]

Follow on from issue 158 - my apology I used the term private, I should have 
said revoke.

Currently once a public link to a file has been published there appears no way 
of revoking that link.

Say you have shared some photos or a document with a friend or posted on 
another website, but then change your mind. The only way I can see of stopping 
them from still having access to the file(s)is to rename /move the file - am I 
right? This seems like a bit of a headache for me.

I would like a way of revoking that permission /link to download my file.

It would seem reasonable that if I turn of default rights (no read) to a file 
then no one should have any rights to the file including downloading it, that I 
have not assigned them.

Original issue reported on code.google.com by google.code@casanet.co.uk on 15 Nov 2010 at 6:05

[GoogleCodeExporter]

Yes, I see your point, and agree it is something to consider.

But I really wouldn't want to mix permissions with public links, they are meant 
for totally different things. Sometimes it is just easier to manage access 
_within registered users_ if you set default permission to none, and then grant 
access only for those who need it. But still it does not necessarily mean I 
don't want to have public access.

I'd like to see some other solution. Some time ago I was thinking about 
different kinds of public link scenarios, one being this simple "on/off" 
method, but then there could more dynamic sharing where you could set 
expiration for public links, maybe password, and of course ability to turn 
sharing off, for each file individually. This method would require public link 
storage, and is naturally a bit more complicated, but definitely possible.

Original comment by samuli.j...@gmail.com on 15 Nov 2010 at 6:15

[GoogleCodeExporter]

Thanks Samuli, your suggestions all sound good. Another thought maybe to have 
an option to fire an email off to whoever with the public link and a message 
from the file owner. If passworded then also include the password, or oblige 
the recipient to register before they can download the file, using the email 
address used to send the "invite". For flexibility it would still be good to 
keep the public (no login /password)link available, but controllable.

Original comment by google.code@casanet.co.uk on 15 Nov 2010 at 9:37

[GoogleCodeExporter]

Issue 324 has been merged into this issue.

Original comment by samuli.j...@gmail.com on 21 Nov 2011 at 5:16

[GoogleCodeExporter]

Version 1.8.6 has now Share plugin, which allows controlling what items are 
shared, and also to remove the share if needed. In future, there will be also 
password protection, expiration time etc.

Original comment by samuli.j...@gmail.com on 6 Jan 2012 at 8:20

• Changed state: Fixed