Differences between revisions 37 and 38
Revision 37 as of 2010-08-07 18:05:07
Size: 5575
Editor: TheAnarcat
Comment:
Revision 38 as of 2010-08-07 18:16:57
Size: 5556
Editor: TheAnarcat
Comment: triage through todo, add peer-to-peer to vision statement and cleanup top of page
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
There are a number of projects working to realize a future of distributed services; we aim to bring them all together in a convenient package.

Freedom Box is about gathering the software on inexpensive hardware
to give people their freedom back through aggregation and transition
of cloud services to friend to friend services.
Line 22: Line 16:
== Resources ==

 * Alioth project: https://alioth.debian.org/projects/freedombox/
Line 28: Line 18:
We live in a world where our use of the network is mediated by organizations that often do not have our best interests at heart. By building software that does not rely on a central service, we can regain control and privacy. By keeping our data in our homes, we gain useful legal protections over it. We live in a world where our use of the network is mediated by organizations that often do not have our best interests at heart. By building software that does not rely on a central service, we can regain control and privacy. By keeping our data in our homes, we gain useful legal protections over it. By giving back power to the users over their networks and machines, we are returning the Internet to its intended peer-to-peer architecture.
Line 32: Line 22:
We are working to build these systems; it is merely a small matter of programming. There are a number of projects working to realize a future of distributed services; we aim to bring them all together in a convenient package.

== Requirements ==

This is the result of a brainstorm from the debconf team.
Line 39: Line 33:
 * use at home (NOTE: legal significance of 4th amendment context)  * use at home (''expand: legal significance of 4th amendment context'')
Line 45: Line 39:

== Resources ==

 * Alioth project: https://alioth.debian.org/projects/freedombox/
Line 69: Line 67:
== ToDo ==

 * What we need
 * What we have
 * How to contribute
 * Who else is doing similar stuff
Line 70: Line 75:
Line 76: Line 82:

== ToDo ==
Line 79: Line 83:
 * What we need
 * What we have
 * How to contribute
 * Who else is doing similar stuff
Line 85: Line 85:
== Areas of work / architecture ==
Line 86: Line 87:
== Areas ==

Freedom Box Project

Inspired by Eben Moglen's vision of a small, cheap and simple computer that serves freedom in the home, we are building a Debian-based platform for distributed applications.

Freedom Box is about:

  • privacy
  • control
  • ease of use
  • dehierarchicalization

1. Vision Statement

We live in a world where our use of the network is mediated by organizations that often do not have our best interests at heart. By building software that does not rely on a central service, we can regain control and privacy. By keeping our data in our homes, we gain useful legal protections over it. By giving back power to the users over their networks and machines, we are returning the Internet to its intended peer-to-peer architecture.

In order to bring about the new network order, it is paramount that it is easy to convert to it. The hardware it runs on must be cheap. The software it runs on must be easy to install and admimistrate by anybody. It must be easy to transition from existing services.

There are a number of projects working to realize a future of distributed services; we aim to bring them all together in a convenient package.

2. Requirements

This is the result of a brainstorm from the debconf team.

  • enable people to reclaim their privacy and control of their data
  • return to the peer to peer nature of the net (vs. tendency towards hierarchical organization)
  • making a consumer product
  • easy to use for everyone (pre-installed, easily configured, easily restored)
  • inexpensive (dirt cheap)
  • use at home (expand: legal significance of 4th amendment context)

  • smooth transition from cloud services (e.g. social networks)
  • secure routing
  • generic and configurable
  • extensible
  • want hardware makers to be enthusiastic about the project

3. Resources

5. Example projects

6. ToDo

  • What we need
  • What we have
  • How to contribute
  • Who else is doing similar stuff

7. Done

8. Areas of work / architecture

  • project management tool
  • installer
  • UI
  • config
  • telephony
  • mail
  • hardware support

9. Issues

  • How is each box discovered and identified?
    • Need some way of finding your mates Most ISPs provide dynamic IPs. Would need to reply on external dynamic DNS service. (everyone ele's Freedom boxes?)
  • Upstream bandwidth
    • Very limited with typcial ADSL connections. How much of a problem is that if people keep downling photos from it whilst you try to use the net?
  • Mail
    • If the box does mail then spam is a problem. Running spamassassin dramitically increases resource requirements on box Collective spam processing is effective because it is easy to identify mass-mailing. Would need to do this in distributed manner (razor-style?)
  • 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 brings FB home from college)

10. Target Hardware

  • ?SheevaPlug/GuruPlug

    • Latter has WiFi and can act as an access point; both have heat problems.

  • OpenRD

    • Same hardware platform as the ?SheevaPlug, more flexible and more expensive

  • NSLU2
    • Discontinued?
  • Fonera 2.0n

    • Slow and very limited memory (64MB)