-
Notifications
You must be signed in to change notification settings - Fork 9
Posts
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
For more details on the URL format, see the URL Specification.
These strings assign the privlyInjectableApplication
parameter with the name of the referenced injectable application.
- PlainPost
These parameters cannot be placed on the parameter string since that would result in their being transmitted to the remote server.
- privlyLinkKey: This key is used to decrypt the ciphertext. It may also be placed in the server parameters, but doing so is discouraged since it provides the parameter to the remote server.
These parameters can be on either the parameter string or the hash text.
- privlyDataURL: The injected web application fetches the content from this URL. When the application is injected by an extension, the content found at this URL will be messaged to this application from the extension.
These parameters are added by the extension.
- privlyOriginalURL: This parameter gives the original URL of the application. Privly-type extensions often have to change the source URL to point to local storage on the extension, but the extension still needs to provide the original parameters to the application. This parameter is only used internally in the extensions.
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
This is the high level process for posting content by the content server.
- (User Action) The user types the content into the Posting Application, selects which identities they want to share with, and submits the form.
- The content server then returns a URL for the content, which is placed into the host page
- None
The following network requests will be made by the application:
- Get user sharing lists and CSRF token
- Post Content and sharing list
This is the high level process for decrypting content by users who have permission to view the content.
- Request the content
- None
The following network requests will be made by the application:
- Get Content
- Post an Update to Content
Foundation Home
Repository List
Development Mailing List
Testing Mailing List
Announcement Mailing List
Central Wiki
Submit a Bug
IRC
Download Extension
These documents are under active development and discussion.
Credit: This Google Summer of Code content is licensed under the CC Attribution-Noncommercial-Share Alike 3.0 Unported license furnished by the Sahana Software Foundation.