=== Plugin Name ===
Contributors: bastb
Donate link: http://www.tenberge-ict.nl/tools/wordpress/lips/
Tags: LinkedIn, API, OAuth, profile, zzp, freelance, cv, experience, resume, template, Smarty, templating, business, job, hiring, professional, stackoverflow, stackexchange, reputation, serverfault, superuser.com,
Requires at least: 3.3.1
Tested up to: 3.4.1
Stable tag: 0.8.4
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

This tool downloads your LinkedIn® profile and maintains a selectable page on your WordPress installation.

== Description ==
LiPS creates a local copy of your LinkedIn® Profile, using the LinkedIn® REST API to get the data. There's no page-parsing or screen-scraping, it's just your data, structured in a way it allows for automatic processing using a template.
The REST API uses OAuth, so it does not need to know your LinkedIn® username and password. It uses a token which is granted access to your data. Revoking access is easy too, in fact, it's done automatically.
There's a drawback, and that's the user needing a LinkedIn Developer account.

The tool processes the profile data and creates a page, using the Smarty templating engine. Smarty is included in the distribution, as are two minimal templates. You can choose which page to use and which template to use. In fact, you can even create your own template. Learn how through the Donate link.
  
There is one more important feature. LiPS can also create posts for each position in your profile, allowing you to add more detail, such as (ex) coworkers adding their appreciation in working with you through the comments system build into WordPress™. Posts maintained by this tool are filtered from your "normal" blog stream, but you can link to them from any other page. You can use 
a different template for the post content too.

Really impress an employer or client? Add your StackExchange reputation from one of their major sites to your resume. Just select the site you registered on and enter your login or account id. Your account details will be automatically included when you update your profile page.

One more thing that needs to be clear. You're using this tool at your own risk. I'm not responsible for any type of damages caused by this tool.

Do you think you found a bug? Do you want additional features or help? Contact me through http://www.tenberge-ict.nl/contact/english/.

== Installation ==

This section describes how to install the plugin and get it working.

1. Upload `lips` to the `/wp-content/plugins/` directory
1. Activate the plugin through the 'Plugins' menu in WordPress
1. Open the WordPress Dashboard, click Tools and LinkedIn® Profile Sync.

== Frequently Asked Questions ==

= What's with these pop-ups? =
These are there due to my understanding of the LinkedIn® terms of service. LinkedIn Corporation wants the user to have some way of verifying where the data is from.

= Why do I need to authorize the plugin every time I want to fetch my profile? =
I have not found a way to request read-only access to the profile. This means that an OAuth token is granted permission to modify your LinkedIn® data too. Saving the tokens would allow everybody with access to the blog database to perform actions on LinkedIn® on your behalf.
Both revoking access and just not saving the OAuth tokens is a great way to prevent that.  

== Screenshots ==

1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
the directory of the stable readme.txt, so in this case, `/tags/4.3/screenshot-1.png` (or jpg, jpeg, gif)
2. This is the second screen shot

== Changelog ==
= 0.8.4 =
* Fixed error in jQuery scripting.
= 0.8.3 =
* Fixed error in jQuery when pressing the Save button without downloading the profile.
* Added support for Stack Exchange QA sites.
= 0.8.2 =
* Initial release. 0.8.0 was under active development 

== Upgrade Notice ==
= 0.8.0 = 
This plugin uses metadata stored in the WordPress database. This metadata gets regenerated each time the plugin is activated. The template metadata has changed in 0.8.2, so you'll need to deactivate and activate the
plugin right after installation. This is a generic update issue.

== Arbitrary section ==
= Things to do =
 * it's probably a good idea to encrypt the OAuth authenticated tokens with
  some form of a password, because anybody with access to the MySQL database
  will have access to port of the authentication details. 
 * verify whatever a template generates -> the page template must start with a <h1> or
  <div>, same for a post.
 * use the other OAuth library, so the limiting PECL extension is not needed anymore.
 * allow a user to remove languages, thus shortening the language list.
 * optimize the jQuery code. It's a bit bloated and contains different styles at once.
 * ...