+-+-+-+-+-+-+
|B|R|U|I|S|E|
+-+-+-+-+-+-+
\\

library

Bibliotecha

I have started a Bibliotecha instance(?) running from a Raspberry Pi 3b. I’m hoping to install this within a local artist-led space.

This is now installed at Two Queens. It is accessible from the communal spaces - and probably even to the street.

Informed by the PLS discussions I'm interested in thinking more about the physicality of these libraries. I'd like to see if it's possible to run a couple of instances in the region and rotate them periodically, creating traveling libraries.

It requires local administration - adding users, etc. So at the moment folks can email me to request an account. To access the library an account is needed and there are some rules for using the space (based on the needs of the host venue).

gg-notes

gg-notes which is a very simple web page that allows a user to create and save a simple .txt file. The use I’m imagining is that a visitor to the library could easily leave a record of their reading or annotation within the library.

Wemos D1 mini

I have a bunch of Wemos D1 mini boards from a project that fell apart a while back. They’re tiny boards that can be used in IoT type projects and can run as a miniature web server. I reinstalled the Arduino IDE and have been playing with a few sketches. Attempting to make the board do things. An offline/online hub. A hardware text. The text is on the chip. It isn’t useful like the library. It isn’t read/write. It’s store/read. It is storied. The example code is a few steps away from being something like text that is stored in a very specific space and accessible from close proximity. The login details could be shared with friends and when nearby they could open it up and see. Messages could pass along. Like the Bibliotecha setup it introduces its own constraints and methods of access, modes of community, that must be worked out and created.

reading

I keep a reading list updated here.



+-+-+-+-+-+-+
|B|R|U|I|S|E|
+-+-+-+-+-+-+

v2

~gg 06/22

sitemap

bruise.in