Toward OwnCloud Core Processing Library

The purpose of the OwnCloud Core Processing Library is to give the possibility to program “cloud functionalities” within a well known and simplified designer oriented programming language (and community): Processing.


Therefore, the OwnCloud Core Processing Library linked with our personal cloud merges the Open Collaboration Service (OCS) Share API with higher level functions in order to implement seamlessly “search&share files” applications written in the well known designers oriented Processing programming language. This will soon become available to everyone on the I&IC website. The workshops we are currently running / will run during the coming weeks are helping/will help us fine tune its functionalities.


The OwnCloud Core Processing Library allows the automation of the action of sharing files and the action of file tagging within an open source OwnCloud environment. Search&Sharing tasks can be threaded and/or interdependent, everything depending on the kind of results expected from one application to another. Thus, these actions can be driven by unmanned processes, decision-making (copy, delete, share one or several files) based on related metadata (i.e. metadata relation/link) or based on external data, dug from the Internet or networked/connected items/things.

Setting up our own (small size) personal cloud infrastructure. Part #2, components

While setting up our own small size data center and cloud infrastructure, we’ve tried to exemplify the key constitutive ingredients of this type of computing infrastructure, as of November 2014. But we’ve also tried to maintain them as much open as we could, for further questioning, developments and transformations.

The first key ingredients are software parts and we’ve described them in the previous post about the same topic.

Comments on: Setting up our own (small size) personal cloud infrastructure. Part #1, components

Following Patrick’s post about our different options for choosing a “Cloud” software and the one that we finally made by choosing ownCloud. Here are a few related comments that develop our point of view and technical choices.

ArkOs, Openstack and RiakCS all take the hand over an entire server/system/computer, offering a kind of embedded linux system within a human-friendly interface, the kind of mechanism one can find on ready-to-use NAS (Network Attached Storage) hardware.

Basically, it transforms any regular computer into a NAS device. One of the key points about the structure we are trying to setup is to be able to host anything we would like/need or may appear interesting to probe. That includes our own website(s), web services in order to feed projects with data and any kind of applications that may be useful to try and develop within the frame of this research.

We do need therefore to keep the research server as generic as possible by using a normal linux distribution, which we can then enhance by any set of additional services. While ArkOS, Openstack and RiakCS are of course interesting projects, at some point, it may become already too specific for our goals.




Owncloud appears to be a simple web site structure dedicated to file sharing. As mentioned in my previous post, Owncloud proposes a set of APIs that allow the access to Owncloud features while being able to develop our own applications. Thus, these applications can rely on Owncloud while being hosted on a heterogeneous set of devices, network connected.

Setting up our own (small size) personal cloud infrastructure. Part #1, components

On the way to the development of different artifacts for the design research (Inhabiting & Interfacing the Cloud(s)), we’ll need to work with our own “personal cloud”. The first obvious reason is that we’ll need a common personal platform to exchange research documents, thoughts and work together between the different (geographically distributed) partners involved in the project. We are thus our own first case study. The second one is to exemplify the key components about how a small data center / cloud infrastructure might be assembled today and learn from it.

But then, more importantly, this will become necessary for two other main objectives: first one is that we would like to give access to “cloud” tools to the design, architecture and makers communities, so that they can start play and transform a dedicated infrastructure (and this won’t of course be possible with all type of systems); second one will possibly be for the “hands on” and “prototyping” parts of our research, for which we’ll need an accessible cloud based architecture to modify or customize (this includes both the software and hardware), around which some open developments, networked objects, new interfaces, apps, etc. could be developed.

From Bergcloud to ?

By Wednesday, October 29, 2014 Tags: 0052, Clouds, Hardware, Software Permalink 0

Even if unfortunately Bergcloud is a dead project now (and that it sadly brought down the design collective Berg too), I mention it here on our research blog as it probably has some connections with our own research project and what we might try to develop later as tools. The unsuccessful commercial approach of Bergcloud to connected objects should also be taken as a question toward this big “buzz” though.

Reblog > Deterritorialized Living, residency, storyboard for workshop and follow-up #1 (open call)


Note: I had the opportunity to lead a workshop last year for fabric | ch at the Tsinghua University in Beijing, for the student of the Tsinghua Art & Sciences Media Laboratory. The workshop took place during a residency at the university and we developed the idea of revisiting the computer cabinet, possibly inhabiting it and developing a symbiotic environment between human and computers. The workshop was short and ideas didn’t have the occasion to unfold very far unfortunately. It even became later an open call during the last Lisbon Architecture Triennale. Yet this workshop undoubtedly constituted the preliminary work before the redaction of this research project and it could continue to be a line of thinking during this project.

Below are the storyboard little sketches I made at that time to introduce this workshop.


Via fabric | rblg




I came back from Beijing more than a month ago now and before Christian Babski will return next week to China for fabric | ch during another month to finish our residency at the Tsinghua University (until mid July), I’m taking a bit of time to write a follow-up about the short workshop/sketch session I headed there with the students of Prof. Zhang Ga, at the Tsinghua Art & Sciences Media Laboratory.

I&IC – Preliminary intentions


The following text was written as a description of our goals later in 2013, prior to the start of the project. The structure of the text follows the given guidelines. So to say, to get financing.

It is nonetheless a blueprint of what we intend to do and is published on the I&IC blog as a matter of documentation.


Inhabiting and Interfacing the Cloud(s)

An intredisciplinary design research project under the co-direction of Prof. Patrick Keller (ECAL) and Nicolas Nova (HEAD). With the support of HES-SO and the collaboration of ECAL, HEAD, EPFL (Prof. Dieter Dietz) and EPFL+ECAL Lab (Dir. Nicolas Henchoz).


This design research project explores the creation of counter-proposals to the current expression of “Cloud Computing”, particularly in its forms intended for private individuals and end users (“Personal Cloud”). It is to offer a critical appraisal of this “iconic” infrastructure of our modernity and its user interfaces, because to date their implementation has followed a logic chiefly of technical development, governed by the commercial interests of large corporations, and continues to be seen partly as a purely functional, centralized setup. However, the Personal Cloud holds a potential that is largely untapped in terms of design, novel uses and territorial strategies. Through its cross-disciplinary approach, our project aims at producing alternative models resulting from a more contemporary approach, notably factoring in the idea of creolization (Glissant, 1990). From a practical standpoint, the project is intended to produce speculative versions of the “Personal Cloud” in the form of prototypes (whether functional or otherwise) of new interfaces, data processing, reactive environments and communicating objects. To do this, the project will be built around three dimensions forming the relevant pillars of a cross-disciplinary approach: interaction design, the architectural and territorial dimension, and the ethnographic dimension.