4 ms·
You can if it's one link per user
by colecut 3y ago
You can if it's one link per user
- vel0city 3y agoLots of platforms I've used with these public share links don't really support multiple share links, and if they do the management of it is pretty miserable. Clicking share multiple times just gives the same link.
- ses1984 3y agoTrue but if you’re generating one link per user, at what point do you lift up your head and wonder if it wouldn’t be easier to just use authentication?
- jddj 3y agoThe friction that semi-private links remove is that the recipient doesn't need an account for your service. Any tradeoffs should be viewed in that context.
- anonymousDan 3y agoI like how google docs does it. You can specify the email of a user allowed to access the link (doesn't need to be gmail). When they click it they will be told to check for a validation email containing a link to the actual document.
- ses1984 3y agoIsn’t that basically a form of authentication? I’m not sure if short lived temporary private links fit the model of private links as described above. If that counts as a private link, what if I’m using a conventional session based app, I go into dev tools and “copy as curl”, does that qualify as a private link?
- anonymousDan 3y agoYes it is. My point was more that it's a relatively lightweight way to create a shareable link that does not require the consumers to create a new account on the service hosting the linked resource in order to access it. At the same time, merely having access to the link doesn't really gain you anything, and so it is immune to the kind of issues discussed in the article