Twitter login now prompts for read-only permissions, instead of read+write. I think that was the most popular suggestion from the HN crowd. Thanks all.
I'm a technical lead on the Google+ team. Ask me anything.
31–40 of 42 posts
Re: I'm a technical lead on the Google+ team. Ask me anything.
#32Earlier quoted context omitted.
Sorry, we're working on allowing other login mechanisms. The publishing permission is so you can tweet out questions you ask easily if the box is checked. We never misuse any permissions.
While I realize that part of this comes from the structure that Twitter's authorization takes, which doesn't allow fine-grained permissions, ideally I'd love to see more sites asking which permissions you want to grant them. I almost never want to allow a site to tweet on my behalf (though I don't mind if it wants to send me over to Twitter with a suggested tweet), and I don't want to trust the site itself to not abu…
We now prompt only for read access. Later on we might add back in some options to grant read+write access in order to more deeply integrate it with Twitter.
Re: I'm a technical lead on the Google+ team. Ask me anything.
#33Earlier quoted context omitted.
I stopped reading after realizing they didn't use reddit for an IAmA. EDIT: Directly.
Why do you think the fact they don't use reddit matters? On a side note: I think they managed to come up with a good UI targeted at the use case of asking questions to one person.
Answers like "We're a surprisingly small team" would never fly on Reddit
Re: I'm a technical lead on the Google+ team. Ask me anything.
#34Earlier quoted context omitted.
I stopped reading after realizing they didn't use reddit for an IAmA. EDIT: Directly.
Why do you think the fact they don't use reddit matters? On a side note: I think they managed to come up with a good UI targeted at the use case of asking questions to one person.
There's no followup, which is an essential part of asking questions, both to deal with evasion but also to clarify what you were asking. If they don't answer your question, you have no recourse, no call out, no opportunity to say: "Obviously you don't know the exact number, but is it ten or a hundred or a thousand?"
Re: I'm a technical lead on the Google+ team. Ask me anything.
#35"I think everyone feels the need to share different things with different people--and the desire to be able to hear from certain circles without losing them in the overall stream." Personally I'm interested in the real numbers behind this. Have people actually split up their social network into circles? To what degree? Are people actually using the feature the way it was intended? How many posts are public or effecti…
To me, G+ feels like a better content sharing network rather than a social network. For example, you can't even privately message somebody.
There are two ways to send private messages: 1) The chat, which you have to enable for circles or individuals. 2) You can contact anybody with a private message by sharing a message just with that person. To find out if a message you received is private, you have to check the sharing details, though.
Re: I'm a technical lead on the Google+ team. Ask me anything.
#36Earlier quoted context omitted.
that's just propaganda. Their Chrome team alone is over 300 engineers.
It depends what you consider a team. The "Chrome" team is big, but the team that works on the HTML5 parser within Chrome is pretty tiny, as is the team responsible for V8, as are many of the other teams.
How does "pretty tiny" compare to "surprisingly small"?
Re: I'm a technical lead on the Google+ team. Ask me anything.
#37Earlier quoted context omitted.
Why do you think the fact they don't use reddit matters? On a side note: I think they managed to come up with a good UI targeted at the use case of asking questions to one person.
There's no followup, which is an essential part of asking questions, both to deal with evasion but also to clarify what you were asking. If they don't answer your question, you have no recourse, no call out, no opportunity to say: "Obviously you don't know the exact number, but is it ten or a hundred or a thousand?"
"both to deal with evasion but also to clarify what you were asking"
Very true. They would need to add comments and allow the interviewee to edit his/her answers.
Re: I'm a technical lead on the Google+ team. Ask me anything.
#38Earlier quoted context omitted.
It depends what you consider a team. The "Chrome" team is big, but the team that works on the HTML5 parser within Chrome is pretty tiny, as is the team responsible for V8, as are many of the other teams.
How does "pretty tiny" compare to "surprisingly small"?
The same as the ratio of unicorns to leprechauns.
Re: I'm a technical lead on the Google+ team. Ask me anything.
#39Earlier quoted context omitted.
There's no followup, which is an essential part of asking questions, both to deal with evasion but also to clarify what you were asking. If they don't answer your question, you have no recourse, no call out, no opportunity to say: "Obviously you don't know the exact number, but is it ten or a hundred or a thousand?"
"both to deal with evasion but also to clarify what you were asking" Very true. They would need to add comments and allow the interviewee to edit his/her answers.
Comments are coming; answers can already be edited
Re: I'm a technical lead on the Google+ team. Ask me anything.
#40Earlier quoted context omitted.
It depends what you consider a team. The "Chrome" team is big, but the team that works on the HTML5 parser within Chrome is pretty tiny, as is the team responsible for V8, as are many of the other teams.
How does "pretty tiny" compare to "surprisingly small"?
I believe "pretty tiny" is smaller.