There is a paper linked on Wikipedia stating that studies conducted in Germany showed that "Water fluoridation was followed by a decrease of caries, and interruptions in fluoridation were followed by increasing caries levels." but also "There was a significant caries decrease down to the lowest DMFT (2.0) since 1959 in spite of the fact that only F-poor water was available over years [...] explained by changes in caries-preventive and environmental conditions."

https://onlinelibrary.wiley.com/doi/abs/10.1034/j.1600-0528....

Which costs $199.

Sounds very interesting, do you have an image in the docker hub?

I'll get around to putting up a GitHub repo soon, but for now you can pull gigablah/busybox-node. You can either override the entrypoint or daemonize it and use docker exec.

Is there a ticket in the docker project? I would like to follow the progress on this one.

Everything I could find was this ticket: https://github.com/docker/docker/issues/5305

We are talking about Twitter here. They can't avoid collisions even inside their own company:

https://www.twitterflight.com/ and http://flightjs.github.io/

Well, because there's <ANY_WORD>.js. It's quite obvious that the links you copied have hardly any overlap, and I much prefer a simple generic name rather than a made up word which is hard to remember and doesn't make much sense.

Which, by the way, was discontinued: http://techcrunch.com/2014/03/08/mozilla-stops-developing-it...

The right intrepation is that Mozilla is not funding the project, but the protocl (browser id) and Persona source code are still out there.

The downside is Mozilla MIGHT sunset their Persona infrastructure one day. But that's not a real concern because Mozilla is never interested in being people's Persona verifier. They were hoping Persona would take off and people would host their own bridge, instead of relying on Mozillia's.

Persona was not discontinued. Persona lost active development and marketing. A wrong decision, but not one that affects the protocol itself.

If I have a specific task the workflow for me looks like that: 1. Search through Google, Github, Unheap, npm, bower, jster and so on. 2. Compile a list of useful packages and tutorials for every one of them. 3. Select the best package for the task.

So I created this list to not have to go through step #1 and #2 every time.

What project details would you like to see for each item on the list?

It's tough because : 1. There is a lack in uniformity: you have CSS solutions, jQuery extensions, node.js packages, articles, books, videos and so on. 2. Every bit of information you include makes the list bloated. I think it's enough to have the category, a link, and maybe a short description. If I need a template engine for a project, I will click on every link and look through them anyway.

Please make a suggestion how you would like this list to look.

Thank you for building it!

pineapple.io is awesome, I read it ever day. It's more of a news website for me though, not a reference.

Awesome! :) Great list by the way -- good work