“A Personal Cloud”: a home cloud kit for personal data (centers) / “reappropriate your dataself”!

We’re entering the final straight of the research project Inhabiting and Interfacing the Cloud(s) and we can give at this point a first glimpse of the four design artifacts we are working on at the moment. They will constitute the main outcomes of our joint experimental effort (ECAL, HEAD, EPFL-ECAL Lab) and a kind of “personal cloud kit” (explained below). These creations will be accompanied by two books: one will present the results of the ethnographic research about “the cloud”, the other will present the design research process and its results – both in pod/pdf.

We already pointed out in the recent post “Updated Design Scenario” where we were heading. Since then, the different projects were better identified and started to get shaped. Some got eliminated. Prototyping and further technical tests are running in parallel at the moment.

 

IMG_1239ct

From the original “final scenario” sketch to …

iiclouds_006

… a “Personal Cloud Kit”, composed of various physical and digital modular artifacts.

 

What emerged reinforced from the main design scenario is that we seek to deliver four artifacts (some physical, some digital, some combined) which themselves will constitute the building blocks of what we’ll call “A Personal Cloud Kit”. All four parts of this kit will be openly accessible on a dedicated website (e.g. in a similar way to what OpenDesk is doing).

The purpose of this “home kit” is to empower designers, makers and citizens at large who would be interested to start develop their own cloud projects, manage or interact with their data or even to set up small scale personal data centers at their places (homes, offices, garages …)

