Datadroppers, a communal tool to drop off and/or pick up data (and then develop projects)

Note: fabric | ch, one of our partner on this project, has developed an open source data sharing tool that tries to simplify the procedures of declaring/logging and sharing data (from “connected sensor things”, mainly). This is Datadroppers. The service is somehow similar, yet slightly more versatile than the now vanished Pachube, or the contemporary, but proprietary, (that we’ve already mentioned in the resources section of this blog).

One of the interesting points in this case is that the new web service has been created by designers/coders that are themselves in need of such data service for their own work, promising in some ways that it won’t be commodified.

The other interesting point is the fact that they are formally involved in this design research project as well (through Christian Babski, developer), which should help us match the functions of Datadroppers with OwnCloud: through the use of the documented OwnCloud Core Processing Library and the one of Datadroppers, new paradigms and artifacts in file/data sharing and cloud operations could be envisioned, implemented and tested.

But moreover and mainly, projects made by the design community could be developed that will take advantages of the open resources of Processing (later on, Javascipt as well), OwnCloud and these libraries. Designing tools remains one of the goals of this design research project. Designing artifacts that will use these (improved) tools will be the work of the coming year in our design research…


Via fabric | rblg, via



I&IC Workshop #3 with Algopop at ECAL: Botcaves on Github

Note: a message from Matthew on Tuesday about his ongoing I&IC workshop. More resources to come there by the end of the week, as students are looking into many different directions!

I’ve started a github repository for the workshop so I can post code and tips there.

Please share with the students:

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.