I briefly started working on an application that would have many positive benefits for the LinkedIn community. After reading the API terms and conditions, it was very apparent that I would not have been able to achieve my goals, so I stopped.
The terms and conditions are pretty restrictive, but they are provided. I should not have come as a surprise that their API access was cut off. You should not be developing an application that not only is dependent on one company's API, but also against their terms of service (without an explicit authorization/partnership).
this is the point I came to make. LinkedIn's TOS specifically disallow apps that cut into their turf. These guys should be negotiating to get their codebase bought and their team acquired.
The terms and conditions are pretty restrictive, but they are provided. I should not have come as a surprise that their API access was cut off. You should not be developing an application that not only is dependent on one company's API, but also against their terms of service (without an explicit authorization/partnership).