undefined | Better HN

0 pointsjddj2y ago0 comments

The 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.

0 comments

I 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.

ses19842y ago

Isn’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?

anonymousDan2y ago

Yes 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

j / k navigate · click thread line to collapse

0 comments

anonymousDan2y ago

ses19842y ago

Isn’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?

anonymousDan2y ago

j / k navigate · click thread line to collapse