Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Zips are great - they allow users to download numerous files in an organized file structure from a single browser download. That’s why, when building Memory Labs (memorylabs.app), we were surprised to learn that S3 offers NO built-in zipping. Our users required personalized downloads with the photos/videos they were in and had ‘favorited.’ The two solutions were reminiscent of a 2012 user experience: 1. instantly offer a unpersonalized, premade zip with all files 2. make our client wait minutes for an email once their personalized zip has been created

Both of these solutions required us to create, store, and manage the lifecycle our users’ zips.

We needed the best of both worlds: instant, personalized downloads. That’s why we built Streamzipper. Pass our API an array of files to zip, with whatever file structure you’d like, and immediately receive a signed download link. No zip creation, storage or management needed. Customize the name of the returned ZIP and add an expiration time. Hook up your S3 bucket to pass file paths directly, or pass public or signed URLs.

We deliver the most seamless, feature-rich zipping experience for developers.

Coming soon: Track user downloads (dates, download duration, user internet speed), Dynamically adjust expiration.



Why does this have to be a service, paid or otherwise? Why should a client trust you with their S3 creds and data? It feels like something that could be implemented in max 3 billed hours by one engineer.

>href="sms:XXX-XXX-XXXX"

That's pretty nifty.

Also try prepending "Show HN:" to the post title so it gets put in the show tab.


Anyone entering their S3 credentials should only enable the s3:GetObject scope, which we mention on the dashboard. They can also pass presigned URLs instead.

As far as rolling it yourself, it's certainly doable. This project started as an internal feature for our other business. Like most things, it ended up being more complicated + took longer than we thought and we were surprised there was no easy-to-use, plug-and-play solution to this problem.

We generally believe in operating at the highest level of abstraction to focus on the product, and felt that this was a hole in dev tooling!

>That's pretty nifty.

Thank you! The sms href is pretty underutilized. We’re thinking about using it in a CRM tool as well with the auto-filled fields.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: