Charlesmigli

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 ?

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

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.

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?

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...

There is a huge gap on how people behave at home and at work. Following our primitive instincts our home has to be defended. That's why we don't like somebody walking into it and doing stuffs we are responsible for. There is a summary available for this blogpost here http://tldr.io/tldrs/5155bc59ccd25bb8600005c1/what-being-a-h....

Here is an short summary of the article for those who want to catch up the discussion http://tldr.io/tldrs/5155b26accd25bb86000051f/soaring-bee-de...

Thanks a lot for the traduction. This summary has been added to tldr.io, see here http://tldr.io/tldrs/5134660e28b6ae385b0000de/microsoft-owes...

Here are the highlights the author has extracted from his study http://tldr.io/tldrs/5123bba2793151711c00001b/good-sleep-goo...

Very useful post. I put the tl;dr version the author wrote on tldr.io http://tldr.io/tldrs/51238dc4b3a7a6ca1000002f/step-by-step-l...

I posted it on tldr.io, it's now accessible by everyone at this url http://tldr.io/tldrs/511e2afb84eebe2d69000006/that-tesla-dat...

Thanks for the tl;dr.

Awesome summary! You should love http://tldr.io :)

Thx for the feedback I'll make a blog post out of it.

I'm indeed a cofounder of tldr.io but that's not a mystery, Googling my alias will give you my Twitter profile with my bio as the first result.

List of extensions: Clearly, tldr.io, Pocket, RSS Subscription, TooManyTabsOpen, Buffer, High Contrast.

It's to avoid people to post links in comments and benefit from HN's popularity to increase their rank in the search engines results. By specifying rel=nofollow HN indicates the crawlers from Google not to count this hyperlink as a reference in their ranking algorithm. This is a common practice that you can see on other popular forums.

Hey Andreas, it's not down anymore but here is the tl;dr version:

- Automated text-to-speech radio of Hacker News front page's links.

- Listen instead of reading.

See it here http://tldr.io/tldrs/50fe8b4c8aa388171700184f/soundgecko-hac...

Yes I agree. tl;drs versions are especially useful for high quality content like the articles on http://longreads.com.

So the TL;DR of this article is:

- Author should summarize their idea in the first sentence of their writings.

- Prefixing this summary with TL;DR is useless and asinine as it stands for "Too Long; Didn't Read".

http://tldr.io/tldrs/50f34acc3ea2fa3e06001f25/tldr-is-unnece...

As a cofounder of http://tldr.io I'd say that having a tl;dr separated from the main article is very useful for readability. Like ps for example it helps structure the text. tl;dr version of articles are essential to get directly to the point. As an heavy reader I like to have theses summaries detached from the article.

Very interesting and actionable. One thing I disagree is point #5 because your previous users could feel screwed.

Here are the 10 hacks

1. Guest post (send editor email with post and short intro)

2. Offer premium giveaways

3. Use Rapportive to find and connect with anyone

4. Use Hacker News (~10k to 50k visitors for #1)

5. Drop the app to free after a regular pricing

6. Create one day viral projects to promote your brand

7. Use share buttons

8. Distribute on AppSumo (+730k subscribers)

9. Reach out bloggers (provide value before asking for something)

10. Use Dropbox style to incentive and gamify signups

Accessible on this link http://tldr.io/tldrs/50c74e31babbb5f813000b32

I understand that they provide all the back-stuff to store your metrics data and an easy way to plug to the data to draw charts, analytics dashboard. I find it really cool tough I don't know if people/startuper prefer this flexible solution as Mixpanel one wich gives you already the front end functions. I don't know if they do but they should provide templates for creating a funnel, a retention graphs etc.

Doesn't phantomjs do the thing for you?

I didn't know much about the KDE e.v. but now I feel like supporting the community :). Awesome work these guys did. Is there the same kind of organization for other main open source projects/communities? I highlighted the sentences I found the most interesting here http://tldr.io/tldrs/50b86deeada40f08170009f3.