Design and ToDos
Most of the work to be done on FreedomBox is available at RoadMap and issue tracker Salsa). The following is an old list kept for historic reasons.
Objectives
use at home (expand: legal significance of 4th amendment context; non US-specific: Article 12 of the Universal Declaration of Human Rights)
Relevant protocols
- Identity
Gnupg, good old proven method to allow encrypting and signing your data and communication, features a versatile key management system as well as access modules for all kinds of public key directories. Usability considerations need to be considered.
WebID, draft definition of URI to defining "you" on the semantic web - i.e. works directly with FOAF, Sparql etc. Draft implementation seemlessly fallback to resolving via Webfinger if no FOAF data resolved.
OpenID, single sign-on
OAuth2, single sign-on plus authorization flows - IETF draft
- user info (metadata)
Webfinger, draft of a protocol for getting user info (metadata) associated with e-mail via HTTP
Fingerpoint, draft of a protocol for getting user info (metadata) associated with e-mail via HTTP - requires minimal implementation (need no processing beyond static http to serve an identity!) and works directly with FOAF and Sparql.
Base system
- Encrypted filesystem
Issues
- How is each box discovered and identified?
- Need some way of finding your mates
Most ISPs provide dynamic IPs. Would need to rely on external dynamic DNS service. (everyone else's Freedom boxes?)
possible solution: page kite
possible solution: unhosted
possible solution: p2p-dns modified to be cacheing and independent of .p2p TLD
- possible solution: set up a list of dyndns style services that freedombox will update with IP info. Good enough for most folks.
- Upstream bandwidth
- Very limited with typcial ADSL connections. How much of a problem is that if people keep downloading photos from it whilst you try to use the net?
- Coping with high demand
- Limited system resources mean popular hosted content (such as a popular social networking node) could easily make server unavailable
- How to cope with 'slashdotting'?
- Identity management
- Important to be able to identify yourself on various services so you know email and facebook and whatever IDs are all you, and should refer back to this FB for authentication. How do we do it? Is it needed in order to realise that an email addy is freedom-able and so signing/encryption can be used?
- Multiple identities needed e.g for two sites (e.g. home+college) or ID for FB and ID for mobile phone?
- Two boxes in one building (son/daughter brings FB home from college)
- Movable, transportable
- If a box is moved from one location to another and plugged in again, how does it continue to do what it was doing seamlessly?
- Storage: if it hosts all data one produces, plus backup from friends, it needs to house adequate storage, preferably commodity sata disks.
- For a purely online storage solution, this would be ok, but we would need a way to plug in or configure external storage. For example, I would want to plug in an external hard drive or configure it to use a NAS or a Eucalyptus cloud that someone I know operates.
General ToDo
Investigate similar stuff.
Intro |
Information |
Support |
Contribute |
Reports |
Promote |
|
|
|
|||||
|
|
|
HELP & DISCUSSIONS: Discussion Forum - Matrix - Mailing List - #freedombox irc.debian.org | CONTACT Foundation | JOIN Project
Next call: Saturday, April 13 at 14:00 UTC
This page is copyright its contributors and is licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.