News for hackers. Stuff that matters.

A comment on Dropbox kills grandfathered Public/ folders. Parent comment

Re:Dropbox kills grandfathered Public/ folders by viraptor on Thursday December 15, 2016 @03:19PM (#13187930)
Your own domain. You only need to setup a redirect from my-awesome-stuff.com/the-app to whatever storage provider you use.
[ Parent | on HN ]
Re:Dropbox kills grandfathered Public/ folders by Cerium on Thursday December 15, 2016 @04:46PM (#13188754)
Looks like you could do it with AWS pretty cheap: https://aws.amazon.com/blogs/compute/build-a-serverless-priv...

Key part is that S3 supports redirects.

[ Parent | on HN ]
Re:Dropbox kills grandfathered Public/ folders by fernly on Thursday December 15, 2016 @03:35PM (#13188112)
OK, fair answer. I don't really want to own a domain, but that would be a solution: it gives me complete control over the form of the link, and makes it editable and redirectable.
[ Parent | on HN ]
Re:Dropbox kills grandfathered Public/ folders by photogrammetry on Thursday December 15, 2016 @07:46PM (#13190139)
You don't need a domain for S3. It's usually something like mybucket.s3.region.amazonaws.com.
[ Parent | on HN ]
Re:Dropbox kills grandfathered Public/ folders by eveningcoffee on Friday December 16, 2016 @05:57AM (#13192394)
Using S3 does not solve the problem. It just postpones it to the unknown future.
[ Parent | on HN ]