Happy to get your feedback to make it more comprehensive

Awesome, how often do you plan to test it ?

Is the code available on Github ?

Yes you can find it at the end of the article ;)

Nice post. I see that you used dc.js, could you share some code ?

The code to process the lending club data is done in python. I got the full history of all payments made on the platform and pre-process it to have something that's light enough to be explored with a good user experience.

For the viz', yes I used DC.js, I can open source the .js if you guys want it.

Hi Clement, very neat dataviz ! How did you get the full history of all payments ? Is it available in the open ? What is 100mdeep btw ? Just a blogging site you are bootstraping or any plans to make a living out of it ? (We met a few months ago @ ToucanToco...)

100m is the depth human can free dive to. Without any aid. Without any fins.

https://en.wikipedia.org/wiki/Constant_weight_apnea

Tribute to people who go deep into things ;).

Nice image! I'm a big fan of Guillaume Nery, the french free diver (4 word records). Actually Constant weight divers are allowed to use fins (monofins most of the time), although they use it only to get to ~30m deep, after that point, the pressure is such that the volume of the body decreases and Archimedes thrust is no longer sufficient to compensate for the weight... so the diver can descend without any mouvement... It's very impressive to see (http://www.liveleak.com/view?i=d4a_1244462128).

Funny to read about this a few days after Guillaume Nery's accident: a line was set to the wrong depth causing the diverto dive to -139m/456ft instead of -129m/-423ft that he had announced the night before...

I did this work for myself at first as I invested some money on the Lending Club.

Plans will depend on feedbacks I receive. If it generates enough interest I will develop the project into something bigger.

Funny you mention ToucanToco. They helped me in debugging the viz.

Thanks for the replies, what about the source of the data ?

I'd imagine we'd all appreciate that!

I'll update the post and put a link to a github

I highlighted the conclusion of Lerner's analysis here https://tldr.io/tldrs/516f951cc8cb5249260002c5/the-well-dese.... This looks pretty convincing even tough one might think that Satoshi would own multiple wallets.

I think no algorithm can perform such a summarizing task. If you're looking for summaries of PG's essays see here http://tldr.io/discover/paulgraham.com.

As as cofounder of http://tldr.io this confirms our vision that for now (and for many years) only people can perform such a hard task like summarizing.

I agree with "for now" but not "for many years". Right now, most or all automatic summarizers are doing extraction. Which is just lifting sentences from the original article itself. It is different from the human perception of summary, which is abstraction. That uses the most important parts of the article and paraphrase it for easy reading.

Right now, abstraction or paraphrasing is hard to do by a computer. But I think and hopefully it will be possible in few years time. There are various open source and academic tools that can do some pretty good NLP. I'm looking into Apache OpenNLP, and WordNet. I'm hoping for 2 or 3 years time.

BTW, I have an app similar to your tldr.io. Check my HN comment (https://news.ycombinator.com/item?id=5523770) for more info about it. ;)

Changing the sentences adds bias. Maintaining the author's intent is important.

Generating news highlights from lots of sources might be cool as computer generated content. But rewriting an author's story in new words is not adding value it is just ripping them off.

Thanks. I got pretty good insights. Bias doesn't come into my mind. So you're saying multi-document "summarization" maybe the next step of consumer automatic summarization? There are many research about multi-document summarization, and will look into it.

It seems like your comment was well intended, but you come off as a bit presumptuous.

The problem TODAY is not whether or not a computer can summarize, but rather to what extent we as humans are satisfied with the computer's summary.

In some cases a dumb summary is good enough (first 200 characters for example). Given this baseline, and a target (human summary), you have to admit it's really an incremental process.

well put, hayksaakian. Also, never underestimate the built in auto-correct of the human mind :) There will always be a market for expert-curated approaches, but sometimes it's just cheaper to algorithmically "Crunch" it. Sometimes RAIN MAN counting toothpicks is enough, but when you need Ramanujam... :D

Also, do keep in mind... this is 2 hrs worth of coding time late on a sunday night. I don't have a CS degree, just a utilitarian/curious programmer who sometimes is stupid enough not to realize how hard a problem I'm tackling. :) Someone better qualified can do a much better job. Sometimes "just good enough" is good enough! :)

People are inherently biased. It's impossible for any person to read news and not inject their own personal tendencies into a summary they write.

Yes that's indeed the conclusion of the article that one should prefer dynamic warm up instead of static stretching. For long efforts it says that post stretching help to recover (The other takeaways of the article can be found here https://tldr.io/tldrs/515d3491207be0f11e0007bf/reasons-not-t...)

This post is fundamental to understand the ins and outs of Asm.js this was really helpful. It deserves its summary to make it even more understandable! http://tldr.io/tldrs/515c59e49ac882db1600010b/asm-js-the-jav...

Asm.js's support should make sense for Chrome OS no?

Nice summary, never heard of tldr.io, looks useful.

The form of the content is perfect for me, I don't see why he says it's a wall of text. It was very clear and easy to follow. Extracting the key takeaways to make the discussion richer was easy: http://tldr.io/tldrs/5156cd92b0eb7fae5800016b/lessons-learne...