> Mateus (gg/ghostglyph) is an artist and writer working in Leicester, UK. His work has included games, p2p networks, 3d printing, fictional alphabets, maps and filmmaking. He's interested in exploring narrative, place, text and language. He runs a meetup for Leicester-based artists called FTP, at Phoenix. He publishes experimental fiction and other texts at BRUISE.
< I have started a Bibliotecha instance(?) running from a Raspberry Pi 3b. I'm hoping to install this within a local artist-led space.
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.
I've also been experimenting with some other related tools/things:
- 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.
- 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.