Changing The OpenPhoto Project to The Photo Project or Trovebox as applicable
This commit is contained in:
parent
9f99ac2a12
commit
eabbc2f4ee
5 changed files with 10 additions and 10 deletions
|
@ -3,7 +3,7 @@ Authentication using OAuth 1.0a
|
|||
|
||||
### Using OAuth (1.0a)
|
||||
|
||||
A full introduction to OAuth is beyond the scope of the OpenPhoto documentation.
|
||||
A full introduction to OAuth is beyond the scope of the Trovebox documentation.
|
||||
In all reality you probably don't need to understand the ins and outs of OAuth, just grab one of our libraries.
|
||||
|
||||
* <a href="https://github.com/photo/openphoto-php">openphoto/openphoto-php</a> - Our PHP language binding.
|
||||
|
@ -14,9 +14,9 @@ In all reality you probably don't need to understand the ins and outs of OAuth,
|
|||
|
||||
### Obtaining a consumer key and secret
|
||||
|
||||
Since OpenPhoto is distributed the flow to obtain a consumer key and secret differs slightly from typical OAuth applications.
|
||||
Since Trovebox is distributed the flow to obtain a consumer key and secret differs slightly from typical OAuth applications.
|
||||
Typically you would sign up for an application ID and be given a key and secret to be used with your app.
|
||||
OpenPhoto differs because the host you'll be sending requests to is arbitrary and there's no central application repository.
|
||||
Trovebox differs because the host you'll be sending requests to is arbitrary and there's no central application repository.
|
||||
|
||||
### Resources on the web
|
||||
|
||||
|
|
|
@ -4,7 +4,7 @@ Response Envelope
|
|||
|
||||
----------------------------------------
|
||||
|
||||
### Standard OpenPhoto API response envelope
|
||||
### Standard Trovebox API response envelope
|
||||
|
||||
Every API returns a JSON response adhering to the following format.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue