<br><div class="gmail_quote">On Tue, Jul 3, 2012 at 8:59 AM, Michiel de Jong <span dir="ltr"><<a href="mailto:michiel@unhosted.org" target="_blank">michiel@unhosted.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is great stuff!<br>
<div><br>
On Tue, Jul 3, 2012 at 5:29 AM, Nick M. Daly <<a href="mailto:nick.m.daly@gmail.com" target="_blank">nick.m.daly@gmail.com</a>> wrote:<br>
> I'd *love* to see Tor and PageKite in the default image. I don't know<br>
> if there'll be time/expertise to get Tor into the image before EOY, but<br>
> we should be able to include PageKite, if nothing else. Bjarni's two<br>
> line install instructions are confounding! :)<br>
><br>
> Nick<br>
><br>
> 0: <a href="http://github.com/nickdaly/freedom-maker" target="_blank">http://github.com/nickdaly/freedom-maker</a><br>
><br>
> 1: <a href="http://github.com/nickdaly/plinth" target="_blank">http://github.com/nickdaly/plinth</a><br>
><br>
> 2: <a href="http://github.com/nickdaly/freedombox-privoxy" target="_blank">http://github.com/nickdaly/freedombox-privoxy</a><br>
<br>
</div>So even though ownCloud has a nicer interface than pyUnhosted, getting<br>
apache, sqlite, GD, php5 and ownCloud 4.0.4 all on a device with<br>
basically the power of a smartphone might be a bit ambitious. Also,<br>
the whole point of the remoteStorage web architecture is that the<br>
storage is just dumb storage and that all functionality and actual<br>
niceness is in unhosted web apps to which you connect your<br>
remoteStorage dynamically, instead of doing server-side webpage<br>
generation.<br>
<br>
So let me think about what steps we would need:<br>
<br>
- add pagekite and pyUnhosted to the image.<br>
<br>
- right now pyUnhosted outputs information (including the password you<br>
need) to the console. that should be piped somehow to plinth, so that<br>
the user can actually see it.<br>
<br>
- IIUC, for privoxy to work out of the box, we still need a way for<br>
the freedombox to become the default proxy for all devices on the<br>
wifi. how does that work?</blockquote><div><br>My understanding is that it would be a transparent proxy, i.e. it captures all connections.<br>So you don't have to configure anything on the client devices, they get privoxyfied automatically if they use the FreedomBox wifi.<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The easiest UI for this would be if the<br>
freedombox emits a wifi signal. people will understand that. If the<br>
freedombox only lets through https and ssh traffic, then this wifi<br>
signal can be unencrypted, like for instance the wifi signal at fosdem<br>
or other big conferences, so we help with the open wifi movement<br>
<a href="http://www.dslreports.com/shownews/EFF-Pushes-For-Open-WiFi-Movement-114016" target="_blank">http://www.dslreports.com/shownews/EFF-Pushes-For-Open-WiFi-Movement-114016</a><br>
by default (of course if the user is opposed to bandwidth altruism for<br>
some reason then they should be able to switch it off in plinth). If<br>
the freedombox does not emit its own wifi single, then i cannot see an<br>
easy first-use experience, but maybe i'm missing something.<br></blockquote><div><br>Idealistic as it may be, I don't think the open WiFi movement is appealing to the mainstream of Internet users. I think we'll get into all sorts of troubles and liabilities if we ship FreedomBox'es with open WiFi. Of course it could be optional, but I don't think it should be the default.<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- on first use, you would have to opt-in to setting up the public<br>
interface to your remoteStorage. so plinth would need a screen that<br>
say "choose your username and password at <a href="http://freedomstorage.org" target="_blank">freedomstorage.org</a> (or<br>
whatever we call it)", and from that moment on, it would be dialled in<br>
there, and ready for connecting your freedombox to unhosted web apps<br>
as remoteStorage.<br></blockquote><div><br>Sounds good to me, yeah the user will have to choose their PageKite name (and maybe be allowed to later change it? or add multiple names?)<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- we would have to set up said service, with for instance a 5-year<br>
plan included in the purchase of the off-the-shelf device. i know this<br>
proposal is only for creating the disk image, but we should also set<br>
up a pre-order production chain. As soon as 100 orders are in, we just<br>
organize a flashing-weekend, flash 100 devices in an afternoon, and<br>
ship them.<br></blockquote><div><br>Sounds great.<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- if we can resolve the first-use/wifi question then i think putting a<br>
box with privoxy+remoteStorage-through-pagekite on the market should<br>
be achievable.<br>
</blockquote></div><br>We should also have some updating mechanism.<br>Ideally, we would have a FreedomAppStore where you can download additional functionality, but that may be too hard for now, and a bit risky from a security perspective.<br>
<br>A simple future-ready updating mechanism could be:<br>1. When the FreedomBox boots, it checks if a certain file (together with a signature) is present on an attached USB drive.<br>2. If yes, and if the user enters their password, that file is executed and can update the box.<br>
<br>So we could start shipping simple Privoxy+remoteStorage+PageKite boxes now, and in a year or so we could tell people to download the update file and stick it into their box.<br><br>