I'm in a similar situation to yours with similar numbers now. Just curious, what technology are you using? I'm on Rails, outside the valley, but my clients are inside. Ironically enough, 2 years ago I was working for $500/week, and working twice as hard as I am now
Current contract is 80% PHP. I usually prefer to stick with Python, Clojure, and Go. Most of my past work has been Python (including when I was CTO at a funded startup).
It basically means something that currently isn't your full-time gig (although I suppose someone could be independently wealthy and working on their own project full-time). I want to talk to people that are taking their free time and using it to build projects and be productive. The people that are scratching an itch and can't be stopped from building things. It would be amazing if some of these projects end up turning into companies and full-time jobs, but that doesn't necessarily have to be the end goal. I just want to interview people that are passionate about what they are doing and can't help doing it with the time they have.
Yep. That was my question off the bat. (That and what did Gruber mean by "private"). I think the TL;DR is "they don't sell your information to advertisers/use your call information to market to you". And perhaps some ease of use advantages, especially for iOS users.
At first, that didn't seem appealing to me. I've been a GV user since way back in the GrandCentral days. But, frankly, it is an essential service for me. And you know what they say, "If you aren't the [paying] customer, then you are the product." It would be nice to have actual customer support and actual accountability. GV is wonderful, but it's also a complete support black hole.
We don't automatically send anything through LinkedIn. However, we have a feature that allows an entrepreneur to send an invitation to someone else via LinkedIn's API. In order for that to function we need the permissions you are referring to. When we have more time we will probably reduce the number of requested permissions for general users.
I implemented one for work. Basically, you have a websocket for each client, and any message received from client X is transmitted to clients Y and Z. There's not much to it at all; the magic happens client-side.
