Hacker News new | past | comments | ask | show | jobs | submit login

Not a bad idea, but you could probably just use the session ID (or a unique ID linked to the users session if it's a secure site). So when the session expires, so does access to the content. The drawback to this is you're exponentially increasing DB i/o.

Personally though, I'd rather not block hotlinking. But I understand why some people are against it.




It's actually implemented in a better way (no db required) with most web servers: http://wiki.nginx.org/HttpSecureLinkModule




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: