Skip to content
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.

Burrowing

Sean McGregor edited this page Dec 12, 2013 · 3 revisions

Deprecated

See Version List

"Burrow" focuses on the development of the content server. Upon release, Burrow will allow permanent storage of content and provide paid hosting. Temporary posts, like those found in Caged and Barn will likely still be free.

Philosophically, the content server has three purposes:

  1. Store and permission content
  2. Provide a web application to view content without an extension
  3. Provide data management tools for one’s own content

The web application will not directly provide social network functionality, because links are shared across existing social networks and emails. People will be able to read through their posts on the content server’s web application without giving the server access to the decrypted text.

Out of scope use cases include friending functionality, user inboxes, or anything not focused on linked communications.

Rule-based access restrictions

Initially, the content server will validate identities (ex: the server will send an account confirmation email), but when the identity system is completed, the content server will use the identities reported by the identity system. The following access restrictions will be implemented in the content server independently of the identity system.

  • Share by Password
  • Share by Email
  • Share by Domain (Organizational sharing)
  • Share by Diaspora Aspect, Google+ Circle, Twitter List, etc
  • Share by IP Address
  • Share by Geography (GeoIP)
  • Share by List of Sharing Rules

Permissions to read, update, destroy, or share can be granted to identity types covered by the rule based restrictions.