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

Not a professional liar either but I'm not sure about that. I imagine torrent trackers are a decent analog thats been through the courts already. They don't host the content, they just host URIs and metadata to people that host the content.

The drag and drop interface isn't to upload the content to be hosted like a traditional server (what's the point then?) It looks like (without digging through code) it's so they can parse the file-structure and generate the URIs to forward requests.



> It looks like (without digging through code) it's so they can parse the file-structure and generate the URIs to forward requests.

I haven't looked at the code either. But the hosting seems to be handled in JavaScript. There are no required clients (though there does seem to be an optional one); this is all completed in the browser.

So you're not "uploading" content, you're providing the content to the client-side application so it can be shared through that same client-side solution.


I don't think that torrent trackers are analogous to this at all, unless I'm misunderstanding how it works. AFAIK, this is essentially a proxy:

you <-> hostyoself <-> someone else

where all data goes through hostyoself. This is analogous to ngrok, but at file-system level rather than TCP.




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

Search: