Hacker Newsnew | past | comments | ask | show | jobs | submit | davewhat's commentslogin

http://learngitbranching.js.org/?NODEMO

I haven't seen a git article link to this amazing website recently. By far one of the best ways to teach someone git is to walk someone through git by executing commands and allowing them to see the visual representation of those commands.

There is also an amazing single-player learning mode.



Uber - Seattle, WA - Full Time

Uber has recently (3 months ago) opened an engineering office here in Seattle. We believe in owning things, and as such the engineering team here is focused fully on Uber's Scalability (think sharded database, service routing, service discovery, byte protocols replacing http, etc.).

The team is building out fast, and so far we have been putting together a great team of talent with a healthy mix of alumni from the area (Facebook, Foursquare, EMC/Isilon, Amazon, Microsoft, and several local startups). The working environment is ideal -- best ideas win, the tooling strives to let builders build, and individuals think of themselves as owners and not renters.

Come enjoy working for a hot tech startup at home in Seattle... help us build out our new office's culture... exposure yourself to amazingly tough engineering challenges...

Looking for:

- Software Engineers interested in scalability / distributed systems

https://www.uber.com/jobs/48886


Hello, I am a university student graduating next year, and I am very interested in any recent-graduate positions that uber has available - the website does not feature the usual "recent graduate" section that I am used to. Any pro-tips for me?


If you are looking for a position in Seattle, you can rest assured that we will be hiring recent-graduates for Summer 2016. At the current moment we are building out our office, which has us focused on senior engineers.

Summer 2016 will have both recent-graduate and internship positions for Seattle.


Looks like you got so many applications no human gets to read incoming resumes. What is the best way to contact you? Or contact me directly alexander.blez@ gmail .com


The flow does not originate at your site. Your site did not create the redirect URI that is being passed to Google / Twitter in your example.

The URL is generated by a malicious party. The URL constructed (1) sends the user to Google / Twitter for authentication, (2) includes a return URL of your open redirector, and (3) has your open redirect send you on to an evil site.


> Your site did not create the redirect URI that is being passed to Google / Twitter in your example.

Sorry, I don't understand this sentence.

The redirect URI is not normally passed to Google / FB / Instagram dynamically, but normally registered with Google / FB / Instagram once, when you set up an app with them (and get a secret key etc).

If someone else registered their own app with their own redirector, they wouldn't have my secret key.

Edit: removed Twitter, they use oAuth 1 which is strange / different / weird.


No, you do pass the URI dynamically, it's a required part of the Access Token Request: http://tools.ietf.org/html/draft-ietf-oauth-v2-16#section-4....

It's just that with a decent implementation, you should also be required to register it beforehand with the provider.


Not just a decent implementation; an implementation which meets the spec. This is not a problem with OAuth2, which explicitly requires registration of URIs where the implicit grant type is used, and covers other cases well in the Security Considerations section.


That makes a lot of sense: I've only really dealt with oAuth 2, as oAuth 1.0a is vastly more complicated and only Twitter seems to still use it.

Thanks icebraining & vertex-four.


Biggest wins (in my opinion):

- Persistent storage of up to 4K of data on the watch per app. Storage is a key/value dictionary. No single value may exceed 256 bytes. (Keys are 32 bit integers.)

- New JavaScript framework. Allows running of custom js in a sandbox on the Official Pebble Iphone app

  * Supports communicating (bi-directional at all times) between a Watch App and an Android/iPhone javascript companion app.
  * Supports HTML5 local storage (on the iPhone)
  * Supports location APIs (via HTML5 navigaor.geolocation)
  * Supports web requests (JavaScript's XMLHttpRequest())
  * Supports sending a simple title/text notification to the watch
  * Supports opening a webview on the phone inside the Official Pebble App and the ability to pass a string message back to the JavaScript app when the view is subsequently closed.


Windows WSYP Project -- http://www.youtube.com/watch?v=M-c0YSsF_O0

Such a good video... even this many years later.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: