daveman692

Structure wise the Digital Service is made up of a headquarters team within the White House, 18F which is an internal software development organization within the General Services Administration, and then embedded teams growing to be within each cabinet level agency. This creates a mixture of distributed execution plus centralized resources to help each team as needed.

Hey, since I can't find your name or contact info on your account I figured I'd comment saying that I run Bootcamp and it sounds like we should chat (dr@fb.com) :)

I feel like this is what the rating system helps deal with. You should be finding yourself with drastically more taxi experiences where 20% is a reasonable tip.

The earlier drafts were much more like that. They were largely a collaboration between a few web companies who had deployed OAuth 1.0 with Dick Hardt who had written WRAP at Microsoft. One of the major design goals was producing a protocol simple enough that client developers would not have to use libraries.

I was pretty happy with this result since we could write a simple page like https://developers.facebook.com/docs/authentication/server-s... which conformed to the spec (http://tools.ietf.org/html/draft-ietf-oauth-v2-12#section-4....) and was an easy to implement explanation of authenticating a user.

But the OAuth 2.0 spec we were working off of is now eighteen months old and as Eran said the vast majority of those contributors have drifted away from the effort over this past year :-\

It's a bar on Virgin Atlantic :)

Really like the transparency and applying the same rules, but at the same time when I search for "Google Chrome" the single ad in a yellow box above all of the results is for http://www.google.com/chrome. I guess I wonder if this page rank demotion will really make a difference since Google still controls that ad spot.

Menlo Park - Facebook

I manage one of our tools engineering teams focused on making it easy for employees to quickly find the right information and keeping it up to date. But there are a number of different tools engineering teams focused on things from tools engineers use daily to how we can better support users.

Email is on my profile.

https://www.facebook.com/careers/department.php?dept=enginee...

You're able to apply via email if you don't wish to be logged in to the site. Each job has a unique email address such as careers+a2KA0000000LhWnMAK@facebook.com which is for tools engineering in New York.

Sorry, but this really feels like hyperbole to me. For two reasons:

1) Before any action is shared back from the site to Facebook, the user has agreed to authorize that site (application) and add it to their timeline. Part of that dialog shows what's going to happen (https://developers.facebook.com/docs/beta/authentication/).

2) There are plenty of other examples around the web where submitting a HTTP GET request results in an action. For example, clicking an up arrow on Hacker News submits a GET request which increases the karma score on another author. What becomes more important is how you protect against XSRF and crawlers not accidentally changing state within your app.

This is my old first draft from last year. Others have been working on making it real over the past few months but the site hasn't been updated yet.

There's also a two minute version at https://www.facebook.com/video/video.php?v=778890205865&....

Cherry picking based on which engineers are around is much more about our daily releases. Everything checked into trunk on Sunday will go out on Tuesday. But if I've requested a diff be merged for the Wednesday release, it won't happen unless I've told request_bot that I'm around to support my changes. This also means that if there are merge conflicts, the engineers who wrote the patches will be there to help resolve them.

Then corrected himself to subversion and git.

This would become quite a bit simpler if they also moved to OAuth 2.0 (bearer tokens over SSL) instead of sticking with 1.1 (HMAC signatures).

Any info on where to buy one of the hardware kits?

I don't see the giant gate that they had in the video though.

Think it depends on the cost. Got mine for $99 which it is certainly worth! The 15% Uber discount makes up for that by itself. Would be harder to justify at $500.

Because that's how Tom dresses. He's not a "corporate guy" but manages the team who runs our data centers and was directly involved in building this one.

Amir Michael who worked on the hardware team said, "The utility provides us with AC voltage which we then convert to DC very close to the motherboard in the power supply. Our goal was to bring the high voltage as close as possible to the load to minimize IR losses. We could do an efficient AC –DC conversion in the rack and then distribute DC to the individual servers but that would mean several feet of low voltage conductors which would be made from large copper bars and a would have higher IR losses."

Am I mean for just not caring what's currently trending on Twitter? Feels like a similar problem to showing ads on blogs. I'm there for the content and the ad has to be exceptionally good in order to get any of my attention.

We'd be more than happy to host a SHDH. Shoot me an email at dr@fb.com.

It's under "Account Security" on https://www.facebook.com/editaccount.php?ref=mb&drop.

There's definitely a desire to build out more environments. Just decided to get it up and running on x86 first with both 32 and 64 bit architectures on a variety of Linux distributions.

I interact with the IRS once a year having to remember a short PIN I created years ago and can't figure out how to change. My bank has a very strong knowledge of who I am partially via http://en.wikipedia.org/wiki/Know_your_customer and because I login to it on a much more frequent basis.

It isn't that my bank would change the role of the IRS, but I'd login to the IRS using a strong identity issued by my bank versus this silly PIN I use today.

This headline is actually pretty misleading. From what I've seen of the project, it is not about the government issuing online identities. Rather they've realized that people already have identities from services like Facebook and Google as well as banks.

This project is aimed at making it possible for people to interact with government agencies using identities they already have. Some interactions require very little security and knowledge of who a person is (leaving a comment here for example) while others (paying your taxes) require quite a bit.

A bit strange though when comparing the pie chart with the other graphs.

http://www.facebook.com/notes/facebook-engineering/the-under... talks a bit more about this decision.

That comment is in Primer which is a very small piece of JavaScript loaded at the beginning of every page.

As a number of other people have pointed out, we (I'm an engineer at Facebook) use http://www.java.com/js/deployJava.txt which Oracle has released under the BSD licensed. One of the requirements of the license is that their copyright header is preserved when distributing the source code.