Michael, An WTC25

continuing discussions from here:
http://pad.constantvzw.org/p/etherbox
http://pad.constantvzw.org/p/Pi_install

Upcoming events where set-up can be tested:
Beginning of September, Bern: Frankenstein chatbots
October, Brussels: Geoff Cox / Hans Ulrik Andersson TransMediale / Peer review
December, Brussels: Diversions

What are the boundaries of the project?
* Portable infrastructure Local server
* Local services: Etherpad
* Local services: IRC
* Local services: Local files as archive
* Network:creating a hotspot for situated networks / working within existing / constrained network infrastructures (or none at all)
* Multiplicity of platform

• * Separation of "documents" from their editing platforms/applications
• * Identification / curation of "sources" in publishing workflows
• * Avoiding the "single platform will solve the problem" problem, allowing flexibility to use series of tools
• * Collaborative editing / writing / photography / recordings / coding 
• * "Bots" as ways of contributing tools to a system that's promiscuously open to plugins (bots vs. cgi ... in terms of lightness / portability / ability to stop/start / interrogability, visibility)

* "Portal" model

• * Shows services running
• * Link to "terms of services"
• * Links to inputs / outputs (import / export)

SItuating the work (alternatives to / integration with...)
* Dropbox
* Google Docs / Drive
* Twitter / Instagram / Flickr
* Wordpress

Priorities
------------
* Infrastructure and network
* Design of the "portal" page / landing page of portable server



The important of LABELING the pi AND the OpenWRT router with it's SUBNET + IP address

LETTING the pi use dhcp would be nicer (could it "auto sense" this?!)
OR>... is it unavoidable ... even PART of the work to create your own subnet ?!?!?!? YESSSSSSSSSSSSSSSSSSS

configuring openwrt box for new subnet
configuring pi with static ip for new subnet

making the root of the machine the root of the webserver...


!! Idea of server as an editable thing...
By changing apache's root to "/" instead of /var/www (change in two places!!)... suggests how the server itself can become an editable document.
Combined with editable descriptions, people could start to label where in the system changes are made and for what reason.
What's really significant about making the root of the machine, the root of the webserver is that every system file has a URL to for instance, then add on the pad as documentation.
(URLs mean you can write with the files!)

https://vimeo.com/144557453

In working today, we (re)discovered the significance of "simply" enabling a web interface to the entire file system as we could more comfortably read and search (ctrl-f) the ircd page, where we saw the network restrictions and made the correction of:

/* exempt {}: IPs that are exempt from deny {} and Dlines. (OLD d:) */
exempt {
        ip = "10.9.8.0/24";
};

So an "etherbox" would ideally mean the ability to collaboratively edit the entire system...
(and version control it ?!)
POC: what would it mean to make a git repo of THE WHOLE SYSTEM and then have an etherpad interface to the files ?!?!