Hacker News Reader

Having actually written something like this before --- and it remains on my machine as an executable of only a few kilobytes --- I'm curious about the thought process that could lead to someone uploading a considerable volume of potentially sensitive CSV data to this site, and then downloading a proportionally larger amount of JSON from it.

The site doesn't even appear to support HTTPS.

View on HN

Technically, all the file processing can happen client-side now, thanks to the HTMl5 file API. Users' data doesn't have to leave the browser.

[shameless plug] This is the approach I have taken creating a similar converter (which also works offline):

http://mango-is.com/tools/csv-to-json/

Yes, that is a good idea. However I chose to upload it in order to allow sharing the conversion via a unique generated URL.

Why not use location.hash and URL shortener? That way no upload is needed.

What's the maximum length of a URL?

Hint: a lot smaller than almost all the CSV files I've had to deal with.

To the grandparent: you might want to make it more explicit that you're actually retaining the uploaded data and not just using it to generate the result page.

If the information is sensitive, I sure hope the person does not upload it to the internet.

Reply on news.ycombinator.com