Posts

Status and Overview

Status: Under development
Plain Posts are the injectable application endpoint developed for the Proof-of-Concept of Privly. Plain Posts do not implement any content cryptography. The current effort for plain posts is to refactor it into an application we can eventually serve directly from the extension.

Plain Posts were developed as a Ruby on Rails application. We need to refactor:

• Package all the templates and scripts together into a static application (no templating) and make it indifferent to where the content is stored
• Render the posted Markdown on the client

Which Systems Have Access to What

We list which components have access to particular pieces of information below:

• Content Server (Privly or similar party)
• Cleartext
• Link
• Host Page
• Link
• [Injectable Application](Injectable Applications) - Posting
• Cleartext
• Link
• [Injectable Application](Injectable Applications) - Reading, non-permissioned
• Link
• [Injectable Application](Injectable Applications) - Reading, permissioned
• Cleartext
• Link
• Extension
• Cleartext
• Link
• Encryption Library
• Nothing

Posting Process

This is the high level process for posting content by the content server.

1. (User Action) The user types the content into the Posting Application, selects which identities they want to share with, and submits the form.
2. The content server then returns a URL for the content, which is placed into the host page

Cryptography API Function Calls

• None

HTTPS Requests

The following network requests will be made by the application:

• Get user sharing lists and CSRF token
• Post Content and sharing list

Viewing Process

This is the high level process for decrypting content by users who have permission to view the content.

1. Request the content

Cryptography API Function Calls

• None

HTTPS Requests

The following network requests will be made by the application:

• Get Content
• Post an Update to Content