diff options
| -rw-r--r-- | controllers/controllers.php | 5 | ||||
| -rw-r--r-- | views/creating-a-micropub-endpoint.php | 10 | ||||
| -rw-r--r-- | views/privacy.php | 12 |
3 files changed, 22 insertions, 5 deletions
diff --git a/controllers/controllers.php b/controllers/controllers.php index 0de366b..b6bb30a 100644 --- a/controllers/controllers.php +++ b/controllers/controllers.php @@ -119,6 +119,11 @@ $app->get('/docs', function() use($app) { $app->response()->body($html); }); +$app->get('/privacy', function() use($app) { + $html = render('privacy', array('title' => 'Quill Privacy Policy')); + $app->response()->body($html); +}); + $app->get('/add-to-home', function() use($app) { $params = $app->request()->params(); diff --git a/views/creating-a-micropub-endpoint.php b/views/creating-a-micropub-endpoint.php index d911ce6..4da9510 100644 --- a/views/creating-a-micropub-endpoint.php +++ b/views/creating-a-micropub-endpoint.php @@ -18,7 +18,7 @@ The example code here is written in PHP but the idea is applicable in any langua The request will contain the following POST parameters: * `h=entry` - Indicates the type of object being created, in this case an <a href="http://indiewebcamp.com/h-entry">h-entry</a>. -* `content` - The text content the user entered, in this case the caption on the Instagram photo. +* `content` - The text content the user entered * `category` - A comma-separated list of tags that you entered * `location` - A "geo" URI including the latitude and longitude of the photo if included. (Will look like `geo:37.786971,-122.399677;u=50`, where u=50 indicates the "uncertainty" of the location in meters) * `in-reply-to` - If set, this is a URL that the post is in reply to @@ -32,11 +32,11 @@ Authorization: Bearer XXXXXXXX ### Verifying Access Tokens -Before you can begin processing the photo, you must first verify the access token is valid +Before you can begin processing the request, you must first verify the access token is valid and contains at least the "post" scope. How exactly you do this is dependent on your architecture. You can query the token endpoint -to check if an access token is still valid. See [https://tokens.indieauth.com/#verify tokens.indieauth.com] +to check if an access token is still valid. See <a href="https://tokens.indieauth.com/#verify">tokens.indieauth.com</a> for more information. Once you have looked up the token info, you need to make a determination @@ -58,7 +58,7 @@ one that can create posts on your website. A valid request to create a post will contain the parameters listed above. For now, you can verify the presence of everything in the list, or you can try to genericize your -micropub endpoint so that it can also create [http://ownyourgram.com/creating-a-micropub-endpoint photo posts]. +micropub endpoint so that it can also create <a href="http://ownyourgram.com/creating-a-micropub-endpoint">photo posts</a>. At a bare minimum, a Micropub request will contain the following: @@ -91,4 +91,4 @@ and optionally an HTML or other body with more information. Below is a list of p <?= Markdown(ob_get_clean()) ?> -</div>
\ No newline at end of file +</div> diff --git a/views/privacy.php b/views/privacy.php new file mode 100644 index 0000000..acdf235 --- /dev/null +++ b/views/privacy.php @@ -0,0 +1,12 @@ +<div class="narrow"> + <?= partial('partials/header') ?> + + <h2>Privacy Policy</h2> + + <p>Quill enables you to post text, bookmarks and likes to your own wbesite</p> + + <p>Quill does not store your posts itself, but does cache the last response from your website and provides it to you for debugging purposes.</p> + + <p>If you connect Quill to your Facebook or Twitter account, Quill can post to those sites on your behalf. Quill will never post anything to your accounts without an explicit action on your part.</p> + +</div> |