Live data from Hacker News

Show HN: File.io – Ephemeral file sharing

file.io

21–30 of 92 posts

Re: Show HN: File.io – Ephemeral file sharing

#22
Something similar I made a while back for those interested in hosting their own file-upload service via S3. You can configure S3's object expiration to delete/expire files after a set amount of days.

I still use it today for sending files here and there. :)

https://github.com/alfg/dropdot - Source with demo.

Re: Show HN: File.io – Ephemeral file sharing

#24
post #13

tl;dr from the FAQ: Q: "Why should I trust you?" A: "Because you should! We're good people! Honest!" I'd love to trust a service like this, but there's no credible effort to actually establish that trust.

Now it says > file.io is a project of humb.ly. It was created simply out of the joy of trying to build cool things on the internet, and we thought it may be useful for others. We take privacy very seriously and do not save any data once it has been deleted. But going to humb.ly still doesn't really get me to trust you, there's not even any identifying info on that page. Two projects, one discontinued and one -- it se…

Humb.ly also makes park.io where the domain file.io is from.

Re: Show HN: File.io – Ephemeral file sharing

#29
post #16
post #2

I built this site and appreciate any feedback from the HN community

I was using https://usetorpedo.com (similar service) before it shut down. Probably some lessons to be learned from them. While I didn't use it super often, when I did want to use it, it was very valuable. Thanks for building this!

Maybe it failed because USE TOR -> PEDO :)

Re: Show HN: File.io – Ephemeral file sharing

#30

Although perhaps more constraining, why not use a website that uses WebRTC data channels to transfer the files? Then you can be more sure the data isn't persisting in a datacenter somewhere. Plus, it is more plausible that the service can remain free and private.

I did exactly what you're suggesting at: https://filesender.io

As you pointed out, it is a bit more constraining due to the support for WebRTC and users behind an SNAT, but I think for the majority of users it works well.

Post reply on HN