Skip to content
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
Sean McGregor edited this page Dec 12, 2013 · 3 revisions

Deprecated

See Version List

The functionality outlined in "Caged" is the bare minimum required to begin integration testing with the internet. Caged will find Privly-type links on any web page, and replace them with the referenced, clear-text content. The lack of content encryption means Caged will never be "released," but it is enough to start testing Privly integration across the internet. Caged Functionality includes:

  • Read Unencrypted Content: Pulling remote content into the current page is the core functionality of Privly. The format for unencrypted links needs to be finalized.
  • Provides Modal Button: During testing people need the easy ability to turn the extension’s functionality on and off.
  • URL Parameter Support: The Privly-type link can optionally supply parameters, which will affect the operation of the extension. Parameters may give the following information:
  • Post to Anonymous Endpoint: We need a way for people to easily test the Privly extension. The anonymous posting endpoint supports content lasting one day before it is destroyed. To simplify security and sharing concerns, this endpoint allows anyone with access to the link to read the content.
  • User Authentication (single server): Authenticating users is a better means of proving the user is human than captchas. We need to allow people to create user accounts, even if we don't allow them to store data for long periods of time.
  • Broadcasts Privly Headers: We can't roll out new versions of the extensions and content server simultaneously. In order to push out breaking changes, we need a way to know which extension version is generating the request. With reliable version numbers we can gracefully integrate new extension versions more frequently.
Clone this wiki locally