The key finding of a new article in the Feb. 27 issue of the journal PLoS One links sugar to diabetes like cigarettes to cancer: “Each 150 kilocalories/person/day increase in total calorie availability related to a 0.1 percent rise in diabetes prevalence (not significant), whereas a 150 kilocalories/person/day rise in sugar availability (one 12-ounce can of soft drink) was associated with a 1.1 percent rise in diabetes prevalence.”
This is something a few people asked for. What would you like to use it for? Besides matching people to people, you can match people to products (if properly tagged). Do you see other uses for something like this?
We are a startup called Glancee. We build a mobile app (iphone version + android version) that finds people in your area with friends or interests in common with you. The apps are native objective-c and java apps, and the backend is a mix of python, mondodb, and a bit of erlang.
A month ago we decided to build a facebook app to reach users that don't have a smartphone. We chose not to change one bit of code in the backend, and we were able to build the web app in 3 weeks with backbone, jquery, and websocket-js.
The app is just one 40-line html page, the rest is javascript (and templates embedded in js). You never refresh the page when clicking a link, which gives you the feeling of using something as fast and robust as gmail.
CSS files and JS files are compressed with requirejs before being deployed, so to load the page you need three requests (plus images). Right now our biggest bottleneck is the facebook api, which is tremendously slow.
It's great to see Jig finally launching to the public. I had a first look in June, when I used it together with 200 others foo campers to coordinate the trip to Sebastopol. Then I used it again when I moved from Chicago to San Fran to find a new accommodation.
I don't see Jig as a Q&A site because needs, unlike questions, tend to be personal in nature and change (or even die out) over time. The same need could be posted by multiple people in different locations, or by the same person over time, and all could get different answers.
With that said, Jig will have to fight the only known certainty of any online community: as your user base grows, your quality declines. I can already notice the difference in both the needs and the answers posted now from those of just few weeks ago. Let's hope the Jig team has a strategy in mind to keep the trolls at the gates.
Yep! We have a lot of ideas, and a bunch of them came from reacting to the traffic.
It looks a lot higher quality if you load your personal networks from twitter/facebook/etc but the traffic goes by much slower, so we need to work that.
https://youtu.be/dHo_EUyShOg