From design research wrap-up to final artifacts, updated design scenario (in scribble mode, #2)

 

This post consists in an important update to the previous note “From design research wrap-up to final artifacts, a design scenario (in scribble mode, #1)“.

It’s main purpose is to narrow down the previously sketched scenario and become more precise about the possible artifacts we will develop. In doing so, the present description shows a likely path and tries to keep some coherence within the overall design that is segmented in four different areas, often combined (software, hardware furniture, responsive objects, visualization). Yet and even so several objects and functions are described and named in this post, it will continue to serve only as a general blueprint for the last phase of our I&IC joint design research, while the final outputs could still largely evolve, based on the same ideas and plan.

 

These ideas keep their importance though:

Based on the graphic “Motivations <-> Usages <-> Problems” and its description of procedures, based on our “Design Learnings” too, we’ve tried to translate and objectify these into “natural language” of actions (and problems). At this stage, this is still a trial, but we’ve listed five pairs of words that work in opposition (verbs vs. past participles) and that cover the spectrum of functions and procedures: To Care (vs. Neglected!), To Accumulate (vs. Vanished!), To Multiply (vs. Shrinked! ), To Freeze (vs. “Melted!”), To “Pimp” (vs. “Jumbled!”) — all these corresponding to a set of cloud actions and explained with more details below, after the break —

These 5 pairs of terms will drive the development of an alternative, domestic and hopefully objective Cloud (“Our Cloud”), built upon the open source software OwnCloud with the help of our own I&IC OwnCloud Core Processing Library (which will be further edited and editable therefore). This personal Cloud will have the opportunity to be hosted into a new type of diy (and domestic as well) 19″ Cabinet.

The 5 pairs of terms will further drive the implementation of 5 Controllers or Network Data/Bot Objects (“Smart Objects”). The aim of these “controllers” will be to give an everyday physical presence to each user’s personal Cloud, to its 5 main folders, contained files or data and the processes they undergo. The manipulation of some of these objects will include the idea of “natural interface” or “gestures”.

In addition to these 5 physical controllers, 1 or 2 “root objects” could help monitor and possibly moderate the overall behavior of “Our Cloud”.

For the development of these “smart objects”, we’ve decide to take into account the kind of objects or infrastructure that are already present in a domestic environment, things like single functional objects (i.e. lamps, electric plugs, consoles, mirrors, clocks, etc.) and revisit them with a slight sculptural approach. We’ve also decided to consider a “language” that takes into account “invisibility” or “immateriality” (i.e. electricity, electrostatics, magnets, light, reflections, air currents or temperature, dust).

Finally, all of the above should be distributed as open source.

Three summary drawings

Three drawings from the previous series of scenario that resume quite well what we intend to do:

 

An objectified cloud (a combination of open source software, automated behaviors and physical data controllers),

 

IMG_1239ct

IMG_1244ct

 

… that would find its physical location in a kind of retrofitted and open source 10″ cabinet,

 

IMG_1644ct

 

… to let anyone create and manage its own “tiny” and personal/home data center, based on existing or newly created open source technology.

From design research wrap-up to final artifacts, a design scenario (in scribble mode, #1)

 

Based on the design guidelines drawn from the wrap-up (recently published on this blog) and following a logic of “branching” from the existing (forks, branches, hacks, versions, etc.), we’ve identified in collaboration with the research team four main design projects/artifacts to further investigate in the context of Inhabiting and Interfacing the Cloud(s), following the questions addressed by the research project.  These design artifacts are intended to become the major outputs from our joint research:

 

1° We will continue develop the open source tools, the related procedures and our OwnCloud Processing library, possibly developing a Javascript version of it as well. (Christian Babski)

2° By way of practical applications about these libraries, we will design and develop I&IC’s “branches” of OwnCloud (OwnCloud + scripts). They will favor alternative ways to operate and interact with the Cloud in direct link with the identified “motivations” to use this universal service. (Patrick Keller, Christian Babski)

3° A set of networked data objects (“controllers”, kind of…) will be developed directly in connection with the above “branches” of OwnCloud. In order to embody the usually hidden processes and data so as to trigger objective interactions with the personal cloud. (Lucien Langton)

4° We will retrofit the 19″ server cabinet built around the standard unit “U” with the purpose to create a domestic version, a kind of modular and highly decentralized “house/personal data center”. (Léa Pereyre)

In order to address the maker and designer communities, users will be able to openly access the blueprints, the parts, the files or the code of these elements (librairies, OwnCloud versions, “controllers”, 19″ Cabinet and develop or adapt their own versions from them).

 

I drew a series of scribbles lately to sustain our investigations towards this final design scenario. It will serve to frame the development range for our design artifacts (points 1° – 4° above and top slideshow). It is further explained with additional information and images below, after the break.

 

I&IC design research wrap-up of sketches, towards artifacts

Following Nicolas Nova’s wrap-up regarding the ethnographic research about Cloud Computing which came to an end last April (publication to come) in the frame of Inhabiting and Interfacing the Cloud(s) (I&IC) and learning from it, it is also time for me to write a midterm status report about the design aspects of this ongoing work. It is the occasion to resume what we’ve been through along the process and highlight the most important elements.

 

founding_doc

“No-Stop City” (A. Branzi, 1969) used as an illustration in the founding document of the I&IC design research.
Image retrieved from the post “I&IC Preliminary Intentions” (05.09.2014).

 

We are therefore trying to put in evidence in this article what we’ve learned so far during the process and where this might lead us as design strategies during the last year of this design study. This while knowing that our plans are to produce design artifacts and functional prototypes as results of this research process — among other ones (books, tools, etc.)

Inhabiting & Interfacing the Cloud(s): all research workshops results at once (recap about usages, interaction, territory)

Note: the 6 research workshops we organized in the frame of Inhabiting and Interfacing the Cloud(s) took place during the “preliminary sketches” phase. A known and common phase that takes place in the course of each design process, during which we could naturally involve peers partners and students so to increase our “trials and errors”.

The outcomes of these experimental workshops were further analyzed in two posts by N. Nova and P. Keller (ethnographic “Lessons” and design “Learnings“), to further develop design proposals as the main results of this research, along with two publications to come.

 

Introduction to I&IC & field study (10.2014) – no sound :

Soilless – a research introduction and a field study from iiclouds.org design research on Vimeo.

More information about “Soilless, diagrams of uses” at HEAD – Genève on iiclouds.org

 

Situations, usages and alternative clouds (01.2016 & 11.2014), at HEAD – Genève:

Cloud Gestures – A workshop with S. Pohflepp at HEAD – Genève from iiclouds.org design research on Vimeo.

More information about  Cloud Gestures on iiclouds.org

 

Cloudified Scenarios – a workshop with James Auger at HEAD – Genève on Vimeo.

More information about Cloudified Scenarios on iiclouds.org

 

 

Interaction and data interfaces (11.2014 & 11.2015), at ECAL:

Botcaves – a workshop with Matthew Plummer-Fernandez at ECAL on Vimeo.

More information about  Networked Data Objects / Botcaves on iiclouds.org

 

The Everlasting Shadows – a workshop with rAndom International at ECAL from iiclouds.org design research on Vimeo.

More information about  The Everlasting Shadow on iiclouds.org

 

 

Networked and decentralized cloud infrastructures (02.2015), at EPFL-ECAL Lab:

Data territories – a workshop at EPFL-ECAL Lab with ALICE from iiclouds.org design research on Vimeo.

More information about  Distributed Data Territories on iiclouds.org

 

Hu T.-H. (2015). A Prehistory of The Cloud

a_prehistory

We may imagine the digital cloud as placeless, mute, ethereal, and unmediated. Yet the reality of the cloud is embodied in thousands of data centers, any one of which can use as much electricity as a midsized town. Even all these data centers are only one small part of the cloud. Behind that cloud-shaped icon on our screens is a whole universe of technologies and cultural norms, all working to keep us from noticing their existence. In this book, Tung-Hui Hu examines the gap between the real and the virtual (sic) in our understanding of the cloud. (…)

 

Note: while we do not necessarily follow Mr. Hu in all is assertions, we found it very interesting to digg into the potential past of this physical and digital construct (the cloud), even so it obviously mingles its own past with the one of the Internet, and previously with telegraph/telephone lines and railways that served as the initial paths for these “lines”.

Very interesting is also the part that presents the invention of the “user”, coming from an initial idea of sharing a common resource. It indeed seems that the “user” emerged from the ideas and technologies of “time-sharing”, then “multiprocessing”, when a single mainframe computer could remain stuck by a single user’s computations for hours or even days, sometimes for no results (error in the code).